Status: APEX Listener is not configured. - ORDS, SODA & JSON in the Database

Apex 4.0 on Oracle Database 10 XE.
(version 3.2 was previously in use with the DB instance)
I have gone thru installation scenario 1 :
1.5.1 Scenario 1: Downloading from OTN and Configuring the Oracle Application Express Listener
...
Step 6: Download and Install Oracle Application Express Listener
The listener implementation with OC4J version 10.1.3.5 (java: jdk1.5.0_10)
APEX Listener version : 1.10.179.10.43
http://localhost:8888/apex/listenerConfigure
On the main page (connection tab) when I press Apply button with specifed parameters :
500 Internal Server Error
Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response.
Please consult the application log for details.
OC4J log:
C:\K\O\OC4J_10135\bin>oc4j -start
Starting OC4J from C:\K\O\OC4J_10135\j2ee\home ...
2010-07-03 13:56:20.531 NOTIFICATION Auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\dms.war...
2010-07-03 13:56:20.531 NOTIFICATION Unjar C:\K\O\OC4J_10135\j2ee\home\applications\dms.war in C:\K\O\OC4J_10135\j2ee\home\applications\dms
2010-07-03 13:56:20.531 NOTIFICATION Finished auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\dms.war
2010-07-03 13:56:20.546 NOTIFICATION Auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\JMXSoapAdapter-web.war...
2010-07-03 13:56:20.546 NOTIFICATION Unjar C:\K\O\OC4J_10135\j2ee\home\applications\JMXSoapAdapter-web.war in
C:\K\O\OC4J_10135\j2ee\home\applications\JMXSoapAdapter-web
2010-07-03 13:56:20.796 NOTIFICATION Finished auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\JMXSoapAdapter-web.war
2010-07-03 13:56:20.906 NOTIFICATION Auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\jmsrouter.war...
2010-07-03 13:56:20.906 NOTIFICATION Unjar C:\K\O\OC4J_10135\j2ee\home\applications\jmsrouter.war in C:\K\O\OC4J_10135\j2ee\home\applications\jmsrouter
2010-07-03 13:56:20.921 NOTIFICATION Finished auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\jmsrouter.war
2010-07-03 13:56:20.968 NOTIFICATION Auto-unpacking C:\K\O\OC4J_10135\j2ee\home\connectors\datasources\datasources.rar...
2010-07-03 13:56:21.015 NOTIFICATION Unjar C:\K\O\OC4J_10135\j2ee\home\connectors\datasources\datasources.rar in
C:\K\O\OC4J_10135\j2ee\home\connectors\datasources\datasources
2010-07-03 13:56:21.015 NOTIFICATION Finished auto-unpacking C:\K\O\OC4J_10135\j2ee\home\connectors\datasources\datasources.rar
2010-07-03 13:56:21.078 NOTIFICATION Auto-unpacking C:\K\O\OC4J_10135\j2ee\home\connectors\OracleASjms\OracleASjms.rar...
2010-07-03 13:56:21.078 NOTIFICATION Unjar C:\K\O\OC4J_10135\j2ee\home\connectors\OracleASjms\OracleASjms.rar in
C:\K\O\OC4J_10135\j2ee\home\connectors\OracleASjms\OracleASjms
2010-07-03 13:56:21.140 NOTIFICATION Finished auto-unpacking C:\K\O\OC4J_10135\j2ee\home\connectors\OracleASjms\OracleASjms.rar
Jul 3, 2010 1:56:21 PM com.evermind.server.XMLDataSourcesConfig parseRootNode
INFO: Legacy datasource detected...attempting to convert to new syntax.
2010-07-03 13:56:21.187 NOTIFICATION Auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\javasso.ear...
2010-07-03 13:56:21.187 NOTIFICATION Unjar C:\K\O\OC4J_10135\j2ee\home\applications\javasso.ear in C:\K\O\OC4J_10135\j2ee\home\applications\javasso
2010-07-03 13:56:21.187 NOTIFICATION Finished auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\javasso.ear
2010-07-03 13:56:21.203 NOTIFICATION Auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\javasso\javasso-web.war...
2010-07-03 13:56:21.203 NOTIFICATION Unjar C:\K\O\OC4J_10135\j2ee\home\applications\javasso\javasso-web.war in
C:\K\O\OC4J_10135\j2ee\home\applications\javasso\javasso-web
2010-07-03 13:56:21.265 NOTIFICATION Finished auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\javasso\javasso-web.war
2010-07-03 13:56:21.390 NOTIFICATION Auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\ascontrol.ear...
2010-07-03 13:56:21.390 NOTIFICATION Unjar C:\K\O\OC4J_10135\j2ee\home\applications\ascontrol.ear in C:\K\O\OC4J_10135\j2ee\home\applications\ascontrol
2010-07-03 13:56:25.796 NOTIFICATION Finished auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\ascontrol.ear
2010-07-03 13:56:27.125 NOTIFICATION Auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\ascontrol\ascontrol.war...
2010-07-03 13:56:27.125 NOTIFICATION Unjar C:\K\O\OC4J_10135\j2ee\home\applications\ascontrol\ascontrol.war in
C:\K\O\OC4J_10135\j2ee\home\applications\ascontrol\ascontrol
2010-07-03 13:56:35.609 NOTIFICATION Finished auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\ascontrol\ascontrol.war
Jul 3, 2010 1:56:40 PM com.evermind.server.XMLApplicationServerConfig randomizeJtaAdminPassword
INFO: Updating JtaAdmin account
10/07/03 13:56:40 Set OC4J administrator's password (password text will not be displayed as it is entered)
Enter password:
Confirm password:
The password for OC4J administrator "oc4jadmin" has been set.
10/07/03 13:56:56 The OC4J administrator "oc4jadmin" account is activated.
10/07/03 13:57:02 Oracle Containers for J2EE 10g (10.1.3.5.0) initialized
2010-07-03 13:58:57.750 NOTIFICATION Application Deployer for Apex4Listener STARTS.
Jul 3, 2010 1:58:57 PM com.evermind.server.XMLDataSourcesConfig parseRootNode
INFO: Legacy datasource detected...attempting to convert to new syntax.
2010-07-03 13:58:57.765 NOTIFICATION Copy the archive to C:\K\O\OC4J_10135\j2ee\home\applications\Apex4Listener.ear
2010-07-03 13:58:57.781 NOTIFICATION Initialize C:\K\O\OC4J_10135\j2ee\home\applications\Apex4Listener.ear begins...
2010-07-03 13:58:57.796 NOTIFICATION Auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\Apex4Listener.ear...
2010-07-03 13:58:57.796 NOTIFICATION Unpacking Apex4Listener.ear
2010-07-03 13:58:57.796 NOTIFICATION Unjar C:\K\O\OC4J_10135\j2ee\home\applications\Apex4Listener.ear in C:\K\O\OC4J_10135\j2ee\home\applications\Apex4Listener
2010-07-03 13:58:57.859 NOTIFICATION Done unpacking Apex4Listener.ear
2010-07-03 13:58:57.859 NOTIFICATION Finished auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\Apex4Listener.ear
2010-07-03 13:58:57.875 NOTIFICATION Auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\Apex4Listener\apex.war...
2010-07-03 13:58:57.875 NOTIFICATION Unpacking apex.war
2010-07-03 13:58:57.875 NOTIFICATION Unjar C:\K\O\OC4J_10135\j2ee\home\applications\Apex4Listener\apex.war in
C:\K\O\OC4J_10135\j2ee\home\applications\Apex4Listener\apex
2010-07-03 13:58:58.031 NOTIFICATION Done unpacking apex.war
2010-07-03 13:58:58.031 NOTIFICATION Finished auto-unpacking C:\K\O\OC4J_10135\j2ee\home\applications\Apex4Listener\apex.war
2010-07-03 13:58:58.031 NOTIFICATION Initialize C:\K\O\OC4J_10135\j2ee\home\applications\Apex4Listener.ear ends...
2010-07-03 13:58:58.031 NOTIFICATION Starting application : Apex4Listener
2010-07-03 13:58:58.031 NOTIFICATION Initializing ClassLoader(s)
2010-07-03 13:58:58.031 NOTIFICATION Initializing EJB container
2010-07-03 13:58:58.031 NOTIFICATION Loading connector(s)
2010-07-03 13:58:58.062 NOTIFICATION Starting up resource adapters
2010-07-03 13:58:58.062 NOTIFICATION Initializing EJB sessions
2010-07-03 13:58:58.062 NOTIFICATION Committing ClassLoader(s)
2010-07-03 13:58:58.062 NOTIFICATION Initialize apex begins...
2010-07-03 13:58:58.062 NOTIFICATION Initialize apex ends...
2010-07-03 13:58:58.062 NOTIFICATION Started application : Apex4Listener
2010-07-03 13:58:58.062 NOTIFICATION Binding web application(s) to site default-web-site begins...
2010-07-03 13:58:58.062 NOTIFICATION Binding apex web-module for application Apex4Listener to site default-web-site under context root apex
2010-07-03 13:58:58.109 NOTIFICATION Binding web application(s) to site default-web-site ends...
2010-07-03 13:58:58.125 NOTIFICATION Application Deployer for Apex4Listener COMPLETES. Operation time: 375 msecs
10/07/03 13:59:25 Using Config file:C:\DOCUME~1\Mihaela\LOCALS~1\Temp\\apex\apex-config.xml
10/07/03 13:59:25 Mime Mappings in : C:\K\O\OC4J_10135\j2ee\home\applications\Apex4Listener\apex\WEB-INF\mimes.xml
10/07/03 14:02:16 APEX Listener version : 1.10.179.10.43
10/07/03 14:02:16 APEX Listener server info: Oracle Containers for J2EE 10g (10.1.3.5.0)
2010-07-03 14:20:43.718 ERROR [RealmLoginModule] authentication failed
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Application.log
10/07/03 14:19:36.531 apex: Servlet error
java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z
     at oracle.dbtools.apex.admin.AdminManager.validConnection(AdminManager.java:337)
     at oracle.dbtools.apex.admin.AdminManager.validateInfo(AdminManager.java:168)
     at oracle.dbtools.apex.admin.AdminManager.processAdministration(AdminManager.java:81)
     at oracle.dbtools.apex.admin.Admin.doPost(Admin.java:89)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:734)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:391)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:908)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:458)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:226)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:127)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:116)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0)
].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
What is wrong ?
How to proceed. 

