activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel, Vojtech (JIRA)" <>
Subject [jira] Created: (AMQ-1634) Broken Pipe Exception
Date Thu, 27 Mar 2008 14:06:32 GMT
Broken Pipe Exception

                 Key: AMQ-1634
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 4.1.1
         Environment: AIX 5.3
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc-32
Filesystem: GPFS
            Reporter: Daniel, Vojtech

We startup AMQ 4.1.1, have some messages send and after some time we get a broken pipe exception:

Loading message broker from: xbean:activemq.xml
INFO  BrokerService                  - ActiveMQ 4.1.1 JMS Message Broker (BrokerMQ1) is starting
INFO  BrokerService                  - For help or more information please see:
INFO  JDBCPersistenceAdapter         - Database driver recognized: [apache_derby_embedded_jdbc_driver]
INFO  DefaultDatabaseLocker          - Attempting to acquire the exclusive lock to become
the Master broker
INFO  DefaultDatabaseLocker          - Becoming the master on dataSource: org.apache.derby.jdbc.EmbeddedDataSource@6e5a6e5a
INFO  JournalPersistenceAdapter      - Journal Recovery Started from: Active Journal: using
2 x 20.0 Megs at: /somePathToASharedFS/foBroker1/journal
INFO  JournalPersistenceAdapter      - Journal Recovered: 0 message(s) in transactions recovered.
INFO  TransportServerThreadSupport   - Listening for connections at: tcp://xxxxxxxxxxxxxxx:63616
INFO  TransportConnector             - Connector tcp://localhost:63616 Started
INFO  BrokerService                  - ActiveMQ JMS Message Broker (BrokerMQ1, ID:xxxxxxxxxxx-63589-1206619947406-1:0)
ERROR TransportConnector             - Could not accept connection from /xxxxxxxxxxxxxxxx:64529: Broken pipe Broken pipe
        at Method)
        at org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(
        at org.apache.activemq.transport.tcp.TcpTransport.oneway(
        at org.apache.activemq.transport.InactivityMonitor.oneway(
        at org.apache.activemq.transport.TransportFilter.oneway(
        at org.apache.activemq.transport.WireFormatNegotiator.oneway(
        at org.apache.activemq.transport.MutexTransport.oneway(

Objective was to have filesystem based Master-Slave failover scenario.

Our configuration file looks like this:

        <!-- Allows us to use system properties as variables in this configuration file
        <bean   class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"

        <broker brokerName="BrokerMQ1" useJmx="false" xmlns="">
                <!-- Use the following to configure how ActiveMQ is exposed in JMX -->
                <!-- managementContext>
                <managementContext connectorPort="61099" jmxDomainName="org.apache.activemq"/>

                        <journaledJDBC dataDirectory="/somePathToASharedFS/foBroker1"/>

                        <transportConnector uri="tcp://localhost:63616" />



This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message