JBOSS hot-deployment problem/bug ?!

[tom_ck]

Hi;

I'm using JBOSS 2.4, Tomcate 3.2.3,MySql 3.23.42 (with BDB for transaction-safe supoprt), Jdk1.3.1, and mm.mysql.jdbc 1.2 driver. all installed on a Linux box.

I'm able to deply (hot-deploy) my (BMP) entity bean and access it (via a servlet) just fine with no problems. However, when I attempt to perform hot-deployment (for my entity bean)at the same time there are active bean instances (of the same entity bean being hot-deployed), belonging to to multi-threaded client http-servlet based requests, that are accessing (i.e. performing SQL updates), or trying to access the database; all those beans active instances through expections.

Every time I re-attempt the test, I get a different exception raised from the bean. The exception I've seen so far are:
- EJBException
- IllegalStateException
- RemoteException
- TransactionRolledBackException
- MarshalException: invalid remote object
- UndeclaredThrowableException

Initially I thuoght that it was a MySql, or an mm jdbc driver problem. However, MySql (or even the mm jdbc driver)has no problems handling parallel db transactions in any shape. Only when HotDeploy is done for the same (BMP) entity bean type that at the same time is beeing used by clients, creates/raises exceptions and causes all db transactions that are taking place at that same hot-deployment time to fail.

Did I stumple upon a JBOSS bug?... Have someone else encountered this problem?

Any help/clues will be greatly appreciated.

Tom

PS: Apologies if I'm posting to the wrong Forum

[geetha]

I am a newbie to JBoss .I am getting TransactionRollBackException.how to rectify this ?.I am not to locate exactly why this exception arise.if anyone knows pls help me out.

[davidjencks]

Tom-ck, hot deployment is a convenience for developers, it is not intended to allow you to seamlessly upgrade your production app while it is running. We've talked a little bit about how that might be possible, but no implementation is on the horizon at this time. There are a lot of difficulties to be solved before this is plausible (such as making the jmx agent transactional so all redeployments become visible at the same time)

Transaction-rollback-exception, this is not enough info. Look at the server log until you find out what is going wrong, then ask with this info if the problem is not obvious.