Any solution?
I have same error, in same enviroment. I read about use JDK 1.6. 

This error means it's using a lower version of java. 1.6+ is required. The isEmpty is something that was added in 1.6.
java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z
-kris 

Problem resolved installing jdk 1.6 update 21 in the OC4J server.

Related

Error launching Application Server from within Java Studio Creator

I'll post the server.log down below. I can no longer start the Application Server.
A few months ago I set up a Sun Blade 100 from scratch as a development box to test this Sun software. I installed Solaris 10, and also Java Studio Creator. Everything worked fine, as I did the tutorials and they ran just fine.
I then installed Net beans and played around with that a little. I also installed a bunch of updates using the manual Sun update manager. I then returned to Java Studio Creator about a month later, I started working on my first real web application, but when I tried to run it the application server would not start. Since this happened, i've uninstalled Net beans, and uninstalled and reinstalled Java Studio Creator, without Netbeans, and it still doesn't work.
Please help me diagnose the problem. Here is the server.log file, see below the log for more comments about the imq broker:
start
display|#]
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string "-dt-interface system-medium-r-normal-s*-*-*-*-*-*-*-*-*" to type FontSet
Warning: Cannot convert string "-monotype-arial-regular-r-normal--*-140-*-*-p-*-iso8859-1" to type FontStruct
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string "-dt-interface user-medium-r-normal-s*-*-*-*-*-*-*-*-*" to type FontSet
[#|2006-07-02T18:00:48.068-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
[#|2006-07-02T18:00:48.080-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory /home/daren/sun/Creator2_1/SunAppServer8/imq/var/instances|#]
[#|2006-07-02T18:00:48.081-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2006-07-02T18:00:48.083-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:28676]. - cause: java.io.IOException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:427)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:54)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
at com.sun.rave.tray.RavePEMain.main(RavePEMain.java:37)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:28676]. - cause: java.io.IOException
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:191)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:116)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:54)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:61)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:291)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:113)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:98)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:613)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1194)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1949)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:745)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:315)
at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:783)
at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:335)
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:396)
... 4 more
Caused by: java.io.IOException
at com.sun.enterprise.server.ss.ASInputStream.waitForSelect(ASInputStream.java:118)
at com.sun.enterprise.server.ss.ASInputStream.read(ASInputStream.java:81)
at com.sun.enterprise.server.ss.ASInputStream.read(ASInputStream.java:73)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at com.sun.messaging.jmq.io.PortMapperTable.readLine(PortMapperTable.java:277)
at com.sun.messaging.jmq.io.PortMapperTable.read(PortMapperTable.java:233)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:185)
... 22 more
Caused by: java.io.IOException: Invalid argument
at sun.nio.ch.DevPollArrayWrapper.poll0(Native Method)
at sun.nio.ch.DevPollArrayWrapper.poll(DevPollArrayWrapper.java:158)
at sun.nio.ch.DevPollSelectorImpl.doSelect(DevPollSelectorImpl.java:68)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80)
at com.sun.enterprise.server.ss.ASSelector.select(ASSelector.java:92)
at com.sun.enterprise.server.ss.ASInputStream.waitForSelect(ASInputStream.java:101)
... 29 more
|#]
[#|2006-07-02T18:00:48.645-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: Error occurred on connection creation [127.0.0.1:28676]. - cause: java.io.IOException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:376)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:178)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:172)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
at com.sun.rave.tray.RavePEMain.main(RavePEMain.java:37)
|#]
=========MORE NOTES============
My imq broker log file looks fine, it appears to start up just fine, in fact, pointing my webbrowser to the broker port reveals the following
101 imqbroker 3.7
portmapper tcp PORTMAPPER 28676
admin tcp ADMIN 32976 [hostname=127.0.0.1]
jms tcp NORMAL 32975 [hostname=127.0.0.1]
Any idea on how i can fix the problem, or figure out why it's failing?
Thanks in advance
Daren 
I wanted to followup my original post with 2 more things. First to state that Now I am running a brand new installation of Java Studio Creator with no projects. Here's my routine to create the error's. 1) Install Java Studio Creator from scratch into a new folder, 2) During the installation the final act of the installation wizard is to start the Application Server, well, it fails there with these logs.
And finally, here is the imqbroker log
bash-3.00$ cat log/log.txt
# 1151950322199 Do not modify this line
[03/Jul/2006:14:12:06 EDT]
================================================================================
Sun Java(tm) System Message Queue 3.7
Sun Microsystems, Inc.
Version: 3.7 (Build 3-e)
Compile: Mon Dec 5 21:58:50 PST 2005
Copyright ? 2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.5.0_06 Sun Microsystems Inc. /home/daren/Sun/Creator2_1/java/jre
[03/Jul/2006:14:12:06 EDT] License: Sun Java(tm) System Message Queue 3.7 Platform Edition
[03/Jul/2006:14:12:06 EDT] IMQ_HOME=/home/daren/Sun/Creator2_1/SunAppServer8/imq
[03/Jul/2006:14:12:06 EDT] IMQ_VARHOME=/home/daren/Sun/Creator2_1/SunAppServer8/domains/creator/imq
[03/Jul/2006:14:12:06 EDT] SunOS 5.10 sparc 127.0.0.1 (1 cpu) daren
[03/Jul/2006:14:12:06 EDT] Max file descriptors: 4096 (4096)
[03/Jul/2006:14:12:06 EDT] Java Heap Size: max=194688k, current=32448k
[03/Jul/2006:14:12:06 EDT] Arguments: -javahome /home/daren/Sun/Creator2_1/java -varhome /home/daren/Sun/Creator2_1/SunAppServer8/domains/creator/imq -Dimq.hostname=127.0.0.1 -name imqbroker -port 28676 -bgnd -silent
[03/Jul/2006:14:12:06 EDT] [B1004]: Starting the portmapper service using tcp [ 28676, 50, 127.0.0.1 ] with min threads 1 and max threads of 1
[03/Jul/2006:14:12:06 EDT] [B1060]: Loading persistent data...
[03/Jul/2006:14:12:06 EDT] Using built-in file-based persistent store: /home/daren/Sun/Creator2_1/SunAppServer8/domains/creator/imq/instances/imqbroker/
[03/Jul/2006:14:12:08 EDT] [B1136]: Processing stored transactions
[03/Jul/2006:14:12:08 EDT] [B1013]: Auto Creation of Queues is Enabled
[03/Jul/2006:14:12:08 EDT] [B1151]: Loading destination mq.sys.dmq [Queue] with 0 messages
[03/Jul/2006:14:12:08 EDT] [B1152]: Loading of destination mq.sys.dmq [Queue] complete
[03/Jul/2006:14:12:08 EDT] [B1004]: Starting the admin service using tcp(host = 127.0.0.1, port=0, mode=dedicated) with min threads 4 and max threads of 10
[03/Jul/2006:14:12:08 EDT] [B1004]: Starting the jms service using tcp(host = 127.0.0.1, port=0, mode=dedicated) with min threads 10 and max threads of 1000
[03/Jul/2006:14:12:09 EDT] [B1039]: Broker "imqbroker#127.0.0.1:28676" ready.
[03/Jul/2006:14:13:00 EDT] WARNING [B3164]: The portmapper service got an exception processing a request from client 127.0.0.1. The client may need to attempt the connection again:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at com.sun.messaging.jmq.jmsserver.service.PortMapper.run(PortMapper.java:485)
at java.lang.Thread.run(Thread.java:595)
bash-3.00$ 
I suspect there is a bug in the Async Startup code. As a workaround, can you try adding, in domain.xml, the following line:
<jvm-options>-Dcom.sun.enterprise.server.ss.ASQuickStartup=false</jvm-options>
and update the thread?
Thanks. I will ping Binod, who manages AsyncStartup/JMS code better than me.
-- Jeanfrancois 
Caused by: java.io.IOException: Invalid argument
at sun.nio.ch.DevPollArrayWrapper.poll0(Native Method)
at sun.nio.ch.DevPollArrayWrapper.poll(DevPollArrayWrapper.java:158)
at sun.nio.ch.DevPollSelectorImpl.doSelect(DevPollSelectorImpl.java:68)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80)
at com.sun.enterprise.server.ss.ASSelector.select(ASSelector.java:92)
at com.sun.enterprise.server.ss.ASInputStream.waitForSelect(ASInputStream.java:101 )
This indicates that this is the JDK issue http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322825
Only the second workaround will work with Sun appserver. i.e Keep the file descriptor limit above 8193 
Thank you Jeanfrancois and Binod.
Setting rlim_fd_max=8193 as outlined in your included hyperlink did fix my problem. I now know the sequence of events that led up to me having this problem.
1) Initial install of Solaris on Blade 100
2) Install of Java Studio Creator
At this point, the tutorials all worked fine with the App server starting every time.
3)
I then followed the directions here http://www.postgresql.org/docs/techdocs.31 (note: the hyperlink for the document in pdf format doesn't seem to be working at the moment) for installing postgresql on Solaris.
The document mentions to set rlim_fd_max=4096 as well as some other sytem configuration variables.
4) I created some command line jdbc programs to work with postgres. Running these via JSC did not require starting up the web app service. Java Studio Creator appeared to still b working fine for a month of this activity.
5) One day I decide it's time to put a gui frontend to my jdbc stuff. Guess what? I try to run the gui web application and Java Studio Creator fails to start the Web application server.
It was all because of my setting rlim_fd_max=4096 a month ago when I installed postgres (step #3 above)
Thank you for the work around. I can now continue my development on the Sun platform using Sun tools. 
Yep..... Default file descriptor limit in S10 is above 4096 and 8192. So, you really dont need to set it to 4096 while setting up the OS for postgres.
In any case, issue will be gone for ever once people start using fixed versions of JDK.

Glassfish Lifecycle module debugging

I'm trying to write a message driven bean that listens on an oracle aq queue. To do that I'm trying to follow create a lifecycle module that binds the Oracle JMS AQ to glassfish jndi. This is using Glassfish V2.
I am having trouble debugging a lifecycle module that I deployed per these instructions:
https://oracleaq.dev.java.net/servlets/ProjectForumMessageView?messageID=23962&forumID=3117
I created the lifecycle module and dropped the created lifecyclemodule jar file into glassfish/domains/domain1/lib directory. I set the is-failure-fatal flag to "true" to verify that the lifecycle module starts up correctly.
When I restart the app server I get the following error message:
[#|2008-09-03T11:27:04.578-0700|WARNING|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=2064cd49-cc9d-430e-9267-107bc51916b5;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: LCM0103: Treating failure loading the lifecycle module [AqJmsListener] as fatal; please check your classpath and the is-failure-fatal property.
at com.sun.appserv.server.ServerLifecycleModule.postEvent(ServerLifecycleModule.java:209)
at com.sun.appserv.server.ServerLifecycleModule.onTermination(ServerLifecycleModule.java:277)
at com.sun.appserv.server.LifecycleModuleService.onTermination(LifecycleModuleService.java:496)
at com.sun.enterprise.server.ApplicationServer.onTermination(ApplicationServer.java:587)
at com.sun.enterprise.server.PEMain.run(PEMain.java:434)
at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
|#]
[#|2008-09-03T11:27:04.594-0700|SEVERE|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=2064cd49-cc9d-430e-9267-107bc51916b5;|Server stopped due to Server startup failure.|#]
Unfortunately it gives no indication as to what the problem is. Is there any way to debug my lifecycle module? I added log statements in the handleEvent method of the implemented LifecycleListener class but I'm not seeing them in the server.log.
BTW, my lifecycle xml stub looks like:
<lifecycle-module class-name="com.oracle.oems.glassfish.AqJmsListener" enabled="true" is-failure-fatal="true" load-order="101" name="AqJmsListener" object-type="user">
<description>JNDI loader for Oracle AQ</description>
</lifecycle-module>
So does anybody see anything obvious that I'm doing wrong? or what would be the way to debug a lifecycle module? The error message really doesn't tell me what is wrong.

Why I Can't Deploy the BMP EJB Sample Provided to IAS6SP4?

When I tried to deploy the sample at j2eeguide/account I Get:
------Register Enterprise Beans: ------
PMY:10 MyAccount
PMY:10 execution of kreg returned non-zero return status, sts = -1
PMY:10 java.lang.NullPointerException
PMY:10      at com.netscape.server.deployment.ComponentGDSUtil.getClassImpGDSKeyByGuid(Unknown Source)
PMY:10      at com.netscape.server.deployment.EjbJARGDSUtil.putEjbToGDS(Unknown Source)
PMY:10      at com.netscape.server.deployment.EjbJARGDSUtil.putAllEjbsToGDS(Unknown Source)
PMY:10      at com.netscape.server.deployment.EjbJARGDSUtil.putEjbJARDescriptorInGDS(Unknown Source)
PMY:10      at com.netscape.server.deployment.EjbReg.registerEjbJar(Unknown Source)
PMY:10      at com.netscape.server.deployment.J2eeAppReg.registerJ2eeApp(Unknown Source)
PMY:10      at com.netscape.server.deployment.J2eeAppReg.run(Unknown Source)
PMY:10      at com.netscape.server.deployment.J2eeAppReg.main(Unknown Source)
PMY:10 j2eeappreg done. 
Hi,
How did you deploy the application or are there any changes made to the working environment or any additional changes for customization to the sample application and then deployed it ?
I just deployed(did not run the application), in both Windows and Solaris with iAS SP4 and it has deployed fine. Here are the results...
WINDOWS
C:\iPlanet\ias6\ias\ias-samples\j2eeguide\account>iasdeploy deployapp j2eeguide-account.ear
iasdeploy for iPlanet Application Server 6.0 SP4
Connected to LDAP server on sundts2 port 389
iPlanet Application Server is running in international mode
sundts2.india.sun.com:null
sundts2.india.sun.com:10 kas> deployment action ''J2EEInstallEar'' (c:/iplanet/ias6/ias/JAR/j2eeguide-account.ear) running.
sundts2.india.sun.com:10 kas> deployment action ''J2EEInstallEar'' (c:/iplanet/ias6/ias/JAR/j2eeguide-account.ear) running.
sundts2.india.sun.com:j2eeappreg -nodeprecated c:/iplanet/ias6/ias/JAR/j2eeguide-account.ear 2>&1
sundts2.india.sun.com:10 Connected to LDAP server on sundts2 port 389
sundts2.india.sun.com:10 iPlanet Application Server is running in internationalmode
sundts2.india.sun.com:10 login page is being set to :
sundts2.india.sun.com:10 Module: j2eeguide-account
sundts2.india.sun.com:10 Module: j2eeguide-accountEjb
sundts2.india.sun.com:10 ------ Register Web Module: j2eeguide-account.war ------
sundts2.india.sun.com:10 ------ Register EJB Module: j2eeguide-accountEjb.jar ------
sundts2.india.sun.com:10 ------Register Enterprise Beans: ------
sundts2.india.sun.com:10 MyAccount
sundts2.india.sun.com:10 j2eeappreg done.
sundts2.india.sun.com:20 kas> deployment action ''J2EEInstallEar'' (c:/iplanet/i
as6/ias/JAR/j2eeguide-account.ear) complete.
sundts2.india.sun.com:
Finished deploying to sundts2.india.sun.com at [20/Mar/2002 22:49:38]
SOLARIS
# iasdeploy deployapp j2eeguide-account.ear
iasdeploy for iPlanet Application Server 6.0 SP4
Connected to LDAP server on jwala.india.sun.com port 389
iPlanet Application Server is running in international mode
jwala:null
jwala:10 kas> deployment action ''J2EEInstallEar'' (/usr/iplanet/ias6/ias/JAR/j2eeguide-account.ear) running.
jwala:10 kas> deployment action ''J2EEInstallEar'' (/usr/iplanet/ias6/ias/JAR/j2eeguide-account.ear) running.
jwala:j2eeappreg -nodeprecated /usr/iplanet/ias6/ias/JAR/j2eeguide-account.ear 2>&1
jwala:10 Connected to LDAP server on jwala.india.sun.com port 389
jwala:10 iPlanet Application Server is running in international mode
jwala:10 login page is being set to :
jwala:10 Module: j2eeguide-account
jwala:10 Module: j2eeguide-accountEjb
jwala:10 ------ Register Web Module: j2eeguide-account.war ------
jwala:10 [17/Mar/2002 09:21:20:6] info: GDS-007: finished a registry load
jwala:10 [17/Mar/2002 09:21:22:7] info: GDS-007: finished a registry load
jwala:10 [17/Mar/2002 09:21:23:4] info: GDS-007: finished a registry load
jwala:10 [17/Mar/2002 09:21:25:9] info: GDS-007: finished a registry load
jwala:10 [17/Mar/2002 09:21:26:0] info: GDS-007: finished a registry load
jwala:10 ------ Register EJB Module: j2eeguide-accountEjb.jar ------
jwala:10 ------Register Enterprise Beans: ------
jwala:10 MyAccount
jwala:10 [17/Mar/2002 09:21:47:4] info: GDS-007: finished a registry load
jwala:10 [17/Mar/2002 09:21:49:3] info: GDS-007: finished a registry load
jwala:10 [17/Mar/2002 09:21:49:9] info: GDS-007: finished a registry load
jwala:10 j2eeappreg done.
jwala:20 kas> deployment action ''J2EEInstallEar'' (/usr/iplanet/ias6/ias/JAR/j2eeguide-account.ear) complete.
jwala:
Finished deploying to jwala at [17/Mar/2002 9:22:05]
Also I verified this with the iASAT tool and found that the application is deployed. Please let me know if you have repacked the application, the OS name and version. Also please ensure that the LDAP server is up and running fine. Any other information is highly appreciated.
Thanks & Regards
Ganesh .R
Developer Technical Support
Sun Microsystems
http://www.sun.com/developers/support

JMS Exception when using JCA1.5 and non-JMS MDBs

Hello all,
I've written an JCA 1.5 compatible Resource Adapter (RA). This adapter listenes for incomming messages on the network (SIP) and wraps generates events of those which should be processed by Message Driven Beans.
The message Driven Beans don't process JMS Messages, but implement my own listener type and custom events. (As per JCA 1.5 specification can be done)
I've implemented a demo-application (one MDB) and the RA and packaged them into an ear. The implemented Resource Adapter and demo application can be succesfully deployed on JBoss and the application functions as expected.
I've now tried to deploy the same application on the Sun Application Server PE 8 but get exceptions on deployment. When I verify the J2EE compliance of the ear with the provided deploytool, I get no warnings and no failed tests.
If I deploy the application the deploytool says the operation has succeeded completely and does mention any problems whatsoever.
However, the Message Driven Bean is not succesfully deployed and started. (the RA does get started just fine) When I look into the server.log file I can see the following messages:
[#|2006-01-18T11:35:14.672+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core.naming|_ThreadID=12;|NAM0006: JMS Destination object not found: eis/SIPRA|#]
[#|2006-01-18T11:35:14.672+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core.naming|_ThreadID=12;|javax.naming.NameNotFoundException
javax.naming.NameNotFoundException
|#]
[#|2006-01-18T11:35:14.687+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=12;|Instantiated container for: ejbName: SIP_Proxy; containerId: 74552476408283136|#]
[#|2006-01-18T11:35:14.906+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=12;|JMS Service Connection URL is :mq://twain:7676/,|#]
[#|2006-01-18T11:35:14.952+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb.mdb|_ThreadID=12;|MDB00017: [SIP_Proxy]: Exception in creating message-driven bean container: [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : ejb/SIP_Proxy]|#]
[#|2006-01-18T11:35:14.952+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb.mdb|_ThreadID=12;|com.sun.enterprise.connectors.ConnectorRuntimeException
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : ejb/SIP_Proxy
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:560)
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:444)
     at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:139)
     at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:187)
     at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:221)
     at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:477)
     at com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:125)
<cut (no more useful part of) stacktrace here>
[#|2006-01-18T11:35:14.952+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=12;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : ejb/SIP_Proxy]|#]
[#|2006-01-18T11:35:14.952+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=12;|appId=ProxyApplication moduleName=proxyBean_jar ejbName=SIP_Proxy|#]
[#|2006-01-18T11:35:14.952+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core.classloading|_ThreadID=12;|LDR5004: UnExpected error occured while creating ejb container
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : ejb/SIP_Proxy
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:560)
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:444)
     at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:139)
     at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:187)
     at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:221)
