[black_fire]

I’m getting an exception when I try to run Sun Application Server

This is my system config:
JVM: C:\Java\jdk1.5.0_04
App Server: C:\Java\Sun\AppServer
Server Name: server
Domain Name: domain1
Domain Directory: C:\Java\Sun\AppServer\domains\domain1

Is there anybody that had already fixed this problem?
Any help is welcome! 😉

Best Regards,
Rodrigo G. Tavares de Souza
São Paulo – Brazil

Follow the exception
[color=red]

28/07/2005 13:57:30 com.sun.enterprise.jms.JmsProviderLifecycle checkProviderStartup
INFO: JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\java\Sun\AppServer\imq\bin].
28/07/2005 13:57:30 com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
WARNING: 28/07/2005 13:57:30 com.sun.enterprise.jms.JmsProviderLifecycle checkProviderStar
recursive call into SystemOutandErrhandler
java.lang.RuntimeException: recursivecall
    at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:189)
.
.
.
28/07/2005 14:22:10 com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
INFO: JMS5029: Successfully attached to an existing Message Queue broker. Instance Name = imqbroker
28/07/2005 14:22:10 com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush
WARNING: 28/07/2005 14:22:10 com.sun.enterprise.jms.JmsProviderLifecycle onInitialization
INFO: JMS5029: Successfully attached to an existing Message Queue broker. Instance Name = imqbroker
.
.
.

[Scott Anderson]

That’s a known issue in 4.0M2 that was caused by a change in the latest release of Sun’s server. We’ve corrected the issue internally
and the fix will be available as part of the 4.0M3 build in about a week. Sorry for the inconvenience.

[Author]

Posts