• Post Reply Bookmark Topic Watch Topic
  • New Topic

Broken pipe exception  RSS feed

 
blr sam
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
We are using JSP to call Session beans which in turn call DB. While development we did not find
any erros and whole application was working fine.
While testing we find that almost all Bean
calls return this exception "java.io.IOException: Broken pipe".
Is this a network problem between the App Server and the DB server? If so, what parameters i have to set?
Many thx
Sham
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There is NO possible way we can help you unless you tell us at the very least what application server and database server you are using. Also, it would be VERY helpful if you posted the entire stack trace of the exception and not just a summary of it. Think about it -- you can't debug without information...
Kyle
 
Naveen Sydney
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi shyam,
a broken pipe error could happen do to various reasons. But since u say that all the session beans that talk to the database get the same error i would see
1)the communication between the appserver and dbserver
2)stack trace to pinpoint the exact origin of error
3)if u use a database pool see if the connection has been estabilished.
regards
syd
 
blr sam
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mr Bartender,
I'm sorry.
Here it is:
java.io.IOException: Broken pipe
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
at weblogic.servlet.internal.ChunkUtils.writeHeaderChunk(ChunkUtils.java:151)
at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:345)
at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:718)
at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:130)
at weblogic.servlet.internal.ServletResponseImpl.sendRedirect(ServletResponseImpl.java:458)
at jsp_servlet.3T._Process._jspService(_Process.java:343)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:246)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

The above exception has occurred between the Appserver and the Webserver.
The configuration is as follows:
Solaris 5.8 running Weblogic 6.0 Service pack 2.0
Database Oracle 8.1.7
The Weblogic is being used as a webserver as well as a Appserver on the Solaris system & Database is running on another Solaris system.
i hope this will help. I would really appreciate if a solution can be found for this
Cheers,
Sham
 
Meghana Reddy
Ranch Hand
Posts: 76
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi sam/kyle..........!!!---URGENT---!!!
cd yu pls let me know if u found any soln for the above, i exactly get the same error. in fact i get this problem when i log in to my system(not application) with different users(login profiles in win2k system) ...for some logins i dont get this error hwevr i get this for some users ....cd u pls let me know wht is causing this error and hw to avoid this since this error is causing the application to stop.
i guess this problem might be due to the insufficient privileges for some users....and they are not able to connect(not enough connections, say) to the database. i am not sure of this...should anybody had come across this error ???
 
sabuj paul
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hey , once i also the same error.. its sometime happen because of communication failure with DB.So check ur DB schemas and the connection..
 
jinhao he
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Solution:
During developpment of last project, we have invited sun and oracle experts to help us solving this problem. Finally, they give us an answer that this problem probably is a oracle bug and we need to wait for orable's patch.
According to my experience:
While developping application with oracle database, this problem will come. However, i never meet it if i choose other database vendors(eg SQL server+merant,DB2 and sybase).
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!