Tomcat3.2.3+Jboss2.4.1 on SuSE Linux 7.2, jdk1.3.1_01 against PostgreSQL 7.0/Hypersonic
I am finding my cmp entity bean is not flushing its state back to the db when shutting down JBoss. It looks as though JBoss doesn't hang around long enough - it just goes down like a ton of bricks when you click on that shutdown button in the port 8082 shutdown interface.
Can anyone confirm whether this is a bug? I know I'm using a slightly older version of jboss+tomcat but I couldn't find any reference to shutdowns in the change logs nor any relative posts in the forum.
When I redeploy on-the-fly (very nice feature, guys!), my servlet which contains the state is reloaded, which is fine. Before the old instance goes down I flush the state from the servlet to the cmp entity bean and it updates the db as expected.
The following is what is generated in the space of less than 3 seconds from the time I click on shutdown:
[Default] Shutting down
[Service Control] Stopping 51 MBeans
[MailService] Mail service 'Mail' removed from JNDI
[MinervaXACMFactory] Connection manager factory 'MinervaXACMFactory' removed from JNDI
[MinervaSharedLocalCMFactory] Connection manager factory 'MinervaSharedLocalCMFactory' removed from JNDI
[MinervaNoTransCMFactory] Connection manager factory 'MinervaNoTransCMFactory' removed from JNDI
[J2EE Deployer Default] Undeploying all applications.
Any advice/help/confirmation on this is much appreciated.