11 Replies Latest reply on Dec 14, 2010 4:23 AM by Benson Fung

    Alert cannot be fired because JMS subsystem issue

    Benson Fung Newbie

      Hi,

       

      I setup several alert element in the RHQ.  However, it doesn't get fired even the conditions are matched with exception as below.  Please help.

       

      2010-11-18 07:15:27,524 ERROR [org.rhq.enterprise.server.alert.engine.internal.AlertConditionCacheCoordinator] Error processing matched cache element 'MeasurementNumericCacheElement[ alertConditionTriggerId=10037, alertConditionOperator=GREATER_THAN, alertConditionValue=2.0 ]': null

      2010-11-18 07:15:27,524 ERROR [org.rhq.enterprise.server.alert.engine.internal.AlertConditionCacheCoordinator] There were 2 alert conditions that did not fire. Please check the configuration of the JMS subsystem and try again.

       

       

       

      Actually, I just downloaded, extract it and then run.  No configuration was done.  Please  help

       

       

      Thanks

        • 1. Re: Alert cannot be fired because JMS subsystem issue
          Heiko Rupp Master

          Hey,

          can you give us some more information about your system? Perhaps from the start process. I think JMS would be hosed if at installation time some thing went wrong (like when running on some unsupported database).

          Also could you look up

           

          2010-11-18 07:15:27,524 ERROR [org.rhq.enterprise.server.alert.engine.internal.AlertConditionCacheCoordinator] Error processing matched cache element 'MeasurementNumericCacheElement[ alertConditionTriggerId=10037, alertConditionOperator=GREATER_THAN, alertConditionValue=2.0 ]': null

           

          rhq-server.log file to see if there are any excpetions listed around this?

          • 2. Re: Alert cannot be fired because JMS subsystem issue
            Benson Fung Newbie

            Hi,

             

            I used the built-in database(hypersonic).  Therefore, I don't think it is running  unsupported database.  And the above error message is full of the rhq-server.log file.  No others.  Could you give me more hints?

            • 3. Re: Alert cannot be fired because JMS subsystem issue
              mazz Master

              We haven't used hypersonic in this code base in year(s) - we ripped that out a while ago because it was very buggy and caused many JMS problems - if you see hypersonic being used by your server, you must be using some really old version of RHQ (in fact, I don't think it was ever used in the open source RHQ codebase, but it was used in a very early version of the Red Hat closed source version of the Jboss Operations Network 1.0 or something like that). What version are you using?

              • 4. Re: Alert cannot be fired because JMS subsystem issue
                Heiko Rupp Master

                Hey, did you mean "H2" ?

                In any case - we were having severe issues with JMS on Hypersonic/Hsqldb in the past

                 

                Having said that: H2 is only meant for Demo purposes and not for any production usage. So I think if you need to have many alerts firing, you should probably switch to Postgres or Oracle.

                • 5. Re: Alert cannot be fired because JMS subsystem issue
                  Benson Fung Newbie

                  Hi John,

                   

                  Actually, I am using JBossON 2.4.  This is also just for demo purposes and display to the client how this product works.  But looks like the alert doesn't work.

                   

                   

                  Benson

                  • 6. Re: Alert cannot be fired because JMS subsystem issue
                    Newbie

                    Benson,

                     

                    I believe the error message here is misleading.  The presumption, when that code was originally written, was that if there was ever any problem sending a message to the JMS queue, then there must be a problem with the JMS subsystem, it's configuration, the load on it, etc.  However, you're first error message:

                     

                    2010-11-18 07:15:27,524 ERROR [org.rhq.enterprise.server.alert.engine.internal.AlertConditionCacheCoordinator] Error processing matched cache element 'MeasurementNumericCacheElement[ alertConditionTriggerId=10037, alertConditionOperator=GREATER_THAN, alertConditionValue=2.0 ]': null

                     

                    Indicates that there was a NullPointerException which prevented (or preempted) the sending of the message onto the JMS queue for out-of-band processing.  Looking at that part of the code, there can only be so many things that could be null:

                     

                    * cacheElement - if this had been null, the NullPointerException would have bubbled up to the caller instead of being a simple error message like you're seeing

                    * providedValue - if this had been null, the condition wouldn't have matched, thus it wouldn't have entered the code block that's throwing the null pointer exception

                    * cachedConditionProducer - this should never be null, but i suppose it's possible if the jndi lookup returns null

                    * stats - but I checked all 6 calling locations, and they always pass a non-null parameter

                     

                    So I'd surmise that your server did not start up properly, and at the moment the alerts cache was loaded the cachedConditionProducer lookup in jndi returned null.  I'm sure you've already done this, but have you restarted the server yet?  Presuming the server starts up correctly without errors, this jndi reference should be available and working correctly.

                     

                    If thing still aren't working after a restart of the server, and you're positive that there are no errors/exceptions upon startup, then one thing you could is:

                     

                    * disable all of your alert definitions

                    * restart the server

                    * enable one alert definition, and wait until it fires

                    * report your finding back on this thread

                     

                    Good luck,

                    -joseph

                    • 7. Re: Alert cannot be fired because JMS subsystem issue
                      Benson Fung Newbie

                      Hi Joseph,

                       

                      I restarted the server, there are exception discovered.

                       

                      2010-11-25 15:33:41,156 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.mq.destination:service=Queue,name=AlertConditionQueue
                      org.jboss.mq.SpyJMSException: Unexpected error in recovery; - nested throwable: (java.lang.ClassCastException: org.h2.jdbc.JdbcBlob cannot be cast to org.jboss.mq.SpyMessage)
                              at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:72)
                              at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:57)
                              at org.jboss.mq.pm.jdbc2.PersistenceManager.restoreQueue(PersistenceManager.java:570)
                              at org.jboss.mq.server.JMSQueue.<init>(JMSQueue.java:66)
                              at org.jboss.mq.server.jmx.Queue.startService(Queue.java:85)
                              at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
                              at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
                              at sun.reflect.GeneratedMethodAccessor3.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.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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
                              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 sun.reflect.GeneratedMethodAccessor5.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.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 $Proxy39.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.GeneratedMethodAccessor36.invoke(Unknown Source)
                              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                              at java.lang.reflect.Method.invoke(Method.java:597)

                       

                      Caused by: java.lang.ClassCastException: org.h2.jdbc.JdbcBlob cannot be cast to org.jboss.mq.SpyMessage
                              at org.jboss.mq.pm.jdbc2.PersistenceManager.extractMessage(PersistenceManager.java:756)
                              at org.jboss.mq.pm.jdbc2.PersistenceManager.internalRestoreQueue(PersistenceManager.java:630)
                              at org.jboss.mq.pm.jdbc2.PersistenceManager.restoreQueue(PersistenceManager.java:559)

                       

                       

                      2010-11-25 15:33:42,353 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.mq.destination:service=Queue,name=DLQ
                      org.jboss.mq.SpyJMSException: Unexpected error in recovery; - nested throwable: (java.lang.ClassCastException: org.h2.jdbc.JdbcBlob cannot be cast to org.jboss.mq.SpyMessage)
                              at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:72)
                              at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:57)
                              at org.jboss.mq.pm.jdbc2.PersistenceManager.restoreQueue(PersistenceManager.java:570)
                              at org.jboss.mq.server.JMSQueue.<init>(JMSQueue.java:66)
                              at org.jboss.mq.server.jmx.Queue.startService(Queue.java:85)
                              at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
                              at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
                              at sun.reflect.GeneratedMethodAccessor3.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.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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
                              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.GeneratedMethodAccessor5.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.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 $Proxy39.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)

                       

                      Caused by: java.lang.ClassCastException: org.h2.jdbc.JdbcBlob cannot be cast to org.jboss.mq.SpyMessage
                              at org.jboss.mq.pm.jdbc2.PersistenceManager.extractMessage(PersistenceManager.java:756)
                              at org.jboss.mq.pm.jdbc2.PersistenceManager.internalRestoreQueue(PersistenceManager.java:630)
                              at org.jboss.mq.pm.jdbc2.PersistenceManager.restoreQueue(PersistenceManager.java:559)
                              ... 115 more

                       

                      WARN  [org.jboss.system.ServiceController] Problem starting service jboss.j2ee:ear=rhq.ear,jar=rhq-enterprise-server-ejb3.jar,name=AlertConditionConsumerBean,service=EJB3
                      javax.management.InstanceAlreadyExistsException: jboss.mq.destination:service=Queue,name=AlertConditionQueue already registered.
                              at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:761)
                              at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:225)
                              at sun.reflect.GeneratedMethodAccessor1.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.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1422)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1417)
                              at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:295)
                              at org.jboss.mq.server.jmx.DestinationManager.createDestination(DestinationManager.java:327)
                              at org.jboss.mq.server.jmx.DestinationManager.createQueue(DestinationManager.java:293)
                              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.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.ejb3.JmxClientKernelAbstraction.invoke(JmxClientKernelAbstraction.java:44)
                              at org.jboss.ejb3.jms.DestinationManagerJMSDestinationFactory.createDestination(DestinationManagerJMSDestinationFactory.java:75)
                              at org.jboss.ejb3.mdb.MessagingContainer.createTemporaryDestination(MessagingContainer.java:573)
                              at org.jboss.ejb3.mdb.MessagingContainer.createDestination(MessagingContainer.java:512)
                              at org.jboss.ejb3.mdb.MessagingContainer.innerCreateQueue(MessagingContainer.java:438)
                              at org.jboss.ejb3.mdb.MessagingContainer.jmsCreate(MessagingContainer.java:400)
                              at org.jboss.ejb3.mdb.MessagingContainer.innerStart(MessagingContainer.java:166)
                              at org.jboss.ejb3.mdb.MessagingContainer.start(MessagingContainer.java:152)
                              at org.jboss.ejb3.mdb.MDB.start(MDB.java:126)
                              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.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103)
                              at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
                              at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
                              at sun.reflect.GeneratedMethodAccessor3.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.server.Invocation.invoke(Invocation.java:86)
                              at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)

                       

                       

                       

                      It really looks like the JMS server cannot be started properly because of the ClassCastExeption.  This is my first time that I came across this strange issue.    Please help how I can fix this.

                       

                       

                      Thanks

                      • 8. Re: Alert cannot be fired because JMS subsystem issue
                        Newbie

                         

                        I believe the error you're seeing might have been introduced during the work done for one of the following bugs:

                         

                        https://bugzilla.redhat.com/show_bug.cgi?id=566235

                        https://bugzilla.redhat.com/show_bug.cgi?id=562236

                         

                        We were migrating off the use of the 'bytea' type on Postgres in favor of 'oid' so that we could properly stream content out of the database, and I believe a regression was introduced for the h2 integratoin regarding blobs.  At the time, it was believed to only affect the content subsystem and patching, but clearly the SpyObjectMessage as part of the JMS subsystem was also affected.  I stood up a quick instance of JON 2.4.0.GA backed by H2, and verified that alerting is completely broken.  I've also verified that the most recent published binary for RHQ also has this issue.  I'm going to escalate with the team, and see what it will take to fix this.

                        • 9. Re: Alert cannot be fired because JMS subsystem issue
                          Benson Fung Newbie

                          Thanks Joseph.  I will wait for your update.

                           

                          BTW, I have installed Postgresql instead to get it connected to JON.  However, I got another exception for Postgresql.  Please see the following :

                           

                          2010-11-26 12:05:01,527 WARN  [org.jboss.resource.connectionmanager.NoTxConnectionManager] Connection error occured: org.jboss.resource.connectionmanager.NoTxConnectionManager$NoTxConnectionEventListener@1a33da2[state=NORMAL mc=org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1c2d176 handles=1 lastUse=1290744301512 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$PoolBySubject@145b486 context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@14ee7d0]
                          java.lang.ArrayIndexOutOfBoundsException: 2
                                  at org.postgresql.util.PGbytea.toBytes(PGbytea.java:76)
                                  at org.postgresql.jdbc2.AbstractJdbc2ResultSet.getBytes(AbstractJdbc2ResultSet.java:2271)
                                  at org.postgresql.jdbc2.AbstractJdbc2ResultSet.getBytes(AbstractJdbc2ResultSet.java:2451)
                                  at org.jboss.resource.adapter.jdbc.WrappedResultSet.getBytes(WrappedResultSet.java:464)
                                  at org.quartz.impl.jdbcjobstore.PostgreSQLDelegate.getJobDetailFromBlob(PostgreSQLDelegate.java:118)
                                  at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.getMapFromProperties(StdJDBCDelegate.java:928)
                                  at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.selectTrigger(StdJDBCDelegate.java:2133)
                                  at org.quartz.impl.jdbcjobstore.JobStoreSupport.retrieveTrigger(JobStoreSupport.java:1554)
                                  at org.quartz.impl.jdbcjobstore.JobStoreSupport.retrieveTrigger(JobStoreSupport.java:1548)
                                  at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2768)
                                  at org.quartz.impl.jdbcjobstore.JobStoreSupport$36.execute(JobStoreSupport.java:2733)
                                  at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3760)
                                  at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2729)
                                  at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:266)
                          2010-11-26 12:05:01,531 WARN  [org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionInvocationHandler] Failed restore connection's original auto commit setting.
                          java.sql.SQLException: Connection is not associated with a managed connection.org.jboss.resource.adapter.jdbc.jdk5.WrappedConnectionJDK5@b2d899
                                  at org.jboss.resource.adapter.jdbc.WrappedConnection.lock(WrappedConnection.java:81)
                                  at org.jboss.resource.adapter.jdbc.WrappedConnection.setAutoCommit(WrappedConnection.java:454)
                                  at org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionInvocationHandler.restoreOriginalAtributes(AttributeRestoringConnectionInvocationHandler.java:134)
                                  at org.quartz.impl.jdbcjobstore.JobStoreSupport.cleanupConnection(JobStoreSupport.java:3551)
                                  at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3774)
                                  at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2729)
                                  at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:266)
                          2010-11-26 12:05:01,532 ERROR [org.quartz.core.QuartzSchedulerThread] quartzSchedulerThreadLoop: RuntimeException null
                          java.lang.reflect.UndeclaredThrowableException
                                  at $Proxy492.rollback(Unknown Source)
                                  at org.quartz.impl.jdbcjobstore.JobStoreSupport.rollbackConnection(JobStoreSupport.java:3601)
                                  at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3764)
                                  at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2729)
                                  at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:266)
                          Caused by: java.lang.reflect.InvocationTargetException
                                  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:592)
                                  at org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionInvocationHandler.invoke(AttributeRestoringConnectionInvocationHandler.java:71)
                                  ... 5 more
                          Caused by: java.sql.SQLException: Connection is not associated with a managed connection.org.jboss.resource.adapter.jdbc.jdk5.WrappedConnectionJDK5@b2d899
                                  at org.jboss.resource.adapter.jdbc.WrappedConnection.lock(WrappedConnection.java:81)
                                  at org.jboss.resource.adapter.jdbc.WrappedConnection.rollback(WrappedConnection.java:496)
                                  ... 10 more

                           

                           

                           

                          Please advise how I can fix this.

                           

                           

                           

                          Thanks

                          • 10. Re: Alert cannot be fired because JMS subsystem issue
                            Newbie

                            By the way, which version of Postgres are you using Benson?

                            • 11. Re: Alert cannot be fired because JMS subsystem issue
                              Benson Fung Newbie

                              Hi,

                               

                              I just downloaded the latest version from Postgresql.

                               

                               

                              Benson