Java Web Service Internal Server Error 500

[forum@java]

Hi All,

I have developed a web service client in eclipse using Axis1.
The web service is hosted on Seibel server and we have moved to production.
But occassionally, we get an error - "Internal Server Error 500" with no Seibel Code.
Can anyone help me in figuring out what may be the cause?

[travishein]

is there no servlet container log file in the Sieble system?

One random theory (I'm brain storming here), it might be possible, if in the [integrated servlet container (e.g. tomcat?) inside siebel, in that application, if it uses a JDBC connection to a data source within siebel, and that JDBC connection would close after so many hours of inactivity, so the connection pool contains one or more stale JDBC Connections. This causes the first couple of people to hit our web application after the weekend, usually monday morning is long enough and they observe an error message. But it starts working again for the next person, or even if the first user reloads their page. Now we don't have Siebel, just plain tomcat. and that kind of "a resource in use and open connection handle in a pool but goes stale or self-closes after some amount of inactivity" thing was difficult to track down; we eventually fixed it with a JDBC validation query in the commons-dbcp configuration.

[forum@java]

is there no servlet container log file in the Sieble system?

One random theory (I'm brain storming here), it might be possible, if in the [integrated servlet container (e.g. tomcat?) inside siebel, in that application, if it uses a JDBC connection to a data source within siebel, and that JDBC connection would close after so many hours of inactivity, so the connection pool contains one or more stale JDBC Connections. This causes the first couple of people to hit our web application after the weekend, usually monday morning is long enough and they observe an error message. But it starts working again for the next person, or even if the first user reloads their page. Now we don't have Siebel, just plain tomcat. and that kind of "a resource in use and open connection handle in a pool but goes stale or self-closes after some amount of inactivity" thing was difficult to track down; we eventually fixed it with a JDBC validation query in the commons-dbcp configuration.

Thanks for the reply.
Having no knowledge of Seibel, what I understand is that there may be a JDBC connection timeout happening in the integrated tomcat container. This is what I would be telling to my Seibel team mate.
Now, how can I suggest him to fix it?
Should I tell him?
"Add a JDBC validation query in the commons-dbcp configuration, i mean where the connection is made"

Thanks a lot. Will investigate if this is the real issue.