I am using Jboss 3.2.3 and am getting the following error message. The JDBC
version is 2.0. Will this be solved by using JDBC 3.0. Is this JDBC version
change possible without changing Jboss 3.2.3 version.
INFO | jvm 1| 2005/03/25 19:30:54 | processName= acceptance_processCould
not
I am working with jboss-3.2.4.
Sorry, I thought it is a matter of course.
I have read your posting here. So I tried the
org.jboss.mq.pm.jdbc3.PersistenceManager. This works fine. Thank you :-) But I thought
it was a bug in 3.2.4RC or earlier versions.
It seems your bugfix for jboss-3.2.4 doesnt
Hello Adrian, I have a similar problem: want do you mean? thank you for comment.
2004-06-21 09:54:04,391 ERROR [com.company.JMSSender](Thread-13 :) 1010
7: Fehler beim senden der TIMEOUT-JMS
org.jboss.mq.SpyJMSException: Could not store message: 886 msg=0 hard NOT_STORED
NON_PERSISTENT
Which version of JBoss are you running?
Try JBoss 3.2.4 release.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3839548#3839548
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3839548
Genman,
Your fix relates to transactions not messages?
Can you explain how this would fix a duplicate message id?
Thanks for the fix by the way.
Regards,
Adrian
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3831907#3831907
Reply to the post :
Adrian, there is a real bug in jdbc2/PersistenceManager which you avoided in your
jdbc3 PM, with respect to incrementing long values.
I'm checking a fix for 3.2 branch.
isotope1145, if you use org.jboss.mq.pm.jdbc3.PersistenceManager (in 3.2.4RC) your
problem should go away.
View the
For purposes of showing up on a search, here is the trace I get:
Caused by: org.jboss.mq.SpyJMSException: Could not crate tx: 97107; - nested
throwable: (java.sql.SQLException: Violation of unique index: SYS_PK_JMS_TRANSACTIONS
in statement [INSERT INTO JMS_TRANSACTIONS (TXID) values(97107)])