<cut (no more useful part of) stacktrace here>
[#|2006-01-18T11:35:14.984+0100|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=12;|CORE5021: Application NOT loaded: [ProxyApplication]|#]As you can see from the stacktraces, it is assumed (for some reason) that the JCA and the listening MDB are using JMS, as no JMS queues or topics are configured it complains and breaks out.
Any advice what could be the cause of this problem?
I'm not using JMS in my application at all, de deploymentool says everything is deployed succesfully, although it is not, and it does work on JBoss.
Kind regards,
Bruno 
Hi Bruno
As you can see from the stacktraces, it is assumed
(for some reason) that the JCA and the listening MDB
are using JMS, as no JMS queues or topics are
configured it complains and breaks out.Yes, you are right that the application server tries to find a related JMS resource and fails. Have you specified your custom RA as the resource adapter that delivers messages to the MDB via the resource-adapter-mid element in sun-ejb-jar.xml? If this is not specified, the application server assumes that it is a JMS MDB and tries to search for a JMS resource
More details available off http://docs.sun.com/source/819-0079/dgconn.html#wp28370
Thanks
--Siva                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        
Hello Siva,
Yes, you are right that the application server tries
to find a related JMS resource and fails. Have you
specified your custom RA as the resource adapter that
delivers messages to the MDB via the
resource-adapter-mid element in sun-ejb-jar.xml? IfAha, this (partially) solves the problem indeed. I do not get the exceptions about the the JMS-stuff anymore
However, I did not succeed in actually deploying and using the RA yet.
If I deploy it throug the deploytool (ear-file with both the RA and MDB) I get an exception that the RA is not deployed:
[#|2006-01-19T12:33:51.311+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core.naming|_ThreadID=12;|javax.naming.NameNotFoundException
javax.naming.NameNotFoundException: SIPRA not found
|#]
[#|2006-01-19T12:33:51.311+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=12;|Instantiated container for: ejbName: SIP_Proxy; containerId: 74558369195360256|#]
[#|2006-01-19T12:33:51.389+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb.mdb|_ThreadID=12;|MDB00017: [SIP_Proxy]: Exception in creating message-driven bean container: [com.sun.enterprise.connectors.ConnectorRuntimeException: Resource adapter SIPRA is not deployed]|#]
[#|2006-01-19T12:33:51.389+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb.mdb|_ThreadID=12;|com.sun.enterprise.connectors.ConnectorRuntimeException
com.sun.enterprise.connectors.ConnectorRuntimeException: Resource adapter SIPRA is not deployed
     at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:134)
     at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:187)
     at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:221)
     at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:477)I assume this still has something to do with names specified wrong in some xml-file. Could you give me a pointer about that too?
If I try to deploy the RA and MDB-jar seperately using the web-interface I do get a little further.
I can deploy the RA without any problems.
Next when I try to deploy the MDB the deploying doesn't end!
I get the following:
[#|2006-01-19T12:41:39.786+0100|INFO|sun-appserver-pe8.1_02|ResourceAdapterImpl|_ThreadID=16;|[RA.endpointActivation()] Entered|#]
[#|2006-01-19T12:42:39.657+0100|WARNING|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=16;|RAR7004 : MDB deployment is still happening. Cannot create end point now.|#]
[#|2006-01-19T12:42:39.657+0100|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.stream.err|_ThreadID=16;|javax.resource.spi.UnavailableException: EndpointFactory is currently not available
     at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.createEndpoint(ConnectorMessageBeanClient.java:328)
     at be.ugent.ibcn.sipconnector.ra.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:69)
     at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:221)
     at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:187)
     at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:221)
     at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:477)So it arrives until the EndpointActivation in the RA-implementation, but for some reason, actually creating the endpoint doesn't work?
