Hello Chris,
Siebel Team made some changes on their side, and we are able to see the "timed
out error" on Siebel logs when Siebel is posting data to Tomcat.
The flow is: Siebel post data to Servlet --> Servlet processes the data..
We observe that Siebel application waits for 2 minutes and then gets a timeout
while posting data to Tomcat. The request never reaches Tomcat (as seen from
the localhost log files). If Siebel sends 50 transactions, then only 30-40
reaches Tomcat Servlet.
At a later point of time, if the Siebel is trying again, then the data is
getting posted successfully.
<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="60000"/>
Timeout at Servlet level is defined as
int requestTimeout = 180000;
We are trying to figure out whether the problem is at Tomcat side or Siebel
side or in between. The ping from Siebel to Tomcat server is fine, so we think
that network is fine. Also the network team informed that the packets are not
getting lost.
There are more than 20 servlets deployed in the tomcat and there are around
10-12 requests (for all the servlets) coming to Tomcat in a minute.
I even increased the maxProcessors from 75 to 150 and acceptCount from 10 to
20, but the behavior doesn't change.
The architecture of Siebel is that it posts all the request at one point of
time - ie at one instance.
Please do inform if anybody has seen such behavior and how they resolved the
problem. How do I find out that this is not a Tomcat issue.
Thanks
Mrinmoy
-----Original Message-----
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 26, 2007 2:31 PM
To: Tomcat Users List
Subject: Re: IMP - Requests not reaching Tomcat Server
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mrimony,
Mrinmoy Pal wrote:
> Problem - Some of the requests not reaching Tomcat server from Siebel
> Application.
Sounds like this isn't a Tomcat problem. If Tomcat isn't getting the
request, it certainly can't fail!
> Siebel is posting the message to Tomcat Server via the url -
> http://xyz.ddns.slb.atosorigin-asp.com:8080/servlet/siebelLicenseOrder
> <http://xyz.ddns.slb.atosorigin-asp.com:8080/servlet/siebelLicenseOrder> .
> SiebelLicenseOrder is a servlet hosted on Tomcat Server.
>
> Siebel is getting the following error while posting to eGate servelet
> [Wed Sep 26 18:52:53 2007] *** ERROR [@ 0]: PosttoEGate() 201009 - Error
> while posting XML message to
> "http://xyz.ddns.slb.atosorigin-asp.com:8080/servlet/siebelLicenseOrder
> <http://xyz.ddns.slb.atosorigin-asp.com:8080/servlet/siebelLicenseOrder> "
> Exception: "201007 - Invalid Parameter [httpResponse]!"
I would try to find out what that error meant to Siebel. It's clearly
interfering with its ability to send the XML message to Tomcat. The
"invalid parameter" (httpResponse) is unlikely to have come from Tomcat
since Tomcat never handled the request.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG+rOL9CaO5/Lv0PARAl++AJ9Glahb9VkC+a9SZgXGGLWTU57UAQCeIHsa
rgknjCBkOOulUew1wsW8xXs=
=WM8o
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
