• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Socket Exception, Applet Servlet Comm.. Very Urgent!

 
Ugly Redneck
Posts: 1006
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear All,
I have an application that performs applet servlet communication with IBM Websphere 3.5 Advanced Edition. The entire application is an n-tier application and it works fine in almost all cases. But in one particular case, where the database(Oracle) takes 9 minutes to complete its operation (due to the sheer volume of data) I recieve a java.net.SocketException from the applet side with the message that "end of file" appended to the exception. I am using a URLConnection to communicate to and from the servlet. The communication from the applet to the servlet is fine, but after the middleware and backend have completed their operations, when the servlet tries to convey back the result to the applet the error appears. I have increased the Transaction time out to 2000, tried fiddling around with all other settings, but nothing seems to help. I examined the JDK source code and it states that if the HTTP header is corrupted then the exception with the above error message is thrown, so from the looks of it, I guess the HTTP Header does not exist on the way back from the servlet to the applet, is this due to the excessive time being taken by the middleware and backend?? If anyone knows the solution to this, please reply immediately.. this is very urgent!
Thanks in advance
Regards
Sriraj Rajaram
 
Paul McKenna
Ugly Redneck
Posts: 1006
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi..
To those of you, who are facing a similar problem I have been able to solve the issue. The solution is 2 step
1. Increase the transaction idle timeout in Websphere Administrative console. By default it is 60000 milliseconds. Once a transaction idle timeout is reached, Websphere tries to validate the status of the transaction and/or fires another transaction. This might be the reason why sometimes we see 2 transactions
2. If you are using Oracle, ask the DBA to Reanalyze and Reindex the tables. This increased my performance heavily.
Also finally, if you are inserting large amounts of data into a table use Bulk insert in Oracle, this increases performance by 400%
Thanks
Sriraj Rajaram
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic