Tomcat exception of broken pipes

I got the exeption continueously as below. how to get rid of it? thanks
2005-3-29 14:46:05 org.apache.jk.server.JkCoyoteHandler action
: Error in action code
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 org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:457)
     at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:654)
     at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:435)
     at org.apache.coyote.Response.action(Response.java:226)
     at org.apache.coyote.Response.finish(Response.java:348)
     at org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:328)
     at org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(CoyoteResponse.java:497)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:213)
     at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309)
     at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387)
     at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673)
     at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615)
     at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:677)
     at java.lang.Thread.run(Thread.java:536)
http://blog.csdn.net/zwwwxy/

What do you mean by continuously?
Usually, this kind of exception is thrown once in a while as the pipe, one end of which is your server and the other end is the client, is broken. It might be caused by client closing the connection prematurely or it might be an artifact of transient network condition. Or something else. In many cases, you can do nothing about it. If there is no real problem you can associate to this SockeException, you may safely ignore them.

Similar Messages

  • IO Exception Broken Pipe ORA-17002 while using connection pooling

    Hi
    We are experiencing "broken pipe ORA-17002 error" when using connection pooling. This seems to be a common error when implementing connection pooling, but I didn't find any solution anywhere.
    we are using Oracle 9i 9.2.0.1 JDBC thin driver
    Our database is Oracle 8.1.7 running on HP Unix
    The middle tier(Tomcat) runs on RedHat linux server
    We are using JDK1.3
    It seems the connections automatically get stale or bad after certain period of time.Iam checking to see if the connection is closed, before giving the connection from the pool to the appilcation.It seems its still open.But when I start using the connection to open a callable statement or setAutocommit to false, it says Broken pipe or No more data to read from the socket.
    We are implementing our own connection pooling class(we experimented with OracleConnectionCacheImpl but it too gave the same errors).
    Does anybody have a solution for this problem??
    Is there a workaround for this?I would like to know how connection pooling is implemented in most of the applications that use oracle database?Or do we need to explicitly test the connection before using it, and reopen a connection if that is bad??
    Thanks
    Anil

    kalle
    Thank you very much for your advice!!!
    Like you said, I started to check whether the connections are fine before giving them from the pool.I am executing a simple "select 'anil' from dual" and if its fine only then I return the connection. So far it seems to be fine. Also I am reopening the connections(closing the old ones and opening new connections) after every 12 hours.
    As far as the JDBC driver is concerned, I already tried with Oracle 8i driver, it gave the same problems. I read that 9i driver might solve this problem, so I changed to the latest 9i driver (classes12_g.zip).
    Sometimes before(before I started checking whether the connection is good )the application used to hang up at the point where I am issuing setAutoCommit(false).It never comes out from that statement.Is this something to do with theconnections being closed?
    What I am afraid is, will the appilation get hung up even after I check the connection with select query and then issue autocommit(false)??
    Or will it hang up while I check with a select query??
    As long as it doesn't hung up, I am fine. Because i am cathching the exceptions.
    Thanks In ADVANCE
    Anil

  • Jsf web application has to be restarted everytime a broken pipe exception

    Hi,
    My jsf web application using tomcat is experiencing a sql exception "java.sql.SQLException: System or internal error java.net.SocketException: Broken pipe" when it tries to connect to database.
    Everytime this exception happens I have to restart the application and the application runs fine then.
    Is there a way to handle this exception that we don't have to restart the application.
    -kap

    It depends....
    How do you have (where) the connection, how you obtain them, etc?

  • Exception writing binary data to the output stream to client -Broken pipe

    Hi,
    I am trying to use the drag & drop feature using Contributor mode of Webcenter sites. Single Image Page Attribute is working properly where as Multiple Image Page Attribute throws the following error:
    [ERROR] [.kernel.Default (self-tuning)'] [logging.cs.satellite.request] Exception writing binary data to the output stream to client 10.191.117.106
    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.ChunkOutput.writeChunkTransfer(ChunkOutput.java:568)
         at weblogic.servlet.internal.ChunkOutput.writeChunks(ChunkOutput.java:539)
         at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:427)
         at weblogic.servlet.internal.ChunkOutput$2.checkForFlush(ChunkOutput.java:648)
         at weblogic.servlet.internal.ChunkOutput.write(ChunkOutput.java:333)
         at weblogic.servlet.internal.ChunkOutputWrapper.write(ChunkOutputWrapper.java:148)
         at weblogic.servlet.internal.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:148)
         at COM.FutureTense.Servlet.ServletRequest$OutputOutputStream.write(ServletRequest.java:80)
         at COM.FutureTense.Servlet.ServletRequest.write(ServletRequest.java:1633)
         at com.openmarket.Satellite.RequestContext.write(RequestContext.java:1123)
         at com.openmarket.Satellite.BytePiece.stream(DataPiece.java:253)
         at com.openmarket.Satellite.CacheObjectImpl.stream(CacheObjectImpl.java:651)
         at com.openmarket.Satellite.Http11Responder.respondForWrapper(Http11Responder.java:142)
         at com.openmarket.Satellite.WrapperAwareResponder.respond(WrapperAwareResponder.java:36)
         at com.openmarket.Satellite.SatelliteServer.execute(SatelliteServer.java:85)
         at com.openmarket.Satellite.servlet.BaseServlet.doGet(BaseServlet.java:118)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at com.fatwire.wem.sso.cas.filter.CASFilter.doFilter(CASFilter.java:557)
         at com.fatwire.wem.sso.SSOFilter.doFilter(SSOFilter.java:51)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Thanks
    KarthiK

    Thank u very much,
         FileOutputStream opGif = new FileOutputStream(destFile, false);
    I have changed above line with the following line:
         PrintWriter opGif = new PrintWriter ( new FileWriter(destFile, false));
    and now this code is working very fine.
    Thanks once again...

  • Web Service Error: java.sql.SQLException: Io exception: Broken pipe

    Hi,
    I am using JDeveloper PL/SQL web service generator. After some time we start receiving the "java.sql.SQLException: Io exception: Broken pipe" exception when we invoke the web service. I've noticed that the error starts occuring once all the connections in the database have been closed.
    Here are the Data Source configurations I tried using:
    <data-source name="jdev-connection-SACS" class="com.evermind.sql.DriverManagerDataSource" location="jdbc/SACSCoreDS" xa-location="jdbc/xa/SACSXADS" ejb-location="jdbc/SACSDS" pooled-location="jdbc/MACSPooledDS" connection-driver="oracle.jdbc.driver.OracleDriver" username="xxx" password="xxxx" url="jdbc:oracle:thin:@test:1521:SACS" inactivity-timeout="30" connection-retry-interval="3" max-connections="5" min-connections="0" wait-timeout="20"/>
    AND I also tried:
    <data-source name="jdev-connection-SACS" class="com.evermind.sql.DriverManagerDataSource" location="jdbc/SACSCoreDS" xa-location="jdbc/xa/SACSXADS" ejb-location="jdbc/SACSDS" pooled-location="jdbc/SACSPooledDS" connection-driver="oracle.jdbc.driver.OracleDriver" username="xxxx" password="xxxx" url="jdbc:oracle:thin:@xxxx:1521:SACS" inactivity-timeout="30"/>
    That did not make any changes.
    I then changed ConnectionContext.KEEP_CONNECTION to ConnectionContext.CLOSE_CONNECTION in the <name>Base.sqlj:
    public void release() throws SQLException
    { if (__tx!=null && __onn!=null) __tx.close(ConnectionContext.CLOSE_CONNECTION);
    __onn = null; __tx = null;
    That did not help either. We are running these web services on the standalone OC4J and Oracle 8.1.7.2 database with the MTS installed on it.

    Hi,
    I don't use JDeveloper to develop stored procedure web services. However, I do use WebServicesAssembler.jar to generate stored procedure web services.
    I had the same problem as you did. After some research in this forum, I was informed that it's a bug in the web services generator itself. I was also informed that the newest version of WebServicesAssembler.jar is supposed to fix the problem.
    If you want, you can always write a batch job to restart the OC4J periodically. The command is
    dcmctl -ct oc4j -co home
    If I come across the posting containing the answer to your solution, I will forward it to you.
    Good luck
    Jack

  • Broken Pipe/Connection Reset By Peer IO Exceptions

    Can someone explain what causes a connection reset by peer exception vs.
              a Broken Pipe IO exception? I realize they are generally caused by
              someone hitting stop, closing their browser, hitting a different link,
              etc.. but I was trying to understand what might cause a connection
              reset by peer exception vs. a broken pipe exception. I've added code to
              my servlet to suppress the "Connection Reset By Peer" socket exceptions
              but I'm wondering if I should do the same with Broken Pipe. Also, are
              there are other types of similar exceptions that can occur when users
              get impatient.. Thanks
              Kirk
              

    I do not have an idea about your application server but i do know how i solved it in weblogic. Just see whether this is helpful to you.
    Points to be sure of........
    1) Make sure that when ever you request a connection from a pool, after you are done with it return it. If you are not returning it and trying to use that reference again, this problem will occur.
    2) Look at the capabilities of your app server. Set the connection pool such that
    a) All the connections are checked at regular interval with some default select statement from any table in the database.
    b) Connections are check when the connection is checked out and returned to the pool.
    I the connection object is not ready , close it and create a new one. The app server which manages the pool should implement these feature so that when you get the connection - its the tested and working object.
    If your app server does not support - then think of ways you testing it before you using it(Anyway this is not the good solution).

  • Too many broken pipe exceptions

              I understand this broken pipe exceptions are caused when the
              user clicks stop on the browser. However, it seems as if clicking
              stop once results in dozens of broken pipe exceptions cropping
              up in the weblogic.log file. This is causing our log files to grow
              at enormous rates taking up too much hard disk space.
              Is BEA going to come up with a service pack soon to trim these
              exceptions off?
              

    is this normal?Not really no.
    You might want to look at where those exceptions are happening and then you can figure out why.
    Under enough load stress you can break about anything but the load you can put on yourself probably shouldn't be enough. What I suspect is more of a problem is the aborted requests rather than the load.
    You might post some formatted code into one of the Web Tier API's forums and see what feedback and suggestions you get.

  • IO Exception: Broken Pipe

    Hi,
    I use WLS6.0/Linux. I'm accessing EJBs on the server from a standalone Java
    Client application. From time to time, I suddenly get this error:
    IO Exception: Broken Pipe
    The error has not been reproducible (so far...). Any ideas what causes this
    error?
    thx
    Heiko

    I too am having the same problem with using an OAS 9.0.4. server talking to a 9iAS db. I have a Struts application that if you leave the application over night will have broken pipes in the morning. The connections should not have persisted, but might have. This problem only happens when the Servlet is left up and no activity over night.
    They claim that no restart of the server or DB happened during that time so I am betting on a timeout somewhere in the system too.
    I have two problems:
    One to set up a situation that reproduces the problem.
    Two finding out some way through JDBC to effectively test for this situation and
    be able to re-create, or re-open a connection to continue processing.
    Error in fetcAllDBRecord java.sql.SQLException: Io exception: Broken
    pipe06/09/26 09:05:25 java.sql.SQLException: Io exception: Broken pipe
    06/09/26 09:05:25 at
    oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:189)
    06/09/26 09:05:25 at
    oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:231)
    06/09/26 09:05:25 at
    oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:345)
    06/09/26 09:05:25 at
    oracle.jdbc.driver.OracleStatement.open(OracleStatement.java:717)
    06/09/26 09:05:25 at
    oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2605)
    06/09/26 09:05:25 at
    oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:777)
    ......app specific levels
    Any help would be appreciated.
    ---John Putnam

  • LDAP Broken Pipe exception when deploying processes via ant task

    Hi,
    Has anyone experienced this and can offer a fix? We are publishing/deploying our processes using the fuego:publish task in Fuego 5.7 (we are migrating our system from 5.1) and one of the publish tasks for a large project always fails with the following exception:
    Caused by: fuego.directory.CommunicationException: Cannot connect to the Directory Service at: [iplanet://zion:28899/o=nexagent.com].
    Detail:The Directory Service could not be reached. Either the Directory Service is down, the host where it resides is unavailable, a network problem exists, or there is no Directory Service at the specified location.
    at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:465)
    at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:489)
    at fuego.directory.provider.ldap.LDAPProjectAccessor.createCatalogJar(LDAPProjectAccessor.java:160)
    at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:257)
    at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:46)
    at fuego.mami.CatalogPublisher.store(CatalogPublisher.java:369)
    at fuego.mami.ProjectPublisher.storeCatalog(ProjectPublisher.java:1631)
    at fuego.mami.ProjectPublisher.storeProject(ProjectPublisher.java:1653)
    at fuego.mami.ProjectPublisher.publish(ProjectPublisher.java:854)
    at fuego.tools.ant.enterprise.impl.PublishProjectTaskImpl.execute(PublishProjectTaskImpl.java:377)
    ... 23 more
    Caused by: javax.naming.CommunicationException: Broken pipe [Root exception is java.net.SocketException: Broken pipe]; remaining name 'cn=catalogJar-3,cn=fuego-dirCatalogJars,cn=fuego-directoryRoot'
    at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:803)
    at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
    at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
    at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
    at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:178)
    at fuego.jndi.FaultTolerantDirContext.createSubcontext(FaultTolerantDirContext.java:413)
    at fuego.directory.provider.ldap.LDAPPersistenceManager.createNestedEntry(LDAPPersistenceManager.java:1744)
    at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:455)
    ... 32 more
    Caused by: 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 java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
    at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:389)
    at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:364)
    at com.sun.jndi.ldap.LdapClient.add(LdapClient.java:1007)
    at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:766)
    ... 39 more
    Looking at the LDAP access log the error code is B1 which means that the client closed the connection without sending an unbind request or it could also mean that the client sent a malformed request to the server. The project being deployed is quite big and fails when storing the catalog, could the size have something to do with it (this worked in v5.1) is this a bug in 5.7?
    Any help would be greatly appreciated!
    regards,
    Mike

    Hi,
    Has anyone experienced this and can offer a fix? We are publishing/deploying our processes using the fuego:publish task in Fuego 5.7 (we are migrating our system from 5.1) and one of the publish tasks for a large project always fails with the following exception:
    Caused by: fuego.directory.CommunicationException: Cannot connect to the Directory Service at: [iplanet://zion:28899/o=nexagent.com].
    Detail:The Directory Service could not be reached. Either the Directory Service is down, the host where it resides is unavailable, a network problem exists, or there is no Directory Service at the specified location.
    at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:465)
    at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:489)
    at fuego.directory.provider.ldap.LDAPProjectAccessor.createCatalogJar(LDAPProjectAccessor.java:160)
    at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:257)
    at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:46)
    at fuego.mami.CatalogPublisher.store(CatalogPublisher.java:369)
    at fuego.mami.ProjectPublisher.storeCatalog(ProjectPublisher.java:1631)
    at fuego.mami.ProjectPublisher.storeProject(ProjectPublisher.java:1653)
    at fuego.mami.ProjectPublisher.publish(ProjectPublisher.java:854)
    at fuego.tools.ant.enterprise.impl.PublishProjectTaskImpl.execute(PublishProjectTaskImpl.java:377)
    ... 23 more
    Caused by: javax.naming.CommunicationException: Broken pipe [Root exception is java.net.SocketException: Broken pipe]; remaining name 'cn=catalogJar-3,cn=fuego-dirCatalogJars,cn=fuego-directoryRoot'
    at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:803)
    at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
    at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
    at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
    at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:178)
    at fuego.jndi.FaultTolerantDirContext.createSubcontext(FaultTolerantDirContext.java:413)
    at fuego.directory.provider.ldap.LDAPPersistenceManager.createNestedEntry(LDAPPersistenceManager.java:1744)
    at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:455)
    ... 32 more
    Caused by: 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 java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
    at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:389)
    at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:364)
    at com.sun.jndi.ldap.LdapClient.add(LdapClient.java:1007)
    at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:766)
    ... 39 more
    Looking at the LDAP access log the error code is B1 which means that the client closed the connection without sending an unbind request or it could also mean that the client sent a malformed request to the server. The project being deployed is quite big and fails when storing the catalog, could the size have something to do with it (this worked in v5.1) is this a bug in 5.7?
    Any help would be greatly appreciated!
    regards,
    Mike

  • Java.sql.SQLException: Io exception: Broken pipe

    To whom it may concern:
    Anyone who can help me with my problem? We have Java application(Loading2Staging) that calls a series of stored procedures in Oracle. This job takes about 30 hours to complete. We have other Java applications that is running and calling Oracle on the same machine and database. All of the applications are using "Java connection pooling". I'm encountering problem with the said application. When Loading2Staging is running and then other jobs would start to establish a connection, Loading2Staging then fails with this error: java.sql.SQLException: Io exception: Broken pipe
    The procedures of Loading2Staging is taking too long to complete. So my question is, "Is the job failing because of its inactivity or do some other applications steal the 'connection pooling' assigned to it for it to run smoothly?"
    If that's the case, could I create a "dedicated connection" or "connection pooling" to prevent the stealing of connection among jobs?
    This is a very urgent issue. Your immediate response will be much appreciated.
    Thank you.
    wletmp5

    Having exactly the same problem, does anybody know where the problem is?
    Thanks
    PD

  • Broken pipe issue on Weblogic 8.1 and HP-UX

    Hey all,
    I get the following "broken pipe" error when stress-testing the Weblogic AS 8.1 installed on HP-UX 11.
    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.writeChunkNoTransfer(ChunkUtils.
    java:280)
            at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:241)
            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.MultibyteOutput.write(ChunkOutput.java:482)
            at weblogic.servlet.internal.ChunkOutputWrapper.write
    (ChunkOutputWrapper
    .java:125)
            at weblogic.servlet.internal.ServletOutputStreamImpl.write(ServletOutput
    StreamImpl.java:184)
            at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66
            at java.io.BufferedOutputStream.write(BufferedOutputStream.java:110)
            at java.io.FilterOutputStream.write(FilterOutputStream.java:80)However, a quick glance on the forums revealed that this also happens on Weblogic+linux or tomcat+linux.
    Looks like an operating-system issue. Anyone has a clue ?
    Thank you,
    Cristian

    The following is the scenario where the broken pipe exception occurs to me:
    - webapp on a Linux server with Apache + Tomcat.
    - database (SQL Server) on another computer.
    - the webapp creates one db connection at startup, stores it in the ServletContext and always uses that connection for any db access.
    - If the db server is restarted, or just the SQL Server service is restarted, the connection that was in the ServletContext becomes invalid, and any attempt to access the db through it throws the broken pipe exception.
    At this point the webapp has to recreate the connection and re-store it in the ServletContext in order to gain access to the db again.
    HTH

  • SQLException from Broken Pipe.

    We're using NetDynamics, and conecting to Oracle 8.1.7. We've just moved our applications from one data center to another, and we find that after running a few hours two of our NetDynamics instances are getting SQLExecptions as follows;
    System Err: java.sql.SQLException caught. Vendor Err: null Io exception: Broken pipe
    I've worked with out networking people and DBA's. It doesn't seem that the firewall is getting in the way. Any suggestions ?

    My colleague had a similar problem though they were using Tomcat's connection pooling. The error was cause because a keep alive validation query was required to have active connections available in the pool. Your problem may be something similar.

  • Broken Pipe issue on HP

    I was printing large format color images on my HP Color LaserJet CP1515 with great results when suddenly one image did not come out. I checked the printer and appeared this info: Error 49 Broken Pipe... I thought it was a printer problem, I turned off and on and tried to print the demo page. It worked perfectly, tried an Acrobat file with image and again perfect, so I tried again the file I had the issue and again no results... This file was being printed using Photoshop.
    I would appreciate any help about this issue.
    Thanks!
    Mario

    The following is the scenario where the broken pipe exception occurs to me:
    - webapp on a Linux server with Apache + Tomcat.
    - database (SQL Server) on another computer.
    - the webapp creates one db connection at startup, stores it in the ServletContext and always uses that connection for any db access.
    - If the db server is restarted, or just the SQL Server service is restarted, the connection that was in the ServletContext becomes invalid, and any attempt to access the db through it throws the broken pipe exception.
    At this point the webapp has to recreate the connection and re-store it in the ServletContext in order to gain access to the db again.
    HTH

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

    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

    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

  • Ping timeouts at server and broken pipes at client

    I am experiencing unexpected broken pipe exceptions at the client side of a coherence server. These exceptions prevent our code to establish a connection to the cache server.
    Due to network restrictions, we are connecting client and server through Coherence*Extend.
    At the server side, the logs show the following message:
    DEBUG Coherence:3 - 2013-02-01 11:12:20.584/85.322 Oracle Coherence GE 3.7.1.5 <D6> (thread=Proxy:TcpProxyServicePof:TcpAcceptor, member=1): Closed: TcpConnection(Id=0x0000013C953D8F150AA202D9F632E5EAFD6BDDE1A713F026C65BC1E7CC1E5952, Open=false, Member(Id=0, Timestamp=2013-02-01 11:11:44.404, Address=127.0.0.1:0, MachineId=0, Location=site:,process:1612, Role=WeblogicServer), LocalAddress=10.162.2.217:28088, RemoteAddress=10.162.2.231:45202) due to:
    com.tangosol.net.messaging.ConnectionException: TcpConnection(Id=0x0000013C953D8F150AA202D9F632E5EAFD6BDDE1A713F026C65BC1E7CC1E5952, Open=true, Member(Id=0, Timestamp=2013-02-01 11:11:44.404, Address=127.0.0.1:0, MachineId=0, Location=site:,process:1612, Role=WeblogicServer), LocalAddress=10.162.2.217:28088, RemoteAddress=10.162.2.231:45202): did not receive a response to a ping within 500 millis
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.checkPingTimeout(Peer.CDB:12)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.Acceptor.checkPingTimeouts(Acceptor.CDB:7)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.onNotify(Peer.CDB:115)
    at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
    at java.lang.Thread.run(Thread.java:662)
    And at the client side:
    ERROR (01/02/2013) 11:12:20 [threadsafe]Thread-15/AbstractComponentHandler Unable to create new instance 45067 ms
    com.tangosol.net.messaging.ConnectionException: TcpConnection(Id=0x0000013C953D8F150AA202D9F632E5EAFD6BDDE1A713F026C65BC1E7CC1E5952, Open=true, Member(Id=0, Timestamp=2013-02-01 11:11:44.404, Address=127.0.0.1:0, MachineId=0, Location=site:,process:1612, Role=WeblogicServer), LocalAddress=10.162.2.231:45202, RemoteAddress=10.162.2.217:28088)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.initiator.TcpInitiator$TcpConnection.send(TcpInitiator.CDB:35)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.send(Peer.CDB:29)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.post(Peer.CDB:23)
    at com.tangosol.coherence.component.net.extend.Channel.post(Channel.CDB:25)
    at com.tangosol.coherence.component.net.extend.Channel.request(Channel.CDB:18)
    at com.tangosol.coherence.component.net.extend.Channel.request(Channel.CDB:1)
    at com.tangosol.coherence.component.net.extend.RemoteNamedCache$BinaryCache.putAll(RemoteNamedCache.CDB:10)
    at com.tangosol.util.ConverterCollections$ConverterMap.putAll(ConverterCollections.java:1708)
    at com.tangosol.coherence.component.net.extend.RemoteNamedCache.putAll(RemoteNamedCache.CDB:1)
    at com.tangosol.coherence.component.util.SafeNamedCache.putAll(SafeNamedCache.CDB:1)
    at com.tangosol.net.cache.CachingMap.putAll(CachingMap.java:1023)
    Caused by: java.net.SocketException: Write failed: Broken pipe
    at jrockit.net.SocketNativeIO.writeBytesPinned(Native Method)
    at jrockit.net.SocketNativeIO.socketWrite(SocketNativeIO.java:46)
    at java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java)
    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
    at java.io.BufferedOutputStream.write(BufferedOutputStream.java:104)
    at java.io.DataOutputStream.write(DataOutputStream.java:90)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.initiator.TcpInitiator$TcpConnection.send(TcpInitiator.CDB:27)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.send(Peer.CDB:29)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.post(Peer.CDB:23)
    at com.tangosol.coherence.component.net.extend.Channel.post(Channel.CDB:25)
    at com.tangosol.coherence.component.net.extend.Channel.request(Channel.CDB:18)
    at com.tangosol.coherence.component.net.extend.Channel.request(Channel.CDB:1)
    at com.tangosol.coherence.component.net.extend.RemoteNamedCache$BinaryCache.putAll(RemoteNamedCache.CDB:10)
    at com.tangosol.util.ConverterCollections$ConverterMap.putAll(ConverterCollections.java:1703)
    at com.tangosol.coherence.component.net.extend.RemoteNamedCache.putAll(RemoteNamedCache.CDB:1)
    at com.tangosol.coherence.component.util.SafeNamedCache.putAll(SafeNamedCache.CDB:1)
    at com.tangosol.net.cache.CachingMap.putAll(CachingMap.java:1023)
    I can ping the client machine from the server without a problem.
    Has anybody seen this before?
    Edited by: 982740 on Feb 1, 2013 2:29 AM

    Hi user,
    It seems from the log that when the proxy node accepts your client connection the client fails to respond to a ping request down the same pipe. Does this happen consistently? If so, no putAll would ever succeed.
    I have to admit I've never seen this behaviour before. I can't see how this would be a firewall port issue, as the connection has been established... the only things I can think of would be a) your weblogic client node is running way to hot and doesn't respond to the grids ping request in time, b) Some very aggressive network infrastructure is killing the connection just after its created, or c) aliens are interfering with your system.
    sorry I can't be of more help,
    Andy

Maybe you are looking for

  • Can't open WMV files in Quicktime since Snow Lep upgrade.....

    I Can't open WMV files in Quicktime since Snow Leopard upgrade I get an error message saying 'Quicktime player must be installed to run this application' This is happening on both of my macs Any help appreciated

  • Word doc from javaScript

    I am creating the MS word document in java script by using command document.execCommand('SaveAs', true, 'test.doc'); now my requirement is Each page in above generated word document should have a footer with a centered �Page x of y� line. please tell

  • Can I change my SIM card to use it in South Korea?

    Hi, I'm planning to stay in South Korea for 3 months this summer and I was wondering if I could buy a new SIM card in Korea and put it into my current Verizon phone that I'm using in the States(It is Galaxy S4). Global plan seems to be expensive so I

  • Maint order should get TECO automatically after final Confirmation

    Hi Gurus, My customer requirement is that, Maint order should get TECO automatically after final Confirmation (in IW41) of last operation. Is it possible? If yes, plz let me know the steps which I need to do. Thanks in Advanceu2026 Amol.

  • /etc/hosts in Snow Leopard: ping works, browsers don't?

    I've had success in the past using /etc/hosts to direct web browsers to a test server instead of the production server, but it's not working in OS X 10.6.7. I edit the hosts file: $ sudo vi /etc/hosts Add my entry: # Host Database # localhost is used