Web Enterprise and IIS 3.0

Question

We are currently experiencing a problem with Web Enterprise and IIS 3.0.
When a request is entered through a web site to our Web Enterprise back end,
using either fortecgi.exe or forteisapi.dll, the first request comes almost
straight through to the back end - this is seen by looking at the log file.
However, subsequent requests from the same browser session (IE or NS) take
consistently about 45 seconds to come through to the back end. If a new
browser session is started up, on the same PC, whilst waiting for the other
one to come through, a new request will once again go straight through
before the one that is waiting does.
This only happens on two external web servers - the internal ones don't do
it. I have compared setups of IIS on the internal and external web servers
without discovering what the cause could be. Monitoring the external web
server shows that for the initial request from a new browser session,
fortecgi.exe starts up and shuts down very quickly, but for subsequent
requests hangs around until the log file at the back end shows it has
received the request.
Any help would be greatly appreciated.
Steve Isaac
Senior Consultant
Xpedior
Tel: [phone]
Fax: [phone]
Eml: Steve.IsaacXpedior.com
Web: http://www.xpedior.com

Answer 1

Hello Frank,
look out, it's likely that you are using a default JNDI name, so the name of the ear it's part of the JNDI name.
If the application is deployed in a EAR file, the default JNDI name is the EAR-FILE-BASE-NAME/EJB-CLASS-NAME/local for the stub for local interface. For the remote interface (see below), it is EAR-FILE-BASE-NAME/EJB-CLASS-NAME/remote.
If the bean is deployed in a JAR file, the JNDI names are EJB-CLASS-NAME/local and EJB-CLASS-NAME/remote.
Regards
Mark
[Master the Boss - a Jboss magazine|http://www.mastertheboss.com]
Edited by: mark1970_mtb on Sep 2, 2008 3:26 AM