App Server 9 - virtual server listener

Problem - getting 'Already bound: 80' if virtual server using 2 IP's
Yes, I know the answer to the question is...
There MUST be something else bound to port 80 - but there ISN'T.
Pretty 'basic' stuff. But, after 2 days work, I am
unable to configure with 2 different IP's - I know it
'should work' - but curious if anyone can confirm it DOES work?
fresh install OS & Application Server
Sparc Solars 11/06, Sun V210
Java Aplication Platform SDK-5 Update 3
DNS: (x's are valid IP address)
x.x.x.34 -> web30.domainabc.com - machine primary IP bge0
x.x.x.35 -> www.domaindef.com - 2nd IP bge0:1
======== WORKS ==== (listens to all IP's)
listeners...
admin-listener true 0.0.0.0 8444 __asadmin
http-listener-2 true 0.0.0.0 443 server
http-listener-1 true 0.0.0.0 80 server
virtual servers...
server http-listener-1,http-listener-2
__asaadmin admin-listener
domaindef http-listener-1
======== DOES NOT WORK ====
listeners...
admin-listener true x.x.x.34 8444 __asadmin
http-listener-2 true 0.0.0.0 443 server
http-listener-1 true x.x.x.34 80 server
http-domaindef true x.x.x.35 80 domaindef
virtual servers...
server http-listener-1,http-listener-2
__asaadmin admin-listener
domaindef http-domaindef
netstat -a ONLY shows domainabc.com using port 80
NOTHING else is using port 80
Server will not restart - server log shows:
grizzlyHttpProtocol.endpoint.initerror
java.net.BindException: Already bound: 80
WHILE in Admin, if 'Enable' listener http-domaindef
it WORKS - but netstat shows the server 'clobbered' the x.x.x.34:80
and is only running the x.x.x.35:80 listener instead
[#|2007-04-16T17:09:44.261-0400|SEVERE|sun-appserver9.1|org.apache.catalina.core.StandardService|_ThreadID=22;_ThreadName=httpWorkerThread-8444-1;_RequestID=ea8003f3-d4df-40bd-a403-558f4f6928a2;|Connector.initialize
LifecycleException: PWC3985: Protocol handler initialization failed: java.net.BindException: Already bound: 80
at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.java:1592)

You are mixing version.
EJB 2.0 is part of J2EE 1.3.
EJB 2.1 is part of J2EE 1.4.
Oracle Application Server 9.0.4 supports J2EE 1.3
There is also a preview of the J2EE 1.4 version.
Both can be found here:
http://www.oracle.com/technology/tech/java/oc4j/index.html

Similar Messages

How to make the App Server Listen for HTTPS

I have a web application that needs to be accesible over an HTTPS connection, not HTTP.
When I deploy an application with Java Studio Creator to the App Server it is automatically set to an HTTP URL. How do I setup HTTPS ?
Thank you in advance,
Joe Paladin

Looks like I should have thanked myself in advance....
Turns out its pretty easy. Open the admin console, go to configuration, add and HTTP listener, check the security check box, and fill out the other mandatory fields like the port. Standard SSL port is 443.
Save changes, and restart the App Server. Any deployed apps should be reachable via https://localhost:443/myWebApp
This approach uses a default certificate that comes with the app server. Here is a link if you want to create a certificate :
http://java.sun.com/developer/technicalArticles/WebServices/appserv8-1.html
Joe Paladin

J2EE App Server with virtual servers

H! !
I have a Win2K with J2EE App Server 1.4. Everything is working fine. In this computer I stopped the IIS 5.0 in order to use the HTTP Server included with the product.
I also run the DNS on the same machine with 3 domains. All name resolutions for these 3 domains work fine.
Now I want to enter to any of the 3 domains freelyand execute JSP apps. But I don't want to enter ports numbers like this:
http://www.mytest.com:8081/hello.jsp
I just want to enter:
http://www.mytest.com/hello.jsp
So I defined a new http-port listener pointing to the 80 port on this server. With no SSL support.
Name: http-port80
IP Address: 0.0.0.0
POrt: : 80
Return server name: <blank> (Should I put here the name of the computer?)
Then I defined a new virtual server using the http-port listener. I set the following fields:
ID: mytest
Hosts: www.mytest.com (Should I put here the name of the computer?)
HTTP Listener: http-port80 (This is the name of the port listener)
Everything seems to be fine. I can enter http://www.mytest.com and call the hello.jsp it's ok.
But then I create a new virtual server for http://www.mytest2.com exactly as the one for the www.mytest.com, except for the host field: http://www.mytest2.com
Then when I restart the app server I got the message on the log: "Port already in use".
I want to use the same http-listener because I don't want to enter http://www.mytest2.com:<port>
Any ideas how to handle this?
Am I doing something wrong on the configuration?
Thank you very much!!

What I want is to enter to any of the 3 domains freely and execute JSP apps. But I don't want to enter ports numbers like this:
http://www.mytest.com:8081/hello.jsp
I just want to enter:
http://www.mytest.com/hello.jsp
As far as I understand only by having an http-listener linked to the virtual web server I can achieve this goal, right? Or Am I on the wrong direction?

Listening port in oracle app. server 10gR2 in window 2003

Hi Experts,
How to find a listening port number of app. server?
Thanks,
Jim

Check on the midtier home, the %ORACLE_HOME%\Apcahe\Apache\conf\httpd.conf file for port directive. Or if you have SSL-configured on the AS, the check ssl.conf file in the same location for the same directive.
or Alternatively, log on to the EM for midtier. Go to ports and see the Webcache port for listen.
Remember that these will be the listen ports for Webcache. For port where OHS will listen can be obtained by looking for Listen directive in the above files, and on EM, the port listed for OHS Listen (or SSL Listen, in case of SSL).
Edited by: AMN on Dec 2, 2008 10:42 AM

Virtual Directory / path mapping in Sun ONE App Server 7

Hi,
I am trying to migrate my application from WebLogic 7
to Sun ONE App Server 7.0
In WebLogic, we used the following mapping in weblogic.xml:
<virtual-directory-mapping>
<local-path>f:/ekm</local-path>
<url-pattern>/data/*</url-pattern>
</virtual-directory-mapping>
What would be the equivalent in sun-web.xml in Sun ONE?
Thanks
Amrit

This is not deployment instructions.
Its deployment descriptor like web.xml
You can find more info here:
http://docs-pdf.sun.com/816-7150-10/816-7150-10.pdf
on page 91

Error in starting app server

The following error shown up in the command prompt while starting the "Default Server":
Starting Domain domain1, please wait.
Log redirected to C:\Sun\Creator\SunAppServer8\domains\domain1\logs\server.log.
Domain domain1 failed to startup. Please check the server log for more details.
CLI156 Could not start the domain domain1.
Press any key to continue . . .
When I looked at the log files (as mentioned above), the following errors have shown up in the log file. Following are the log entries that were generated while the server is being started (rather failed):
************** FROM HERE **********
Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) ...
[#|2004-06-03T15:32:31.480+0530|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_03] from [Sun Microsystems Inc.]|#]
[#|2004-06-03T15:32:32.371+0530|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-06-03T15:32:32.575+0530|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-06-03T15:32:34.747+0530|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-06-03T15:32:34.763+0530|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-06-03T15:32:34.763+0530|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-06-03T15:32:35.873+0530|SEVERE|sun-appserver-pe8.0|javax.enterprise.resource.corba|_ThreadID=10;|IOP5006: Exception creating socket: [SSL_MUTUALAUTH, 1061]. Please make sure the port is not being used.|#]
[#|2004-06-03T15:32:35.873+0530|SEVERE|sun-appserver-pe8.0|javax.enterprise.resource.corba|_ThreadID=10;|
java.net.BindException: Address already in use: JVM_Bind
     at java.net.PlainSocketImpl.socketBind(Native Method)
     at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
     at java.net.ServerSocket.bind(ServerSocket.java:318)
     at java.net.ServerSocket.<init>(ServerSocket.java:185)
     at java.net.ServerSocket.<init>(ServerSocket.java:141)
     at javax.net.ssl.SSLServerSocket.<init>(DashoA6275)
     at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.<init>(DashoA6275)
     at com.sun.net.ssl.internal.ssl.SSLServerSocketFactoryImpl.createServerSocket(DashoA6275)
     at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSSLServerSocket(IIOPSSLSocketFactory.java:312)
     at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createServerSocket(IIOPSSLSocketFactory.java:270)
     at com.sun.corba.ee.impl.legacy.connection.SocketFactoryAcceptorImpl.initialize(SocketFactoryAcceptorImpl.java:53)
     at com.sun.corba.ee.impl.transport.CorbaTransportManagerImpl.getAcceptors(CorbaTransportManagerImpl.java:190)
     at com.sun.corba.ee.impl.transport.CorbaTransportManagerImpl.addToIORTemplate(CorbaTransportManagerImpl.java:207)
     at com.sun.corba.ee.spi.oa.ObjectAdapterBase.initializeTemplate(ObjectAdapterBase.java:104)
     at com.sun.corba.ee.impl.oa.poa.POAImpl.initialize(POAImpl.java:385)
     at com.sun.corba.ee.impl.oa.poa.POAImpl.makeRootPOA(POAImpl.java:253)
     at com.sun.corba.ee.impl.oa.poa.POAFactory$1.evaluate(POAFactory.java:163)
     at com.sun.corba.ee.impl.orbutil.closure.Future.evaluate(Future.java:28)
     at com.sun.corba.ee.impl.resolver.LocalResolverImpl.resolve(LocalResolverImpl.java:22)
     at com.sun.corba.ee.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:20)
     at com.sun.corba.ee.impl.orb.ORBImpl.resolve_initial_references(ORBImpl.java:1112)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:185)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:600)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:232)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:210)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-06-03T15:32:35.873+0530|WARNING|sun-appserver-pe8.0|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710209: (INTERNAL) Unable to create listener thread on the specific port"
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 209 completed: No
     at com.sun.corba.ee.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:3142)
     at com.sun.corba.ee.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:3160)
     at com.sun.corba.ee.impl.legacy.connection.SocketFactoryAcceptorImpl.initialize(SocketFactoryAcceptorImpl.java:60)
     at com.sun.corba.ee.impl.transport.CorbaTransportManagerImpl.getAcceptors(CorbaTransportManagerImpl.java:190)
     at com.sun.corba.ee.impl.transport.CorbaTransportManagerImpl.addToIORTemplate(CorbaTransportManagerImpl.java:207)
     at com.sun.corba.ee.spi.oa.ObjectAdapterBase.initializeTemplate(ObjectAdapterBase.java:104)
     at com.sun.corba.ee.impl.oa.poa.POAImpl.initialize(POAImpl.java:385)
     at com.sun.corba.ee.impl.oa.poa.POAImpl.makeRootPOA(POAImpl.java:253)
     at com.sun.corba.ee.impl.oa.poa.POAFactory$1.evaluate(POAFactory.java:163)
     at com.sun.corba.ee.impl.orbutil.closure.Future.evaluate(Future.java:28)
     at com.sun.corba.ee.impl.resolver.LocalResolverImpl.resolve(LocalResolverImpl.java:22)
     at com.sun.corba.ee.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:20)
     at com.sun.corba.ee.impl.orb.ORBImpl.resolve_initial_references(ORBImpl.java:1112)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:185)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:600)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:232)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:210)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.RuntimeException: Failed to create server socket when calling ORBSocketFactory.createServerSocket(SSL_MUTUALAUTH, 1061)
     at com.sun.corba.ee.impl.legacy.connection.SocketFactoryAcceptorImpl.initialize(SocketFactoryAcceptorImpl.java:57)
     ... 20 more
Caused by: java.net.BindException: Address already in use: JVM_Bind
     at java.net.PlainSocketImpl.socketBind(Native Method)
     at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
     at java.net.ServerSocket.bind(ServerSocket.java:318)
     at java.net.ServerSocket.<init>(ServerSocket.java:185)
     at java.net.ServerSocket.<init>(ServerSocket.java:141)
     at javax.net.ssl.SSLServerSocket.<init>(DashoA6275)
     at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.<init>(DashoA6275)
     at com.sun.net.ssl.internal.ssl.SSLServerSocketFactoryImpl.createServerSocket(DashoA6275)
     at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSSLServerSocket(IIOPSSLSocketFactory.java:312)
     at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createServerSocket(IIOPSSLSocketFactory.java:270)
     at com.sun.corba.ee.impl.legacy.connection.SocketFactoryAcceptorImpl.initialize(SocketFactoryAcceptorImpl.java:53)
     ... 20 more
|#]
[#|2004-06-03T15:32:35.888+0530|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5081: Exception while creating ORB: [org.omg.CORBA.INTERNAL:   vmcid: SUN minor code: 209 completed: No]|#]
[#|2004-06-03T15:32:35.888+0530|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5082: Exception running j2ee services: [java.lang.RuntimeException: Unable to create ORB]|#]
[#|2004-06-03T15:32:35.888+0530|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5091: Error executing J2EE server ...
java.lang.RuntimeException: Unable to create ORB
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:316)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:600)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:232)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:210)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.RuntimeException: Unable to create ORB
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
     ... 9 more
|#]
[#|2004-06-03T15:32:35.888+0530|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5092: J2EE server reported following error: [Unable to create ORB] |#]
[#|2004-06-03T15:32:35.888+0530|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5093: Error executing J2EE server |#]
[#|2004-06-03T15:32:35.888+0530|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: com.sun.appserv.server.ServerLifecycleException: Unable to create ORB
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:234)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:210)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.appserv.server.ServerLifecycleException: Unable to create ORB
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:609)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:232)
     ... 7 more
Caused by: java.lang.RuntimeException: Unable to create ORB
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:316)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:600)
     ... 8 more
Caused by: java.lang.RuntimeException: Unable to create ORB
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
     ... 9 more
|#]
[#|2004-06-03T15:32:35.888+0530|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2004-06-03T15:32:35.888+0530|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2004-06-03T15:32:35.888+0530|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Tomcat.|#]
[#|2004-06-03T15:32:35.888+0530|WARNING|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:536)
     at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:65)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:233)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: LifecycleException: WEB0103: This web container has not yet been started
     at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:529)
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:528)
     ... 9 more
|#]
[#|2004-06-03T15:32:35.888+0530|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2004-06-03T15:32:35.888+0530|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2004-06-03T15:32:36.107+0530|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\Creator\SunAppServer8\imq\bin].|#]
[#|2004-06-03T15:32:36.139+0530|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|core.tmp_folder_deletion_failed|#]
[#|2004-06-03T15:32:36.154+0530|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
[#|2004-06-03T15:32:37.280+0530|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
[#|2004-06-03T15:32:37.280+0530|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
*********** UPTO HERE **********
Previously I am able to start the server and was able to test an application. But, this time somehow it failed to start.
I have checked the port numbers whether they are in use. But, all the port numbers required for the app server are free. I have checked it through "netstat -a".
thanks in advance,
-Ranjan

See if this helps:
http://forum.java.sun.com/thread.jsp?forum=136&thread=458833
-Alexis

App Server not starting

Hi,
I have recently installed Studio Creator.
While I try to start the Application Server, it doesn't.
Any help is appreciated.
Thanks in advance.

The other App server is not running at the time this Creator's app server is started. However, the other app server is configured at 4848. And I think, if the other app server is not running, there should not be any problem even if there are common ports.
Here's the server log:
============================
Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) ...
[#|2004-04-12T12:40:46.730-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_03] from [Sun Microsystems Inc.]|#]
[#|2004-04-12T12:40:48.603-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-04-12T12:40:49.033-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-04-12T12:40:52.108-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-04-12T12:40:52.138-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-04-12T12:40:52.148-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-04-12T12:40:59.498-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-04-12T12:41:01.351-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-04-12T12:41:02.002-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-04-12T12:41:03.164-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-04-12T12:41:03.204-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\Creator\SunAppServer8\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2004-04-12T12:41:03.214-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\Creator\SunAppServer8\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-04-12T12:41:03.214-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\Creator\SunAppServer8\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2004-04-12T12:41:04.826-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2004-04-12T12:41:04.866-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2004-04-12T12:41:04.906-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Compiling RMI-IIOP code ...|#]
[#|2004-04-12T12:41:19.287-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2004-04-12T12:41:19.297-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.stream.out|_ThreadID=10;| role is admin-role class class java.lang.String|#]
[#|2004-04-12T12:41:19.377-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.stream.out|_ThreadID=10;|
role is admin-role class class java.lang.String|#]
[#|2004-04-12T12:41:20.048-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 16434 msec, Total EJB Compiler Module Time: 14461 msec, Portion spent EJB Compiling: 87%
Breakdown of EJBC Module Time: Total Time for EJBC: 14461 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 14371 msec (99%), JAX-RPC Generation: 10 msec (0%),
|#]
[#|2004-04-12T12:41:20.058-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
[#|2004-04-12T12:41:20.188-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2004-04-12T12:41:20.819-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-04-12T12:41:20.829-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-04-12T12:41:20.849-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\Creator\SunAppServer8\lib\install\applications\MEjbApp.ear.|#]
[#|2004-04-12T12:41:20.849-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\Creator\SunAppServer8\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-04-12T12:41:21.500-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-04-12T12:41:26.237-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2004-04-12T12:41:26.237-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2004-04-12T12:41:26.387-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5468 msec, Total EJB Compiler Module Time: 4737 msec, Portion spent EJB Compiling: 86%
Breakdown of EJBC Module Time: Total Time for EJBC: 4737 msec, CMP Generation: 1091 msec (23%), Java Compilation: 3225 msec (68%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2004-04-12T12:41:26.397-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
[#|2004-04-12T12:41:26.417-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2004-04-12T12:41:27.008-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-04-12T12:41:27.008-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-04-12T12:41:27.008-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-04-12T12:41:27.018-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\Creator\SunAppServer8\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-04-12T12:41:27.028-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-04-12T12:41:27.238-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-04-12T12:41:27.489-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-04-12T12:41:27.499-0500|WARNING|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-04-12T12:41:27.609-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-04-12T12:41:27.629-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-04-12T12:41:27.629-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-04-12T12:41:27.759-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-04-12T12:41:33.447-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-04-12T12:41:36.311-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8081|#]
[#|2004-04-12T12:41:36.351-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8081|#]
[#|2004-04-12T12:41:36.542-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1044|#]
[#|2004-04-12T12:41:36.552-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1044|#]
[#|2004-04-12T12:41:36.602-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4849|#]
[#|2004-04-12T12:41:36.612-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4849|#]
[#|2004-04-12T12:41:36.892-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\Creator\SunAppServer8\imq\bin].|#]
[#|2004-04-12T12:41:36.902-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1081791696902|#]
[#|2004-04-12T12:41:36.902-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-04-12T12:41:36.902-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-04-12T12:42:22.958-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Selecting file [ C:\Sun\Creator\SunAppServer8\domains\domain1\autodeploy\hello-jaxrpc.war ] for autodeployment.|#]
[#|2004-04-12T12:42:25.182-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [hello-jaxrpc]|#]
[#|2004-04-12T12:42:25.182-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=11;|Processing beans ...|#]
[#|2004-04-12T12:42:25.212-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [hello-jaxrpc]|#]
[#|2004-04-12T12:42:25.813-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 2714 msec, Total EJB Compiler Module Time: 30 msec, Portion spent EJB Compiling: 1%
Breakdown of EJBC Module Time: Total Time for EJBC: 30 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 10 msec (33%),
|#]
[#|2004-04-12T12:42:25.813-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=11;|deployed with moduleid = hello-jaxrpc|#]
[#|2004-04-12T12:42:25.933-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/hello-jaxrpc]|#]
[#|2004-04-12T12:42:26.233-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [hello-jaxrpc] in virtual server [server] at [hello-jaxrpc]|#]
[#|2004-04-12T12:42:29.268-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=11;|JAXRPC.JAXRPCSERVLET.12: JAX-RPC context listener initializing|#]
[#|2004-04-12T12:42:30.289-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=11;|JAXRPC.JAXRPCSERVLET.14: JAX-RPC servlet initializing|#]
[#|2004-04-12T12:42:30.429-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-04-12T12:42:30.459-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Successfully autodeployed : C:\Sun\Creator\SunAppServer8\domains\domain1\autodeploy\hello-jaxrpc.war.|#]
[#|2004-04-12T12:42:32.472-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Selecting file [ C:\Sun\Creator\SunAppServer8\domains\domain1\autodeploy\jTravellerService.war ] for autodeployment.|#]
[#|2004-04-12T12:42:33.724-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [jTravellerService]|#]
[#|2004-04-12T12:42:33.724-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=11;|Processing beans ...|#]
[#|2004-04-12T12:42:33.724-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [jTravellerService]|#]
[#|2004-04-12T12:42:33.814-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 1282 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%
Breakdown of EJBC Module Time: Total Time for EJBC: 0 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2004-04-12T12:42:33.814-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=11;|deployed with moduleid = jTravellerService|#]
[#|2004-04-12T12:42:33.834-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/jTravellerService]|#]
[#|2004-04-12T12:42:33.944-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [jTravellerService] in virtual server [server] at [jTravellerService]|#]
[#|2004-04-12T12:42:35.346-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=11;|JAXRPC.JAXRPCSERVLET.12: JAX-RPC context listener initializing|#]
[#|2004-04-12T12:42:35.406-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=11;|JAXRPC.JAXRPCSERVLET.14: JAX-RPC servlet initializing|#]
[#|2004-04-12T12:42:35.456-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-04-12T12:42:35.466-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Successfully autodeployed : C:\Sun\Creator\SunAppServer8\domains\domain1\autodeploy\jTravellerService.war.|#]
Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) ...
[#|2004-05-05T21:59:45.928-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_03] from [Sun Microsystems Inc.]|#]
[#|2004-05-05T21:59:49.112-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-05-05T21:59:49.914-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-05-05T21:59:57.194-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-05-05T21:59:57.304-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-05-05T21:59:57.324-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-05-05T22:00:05.917-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-05-05T22:00:09.161-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-05-05T22:00:09.452-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-05-05T22:00:10.593-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-05-05T22:00:12.025-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-05-05T22:00:13.568-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-05-05T22:00:13.568-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-05-05T22:00:13.818-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-05-05T22:00:15.040-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-05-05T22:00:15.390-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-05-05T22:00:15.390-0500|WARNING|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-05-05T22:00:15.400-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-05-05T22:00:15.420-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello-jaxrpc] in virtual server [server] at [hello-jaxrpc]|#]
[#|2004-05-05T22:00:15.450-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [jTravellerService] in virtual server [server] at [jTravellerService]|#]
[#|2004-05-05T22:00:15.470-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-05-05T22:00:15.470-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-05-05T22:00:15.661-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-05-05T22:00:23.802-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.12: JAX-RPC context listener initializing|#]
[#|2004-05-05T22:00:25.014-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.14: JAX-RPC servlet initializing|#]
[#|2004-05-05T22:00:25.114-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-05-05T22:00:27.387-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.12: JAX-RPC context listener initializing|#]
[#|2004-05-05T22:00:27.728-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.14: JAX-RPC servlet initializing|#]
[#|2004-05-05T22:00:28.940-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8081|#]
[#|2004-05-05T22:00:29.020-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8081|#]
[#|2004-05-05T22:00:29.170-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1044|#]
[#|2004-05-05T22:00:29.170-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1044|#]
[#|2004-05-05T22:00:29.240-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-05T22:00:29.240-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-05T22:00:29.631-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\Creator\SunAppServer8\imq\bin].|#]
[#|2004-05-05T22:00:29.651-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1083812429651|#]
[#|2004-05-05T22:00:29.651-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-05-05T22:00:29.651-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) ...
[#|2004-05-05T22:46:53.494-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_03] from [Sun Microsystems Inc.]|#]
[#|2004-05-05T22:46:54.766-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-05-05T22:46:55.156-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-05-05T22:46:58.871-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-05-05T22:46:58.891-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-05-05T22:46:58.901-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-05-05T22:47:01.806-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-05-05T22:47:03.538-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-05-05T22:47:03.799-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-05-05T22:47:04.880-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-05-05T22:47:05.731-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-05-05T22:47:06.462-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-05-05T22:47:06.462-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-05-05T22:47:06.522-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-05-05T22:47:06.863-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-05-05T22:47:07.063-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-05-05T22:47:07.063-0500|WARNING|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-05-05T22:47:07.073-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-05-05T22:47:07.083-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello-jaxrpc] in virtual server [server] at [hello-jaxrpc]|#]
[#|2004-05-05T22:47:07.103-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [jTravellerService] in virtual server [server] at [jTravellerService]|#]
[#|2004-05-05T22:47:07.123-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-05-05T22:47:07.123-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-05-05T22:47:07.263-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-05-05T22:47:12.952-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.12: JAX-RPC context listener initializing|#]
[#|2004-05-05T22:47:13.242-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.14: JAX-RPC servlet initializing|#]
[#|2004-05-05T22:47:13.332-0500|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-05-05T22:47:16.196-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.12: JAX-RPC context listener initializing|#]
[#|2004-05-05T22:47:16.246-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.14: JAX-RPC servlet initializing|#]
[#|2004-05-05T22:47:17.428-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8081|#]
[#|2004-05-05T22:47:17.508-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8081|#]
[#|2004-05-05T22:47:17.648-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1044|#]
[#|2004-05-05T22:47:17.658-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1044|#]
[#|2004-05-05T22:47:17.719-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-05T22:47:17.739-0500|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-05T22:47:18.029-0500|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\Creator\SunAppServer8\imq\bin].|#]
[#|2004-05-05T22:47:18.039-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1083815238039|#]
[#|2004-05-05T22:47:18.049-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-05-05T22:47:18.049-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) ...
[#|2004-05-07T09:13:50.977-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_03] from [Sun Microsystems Inc.]|#]
[#|2004-05-07T09:13:55.233-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-05-07T09:13:56.064-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-05-07T09:14:03.705-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-05-07T09:14:03.765-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-05-07T09:14:03.775-0500|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-05-07T09:14:13.079-0500|INFO|sun-appserver-pe8.0|java

App Server Fails to Start after Installation

Hi,
I've spent a whole day struggling with this, looking through forum discussions and trying out every single suggestion I've come across in the forums. I'm running out of ideas now and really appreciate any help I can get with this problem.
I'm trying to install SJSC2 (also tried with SJSC2u1 with the same outcome) on a new HP notebook (nw9440) running WinXP_sp2. I'm using the default installation done by HP.
My installation path is C:\Java\SunCreator2 (C:\Java\SunCreator2_1 for update 1).
After the installation the App server fails to start up and gives the below error in the server.log.
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d779c9d, pid=5368, tid=5760
# Java VM: Java HotSpot(TM) Client VM (1.5.0_06-b05 mixed mode)
# Problematic frame:
# V [jvm.dll+0x99c9d]
# An error report file with more information is saved as hs_err_pid5368.log
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
Upon looking at the install.log in the rave_home directory, I noticed the below sequence of errors.
Timeout waiting for domain creator to go to starting state.
Compiler warnings:
line 44: Attribute 'debug-options' outside of element.
line 62: Attribute 'port' outside of element.
line 73: Attribute 'port' outside of element.
line 84: Attribute 'port' outside of element.
line 105: Attribute 'port' outside of element.
line 116: Attribute 'port' outside of element.
line 127: Attribute 'port' outside of element.
line 145: Attribute 'port' outside of element.
line 156: Attribute 'port' outside of element.
CLI156 Could not start the domain creator.
The following script has unexpected output: "C:\Creator2\bin\deploy-ws.bat"
Aug 14, 2006 11:27:33 PM com.sun.appserv.management.client.ProxyFactory getInstance
SEVERE: ProxyFactory.getInstance: Failure trying to create a new ProxyFactory: java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.
CLI171 Command deploy failed : Deployment of application failed - java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.; requested operation cannot be completed
Aug 14, 2006 11:27:35 PM com.sun.appserv.management.client.ProxyFactory getInstance
SEVERE: ProxyFactory.getInstance: Failure trying to create a new ProxyFactory: java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.
CLI171 Command deploy failed : Deployment of application failed - java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.; requested operation cannot be completed
Aug 14, 2006 11:27:37 PM com.sun.appserv.management.client.ProxyFactory getInstance
SEVERE: ProxyFactory.getInstance: Failure trying to create a new ProxyFactory: java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.
CLI171 Command deploy failed : Deployment of application failed - java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.; requested operation cannot be completed
The following script has unexpected output: "C:\Creator2\bin\deploy-ejbs.bat"
Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.
Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.
Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.
Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.
CLI137 Command create-jdbc-connection-pool failed.
CLI137 Command create-jdbc-resource failed.
CLI137 Command create-jdbc-connection-pool failed.
CLI137 Command create-jdbc-resource failed.
Aug 14, 2006 11:27:52 PM com.sun.appserv.management.client.ProxyFactory getInstance
SEVERE: ProxyFactory.getInstance: Failure trying to create a new ProxyFactory: java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.
CLI171 Command deploy failed : Deployment of application failed - java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.; requested operation cannot be completed
Aug 14, 2006 11:27:53 PM com.sun.appserv.management.client.ProxyFactory getInstance
SEVERE: ProxyFactory.getInstance: Failure trying to create a new ProxyFactory: java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.
CLI171 Command deploy failed : Deployment of application failed - java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.; requested operation cannot be completed
Aug 14, 2006 11:27:55 PM com.sun.appserv.management.client.ProxyFactory getInstance
SEVERE: ProxyFactory.getInstance: Failure trying to create a new ProxyFactory: java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.
CLI171 Command deploy failed : Deployment of application failed - java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.; requested operation cannot be completed
Aug 14, 2006 11:27:57 PM com.sun.appserv.management.client.ProxyFactory getInstance
SEVERE: ProxyFactory.getInstance: Failure trying to create a new ProxyFactory: java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.
CLI171 Command deploy failed : Deployment of application failed - java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct.; requested operation cannot be completed
I've tried every workaround I've seen in the forums such as installing under different paths (both with spaces and without spaces), cleaning all the temporary files in the Temp directory, renaming the productregistry in the windows system directory. Each time I get the exact same error in the install.log.
I also tried installing the stand alone SUN App Server 8.1_02_2005Q2 as well as 8.2. I don't seem to have any issue with this installation or running of the stand alone server at all on the same machine.
Really appreciate any help I can get. TIA....
rgds,
KC

Hi,
After spending more time looking through the forum, I came across the below thread which has worked in my case (though it was suggested for Sol10x86).
http://forum.sun.com/jive/thread.jspa?threadID=62404&messageID=243113
This is the workaround that worked in my case.
> $ cd <Creator_Home>/SunAppServer8/lib
$ mv processLauncher.xml processLauncher.xml.trayIcon
$ cp processLauncher.xml.bak processLauncher.xml
# If you have a domains/creator/config/domain.xml
$ cd ../bin
$ ./asadmin start-domain creator
This started the app server. After that I was able to start and stop app server within the JSC as well.
Only difference between these two xml files seem to be,
processLauncher.xml.trayicon
<main_class classname="com.sun.rave.tray.RavePEMain"/>
processLauncher.xml
<main_class classname="com.sun.enterprise.server.PEMain"/>
Possibly pointing to a bug in the "com.sun.rave.tray.RavePEMain" class.
Thanks for your suggestions guys... and especially to Marco and Greg.
Rgds,
Kc
Message was edited by:
Kc

Problem with Java System Application Server *(Sun one 8 or J2EE 1.4 app server)

Hi,
Iam able to deploy KODO JDO through JCA in Sun One App server 7,
But iam unable to deploy in J2EE1.4 app server. I followed the J2EE1.4
guide developer guide it is compitable with JCA1.5 and also given backward
compatibility for JCA1.0
I had removed the sun-ra.xml from kodo.rar which is not needed in
J2EE1.4 and deployed but iam un able to get the
PersistanceManagerConnectionFactory.
Can any one heip in sloving this issues the exceptions Iam getting
Starting J2EE(TM) Application Server 1.4 Developer Release (build b44-dr)
[#|2004-03-06T18:07:16.801+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076:
Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun
Microsystems Inc.]|#]
[#|2004-03-06T18:07:20.356+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following
is the information about the JMX MBeanServer used:|#]
[#|2004-03-06T18:07:20.757+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer
initialized successfully|#]
[#|2004-03-06T18:07:23.761+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
Engine server|#]
[#|2004-03-06T18:07:25.223+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
virtual server server|#]
[#|2004-03-06T18:07:25.283+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS
AVK Instrumentation disabled|#]
[#|2004-03-06T18:07:25.353+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143:
Loading policy provider
com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-03-06T18:07:32.904+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014:
Recoverable JTS instance, serverId = [100]|#]
[#|2004-03-06T18:07:37.701+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying
Optional Packages dependencies...|#]
[#|2004-03-06T18:07:38.392+0530|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008
: Initialized monitoring registry and listeners|#]
[#|2004-03-06T18:07:41.016+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading
system apps|#]
[#|2004-03-06T18:07:43.239+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB
Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6005
: Could not create mcf : kodo.jdbc.ee.JDBCManagedConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6021
:Failed to create MCF : JDOKODO#javax.resource.cci.ConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
     at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
     at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
     at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
     at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
     at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
     at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
     at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
     at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5059:
Error in loading resource|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
     at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
     at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
     at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
     at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
     at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
     at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
     at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
     at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
With Regards,
M.S.Veerendra

M.S. Veerendra-
This is a known incompatibility, described at:
http://support.solarmetric.com/Ticket/Display.html?id=14082
Can you try the workarounds listed at:
http://forum.java.sun.com/thread.jsp?forum=136&thread=499803&tstart=0&trange=15
and let us know if it works?
In article <[email protected]>, veerendra wrote:
Hi,
Iam able to deploy KODO JDO through JCA in Sun One App server 7,
But iam unable to deploy in J2EE1.4 app server. I followed the J2EE1.4
guide developer guide it is compitable with JCA1.5 and also given backward
compatibility for JCA1.0
I had removed the sun-ra.xml from kodo.rar which is not needed in
J2EE1.4 and deployed but iam un able to get the
PersistanceManagerConnectionFactory.
Can any one heip in sloving this issues the exceptions Iam getting
Starting J2EE(TM) Application Server 1.4 Developer Release (build b44-dr)
[#|2004-03-06T18:07:16.801+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076:
Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun
Microsystems Inc.]|#]
[#|2004-03-06T18:07:20.356+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following
is the information about the JMX MBeanServer used:|#]
[#|2004-03-06T18:07:20.757+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer
initialized successfully|#]
[#|2004-03-06T18:07:23.761+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
Engine server|#]
[#|2004-03-06T18:07:25.223+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
virtual server server|#]
[#|2004-03-06T18:07:25.283+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS
AVK Instrumentation disabled|#]
[#|2004-03-06T18:07:25.353+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143:
Loading policy provider
com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-03-06T18:07:32.904+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014:
Recoverable JTS instance, serverId = [100]|#]
[#|2004-03-06T18:07:37.701+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying
Optional Packages dependencies...|#]
[#|2004-03-06T18:07:38.392+0530|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008
: Initialized monitoring registry and listeners|#]
[#|2004-03-06T18:07:41.016+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading
system apps|#]
[#|2004-03-06T18:07:43.239+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB
Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6005
: Could not create mcf : kodo.jdbc.ee.JDBCManagedConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6021
:Failed to create MCF : JDOKODO#javax.resource.cci.ConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
     at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
     at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
     at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
     at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
     at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
     at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
     at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
     at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5059:
Error in loading resource|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
     at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
     at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
     at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
     at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
     at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
     at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
     at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
     at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
With Regards,
M.S.Veerendra--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

JDK1.5.0_12 crash when I try to startup a tomcat app server with it.

Hi,
I am support a Blackboard application running on a PrimePower box.
Recently I installed JDK1.5.0_12 on the box. When I re-configured Blackboard to use the new JDK and tried to restart the server, the tomcat portion will keep getting the JVM Hotspot crash error as illustrated below.
The startup is invoked from a shell script that starts the web server as well as the tomcat (app) server. As long as the root partition has enough diskspace, the script will try to "start" the tomcat server.
The JVM will keep throwing core dumps and issuing messages like the following, with each core dump taking about 100 to 150MB in space from the root partition.
Only when there isn't enough space in the root partition for another core dump, did I notice that it stopped.
My sys admin has since cleaned up the dump files and I have reverted back to the earlier minor release of JDK1.5.0.
I have used ldd -r libjvm.so and the command could return me the list of libraries that the libjvm.so depends on (not a problem with the loading of the dynamic libraries and such).
I have submitted the JVM crash report. But no one has gotten back to me.
Has anyone encountered the same problems / have any suggestions on what could be cause and how to resolved this?
Thanks.
Regards,
Hon Peng.
=============================
# An unexpected error has been detected by HotSpot Virtual Machine:
# SIGSEGV (0xb) at pc=0xfea84b00, pid=13715, tid=1
# Java VM: Java HotSpot(TM) Server VM (1.5.0_12-b04 mixed mode)
# Problematic frame:
# V [libjvm.so+0x284b00]
--------------- T H R E A D ---------------
Current thread (0x00036e20): JavaThread "main" [_thread_in_vm, id=1]
siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x57726974
Registers:
O0=0x00000000 O1=0x00000000 O2=0x0000015c O3=0x00000000
O4=0x0000015c O5=0x0000015c O6=0xffbfe6f8 O7=0x0000015c
G1=0x00000000 G2=0x0000015c G3=0x0000015c G4=0x00000000
G5=0x00000000 G6=0x00000000 G7=0xff350000 Y=0x00000000
PC=0xfea84b00 nPC=0xfea84b04
Top of Stack: (sp=0xffbfe6f8)
0xffbfe6f8: 000373fc 57726974 000adfb0 ff028d48
0xffbfe708: 00032778 fefdc000 001b3990 b4805210
0xffbfe718: ffbfe84c 00000000 00000000 ff010c40
0xffbfe728: 00009c00 80000000 ffbfe7e8 fea84674
0xffbfe738: 00000000 e3908660 ffbfe7c0 f900587c
0xffbfe748: b4a64018 007f9a80 ffbfe7b4 b4a5e2c5
0xffbfe758: ffbfe7b8 ffbfe8e0 f9015b04 00000000
0xffbfe768: 00000000 f900576c b4a64018 007f9a80
Instructions: (pc=0xfea84b00)
0xfea84af0: 80 a5 a0 00 04 40 00 15 b4 10 20 00 e2 04 a0 08
0xfea84b00: d4 04 60 00 d2 04 60 04 8b 2a b0 20 88 12 40 05
Stack: [0xffb80000,0xffc00000), sp=0xffbfe6f8, free space=505k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x284b00]
V [libjvm.so+0x28467c]
j java.lang.Object.notify()V+0
j blackboard.util.Queue.put(Ljava/lang/Object;)V+19
j blackboard.platform.log.impl.QueuedLogger.doLogMessage(Ljava/lang/String;)V+77
j blackboard.platform.log.impl.BaseLogger.log(Ljava/lang/String;Lblackboard/platform/log/LogService$Verbosity;)V+10
j blackboard.platform.log.impl.BaseLogger.logInfo(Ljava/lang/String;)V+5
j blackboard.platform.log.impl.BbLogServiceImpl.logInfo(Ljava/lang/String;)V+5
j blackboard.platform.BbServiceManager.init(Ljava/io/File;Ljava/util/Properties;Z)V+249
j blackboard.platform.BbServiceManager.init(Ljava/lang/String;Ljava/util/Properties;Z)V+44
j blackboard.platform.ApplicationLauncher.main([Ljava/lang/String;)V+479
v ~StubRoutines::call_stub
V [libjvm.so+0x19b4dc]
V [libjvm.so+0x2dd2cc]
C [java+0x222c] main+0x1164
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j java.lang.Object.notify()V+0
j blackboard.util.Queue.put(Ljava/lang/Object;)V+19
j blackboard.platform.log.impl.QueuedLogger.doLogMessage(Ljava/lang/String;)V+77
j blackboard.platform.log.impl.BaseLogger.log(Ljava/lang/String;Lblackboard/platform/log/LogService$Verbosity;)V+10
j blackboard.platform.log.impl.BaseLogger.logInfo(Ljava/lang/String;)V+5
j blackboard.platform.log.impl.BbLogServiceImpl.logInfo(Ljava/lang/String;)V+5
j blackboard.platform.BbServiceManager.init(Ljava/io/File;Ljava/util/Properties;Z)V+249
j blackboard.platform.BbServiceManager.init(Ljava/lang/String;Ljava/util/Properties;Z)V+44
j blackboard.platform.ApplicationLauncher.main([Ljava/lang/String;)V+479
v ~StubRoutines::call_stub
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x0037fbe8 JavaThread "FileLogSinkImpl Daemon" [_thread_blocked, id=15]
0x0015ddc0 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=13]
0x0015c4e8 JavaThread "CompilerThread1" daemon [_thread_blocked, id=12]
0x0015b670 JavaThread "CompilerThread0" daemon [_thread_blocked, id=11]
0x0015a7f8 JavaThread "AdapterThread" daemon [_thread_blocked, id=10]
0x001599e8 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=9]
0x0014d768 JavaThread "Finalizer" daemon [_thread_blocked, id=8]
0x0014d228 JavaThread "Reference Handler" daemon [_thread_blocked, id=7]
=>0x00036e20 JavaThread "main" [_thread_in_vm, id=1]
Other Threads:
0x0014ab40 VMThread [id=6]
0x000aff90 WatcherThread [id=14]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x00032778/0x00035dd0] SignatureHandlerLibrary_lock - owner thread: 0x00036e20
Heap
PSYoungGen total 39424K, used 5458K [0xe3400000, 0xe6000000, 0xf8c00000)
eden space 33792K, 16% used [0xe3400000,0xe3954b40,0xe5500000)
from space 5632K, 0% used [0xe5a80000,0xe5a80000,0xe6000000)
to space 5632K, 0% used [0xe5500000,0xe5500000,0xe5a80000)
PSOldGen total 90112K, used 0K [0xb8800000, 0xbe000000, 0xe3400000)
object space 90112K, 0% used [0xb8800000,0xb8800000,0xbe000000)
PSPermGen total 16384K, used 4896K [0xb4800000, 0xb5800000, 0xb8800000)
object space 16384K, 29% used [0xb4800000,0xb4cc83e8,0xb5800000)
Dynamic libraries:
0x00010000      /usr/local/jdk1.5.0_12/bin/java
0xff370000      /usr/lib/libthread.so.1
0xff3fa000      /usr/lib/libdl.so.1
0xff280000      /usr/lib/libc.so.1
0xff3a0000      /usr/platform/FJSV,GPUS/lib/libc_psr.so.1
0xfe800000      /usr/local/jdk1.5.0_12/jre/lib/sparc/server/libjvm.so
0xff240000      /usr/lib/libsocket.so.1
0xff220000      /usr/lib/libsched.so.1
0xff1f0000      /usr/lib/libCrun.so.1
0xff1a0000      /usr/lib/libm.so.1
0xff080000      /usr/lib/libnsl.so.1
0xff170000      /usr/lib/libmp.so.2
0xfe7e0000      /usr/local/jdk1.5.0_12/jre/lib/sparc/native_threads/libhpi.so
0xfe7b0000      /usr/local/jdk1.5.0_12/jre/lib/sparc/libverify.so
0xfe770000      /usr/local/jdk1.5.0_12/jre/lib/sparc/libjava.so
0xfe740000      /usr/local/jdk1.5.0_12/jre/lib/sparc/libzip.so
0xf8cd0000      /usr/local/jdk1.5.0_12/jre/lib/sparc/libj2pkcs11.so
0xb3580000      /usr/lib/libpkcs11.so
0xf8c50000      /usr/lib/libasn1.so
0xb3400000      /usr/lib/libcmicmn.so
0xb47a0000      /opt/FJSVsmee/lib/libinfoca.so
0xf8f90000      /opt/FJSVsmee/lib/libinfocacom.so
0xf8c30000      /opt/FJSVsmee/lib/libsctl15d.so
VM Arguments:
java_command: blackboard.platform.ApplicationLauncher -S ../config/update-tool-vm/install-tool-vm-servicedef.properties -A blackboard.apis.updatetools.CommandLineToolInvokerApp blackboard.apis.updatetools.tooldefs.install.ServiceControllerTool services.stop
Launcher Type: SUN_STANDARD
Environment Variables:
JAVA_HOME=/usr/local/jdk1.5.0_12
CLASSPATH=
PATH=/usr/local/blackboard/apps/openssl/bin:/usr/local/blackboard/apps/bbcms/bin:/usr/local/jdk1.5.0_12/bin:/usr/bin:/usr/ucb:/etc:/usr/local/bin:.
LD_LIBRARY_PATH=/usr/local/jdk1.5.0_12/jre/lib/sparc/server:/usr/local/jdk1.5.0_12/jre/lib/sparc:/usr/local/jdk1.5.0_12/jre/../lib/sparc
SHELL=/bin/ksh
HOSTTYPE=sparc
OSTYPE=solaris2.9
MACHTYPE=sparc-sun-solaris2.9
Signal Handlers:
SIGSEGV: [libjvm.so+0x70cb50], sa_mask[0]=0x7fbffeff, sa_flags=0x00000004
SIGBUS: [libjvm.so+0x70cb50], sa_mask[0]=0x7fbffeff, sa_flags=0x00000004
SIGFPE: [libjvm.so+0x2743ac], sa_mask[0]=0x7fbffeff, sa_flags=0x0000000c
SIGPIPE: [libjvm.so+0x2743ac], sa_mask[0]=0x7fbffeff, sa_flags=0x0000000c
SIGILL: [libjvm.so+0x2743ac], sa_mask[0]=0x7fbffeff, sa_flags=0x0000000c
SIGUSR1: [libjvm.so+0x67f5f0], sa_mask[0]=0x00000000, sa_flags=0x00000008
SIGUSR2: [libjvm.so+0x2743ac], sa_mask[0]=0x7fbffeff, sa_flags=0x0000000c
SIGHUP: [libjvm.so+0x67e22c], sa_mask[0]=0x7fbffeff, sa_flags=0x00000004
SIGINT: [libjvm.so+0x67e22c], sa_mask[0]=0x7fbffeff, sa_flags=0x00000004
SIGQUIT: [libjvm.so+0x67e22c], sa_mask[0]=0x7fbffeff, sa_flags=0x00000004
SIGTERM: [libjvm.so+0x67e22c], sa_mask[0]=0x7fbffeff, sa_flags=0x00000004
--------------- S Y S T E M ---------------
OS: Solaris 9 4/04 s9s_u6wos_08a SPARC
Copyright 2004 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 22 March 2004
uname:SunOS 5.9 Generic_118558-33 sun4us (T2 libthread)
rlimit: STACK 8192k, CORE infinity, NOFILE 5120, AS infinity
load average:0.05 0.12 0.16
CPU:total 4 has_v8, has_v9, has_vis1, has_vis2, is_ultra3
Memory: 8k page, physical 8388608k(6679936k free)
vm_info: Java HotSpot(TM) Server VM (1.5.0_12-b04) for solaris-sparc, built on May 2 2007 02:33:21 by unknown with unknown Workshop:0x550

Hi,
Thanks for the reply. I have tried this on another machine running the same version of Blackboard. It works fine.
Only difference is that the machine that has the JVM crash is running on Fujitsu PrimePower and the OS is Solaris 9 (but twigged for PrimePower).
The one where it runs and starts up successfully is running on SunFire (OS is Solaris 10).
I am wondering if there is a problem with the JVM loading required libraries because of the OS being different versions.
Any leads on this is welcomed. Thank you.
Regards,
Hon Peng
===================
On Fujitsu Primepower
SunOS 5.9 Generic_118558-33 sun4us sparc FJSV,GPUS
the Dependencies for libjvm.so are as follows:
===================
bash-2.05$ ldd -r libjvm.so
libsocket.so.1 => /usr/lib/libsocket.so.1
libsched.so.1 => /usr/lib/libsched.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libCrun.so.1 => /usr/lib/libCrun.so.1
libm.so.1 => /usr/lib/libm.so.1
libthread.so.1 => /usr/lib/libthread.so.1
libc.so.1 => /usr/lib/libc.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libmp.so.2 => /usr/lib/libmp.so.2
/usr/platform/FJSV,GPUS/lib/libc_psr.so.1
=====================================
On SunFire, Sun machine
SunOS 5.10 Generic_118833-36 sun4u sparc SUNW,Sun-Fire-280R
the dependencies are different for the libjvm.so:
=====================================
bash-2.05$ ldd -r libjvm.so
libsocket.so.1 => /lib/libsocket.so.1
libsched.so.1 => /usr/lib/libsched.so.1
libdl.so.1 => /lib/libdl.so.1
libCrun.so.1 => /usr/lib/libCrun.so.1
libm.so.1 => /lib/libm.so.1
libthread.so.1 => /lib/libthread.so.1
libc.so.1 => /lib/libc.so.1
libnsl.so.1 => /lib/libnsl.so.1
libmp.so.2 => /lib/libmp.so.2
libmd5.so.1 => /lib/libmd5.so.1
libscf.so.1 => /lib/libscf.so.1
libdoor.so.1 => /lib/libdoor.so.1
libuutil.so.1 => /lib/libuutil.so.1
/platform/SUNW,Sun-Fire-280R/lib/libc_psr.so.1
libm.so.2 => /lib/libm.so.2
/platform/SUNW,Sun-Fire-280R/lib/libmd5_psr.so.1

Crystal Report Viewer Not viwed - Through APP Server Re-Direction

Hello Team
I have a critical problem in my organizaion for viewing the reports.
Configuration that we are using:
1. Windows Server 2008 R2
2. Crystal 13 - Server Trial Version - Expiring on Aug-25th, 2014
3. Used Visual Studio 2010 - .NET
4. IIS 7.0 - configured a Virtual Directory for ASP.NET application
Out Application is using an Oracle APP Server to view the HTML. A button is provided in the HTML to redirect to view the Crystal Report.
when I click on the Hyperlink and the url is directly accessed, then the Report is being shown without any issue.
But ours is a corporate application and we have given a provision of accessign this application when users are outside of network. Hence the Crystal Server is under fire-wall. So, I cannot access it directly with a URL. Hence the app server is configured in such a way that if it find a name like "Reports" in the URL, then it redirects to the actual Web Server and gets back the data to the browser.
for URL redirection, the app server is configured as below
    ProxyPass /crystalreportviewers/ http://<<ServerIP>>/crystalreportviewers/
    ProxyPassReverse /crystalreportviewers/ http://<<ServerIP>>/crystalreportviewers
    ProxyPass /reports10/ http://<<ServerIP>>/reports10/
    ProxyPassReverse /reports10/ http://<<ServerIP>>/reports10
When the user redirects from the APP server using those redirection rules, the pages are being executed but the final crystal report viewer control is not being shown on the browser. I am not sure if we need to perform any other steps to get these thigns done.
Our server is behind fire-wall and whenever I am in network, I used to get the output but when the redirection happens not able to load the Crystal Report Viewer. Not sure, if there are any other security rules that I need to consider to get back the CrystalReportViewer.
Also, there is something called CrystalReportInteractiveViewer prior to Crystal13. Do we have anything as such in Crystal 13 also? Please help me in getting this worked.
Please let me know if I am not clear in my explanation and I can certainly provide you a better information based on your queries.
Thanks
-Srinivasa Nadella

Hi Srinivasa,
Please move this thread to SAP Crystal Reports, version for Visual Studio
Helpful threads: Having issues with Crystal reports report viewer
c# - Application level assembly redirection not working - Stack Overflow
asp.net mvc - Why is my Crystal Report and Viewer invisible on a Web Form in an MVC application? - Stack Overflow
Regards,
DJ

How to dynamically discover runtime properties of app server within webapp

Hi friends,
Does anyone know if the Servlet API provide any methods to dynamically discover app server runtime properties such as which http and https ports the server is listening at?
It's not the same as ServletRequest.getServerPort() which only give you back the port the incoming request comes from.
I want to be able to say redirect user requests to https, WITHOUT in advance knowledge of the https port configured for the app server, which means no hardcoding of the port number.
Thanks very much for help.

You could always add a web resource collection to your web.xml and specify the transport guarantee to be integral.

Deployement problem in Oracle App Serv with hibernate + JPA and Spring

Dear All,
     I am facing a problem in deployment of a web application in oracle application server 10g. but the same is working fine with Tomcat. The following Exception. Is being thrown.
     Failed to deploy web application "OraTest". Failed to deploy web application OraTest". . Nested exception Resolution:
Base Exception:
java.rmi.RemoteException
deploy failed!: ; nested exception is:
oracle.oc4j.admin.internal.DeployerException: Unknown assembly root-tag attribute: version. deploy failed!: ; nested exception is:
oracle.oc4j.admin.internal.DeployerException: Unknown assembly root-tag attribute: version     I am using the following technologies
1.     Spring 2.0.7
2.     Struts 2.0.9
3.     Hibernate 3.3
4.     JPA 1.0
5.     Oracle App Server 10.1.2.0.2
Web.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
     <display-name>My Application</display-name>
     <filter>
          <filter-name>struts2</filter-name>
          <filter-class>
               org.apache.struts2.dispatcher.FilterDispatcher
          </filter-class>
     </filter>
     <filter-mapping>
          <filter-name>struts2</filter-name>
          <url-pattern>/*</url-pattern>
     </filter-mapping>
     <welcome-file-list>
          <welcome-file>/index.jsp</welcome-file>
     </welcome-file-list>
     <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>
     <listener>
          <listener-class>
               org.springframework.web.context.ContextLoaderListener
          </listener-class>
     </listener>
     <context-param>
          <param-name>contextConfigLocation</param-name>
          <param-value>
               /WEB-INF/conf/spring/datasource-context.xml,
               /WEB-INF/conf/spring/aop-context.xml
          </param-value>
     </context-param>
</web-app>
/Datasource-context.xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:aop="http://www.springframework.org/schema/aop"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xsi:schemaLocation="
    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd
    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.0.xsd">
     <bean class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor" lazy-init="true"/>
     
        <bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource" lazy-init="true">
          <property name="driverClassName">
               <value>oracle.jdbc.driver.OracleDriver</value>
          </property>
          <property name="url">
               <value>jdbc:oracle:thin:@//xxx.xxx.xxx.xxx/mydb</value>
          </property>
          <property name="username">
               <value>admin</value>
          </property>
          <property name="password">
               <value>admin</value>
          </property>
     </bean>
     
     
     <bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean" lazy-init="true">
          <property name="persistenceUnitName" value="mkclsetsPersistenceUnit"/>
          <property name="dataSource" ref="dataSource"/>
          <property name="jpaVendorAdapter">
               <bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter" lazy-init="true">
                    <property name="database" value="ORACLE"/>
                    <property name="showSql" value="true"/>
               </bean>
          </property>
     </bean>
     <bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager" lazy-init="true">
          <property name="entityManagerFactory" ref="entityManagerFactory"></property>
     </bean>
     <tx:annotation-driven transaction-manager="transactionManager"/>
</beans>Aop-context.xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:aop="http://www.springframework.org/schema/aop"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xsi:schemaLocation="
    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd
    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.0.xsd">

     <bean id="methodLoggingAdvice" class="com.mkcl.sets.common.interceptor.MehodLogInterceptor"/>
     
      
     <bean id="methodCachingAdvice"
          class="com.mkcl.sets.common.interceptor.MethodCacheInterceptor">
          <property name="cache">
               <ref local="methodCache" />
          </property>
     </bean>
     <bean id="cacheManager"
          class="org.springframework.cache.ehcache.EhCacheManagerFactoryBean">
          <property name="configLocation">
               <value>WEB-INF/conf/other/ehcache.xml</value>
          </property>
     </bean>
     <bean id="methodCache"
          class="org.springframework.cache.ehcache.EhCacheFactoryBean">
          <property name="cacheManager">
               <ref local="cacheManager" />
          </property>
          <property name="cacheName">
               <value>mkclSetsCache</value>
          </property>
     </bean>
     
     <aop:config>
          <aop:pointcut id="getCountriesPointCut" expression="execution(* com.mkcl.sets.dao.master.impl.LocationDAOImpl.getCountries())"/>
          
          <aop:pointcut id="methodLogPointCutDao" expression="execution(* com.mkcl.sets.dao..*.*(..))"/>
          <aop:pointcut id="methodLogPointCutService" expression="execution(* com.mkcl.sets.service..*.*(..))"/>
          <aop:advisor id="methodCachingAdvisor" advice-ref="methodCachingAdvice" pointcut-ref="getCountriesPointCut"/>
          <aop:advisor id="methodLoggingAdvisorDao" advice-ref="methodLoggingAdvice" pointcut-ref="methodLogPointCutDao"/>
          <aop:advisor id="methodLoggingAdvisorService" advice-ref="methodLoggingAdvice" pointcut-ref="methodLogPointCutService"/>
     </aop:config>
</beans>Persistence.xml
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
    version="1.0">
     <persistence-unit name="mkclsetsPersistenceUnit" transaction-type="RESOURCE_LOCAL">
          
          <provider>org.hibernate.ejb.HibernatePersistence</provider>
          
     </persistence-unit>
</persistence>Do I need to add some other configuration in the existing files or do I need to add some other configuration files ? Please help to deploy my application.
Thanks a lot in advance.
With Best Regards,
Ishaan
null

Did you ever find a solution to this Ishaan?
I imagine you ended up having to upgrade 10gR2 to 10gR3 at least. Correct?

Can't execute web app from NetBeans 3.6 with Sun Java App Server 8

Hi there,
I'm tyring to execute a java web application called myfirstjsp.
In directory ...\myfirstsjp I've got:
- index.jsp
- WEB-INF dir
- META-INF dir.
I can run myfirstjsp from NetBeans if I choose the Netbeans default server, Tomcat 5.0.19 (this web server is configured to port 8084).
However, when I try to execute myfirstjsp from NetBeans with Sun Java System Application Server 8(configured to port 8080), it gives me an annoying message:
The Sun Java System Application Server 8 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
I checked port conflicts but none found.
The other two options don't give me a place to start (I don't know what to do with domain.xml)
I'm working with:
- Windows XP Pro
- J2SE 1.4.2_04 (installed in C:\Program Files\j2sdk1.4.2_04)
- Sun Java Application Server 8 (installed in C:\Program Files\Sun\AppServer)
- Netbeans 3.6 + Sun Java System Application Server Plugin (installed in C:\Program Files\NetBeans3.6).
My PC has the following environment variables:
PATH(in user MGoncalv)=C:\Program Files\Sun\AppServer\bin;,?ut
PATH(system variable)=C:\Program Files\j2sdk1.4.2_04\bin;D:\ProgramFiles\OraReportNT\bin;C:\OraHome92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Personal Communications\;C:\Program Files\IBM\Trace Facility\;%SystemRoot%\system32\nls;%SystemRoot%\system32\nls\ENGLISH
CLASSPATH(system variable)=.;C:\OraHome92\jdbc\lib\ojdbc14.jar
By looking at the Sun App Server log file, I discovered that the log outputs of
- Start Default Server (a link in the folder created by the installation of Sun App Server)
- and trying to execute myfirstjsp from NetBeans through Sun App Server
are very similar.
Below is a piece of server.log when I tried to execute myfirstjsp from NetBeans through Sun App Server. Please, pay attention to the EJBC error:
Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) ...
[#|2004-05-19T17:20:05.198+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2004-05-19T17:20:08.713+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-05-19T17:20:09.384+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-05-19T17:20:14.752+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-05-19T17:20:14.772+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-05-19T17:20:14.792+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-05-19T17:20:20.200+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-05-19T17:20:23.645+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-05-19T17:20:24.336+0100|INFO|sun-appserver-pe8.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-05-19T17:20:26.098+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-05-19T17:20:27.811+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-05-19T17:20:27.921+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-05-19T17:20:27.931+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-05-19T17:20:30.004+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-05-19T17:20:33.459+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Compilation failed: Native compiler returned an error: 2
Error messages are: |#]
[#|2004-05-19T17:20:33.479+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.stream.err|_ThreadID=10;|Compilation failed: Native compiler returned an error: 2
Error messages are:
     at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
     at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
     at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
     at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
     at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
     at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
     at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
     at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
     at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
     at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
     at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
     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:324)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
     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:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
     at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
     at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
     at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.ejb.codegen.JavaCompilerException: Native compiler returned an error: 2
Error messages are:
     at com.sun.ejb.codegen.JavaCompiler.javacCompile(JavaCompiler.java:139)
     at com.sun.ejb.codegen.JavaCompiler.internal_compile(JavaCompiler.java:60)
     at com.sun.ejb.codegen.Compiler.compile(Compiler.java:57)
     at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:293)
     ... 45 more
|#]
[#|2004-05-19T17:20:33.739+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Deployment Error
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
     at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
     at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
     at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
     at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
     at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
     at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
     at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
     at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
     at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
     at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
     at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
     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:324)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
     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:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
     at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
     at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
     at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-05-19T17:20:33.739+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5187 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%|#]
[#|2004-05-19T17:20:33.759+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
     at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
     at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
     at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
     at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
     at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
     at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
     at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
     at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
     at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
     at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
     at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
     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:324)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
     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:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
     at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
     at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
     at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-05-19T17:20:33.789+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|Exception while deploying : Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
.|#]
[#|2004-05-19T17:20:33.799+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-05-19T17:20:33.879+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-05-19T17:20:34.811+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-05-19T17:20:35.111+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-05-19T17:20:35.121+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-05-19T17:20:35.161+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-05-19T17:20:35.181+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-05-19T17:20:35.201+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-05-19T17:20:35.201+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-05-19T17:20:35.412+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-05-19T17:20:37.945+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-05-19T17:20:38.456+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-05-19T17:20:38.556+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-05-19T17:20:38.847+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-05-19T17:20:38.887+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-05-19T17:20:38.987+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-19T17:20:39.007+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-19T17:20:39.558+0100|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Program Files\Sun\AppServer\imq\bin].|#]
[#|2004-05-19T17:20:39.568+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1084983639568|#]
[#|2004-05-19T17:20:39.568+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-05-19T17:20:39.588+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-05-19T17:20:44.475+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[com.sun.enterprise.admin.event.ConfigChangeEvent -- server [1 Change(s), Id:1, ts:1084983644465]]|#]
[#|2004-05-19T17:20:44.545+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1046:A change notification was not handled sucessfully, the server will need a restart for the change to be effective.|#]
Is this EJB compilation error normal ? if not what does it mean ? Sun Java App Server installation isn't OK ?
I tried to look into the Sun App Server Troubleshooting, searched forums... but couldn't squeeze any valuable info from any of them.
If you have any sugestion regarding this problem, or you know some web site that addresses it please tell me !
Many thanks,
Miguel

I seem to have the same problem, I cant run sun application server 8.1. The server is in c:\sun\appserver\, I am using netbeans 4.1. I recieve the same comment above:
The Sun Java System Application Server 8 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
I cant see any port conflict, the server is set to port 4848. I dont know about any configurations.
This is the Exception:
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:45:43.930+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:45:43.940+0300|INFO|sun-appserver-pe8.1_02|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.|#]
[#|2005-11-02T11:45:43.940+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:45:43.950+0300|SEVERE|sun-appserver-pe8.1_02|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: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:45:43.960+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
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)
|#]
[#|2005-11-02T11:47:53.507+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:47:53.517+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:47:57.533+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:47:57.543+0300|INFO|sun-appserver-pe8.1_02|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.|#]
[#|2005-11-02T11:47:57.543+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:47:57.563+0300|SEVERE|sun-appserver-pe8.1_02|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: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:47:57.563+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
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)
|#]
[#|2005-11-02T11:47:58.224+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2005-11-02T11:47:58.224+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|Server shutdown complete.|#]
[#|2005-11-02T11:49:01.705+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:49:01.715+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:49:05.671+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:49:05.671+0300|INFO|sun-appserver-pe8.1_02|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.|#]
[#|2005-11-02T11:49:05.681+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:49:05.691+0300|SEVERE|sun-appserver-pe8.1_02|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: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:49:05.691+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
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)
|#]
[#|2005-11-02T11:49:06.432+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2005-11-02T11:50:38.915+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:50:38.925+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Dcom.sun.aas.jdwpOptions=transport=dt_socket,server=y,suspend=n,address=9009
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/

Peoplesoft HRMS 9.1, Peopletools 8.50 - PS PS fails when firing up app serv

Hi everyone.
I am working on setting up an environment under Oracle Enterprise Linux 5.4 (64 bit) running Oracle 11gR1 (11.0.6), Peopletools 8.50 (64 bit), Tuxedo 10gR3, Weblogic, Peoplesoft HRMS 9.1 (64 bit). Both Peopletools 8.50 and Peoplesoft HRMS 9.1 are relatively new. We are probably one of the first to set this up and we have an issue.
All of the software has been installed and configured. All database sql, datamover, and other scripts have been executed. Also, the database is fully populated.
We encounter an error when going into psadmin and trying to boot the domain HC:
CMDTUX_CAT:1685: ERROR: Application initialization failure
CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
We also receive the following errors:
Do you wish to see the error messages in the APPSRV.LOG file? (y/n) [n] :y
PSADMIN.3612 (0) [10/19/09 15:48:31](0) Begin boot attempt on domain HC
PSAPPSRV.3643 (0) [10/19/09 15:48:42](0) PeopleTools Release 8.50 (Linux) starting. Tuxedo server is APPSRV(99)/1
PSAPPSRV.3643 (0) [10/19/09 15:48:42](0) Cache Directory being used: /home/oracle/psft/pt/8.50/appserv/HC/CACHE/PSAPPSRV_1/
PSAPPSRV.3643 (0) [10/19/09 15:48:43](3) File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 404 - ORA-01017: invalid username/password; logon denied
PSAPPSRV.3643 (0) [10/19/09 15:48:43](1) GenMessageBox(200, 0, M): SQL Access Manager: File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 404 - ORA-01017: invalid username/password; logon denied
PSAPPSRV.3643 (0) [10/19/09 15:48:43](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database HC with user PS.
PSAPPSRV.3643 (0) [10/19/09 15:48:43](0) Server failed to start
PSADMIN.3612 (0) [10/19/09 15:48:49](0) End boot attempt on domain HC
Do you wish to see the error messages in the TUXLOG.101909 file? (y/n) [n] :y
155108.sa2tech47.domain.com!PSADMIN.3722: Begin attempt on domain HC
155112.sa2tech47.domain.com!tmadmin.3743.3663685232.-2: TMADMIN_CAT:1330: INFO: Command: boot -A
155114.sa2tech47.domain.com!tmboot.3744.925238816.-2: 10-19-2009: Tuxedo Version 10.3.0.0, 64-bit
155114.sa2tech47.domain.com!tmboot.3744.925238816.-2: CMDTUX_CAT:1851: INFO: TM_BOOTTIMEOUT is set to 120 seconds
155114.sa2tech47.domain.com!tmboot.3744.925238816.-2: CMDTUX_CAT:1855: INFO: TM_BOOTPRESUMEDFAIL option is selected
155116.sa2tech47.domain.com!BBL.3745.1611062368.0: 10-19-2009: Tuxedo Version 10.3.0.0, 64-bit, Patch Level (none)
155116.sa2tech47.domain.com!BBL.3745.1611062368.0: LIBTUX_CAT:262: INFO: Standard main starting
155118.sa2tech47.domain.com!tmboot.3748.2436493632.-2: 10-19-2009: Tuxedo Version 10.3.0.0, 64-bit
155118.sa2tech47.domain.com!tmboot.3748.2436493632.-2: CMDTUX_CAT:1851: INFO: TM_BOOTTIMEOUT is set to 120 seconds
155118.sa2tech47.domain.com!tmboot.3748.2436493632.-2: CMDTUX_CAT:1855: INFO: TM_BOOTPRESUMEDFAIL option is selected
155118.sa2tech47.domain.com!PSWATCHSRV.3750.3590176352.-2: 10-19-2009: Tuxedo Version 10.3.0.0, 64-bit
155118.sa2tech47.domain.com!PSWATCHSRV.3750.3590176352.-2: LIBTUX_CAT:262: INFO: Standard main starting
155118.sa2tech47.domain.com!PSAPPSRV.3751.286221264.0: 10-19-2009: Tuxedo Version 10.3.0.0, 64-bit
155118.sa2tech47.domain.com!PSAPPSRV.3751.286221264.0: LIBTUX_CAT:262: INFO: Standard main starting
155119.sa2tech47.domain.com!PSAPPSRV.3751.286221264.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
155119.sa2tech47.domain.com!tmboot.3748.2436493632.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
155123.sa2tech47.domain.com!BBL.3745.1611062368.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
155126.sa2tech47.domain.com!PSADMIN.3722: End boot attempt on domain HC
Issue is that when trying to connect and fire up the app server it fails on authentication with PS/PS. I have not changed any of the passwords. I also have searched and even run a fix located at:
http://tech.groups.yahoo.com/group/psftdba/message/577
I have also gone back and checked that:
1. The environment for weblogic is exported.
2. The weblogic daemon wlserver is running.
3. The environment for tuxedo is exported.
4. The tlisten daemon is running.
5. The tlisten listener is configured in /etc/services for port 3050.
6. Tested the sysadm, people accounts to ensure that I can log into the Oracle database. No passwords have been changed. Also checked that all of the tables exist and that they are populated with data.
7. Terminated the daemons and removed the ones that were hung using system resources using ipcrm.
8. Checked the UDDCONFIG file that was created by Peoplesoft to ensure that it was being read.
9. Went back and rechecked the installation and post-installation documentation for Tuxedo 10gR3, Weblogic, Peoplesoft PT 8.50, and Peoplesoft HRMS 9.1.
10. Went back and checked that all binaries and libraries were installed. (I did this prior to the install, but went back and checked again.)
11. Searched the error log files and looked up the codes presented. Checking on possible solutions (this is where I am now).
Anything that anyone can add would be most appreciated. I have log files from the server (of which I am still going through) that I can make available to anyone that is willing to help..
I will share any other findings as they become available and as I make progress.
Thanks in advance!
Walt
[email protected]

"PSAPPSRV.3643 (0) 10/19/09 15:48:43(3) File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 404 - ORA-01017: invalid username/password; logon denied
PSAPPSRV.3643 (0) 10/19/09 15:48:43(1) GenMessageBox(200, 0, M): SQL Access Manager: File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 404 - ORA-01017: invalid username/password; logon denied"
sounds like something to do with connect-id or access-id.
are you able to login to datamover using sysadm user ?
if yes ...can you try to login and run
set log c:\temp\test1.log;
UPDATE PSSTATUS SET OWNERID = 'SYSADM';
UPDATE PSOPRDEFN SET SYMBOLICID = 'SYSADM1', OPERPSWD = 'upg2009', ENCRYPTED = 0 WHERE OPRID = 'VP1';
UPDATE PSACCESSPRFL SET ACCESSID = 'SYSADM', SYMBOLICID = 'SYSADM1', ACCESSPSWD = 'fin23SQL', VERSION = 0, ENCRYPTED = 0;
GRANT SELECT ON PSSTATUS TO people;
GRANT SELECT ON PSOPRDEFN TO people;
GRANT SELECT ON PSACCESSPRFL TO people;
REM - ENCRYPT PASSWORD
SET LOG c:\temp\encrypt.log;
ENCRYPT_PASSWORD *;
Also check PSDBOWNER, it should contain only one row and DB Name should be in caps/lower same case as DB name ...somting it also causes issue.

Issue with lock file in Oracle 10g app server - MDB not running

Hi,
I have Oracle 10g & MQ 6 on my laptop. I generated JNDI bindings for app server-MQ by giving ip address of my machine first. Then i changed it to "localhost" & generated new set of .bindings file.
With this new set i am able to send messages from my program to a queue. I also have an MDB which should listen to the same queue.
However now my mdb is not listening to the queue & i suspect it is due to host address change, - because each time i start the server, i see a lock file created "OracleASRouter_store.lock" - under j2ee\home\persistance. And below is the content of the same -
"O10.1.4.245:/C:/Program Files/Oracle/oc4j_extended_101330/j2ee/home/persistence/"
As per few suggestions on this site, I deleted this file & restated app server, deleted whole content of persistance folder, restarted app server. But each time i see this file created and also see the ip address in log.xml under j2ee\home\log\oc4j
Error message in this log.xml file is
<MESSAGE>
<HEADER>
<TSTZ_ORIGINATING>2007-09-19T11:22:35.265-04:00</TSTZ_ORIGINATING>
<COMPONENT_ID>j2ee</COMPONENT_ID>
<MSG_ID>J2EE EJB-02009</MSG_ID>
<MSG_TYPE TYPE="WARNING"></MSG_TYPE>
<MSG_LEVEL>1</MSG_LEVEL>
<HOST_ID>IFLEXNY-EXT99</HOST_ID>
<HOST_NWADDR>10.1.4.245</HOST_NWADDR>
<MODULE_ID>ejb.runtime</MODULE_ID>
<THREAD_ID>10</THREAD_ID>
<USER_ID>chetanmi</USER_ID>
</HEADER>
<CORRELATION_DATA>
<EXEC_CONTEXT_ID><UNIQUE_ID>10.1.4.245:65858:1190215355296:0</UNIQUE_ID><SEQ>0</SEQ></EXEC_CONTEXT_ID>
</CORRELATION_DATA>
<PAYLOAD>
<MSG_TEXT>[STGMQ:STGMQEJB:TestMDB] Unexpected exception by JMS provider: javax.jms.MessageEOFException: initializeConnection.</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[javax.jms.MessageEOFException: initializeConnection
     at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1075)
     at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1155)
     at com.evermind.server.jms.TCPJMSRemoteServer.initializeConnection(TCPJMSRemoteServer.java:154)
     at com.evermind.server.jms.TCPJMSRemoteServer.initializeConnection(TCPJMSRemoteServer.java:110)
     at com.evermind.server.jms.TCPJMSRemoteServer.<init>(TCPJMSRemoteServer.java:68)
     at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:122)
     at com.evermind.server.jms.EvermindQueueConnection.<init>(EvermindQueueConnection.java:70)
     at com.evermind.server.jms.EvermindQueueConnectionFactory.unprivileged_createQueueConnection(EvermindQueueConnectionFactory.java:101)
     at com.evermind.server.jms.EvermindQueueConnectionFactory.access$000(EvermindQueueConnectionFactory.java:44)
     at com.evermind.server.jms.EvermindQueueConnectionFactory$1.execute(EvermindQueueConnectionFactory.java:81)
     at com.evermind.server.jms.InContainerProxy.doSecureOp(InContainerProxy.java:157)
     at com.evermind.server.jms.EvermindQueueConnectionFactory.createQueueConnection(EvermindQueueConnectionFactory.java:78)
     at com.evermind.server.jms.EvermindQueueConnectionFactory.createQueueConnection(EvermindQueueConnectionFactory.java:69)
     at com.evermind.server.ejb.MessageDrivenConsumer.createNonXAResources(MessageDrivenConsumer.java:567)
     at com.evermind.server.ejb.MessageDrivenConsumer.initializeJMSResources(MessageDrivenConsumer.java:491)
     at com.evermind.server.ejb.MessageDrivenConsumer.processMessages(MessageDrivenConsumer.java:208)
     at com.evermind.server.ejb.MessageDrivenConsumer.run(MessageDrivenConsumer.java:169)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.EOFException
     at java.io.DataInputStream.readInt(DataInputStream.java:358)
     at com.evermind.server.jms.JMSRemoteServer.readCheck(JMSRemoteServer.java:678)
     at com.evermind.server.jms.JMSRemoteServer.readProtocol(JMSRemoteServer.java:696)
     at com.evermind.server.jms.TCPJMSRemoteServer.initializeConnection(TCPJMSRemoteServer.java:134)
     ... 16 more
]]></SUPPL_DETAIL>
</PAYLOAD>
</MESSAGE>
<MESSAGE>
<HEADER>
<TSTZ_ORIGINATING>2007-09-19T11:22:35.312-04:00</TSTZ_ORIGINATING>
<COMPONENT_ID>j2ee</COMPONENT_ID>
<MSG_ID>J2EE EJB-02014</MSG_ID>
<MSG_TYPE TYPE="WARNING"></MSG_TYPE>
<MSG_LEVEL>1</MSG_LEVEL>
<HOST_ID>IFLEXNY-EXT99</HOST_ID>
<HOST_NWADDR>10.1.4.245</HOST_NWADDR>
<MODULE_ID>ejb.runtime</MODULE_ID>
<THREAD_ID>10</THREAD_ID>
<USER_ID>chetanmi</USER_ID>
</HEADER>
<CORRELATION_DATA>
<EXEC_CONTEXT_ID><UNIQUE_ID>10.1.4.245:65858:1190215355296:0</UNIQUE_ID><SEQ>0</SEQ></EXEC_CONTEXT_ID>
</CORRELATION_DATA>
<PAYLOAD>
<MSG_TEXT>[STGMQ:STGMQEJB:TestMDB] All message consumer threads have terminated due to provider errors, stopping MDB.</MSG_TEXT>
</PAYLOAD>
</MESSAGE>
And my MDB is NOT WORKING. Please let me know how to deal with this.
Your suggestions would be much appreciated.
Regard,
Chetan

Line # 127 is creating a new application object using ApplicationFactory.
ApplicationFactory aFactory =
(ApplicationFactory) FactoryFinder.getFactory(
FactoryFinder.APPLICATION_FACTORY);
application = aFactory.getApplication();
The only way that can throw a null pointer is when aFactory is NULL. I really doubt this case because, the same thing is doen in init() of FacesServlet. If it had failed there, the exception should have occured during server startup.
This leaves me more and more confused....I am desperate for some help now :((
Ramesh

App Server 9 - virtual server listener

Similar Messages

Maybe you are looking for