I could reproduce it again sometimes.
Yesterday afternoon I restarted the Glassfish and started the test. The log output looked like this:
[#|2009-06-17T16:38:36.865+0200|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=p: thread-pool-1; w: 6;|instance = testing.ejbeans.testmultipleejbs.TestMDB_at_19b5a0b - someEnv = anotherString|#]
[#|2009-06-17T16:38:36.869+0200|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=15;_ThreadName=p: thread-pool-1; w: 5;|
instance = testing.ejbeans.testmultipleejbs.TestMDB_at_19b5a0b - someEnv = aString|#]
[#|2009-06-17T16:38:36.959+0200|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=p: thread-pool-1; w: 6;|
instance = testing.ejbeans.testmultipleejbs.TestMDB_at_19b5a0b - someEnv = anotherString - message = this is another test|#]
[#|2009-06-17T16:38:36.959+0200|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=15;_ThreadName=p: thread-pool-1; w: 5;|
instance = testing.ejbeans.testmultipleejbs.TestMDB_at_19b5a0b - someEnv = aString - message = this is a test|#]
I.e. there was only one bean. I started the test again this morning without re-deploying or restarting the GF and now it worked fine:
[#|2009-06-18T08:26:52.285+0200|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=p: thread-pool-1; w: 103;|
instance = testing.ejbeans.testmultipleejbs.TestMDB_at_14bee1 - someEnv = aString|#]
[#|2009-06-18T08:26:52.288+0200|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=p: thread-pool-1; w: 103;|
instance = testing.ejbeans.testmultipleejbs.TestMDB_at_14bee1 - someEnv = aString - message = this is a test|#]
[#|2009-06-18T08:26:52.479+0200|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=p: thread-pool-1; w: 103;|
instance = testing.ejbeans.testmultipleejbs.TestMDB_at_3034cc - someEnv = anotherString|#]
[#|2009-06-18T08:26:52.479+0200|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=p: thread-pool-1; w: 103;|
instance = testing.ejbeans.testmultipleejbs.TestMDB_at_3034cc - someEnv = anotherString - message = this is another test|#]
The generated XML did not change from the deployment yesterday until this morning. Moreover, the XML file does not have any differences to an XML file from a deployment that worked at once. Except the unique-id in the generated sun-ejb-jar.xml. So I suspect that I maybe need some other log or debug output that might help to analyse the issue. Do you have any suggestions what else I could do and which other information would be helpful for the bug report?
Thanks,
Chris.
[Message sent by forum member 'chrjohn' (chrjohn)]
http://forums.java.net/jive/thread.jspa?messageID=351756