Hi Adrian,
thanks a lot for your reply!
An interesting fact to notice is that the problem occurs without any
modification of JBoss configuration and without anyone deploying anything.
1. JBoss startup -> no exceptions (I assume the jndi context is correctly
configured then)
2. JBoss is just ru
we are using JBoss (build: CVSTag=JBoss_3_2_1 date=200305041533) on over 60
servers at a customer site.
OS is Linux 2.4.19-4GB, Java VM 1.4.1_02-b06
After JBoss startup the JNDI tree contains the following bindings, whereas
after a certain time the same JNDI tree does no longer contain them (lis