Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-11203

Interoperability EAP 5 <-> EAP6 - Client is not being consistent on the request versioning. It just sent a version id=122 while it informed 123 previously

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • EAP_EWP 5.2.0
    • EAP_EWP 5.2.0
    • HornetQ
    • None

    Description

      There are warnings in the log of EAP 5.2.0 (with HornetQ roll-up patch JBPAPP-11200 - HornetQ 2.2.30.Final) server in the following scenario:

      1. Start 2 EAP 5 servers with queue InQueue/InTopic and OutQueue/OutTopic
2. Start EAP 6 server
3. Start producer which sends messages to InQueue/InTopic
4. Deploy MDB on EAP 6 listening on InQueue/InTopic and calls EJB sending to OutQueue/OutTopic
5. When processing messaging kill/shutdown EAP 5 or EAP 6 server
6. Start killed/shutdowned server
7. Start consumer which receives messages from OutQueue
8. Check all messages were received

      Every time when EJB is called by MDB to send message to OutQueue this warning is logged in EAP 5.2.0 server:

      2014-11-14 14:25:52,185 WARN  [org.hornetq.core.protocol.core.impl.HornetQPacketHandler] (Old I/O server worker (parentId: 1469453217, [id: 0x579613a1, /127.0.0.1:5447])) Client is not being consistent on the request versioning. It just sent a version id=122 while it informed 123 previously

      This warning appears to be harmless but it floods the server.log. This can be unacceptable for our users/customers.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-11022 Interoperability EAP 5 <-> EAP6 - WARN Client with version 123 and address /127.0.0.1:48777 is not compatible with server version 2.2.24.GA

          • 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.
          • Resolved

          Activity

            People

              rhn-support-toross Tom Ross
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: