[jira] [Created] (PROTON-244) NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting qpid-client to qpid-proton in ActiveMQ

[Jan-Helge Bergesen (JIRA)]

Jan-Helge Bergesen created PROTON-244:
-

 Summary: NPE in org/apache/qpid/proton/jms/InboundTransformer when 
connecting qpid-client to qpid-proton in ActiveMQ
 Key: PROTON-244
 URL: https://issues.apache.org/jira/browse/PROTON-244
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-j
Affects Versions: 0.3
Reporter: Jan-Helge Bergesen


Connecting a ConnectionFactory from qpid-amqp-1-0-client-jms version 0.20 to 
ActiveMQ 5.8.0, yields NPE:

{code}
org.apache.activemq.transport.amqp.AmqpProtocolException: Could not process 
AMQP commands
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:245)
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter.onAMQPData(AmqpProtocolConverter.java:151)
at 
org.apache.activemq.transport.amqp.AmqpTransportFilter.onCommand(AmqpTransportFilter.java:94)
at 
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at 
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at 
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at 
org.apache.qpid.proton.jms.InboundTransformer.populateMessage(InboundTransformer.java:146)
at 
org.apache.qpid.proton.jms.AMQPNativeInboundTransformer.transform(AMQPNativeInboundTransformer.java:37)
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter$ProducerContext.onMessage(AmqpProtocolConverter.java:454)
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter$BaseProducerContext.onDelivery(AmqpProtocolConverter.java:435)
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:215)
... 6 more
{code}

Looking at 
https://github.com/apache/qpid-proton/blob/trunk/proton-j/contrib/proton-jms/src/main/java/org/apache/qpid/proton/jms/InboundTransformer.java#L146

It would seems that qpid-amqp-1-0-client-jms sends a message with header 
"x-opt-jms-type" with value NULL.

This might very well be an invalid combination of client/broker setup -- 
however, the proton-jms code could possibly benefit from utilizing 
{code}String.valueOf(..){code} instead of {code}getValue().toString(){code} (or 
similar) :-)


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (PROTON-244) NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting qpid-client to qpid-proton in ActiveMQ

[Jan-Helge Bergesen (JIRA)]

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

Jan-Helge Bergesen updated PROTON-244:
--

Description: 
Connecting a ConnectionFactory from qpid-amqp-1-0-client-jms version 0.20 to 
ActiveMQ 5.8.0, yields NPE:

org.apache.activemq.transport.amqp.AmqpProtocolException: Could not process 
AMQP commands
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:245)
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter.onAMQPData(AmqpProtocolConverter.java:151)
at 
org.apache.activemq.transport.amqp.AmqpTransportFilter.onCommand(AmqpTransportFilter.java:94)
at 
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at 
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at 
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at 
org.apache.qpid.proton.jms.InboundTransformer.populateMessage(InboundTransformer.java:146)
at 
org.apache.qpid.proton.jms.AMQPNativeInboundTransformer.transform(AMQPNativeInboundTransformer.java:37)
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter$ProducerContext.onMessage(AmqpProtocolConverter.java:454)
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter$BaseProducerContext.onDelivery(AmqpProtocolConverter.java:435)
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:215)
... 6 more

Looking at 
https://github.com/apache/qpid-proton/blob/trunk/proton-j/contrib/proton-jms/src/main/java/org/apache/qpid/proton/jms/InboundTransformer.java#L146

It would seems that qpid-amqp-1-0-client-jms sends a message with header 
"x-opt-jms-type" with value NULL.

This might very well be an invalid combination of client/broker setup -- 
however, the proton-jms code could possibly benefit from utilizing 
String.valueOf(..) instead of getValue().toString() (or similar) :-)


  was:
Connecting a ConnectionFactory from qpid-amqp-1-0-client-jms version 0.20 to 
ActiveMQ 5.8.0, yields NPE:

{code}
org.apache.activemq.transport.amqp.AmqpProtocolException: Could not process 
AMQP commands
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:245)
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter.onAMQPData(AmqpProtocolConverter.java:151)
at 
org.apache.activemq.transport.amqp.AmqpTransportFilter.onCommand(AmqpTransportFilter.java:94)
at 
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at 
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at 
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at 
org.apache.qpid.proton.jms.InboundTransformer.populateMessage(InboundTransformer.java:146)
at 
org.apache.qpid.proton.jms.AMQPNativeInboundTransformer.transform(AMQPNativeInboundTransformer.java:37)
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter$ProducerContext.onMessage(AmqpProtocolConverter.java:454)
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter$BaseProducerContext.onDelivery(AmqpProtocolConverter.java:435)
at 
org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:215)
... 6 more
{code}

Looking at 
https://github.com/apache/qpid-proton/blob/trunk/proton-j/contrib/proton-jms/src/main/java/org/apache/qpid/proton/jms/InboundTransformer.java#L146

It would seems that qpid-amqp-1-0-client-jms sends a message with header 
"x-opt-jms-type" with value NULL.

This might very well be an invalid combination of client/broker setup -- 
however, the proton-jms code could possibly benefit from utilizing 
{code}String.valueOf(..){code} instead of {code}getValue().toString(){code} (or 
similar) :-)



> NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting 
> qpid-client to qpid-proton in ActiveMQ
> ---
>
> Key: PROTON-244
> URL: https://issues.apache.org/jira/browse/PROTON-244
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: 0.3
>Reporter: Jan-Helge Bergesen
>
> Connecting a ConnectionFactory from qpid-amqp-1-0-client-jms version 0.20 to 
> ActiveMQ 5.8.0, yields NPE:
> org.apache.activemq.transport.amqp.AmqpProtocolException: Could not process 
> AMQP commands
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.o

[jira] [Updated] (PROTON-244) NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting qpid-client to qpid-proton in ActiveMQ

[Jan-Helge Bergesen (JIRA)]

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

Jan-Helge Bergesen updated PROTON-244:
--

Attachment: PROTON-244.logexcerpt.txt

Attached log excerpt containing TRACE of amqp wireformat/transport

> NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting 
> qpid-client to qpid-proton in ActiveMQ
> ---
>
> Key: PROTON-244
> URL: https://issues.apache.org/jira/browse/PROTON-244
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: 0.3
>Reporter: Jan-Helge Bergesen
> Attachments: PROTON-244.logexcerpt.txt
>
>
> Connecting a ConnectionFactory from qpid-amqp-1-0-client-jms version 0.20 to 
> ActiveMQ 5.8.0, yields NPE:
> org.apache.activemq.transport.amqp.AmqpProtocolException: Could not process 
> AMQP commands
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:245)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onAMQPData(AmqpProtocolConverter.java:151)
> at 
> org.apache.activemq.transport.amqp.AmqpTransportFilter.onCommand(AmqpTransportFilter.java:94)
> at 
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.NullPointerException
> at 
> org.apache.qpid.proton.jms.InboundTransformer.populateMessage(InboundTransformer.java:146)
> at 
> org.apache.qpid.proton.jms.AMQPNativeInboundTransformer.transform(AMQPNativeInboundTransformer.java:37)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter$ProducerContext.onMessage(AmqpProtocolConverter.java:454)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter$BaseProducerContext.onDelivery(AmqpProtocolConverter.java:435)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:215)
> ... 6 more
> Looking at 
> https://github.com/apache/qpid-proton/blob/trunk/proton-j/contrib/proton-jms/src/main/java/org/apache/qpid/proton/jms/InboundTransformer.java#L146
> It would seems that qpid-amqp-1-0-client-jms sends a message with header 
> "x-opt-jms-type" with value NULL.
> This might very well be an invalid combination of client/broker setup -- 
> however, the proton-jms code could possibly benefit from utilizing 
> String.valueOf(..) instead of getValue().toString() (or similar) :-)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (PROTON-244) NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting qpid-client to qpid-proton in ActiveMQ

[Jan-Helge Bergesen (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582084#comment-13582084
 ] 

Jan-Helge Bergesen commented on PROTON-244:
---

When exception occurr, the client will hang:

Daemon Thread [Camel (wms) thread #0 - 
JmsConsumer[WMSTransactionTopicDestination]] (Suspended) 
waiting for: ConnectionEndpoint  (id=71)
Object.wait(long) line: not available [native method]   
ConnectionEndpoint(Object).wait() line: 485 
Sender.close() line: 325
MessageProducerImpl.close() line: 159   
JmsUtils.closeMessageProducer(MessageProducer) line: 128
JmsConfiguration$CamelJmsTemplate.doSendToDestination(Destination, 
MessageCreator, MessageSentCallback, Session) line: 227  

JmsConfiguration$CamelJmsTemplate.access$100(JmsConfiguration$CamelJmsTemplate, 
Destination, MessageCreator, MessageSentCallback, Session) line: 159
JmsConfiguration$CamelJmsTemplate$1.doInJms(Session) line: 173  

JmsConfiguration$CamelJmsTemplate(JmsTemplate).execute(SessionCallback, 
boolean) line: 466   
JmsConfiguration$CamelJmsTemplate.send(String, MessageCreator, 
MessageSentCallback) line: 170   
JmsProducer.doSend(boolean, String, Destination, MessageCreator, 
MessageSentCallback) line: 402 
JmsProducer.processInOnly(Exchange, AsyncCallback) line: 356
JmsProducer.process(Exchange, AsyncCallback) line: 132  
AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) 
line: 73  
SendProcessor$2.doInAsyncProducer(Producer, AsyncProcessor, Exchange, 
ExchangePattern, AsyncCallback) line: 122 
ProducerCache.doInAsyncProducer(Endpoint, Exchange, ExchangePattern, 
AsyncCallback, AsyncProducerCallback) line: 298
SendProcessor.process(Exchange, AsyncCallback) line: 117
AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) 
line: 73  
InstrumentationProcessor(DelegateAsyncProcessor).processNext(Exchange, 
AsyncCallback) line: 99  
InstrumentationProcessor(DelegateAsyncProcessor).process(Exchange, 
AsyncCallback) line: 90  
InstrumentationProcessor.process(Exchange, AsyncCallback) line: 73  
AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) 
line: 73  
TraceInterceptor(DelegateAsyncProcessor).processNext(Exchange, 
AsyncCallback) line: 99  
TraceInterceptor(DelegateAsyncProcessor).process(Exchange, 
AsyncCallback) line: 90  
TraceInterceptor.process(Exchange, AsyncCallback) line: 91  
AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) 
line: 73  

DefaultErrorHandler(RedeliveryErrorHandler).processErrorHandler(Exchange, 
AsyncCallback, RedeliveryErrorHandler$RedeliveryData) line: 334   
DefaultErrorHandler(RedeliveryErrorHandler).process(Exchange, 
AsyncCallback) line: 220  
RouteContextProcessor.processNext(Exchange, AsyncCallback) line: 45 
RouteContextProcessor(DelegateAsyncProcessor).process(Exchange, 
AsyncCallback) line: 90 
DefaultChannel.process(Exchange, AsyncCallback) line: 303   
AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) 
line: 73  
Pipeline.process(Exchange, Exchange, AsyncCallback, 
Iterator, AsyncProcessor) line: 117  
Pipeline.process(Exchange, AsyncCallback) line: 80  
AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) 
line: 73  
ChoiceProcessor.process(Exchange, AsyncCallback) line: 85   
AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) 
line: 73  
InstrumentationProcessor(DelegateAsyncProcessor).processNext(Exchange, 
AsyncCallback) line: 99  
InstrumentationProcessor(DelegateAsyncProcessor).process(Exchange, 
AsyncCallback) line: 90  
InstrumentationProcessor.process(Exchange, AsyncCallback) line: 73  
AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) 
line: 73  
TraceInterceptor(DelegateAsyncProcessor).processNext(Exchange, 
AsyncCallback) line: 99  
TraceInterceptor(DelegateAsyncProcessor).process(Exchange, 
AsyncCallback) line: 90  
TraceInterceptor.process(Exchange, AsyncCallback) line: 91  
AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) 
line: 73  

DefaultErrorHandler(RedeliveryErrorHandler).processErrorHandler(Exchange, 
AsyncCallback, RedeliveryErrorHandler$RedeliveryData) line: 334   
DefaultErrorHandler(RedeliveryErrorHandler).process(Exchange, 
AsyncCallback) line: 220  
RouteContextProcessor.processNext(Exchange, AsyncCallback) line: 45 
RouteContextProcessor(DelegateAsyncProcessor).process(Exchange, 
AsyncCall

[jira] [Updated] (PROTON-244) NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting qpid-client to qpid-proton in ActiveMQ

[Jan-Helge Bergesen (JIRA)]

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

Jan-Helge Bergesen updated PROTON-244:
--

Labels: robustness  (was: )

> NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting 
> qpid-client to qpid-proton in ActiveMQ
> ---
>
> Key: PROTON-244
> URL: https://issues.apache.org/jira/browse/PROTON-244
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: 0.3
>Reporter: Jan-Helge Bergesen
>  Labels: robustness
> Attachments: PROTON-244.logexcerpt.txt
>
>
> Connecting a ConnectionFactory from qpid-amqp-1-0-client-jms version 0.20 to 
> ActiveMQ 5.8.0, yields NPE:
> org.apache.activemq.transport.amqp.AmqpProtocolException: Could not process 
> AMQP commands
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:245)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onAMQPData(AmqpProtocolConverter.java:151)
> at 
> org.apache.activemq.transport.amqp.AmqpTransportFilter.onCommand(AmqpTransportFilter.java:94)
> at 
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.NullPointerException
> at 
> org.apache.qpid.proton.jms.InboundTransformer.populateMessage(InboundTransformer.java:146)
> at 
> org.apache.qpid.proton.jms.AMQPNativeInboundTransformer.transform(AMQPNativeInboundTransformer.java:37)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter$ProducerContext.onMessage(AmqpProtocolConverter.java:454)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter$BaseProducerContext.onDelivery(AmqpProtocolConverter.java:435)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:215)
> ... 6 more
> Looking at 
> https://github.com/apache/qpid-proton/blob/trunk/proton-j/contrib/proton-jms/src/main/java/org/apache/qpid/proton/jms/InboundTransformer.java#L146
> It would seems that qpid-amqp-1-0-client-jms sends a message with header 
> "x-opt-jms-type" with value NULL.
> This might very well be an invalid combination of client/broker setup -- 
> however, the proton-jms code could possibly benefit from utilizing 
> String.valueOf(..) instead of getValue().toString() (or similar) :-)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: topology: all tests pass!

[Michael Goulish]

1. Yes! I'll do that today.

2. Yes! I just talked to Cliff about ctest.  Something I had already started 
should work well for that.




- Original Message -
From: "Rafael Schloming" 
To: proton@qpid.apache.org
Sent: Tuesday, February 19, 2013 11:35:06 PM
Subject: Re: topology: all tests pass!

Cool, can you rerun this with the update version of the proton-200 -1
patch? (https://reviews.apache.org/r/9503/)

Also,would it make sense to set these tests up to run as part of the new
ctest stuff?

--Rafael

On Tue, Feb 19, 2013 at 2:05 PM, Michael Goulish wrote:

>
> Green across the board.
>
> Same program running in 1, 2, or 3 instances.
> 1 messenger in each process.  No recompile
> needed between tests -- only the command line args
> change.
>
> All possible combinations of 3 or fewer nodes,
> with 0, 1, or 2 (bi-directional) links between each
> pair.  Including single node, with self-loop.
>
> To pass a test, I have to see that all nodes are receiving
> messages simultaneously, and when one node is receiving from
> 2 senders, its incoming messages should be interleaved ( i.e.
> *not* all the messages from node A, followed by all the messages
> from node B ) and getting them in similar proportions from both
> sources.
>
> This is using Proton 0.4 RC1 code, with the "infinite credit"
> patch -- but none of the messengers are actually asking for
> infinite credit.
>
> The tests are easy to re-run for future versions, and I will
> do that.
>
> ... pretty picture attached ...
>
>

[jira] [Commented] (PROTON-244) NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting qpid-client to qpid-proton in ActiveMQ

[Hiram Chirino (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582225#comment-13582225
 ] 

Hiram Chirino commented on PROTON-244:
--

Hi, could you post how you were using the Qpid JMS client?  What kind of 
message you were creating, what fields your were setting etc?

> NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting 
> qpid-client to qpid-proton in ActiveMQ
> ---
>
> Key: PROTON-244
> URL: https://issues.apache.org/jira/browse/PROTON-244
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: 0.3
>Reporter: Jan-Helge Bergesen
>  Labels: robustness
> Attachments: PROTON-244.logexcerpt.txt
>
>
> Connecting a ConnectionFactory from qpid-amqp-1-0-client-jms version 0.20 to 
> ActiveMQ 5.8.0, yields NPE:
> org.apache.activemq.transport.amqp.AmqpProtocolException: Could not process 
> AMQP commands
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:245)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onAMQPData(AmqpProtocolConverter.java:151)
> at 
> org.apache.activemq.transport.amqp.AmqpTransportFilter.onCommand(AmqpTransportFilter.java:94)
> at 
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.NullPointerException
> at 
> org.apache.qpid.proton.jms.InboundTransformer.populateMessage(InboundTransformer.java:146)
> at 
> org.apache.qpid.proton.jms.AMQPNativeInboundTransformer.transform(AMQPNativeInboundTransformer.java:37)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter$ProducerContext.onMessage(AmqpProtocolConverter.java:454)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter$BaseProducerContext.onDelivery(AmqpProtocolConverter.java:435)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:215)
> ... 6 more
> Looking at 
> https://github.com/apache/qpid-proton/blob/trunk/proton-j/contrib/proton-jms/src/main/java/org/apache/qpid/proton/jms/InboundTransformer.java#L146
> It would seems that qpid-amqp-1-0-client-jms sends a message with header 
> "x-opt-jms-type" with value NULL.
> This might very well be an invalid combination of client/broker setup -- 
> however, the proton-jms code could possibly benefit from utilizing 
> String.valueOf(..) instead of getValue().toString() (or similar) :-)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (PROTON-243) 0.4 RC1 libqpid-proton not found

[Rafael H. Schloming (JIRA)]

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

Rafael H. Schloming updated PROTON-243:
---

Fix Version/s: 0.4

> 0.4 RC1 libqpid-proton not found 
> -
>
> Key: PROTON-243
> URL: https://issues.apache.org/jira/browse/PROTON-243
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.4
> Environment: Fedora 18
>Reporter: michael goulish
> Fix For: 0.4
>
>
> All build steps went well, following the README directions, until I got to 
> building the C examples
> here is what happened then:
> ( executive summary: I had to set LD_LIBRARY_PATH to get libqpid-proton to be 
> findable at link time. )
>   cd ../examples/messenger/c
>   cmake .
>   make
>   ./recv &
>   ./recv: error while loading shared libraries: 
> libqpid-proton.so.1: cannot open shared object file: 
> No such file or directory
>   # Uh-oh.
>   ldd recv
> linux-vdso.so.1 =>  (0x7fff0396)
> libqpid-proton.so.1 => not found
> libc.so.6 => /lib64/libc.so.6 (0x7f5dfc48f000)
> /lib64/ld-linux-x86-64.so.2 (0x7f5dfc851000)
>   export LD_LIBRARY_PATH=/usr/lib
>   ./recv &
>   # It's Happy !
>   ./send
>   Address: amqp://0.0.0.0
>   Subject: (no subject)
>   Content: "Hello World!"
>   # Hooray !

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (PROTON-243) 0.4 RC1 libqpid-proton not found

[Rafael H. Schloming (JIRA)]

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

Rafael H. Schloming resolved PROTON-243.


Resolution: Fixed

> 0.4 RC1 libqpid-proton not found 
> -
>
> Key: PROTON-243
> URL: https://issues.apache.org/jira/browse/PROTON-243
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.4
> Environment: Fedora 18
>Reporter: michael goulish
>Assignee: Rafael H. Schloming
> Fix For: 0.4
>
>
> All build steps went well, following the README directions, until I got to 
> building the C examples
> here is what happened then:
> ( executive summary: I had to set LD_LIBRARY_PATH to get libqpid-proton to be 
> findable at link time. )
>   cd ../examples/messenger/c
>   cmake .
>   make
>   ./recv &
>   ./recv: error while loading shared libraries: 
> libqpid-proton.so.1: cannot open shared object file: 
> No such file or directory
>   # Uh-oh.
>   ldd recv
> linux-vdso.so.1 =>  (0x7fff0396)
> libqpid-proton.so.1 => not found
> libc.so.6 => /lib64/libc.so.6 (0x7f5dfc48f000)
> /lib64/ld-linux-x86-64.so.2 (0x7f5dfc851000)
>   export LD_LIBRARY_PATH=/usr/lib
>   ./recv &
>   # It's Happy !
>   ./send
>   Address: amqp://0.0.0.0
>   Subject: (no subject)
>   Content: "Hello World!"
>   # Hooray !

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (PROTON-243) 0.4 RC1 libqpid-proton not found

[Rafael H. Schloming (JIRA)]

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

Rafael H. Schloming reassigned PROTON-243:
--

Assignee: Rafael H. Schloming

> 0.4 RC1 libqpid-proton not found 
> -
>
> Key: PROTON-243
> URL: https://issues.apache.org/jira/browse/PROTON-243
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.4
> Environment: Fedora 18
>Reporter: michael goulish
>Assignee: Rafael H. Schloming
> Fix For: 0.4
>
>
> All build steps went well, following the README directions, until I got to 
> building the C examples
> here is what happened then:
> ( executive summary: I had to set LD_LIBRARY_PATH to get libqpid-proton to be 
> findable at link time. )
>   cd ../examples/messenger/c
>   cmake .
>   make
>   ./recv &
>   ./recv: error while loading shared libraries: 
> libqpid-proton.so.1: cannot open shared object file: 
> No such file or directory
>   # Uh-oh.
>   ldd recv
> linux-vdso.so.1 =>  (0x7fff0396)
> libqpid-proton.so.1 => not found
> libc.so.6 => /lib64/libc.so.6 (0x7f5dfc48f000)
> /lib64/ld-linux-x86-64.so.2 (0x7f5dfc851000)
>   export LD_LIBRARY_PATH=/usr/lib
>   ./recv &
>   # It's Happy !
>   ./send
>   Address: amqp://0.0.0.0
>   Subject: (no subject)
>   Content: "Hello World!"
>   # Hooray !

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (PROTON-244) NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting qpid-client to qpid-proton in ActiveMQ

[Rafael H. Schloming (JIRA)]

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

Rafael H. Schloming reassigned PROTON-244:
--

Assignee: Hiram Chirino

> NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting 
> qpid-client to qpid-proton in ActiveMQ
> ---
>
> Key: PROTON-244
> URL: https://issues.apache.org/jira/browse/PROTON-244
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: 0.3
>Reporter: Jan-Helge Bergesen
>Assignee: Hiram Chirino
>  Labels: robustness
> Attachments: PROTON-244.logexcerpt.txt
>
>
> Connecting a ConnectionFactory from qpid-amqp-1-0-client-jms version 0.20 to 
> ActiveMQ 5.8.0, yields NPE:
> org.apache.activemq.transport.amqp.AmqpProtocolException: Could not process 
> AMQP commands
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:245)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onAMQPData(AmqpProtocolConverter.java:151)
> at 
> org.apache.activemq.transport.amqp.AmqpTransportFilter.onCommand(AmqpTransportFilter.java:94)
> at 
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.NullPointerException
> at 
> org.apache.qpid.proton.jms.InboundTransformer.populateMessage(InboundTransformer.java:146)
> at 
> org.apache.qpid.proton.jms.AMQPNativeInboundTransformer.transform(AMQPNativeInboundTransformer.java:37)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter$ProducerContext.onMessage(AmqpProtocolConverter.java:454)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter$BaseProducerContext.onDelivery(AmqpProtocolConverter.java:435)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:215)
> ... 6 more
> Looking at 
> https://github.com/apache/qpid-proton/blob/trunk/proton-j/contrib/proton-jms/src/main/java/org/apache/qpid/proton/jms/InboundTransformer.java#L146
> It would seems that qpid-amqp-1-0-client-jms sends a message with header 
> "x-opt-jms-type" with value NULL.
> This might very well be an invalid combination of client/broker setup -- 
> however, the proton-jms code could possibly benefit from utilizing 
> String.valueOf(..) instead of getValue().toString() (or similar) :-)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] [Commented] (PROTON-243) 0.4 RC1 libqpid-proton not found

[Rafael Schloming]

This should be fixed now.

--Rafael

On Mon, Feb 18, 2013 at 12:31 PM, Ted Ross (JIRA)  wrote:

>
> [
> https://issues.apache.org/jira/browse/PROTON-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580820#comment-13580820]
>
> Ted Ross commented on PROTON-243:
> -
>
> The shorter version:  When installing 0.4 on a 64-bit system, the
> libraries are installed into the wrong directory (/usr/lib when it should
> be /usr/lib64).
>
>
> > 0.4 RC1 libqpid-proton not found
> > -
> >
> > Key: PROTON-243
> > URL: https://issues.apache.org/jira/browse/PROTON-243
> > Project: Qpid Proton
> >  Issue Type: Bug
> >  Components: proton-c
> >Affects Versions: 0.4
> > Environment: Fedora 18
> >Reporter: michael goulish
> >
> > All build steps went well, following the README directions, until I got
> to building the C examples
> > here is what happened then:
> > ( executive summary: I had to set LD_LIBRARY_PATH to get libqpid-proton
> to be findable at link time. )
> >   cd ../examples/messenger/c
> >   cmake .
> >   make
> >   ./recv &
> >   ./recv: error while loading shared libraries:
> > libqpid-proton.so.1: cannot open shared object file:
> > No such file or directory
> >   # Uh-oh.
> >   ldd recv
> > linux-vdso.so.1 =>  (0x7fff0396)
> > libqpid-proton.so.1 => not found
> > libc.so.6 => /lib64/libc.so.6 (0x7f5dfc48f000)
> > /lib64/ld-linux-x86-64.so.2 (0x7f5dfc851000)
> >   export LD_LIBRARY_PATH=/usr/lib
> >   ./recv &
> >   # It's Happy !
> >   ./send
> >   Address: amqp://0.0.0.0
> >   Subject: (no subject)
> >   Content: "Hello World!"
> >   # Hooray !
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>

Re: topology: all tests pass!

[Michael Goulish]

OK -- all 15 topology tests still pass using the latest version of the P-200 
patch  ( diff3 ).





- Original Message -
From: "Michael Goulish" 
To: proton@qpid.apache.org
Sent: Wednesday, February 20, 2013 9:36:58 AM
Subject: Re: topology: all tests pass!


1. Yes! I'll do that today.

2. Yes! I just talked to Cliff about ctest.  Something I had already started 
should work well for that.




- Original Message -
From: "Rafael Schloming" 
To: proton@qpid.apache.org
Sent: Tuesday, February 19, 2013 11:35:06 PM
Subject: Re: topology: all tests pass!

Cool, can you rerun this with the update version of the proton-200 -1
patch? (https://reviews.apache.org/r/9503/)

Also,would it make sense to set these tests up to run as part of the new
ctest stuff?

--Rafael

On Tue, Feb 19, 2013 at 2:05 PM, Michael Goulish wrote:

>
> Green across the board.
>
> Same program running in 1, 2, or 3 instances.
> 1 messenger in each process.  No recompile
> needed between tests -- only the command line args
> change.
>
> All possible combinations of 3 or fewer nodes,
> with 0, 1, or 2 (bi-directional) links between each
> pair.  Including single node, with self-loop.
>
> To pass a test, I have to see that all nodes are receiving
> messages simultaneously, and when one node is receiving from
> 2 senders, its incoming messages should be interleaved ( i.e.
> *not* all the messages from node A, followed by all the messages
> from node B ) and getting them in similar proportions from both
> sources.
>
> This is using Proton 0.4 RC1 code, with the "infinite credit"
> patch -- but none of the messengers are actually asking for
> infinite credit.
>
> The tests are easy to re-run for future versions, and I will
> do that.
>
> ... pretty picture attached ...
>
>

Re: Qpid Proton 0.4 RC1

[Ken Giusti]

Fails to build on Centos-5 with a swig parse error (Syntax error on input(1)).

Details:

   swig-1.3.29-2.el5

   chokes on the definition of pn_dtag() in include/proton/engine.h:75 - 
specifically does not like the "inline" specifier.

   I can "fix" it by:

  1) remove "inline"
  2) configure cmake to remove the "treat warnings as errors" flag - since 
removing the 'inline' causes a raft of "defined but not used" errors.

Would it be reasonable to move pn_dtag() into engine.c and make it a non-inline 
function?

-K

- Original Message -
> Source is here:
>   http://people.apache.org/~rhs/qpid-proton-0.4rc1/
> 
> Java binaries are here:
>   https://repository.apache.org/content/repositories/orgapacheqpid-239/
> 
> This is the first release after some significant build system
> changes, so
> don't be surprised if there are a few kinks to work out. Please note
> that
> there is now only a single source release for the whole project.
> Please see
> the README for more details and shout if anything is confusing.
> 
> --Rafael
> 

[jira] [Created] (PROTON-245) Use of "inline" function specifier not compatible with older versions of swig

[Ken Giusti (JIRA)]

Ken Giusti created PROTON-245:
-

 Summary: Use of "inline" function specifier not compatible with 
older versions of swig
 Key: PROTON-245
 URL: https://issues.apache.org/jira/browse/PROTON-245
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-c
Reporter: Ken Giusti
Assignee: Rafael H. Schloming


older version of swig - 1.3.29 specifically on Centos 5 - chokes on the 
"inline" function specifier

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (PROTON-245) Use of "inline" function specifier not compatible with older versions of swig

[Ken Giusti (JIRA)]

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

Ken Giusti updated PROTON-245:
--

Attachment: 0001-NO-JIRA-remove-static-inline-incompatible-with-older.patch

Attached patch I've tested against Centos 5 with success.


> Use of "inline" function specifier not compatible with older versions of swig
> -
>
> Key: PROTON-245
> URL: https://issues.apache.org/jira/browse/PROTON-245
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Reporter: Ken Giusti
>Assignee: Rafael H. Schloming
> Attachments: 
> 0001-NO-JIRA-remove-static-inline-incompatible-with-older.patch
>
>
> older version of swig - 1.3.29 specifically on Centos 5 - chokes on the 
> "inline" function specifier

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Qpid Proton 0.4 RC1

[Rafael Schloming]

Sounds reasonable to me.

--Rafael

On Wed, Feb 20, 2013 at 8:31 AM, Ken Giusti  wrote:

> Fails to build on Centos-5 with a swig parse error (Syntax error on
> input(1)).
>
> Details:
>
>swig-1.3.29-2.el5
>
>chokes on the definition of pn_dtag() in include/proton/engine.h:75 -
> specifically does not like the "inline" specifier.
>
>I can "fix" it by:
>
>   1) remove "inline"
>   2) configure cmake to remove the "treat warnings as errors" flag -
> since removing the 'inline' causes a raft of "defined but not used" errors.
>
> Would it be reasonable to move pn_dtag() into engine.c and make it a
> non-inline function?
>
> -K
>
> - Original Message -
> > Source is here:
> >   http://people.apache.org/~rhs/qpid-proton-0.4rc1/
> >
> > Java binaries are here:
> >   https://repository.apache.org/content/repositories/orgapacheqpid-239/
> >
> > This is the first release after some significant build system
> > changes, so
> > don't be surprised if there are a few kinks to work out. Please note
> > that
> > there is now only a single source release for the whole project.
> > Please see
> > the README for more details and shout if anything is confusing.
> >
> > --Rafael
> >
>

Re: Qpid Proton 0.4 RC1

[Rafael Schloming]

It occurs to me there may be #defines you could key off when swig runs so
you could just remove the inline portion for swig.

--Rafael

On Wed, Feb 20, 2013 at 9:17 AM, Rafael Schloming  wrote:

> Sounds reasonable to me.
>
> --Rafael
>
>
> On Wed, Feb 20, 2013 at 8:31 AM, Ken Giusti  wrote:
>
>> Fails to build on Centos-5 with a swig parse error (Syntax error on
>> input(1)).
>>
>> Details:
>>
>>swig-1.3.29-2.el5
>>
>>chokes on the definition of pn_dtag() in include/proton/engine.h:75 -
>> specifically does not like the "inline" specifier.
>>
>>I can "fix" it by:
>>
>>   1) remove "inline"
>>   2) configure cmake to remove the "treat warnings as errors" flag -
>> since removing the 'inline' causes a raft of "defined but not used" errors.
>>
>> Would it be reasonable to move pn_dtag() into engine.c and make it a
>> non-inline function?
>>
>> -K
>>
>> - Original Message -
>> > Source is here:
>> >   http://people.apache.org/~rhs/qpid-proton-0.4rc1/
>> >
>> > Java binaries are here:
>> >   https://repository.apache.org/content/repositories/orgapacheqpid-239/
>> >
>> > This is the first release after some significant build system
>> > changes, so
>> > don't be surprised if there are a few kinks to work out. Please note
>> > that
>> > there is now only a single source release for the whole project.
>> > Please see
>> > the README for more details and shout if anything is confusing.
>> >
>> > --Rafael
>> >
>>
>
>

Re: Qpid Proton 0.4 RC1

[Ken Giusti]

Perhaps, but then we hit multiple "defined but not used" errors, due to the 
"static" usage.  Which complicates the warning configuration (if old swig, 
change warning flags?)

And, of course, since it's in a header, it has to be static or the link fails.

/tried it all

-K

- Original Message -
> It occurs to me there may be #defines you could key off when swig
> runs so
> you could just remove the inline portion for swig.
> 
> --Rafael
> 
> On Wed, Feb 20, 2013 at 9:17 AM, Rafael Schloming 
> wrote:
> 
> > Sounds reasonable to me.
> >
> > --Rafael
> >
> >
> > On Wed, Feb 20, 2013 at 8:31 AM, Ken Giusti 
> > wrote:
> >
> >> Fails to build on Centos-5 with a swig parse error (Syntax error
> >> on
> >> input(1)).
> >>
> >> Details:
> >>
> >>swig-1.3.29-2.el5
> >>
> >>chokes on the definition of pn_dtag() in
> >>include/proton/engine.h:75 -
> >> specifically does not like the "inline" specifier.
> >>
> >>I can "fix" it by:
> >>
> >>   1) remove "inline"
> >>   2) configure cmake to remove the "treat warnings as errors"
> >>   flag -
> >> since removing the 'inline' causes a raft of "defined but not
> >> used" errors.
> >>
> >> Would it be reasonable to move pn_dtag() into engine.c and make it
> >> a
> >> non-inline function?
> >>
> >> -K
> >>
> >> - Original Message -
> >> > Source is here:
> >> >   http://people.apache.org/~rhs/qpid-proton-0.4rc1/
> >> >
> >> > Java binaries are here:
> >> >   https://repository.apache.org/content/repositories/orgapacheqpid-239/
> >> >
> >> > This is the first release after some significant build system
> >> > changes, so
> >> > don't be surprised if there are a few kinks to work out. Please
> >> > note
> >> > that
> >> > there is now only a single source release for the whole project.
> >> > Please see
> >> > the README for more details and shout if anything is confusing.
> >> >
> >> > --Rafael
> >> >
> >>
> >
> >
> 

[jira] [Resolved] (PROTON-199) [Proton-c] Python binding requires python 2.6+

[Ken Giusti (JIRA)]

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

Ken Giusti resolved PROTON-199.
---

Resolution: Fixed

http://svn.apache.org/viewvc?view=revision&revision=1448323

> [Proton-c] Python binding requires python 2.6+
> --
>
> Key: PROTON-199
> URL: https://issues.apache.org/jira/browse/PROTON-199
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: 0.3
> Environment: python versions < 2.5
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Minor
> Fix For: 0.4
>
> Attachments: proton-199.patch
>
>
> Python bindings make use of (at least two) python language features that 
> require python versions newer than 2.5:
> - uuid
> - bytes
> In order to support older versions of the python language, these features 
> would have to be removed, or a compatibility layer would need to be provided.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

0.4 RC2

[Rafael Schloming]

Source posted here:
  - http://people.apache.org/~rhs/qpid-proton-0.4rc2/

Java binaries here:
  - https://repository.apache.org/content/repositories/orgapacheqpid-280/

I'd like to call an official vote soon, e.g. tomorrow, so please have a
look and share your results here.

Changes from RC1:

PROTON-199: support python 2.4
PROTON-236 freegetopt compat for proton-c windows builds.
PROTON-243: fixed LIB_SUFFIX magic
PROTON-200: maintain a minimum credit level for each receive link
PROTON-200: make similar changes to Java MessengerImpl
PROTON-200: allow recv(-1) to grant unlimited credit
PROTON-232: described arrays seem to force the descriptor to be of the same
type as the array Fixed bug in code.c pn_data_encode_node: was always using
the parent->type for everything inside an array, including the descriptor.
PROTON-242: Shared library used JNI code has poor name "libproton-swig.so"
Shared library now has name libproton-jni.so i.e. follows the naming
conventions of its companion jar.
PROTON-217: cmake build system should include install target for Java
binaries

--Rafael

Re: 0.4 RC2

[Cliff Jansen]

Looks good.  Build and ctest success on rhel6 64 bit.

Successful build and expected ctest results on Windows 7 and VS2008.

Cliff

On Wed, Feb 20, 2013 at 3:31 PM, Rafael Schloming  wrote:
> Source posted here:
>   - http://people.apache.org/~rhs/qpid-proton-0.4rc2/
>
> Java binaries here:
>   - https://repository.apache.org/content/repositories/orgapacheqpid-280/
>
> I'd like to call an official vote soon, e.g. tomorrow, so please have a
> look and share your results here.
>
> Changes from RC1:
>
> PROTON-199: support python 2.4
> PROTON-236 freegetopt compat for proton-c windows builds.
> PROTON-243: fixed LIB_SUFFIX magic
> PROTON-200: maintain a minimum credit level for each receive link
> PROTON-200: make similar changes to Java MessengerImpl
> PROTON-200: allow recv(-1) to grant unlimited credit
> PROTON-232: described arrays seem to force the descriptor to be of the same
> type as the array Fixed bug in code.c pn_data_encode_node: was always using
> the parent->type for everything inside an array, including the descriptor.
> PROTON-242: Shared library used JNI code has poor name "libproton-swig.so"
> Shared library now has name libproton-jni.so i.e. follows the naming
> conventions of its companion jar.
> PROTON-217: cmake build system should include install target for Java
> binaries
>
> --Rafael

Re: 0.4 RC2

[Phil Harvey]

Mostly looks good.  One test is failing when run using the Java JNI binding
- see below.

Tested:

- Download tarball
- cmake, make, make install
  - Observed .so and .jar files installed to correct locations
- Ran ./tests/python/proton-test
- Ran mvn package test and observed all tests passing
- Ran mvn -P proton-jni test
  - *FAILED* test "proton_tests.messenger.MessengerTest.testSendBogus".  I
think this is existing issue PROTON-214 [1].  I don't know if this
represents a serious functional problem but generally we wouldn't want to
release something that fails any tests.
- Created and ran a simple Maven project that depends on proton-api and
proton-j-impl 0.4 in the
orgapacheqpid-280/
 repo.


Environment:
- Linux Mint 12, x86_64
- Java: Oracle 1.6.0_29
- cmake version 2.8.5
- SWIG Version 1.3.40
- Python 2.7.2+


Phil

[1] https://issues.apache.org/jira/browse/PROTON-214



On 20 February 2013 20:31, Rafael Schloming  wrote:

> Source posted here:
>   - http://people.apache.org/~rhs/qpid-proton-0.4rc2/
>
> Java binaries here:
>   - https://repository.apache.org/content/repositories/orgapacheqpid-280/
>
> I'd like to call an official vote soon, e.g. tomorrow, so please have a
> look and share your results here.
>
> Changes from RC1:
>
> PROTON-199: support python 2.4
> PROTON-236 freegetopt compat for proton-c windows builds.
> PROTON-243: fixed LIB_SUFFIX magic
> PROTON-200: maintain a minimum credit level for each receive link
> PROTON-200: make similar changes to Java MessengerImpl
> PROTON-200: allow recv(-1) to grant unlimited credit
> PROTON-232: described arrays seem to force the descriptor to be of the same
> type as the array Fixed bug in code.c pn_data_encode_node: was always using
> the parent->type for everything inside an array, including the descriptor.
> PROTON-242: Shared library used JNI code has poor name "libproton-swig.so"
> Shared library now has name libproton-jni.so i.e. follows the naming
> conventions of its companion jar.
> PROTON-217: cmake build system should include install target for Java
> binaries
>
> --Rafael
>

[jira] [Commented] (PROTON-244) NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting qpid-client to qpid-proton in ActiveMQ

[Jan-Helge Bergesen (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582969#comment-13582969
 ] 

Jan-Helge Bergesen commented on PROTON-244:
---

Certainly!

The actual usecase I've got is bridging events from a legacy system into new 
infrastructure using Camel.
The legacy system isn't too fuzzy about setting all headers and stuff..

Heres a somewhat obscured dump of the inbound message (from Glassfish/OpenMQ) 
that is bridged into ActiveMQ:

07:36:32.207 [Camel (wms) thread #0 - JmsConsumer[MyTopicDestination]] DEBUG 
o.a.c.c.jms.EndpointMessageListener - 
Endpoint[jmsapps01://topic:MyTopicDestination?clientId=jms-bridge-wms-transaction&durableSubscriptionName=jms-bridge-wms-transaction]
 consumer received JMS message: 
Class:  com.sun.messaging.jmq.jmsclient.MapMessageImpl
getJMSMessageID():  ID:4761-10.0.63.37(87:9a:32:dc:6b:a2)-1-1361428595454
getJMSTimestamp():  1361428595454
getJMSCorrelationID():  null
JMSReplyTo: null
JMSDestination: MyTopicDestination
getJMSDeliveryMode():   PERSISTENT
getJMSRedelivered():false
getJMSType():   null
getJMSExpiration(): 0
getJMSPriority():   4
Properties: {eventType=InternalEventType, changedReason=My 3217454 
from P1666 to L1. Attrib:, changedBy=jhb, changedWhen=Thu Feb 21 07:36:35 CET 
2013, itemId=795175}
07:36:32.285 [Camel (wms) thread #0 - JmsConsumer[MyTopicDestination]] DEBUG 
wms-transaction-bridge-to-activemq - From apps01 {JMSRedelivered=false, 
JMSReplyTo=null, JMSDeliveryMode=2, changedWhen=Thu Feb 21 07:36:35 CET 2013, 
JMSCorrelationID=null, JMSPriority=4, changedReason=My 3217454 from P1666 to 
L1. Attrib:, JMSExpiration=0, JMSDestination=Sun Java System MQ Destination
getName():  MyTopicDestination
Class:  com.sun.messaging.Topic
getVERSION():   3.0
isReadonly():   false
getProperties():{imqDestinationName=MyTopicDestination, 
imqDestinationDescription=A Description for the Destination Object}, 
JMSTimestamp=1361428595454, itemId=795175, changedBy=jhb, 
eventType=InternalEventType, JMSType=null, 
JMSMessageID=ID:4761-10.0.63.37(87:9a:32:dc:6b:a2)-1-1361428595454, 
breadcrumbId=ID:4761-10.0.63.37(87:9a:32:dc:6b:a2)-1-1361428595454, 
JMSXGroupID=null}


Letting Camel set the JMSType header before forwarding it solved my particular 
hurdle, but alas I imagine the legacy system I'm looking at isn't that unique 
in it's header processing.. ;-)

> NPE in org/apache/qpid/proton/jms/InboundTransformer when connecting 
> qpid-client to qpid-proton in ActiveMQ
> ---
>
> Key: PROTON-244
> URL: https://issues.apache.org/jira/browse/PROTON-244
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: 0.3
>Reporter: Jan-Helge Bergesen
>Assignee: Hiram Chirino
>  Labels: robustness
> Attachments: PROTON-244.logexcerpt.txt
>
>
> Connecting a ConnectionFactory from qpid-amqp-1-0-client-jms version 0.20 to 
> ActiveMQ 5.8.0, yields NPE:
> org.apache.activemq.transport.amqp.AmqpProtocolException: Could not process 
> AMQP commands
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:245)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onAMQPData(AmqpProtocolConverter.java:151)
> at 
> org.apache.activemq.transport.amqp.AmqpTransportFilter.onCommand(AmqpTransportFilter.java:94)
> at 
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.NullPointerException
> at 
> org.apache.qpid.proton.jms.InboundTransformer.populateMessage(InboundTransformer.java:146)
> at 
> org.apache.qpid.proton.jms.AMQPNativeInboundTransformer.transform(AMQPNativeInboundTransformer.java:37)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter$ProducerContext.onMessage(AmqpProtocolConverter.java:454)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter$BaseProducerContext.onDelivery(AmqpProtocolConverter.java:435)
> at 
> org.apache.activemq.transport.amqp.AmqpProtocolConverter.onFrame(AmqpProtocolConverter.java:215)
> ... 6 more
> Looking at 
> https://github.com/apache/qpid-proton/blob/trunk/proton-j/contrib/proton-jms/src/main/java/org/apache/qpid/proton/jms/InboundTransformer.java#L146
> It would seems that qpid-amqp-1-0-client-jms sends a message with h