Re: [kapua-dev] Kura 2.1.0 exception in Mqtt transfer with latest kapua

["Codutti, Alberto" <Alberto.Codutti@xxxxxxxxxxxx>]

Hi Pablo,

 

Thank you for your patience.

 

About the GitHub issue, I think that it makes sense trying first with the maliling list to check if it is a real bug/problem or not.

If confirmed as bug, then open the GitHub issue.

So, as it is confirmed as bug, you can open the issue :)

 

Please report the context informations about the issue and how to reproduce, so everithing is clear on the issue.

 

Regards,

 

Alberto

 

From: <kapua-dev-bounces@xxxxxxxxxxx> on behalf of Pablo Chacin <pablochacin@xxxxxxxxx>
Reply-To: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Date: Wednesday, January 4, 2017 at 2:42 PM
To: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Subject: Re: [kapua-dev] Kura 2.1.0 exception in Mqtt transfer with latest kapua code

 

Hi Alberto

 

Not urgency for having it running right now. I guess i can wait until you solve the issue.

Just to be sure, should I better open a github issue next time or

reporting here is fine for you?  I didn't do it mostly because i wasn't sure

if it was a kapua issue or not.

Thanks

 

On Wed, Jan 4, 2017 at 2:26 PM, Codutti, Alberto <Alberto.Codutti@xxxxxxxxxxxx> wrote:

Hi Pablo,

 

I can tell for sure this is a Kapua issue.

I’m working to fix it.

 

Do you need a running environment with Broker and Console running?

 

Regards,

 

Alberto

 

 

Alberto Codutti | R&D | EUROTECH | direct: +39 0433 485412 | Timezone: CET (UTC +01:00)

 

From: <kapua-dev-bounces@xxxxxxxxxxx> on behalf of Pablo Chacin <pablo@xxxxxxxxxxxx>
Reply-To: kapua developer discussions <kapua-dev@xxxxxxxxxxx>
Date: Tuesday, January 3, 2017 at 4:41 PM
To: Kura Developers mailing list <kura-dev@xxxxxxxxxxx>, "kapua-dev@xxxxxxxxxxx" <kapua-dev@xxxxxxxxxxx>
Subject: [kapua-dev] Kura 2.1.0 exception in Mqtt transfer with latest kapua code

 

Hi 

Sorry for the cross-posting but I'm not sure on which endpoint the problem is: kapua or kura.

I'm testing Kura 2.1.0 raspberry-pi-nn installer deployed on a docker container, with the latest 

kapua code (I just updated it today). I got the exception described below.

 

This configuration used to work with the kapua version as of December 20th. Also, the same 

problem arises when testing Kura 1.3.0 and 2.0.2, therefore it points to a problem in the kapua side.

 

Note: I'm using the kapua-sys account to authenticate the mqtt service.

 

 

2017-01-03 15:18:48,680 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.DataServiceIm

pl - Connecting...

2017-01-03 15:18:48,681 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataT

ransport - # ------------------------------------------------------------

2017-01-03 15:18:48,682 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataT

ransport - #  Connection Properties

2017-01-03 15:18:48,682 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataT

ransport - #  broker    = tcp://localhost:1883

2017-01-03 15:18:48,682 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataT

ransport - #  clientId  = pablo-thinkpad-t460

2017-01-03 15:18:48,682 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataT

ransport - #  username  = kapua-sys

2017-01-03 15:18:48,683 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataT

ransport - #  password  = XXXXXXXXXXXXXX

2017-01-03 15:18:48,683 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataT

ransport - #  keepAlive = 30

2017-01-03 15:18:48,683 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataT

ransport - #  timeout   = 20

2017-01-03 15:18:48,683 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataT

ransport - #  cleanSession    = true

2017-01-03 15:18:48,684 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataTransport - #  MQTT version    = 3.1.1

2017-01-03 15:18:48,684 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataTransport - #  willDestination = $EDC/kapua-sys/pablo-thinkpad-t460/MQTT/LWT

2017-01-03 15:18:48,684 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataTransport - #  willMessage     = 

2017-01-03 15:18:48,684 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataTransport - #

2017-01-03 15:18:48,685 [DataServiceImpl:ReconnectTask] INFO  o.e.k.c.d.t.m.MqttDataTransport - #  Connecting...

2017-01-03 15:18:48,718 [DataServiceImpl:ReconnectTask] WARN  o.e.k.c.d.t.m.MqttDataTransport - xxxxx  Connect failed. Forcing disconnect. xxxxx {}

Connection lost (32109) - java.io.EOFException

        at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:154)

        at java.lang.Thread.run(Thread.java:745)

Caused by: java.io.EOFException

        at java.io.DataInputStream.readByte(DataInputStream.java:267)

        at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(MqttInputStream.java:89)

        at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:112)

        ... 1 more

 

_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev

 

--

		Pablo Chacin about.me/pablochacin