|> Please help!!
|> I have been spending a lot of time on this, and I do
|> not mind spending a lot more time if needed to get
|> this fixed.
|> But I simply do not know what to do about it!
|
|Did you already try to take jbosstest sources (client and bean+interfaces)
|jarring them from scrap and add the needed jars one by one, trying to add
|them in the manifest or leaving the manifest empty and adding them
|to normal
|classpath ?
|I'll try writing a plain bean and see if there are problems also, but it
|seems to me something very tight coupled with jbosstest module...
|
Ok we are seeing the same thing with Sebastien on a "localhost" lookup so it
is probably not a DNS problem but a classloader problem and probably linked
to the deployer then...
Rickard can you take a look at it?
We are going to track the lock problems with the cache Simone. Simone the
reason we didn't see it before is because it was either few beans with many
threads (so locking but no passivation), or many beans but 1 thread per bean
(so passivation but no locking). The benchmark we run now is
passivation+locking and there are problems there. So to do the test
removing passivation is one option, getting it to work is a better option
;-) we will do that ASAP
marc
|Good luck (to both) !
|
|Simon
|
|
