Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-838

[AMQ7, openwire] WARN [org.apache.activemq.artemis.core.server] Error during message dispatch: java.io.EOFException

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • AMQ 7.0.3.GA
    • broker-core, openwire-protocol
    • None
      • using a producer with A-MQ6 client version 5.11.0.redhat-630283 seems to avoid the issue.
    • Hide

      1) create a standard AMQ7 instance (using admin/admin as username/password)

      2) untar amq6_producer and run following maven commands

      mvn install
mvn exec:java -Dexec.mainClass=com.mysample.MyProducer

      3) untar anq6_consumer.tar and run following maven commands

      mvn install
mvn exec:java -Dexec.mainClass=com.mysample.MyConsumer

      Result:

      • exception in description reported in broker log
      • message does not reach consumer code.
      Show
      1) create a standard AMQ7 instance (using admin/admin as username/password) 2) untar amq6_producer and run following maven commands mvn install mvn exec:java -Dexec.mainClass=com.mysample.MyProducer 3) untar anq6_consumer.tar and run following maven commands mvn install mvn exec:java -Dexec.mainClass=com.mysample.MyConsumer Result: exception in description reported in broker log message does not reach consumer code.
    • AMQ Broker 7.1 Sprint 2

    Description

      Producer (A-MQ6 client version 5.8.0.redhat-60024) appears to succeed in sending message to queue but the message never reaches the consumer(A-MQ6 client version 5.11.0.redhat-630283)

      On the queue JMX statistics it seem to remain in the "delivering count"

      10:30:09,112 WARN  [org.apache.activemq.artemis.core.server] Error during message dispatch: java.io.EOFException
	at org.apache.activemq.util.DataByteArrayInputStream.readOrIOException(DataByteArrayInputStream.java:127) [activemq-client-5.11.0.redhat-630283.jar:5.11.0.redhat-630283]
	at org.apache.activemq.util.DataByteArrayInputStream.readByte(DataByteArrayInputStream.java:193) [activemq-client-5.11.0.redhat-630283.jar:5.11.0.redhat-630283]
	at org.apache.activemq.openwire.OpenWireFormat.tightUnmarshalNestedObject(OpenWireFormat.java:425) [activemq-client-5.11.0.redhat-630283.jar:5.11.0.redhat-630283]
	at org.apache.activemq.openwire.v10.BaseDataStreamMarshaller.tightUnmarsalCachedObject(BaseDataStreamMarshaller.java:151) [activemq-client-5.11.0.redhat-630283.jar:5.11.0.redhat-630283]
	at org.apache.activemq.openwire.v10.MessageIdMarshaller.tightUnmarshal(MessageIdMarshaller.java:70) [activemq-client-5.11.0.redhat-630283.jar:5.11.0.redhat-630283]
	at org.apache.activemq.openwire.OpenWireFormat.doUnmarshal(OpenWireFormat.java:355) [activemq-client-5.11.0.redhat-630283.jar:5.11.0.redhat-630283]
	at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:194) [activemq-client-5.11.0.redhat-630283.jar:5.11.0.redhat-630283]
	at org.apache.activemq.artemis.core.protocol.openwire.OpenWireMessageConverter.toAMQMessage(OpenWireMessageConverter.java:716) [artemis-openwire-protocol-2.0.0.amq-700013-redhat-1.jar:]
	at org.apache.activemq.artemis.core.protocol.openwire.OpenWireMessageConverter.createMessageDispatch(OpenWireMessageConverter.java:427) [artemis-openwire-protocol-2.0.0.amq-700013-redhat-1.jar:]
	at org.apache.activemq.artemis.core.protocol.openwire.amq.AMQConsumer.handleDeliver(AMQConsumer.java:224) [artemis-openwire-protocol-2.0.0.amq-700013-redhat-1.jar:]
	at org.apache.activemq.artemis.core.protocol.openwire.amq.AMQSession.sendMessage(AMQSession.java:250) [artemis-openwire-protocol-2.0.0.amq-700013-redhat-1.jar:]
	at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.deliverStandardMessage(ServerConsumerImpl.java:1080) [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
	at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.proceedDeliver(ServerConsumerImpl.java:458) [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
	at org.apache.activemq.artemis.core.server.impl.QueueImpl.proceedDeliver(QueueImpl.java:2711) [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
	at org.apache.activemq.artemis.core.server.impl.QueueImpl.deliver(QueueImpl.java:2194) [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
	at org.apache.activemq.artemis.core.server.impl.QueueImpl.access$1700(QueueImpl.java:104) [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
	at org.apache.activemq.artemis.core.server.impl.QueueImpl$DeliverRunner.run(QueueImpl.java:2950) [artemis-server-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
	at org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42) [artemis-commons-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
	at org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31) [artemis-commons-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
	at org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53) [artemis-commons-2.0.0.amq-700013-redhat-1.jar:2.0.0.amq-700013-redhat-1]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_20]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_20]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20]

      When using Producer and Client (A-MQ6 client version 5.11.0.redhat-630283) message appears to be dispatched as expected without a WARNING message.

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-743 "Error during message dispatch" when receiving a message sent from OpenWire with wireFormat.tightEncodingEnabled=false

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-437 JMSMessageID doesn't appear to work in selector?

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-836 Messages successfully sent by NMS OpenWire to 7.0.z broker cannot be consumed on 6.3.0 by activemq:consumer

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) AMQDOC-2783 WARN [org.apache.activemq.artemis.core.server] Error during message dispatch: java.io.EOFException

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              gaohoward Howard Gao
              rhn-support-pfox Patrick Fox (Inactive)
              Martyn Taylor Martyn Taylor (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: