[JBoss Messaging] - HeuristicMixedException: cause and remedy?
by kennardconsulting
Hi guys,
I'm having a hard time finding good documentation on javax.transaction.HeuristicMixedException as it relates to JBoss Messaging. JBoss Messaging seems to throw this exception intermittently while processing large volumes of messages in a batch (say, 2000 messages over 3 cluster nodes):
javax.transaction.HeuristicMixedException
| at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1431)
| at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:137)
| at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
| at org.jboss.resource.adapter.jms.inflow.JmsServerSession$XATransactionDemarcationStrategy.end(JmsServerSession.java:657)
| at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:243)
| at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
| at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
| at java.lang.Thread.run(Thread.java:619)
|
The worst thing is, once the exception is thrown, that node is effectively dead. No more messages get processed. My app has multiple queues, but once one queue on the node fails (say, the e-mail queue) then all queues stop working (say, the reports queues): they all report HeuristicMixedException whenever a messages is sent to them.
I had this same error with JBoss MQ, and upgraded to JBoss Messaging in hopes it would be fixed. But no luck! Can anybody suggest why this error happens, and whether there is some setting to automatically recover from it? If I manually restart the node it works fine.
Regards,
Richard
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241134#4241134
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241134
16 years, 4 months
[Installation, Configuration & DEPLOYMENT] - Deplyoment failing in jboss-5.1.0.GA
by XsubinX
I was using jboss-4.2.1.GA for the deployment , and when I moved the war to jboss-5.1.0.GA , I'm getting XML parser errors.
=========================================
Caused by: org.jboss.xb.binding.JBossXBException: Failed to create a new SAX
parser
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJBossXBParser.java:97)
at
org.jboss.xb.binding.UnmarshallerImpl.(UnmarshallerImpl.java:56)
at
org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:96)
... 73 more
Caused by: java.lang.ClassCastException:
org.apache.xerces.parsers.XML11Configuration cannot be cast to
org.apache.xerces.xni.parser.XMLParserConfiguration
at org.apache.xerces.parsers.SAXParser.(Unknown Source)
at org.apache.xerces.parsers.SAXParser.(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.(Unknown Source)
at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown
Source)
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJBossXBParser.java:92)
=========================================
Anybody faced this before ?
Thanks
Subin
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241126#4241126
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241126
16 years, 4 months
[JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
by rnicholson10
Hey Howard,
Got a little further on figuring this out.
What I did is write a keep alive generator for the bridges so I could monitor them. Each bridge has a timer bean which send a message across the bridge at 10 second interval. Unfortunately this did not stop the bridges from failing but did let me highlight the point where the bridge went down.
| 2009-06-30 06:40:15,015 ERROR [org.jboss.remoting.transport.socket.ServerThread](WorkerThread#2[172.16.113.11:65011]) WorkerThread#2[172.16.113.11:65011] exception occurred during first invocation
|
| 2009-06-30 06:42:48,530 ERROR [STDERR] (Timer-3) Exception in thread "Timer-3"
| 2009-06-30 06:42:48,530 ERROR [STDERR] (Timer-3) java.lang.IllegalStateException: org.jboss.remoting.ConnectionValidator.run() should not be called directly; use org.jboss.remoting.ConnectionValidator.addConnectionListener() instead.
|
| 2009-06-30 06:42:48,531 ERROR [STDERR] (Timer-3) at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:289)
|
| 2009-06-30 06:42:48,531 ERROR [STDERR] (Timer-3) at java.util.TimerThread.mainLoop(Unknown Source)
| 2009-06-30 06:42:48,531 ERROR [STDERR] (Timer-3) at java.util.TimerThread.run(Unknown Source)
| 2009-06-30 06:44:43,967 ERROR [STDERR] (Timer-12) Exception in thread "Timer-12"
| 2009-06-30 06:44:43,968 ERROR [STDERR] (Timer-12) java.lang.IllegalStateException: org.jboss.remoting.ConnectionValidator.run() should not be called directly; use org.jboss.remoting.ConnectionValidator.addConnectionListener() instead.
|
| 2009-06-30 06:44:43,968 ERROR [STDERR] (Timer-12) at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:289)
|
| 2009-06-30 06:44:43,968 ERROR [STDERR] (Timer-12) at java.util.TimerThread.mainLoop(Unknown Source)
| 2009-06-30 06:44:43,968 ERROR [STDERR] (Timer-12) at java.util.TimerThread.run(Unknown Source)
| 2009-06-30 07:03:06,112 ERROR [STDERR] (Timer-15) Exception in thread "Timer-15"
| 2009-06-30 07:03:06,112 ERROR [STDERR] (Timer-15) java.lang.IllegalStateException: org.jboss.remoting.ConnectionValidator.run() should not be called directly; use org.jboss.remoting.ConnectionValidator.addConnectionListener() instead.
|
| 2009-06-30 07:03:06,226 ERROR [STDERR] (Timer-15) at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:289)
|
| 2009-06-30 07:03:06,226 ERROR [STDERR] (Timer-15) at java.util.TimerThread.mainLoop(Unknown Source)
| 2009-06-30 07:03:06,227 ERROR [STDERR] (Timer-15) at java.util.TimerThread.run(Unknown Source)
| 2009-06-30 07:04:33,427 ERROR [org.jboss.jms.server.bridge.Bridge] (Thread-281) Failed to start source connection
|
Hopefully this will give you enough info to help pinpoint where the error occurs. If you have any ideas for further tests let me know.
Cheers,
R.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241122#4241122
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241122
16 years, 4 months
[JCA/JBoss] - xa-datasource for postgresql is not getting deployed in jbos
by preetam_pict
hello all
i want to create xa-datasource for postgresql (windows version 8.3)
i am using recently downloaded jboss-5.1.0.GA-jdk6
but somehow the ds is not getting created. there are no errors / exceptions in logs. (even no debug logs about this activity!)
where it might be going wrong?
(My other local-tx-datasource is working fine!)
Thanks in advance for any help!
~PP
here is my configuration of
jboss-5.1.0.GA-jdk6\server\default\deploy\jboss-ds-xa.xml
| <?xml version="1.0" encoding="UTF-8"?>
| <datasources>
| <xa-datasource>
| <jndi-name>TZ</jndi-name>
|
| <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
| <xa-datasource-property name="ServerName">127.0.0.1</xa-datasource-property>
| <xa-datasource-property name="PortNumber">5432</xa-datasource-property>
|
| <xa-datasource-property name="DatabaseName">sz</xa-datasource-property>
| <xa-datasource-property name="User">postgres</xa-datasource-property>
| <xa-datasource-property name="Password">postgres</xa-datasource-property>
|
| <min-pool-size>5</min-pool-size>
| <max-pool-size>20</max-pool-size>
| <blocking-timeout-millis>2000</blocking-timeout-millis>
| <idle-timeout-minutes>5</idle-timeout-minutes>
| <new-connection-sql>;</new-connection-sql>
| <check-valid-connection-sql>;</check-valid-connection-sql>
|
| </xa-datasource>
|
| <xa-datasource>
| <jndi-name>TZ_Archive</jndi-name>
|
| <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
| <xa-datasource-property name="ServerName">127.0.0.1</xa-datasource-property>
| <xa-datasource-property name="PortNumber">5432</xa-datasource-property>
|
| <xa-datasource-property name="DatabaseName">sz-archive</xa-datasource-property>
| <xa-datasource-property name="User">postgres</xa-datasource-property>
| <xa-datasource-property name="Password">postgres</xa-datasource-property>
|
| <min-pool-size>5</min-pool-size>
| <max-pool-size>20</max-pool-size>
| <blocking-timeout-millis>2000</blocking-timeout-millis>
| <idle-timeout-minutes>5</idle-timeout-minutes>
| <new-connection-sql>;</new-connection-sql>
| <check-valid-connection-sql>;</check-valid-connection-sql>
|
| </xa-datasource>
|
| </datasources>
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241120#4241120
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241120
16 years, 4 months