Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2994
  • Last Modified:

problem while start up in JBOSS server 4.0.5 GA

hi all

I have JOBSS server 4.0.5 GA installed on the our server having the operating system as windows server 2003. Server gets startup correctly and works fine at the first time but when i shutdown the server and again tried to start it, it hangs up. Following is the stack trace from log file(jb.10102007.log)


Stack Trace
16:31:49,968 INFO  [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep
loy/management/console-mgr.sar/web-console.war/
16:31:53,484 INFO  [MailService] Mail Service bound to java:/Mail
16:31:54,390 INFO  [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-local-jdbc.rar
16:31:54,656 INFO  [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-xa-jdbc.rar
16:31:54,812 INFO  [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-local-jdbc.rar
16:31:55,015 INFO  [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-xa-jdbc.rar
16:31:55,093 INFO  [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jms/jms-ra.rar
16:31:55,390 INFO  [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/mail-ra.rar
16:32:18,062 INFO  [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca
:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
16:37:20,359 WARN  [TransactionImpl] Transaction TransactionImpl:XidImpl[FormatI
d=257, GlobalId=TPSLVL00102/3, BranchQual=, localId=3] timed out. status=STATUS_
ACTIVE

This happening because server throws the following exception in the server.log file(c:/jboss4.0.5.GA/server/default/log)

Stack Trace
java.sql.SQLException: Table already exists: JMS_MESSAGES in statement [CREATE CACHED TABLE JMS_MESSAGES]
at org.hsqldb.jdbc.Util.throwError(Unknown Source)
at org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate(Unknown Source)
at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.executeUpdate(CachedPreparedStatement.java:95)
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:251)
at org.jboss.mq.pm.jdbc2.PersistenceManager.createSchema(PersistenceManager.java:277)
2007-10-10 16:32:19,093 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Could not create table with SQL: CREATE CACHED TABLE JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY (TXID) )
java.sql.SQLException: Table already exists: JMS_TRANSACTIONS in statement [CREATE CACHED TABLE JMS_TRANSACTIONS]
at org.hsqldb.jdbc.Util.throwError(Unknown Source)
at org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate(Unknown Source)
at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.executeUpdate(CachedPreparedStatement.java:95)

2007-10-10 16:32:19,093 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Could not create table with SQL: CREATE CACHED TABLE JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY (TXID) )
java.sql.SQLException: Table already exists: JMS_TRANSACTIONS in statement [CREATE CACHED TABLE JMS_TRANSACTIONS]
at org.hsqldb.jdbc.Util.throwError(Unknown Source)
at org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate(Unknown Source)
at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.executeUpdate(CachedPreparedStatement.java:95)

I am suspecting server throws this exception due to it is not able to shutdown the instance of "hypersonicdatabase" which is the default database of the JBOSS.

please tell me what is the meaning of the above exception and how to resolve it.  

0
techprocess
Asked:
techprocess
1 Solution
 
ramazanyichCommented:
As you can see it is not an ERROR message it is a DEBUG message.
So you should not worry about it.
It happens because JMS server of JBOSS (JBOSSMQ) tries to create tables during every startup of JBOSS. First time it creates them and after that as it is already created  wil show you such a DEBUG message. But it isnormal behavior.If you want to avoid logging then find file jms/hsqldb-jdbc-state-service.xml under deploy or deploy-hassingleton directory and change lines
CREATE_TABLES_ON_STARTUP = TRUE
to CREATE_TABLES_ON_STARTUP = FALSE
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now