Well the trick is that jboss2.0 uses the same invocation stuff than jboss1.0
we have seen jboss1.0 cruising at great speeds (as/more fast than WL in
certain cases) so we know it is not the proxies that are slow... something
else I think, we need to find it, but it is probably trivial.
marc
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, July 05, 2000 12:10 PM
To: jBoss Developer
Subject: RE: [jBoss-Dev] EJBoss Question
That depends on how much Jboss is borrowing from eJBoss....
John
"marc fleury" <[EMAIL PROTECTED]>
Sent by: <[EMAIL PROTECTED]>
07/05/00 01:56 PM
Please respond to "jBoss Developer"
To: "jBoss Developer" <[EMAIL PROTECTED]>
cc:
Subject: RE: [jBoss-Dev] EJBoss Question
interesting... we are going to drill that kind of problem with the
performance team.
It looks the performance team will be the critical one :) they have some
work on their plate.
Please feed that, as much information as you can, in bugzilla (perf) and add
yourself to the list, we will move forward on that.
regards
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
> Sent: Monday, July 03, 2000 4:26 PM
> To: [EMAIL PROTECTED]
> Subject: [jBoss-Dev] EJBoss Question
>
>
> We have an application with one entity bean, 2 stateless sessions and 1
> stateful session bean. Works great. Except when users perform actions that
> create more instances of entity beans and perform actions that remove the
> remote references: The thread count grows with every action on the server
> almost.
>
> Is there any known issue with ejBoss and threads?
>
> John
>
>
>