One other question I have is, how can I specify the jndi-name of the connectionfactory of the RA?
Kind regards, and thanks for your help so far.
Bruno

Error in Application Log (apex: Servlet error)

Hi Guys,
I am using APEX listener 1.1 EA with OC4J 10.1.3.5.0, APEX 4.0.1 and Oracle DB 10.2.0.4
I have the following error in the application log file:
=================================
10/11/09 07:59:20.312 apex: Servlet error
oracle.dbtools.rt.service.ServiceLocatorException: Exception occurred in activate() method
at oracle.dbtools.rt.service.Provider.activate(Provider.java:55)
at oracle.dbtools.rt.service.Provider.match(Provider.java:109)
at oracle.dbtools.rt.service.Providers.match(Providers.java:22)
at oracle.dbtools.rt.service.ServiceLocator.acquireAll(ServiceLocator.java:97)
at oracle.dbtools.rt.service.ServiceLocator.acquire(ServiceLocator.java:74)
at oracle.dbtools.rt.service.Provider.inject(Provider.java:135)
at oracle.dbtools.rt.service.Provider.activate(Provider.java:38)
at oracle.dbtools.rt.service.Provider.match(Provider.java:109)
at oracle.dbtools.rt.service.Providers.match(Providers.java:22)
at oracle.dbtools.rt.service.ServiceLocator.acquireAll(ServiceLocator.java:97)
at oracle.dbtools.rt.service.ServiceLocator.acquire(ServiceLocator.java:74)
at oracle.dbtools.rt.service.Provider.inject(Provider.java:135)
at oracle.dbtools.rt.service.Provider.activate(Provider.java:38)
at oracle.dbtools.rt.service.Provider.match(Provider.java:109)
at oracle.dbtools.rt.service.Providers.match(Providers.java:22)
at oracle.dbtools.rt.service.ServiceLocator.acquireAll(ServiceLocator.java:97)
at oracle.dbtools.rt.service.ServiceLocator.acquireAll(ServiceLocator.java:104)
at oracle.dbtools.rt.web.RequestDispatchers.choose(RequestDispatchers.java:85)
at oracle.dbtools.rt.web.RequestDispatchers.dispatch(RequestDispatchers.java:52)
at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:77)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher
.java:734)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher
.java:391)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler
.java:908)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler
.java:458)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler
.java:226)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:127)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:116)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.5.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor
.java:303)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.sleepycat.je.EnvironmentLockedException: (JE 4.0.103) C:\WINDOWS\Temp\apex\bdb The environment cannot be locked for
single writer access. ENV_LOCKED: The je.lck file could not be locked. Environment is invalid and must be closed.
at com.sleepycat.je.log.FileManager.<init>(FileManager.java:350)
at com.sleepycat.je.dbi.EnvironmentImpl.<init>(EnvironmentImpl.java:439)
at com.sleepycat.je.dbi.EnvironmentImpl.<init>(EnvironmentImpl.java:341)
at com.sleepycat.je.dbi.DbEnvPool.getEnvironment(DbEnvPool.java:181)
at com.sleepycat.je.Environment.makeEnvironmentImpl(Environment.java:229)
at com.sleepycat.je.Environment.<init>(Environment.java:211)
at com.sleepycat.je.Environment.<init>(Environment.java:165)
at oracle.dbtools.rt.home.DataStore.activate(DataStore.java:49)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.dbtools.rt.service.__Reflections.invoke(__Reflections.java:85)
at oracle.dbtools.rt.service.Provider.activate(Provider.java:42)
... 30 more
Edited by: salim_faisal on Nov 9, 2010 9:26 AM 
Hi,
my first guess would be, that the user you are running the OC4J with has no rights to perform the desired write operation in your configured temp, as the cause says
Caused by: com.sleepycat.je.EnvironmentLockedException: (JE 4.0.103) C:\WINDOWS\Temp\apex\bdb The environment cannot be locked for
single writer access. ENV_LOCKED: The je.lck file could not be locked. Environment is invalid and must be closed. Which OS do you currently use?
This may also happen if more than one instance of the Listener is running, or, since you are using the EA-version instead of the current production release, you may have some IDE running parallel that prevents the lock operation.
If none of my previous suggestions apply, could you try to run the production version of the Listener to see if that will run on your system?
-Udo 
Hi Udo,
Thank you for the fast reply.
I am currently having Windows 2003R2
Yes there is a another listener on the same machine running on GlassFish but on totally a different port.
Could that be an issue?
Initially I had only the listener with GlassFish but I started to get weird error where users could not login and authentication function keeps rejecting them with invalid credential message.
The authentication function is using DBMS_LDAP against active directory. It will work for few hours and suddenly it will stop until I restart the apex listener application from GlassFish and it will work for sometime(hours or so) and then stops again.
Then I thought I should switch to another application server. So I installed OC4J and configured the listener to work on a different port.
The issue is happening again. But this time the application will authenticate for longer times (5 hours or so) and then stops authenticating.
The authentication function that I am using was already working perfectly on another machine but with 11g.
I hope I gave a good summary of my issue wishing to hear your thought about it. 
Hi Salim,
the APEX Listener always uses ${java.io.tmpdir} for temp, which is set to the same default if you use the same JVM for your Glassfish. Probably you'll get the current issue solved by reconfiguring that directory.
To do that, you can add a command line option to your OC4J-standalone start script, e.g.
java -Djava.io.tmpdir=<othertmpdir> -jar oc4j.jarSee the OC4J-documentation on setting system properties:
http://download.oracle.com/docs/cd/B25221_05/web.1013/b14432/sysprops.htm#CHDEJCHD
I'm not sure if the error you get with LDAP will actually disappear just by changing the plattform for the Listener, as DBMS_LDAP is a database package and the calls issued by the Listener are executed by the same database user. If it's running at all, the problem could be located somewhere else. Do you see any stack traces in the Listener's application log? Or any other error in the APEX-Log you can view using the Listeners status page?
Perhaps it's a problem with connection pooling and caching. Have you enabled caching for the Listener?
-Udo 
Thank you Udo for all the help you provided.
I figured out the issue with the DBMS_LDAP and the authentication
I was using S_BIND function and returning a true or false for the authentication function and I forger to use UNBIND before the return happens.
I ended up with 63 LDAP connections open and no more connections were allowed.
The confusing part that the same code was working in 11g but when implemented on 10g it stopped working.
It seems that 11g has an internal ldap connection management while 10g has 63 maximum connections by default.
Good night..

Categories

Resources