change the start() thingy to a real thread pool that takes the invocations
from teh clients (instead of starting a new server each time, should help
you ;-).
Norbert Lataille worked with Nicholas Pioch (the original Apache designer)
on a proxy http and pools of thingies to take invocations and stuff. He can
help.
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> Sent: Friday, June 02, 2000 4:03 AM
> To: jBoss Developer
> Subject: RE: [jBoss-Dev] RMI call latency to naming server=excessive
>
>
> yo.
>
> in org.jnp.server.Main.java
>
> how about doing the listen() once you have done the answer to the
> client (in
> run())
> your listen() does a heavy start() Unicast Export and creation and whatnot
> before
>
> give it a try
>
> marc
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
> > Sent: Friday, June 02, 2000 3:54 AM
> > To: jBoss Developer
> > Subject: Re: [jBoss-Dev] RMI call latency to naming server=excessive
> >
> >
> > Hey
> >
> > Juha-P Lindfors wrote:
> > > > Does anyone have any clue where to start looking?
> > >
> > > Windows protocol stack and network settings.. ?
> >
> > Yeah, but shouldn't that affect the jBoss calls as well??? Because
> > they're superfast... I can't figure out what the difference is between
> > the JNP server and the jBoss EJB server.... argh..
> >
> > /R
> >
> > --
> > Rickard �berg
> >
> > @home: +46 13 177937
> > Email: [EMAIL PROTECTED]
> > http://www.telkel.com
> > http://www.jboss.org
> > http://www.dreambean.com
> >
> >
>
>
>
