这是消息，并在启动调度程序后挂起。没有错误消息。有任何建议可以追查问题吗？它昨天工作正常，今天早上重新开始。没有更改已部署的应用程序。但是我们有大约一百万条jms消息，从JBoss管理控制台中删除了所有消息。
12:30:40,233 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@11c611c6[domain=default, server=default, name=default]
[2012-11-28 12:33:51,325] [main] [WARN ] org.jboss.jms.server.jbosssx.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.
[2012-11-28 12:33:51,606] [main] [WARN ] org.jboss.annotation.factory.AnnotationCreator: No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
[2012-11-28 12:33:51,964] [main] [WARN ] org.jboss.annotation.factory.AnnotationCreator: No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
[2012-11-28 12:33:52,153] [main] [INFO ] com.arjuna.ats.jbossatx.jta.TransactionManagerService: JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.
[2012-11-28 12:33:52,153] [main] [INFO ] com.arjuna.ats.jbossatx.jta.TransactionManagerService: Setting up property manager MBean and JMX layer
[2012-11-28 12:33:52,606] [main] [INFO ] com.arjuna.ats.jbossatx.jta.TransactionManagerService: Initializing recovery manager
[2012-11-28 12:33:52,933] [main] [INFO ] com.arjuna.ats.jbossatx.jta.TransactionManagerService: Recovery manager configured
[2012-11-28 12:33:52,933] [main] [INFO ] com.arjuna.ats.jbossatx.jta.TransactionManagerService: Binding TransactionManager JNDI Reference
[2012-11-28 12:33:53,006] [main] [INFO ] com.arjuna.ats.jbossatx.jta.TransactionManagerService: Starting transaction recovery manager
[2012-11-28 12:33:54,434] [main] [INFO ] org.apache.catalina.core.AprLifecycleListener: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: {my path displayed here}
[2012-11-28 12:33:55,335] [main] [INFO ] org.apache.coyote.http11.Http11Protocol: Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
[2012-11-28 12:33:55,424] [main] [INFO ] org.apache.coyote.ajp.AjpProtocol: Initializing Coyote AJP/1.3 on ajp-0.0.0.0-8009
[2012-11-28 12:33:55,463] [main] [INFO ] org.apache.catalina.core.StandardService: Starting service jboss.web
[2012-11-28 12:33:55,465] [main] [INFO ] org.apache.catalina.core.StandardEngine: Starting Servlet Engine: JBoss Web/2.1.3.GA
[2012-11-28 12:33:55,594] [main] [INFO ] org.apache.catalina.startup.Catalina: Server startup in 170 ms
[2012-11-28 12:34:01,723] [main] [INFO ] org.quartz.simpl.SimpleThreadPool: Job execution threads will use class loader of thread: main
[2012-11-28 12:34:01,765] [main] [INFO ] org.quartz.core.QuartzScheduler: Quartz Scheduler v.1.5.2 created.
[2012-11-28 12:34:01,773] [main] [INFO ] org.quartz.simpl.RAMJobStore: RAMJobStore initialized.
[2012-11-28 12:34:01,773] [main] [INFO ] org.quartz.impl.StdSchedulerFactory: Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
[2012-11-28 12:34:01,773] [main] [INFO ] org.quartz.impl.StdSchedulerFactory: Quartz scheduler version: 1.5.2
[2012-11-28 12:34:01,773] [main] [INFO ] org.quartz.core.QuartzScheduler: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
答案 0 :(得分：0)
我通过删除data / hypersonic文件夹并重新启动来解决了这个问题。它有大型的.script文件（JBoss在这里坚持使用JMS消息），这可能导致了这个问题。