kamilfb / mqtt-spy Goto Github PK

What steps will reproduce the problem?
1. checkout repo
2. cd mqtt-spy-common
3. mvn clean install


What is the expected output? What do you see instead?

BUILD SUCCESS

What version of the product are you using? On what operating system?

Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 
17:22:22+0200)
Maven home: /usr/share/maven-bin-3.1
Java version: 1.8.0_40, vendor: Oracle Corporation
Java home: /opt/oracle-jdk-bin-1.8.0.40/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.18.2-gentoo", arch: "amd64", family: "unix"


Please provide any additional information below.

Using unmodified pom.xml for mqtt-spy-common results in an error on compilation:

[ERROR] 
/home/rathgeb/workspace/esh/mqtt-spy/mqtt-spy-common/src/main/java/pl/baczkowicz
/mqttspy/scripts/ScriptManager.java:[183,50] error: diamond operator is not 
supported in -source 1.5

So, we should set the source to 1.7 or 1.8.

diff --git a/mqtt-spy-common/pom.xml b/mqtt-spy-common/pom.xml
index 1dca75c..d7bdc5c 100644
--- a/mqtt-spy-common/pom.xml
+++ b/mqtt-spy-common/pom.xml
@@ -8,6 +8,8 @@
        <properties>
                <timestamp>${maven.build.timestamp}</timestamp>
                <maven.build.timestamp.format>yyyy</maven.build.timestamp.format>
+               <maven.compiler.source>1.7</maven.compiler.source>
+               <maven.compiler.target>1.7</maven.compiler.target>
        </properties>

        <repositories>

What steps will reproduce the problem?
1. Subscribe to a test topic
2. Publish an HEX encoded value to that topic
3. The result HEX decoded is different than the value sent

What is the expected output? What do you see instead?

I have tested by sending the following HEX sequence: 3f915604fffd
And the result was: efbfbdefbfbd5604efbfbdefbfbd

What version of the product are you using? On what operating system?
I am using the latest beta version on windoes 7 x64

Please provide any additional information below.

Not sure if it is the case, but it looks that is something with JAVA 8, 
probably related to the link below:
http://docs.oracle.com/javase/8/docs/api/java/io/DataInput.html#modified-utf-8

I have attached two files showing the same test with a client using JAVA 7 and 
MQTT-spy (uses JAVA 8).

What steps will reproduce the problem?
1. Tried to edit the XML to add a subscription
2. XML became unusable
3.

What is the expected output? What do you see instead?

I would expect to be able to add subscriptions. Also XML file hard to use in 
NOTEPAD++ (which works for just about any other text file) as file does not 
contain CRLFs even though the documentation suggests it will be formatted as 
such

Can we have subscriptions saved when closing down - it's painful having to 
re-enter them.

What version of the product are you using? On what operating system?

JUST downloaded latest non-beta version.


Please provide any additional information below.


Windows 8

What steps will reproduce the problem?
1. type a user Id with more than 23 chars, it will truncate
2.
3.

What is the expected output? What do you see instead?
allow type more than 23 chars in user id


What version of the product are you using? On what operating system?
3.1.1


Please provide any additional information below.

MQTT 3.1.1 allows user id longer than 23 chars.

Clicking on the 'show' column in the message summary is not properly triggering 
the message currently being displayed in the messaging browser pane.

Found in 0.0.10.

in order to better use desktop estate it would be nice to be able to adjust the 
font size used by MQTT-Spy

What steps will reproduce the problem?
1. Use Eclipse IDE for mqtt-spy-common (import maven project)
2. Build

What is the expected output? What do you see instead?

Build fails:
W3C_XML_SCHEMA_NS_URI cannot be resolved or is not a field

Please provide any additional information below.

These days (in Java 6 and newer), you do not need any explicit JAXB, JAX-WS, 
XML Streaming API (JSR-173) or SAAJ jars because they are all included in the 
JDK. There are many other non-xml related APIs generally available too, such as 
javax.activation for example.
You should exclude anything to do with these if your environment is Java 6 or 
newer.
We could use "mvn dependency:tree" to determine the dependency that depends of 
jsr173_api.

For version 1.8 see issue #33

Patch to solve problem:

