7 Replies Latest reply on Apr 21, 2011 12:10 PM by yashgarg

    JBoss-4.2.3 giving problem when loading

    sentcs

       

      Hi,

      We have deployed the JBoss 4.2.3 with JBoss Messaging 1.4.0.SP3 in production environment.

      we are getting exception as pasted below when starting the Jboss.

      and i have execute the following query to find any mismatch data is available or not but it returned the result as 0 for both.

      select count(1) from jbm_msg_ref where message_id not in (select message_id from jbm_msg);
      select count(1) from jbm_msg where message_id not in (select message_id from jbm_msg_ref);


      Please any body have the idea to what is the impact of this exception and steps to resolve this.





      =========================================================================
      
       JBoss Bootstrap Environment
      
       JBOSS_HOME: /opt/jboss-4.2.3.GA
      
       JAVA: /opt/jdk1.6.0_07/bin/java
      
       JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcIn
      terval=3600000 -Djava.net.preferIPv4Stack=true
      
       CLASSPATH: /opt/jboss-4.2.3.GA/bin/run.jar:/opt/jdk1.6.0_07/lib/tools.jar
      
      =========================================================================
      
      09:53:54,031 INFO [Server] Starting JBoss (MX MicroKernel)...
      09:53:54,031 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)
      09:53:54,032 INFO [Server] Home Dir: /opt/jboss-4.2.3.GA
      09:53:54,032 INFO [Server] Home URL: file:/opt/jboss-4.2.3.GA/
      09:53:54,033 INFO [Server] Patch URL: null
      09:53:54,033 INFO [Server] Server Name: messaging
      09:53:54,033 INFO [Server] Server Home Dir: /opt/jboss-4.2.3.GA/server/messaging
      09:53:54,033 INFO [Server] Server Home URL: file:/opt/jboss-4.2.3.GA/server/messaging/
      09:53:54,033 INFO [Server] Server Log Dir: /opt/jboss-4.2.3.GA/server/messaging/log
      09:53:54,034 INFO [Server] Server Temp Dir: /opt/jboss-4.2.3.GA/server/messaging/tmp
      09:53:54,034 INFO [Server] Root Deployment Filename: jboss-service.xml
      09:53:54,267 INFO [ServerInfo] Java version: 1.6.0_07,Sun Microsystems Inc.
      09:53:54,267 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 10.0-b23,Sun Microsystems Inc.
      09:53:54,267 INFO [ServerInfo] OS-System: Linux 2.6.5-7.244-bigsmp,i386
      09:53:54,605 INFO [Server] Core system initialized
      09:53:56,503 INFO [WebService] Using RMI server codebase: http://172.19.6.5:8083/
      09:53:56,505 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
      09:53:56,950 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
      09:53:56,950 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
      09:53:57,161 INFO [TransactionManagerService] Starting recovery manager
      09:53:57,238 INFO [TransactionManagerService] Recovery manager started
      09:53:57,238 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
      09:53:59,236 INFO [EJB3Deployer] Starting java:comp multiplexer
      09:54:01,736 INFO [NativeServerConfig] JBoss Web Services - Native
      09:54:01,736 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200803312044)
      
      11:30:58 AM: Soumyabrata Dasgupta: 09:54:02,415 INFO [Embedded] Catalina naming disabled
      09:54:02,512 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production envi
      ronments was not found on the java.library.path: /opt/jdk1.6.0_07/jre/lib/i386/server:/opt/jdk1.6.0_07/jre/lib/i386:/opt/jdk1.
      6.0_07/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
      09:54:02,566 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-172.19.6.5-8080
      09:54:02,566 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-172.19.6.5-8009
      09:54:02,566 INFO [Catalina] Initialization processed in 151 ms
      09:54:02,567 INFO [StandardService] Starting service jboss.web
      09:54:02,568 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
      09:54:02,605 INFO [Catalina] Server startup in 38 ms
      09:54:02,682 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
      09:54:03,112 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
      09:54:03,266 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
      09:54:03,511 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war
      /
      09:54:03,811 INFO [MailService] Mail Service bound to java:/Mail
      09:54:03,892 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
      09:54:03,918 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
      09:54:03,935 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
      09:54:03,960 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
      09:54:04,039 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms-ra.rar
      09:54:04,060 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
      09:54:04,083 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
      09:54:04,089 INFO [QuartzResourceAdapter] start quartz!!!
      09:54:04,138 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
      09:54:04,164 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
      09:54:04,166 INFO [RAMJobStore] RAMJobStore initialized.
      09:54:04,166 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Q
      uartz package: 'quartz.properties'
      09:54:04,166 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
      09:54:04,166 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
      09:54:04,364 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=
      JmsXA' to JNDI name 'java:JmsXA'
      09:54:04,454 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=Default
      DS' to JNDI name 'java:DefaultDS'
      09:54:06,109 INFO [ServerPeer] JBoss Messaging 1.4.0.SP3 server [0] started
      09:54:06,683 INFO [ConnectionFactory] Connector bisocket://172.19.6.5:4457 has leasing enabled, lease period 10000 millisecon
      ds
      09:54:06,683 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@47c130 started
      09:54:06,684 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.con
      nectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support f
      ailover
      09:54:06,684 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messagin
      g.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* supp
      11:31:44 AM: Soumyabrata Dasgupta:
      11:31:44 AM: Soumyabrata Dasgupta:  
      11:31:49 AM: Soumyabrata Dasgupta: ort load balancing
      09:54:06,688 INFO [ConnectionFactory] Connector bisocket://172.19.6.5:4457 has leasing enabled, lease period 10000 millisecon
      ds
      09:54:06,688 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@172e08e started
      09:54:06,693 INFO [ConnectionFactory] Connector bisocket://172.19.6.5:4457 has leasing enabled, lease period 10000 millisecon
      ds
      09:54:06,693 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@32087b started
      09:54:34,474 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=100, pageSize=50, downCacheSize=50
      09:54:38,325 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=100, pageSize=50, downCacheSize=50
      09:55:23,448 ERROR [ExceptionUtil] Topic[null, name=CRMTOPIC] startService
      java.lang.IllegalStateException: Unexpected pageOrd: 149 expected: 118
       at org.jboss.messaging.core.impl.JDBCPersistenceManager.getPagedReferenceInfos(JDBCPersistenceManager.java:869)
       at org.jboss.messaging.core.impl.PagingChannelSupport.loadPagedReferences(PagingChannelSupport.java:251)
       at org.jboss.messaging.core.impl.PagingChannelSupport.checkLoad(PagingChannelSupport.java:359)
       at org.jboss.messaging.core.impl.PagingChannelSupport.load(PagingChannelSupport.java:216)
       at org.jboss.jms.server.destination.TopicService.startService(TopicService.java:82)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
       at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
       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:597)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
       at $Proxy0.start(Unknown Source)
       at org.jboss.system.ServiceController.start(ServiceController.java:417)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:597)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      11:32:34 AM: Soumyabrata Dasgupta: at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
       at $Proxy4.start(Unknown Source)
       at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
       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:597)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
       at $Proxy42.start(Unknown Source)
       at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
       at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:597)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
       at $Proxy9.deploy(Unknown Source)
       at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
       at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
       at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
       at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)<?xml version="1.0" encoding="windows-1250"?>
      
      


        • 1. Re: JBoss-4.2.3 giving problem when loading
          peterj

          It appears that you are using hsqldb as the database, is this true? If so, do you want to recover the messages, or do you not care about the messages? If you do not care about the messages, you could simply delete the server/messaging/data directory - that will remove the hsqldb "database."

          • 2. Re: JBoss-4.2.3 giving problem when loading
            sentcs

            Hi,

            Thanks for your response.

            We have rectified this problem by following steps.

            1. we have enabled the trace log.
            2. We found the exact probelm i mean found the particular channel id and which pageOrd getting probelm by following SQL query.

            SELECT MESSAGE_ID, DELIVERY_COUNT, PAGE_ORD, SCHED_DELIVERY FROM JBM_MSG_REF WHERE CHANNEL_ID = 357 order by PAGE_ORD

            3. above query returns invalid data for page_ord column as pasted below.

            45655379, 0, 117, 0
            45655312, 0, 149, 0
            45655313, 0, 150, 0

            Here we can see the inorder second row for page_ord column which has formatted by bold letter for your reference.

            4. Then we have updated page_org to 148 instead of 117.

            5. After mage above chanegs, now jboss is working fine.


            MY DOUBT:

            1. Why the page_org column got changed to inorder.
            2. In which scenario page_org column will get afftect.
            3. If we getting this probelm what is proper way to resolve this same.


            Please kindly request to give any steps to resolve this.


            Thanks,



            • 3. Re: JBoss-4.2.3 giving problem when loading
              timfox

              As Peter points out, if you're using HSQL that is your problem.

              HSQL cannot/must not be used with JBM for anything other than playing around with a few demos. It does not have transaction isolation amongst other things. This is also covered in the user guide and on the wiki.

              Can you clarify which database you are using?

              • 4. Re: JBoss-4.2.3 giving problem when loading
                sentcs

                we are using database as mysql-5.0.22-win32 .

                • 5. Re: JBoss-4.2.3 giving problem when loading
                  timfox

                  Which database engine type are you using for your tables?

                  MySQL allows a choice.

                  • 6. Re: JBoss-4.2.3 giving problem when loading
                    sentcs

                    We are using database engine as innoDB. which is default provided by JBoss Messaging 1.4.0.SP3 server

                    Thanks

                    • 7. Re: JBoss-4.2.3 giving problem when loading
                      yashgarg

                      senthil, do you know how you started the trace log?