From users-return-49844-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Fri Apr 13 19:53:21 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5BC5C180627 for ; Fri, 13 Apr 2018 19:53:21 +0200 (CEST) Received: (qmail 15259 invoked by uid 500); 13 Apr 2018 17:53:20 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 15248 invoked by uid 99); 13 Apr 2018 17:53:19 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Apr 2018 17:53:19 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id ED9FBC0286 for ; Fri, 13 Apr 2018 17:53:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.011 X-Spam-Level: X-Spam-Status: No, score=-0.011 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 4765GCwuUQjs for ; Fri, 13 Apr 2018 17:53:17 +0000 (UTC) Received: from mailrouter.email.uvu.edu (mailrouter.email.uvu.edu [161.28.20.105]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id A805D5F254 for ; Fri, 13 Apr 2018 17:53:16 +0000 (UTC) Message-ID: <1523641995.17772.39.camel@uvu.edu> Subject: Getting 'java.lang.NumberFormatException: For input string: "1-1"' errors when doing client side ack with STOMP clients if message sent by AMQP producer From: Daniel Hutchison To: users@activemq.apache.org Date: Fri, 13 Apr 2018 11:53:15 -0600 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hey all, When my STOMP clients try to do client side ACKs on a message that was sent from an AMQP producer, I'm getting the following error message showing up in activemq's log (and my stomp clients get an error on their connection as well): 2018-04-13 10:38:40,263 | WARN=C2=A0=C2=A0| Transport Connection to: tcp:= //10.1.1.18:39522 failed: java.io.IOException: Unexpected error occurred:= java.lang.NumberFormatException: For input string: "1-1" | org.apache.ac= tivemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///= 10.1.1.18:39522@61613 I have been running activemq 5.10 with JMS java clients and producers. =C2=A0We have some programs written in PHP, Perl and Python that needed t= o interact with the JMS messages. =C2=A0 So, I set them up using STOMP, and everything has been running well for several years now (activemq seems to be able to seamlessly transform the java text messages to stomp, and I've been really happy with the system). We recently had to integrate software that only supported sending AMQP messages. =C2=A0 After integrating the AMQP producer, the messages sent f= rom it are not able to be ACKed by the STOMP clients (I tried all STOMP clients I could, PHP, Python, and 2 different Perl modules). =C2=A0 All o= f them reported the error when they tried to ACK the message. I upgraded to activemq 5.15 to see if that would fix anything, but I'm still getting the same error. =C2=A0 I am currently using the=C2=A0transport.transformer=3Djms flag on my amqp transports (otherwis= e the text body came with binary output in the stomp clients). =C2=A0 Howev= er, I would get the java.lang.NumberFormatException with and with out the transformer setting. Here is what the activemq dashboard shows for the message causing the error above: =C2=A0=C2=A0=C2=A0=C2=A0Headers =C2=A0=C2=A0=C2=A0=C2=A0--------------- =C2=A0=C2=A0=C2=A0=C2=A0Message ID:=C2=A0=C2=A0ID:4ddb14b6-6f7a-4ba2-ad91= -755b3010c5c1:1:1:1-1 =C2=A0=C2=A0=C2=A0=C2=A0Destination: queue://IAM.box.membership =C2=A0=C2=A0=C2=A0=C2=A0Correlation: ID =C2=A0=C2=A0=C2=A0=C2=A0Group" =C2=A0=C2=A0=C2=A0=C2=A0Sequence:=C2=A0=C2=A0=C2=A0=C2=A00 =C2=A0=C2=A0=C2=A0=C2=A0Expiration:=C2=A0=C2=A00 =C2=A0=C2=A0=C2=A0=C2=A0Persistence: Persistent =C2=A0=C2=A0=C2=A0=C2=A0Priority:=C2=A0=C2=A0=C2=A0=C2=A04 =C2=A0=C2=A0=C2=A0=C2=A0Redelivered: true =C2=A0=C2=A0=C2=A0=C2=A0Reply To:=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0Timestamp:=C2=A0=C2=A0=C2=A02018-04-12 16:47:01:1= 33 MDT =C2=A0=C2=A0=C2=A0=C2=A0Type:: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0Properties =C2=A0=C2=A0=C2=A0=C2=A0--------------------- =C2=A0=C2=A0=C2=A0=C2=A0JMS_AMQP_ORIGINAL_ENCODING:=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A05 =C2=A0=C2=A0=C2=A0=C2=A0JMS_AMQP_MA_x-opt-jms-msg-type:=C2=A0=C2=A05 =C2=A0=C2=A0=C2=A0=C2=A0JMSXDeliveryCount:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A053 =C2=A0=C2=A0=C2=A0=C2=A0JMS_AMQP_PROPERTIES:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0true =C2=A0=C2=A0=C2=A0=C2=A0JMS_AMQP_HEADER:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0true =C2=A0=C2=A0=C2=A0=C2=A0JMS_AMQP_MA_x-opt-jms-dest:=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A00 The JMS clients don't have any problem acking the message on the client side. It is only the STOMP clients. =C2=A0 Since all STOMP clients I've tested have the same issue, it seems like something inside activemq is not working right. =C2=A0 The '1-1' that activemq is having problems with seems to be part of the message ID that activemq has in its system.=C2=A0 However, I'm not sure what I can do to work around the issue or try to fix it. Any insight would be much appreciated. Thanks, -daniel