diff --git a/mqtt-spy-common/pom.xml b/mqtt-spy-common/pom.xml
index 1dca75c..1cefb5e 100644
--- a/mqtt-spy-common/pom.xml
+++ b/mqtt-spy-common/pom.xml
@@ -8,6 +8,8 @@
        <properties>
                <timestamp>${maven.build.timestamp}</timestamp>
                <maven.build.timestamp.format>yyyy</maven.build.timestamp.format>
+               <maven.compiler.source>1.8</maven.compiler.source>
+               <maven.compiler.target>1.8</maven.compiler.target>
        </properties>

        <repositories>
@@ -135,6 +137,12 @@
                        <groupId>org.jvnet.jaxb2.maven2</groupId>
                        <artifactId>maven-jaxb2-plugin</artifactId>
                        <version>0.9.0</version>
+                       <exclusions>
+                               <exclusion>
+                                       <groupId>javax.xml.bind</groupId>
+                                       <artifactId>jsr173_api</artifactId>
+                               </exclusion>
+                       </exclusions>
                </dependency>
                <dependency>
                        <groupId>org.jvnet.jaxb2_commons</groupId>

Currently, the Connection dialog has a field "User ID" which is in fact used as 
the MQTT connection Client ID. This is very confusing. I did not want 
authentication so I cleared this value, but then the connection failed with the 
error in the log "Null Client ID" - in fact this is a REQUIRED field. It would 
also be a good idea to autogenerate a random seed for this value in case a user 
wants to have multiple instances of mqtt-spy with multiple connections to the 
same broker.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
0.1.6beta

Please provide any additional information below.
I find the text box is too small, and if you miss with you mouse aim and click 
jest next to the search text box then the whole panel collapses.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

RMB options in edit mode for Publications or Subscriptions are white on white 
text.

Add a possibility to define scripts and start them automatically on opening the 
connection.

This will require configuration and UI changes.

What steps will reproduce the problem?
1. Subscribe to /UK/+/+/BB1/ASM_01/A/modelstate in BB

When I tunnel to subscribe to the topics with unencoded content in the land 
beyond XCS ;-) I start to hear beeps. I think this is because of message 
content.


What is the expected output? What do you see instead?
Expected : Silence. Instead : Noise. :-)

What version of the product are you using? On what operating system?
Latest

Please provide any additional information below.

What steps will reproduce the problem?
1. Subscribe to a topic
2. Receive messages (I receive 1 message every 10 seconds)
3. Note the count go up for "Messages" in the "Received messages summary" panel

What is the expected output? What do you see instead?
After the message count reach 5000, next message should increase the counter to 
5001
For every message after 5000, the label flickers and stays at 5000

What version of the product are you using? On what operating system?
Not sure which version . How do I find out? OS: Windows 8.1

Please provide any additional information below.

What steps will reproduce the problem?
1. Load mqtt-spy v0.0.11 with existing config and it fails to connect
2.
3.

What is the expected output? What do you see instead?
Config was working with previous version (v0.0.10) now I get the following 
error in the log;

2014-09-29 09:24:06,378 WARN  [MQTT Rec: mqtt-spy-mqttwarn   ] 
[MqttConnectionResultHandler   ]  - Connecting to 192.168.1.21 failed
Not authorized to connect (5)
    at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:24)
    at org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:773)
    at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:110)
    at java.lang.Thread.run(Unknown Source)

What version of the product are you using? On what operating system?
v0.0.11 (build 41)

Please provide any additional information below.
I am able to connect to the broker using the same username/password via the 
standard mosquitto-sub client. The mosquitto logs show no sign of any error, I 
just get;

Sep 29 09:12:03 weka mosquitto[20448]: New connection from 192.168.1.25 on port 
1883.

Subscription tab pane shouldn't resize itself based on the number/size of tabs.

It doesn't come back to the original size when tabs are removed.

What steps will reproduce the problem?
1. Select detailed perspective
2. Send a message with QOS=2 to RabbitMQ
3. Watch it disconnect!

What is the expected output? What do you see instead?
I would expect, if I am subscribed to the message I send, to see it come back, 
instead the MQTT-spy momentarily disconnects from the server-  the message 
never goes anywhere.

What version of the product are you using? On what operating system?
Latest of just a couple of days ago - on a Windows 7 PC. MQTT works beautifully 
otherwise.

