Results 1 to 3 of 3
  1. #1
    forum@java is offline Member
    Join Date
    Sep 2010
    Posts
    2
    Rep Power
    0

    Exclamation Java Web Service Internal Server Error 500

    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?

  2. #2
    travishein's Avatar
    travishein is offline Senior Member
    Join Date
    Sep 2009
    Location
    Canada
    Posts
    684
    Rep Power
    5

    Default

    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.

  3. #3
    forum@java is offline Member
    Join Date
    Sep 2010
    Posts
    2
    Rep Power
    0

    Smile Hi travishein!

    Quote Originally Posted by travishein View Post
    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.

Similar Threads

  1. Replies: 6
    Last Post: 04-12-2010, 07:07 PM
  2. Replies: 1
    Last Post: 12-05-2009, 07:28 AM
  3. The server encountered an internal error ()
    By rakesh_n_mehta in forum Web Frameworks
    Replies: 0
    Last Post: 01-19-2009, 01:09 PM
  4. an internal error occurred during refresh
    By christina in forum Eclipse
    Replies: 1
    Last Post: 08-06-2007, 09:37 PM
  5. Description the server encountered an internal error
    By Jack in forum Enterprise JavaBeans (EJB)
    Replies: 2
    Last Post: 07-02-2007, 02:24 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •