APEX Listener/Glassfish: location of apex-config.xml - ORDS, SODA & JSON in the Database

Hi
I have some problems with the location of apex-config.xml.
I edited web.xml to (and removed the comments ;-) )
<init-param>
<param-name>config.dir</param-name>
<param-value>/usr/local/apex</param-value>
</init-param>
This directory exists and is writable. But still /tmp/apex is still used after a restart of the application.
My configuration:
APEX Listener ...10.43
Glassfish: 3.0.1
Any ideas?
Regards
Joe 

This is queued up for the fix.
-kris 

Hi
the problem still exists in version 1.10.230.17.38 !
Regards
Joe 

Does the apex-config.xml file exist in that path ?
It's checking for this:
// check for /path/to/<mountPoint>/apex-config.xml
// check path /path/to/apex-config.xml
if the apex-config.xml doesn't exist, it will fall back to the defaults.
-kris 

yes, it exists but it isn't used. ${java.io.tmpdir}/<Mount Point>/ is used instead, no matter which directory is specified in web.xml.
Joe
Edited by: JoeZ on 25.08.2010 05:04

Related

How to reconfigure apex listener - It stucks all the time

Greetings!
I m stuck to error Http://503. this happpens suddenly after some days while using appication for fixing this i redeployed apex.war file reinstall glassfish server but error was still there. then i all the time had to restart my app server and so that apex listener was reconfigure and then it was working.
i want to know without restarting my application server how i reconfigure apex listener
My enviroment: Oracle 10 g
Apex: 4.1.1
Glassfish.3.1.1
Application Express Listener: Apex 1.1.3 downloaded from www.oracle.com
URL for confiruging listener is : http://localhost:port/apex/listenerConfigure
First time its works, but if i access after pressing ok it gives message "The APEX Listener is already configured. Please login as Administrator to access APEX Listener Administration."
when i use this link http://localhost:port/apex/listenerAdmin, it requires password for windows security as i check all the passwords but no passwords works.
I m stuck on this from previous 2 months but didnt find any sutable solution. Please tell me if anyone knows
My Analysis: I saw my apex-config.xml file is placed in temp folder in c:/users/admin/appdata
is that a fault ?
Got follwing errors in server log files in domain
[#|2012-08-08T11:42:31.946+0500|WARNING|glassfish3.1.1|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=586;_ThreadName=Thread-2;|DPL8004: file open failure; file = file:/C:/Users/Administrator/AppData/Local/Temp/apex2928557998295514068.rar|#]
[#|2012-08-08T11:42:31.948+0500|WARNING|glassfish3.1.1|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=586;_ThreadName=Thread-2;|error in opening zip file --  invalid zip file: file:/C:/Users/Administrator/AppData/Local/Temp/apex2928557998295514068.rar|#]
[#|2012-08-08T11:42:31.950+0500|WARNING|glassfish3.1.1|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=586;_ThreadName=Thread-2;|DPL8004: file open failure; file = file:/C:/Users/Administrator/AppData/Local/Temp/apex2928557998295514068.rar|#]
[#|2012-08-08T11:42:31.950+0500|WARNING|glassfish3.1.1|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=586;_ThreadName=Thread-2;|error in opening zip file --  invalid zip file: file:/C:/Users/Administrator/AppData/Local/Temp/apex2928557998295514068.rar|#]
Edited by: Omzz on Aug 8, 2012 12:05 AM 
Hi Omzz,
My Analysis: I saw my apex-config.xml file is placed in temp folder in c:/users/admin/appdata
is that a fault ?It probably is. Your Temp folder might get cleaned up now and then. This will delete the APEX Listener configuration (including other relevant files stored in that area) causing APEX Listener to hang.
You should configure APEX Listener to use a permanent location for it's configuration instead. See the [url http://docs.oracle.com/cd/E21611_01/doc.11/e21058/config_file.htm#BABIBHAJ]corresponding chapter of the Installation Guide for details.
Note that this also concerns the caching directory if you use caching. A recent post of another user showed that this seems to be forgotten sometimes: {thread:id=2424440}
-Udo 
I changed like this in web.xml file but it doesnt works.
First of all when i changed and saved it i dont know how to convert it in*.war file, then i make apex folder a apex.rar file and upload on glassfish application tag, but it gives error that its an emplty file
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4"
     xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
     <display-name>ApexMod</display-name>
     <context-param>
          <param-name>config.dir</param-name>
          <E:/Apex>${java.io.tmpdir}/APEX</param-value>
     </context-param>
     <context-param>
          <param-name>version</param-name>
          <param-value>1.1.3.243.11.40</param-value>
     </context-param>
     
     <listener>
          <listener-class>oracle.dbtools.rt.web.SCListener</listener-class>
     </listener>
     <servlet>
          <description>
          </description>
          <display-name>HttpEndPoint</display-name>
          <servlet-name>HttpEndPoint</servlet-name>
          <servlet-class>oracle.dbtools.rt.web.HttpEndpoint</servlet-class>
     </servlet>
     <servlet-mapping>
          <servlet-name>HttpEndPoint</servlet-name>
          <url-pattern>/*</url-pattern>
     </servlet-mapping>
     <servlet>
          <description>
          </description>
          <display-name>Config</display-name>
          <servlet-name>Config</servlet-name>
          <servlet-class>oracle.dbtools.apex.config.Config</servlet-class>
     </servlet>
     <servlet-mapping>
          <servlet-name>Config</servlet-name>
          <url-pattern>/Config</url-pattern>
     </servlet-mapping>
     <servlet>
          <description>
          </description>
          <display-name>Admin</display-name>
          <servlet-name>Admin</servlet-name>
          <servlet-class>oracle.dbtools.apex.admin.Admin</servlet-class>
     </servlet>
     <servlet-mapping>
          <servlet-name>Admin</servlet-name>
          <url-pattern>/Admin</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>Admin</servlet-name>
          <url-pattern>/listenerAdmin</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>Admin</servlet-name>
          <url-pattern>/listenerConfigure</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>Admin</servlet-name>
          <url-pattern>/listenerStatus</url-pattern>
     </servlet-mapping>
     <servlet>
          <description>
          </description>
          <display-name>Forbidden</display-name>
          <servlet-name>Forbidden</servlet-name>
          <servlet-class>oracle.dbtools.apex.Forbidden</servlet-class>
     </servlet>
     <servlet-mapping>
          <servlet-name>Forbidden</servlet-name>
          <url-pattern>/____embedded/*</url-pattern>
     </servlet-mapping>
     <welcome-file-list>
          <welcome-file>index.html</welcome-file>
          <welcome-file>index.htm</welcome-file>
          <welcome-file>index.jsp</welcome-file>
          <welcome-file>default.html</welcome-file>
          <welcome-file>default.htm</welcome-file>
          <welcome-file>default.jsp</welcome-file>
     </welcome-file-list>
     <security-constraint>
          <web-resource-collection>
               <web-resource-name>APEX Listener Administration</web-resource-name>
               <url-pattern>/listenerAdmin</url-pattern>
               <http-method>GET</http-method>
               <http-method>POST</http-method>
          </web-resource-collection>
          <auth-constraint>
               <!-- NOTE: This role is not present in the default users file -->
               <role-name>Admin</role-name>
          </auth-constraint>
     </security-constraint>
     <security-constraint>
          <web-resource-collection>
               <web-resource-name>APEX Resource Templates</web-resource-name>
               <url-pattern>/resourceTemplates/*</url-pattern>
               <http-method>GET</http-method>
          </web-resource-collection>
          <auth-constraint>
               <!-- NOTE: This role is not present in the default users file -->
               <role-name>Admin</role-name>
          </auth-constraint>
     </security-constraint>
     <security-constraint>
          <web-resource-collection>
               <web-resource-name>APEX Resource Templates</web-resource-name>
               <url-pattern>/_/*</url-pattern>
               <http-method>GET</http-method>
               <http-method>PUT</http-method>
               <http-method>POST</http-method>
               <http-method>DELETE</http-method>
          </web-resource-collection>
          <auth-constraint>
               <!-- NOTE: This role is not present in the default users file -->
               <role-name>Admin</role-name>
          </auth-constraint>
     </security-constraint>
     <security-constraint>
          <web-resource-collection>
               <web-resource-name>APEX Listener Status</web-resource-name>
               <url-pattern>/listenerStatus</url-pattern>
               <http-method>GET</http-method>
          </web-resource-collection>
          <auth-constraint>
               <!-- NOTE: This role is not present in the default users file -->
               <role-name>Manager</role-name>
          </auth-constraint>
     </security-constraint>
     <login-config>
          <auth-method>BASIC</auth-method>
          <realm-name>APEX</realm-name>
     </login-config>
     <security-role>
          <description>The role that is required to log in to the APEX Listener Administration</description>
          <role-name>Admin</role-name>
     </security-role>
     <security-role>
          <description>The role that is required to log in to the APEX Listener Status</description>
          <role-name>Manager</role-name>
     </security-role>
</web-app> 
One thing more i read that in "init para" you have to give the path where apex-config.xml file located . But i dont know how to create this file, should i coyp that file from temp folder and paster it in given path in web.xml file ? 
You should change the following block in your web.xml
<context-param>
<param-name>config.dir</param-name>
<E:/Apex>${java.io.tmpdir}/APEX</param-value>
</context-param>to look like something similar to
<context-param>
  <param-name>config.dir</param-name>
  <param-value>E:/Apex/ApexListener/apex</param-value>
</context-param>One thing more i read that in "init para" you have to give the path where apex-config.xml file located .You can use a JVM parameter to pass in a path to the web.xml instead of "hard coding" it in there. But it's not necessary, and I'd recommend to take one step after each other, i.e. start with a fixed path in your web.xml and make your APEX Listener work.
To create a war file, you should simply use the tool jar shipped with your JDK. The procedure could be something like go to your apex.war, create a temporary folder for repackaging, unpack the apex.war to that temporary folder, edit the web.xml in the temporary folder, repackage the apex.war from the temporary folder, e.g.
E:
cd \APEX\ApexListener
md repack
cd repack
jar xf ..\apex.war
del apex.war
REM edit web.xml now
jar cf ..\apex.war .
rd /S /Q repackNote that this example assumes you have the Java bin directory (where jar is located) in your PATH environment variable. You may have to adjust paths to your actual scenario.
-Udo 
Hi Udo
<context-param>
<param-name>config.dir</param-name>
<param-value>E:/Apex/ApexListener/apex</param-value>
</context-param>
i am confused with this path understanding "E:/Apex/ApexListener/apex" .. Is this the path where my apex listener is located apex.war ? which i uploaded on glassfish server under application tag ?
OR i have to create this location on my any drive e.g its same like E:/Apex/ApexListener/apex .. and apex-config.xml will automatically created in this folder ?
and second thing
E:
cd \APEX\ApexListener
md repack
cd repack
jar xf ..\apex.war
del apex.war
REM edit web.xml now
jar cf ..\apex.war .
rd /S /Q repack
in follow these steps and upto edit web.xml its fine. after editing i execute jar cf..\apex.war it gives error
" D:\apex_listener.1.1.2.131.15.23\repack>jar cf ..\apex.war
'c' flag requires that input files specified!
Usage: jar {ctx}[vfm0M] [jar-file] [manifest-file] files ...
Options:
-c create new archive
-t list table of contents for archive
-x extract named (or all) files from archive
-v generate verbose output on standard error
-f specify archive file name
-m include manifest information from specified manifest file
-0 store only; use no ZIP compression
-M Do not create a manifest file for the entries
If any file is a directory then it is processed recursively.
Example: to archive two class files into an archive called classes.jar:
jar cvf classes.jar Foo.class Bar.class
Note: use the '0' option to create a jar file that can be put in your CLASSPATH"
what i have to do now ? 
i am confused with this path understanding "E:/Apex/ApexListener/apex" .. Is this the path where my apex listener is located apex.war ?Not necessarily. It's a separate path to store your configuration data. You can put it to another location if you want to.
OR i have to create this location on my any drive e.g its same like E:/Apex/ApexListener/apex .. and apex-config.xml will automatically created in this folder ?That's close to the way it is. I'd put an existing apex-config.xml there, e.g. copy from the current temp location.
in follow these steps and upto edit web.xml its fine. after editing i execute jar cf..\apex.war it gives error Then you didn't follow these steps thoroughly. It seems you omitted the *.* at the end of the jar command. It tells the tool to take the files/directories of the current directory.
-Udo 
Created Jar file with command
jar cvf apex.war . 
ALL steps done successfully,
Now i will see some days weather the same error occur or not.
Thanks For the help Udo! 
Hi Udo !
i want to discuss that if application is running with 5 tabs (5 pages) e.g. Tab 1 = Information, Tab 2 = Customer Profile, Tab 3 = Presentar Profile, Tab 4 = Group Profile and Tab 5 = sequence, assuming application was running fine glassfish is fine even all the pages are fine and checked by cliking on each page, data is displaying fine, but suddenly the same Http 503 error occurs when click on Tab 1 = Information, although rest of tabs are working fine, after few minutes again another tab is giving the same error.
How this will cause ? Is that the same issue of apex-config.xml file located in temp folder or not ? 
Hi Omzz,
[...]but suddenly the same Http 503 error occurs when click on Tab 1 = Information, although rest of tabs are working fine, after few minutes again another tab is giving the same error.
[...]
Is that the same issue of apex-config.xml file located in temp folder or not ?I don't think so. Could you check your server's log to find out what's causing that error?
Since you say it basically concerns one tab, I guess somethings wrong on that page, e.g. you have some long running query there that prevents the database connection to be returned to the connection pool. If you click repeatedly, this may consume all connections you have in your pool resulting the APEX Listener to be unable to serve additional requests and hence producing the 503 error. This would heal itself as soon as your long running query ends and the connection is coming back to the pool.
-Udo 
But the thing is a simple query
like SLECT * FROM CUSTOMER
WHERE CUTOMER_ID = 14
IF IT RUNS ON WEB AFTER SOME DAYS SAME QUERY GIVES ERROR WHILE OTHER PAGES WITH LONG RUNNING QUERY RUNS OK.. VISEVERSA. 
Well, I would have wondered if the 503 affected just one page. But as described above, you need just one page with one long-running query to get all connections busy. It doesn't matter which other page you call - when the connection pool has no idle connection left and is not allowed to open a new one (i.e., limit reached), the request can't be fulfilled. So you need to make sure that your page with a long running query doesn't use up all connections. Often this is caused by impatient users who think repeating a request will show up a result faster - causing an additional request while the first one is still processed in the database. You could prevent such behaviour with application logic. If you already did that but it didn't help you get the deployment stable, you have three other options: Implement a limitation of concurrent requests on pages with long-running queries at application level, reimplement the query basis to make long-running queries end faster, or increase the limit for the number of connections in APEX Listener's connection pool. Note that the latter approach might overload your database...
-Udo 
Hi Udo !
Back on the same question, today when i login in my apps on 2 page same error occurs "HTTP Status 500 - System Unavailable. Please try again later.
--------------------------------------------------------------------------------
type Status report
messageSystem Unavailable. Please try again later.
descriptionThe server encountered an internal error (System Unavailable. Please try again later.) that prevented it from fulfilling this request.
--------------------------------------------------------------------------------
GlassFish Server Open Source Edition 3.1.1".
Is that problem with database. because i have to reset my DB for oversoming this error.
What does it means ? is the query or seesion stucks ? and how i handle this 
Hi Omzz,
sorry for the late reply. Could you please provide APEX Listener's log output for that 500 error? It will usually provide additional information on the reason for that error, in many cases some ORA-Stack trace that will hint on what is wrong in your application or somewhere else. Without that piece of information it's hard to tell what to do...
-Udo

DWR servlet with Tomcat 6.0.9

Hi,
I've been trying to simply install the DWR .jar in my webapp, and I keep running into difficulty. I've read a million different guides on how to do this, but nothing seems to be working.
After I add dwr.jar to my [webapp]/WEB-INF/lib directory, I modified [webapp]/WEB-INF/web.xml with the following:
<servlet>
  <servlet-name>dwr-invoker</servlet-name>
  <servlet-class>org.directwebremoting.servlet.DwrServlet</servlet-class>
  <init-param>
    <param-name>debug</param-name>
    <param-value>true</param-value>
  </init-param>
</servlet>
<servlet-mapping>
  <servlet-name>dwr-invoker</servlet-name>
  <url-pattern>/dwr/*</url-pattern>
</servlet-mapping>Unfortunately, when I try to navigate to http://localhost:port/webapp/dwr in my browser, I get the following error:
HTTP Status 404 - /webapp/dwr
type Status report
message /webapp/dwr
description The requested resource (/webapp/dwr) is not available.
Everything I've read suggests that it is some problem with the way I am setting up my servlet, but my web.xml looks fine based on what I've read. Is there anything else I need to do, anything at all? I use commons-logging-1.1.1.jar because DWR needs this; does this have to be added to my web.xml or anything? Do I have to have any certain files in my webapp structure? I've created everything from scratch.
Any suggestions will be greatly appreciated.
Thanks,
Dan
Edited by: Djaunl on Apr 2, 2008 12:57 PM 
I'm having the same problem. I made a very complex message board using php, DWR on Apache and Tomcat. I lost a drive and all the server setup I had done. After reinstalling the server and publishing the message board backup I can't get the DWR portion to work. I get the
type: Status report
message: Servlet dwr-invoker is not available
description: The requested resource (Servlet dwr-invoker is not available) is not available.
Any suggestions?

Deployment on Tomcat

I am using Tomcat 3.3 stand alone with win2k & IIS. I put a .war file in the [tomcat_home]\webapps directory and it automatically expanded it. When I use the url localhost:8080\myservlet\HelloWorld it works, but localhost\myservlet\HelloWorld produces a 404 error. I know things are redirecting correctly because localhost\examples\servlets works fine. What is the problem? Thanks for any help. 
you may need to add the path mapping in uriworkers.properties or jk.properties in tomcat_home/conf?
how did you setup the iis->tomcat mapping? did you use a connector? 
I used the method explained at this website:
http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-iis-howto.html
this should be how to access my servlet:
localhost/HTMLPage/HTMLPage
I made a apps-HTMLPage.xml in the /conf directory, then I use:
startup -jkconf
and it automatically generates a uriworkers.properties file in the /conf/auto directory, here it is:
###################################################################
# Auto generated configuration. Dated: Tue Oct 28 13:02:56 CST 2003
###################################################################
#
# Default worker to be used through our mappings
#
default.worker=ajp13
/admin=$(default.worker)
/admin/*=$(default.worker)
/examples=$(default.worker)
/examples/*=$(default.worker)
/HTMLPage=$(default.worker)
/HTMLPage/*=$(default.worker)
That is the process shown in the how to guide. When I look in the IIS web log the redirect dll isn't being used when I type in localhost/HTMLPage/HTMLPage or localhost/HTMLPage. I've restarted IIS and Tomcat, but one of them isn't recognizing the changes, unless I've missed a step again. I don't know, Thanks again for any help.

JNDI Error

Been a busy morning... Some applications are failing to run when moved to my "deployment app server". I'm getting a log entry that says in part "[javax.naming.InvalidNameException: Real JNDI name cannot be empty for jdbc/ffdb]". Is this a Creator settings issue, or an App Server settings Issue? Any suggestions? It seems intermittant, if I create a new database connection under a different name, it works for a day or so..
harold 
Did you re deploy the application or just update the entries via Creator?
What does the entries in domain.xml look like for jdbc./ffdb? Is this associated with a pool?
Check the sun-*.xml in the under domain1/.applications/<your_app> to see if this was entered correctly.
It could be possible that Creator did not properly update the info when you made your changes 
Did you re deploy the application or just update the
entries via Creator?I've redeployed. How/where would I update the entries in Creator?
What does the entries in domain.xml look like for
jdbc./ffdb? Is this associated with a pool?On the AppServer, the section looks like this:
<resources>
<jdbc-resource enabled="true" jndi-name="jdbc/__TimerPool" object-type="system-all" pool-name="__TimerPool"/>
<jdbc-resource enabled="true" jndi-name="jdbc/PointBase" object-type="user" pool-name="PointBasePool"/>
<jdbc-resource enabled="true" jndi-name="jdbc/ff_local" object-type="user" pool-name="MySQLPool"/>
<jdbc-resource enabled="true" jndi-name="jdbc/ffdb" object-type="user" pool-name="MySQLPool1">
<description>MySQL Beta Forest Farm DB</description>
</jdbc-resource>
Check the sun-*.xml in the under
domain1/.applications/<your_app> to see if this was
entered correctly.under domain1/applications/ there are only three entries:
drwxr-xr-x 4 root root 4096 Jul 26 14:33 j2ee-apps
drwxr-xr-x 3 root root 4096 Jul 30 12:19 j2ee-modules
drwxr-xr-x 2 root root 4096 Jul 26 14:29 lifecycle-modules
none look like mine
It could be possible that Creator did not properly
update the info when you made your changesIn a possibly related item, none of the DataSource entries in Creator stay when I stop/restart the Creator program.....
harold
Sorry, if you deployed a ear, you would go to the j2ee-apps, for a standalone moudle, the j2ee-modules it is there you will find your app and the exploded directory.
The resources look ok in domain.xml, so my hunch is the sun*xml is missing an entry.
Unforunately, i have not played with creator, so you might try the creator newsgroup for help if we have no luck in the sun* xml files 
I've been moving the .WAR file over and using the autodeploy folder... I'm assuming that if the same DataSource exists on the development and the deployment systems, the program should work. I did find a problem with including the user and password in the URL under creator, the program stopped reading the .xml file part way thru (stopping at the &) and then complaining about unexpected eof.... but I don't think this cured the the JNDI error.
What folder are the sun*.xml files in?
harold 
If this is just a war file, you should see a sub directory under the j2ee-modules directory under applications. In there you should find a directory containing the contests of your war.
You will have a WEB-INF directory there which is where the sun-web.xml will be
Here are the contents of the sun-web.xml file. Looks pretty skimpy to me <smile>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server
8.0 Servlet 2.4//EN" "http://www.sun.com/software/appserver/dtds/sun-web-app_2_4
-0.dtd">
<sun-web-app xmlns="http://java.sun.com/xml/ns/j2ee">
<context-root>/ff07</context-root>
<class-loader delegate="false"/>
</sun-web-app>harold 
Yes, you should have a something like
<resource-ref>
<resource-ref-name>jdbc/MyDB</resource-ref-name>
<jndi-name>jdbc/MyDB</resource-ref-name>
<default-resource-principal>
<name>foo</name>
<passoword>bar</password>
</default-resource-principal>
</resource-ref>
Again assuming you do a JNDI lookup from your web app which it sounds like it does 
OK, the problem seems to have changed when I upgraded the ServerAPP and Creator with the latest patch. Now the sun-web.xml file has these weird characters appended to the end of them:
<res-ref-name>jdbc/ffdb</res-ref-name>
<jndi-name>jdbc/ffdb_RaveGenerated_1091462679</jndi-name>
I didn't have the RaveGenerated1091462679 before... I'm guessing that Creator changed something...
harold 
I am not sure why Rave generated the JNDI name as it did, but i guess the question is can you find your application now or do you still have a JNDI error? 
The application throws an exception:
Exception Details: javax.faces.el.EvaluationException
javax.faces.FacesException: javax.faces.FacesException: Can't instantiate class: 'webapplication1pb1.Page1'.. class webapplication1pb1.Page1 : javax.faces.FacesException: java.sql.SQLException: JdcbRowSetXImpl (connect): (JNDI) Unable to connect: ffdb_RaveGenerated_1091462679 not found
I'm assuming the server is set up for jndi/ffdb, not jndi/ffdb_RaveGenerated_1091462679.
harold 
You could modify this via deploy tool and redeploy and see if that gets you further.
The AppServer is remote, and it seems that the deploytool is a "Xwindows" app, and I didn't put X on that box, to keep it "perky"... is ther another way to do it? Can JNDI make a synonym, i.e. send requests for
jdbc/ffdb_RaveGenerated_1091724629 to jdbc/ffdb ??
harold 
Well I got the app running again by just creating another jdbc resource called      
jdbc/ffdb_RaveGenerated_1091724629... not elegant, but I'm no longer dead-in-the-water...:)
harold 
You could update update the xml file and add it back to the jar and use the asadmin command to deploy the app again.
Glad to see you are running at least

DSCC timeout using Tomcat

Hi all. I've installed DS 6.3 to fool around with and setup DSCC to run with Tomcat. Anyone know how to increase the timeout value so I don't have to keep logging into the console over and over? Thanks ... 
Hi,
Here is the command.
Check if the timeout value is set:
/usr/sbin/wcadmin list -p
to set the value
/usr/sbin/wcadmin add -p -a root session.timeout.value=720
This will set the timeout value for 12hours. 
Thanks for the reply but that won;t work for me. I believe those commands are used when you are running the sun admin server. I'm running tomcat. There is no wcadmin command on my box. 
Any solution for this yet? I am running AS 8.2 and have the same issue.
Thanks,
Eric 
Here's how. Find where your dscc app has been deployed.
Under tomcat /path/to/tomcat/webapps/dsccEdit /path/to/tomcat/webapps/dscc/WEB-INF/web.xmlIt should look like this:
<web-app>
<context-param>
  <param-name>sun.directory.dcc.path.slapx</param-name>
  <param-value>/path/to/sun/dsee/6.3/bits/ds6/bin/dsadm</param-value>
...Change it to something like that:
<web-app>
<session-config>
  <!-- set the session to last 24 hours -->
  <session-timeout>1440</session-timeout>
</session-config>
<context-param>
  <param-name>sun.directory.dcc.path.slapx</param-name>
  <param-value>/path/to/sun/dsee/6.3/bits/ds6/bin/dsadm</param-value>
</context-param>
...if you then log onto tomcat manager application list (http://localhost:8080/manager/html/list by default) you can verify that your new settings were taken into account.
cheers
-=arnaud=-

Categories

Resources