In our environment, we are not allowed to generate multicast traffic on the
default address used by jboss jndi client. Even after setting
disableDiscovery=true the jndi client is generating multicast traffic when the
target jboss server is shutdown. Do i need to set any other attribute as well
you can get 1.3.4 from the source
http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html
and apply it. That is what i did.
regards
Karthik
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867216#3867216
Reply to the post
Since we upgraded the concurrent.jar, we have not seen this problem re-occur.
I see no harm in trying it out. From the size of the jar distributed with
4.0.1, I suspect it is not the latest version.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866998#386699
Thanks for the hint. I will replace our concurrent.jar and see how it goes.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862539#3862539
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862539
All of a sudden the Message Driven Bean stops processing messages. We have to
do a stopDelivery() and startDelivery() on the MDB to restart processing.
Also, the stopDelivery() hangs and the message at the top of the queue, when it
stopped processing, will not get processed till JBoss is resta
1. Instead of writing your own jbosscmp-jdbc.xml, copy standardjbosscmp-jdbc.xml in to
your META-INF directory and rename it as jbosscmp-jdbc.xml .
2.see that you had given datasource-mapping as
PostgreSQL
3. see that postgres-ds.xml is in your hot deployment directory
