The blocking timeout is just how long the DataSource.getConnection() waits when all database connections are in use.
What does the this mean? anonymous wrote : | If the the database connection is away for longer than the configured datasource blocking-timeout for JMS, JBoss doesn't come back. | I don't see the relevence to database failover. If JBossMQ cannot get a JDBC connection it will propogate the exception to the client. Either by: 1) Cannot send message - in this case the message was never sent and the client knows this 2) Cannot acknowledge message - in this case the message was never received the message is not lost because only a successful acknowledge deletes the message it will be redelivered If you are seeing something else show me the logging (READ THIS FIRST) and describe the behaviour. I am usually not very tolerant of posts like this that say "IT DOES NOT WORK". What it usually means is the poster "DOES NOT KNOW HOW IT IS SUPPOSED TO WORK". But in this case I sniff a bug report if I correctly understand your "JBoss doesn't come back". Although what this "JBoss" is that doesn't come back I can only guess? Where did this "JBoss" go in the first place? Do you mean the MDB, the JMS server, the sender, the database connection or what? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865623#3865623 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865623 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
