activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruce Snyder (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2730) Transport failed: java.io.EOFException
Date Thu, 07 Oct 2010 15:43:41 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62436#action_62436
] 

Bruce Snyder commented on AMQ-2730:
-----------------------------------

{quote} 
1. Do You mean configuration of memory in ApacheMQ in bin Directory? It looks like -it is
not reason of problem?
Set jvm memory configuration
ACTIVEMQ_OPTS_MEMORY="-Xms256M -Xmx512M"
{quote} 

Yes, one possibility is memory resources have been exhausted. By default, the ActiveMQ startup
script allocates 512mb to the JVM in which ActiveMQ runs. In addition to the memory allocated
to the JVM, you also need to configure the memory that is made available to the broker via
the {{<systemUsage>}} element in the activemq.xml file. See the docs for the {{<systemUsage>}}
element for more info: 

[http://activemq.apache.org/producer-flow-control.html#ProducerFlowControl-Systemusage]  

{quote} 
2. What do You mean? It is Stomp configurationc for ApacheMQ: there is only Port 61612. How
can client try to contact other ports? Is it possible?
{quote} 

I mean that the client may be connecting to a port that does not have a TCP transport connector
registered to it. It is possible for a client to use TCP to connect to ActiveMQ via a port
that has a non-TCP endpoint registered. However, the client will not get a full handshake
and an error will be thrown. 

{quote} 
3. FAQ. Only one configuration's property works with STOMP protocol. so it doesn't work: 
<transportConnector name="stomp" uri="stomp://0.0.0.0:61612?transport.closeAsync=false&soTimeout=30000&wireFormat.maxInactivityDurationInitalDelay=30000"/>
{quote} 

FAQ item #3 is referring to the failover transport connector which is used on the client-side,
not the Stomp transport connector which is used on the broker-side. Here are the docs for
the failover transport: 

[http://activemq.apache.org/failover-transport-reference.html] 

{quote} 
Hi,
what can i configure in case of using Loadbalancer?
It sends constantly check bytes to Port 61612...
So exceptions come in Stomp Protocol -error of reading of line...
What is right solution?
{quote} 

Typically people have a TCP or NIO transport connector defined in the broker config for this
purpose. The load balancer just opens a socket with the broker via the TCP transport and if
it is able to connect, it assumes that the broker is up and running. More sophisticated setups
that I have seen actually have the load balancer run a script that connects the broker and
sends/receives a message on a destination to ensure that the broker is actually processing
messages. 

> Transport failed: java.io.EOFException
> --------------------------------------
>
>                 Key: AMQ-2730
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2730
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.1
>         Environment: Red hat enterprise
>            Reporter: Dennis Klinkott
>             Fix For: 5.5.0
>
>         Attachments: TCP Dump.jpg
>
>
> We see many Exceptions of this type in the broker logs: 
> 2010-05-12 14:10:03,490 | DEBUG | Transport failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport
| ActiveMQ Transport: tcp:///10.231.233.55:50809
> java.io.EOFException
>         at java.io.DataInputStream.readInt(DataInputStream.java:375)
>         at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:269)
>         at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:211)
>         at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:203)
>         at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:186)
>         at java.lang.Thread.run(Thread.java:619)
> This exception occurs with a lot of clients that run on different machines.
> One case where we almost always see this exception is when shutting down a bridge. We
did a tcp dump on the broker and on the client machine: there a no packets lost.
> LOG ON BRIDGE:
> 2010-05-12 14:10:02,634 INFO  org.apache.activemq.broker.BrokerService - ActiveMQ Message
Broker (solr-2073bridge, ID:solr-2073-50804-
> 1273665033782-0:0) is shutting down
> 2010-05-12 14:10:02,799 INFO  org.apache.activemq.network.jms.JmsConnector - JMS Connector
Connector:0 Stopped
> 2010-05-12 14:10:02,819 INFO  org.apache.activemq.broker.BrokerService - ActiveMQ JMS
Message Broker (solr-2073bridge, ID:solr-2073-50
> 804-1273665033782-0:0) stopped
> LOG ON BROKER:
> 2010-05-12 14:10:03,490 | DEBUG | Transport failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport
| ActiveMQ Transport: tcp:///10.231.233.55:50809
> java.io.EOFException
>         at java.io.DataInputStream.readInt(DataInputStream.java:375)
>         at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:269)
>         at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:211)
>         at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:203)
>         at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:186)
>         at java.lang.Thread.run(Thread.java:619)
> 2010-05-12 14:10:03,492 | DEBUG | Stopping connection: /10.231.233.55:50809 | org.apache.activemq.broker.TransportConnection
| ActiveMQ Task
> 2010-05-12 14:10:03,492 | DEBUG | Stopping transport tcp:///10.231.233.55:50809 | org.apache.activemq.transport.tcp.TcpTransport
| ActiveMQ Task
> 2010-05-12 14:10:03,493 | DEBUG | Stopped transport: /10.231.233.55:50809 | org.apache.activemq.broker.TransportConnection
| ActiveMQ Task
> 2010-05-12 14:10:03,493 | DEBUG | Cleaning up connection resources: /10.231.233.55:50809
| org.apache.activemq.broker.TransportConnection | ActiveMQ Task
> 2010-05-12 14:10:03,493 | DEBUG | remove connection id: ID:solr-2073-50804-1273665033782-2:0
| org.apache.activemq.broker.TransportConnection | ActiveMQ Task
> 2010-05-12 14:10:03,493 | DEBUG | jms1 removing consumer: ID:solr-2073-50804-1273665033782-2:0:225:1
for destination: temp-queue://ID:solr-2073-50804-1273665033782-2:0:105 | org.apache.activemq.broker.region.AbstractRegion
| ActiveMQ Task
> 2010-05-12 14:10:03,493 | DEBUG | remove sub: QueueSubscription: consumer=ID:solr-2073-50804-1273665033782-2:0:225:1,
destinations=1, dispatched=0, delivered=0, pending=0, lastDeliveredSeqId: 0, dequeues: 0,
dispatched: 0, inflight: 0 | org.apache.activemq.broker.region.Queue | ActiveMQ Task

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


Mime
View raw message