I have a j2ee client app that talks to the database via jboss and ojb. This app works fine when there is only one client talking to jboss at a time. It even works fine when I create several pseudo-clients in the same app running separate connections in their own threads (similar to the ojb ejb stress tests). However when I run this test with two separate client machines, each writing to completely different sets of objects, things silently hang in jBoss, and I cannot make any further remote calls. Note that there should not be a problem of simultaneous access to the same persistent object. I need to restart jBoss to be up again.
I realize that I am only giving a general description of the problem, and I intend to investigate further so that I have (hopefully) some stack traces instead of silent death. But first a few pointers to help me in my investigation would be very welcome.
First my setup is the following: WinNT - jBoss 3.0.6 - ojb1.0rc2 - Oracle 8.1.6
I've held off moving up to rc3/4 due to the myriad of sequence problems that I and numerous other Oracle users experienced with rc3. I'm willing to roll up my sleeves and move to rc4 if required (is it possible that this is a bug that has been address recently -- I don't see any bug reports quite like this). Hopefully the sequence problems have been addressed by now?
This is the last leg of a long journey to go into production with ojb and add another "success story" to the list.
Thanks,
Phil
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
