I was having a similar problem. JMS was hanging with the same warning message. I think
the difference with the original post is that my persistent store is oracle. I solved
my problem by changing the type of MESSAGEBLOB to LONG RAW. Most likely oracle thin
driver has some issues with BLOB type w
Thanks for the responses... Ivelin, for your question for the help, yes but after I
get more familiar with jboss...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3829325#3829325
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=r
Ivelin, I am using 4.0.0DR3, not sure it has the same enhancements?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3828896#3828896
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3828896
-
I am trying to use HAJMS to achieve fault tolerance, I think I stumbled into a bug.
Messageid seems to be kept in memory separately in each server in the cluster. If
there are persistent messages stored into database and waiting to be consumed, trying
to fail over to other server causes database