-
2. Re: mysterious shutdown of jboss 5.0.1
tess Jan 5, 2011 11:49 AM (in response to nickarls)HI Thank you for your reply.
I have also seen that documentation .But i do not know where to put -Xr
-
3. Re: mysterious shutdown of jboss 5.0.1
peterj Jan 5, 2011 11:55 AM (in response to tess)But i do not know where to put -Xr
Place the -Xrs in the run.conf.bat file, adding it to the other JAVA_OPTS values. You could also place it into the service.xml file, but then you would have to modify the run.conf.bat file (the file currently doesn't do anything if JAVA_OPTS is already set).
-
4. Re: mysterious shutdown of jboss 5.0.1
tess Jan 7, 2011 4:41 AM (in response to peterj)Hi ,Thank you for your reply.
I have used service.bat file provided along with jboss 5.0.1 to put jboss as a service on windows server 2003.
I have controlled service.bat and there is already set the option:
set JAVA_OPTS=-Xrs
also i have controlled run.conf and found these lines:
# Specify options to pass to the Java VM.
#
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"# Sample JPDA settings for remote socket debuging
#JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"# Sample JPDA settings for shared memory debugging
#JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_shmem,server=y,suspend=n,address=jboss"and when i have controlled run.bat I have found these lines:
rem JVM memory allocation pool parameters. Modify as appropriate.
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512mrem With Sun JVMs reduce the RMI GCs to once per hour
set JAVA_OPTS=%JAVA_OPTS% -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000rem JPDA options. Uncomment and modify as appropriate to enable remote debugging.
rem set JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS%Am I correct if i uncomment these line?
Thank you.
-
5. Re: mysterious shutdown of jboss 5.0.1
nickarls Jan 7, 2011 5:35 AM (in response to tess)I'm not sure you'll want to run the server in debug mode. What is the ouput from splash screen (showing the startup parameters) when you start the server?
-
6. Re: mysterious shutdown of jboss 5.0.1
tess Jan 7, 2011 7:20 AM (in response to nickarls)hi ,
when jboss starts log details go to run.log
This is a part when start jboss.
Starting JBoss Application Server 5.0.1 [2011-01-07 13:10:26]
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\Programmi\jboss-5.0.1.GA
JAVA: C:\Programmi\Java\jdk1.6.0_20\bin\java
JAVA_OPTS: -Xrs -Dprogram.name=run.bat -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: C:\Programmi\jboss-5.0.1.GA\bin\run.jar
I am not running in debug mode.
Thank you again for your patience.
-
7. mysterious shutdown of jboss 5.0.1
nickarls Jan 7, 2011 7:29 AM (in response to tess)Ah yes, the debug stuff was still commented out
How does the log end when it shuts down? Do the shutdown hooks kick in (does it look like a clean shutdown or a process death)
Can you link it to someone using remote desktop session?
-
8. mysterious shutdown of jboss 5.0.1
tess Jan 7, 2011 8:31 AM (in response to nickarls)Hi,
When I stops jboss locally I get this log:
13:50:49,383 INFO [ServerImpl] Shutting down the server, blockingShutdown: false
13:50:49,383 INFO [ServerImpl] Server exit(0) called
13:50:49,398 INFO [ServerImpl] Runtime shutdown hook called, forceHalt: true
13:50:49,398 INFO [Http11Protocol] Pausing Coyote HTTP/1.1 on http-0.0.0.0-8080
13:50:49,398 INFO [Http11Protocol] Stopping Coyote HTTP/1.1 on http-0.0.0.0-8080
13:50:49,429 INFO [AjpProtocol] Pausing Coyote AJP/1.3 on ajp-0.0.0.0-8009
13:50:49,429 INFO [AjpProtocol] Stopping Coyote AJP/1.3 on ajp-0.0.0.0-8009
13:50:49,445 INFO [Http11Protocol] Pausing Coyote HTTP/1.1 on http-0.0.0.0-8443
13:50:49,445 INFO [Http11Protocol] Stopping Coyote HTTP/1.1 on http-0.0.0.0-8443
13:50:49,554 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@70a698 undeployed
13:50:49,554 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@b3b96f undeployed
13:50:49,554 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@7531e4 undeployed
13:50:49,586 INFO [TomcatDeployment] undeploy, ctxPath=/web-console
13:50:49,679 INFO [QueueService] Queue[/queue/ExpiryQueue] stopped
13:50:49,695 INFO [QueueService] Queue[/queue/DLQ] stopped
13:50:49,695 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' from JNDI name 'java:JmsXA'
13:50:49,742 INFO [ServerPeer] JMS ServerPeer[0] stopped
13:50:49,773 INFO [TomcatDeployment] undeploy, ctxPath=/invoker
13:50:49,804 INFO [TomcatDeployment] undeploy, ctxPath=/jbossws
13:50:49,851 INFO [TomcatDeployment] undeploy, ctxPath=/Consultazione
13:50:49,851 INFO [TomcatDeployment] undeploy, ctxPath=/CustomerService
13:50:49,851 INFO [TomcatDeployment] undeploy, ctxPath=/
13:50:49,851 INFO [TomcatDeployment] undeploy, ctxPath=/Sispas
13:50:49,867 INFO [TomcatDeployment] undeploy, ctxPath=/jmx-console
13:50:49,867 INFO [StandardService] Stopping service jboss.web
13:50:50,039 INFO [MailService] Mail service 'java:/Mail' removed from JNDI
13:50:50,117 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' from JNDI name 'java:DefaultDS'
13:50:50,164 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
13:50:50,164 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
13:50:50,164 INFO [SimpleThreadPool] There are still 27 worker threads active. See javadoc runInThread(Runnable) for a possible explanation
13:50:50,164 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.
13:50:50,538 INFO [TransactionManagerService] Stopping transaction recovery manager
13:50:50,866 INFO [HypersonicDatabase] Database standalone closed clean
13:50:54,147 INFO [ServerImpl] Shutdown complete
Shutdown complete
Halting VM
Shutdown JBoss Application Server 5.0.1 service [2011-01-07 13:50:55]
When I put jboss locally ,there is no such problem because each day restart the computer.
But when I put it for client after one week (not exactly) jboss stops alone.
I have a copy of log file of client where jboss shut down.
But How can I send it to you.?It is not permitted to connect to client server.
-
9. mysterious shutdown of jboss 5.0.1
nickarls Jan 7, 2011 8:39 AM (in response to tess)It doesn't have to be the complete file. Post the part before and after it goes down/restarts...
-
10. mysterious shutdown of jboss 5.0.1
tess Jan 7, 2011 9:00 AM (in response to nickarls)Hi,
I am not sure whether I can post a long log file like this:
Starting JBoss Application Server 5.0.1 [2011-01-07 14:46:46]
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\Programmi\jboss-5.0.1.GA
JAVA: C:\Programmi\Java\jdk1.6.0_20\bin\java
JAVA_OPTS: -Xrs -Dprogram.name=run.bat -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: C:\Programmi\jboss-5.0.1.GA\bin\run.jar
===============================================================================
14:46:47,767 INFO [ServerImpl] Starting JBoss (Microcontainer)...
14:46:47,783 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)
14:46:47,783 INFO [ServerImpl] Bootstrap URL: null
14:46:47,783 INFO [ServerImpl] Home Dir: C:\Programmi\jboss-5.0.1.GA
14:46:47,783 INFO [ServerImpl] Home URL: file:/C:/Programmi/jboss-5.0.1.GA/
14:46:47,783 INFO [ServerImpl] Library URL: file:/C:/Programmi/jboss-5.0.1.GA/lib/
14:46:47,783 INFO [ServerImpl] Patch URL: null
14:46:47,783 INFO [ServerImpl] Common Base URL: file:/C:/Programmi/jboss-5.0.1.GA/common/
14:46:47,783 INFO [ServerImpl] Common Library URL: file:/C:/Programmi/jboss-5.0.1.GA/common/lib/
14:46:47,783 INFO [ServerImpl] Server Name: default
14:46:47,783 INFO [ServerImpl] Server Base Dir: C:\Programmi\jboss-5.0.1.GA\server
14:46:47,783 INFO [ServerImpl] Server Base URL: file:/C:/Programmi/jboss-5.0.1.GA/server/
14:46:47,783 INFO [ServerImpl] Server Config URL: file:/C:/Programmi/jboss-5.0.1.GA/server/default/conf/
14:46:47,783 INFO [ServerImpl] Server Home Dir: C:\Programmi\jboss-5.0.1.GA\server\default
14:46:47,783 INFO [ServerImpl] Server Home URL: file:/C:/Programmi/jboss-5.0.1.GA/server/default/
14:46:47,783 INFO [ServerImpl] Server Data Dir: C:\Programmi\jboss-5.0.1.GA\server\default\data
14:46:47,783 INFO [ServerImpl] Server Library URL: file:/C:/Programmi/jboss-5.0.1.GA/server/default/lib/
14:46:47,783 INFO [ServerImpl] Server Log Dir: C:\Programmi\jboss-5.0.1.GA\server\default\log
14:46:47,783 INFO [ServerImpl] Server Native Dir: C:\Programmi\jboss-5.0.1.GA\server\default\tmp\native
14:46:47,783 INFO [ServerImpl] Server Temp Dir: C:\Programmi\jboss-5.0.1.GA\server\default\tmp
14:46:47,783 INFO [ServerImpl] Server Temp Deploy Dir: C:\Programmi\jboss-5.0.1.GA\server\default\tmp\deploy
14:46:48,439 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/Programmi/jboss-5.0.1.GA/server/default/conf/bootstrap.xml
14:46:49,001 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
14:46:49,001 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
14:46:49,314 INFO [CopyMechanism] VFS temp dir: C:\Programmi\jboss-5.0.1.GA\server\default\tmp
14:46:49,314 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
14:46:50,720 INFO [ServerInfo] Java version: 1.6.0_20,Sun Microsystems Inc.
14:46:50,736 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
14:46:50,736 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 16.3-b01,Sun Microsystems Inc.
14:46:50,736 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:46:50,767 INFO [JMXKernel] Legacy JMX core initialized
14:46:53,704 INFO [ProfileServiceImpl] Loading profile: default from: org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@1eae15f(root=C:\Programmi\jboss-5.0.1.GA\server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
14:46:53,704 INFO [ProfileImpl] Using repository:org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@1eae15f(root=C:\Programmi\jboss-5.0.1.GA\server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
14:46:53,704 INFO [ProfileServiceImpl] Loaded profile: ProfileImpl@1d0e2c9{key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default]}
14:46:55,642 INFO [WebService] Using RMI server codebase: http://emanuela:8083/
14:47:02,173 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
14:47:02,173 INFO [NativeServerConfig] 3.0.5.GA
14:47:14,017 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://emanuela/jndi/rmi://emanuela:1090/jmxconnector
14:47:14,204 INFO [MailService] Mail Service bound to java:/Mail
14:47:16,220 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
14:47:16,251 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
14:47:16,392 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
14:47:16,392 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
14:47:16,673 INFO [TransactionManagerService] Initializing recovery manager
14:47:16,861 INFO [TransactionManagerService] Recovery manager configured
14:47:16,861 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
14:47:16,892 INFO [TransactionManagerService] Starting transaction recovery manager
14:47:17,548 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
14:47:17,564 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-0.0.0.0-8009
14:47:18,376 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8443
14:47:18,376 INFO [StandardService] Starting service jboss.web
14:47:18,376 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA
14:47:18,439 INFO [Catalina] Server startup in 1035 ms
14:47:18,454 INFO [TomcatDeployment] deploy, ctxPath=/web-console
14:47:19,376 INFO [TomcatDeployment] deploy, ctxPath=/invoker
14:47:19,470 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
14:47:19,595 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/Programmi/jboss-5.0.1.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
14:47:19,611 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/Programmi/jboss-5.0.1.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
14:47:19,658 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/Programmi/jboss-5.0.1.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
14:47:19,673 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/Programmi/jboss-5.0.1.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
14:47:19,704 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/Programmi/jboss-5.0.1.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
14:47:19,798 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
14:47:19,845 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
14:47:19,845 INFO [RAMJobStore] RAMJobStore initialized.
14:47:19,845 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
14:47:19,845 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
14:47:19,845 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
14:47:20,517 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
14:47:21,142 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started
14:47:21,251 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
14:47:21,454 INFO [ConnectionFactory] Connector bisocket://emanuela:4457 has leasing enabled, lease period 10000 milliseconds
14:47:21,454 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@131797d started
14:47:21,454 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
14:47:21,454 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
14:47:21,454 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
14:47:21,454 INFO [ConnectionFactory] Connector bisocket://emanuela:4457 has leasing enabled, lease period 10000 milliseconds
14:47:21,454 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1544e03 started
14:47:21,454 INFO [ConnectionFactory] Connector bisocket://emanuela:4457 has leasing enabled, lease period 10000 milliseconds
14:47:21,454 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1679a2 started
14:47:21,704 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
14:47:21,986 INFO [TomcatDeployment] deploy, ctxPath=/Consultazione
14:47:22,064 WARN [JAXWSDeployerHookPreJSE] Cannot load servlet class: CustomerServlet
14:47:22,189 INFO [TomcatDeployment] deploy, ctxPath=/CustomerService
14:47:22,236 INFO [TomcatDeployment] deploy, ctxPath=/
14:47:22,283 INFO [TomcatDeployment] deploy, ctxPath=/Sispas
14:47:22,345 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
14:47:22,423 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
14:47:22,454 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
14:47:22,470 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8443
14:47:22,486 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)] Started in 34s:703ms
14:47:35,486 INFO [ServerImpl] Shutting down the server, blockingShutdown: false
14:47:35,486 INFO [ServerImpl] Server exit(0) called
14:47:35,486 INFO [ServerImpl] Runtime shutdown hook called, forceHalt: true
14:47:35,501 INFO [Http11Protocol] Pausing Coyote HTTP/1.1 on http-0.0.0.0-8080
14:47:35,501 INFO [Http11Protocol] Stopping Coyote HTTP/1.1 on http-0.0.0.0-8080
14:47:35,501 INFO [AjpProtocol] Pausing Coyote AJP/1.3 on ajp-0.0.0.0-8009
14:47:35,501 INFO [AjpProtocol] Stopping Coyote AJP/1.3 on ajp-0.0.0.0-8009
14:47:35,517 INFO [Http11Protocol] Pausing Coyote HTTP/1.1 on http-0.0.0.0-8443
14:47:35,517 INFO [Http11Protocol] Stopping Coyote HTTP/1.1 on http-0.0.0.0-8443
14:47:35,642 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1679a2 undeployed
14:47:35,658 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1544e03 undeployed
14:47:35,658 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@131797d undeployed
14:47:35,689 INFO [TomcatDeployment] undeploy, ctxPath=/web-console
14:47:35,751 INFO [QueueService] Queue[/queue/ExpiryQueue] stopped
14:47:35,751 INFO [QueueService] Queue[/queue/DLQ] stopped
14:47:35,767 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' from JNDI name 'java:JmsXA'
14:47:35,783 INFO [ServerPeer] JMS ServerPeer[0] stopped
14:47:35,814 INFO [TomcatDeployment] undeploy, ctxPath=/invoker
14:47:35,861 INFO [TomcatDeployment] undeploy, ctxPath=/jbossws
14:47:35,861 INFO [TomcatDeployment] undeploy, ctxPath=/Consultazione
14:47:35,876 INFO [TomcatDeployment] undeploy, ctxPath=/CustomerService
14:47:35,876 INFO [TomcatDeployment] undeploy, ctxPath=/
14:47:35,876 INFO [TomcatDeployment] undeploy, ctxPath=/Sispas
14:47:35,892 INFO [TomcatDeployment] undeploy, ctxPath=/jmx-console
14:47:35,892 INFO [StandardService] Stopping service jboss.web
14:47:36,142 INFO [MailService] Mail service 'java:/Mail' removed from JNDI
14:47:36,204 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' from JNDI name 'java:DefaultDS'
14:47:36,236 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
14:47:36,236 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
14:47:36,236 INFO [SimpleThreadPool] There are still 29 worker threads active. See javadoc runInThread(Runnable) for a possible explanation
14:47:36,236 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.
14:47:36,470 INFO [TransactionManagerService] Stopping transaction recovery manager
14:47:36,751 INFO [HypersonicDatabase] Database standalone closed clean
14:47:39,908 INFO [ServerImpl] Shutdown complete
Shutdown complete
Halting VM
Shutdown JBoss Application Server 5.0.1 service [2011-01-07 14:47:40]
-
11. mysterious shutdown of jboss 5.0.1
nickarls Jan 7, 2011 9:04 AM (in response to tess)It looks like it started and stopped almost immediately(?). At least it appears to have got some shutdown signal, it didn't just die.
-
12. mysterious shutdown of jboss 5.0.1
tess Jan 7, 2011 9:21 AM (in response to nickarls)Oops.I am sorry.
I have started and stopped it manually to show you the log.
I you have an email address i will send the original log of client as attachment.