Recovering the failed server to the Cluser !!!!!!!!!!!!!!!!!!! BROKEN PIPE

Question

Hi,
          I have a weblogic cluster with 2 managed servers on 2 different machines,
          Now i have an application.ear which is kept on the first server and while deploying i choose the option "copy to the other server" and i deploy this EAR to the cluster.
          Mine is a applet-servlet based application and the applet gets downloaded onto client browser.
          Now when both the servers are up load balancing and the failover is also happening.Now the problem is when rejoing the failed server back to the cluster.
          I have setup the classpath entries and arguments entries "Remote Start" tab in the server configuration,
          I bring back the server through weblogic console and it joins the cluster also without any problem.
          The problem is if some users have already opened the application then after rejoining also it works fine.
          But if a new user tries to access the applications what happens is
          we get
          java.net.SocketException: Broken pipe
          at java.net.SocketOutputStream.socketWrite0(Native Method)
          at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
          at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
          at weblogic.servlet.internal.ChunkUtils.writeChunkTransfer(ChunkUtils.java:267)
          at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:239)
          at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:311)
          at weblogic.servlet.internal.ChunkOutput.checkForFlush(ChunkOutput.java:387)
          at weblogic.servlet.internal.ChunkOutput.write(ChunkOutput.java:254)
          at weblogic.servlet.internal.ChunkOutputWrapper.write(ChunkOutputWrapper.java:125)
          at weblogic.servlet.internal.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:184)
          at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1639)
          at java.io.ObjectOutputStream$BlockDataOutputStream.write(ObjectOutputStream.java:1603)
          at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1325)
          at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
          at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
          at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
          at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1224)
          at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1050)
          at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1224)
          at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1050)
          at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
          at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
          at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
          at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
          at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
          at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
          at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
          at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
          at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
          at WebRequestController.doPost(WebRequestController.java:184)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
          at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
          We use IPlanet proxy server to route to the cluster
          Somebody pls help..
          Regards
          Suresh

Answer 1

Davin Czukoski wrote:
We have been switching back and forth between the BEA MS SQL server driver
and the Data Direct driver ever since the SP3 problem started.
This seems to be a problem with the BEA MS SQL server driver. We switch to
Data Direct and the problem went away.
There were no memory messages in our logs for SQL server.Ok. And this only happens during a big sequence of inserts? Let me see your code,
and please describe the table too. I'll try to duplicate it, but if the data direct driver
or the free MS driver works for you, go with them.
Joe
>
>
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]..
Davin Czukoski wrote:
I am getting this error part way through an 1000 row update.
Exception: I/O exception while talking to the server,
java.io.IOException:
Broken pipe
Is it a driver or network issue?Probably neither. I'm guessing the DBMS ran out of memory for theinsert-logging
or something like that, and killed the client connection. Check your DBMSlog.
Joe Weinstein at BEA