Please provide any additional information below.
On another tab talking to MOSQUITTO the unit does not disconnect - but QOS=2 
appears to have no effect - just seems to act like QOS=0. I'd assumed that the 
message would get through even if the subscription came through after the 
message was sent. Could be me - could be RabbitMQ but I thought I'd better 
bring this to your attention.

When too many topics & messages are being received for a subscription (e.g. #), 
the application struggles to cope with the load.

Most likely too much work is done in the JavaFX threads.

What steps will reproduce the problem?
1. Highlight some text in the Data window
2. Wait for another message to arrive
3. Highlight disappears

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
0.0.9

Please provide any additional information below.

Message payload is not properly displayed in the message pane. Closing the 
subscription tab and creating a new one fixes that.

Seen in 0.1.9 beta.

First of all, I love mqtt-spy. It's brilliant and the person who wrote it must 
be a visionary genius. I may even make a donation next pay day :-)

What steps will reproduce the problem?
1. Create several config files
2. Run with the default config from your home folder
3. Try to load a different config file. You can't (?)

What version of the product are you using? On what operating system?
0.0.9

Please provide any additional information below.

I'm looking at my mqtt-spy. and I have the default config loaded. I'd like to 
switch to another. Configuration -> Load file is greyed out. 

Why ?

At the moment mqtt-spy is a jar file, in order to run it you need Java 8 
installed.

It would be much easier if you could provide binaries using the JavaFX Native 
Packaging 
(https://blogs.oracle.com/talkingjavadeployment/entry/native_packaging_for_javaf
x)

Thanks,
Christian

Currently when you are on a broker tab by default the 'Subscriptions and 
received messages' pane is huge and the 'received messages summary' pane is 
small. It would be nice to make the 'received messages summary' pane bigger so 
I can see all the topics. Currently you can resize the panes but this has to be 
done for each topic.

See attachment for example.

I'd love to try mqtt-spy but can't sort out how to run it.

It appears that what is downloaded is a zip file (but with no zip suffix so I 
had to discover that).

I've unzipped the file and now have META-INF, org and pl subdirectories.

Now what do I run and how do I run it?  I have a java runtime on a linux server 
system with no gui.

I'm not java knowledgeable (obviously).

In the configuration file you can specify subscription topics, however the app 
will not automatically subscribe to these. You have to right click on each tab 
and re-subscribe.

Maybe add a new xml parameter for each subscription to automatically subscribe 
to topic on loading the app.

What steps will reproduce the problem?
1. Load up MQTT-SPY
2. Double click upon the column resizer for the 'Topic' column


What is the expected output? What do you see instead?

Expected is that the Topic column will resize to fit the content but all of the 
remaining columns remain visible. In practice, the Topic column does resize but 
then obscures the 'Last Received' column as per the attached image.


What version of the product are you using? On what operating system?

Living on the edge! - 0.1.3 beta (build 18) on Windows 7.


Please provide any additional information below.

Screenshot attached.

What steps will reproduce the problem?

1. Start mqtt-spy
2. Try to expand the scripted publications pane

What is the expected output? What do you see instead?

The pane doesn't open and close properly - you have to click off the window for 
it to update.

https://www.youtube.com/watch?v=1nWctj0mvgw

It shouldn't be possible to create duplicate subscriptions.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.
... so that I don't have to keep resizing the bottom panel each time I connect 
to a server. Thanks!

When auto-search is enabled, and messages are not matched, the current message 
index might start going up, whereas the total number of messages available for 
browsing stays the same -> (Message 19/5).

Found in 0.0.6.

Needed for those with locked down brokers, i.e. no anonymous connections 
allowed.

Expand subscription tab's context menu to add/remove the subscription from the 
configuration file.

Make any XML written to files formatted, with new lines and indentation.

This should apply to the configuration and statistics files.

The daemon incorrectly interprets the encoding settings.

boolean encoded = MessageLogEnum.XML_WITH_ENCODED_PAYLOAD.equals(messageLog);

Rather than comparing the messageLog object, it should get value from it and 
then compare.

Put something into the "Data" field for publications or receive a message on an 
active subscription so that the "Data" field gets populated.

In either case, the text is blurred. 

Each field is defined as a JavaFx TextArea.

When no connection is created/selected, the 'Open connection' button should be 
disabled.