[ 
https://issues.apache.org/jira/browse/AMQCPP-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liviu Citu updated AMQCPP-754:
------------------------------
    Attachment: broker.xml

> [Artemis Broker] CMS exception: OpenWireFormatNegotiator::onewayWire format 
> negotiation timeout: peer did not send his wire format.
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-754
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-754
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>            Reporter: Liviu Citu
>            Priority: Major
>         Attachments: broker.xml
>
>
> We are currently in process of migrating our JMS Broker from Classic AMQ 5.x 
> to Artemis.
> We are currently using CMS C++ client for connecting to JMS Broker. 
> Everything works fine when using non-SSL setup (on both Windows and Linux) 
> but we have some issues when using SSL on Linux (SSL on Windows is OK).
> The initial problem started with the following exceptions on the client side:
> *_024-02-22 09:54:37.377 [ERROR] [activemq_connection.cc:336] CMS exception: 
> Channel was inactive for too long:_*
>                 *_FILE: activemq/core/ActiveMQConnection.cpp, LINE: 1293_*
>                 *_FILE: activemq/core/ActiveMQConnection.cpp, LINE: 1371_*
>                 *_FILE: activemq/core/ActiveMQConnection.cpp, LINE: 573_*
> while on the JMS Broker side we had:
> *_2024-03-20 12:29:08,700 ERROR [org.apache.activemq.artemis.core.server] 
> AMQ224088: Timeout (10 seconds) on acceptor "netty-ssl-acceptor" during 
> protocol handshake with /10.21.70.53:33053 has occurred._*
> To bypass these we have added the following setting to the *broker.xml* 
> *netty-ssl-acceptor* acceptor: *handshake-timeout=0*
> However now the exceptions we are receiving are:
> *_2024-05-22 09:26:40.842 [ERROR] [activemq_connection.cc:348] CMS exception: 
> OpenWireFormatNegotiator::onewayWire format negotiation timeout: peer did not 
> send his wire format._*
>         *_FILE: activemq/core/ActiveMQConnection.cpp, LINE: 1293_*
>         *_FILE: activemq/core/ActiveMQConnection.cpp, LINE: 1371_*
>         *_FILE: activemq/core/ActiveMQConnection.cpp, LINE: 573_*
> The problem replicates with the following:
>  * SSL on Linux problem does not replicate if non-SSL configuration is used. 
> Also does not replicate on Windows (regardless if SSL or non-SSL is used)
>  * two Artemis JMS Broker instances running on the same Linux host (problem 
> does not replicate if there is only one Artemis JMS Broker instance running)
>  * problem also replicates if there is one Artemis Broker and one Classic 
> Broker instance running on the same host
>  * problem does not replicate with two instances of Classic Brokers. So it is 
> specific to Artemis broker
>  * when testing with both Classic Broker and Artemis Broker, the client 
> connections using the Classic Broker were fine. Only those using Artemis 
> Broker were failing
>  * CMS C++ client is also on Linux running on the same host. Basically both 
> client and server are running on the same host
>  * there are many connections done in the same time to the broker (50+). If 
> there are only few then the problem does not happen
>  * example of JMS Broker URL used by the client (the other instance just uses 
> a different port)
> *ssl://host_aname:3177?soKeepAlive=true&wireFormat.MaxInactivityDuration=0*
>  * one JMS Broker configuration file (attached, just mangled the password). 
> The other one is similar (port changed)
>  
> Does Artemis support non-UTF-8 encoding? Do we need now to encode all 
> messages to UTF-8 before sending them to the server? Similarly to decode them 
> upon receiving?
> This will cause some problems on our end because:
>  * we have many clients already using the ActiveMQ classic and migrating them 
> to Artemis will cause issues when migrating KahaDB to Artemis because all the 
> messages have to be encoded to UTF-8 otherwise they will not work in Artemis
>  * encoding/decoding every message will impact the overall performance. We 
> have applications handling thousands of messages every day and conversion of 
> these messages will increase the time spent during communication with JMS 
> broker
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to