Determining errors
How does one determine if an error occurred when using the Java Messenger
interface?
I am trying to send messages to an Artemis broker using basically the Send.java
and Recv.java examples from https://github.com/apache/qpid-proton.git, with
some extra logging. When I run Recv, I see a connection being made on the
broker, and I can send messages to the broker using other (non-AMQP) protocols.
I do not see a connection when I run Send. In neither case are messages read
nor written. They are not read, even if I send messages (successfully) with
another protocol.
When I run Send with finest logging enabled, I see this output:
Mar 09, 2016 4:32:28 PM org.apache.qpid.proton.messenger.impl.MessengerImpl put
FINE: MessengerImpl [_name=0ab8f4c2-66e4-4eb8-9b7e-23cfea723eaa] about to put
message: Message{properties=Properties{messageId=null, userId=null,
to='amqp://username:password@192.168.99.100/jms.queue.DLQ',
subject='jms.queue.DLQ', replyTo='null', correlationId=null, contentType=null,
contentEncoding=null, absoluteExpiryTime=null, creationTime=null,
groupId='null', groupSequence=null, replyToGroupId='null'}body=AmqpValue{Hello
World!}}
Mar 09, 2016 4:32:28 PM org.apache.qpid.proton.messenger.impl.MessengerImpl
getLink
FINE: Connecting to 192.168.99.100:5672
Mar 09, 2016 4:32:28 PM org.apache.qpid.proton.messenger.impl.MessengerImpl
pumpOut
FINE: Sending on delivery: DeliveryImpl [_tag=[49],
_link=org.apache.qpid.proton.engine.impl.SenderImpl@7e4e1fca,
_deliveryState=null, _settled=false, _remoteSettled=false,
_remoteDeliveryState=null, _flags=0, _defaultDeliveryState=null,
_transportDelivery=null, _dataSize=0, _complete=false, _updated=false,
_done=false, _offset=0]
Mar 09, 2016 4:32:28 PM org.apache.qpid.proton.example.Send run
INFO: Sending message
Mar 09, 2016 4:32:28 PM org.apache.qpid.proton.messenger.impl.MessengerImpl send
FINE: MessengerImpl [_name=0ab8f4c2-66e4-4eb8-9b7e-23cfea723eaa] about to send
Mar 09, 2016 4:32:29 PM org.apache.qpid.proton.example.Send lambda$run$0
INFO: Status of Hello World!: UNKNOWN
Mar 09, 2016 4:32:34 PM org.apache.qpid.proton.example.Send lambda$run$0
INFO: Status of Hello World!: UNKNOWN
Mar 09, 2016 4:32:39 PM org.apache.qpid.proton.example.Send lambda$run$0
...
Mar 09, 2016 4:33:29 PM org.apache.qpid.proton.messenger.impl.MessengerImpl
processActive
FINE: Processing active connector ConnectorImpl
[_channel=java.nio.channels.SocketChannel[connected local=/192.168.99.1:49518
remote=/192.168.99.100:5672]]
Mar 09, 2016 4:33:29 PM org.apache.qpid.proton.example.Send run
INFO: Sent, stopping
Mar 09, 2016 4:33:29 PM org.apache.qpid.proton.messenger.impl.MessengerImpl stop
FINE: MessengerImpl [_name=0ab8f4c2-66e4-4eb8-9b7e-23cfea723eaa] about to stop
Mar 09, 2016 4:33:29 PM org.apache.qpid.proton.example.Send run
INFO: Stopped
The messages from the lambda are printing messenger.getStatus for the tracker
for the message that was sent.
Running Recv gives this output:
Mar 09, 2016 3:57:14 PM org.apache.qpid.proton.example.Recv run
INFO: Subscribing to amqp://username:password@192.168.99.100/jms.queue.DLQ
Mar 09, 2016 3:57:14 PM org.apache.qpid.proton.messenger.impl.MessengerImpl
subscribe
FINE: MessengerImpl [_name=e3b2069e-54d4-415b-a342-4bf0cc98dcdd] about to
subscribe to source amqp://rspace:dpass@192.168.99.100/jms.queue.DLQ
Mar 09, 2016 3:57:14 PM org.apache.qpid.proton.messenger.impl.MessengerImpl
getLink
FINE: Connecting to 192.168.99.100:5672
Mar 09, 2016 3:57:14 PM org.apache.qpid.proton.example.Recv run
INFO: Calling recv
Mar 09, 2016 3:58:15 PM org.apache.qpid.proton.messenger.impl.MessengerImpl
processActive
FINE: Processing active connector ConnectorImpl
[_channel=java.nio.channels.SocketChannel[connected local=/192.168.99.1:62376
remote=/192.168.99.100:5672]]
Mar 09, 2016 3:58:15 PM org.apache.qpid.proton.example.Recv run
INFO: Incoming: 0
The broker is running at 192.168.99.100 on port 5672, and there is both a queue
and an address named jms.queue.DLQ. (This is an AMQP queue that is used for
JMS messaging, but I get simlar results with non-JMS queues and addresses.)
Clearly, something is going wrong, but I cannot find any way to get information
about what it is. I have also done things like change the IP address and the
queue name to invalid values, and it does not seem to have any effect.
Where do I need to look to get this information?
Troy
[jira] [Resolved] (PROTON-1157) Reactor sends messages in the clear if ssl is requested by not available.
[ https://issues.apache.org/jira/browse/PROTON-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1157. Resolution: Fixed Assignee: Ken Giusti (was: Gordon Sim) > Reactor sends messages in the clear if ssl is requested by not available. > - > > Key: PROTON-1157 > URL: https://issues.apache.org/jira/browse/PROTON-1157 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.13.0 > > > See > https://github.com/apache/qpid-proton/blob/master/proton-c/bindings/python/proton/reactor.py#L529 > If 'amqps:' is specified and the SSL libraries are not available the client > will use an unsecured connection instead. This is done silently so the user > is not aware of the security violation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1157) Reactor sends messages in the clear if ssl is requested by not available.
[ https://issues.apache.org/jira/browse/PROTON-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188059#comment-15188059 ] ASF subversion and git services commented on PROTON-1157: - Commit a0585851e1e8ed9678496e38278f4a7554d03636 in qpid-proton's branch refs/heads/master from [~kgiusti] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=a058585 ] PROTON-1157: fail if amqps: scheme is specified but SSL is not available > Reactor sends messages in the clear if ssl is requested by not available. > - > > Key: PROTON-1157 > URL: https://issues.apache.org/jira/browse/PROTON-1157 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Ken Giusti >Assignee: Gordon Sim >Priority: Blocker > Fix For: 0.13.0 > > > See > https://github.com/apache/qpid-proton/blob/master/proton-c/bindings/python/proton/reactor.py#L529 > If 'amqps:' is specified and the SSL libraries are not available the client > will use an unsecured connection instead. This is done silently so the user > is not aware of the security violation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1157) Reactor sends messages in the clear if ssl is requested by not available.
[ https://issues.apache.org/jira/browse/PROTON-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187936#comment-15187936 ] Ken Giusti commented on PROTON-1157: Reviewboard: https://reviews.apache.org/r/44591/ > Reactor sends messages in the clear if ssl is requested by not available. > - > > Key: PROTON-1157 > URL: https://issues.apache.org/jira/browse/PROTON-1157 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Ken Giusti >Assignee: Gordon Sim >Priority: Blocker > Fix For: 0.13.0 > > > See > https://github.com/apache/qpid-proton/blob/master/proton-c/bindings/python/proton/reactor.py#L529 > If 'amqps:' is specified and the SSL libraries are not available the client > will use an unsecured connection instead. This is done silently so the user > is not aware of the security violation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-1157) Reactor sends messages in the clear if ssl is requested by not available.
[ https://issues.apache.org/jira/browse/PROTON-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1157: Assignee: Gordon Sim > Reactor sends messages in the clear if ssl is requested by not available. > - > > Key: PROTON-1157 > URL: https://issues.apache.org/jira/browse/PROTON-1157 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Ken Giusti >Assignee: Gordon Sim >Priority: Blocker > Fix For: 0.13.0 > > > See > https://github.com/apache/qpid-proton/blob/master/proton-c/bindings/python/proton/reactor.py#L529 > If 'amqps:' is specified and the SSL libraries are not available the client > will use an unsecured connection instead. This is done silently so the user > is not aware of the security violation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PROTON-1157) Reactor sends messages in the clear if ssl is requested by not available.
Ken Giusti created PROTON-1157: -- Summary: Reactor sends messages in the clear if ssl is requested by not available. Key: PROTON-1157 URL: https://issues.apache.org/jira/browse/PROTON-1157 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.12.0 Reporter: Ken Giusti Priority: Blocker Fix For: 0.13.0 See https://github.com/apache/qpid-proton/blob/master/proton-c/bindings/python/proton/reactor.py#L529 If 'amqps:' is specified and the SSL libraries are not available the client will use an unsecured connection instead. This is done silently so the user is not aware of the security violation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1156) Building C++ binding causes VS2008 to ICE
[
https://issues.apache.org/jira/browse/PROTON-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187535#comment-15187535
]
Andrew Stitcher commented on PROTON-1156:
-
Building on a different box I get an ICE inside a MS header file instead
(utility.h) So I'm not clear if we can actually figure out which is the
responsible file.
> Building C++ binding causes VS2008 to ICE
> -
>
> Key: PROTON-1156
> URL: https://issues.apache.org/jira/browse/PROTON-1156
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
>Affects Versions: 0.13.0
> Environment: Windows Visual Studio 2008 (VS9)
>Reporter: Andrew Stitcher
>Assignee: Cliff Jansen
>
> {noformat}
> 3>c:\jenkins\workspace\proton-c-master-windows\rh-qpid-proton\proton-c\bindings\cpp\src\terminus.cpp(29)
> : fatal error C1001: An internal error has occurred in the compiler.
> 3>(compiler file
> 'f:\dd\vctools\compiler\utc\src\p2\main.c[0x6C510CA6:0x0010]', line 182)
> 3> To work around this problem, try simplifying or changing the program near
> the locations listed above.
> 3>Please choose the Technical Support command on the Visual C++
> 3> Help menu, or open the Technical Support help file for more information
> 3>Internal Compiler Error in C:\Program Files\Microsoft Visual Studio
> 9.0\VC\bin\cl.exe. You will be prompted to send an error report to Microsoft
> later.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (PROTON-1155) [proton-c] Add allowed_mechs to BlockingConnection constructor
[
https://issues.apache.org/jira/browse/PROTON-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved PROTON-1155.
---
Resolution: Fixed
> [proton-c] Add allowed_mechs to BlockingConnection constructor
> --
>
> Key: PROTON-1155
> URL: https://issues.apache.org/jira/browse/PROTON-1155
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: 0.12.0
>Reporter: Ganesh Murthy
>Priority: Minor
>
> In the Proton Python binding, currently there is no way to pass in
> allowed_mechs to BlockingConnection's constructor
> BlockingConnection's constructor should take in an allowed_mechs parameter.
> The Container object has a connect function
> {code}
> def connect(self, url=None, urls=None, address=None, handler=None,
> reconnect=None, heartbeat=None, ssl_domain=None, **kwargs):
> {code}
> The above function already sets the allowed_mechs on the Connector
> {code}
> connector.allowed_mechs = kwargs.get('allowed_mechs', self.allowed_mechs)
> {code}
> So BlockingConnection just needs to pass in the allowed_mechs and the rest is
> take care of by the Container
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PROTON-1156) Building C++ binding causes VS2008 to ICE
[
https://issues.apache.org/jira/browse/PROTON-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187399#comment-15187399
]
Chuck Rolke commented on PROTON-1156:
-
terminus.cpp will compile with an unacceptable code change but then the ICE
moves to some other module.
{noformat}
-terminus::terminus(pn_terminus_t* t) :
-object_(t), properties_(pn_terminus_properties(t)),
filter_(pn_terminus_filter(t))
-{}
+terminus::terminus(pn_terminus_t* t)
+{ object_ = t;
+properties_ = pn_terminus_properties(t);
+filter_ = pn_terminus_filter(t);
+}
{noformat}
This code has been around for a while and the error is probably a result of
changes to included files.
I'm all for retiring VS2008 support. Do we call for a vote?
> Building C++ binding causes VS2008 to ICE
> -
>
> Key: PROTON-1156
> URL: https://issues.apache.org/jira/browse/PROTON-1156
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
>Affects Versions: 0.13.0
> Environment: Windows Visual Studio 2008 (VS9)
>Reporter: Andrew Stitcher
>Assignee: Cliff Jansen
>
> {noformat}
> 3>c:\jenkins\workspace\proton-c-master-windows\rh-qpid-proton\proton-c\bindings\cpp\src\terminus.cpp(29)
> : fatal error C1001: An internal error has occurred in the compiler.
> 3>(compiler file
> 'f:\dd\vctools\compiler\utc\src\p2\main.c[0x6C510CA6:0x0010]', line 182)
> 3> To work around this problem, try simplifying or changing the program near
> the locations listed above.
> 3>Please choose the Technical Support command on the Visual C++
> 3> Help menu, or open the Technical Support help file for more information
> 3>Internal Compiler Error in C:\Program Files\Microsoft Visual Studio
> 9.0\VC\bin\cl.exe. You will be prompted to send an error report to Microsoft
> later.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PROTON-1155) [proton-c] Add allowed_mechs to BlockingConnection constructor
[
https://issues.apache.org/jira/browse/PROTON-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187378#comment-15187378
]
ASF subversion and git services commented on PROTON-1155:
-
Commit 747ee17215d520b862c81ed4d15949e96da5a6a2 in qpid-proton's branch
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=747ee17 ]
PROTON-1155 - Modified BlockingConnection to pass **kwargs to the
container.connect call
> [proton-c] Add allowed_mechs to BlockingConnection constructor
> --
>
> Key: PROTON-1155
> URL: https://issues.apache.org/jira/browse/PROTON-1155
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: 0.12.0
>Reporter: Ganesh Murthy
>Priority: Minor
>
> In the Proton Python binding, currently there is no way to pass in
> allowed_mechs to BlockingConnection's constructor
> BlockingConnection's constructor should take in an allowed_mechs parameter.
> The Container object has a connect function
> {code}
> def connect(self, url=None, urls=None, address=None, handler=None,
> reconnect=None, heartbeat=None, ssl_domain=None, **kwargs):
> {code}
> The above function already sets the allowed_mechs on the Connector
> {code}
> connector.allowed_mechs = kwargs.get('allowed_mechs', self.allowed_mechs)
> {code}
> So BlockingConnection just needs to pass in the allowed_mechs and the rest is
> take care of by the Container
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
