Andrew
It *sounds* like you are battling a network latency problem
Can you identify the target RMI server then do a simple tracert from client to
RMI Server to determine which intermediate node is causing the delay?
Martin
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Subject: RE: Speeding up RMI calls
> Date: Fri, 27 Jul 2012 17:31:17 -0400
> From: akuj...@evertz.com
> To: users@tomcat.apache.org
>
> > > On 09/07/2012 16:55, Andrew Kujtan wrote:
> > > > Tomcat Version: 7.0.27
> > > >
> > > > OS: Windows XP/7
> > > > I'm fixing an issue we are having with a webapp that does some
> > > > communication over RMI with a remote server. Calls that would be
> > > > instant in similar applications not inside the tomcat container
> are
> > > > taking more than 30 seconds when called from tomcat. After
> > debugging
> > > > I've found that when an RMI call is made, the classlist
> containing
> > > > all the jars in the webapp lib folders is being serialized with
> the
> > > data.
> > > > Which wouldn't be a problem normally, except the webapp has >300
> > jars
> > > > in its lib folder.
> > >
> > > In the other similar applications, are there 300+ jars on the
> > classpath
> > > too?
> > >
> > >
> > > p
> >
> > Yes they are there as well, but the RMI calls don't include them, or
> > any
> > urls
> > for that matter.
> >
> > >
> > > > The only solution I have found is to create a custom
> > > WebAppClassloader
> > > > that returns a zero length URL array on the getURLs() call. We
> > don't
> > > > do any dynamic class loading so breaking that is not a problem.
> > > >
> > > > My question is, is there any other way to resolve this, like a
> > > > configuration property? If not, are there any problems that I am
> > > going
> > > > to introduce by overriding this method? Can I override the
> > > classloader
> > > > for just this webapp or am I stuck doing it for the entire tomcat
> > > > instance?
> > > >
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Andrew Kujtan
>
> I guess no one has run into this issue before, I've pushed it through
> and am just overloading the classloader in the server.xml
>
> Hopefully this doesn't break anything.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
