Re: [Proton-c][Solaris][SunStudio-2.1] Compiling Qpid Proton-c and C++ bindings on Solaris

2016-10-19 Thread Andrew Stitcher 
On Wed, 2016-10-19 at 17:30 -0400, Alan Conway wrote:
> On Tue, 2016-10-18 at 13:24 -0400, Alan Conway wrote:
> > 
> > Hi Adel,
> > 
> > I've got your Solaris fixes and my (minor) changes up on
> >  https://github.com/alanconway/qpid-proton/tree/absolaris
> > 
> > I'd like Andrew to take a look (he's back tomorrow), unless he has
> > anything to add I'll commit them.
> 
> I think I've addressed all Andrew's comments on the github branch,
> will
> wait for one more go-round from him.

I'm happy except for PROTON-1316. I've made a comment on the new github
branch.

Andrew


-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-532) man pages installed in wrong directory (man.X)

2016-10-19 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589928#comment-15589928
 ] 

ASF subversion and git services commented on DISPATCH-532:
--

Commit 444224e90226506d3572f4d4aeecc9059d41ade6 in qpid-dispatch's branch 
refs/heads/0.7.x from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=444224e ]

DISPATCH-532: man pages installed in wrong directory (man.X)


> man pages installed in wrong directory (man.X)
> --
>
> Key: DISPATCH-532
> URL: https://issues.apache.org/jira/browse/DISPATCH-532
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 0.6.1
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.7.0
>
>
> Man pages are being installed in the wrong directories, e.g. man.5 instead of 
> man5. Bug in the cmake install script.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (DISPATCH-532) man pages installed in wrong directory (man.X)

2016-10-19 Thread Alan Conway (JIRA) 

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

Alan Conway resolved DISPATCH-532.
--
Resolution: Fixed

> man pages installed in wrong directory (man.X)
> --
>
> Key: DISPATCH-532
> URL: https://issues.apache.org/jira/browse/DISPATCH-532
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 0.6.1
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.7.0
>
>
> Man pages are being installed in the wrong directories, e.g. man.5 instead of 
> man5. Bug in the cmake install script.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: [Proton-c][Solaris][SunStudio-2.1] Compiling Qpid Proton-c and C++ bindings on Solaris

2016-10-19 Thread Alan Conway 
On Tue, 2016-10-18 at 13:24 -0400, Alan Conway wrote:
> Hi Adel,
> 
> I've got your Solaris fixes and my (minor) changes up on
>  https://github.com/alanconway/qpid-proton/tree/absolaris
> 
> I'd like Andrew to take a look (he's back tomorrow), unless he has
> anything to add I'll commit them.

I think I've addressed all Andrew's comments on the github branch, will
wait for one more go-round from him.



-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: [Proton-c][Solaris][SunStudio-2.1] Compiling Qpid Proton-c and C++ bindings on Solaris

2016-10-19 Thread Adel Boutros 
Hello Andrew,

I will check tomorrow all your comments because I work in France so I am no 
longer in the office now.

I let you choose where to place the comments and we will be happy to reply to 
them by tomorrow. Just let us know where you put them.

Regards,
Adel

Get Outlook for Android



On Wed, Oct 19, 2016 at 9:21 PM +0200, "Andrew Stitcher" 
> wrote:

Being clear, these are all fairly minor issues:

Thank you both for doing this work, I'm very happy to be expanding the
scope of portability for proton,

Andrew

Re: [Proton-c][Solaris][SunStudio-2.1] Compiling Qpid Proton-c and C++ bindings on Solaris

2016-10-19 Thread Andrew Stitcher 
Being clear, these are all fairly minor issues:

Thank you both for doing this work, I'm very happy to be expanding the
scope of portability for proton,

Andrew


-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: [Proton-c][Solaris][SunStudio-2.1] Compiling Qpid Proton-c and C++ bindings on Solaris

2016-10-19 Thread Andrew Stitcher 
On Wed, 2016-10-19 at 14:56 -0400, Andrew Stitcher wrote:
> How would you guys like my comments?
> 
> I can put them in this email thread (with no external visibility), in
> the Jiras, or as comments to the branch in alan's repo.
> 
> Any preferences (I'd prefer to keep the comments public).

So I've made a number of comments both on github and on the Jiras:

* Solaris should have SO_NOSIGPIPE, so the new code in PROTON-1314
should be needed (although there's nothing wrong with the code as far
as I can see).

I think the necessary include might not be getting included.

* Symbol hiding: PROTON-1316 removes symbol hiding for gcc completely,
so that change can't go in as is. I'm sure that wasn't intentional,
just a side effect of doing what was necessary for Solaris without
checking properly again on Linux.

* I agree with Alan's modifications of PROTON-1318/PROTON-1319: I
thionk the branch needs to be rebased before merging to squash these
into one commit each.

Andrew


-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1325) Python "buffer" type in Message body should map to a known encoding type

2016-10-19 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on PROTON-1325:
-

Commit 6dabb379bf029950ce96966a305cf6b0bc38 in qpid-proton's branch 
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=6dabb37 ]

PROTON-1325: Python mapping for 'buffer' and/or 'memoryview'

Use whichever is available, memoryview is 3.x and some later 2.x, buffer is
older 2.x. Some have both.


> Python "buffer" type in Message body should map to a known encoding type
> 
>
> Key: PROTON-1325
> URL: https://issues.apache.org/jira/browse/PROTON-1325
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Affects Versions: 0.14.0
>Reporter: Brian Bouterse
>Assignee: Alan Conway
> Fix For: 0.16.0
>
>
> If I try to send a message like this it fails due to an encoding error.
> from proton import Message
> Message(body=buffer('asdf'))
> If you try to send this and fail to specify an encoding, you will get an 
> encoding traceback like this one.
> Traceback (most recent call last):
>   File "/usr/lib64/python2.7/threading.py", line 804, in __bootstrap_inner
> self.run()
>   File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 1367, in run
> Container(HelloWorld("localhost:5672", self._w, 
> self.outbound_messages)).run()
>   File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 133, in 
> run
> while self.process(): pass
>   File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 159, in 
> process
> self._check_errors()
>   File "/usr/lib64/python2.7/site-packages/proton/reactor.py", line 155, in 
> _check_errors
> _compat.raise_(exc, value, tb)
>   File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 4022, in 
> dispatch
> ev.dispatch(self.handler)
>   File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3934, in 
> dispatch
> self.dispatch(h, type)
>   File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3931, in 
> dispatch
> result = dispatch(handler, type.method, self)
>   File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3812, in 
> dispatch
> return m(*args)
>   File "/usr/lib64/python2.7/site-packages/proton/handlers.py", line 40, in 
> on_link_flow
> self.on_sendable(event)
>   File "/usr/lib64/python2.7/site-packages/proton/handlers.py", line 62, in 
> on_sendable
> dispatch(self.delegate, 'on_sendable', event)
>   File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3812, in 
> dispatch
> return m(*args)
>   File "/home/vagrant/devel/kombu/kombu/transport/qpid.py", line 1351, in 
> on_sendable
> event.sender.send(message)
>   File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2997, in 
> send
> return obj.send(self, tag=tag)
>   File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 1116, in 
> send
> encoded = self.encode()
>   File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 1099, in 
> encode
> self._pre_encode()
>   File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 843, in 
> _pre_encode
> body.put_object(self.body)
>   File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2271, in 
> put_object
> putter(self, obj)
>   File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2114, in 
> put_dict
> self.put_object(v)
>   File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 2270, in 
> put_object
> putter = self.put_mappings[obj.__class__]
> KeyError: 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1314) Fixing SIGPIPE ignore on Solaris OS

2016-10-19 Thread Andrew Stitcher (JIRA) 

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

Andrew Stitcher commented on PROTON-1314:
-

This is odd:
Under Solaris and all BSD derivatives I've used SO_NOSIGPIPE exists, so I don't 
understand why you are falling through to the "not implemented" code.

Could you check if perhaps the include file that defines SO_NOSIGPIPE is not 
being included.

> Fixing SIGPIPE ignore on Solaris OS
> ---
>
> Key: PROTON-1314
> URL: https://issues.apache.org/jira/browse/PROTON-1314
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Adel Boutros
> Attachments: 0001-Fixing-SIGPIPE-ignore-on-Solaris-OS.patch
>
>
> Fixing SIGPIPE ignore on Solaris OS



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1316) Add a way to set visibility of exportable symbols on Solaris

2016-10-19 Thread Andrew Stitcher (JIRA) 

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

Andrew Stitcher commented on PROTON-1316:
-

This patch is not good.
It may fix the issue for Solaris, but it totally turns off symbol hiding for 
gcc.

I think you'll need to indirect the extra definitions a bit (like the LTO 
definitions).

> Add a way to set visibility of exportable symbols on Solaris
> 
>
> Key: PROTON-1316
> URL: https://issues.apache.org/jira/browse/PROTON-1316
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Adel Boutros
> Attachments: 
> 0003-Add-a-way-to-set-visibility-of-exportable-symbols.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: [Proton-c][Solaris][SunStudio-2.1] Compiling Qpid Proton-c and C++ bindings on Solaris

2016-10-19 Thread Andrew Stitcher 
How would you guys like my comments?

I can put them in this email thread (with no external visibility), in
the Jiras, or as comments to the branch in alan's repo.

Any preferences (I'd prefer to keep the comments public).

Andrew


-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-532) man pages installed in wrong directory (man.X)

2016-10-19 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589340#comment-15589340
 ] 

ASF subversion and git services commented on DISPATCH-532:
--

Commit 176e52c0b3d7751e757f9dd1654dbbe09bbaf791 in qpid-dispatch's branch 
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=176e52c ]

DISPATCH-532: man pages installed in wrong directory (man.X)


> man pages installed in wrong directory (man.X)
> --
>
> Key: DISPATCH-532
> URL: https://issues.apache.org/jira/browse/DISPATCH-532
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 0.6.1
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.7.0
>
>
> Man pages are being installed in the wrong directories, e.g. man.5 instead of 
> man5. Bug in the cmake install script.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-532) man pages installed in wrong directory (man.X)

2016-10-19 Thread Alan Conway (JIRA) 
Alan Conway created DISPATCH-532:


 Summary: man pages installed in wrong directory (man.X)
 Key: DISPATCH-532
 URL: https://issues.apache.org/jira/browse/DISPATCH-532
 Project: Qpid Dispatch
  Issue Type: Bug
  Components: Documentation
Affects Versions: 0.6.1
Reporter: Alan Conway
Assignee: Alan Conway
 Fix For: 0.7.0


Man pages are being installed in the wrong directories, e.g. man.5 instead of 
man5. Bug in the cmake install script.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: qpid-jms with C++ Broker - Does it support ByteMessage types from java?

2016-10-19 Thread Bill Gercken 
Figured out the issue. Coding error.

In my onMessage loop I was assigning the message to a TextMessage without
checking the instancof the message class. (I was using mostly TextMessages
when I started.)

Instead of throwing an exception it would just fail the assignment and
return from the method, which was causing the message to be continuously
re-delivered eventually using up all of the memory on my subscriber.

Thanks.
-bill


On Wed, Oct 19, 2016 at 8:29 AM, Robbie Gemmell 
wrote:

> I'm not aware of any issues doing this, and I just modified the
> HelloWorld example to use BytesMessage (with and without writing
> content) and ran it against the 1.35.0 C++ broker without issue. I'd
> be surprised if the older broker made a difference, but its possible I
> guess.
>
> Perhaps you can try looking at the logs to see if anything pops out.
> Beyond the regular logging, if you run the client or broker with
> PN_TRACE_FRM=true environment variable set you should see some
> protocol trace logging to the console from Proton (which they both use
> for their AMQP 1.0 support) which may further help in seeing whats
> going on.
>
> Questions like this are better suited to the users@ list rather than
> dev@, plus theres a bigger audience and less other activity happening
> to get in the way there.
>
> Robbie
>
> On 19 October 2016 at 01:06, bgercken  wrote:
> > Hi
> >
> > I am using qpid-jms (qpid-jms-client-0.20.0-SNAPSHOT.jar) with the C++
> qpid
> > broker version 0.34 from java.
> >
> > I can successfully package and receive standard Message and TextMessage
> > types but when I try to use a ByteMessage or a MapMessage type I never
> > receive the message.
> >
> > I have included two examples below. I can provide more information if
> > needed. I am hoping this is something simple that I am doing wrong.
> >
> > Thanks.
> > -bill
> >
> > THIS WORKS:
> >
> > public void publishHostFinished( String hostName, String
> clientType,
> > boolean success, String result ) {
> > try {
> > TextMessage message =
> session.createTextMessage();
> > message.setBooleanProperty( "finished_state",
> success);
> > message.setStringProperty( "finished_result",
> result );
> > message.setStringProperty( "message_type",
> "FINISHED" );
> > publishHostTextMessage( message, hostName,
> clientType, null );
> > }
> > catch( JMSException e ) {
> > log.error( "Error while publishing finished for
> {} client {}: {}",
> > hostName, clientType, e.getLocalizedMessage() );
> > }
> > }
> >
> > private void publishHostTextMessage( TextMessage message, String
> hostName,
> > String clientType, String body ) throws JMSException {
> > message.setStringProperty( "host", hostName );
> > message.setStringProperty( "client_type", clientType );
> > message.setText( body );
> > publisher.publish( message );
> > }
> >
> > WHERE THIS WON'T:
> >
> > // TEST MESSAGE
> > public void publishBufferedMessage( ) {
> >
> >
> > System.out.println( "** PUBLISH BUFFERD
> MESSAGE
> > *" );
> >
> > Drive.Builder drive = Drive.newBuilder();
> >
> > drive.setSerial( "123-456-789" );
> > drive.setComments( "This is drive: sda" );
> > drive.setId(123);
> > drive.setLabel( "DRIVE_LABEL" );
> >
> > drive.build();
> >
> > try {
> >
> > BytesMessage message = session.createBytesMessage();
> >
> > int messageSize = drive.build().getSerializedSize();
> >
> > message.setStringProperty( "message_type", "DRIVE_DATA"
> );
> > message.setIntProperty( "message_encoded_size",
> messageSize );
> >
> > /**
> > byte[] encodedMessage = new byte[messageSize];
> >
> > encodedMessage = drive.build().toByteArray();
> >
> > message.writeBytes( encodedMessage );
> > **/
> >
> > publisher.publish( message );
> >
> > }
> > catch( JMSException jmse ) {
> > System.out.println( "error while publishing
> buffered message: " +
> > jmse.getLocalizedMessage() );
> > }
> > }
> >
> >
> >
> >
> >
> > --
> > View this message in context: http://qpid.2158936.n2.nabble.
> com/qpid-jms-with-C-Broker-Does-it-support-ByteMessage-
> types-from-java-tp7652144.html
> > Sent from the Apache Qpid developers mailing list archive at Nabble.com.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> >

[jira] [Updated] (QPID-6504) [Pthon Client 0-10] Client can send commands like SessionCompleted, SessionRequestTimeout after sending ConnectionClose

2016-10-19 Thread Alex Rudyy (JIRA) 

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

Alex Rudyy updated QPID-6504:
-
Description: 
Client can send commands like SessionCompleted, SessionRequestTimeout after 
sending ConnectionClose


Broker logs for the test 
qpid_tests.broker_0_10.exchange.MiscellaneousErrorsTests.testDefaultAccessUnbind
{noformat}
2015-04-20 18:21:20,241 INFO  [IO-/127.0.0.1:55801] (connection.open) - 
[con:596(/127.0.0.1:55801)] CON-1001 : Open
2015-04-20 18:21:20,241 INFO  [IO-/127.0.0.1:55801] (connection.open) - 
[con:596(/127.0.0.1:55801)] CON-1001 : Open : Protocol Version : 0-10
2015-04-20 18:21:20,241 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
RECV: [conn:17945207] AMQP.1 0-10
2015-04-20 18:21:20,241 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
SEND: [conn:17945207] AMQP.1 0-10
2015-04-20 18:21:20,241 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
SEND: [conn:17945207] ch=0 ConnectionStart(serverProperties={product=qpid, 
qpid.build=Unversioned directory, qpid.instance_name=Broker, 
qpid.message_compression_supported=true, qpid.features=[qpid.jms-selector], 
qpid.federation_tag=ebf99d76-03f1-43e8-bbeb-a2c4a134ad1c, 
version=6.0.0-SNAPSHOT}, mechanisms=[PLAIN, CRAM-MD5], locales=[en_US])
2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
FLUSH: [conn:17945207]
2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 321 bytes
2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Read 0 byte(s)
2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,245 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,245 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Read 217 byte(s)
2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
RECV: [conn:17945207] ch=0 ConnectionStartOk(clientProperties={product=qpid 
python client, qpid.client_version=unidentified, qpid.client_ppid=22599, 
qpid.client_process=qpid-python-test, platform=posix, qpid.client_pid=10619}, 
mechanism=PLAIN, response="\x00guest\x00guest")
2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
SEND: [conn:17945207] ch=0 ConnectionTune(channelMax=256, maxFrameSize=65535, 
heartbeatMin=0, heartbeatMax=65535)
2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
FLUSH: [conn:17945207]
2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 24 bytes
2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Read 0 byte(s)
2015-04-20 18:21:20,247 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,247 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,247 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Read 16 byte(s)
2015-04-20 18:21:20,248 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
RECV: [conn:17945207] ch=0 ConnectionTuneOk()
2015-04-20 18:21:20,248 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,248 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,248 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Read 0 byte(s)
2015-04-20 18:21:20,248 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,287 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,287 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Read 16 byte(s)
2015-04-20 18:21:20,288 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
RECV: [conn:17945207] ch=0 ConnectionOpen()
2015-04-20 18:21:20,288 INFO  [IO-/127.0.0.1:55801] (connection.open) - 
[con:596(guest@/127.0.0.1:55801/default)] CON-1001 : Open : Client ID : null : 
Protocol Version : 0-10 : Client Version : unidentified : Client Product : qpid 
python client
2015-04-20 18:21:20,288 DEBUG [IO-/127.0.0.1:55801] (updater.TaskExecutorImpl) 
- Submitting task: 
org.apache.qpid.server.model.AbstractConfiguredObject$2@a9555a9
2015-04-20 18:21:20,288 DEBUG [VirtualHostNode-default-Configuration-Thread] 
(updater.TaskExecutorImpl) - Performing task 
org.apache.qpid.server.model.AbstractConfiguredObject$2@a9555a9
2015-04-20 18:21:20,289 DEBUG [VirtualHostNode-default-Configuration-Thread] 
(updater.TaskExecutorImpl) - Task 
org.apache.qpid.server.model.AbstractConfiguredObject$2@a9555a9

[jira] [Updated] (QPID-6504) [Pthon Client 0-10] Client can send commands like SessionCompleted, SessionRequestTimeout after sending ConnectionClose

2016-10-19 Thread Alex Rudyy (JIRA) 

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

Alex Rudyy updated QPID-6504:
-
Description: 
Client can 

The test after receiving an exception in response to unbind command for default 
exchange verifies the exception error code and proceeds  to tearDown where 
connection is closed. It sends ConnectionClose command and continues receiving 
and responding sub-sequent commands/controls from the broker. The broker itself 
after sending an exception to client attempts to close the broker side session 
by sending  SessionRequestTimeout(timeout=0) and SessionDetach. Immediately 
after that, the Broker receives ConnectionClose and sends ConnectionCloseOk 
followed by socket close. At the same time client, receives 
SessionRequestTimeout and attempts to send a response but socket is closed on 
Broker side. As result, the client does not manage to reply on  
SessionRequestTimeout and it seems cannot receive  ConnectionCloseOK.It looks 
like the "broken pipe" is reported before client can receive ConnectionCloseOK.

The symptoms described above indicate about client side defect. 

Broker logs for the test 
qpid_tests.broker_0_10.exchange.MiscellaneousErrorsTests.testDefaultAccessUnbind
{noformat}
2015-04-20 18:21:20,241 INFO  [IO-/127.0.0.1:55801] (connection.open) - 
[con:596(/127.0.0.1:55801)] CON-1001 : Open
2015-04-20 18:21:20,241 INFO  [IO-/127.0.0.1:55801] (connection.open) - 
[con:596(/127.0.0.1:55801)] CON-1001 : Open : Protocol Version : 0-10
2015-04-20 18:21:20,241 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
RECV: [conn:17945207] AMQP.1 0-10
2015-04-20 18:21:20,241 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
SEND: [conn:17945207] AMQP.1 0-10
2015-04-20 18:21:20,241 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
SEND: [conn:17945207] ch=0 ConnectionStart(serverProperties={product=qpid, 
qpid.build=Unversioned directory, qpid.instance_name=Broker, 
qpid.message_compression_supported=true, qpid.features=[qpid.jms-selector], 
qpid.federation_tag=ebf99d76-03f1-43e8-bbeb-a2c4a134ad1c, 
version=6.0.0-SNAPSHOT}, mechanisms=[PLAIN, CRAM-MD5], locales=[en_US])
2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
FLUSH: [conn:17945207]
2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 321 bytes
2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Read 0 byte(s)
2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,245 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,245 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Read 217 byte(s)
2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
RECV: [conn:17945207] ch=0 ConnectionStartOk(clientProperties={product=qpid 
python client, qpid.client_version=unidentified, qpid.client_ppid=22599, 
qpid.client_process=qpid-python-test, platform=posix, qpid.client_pid=10619}, 
mechanism=PLAIN, response="\x00guest\x00guest")
2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
SEND: [conn:17945207] ch=0 ConnectionTune(channelMax=256, maxFrameSize=65535, 
heartbeatMin=0, heartbeatMax=65535)
2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
FLUSH: [conn:17945207]
2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 24 bytes
2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Read 0 byte(s)
2015-04-20 18:21:20,247 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,247 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,247 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Read 16 byte(s)
2015-04-20 18:21:20,248 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
RECV: [conn:17945207] ch=0 ConnectionTuneOk()
2015-04-20 18:21:20,248 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,248 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,248 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Read 0 byte(s)
2015-04-20 18:21:20,248 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,287 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Written 0 bytes
2015-04-20 18:21:20,287 DEBUG [IO-/127.0.0.1:55801] 
(transport.NonBlockingConnection) - Read 16 byte(s)

[jira] [Updated] (QPID-6504) [Pthon Client 0-10] Client can send commands like SessionCompleted, SessionRequestTimeout after sending ConnectionClose

2016-10-19 Thread Alex Rudyy (JIRA) 

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

Alex Rudyy updated QPID-6504:
-
Summary: [Pthon Client 0-10] Client can send commands like 
SessionCompleted, SessionRequestTimeout after sending ConnectionClose  (was: 
[Pthon Client 0-10] Client can send Test 
qpid_tests.broker_0_10.exchange.MiscellaneousErrorsTests.testDefaultAccessUnbind
 fails sporadically due to timeout on connection close)

> [Pthon Client 0-10] Client can send commands like SessionCompleted, 
> SessionRequestTimeout after sending ConnectionClose
> ---
>
> Key: QPID-6504
> URL: https://issues.apache.org/jira/browse/QPID-6504
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Client
>Affects Versions: 0.8, 0.10, 0.12, 0.14, 0.16, 0.18, 0.20, 0.22, 0.24, 
> 0.26, 0.28, 0.30, 0.32, qpid-java-6.0
>Reporter: Alex Rudyy
>
> The test after receiving an exception in response to unbind command for 
> default exchange verifies the exception error code and proceeds  to tearDown 
> where connection is closed. It sends ConnectionClose command and continues 
> receiving and responding sub-sequent commands/controls from the broker. The 
> broker itself after sending an exception to client attempts to close the 
> broker side session by sending  SessionRequestTimeout(timeout=0) and 
> SessionDetach. Immediately after that, the Broker receives ConnectionClose 
> and sends ConnectionCloseOk followed by socket close. At the same time 
> client, receives SessionRequestTimeout and attempts to send a response but 
> socket is closed on Broker side. As result, the client does not manage to 
> reply on  SessionRequestTimeout and it seems cannot receive  
> ConnectionCloseOK.It looks like the "broken pipe" is reported before client 
> can receive ConnectionCloseOK.
> The symptoms described above indicate about client side defect. 
> Broker logs for the test 
> qpid_tests.broker_0_10.exchange.MiscellaneousErrorsTests.testDefaultAccessUnbind
> {noformat}
> 2015-04-20 18:21:20,241 INFO  [IO-/127.0.0.1:55801] (connection.open) - 
> [con:596(/127.0.0.1:55801)] CON-1001 : Open
> 2015-04-20 18:21:20,241 INFO  [IO-/127.0.0.1:55801] (connection.open) - 
> [con:596(/127.0.0.1:55801)] CON-1001 : Open : Protocol Version : 0-10
> 2015-04-20 18:21:20,241 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> RECV: [conn:17945207] AMQP.1 0-10
> 2015-04-20 18:21:20,241 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> SEND: [conn:17945207] AMQP.1 0-10
> 2015-04-20 18:21:20,241 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> SEND: [conn:17945207] ch=0 ConnectionStart(serverProperties={product=qpid, 
> qpid.build=Unversioned directory, qpid.instance_name=Broker, 
> qpid.message_compression_supported=true, qpid.features=[qpid.jms-selector], 
> qpid.federation_tag=ebf99d76-03f1-43e8-bbeb-a2c4a134ad1c, 
> version=6.0.0-SNAPSHOT}, mechanisms=[PLAIN, CRAM-MD5], locales=[en_US])
> 2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> FLUSH: [conn:17945207]
> 2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Written 321 bytes
> 2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Written 0 bytes
> 2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Read 0 byte(s)
> 2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Written 0 bytes
> 2015-04-20 18:21:20,245 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Written 0 bytes
> 2015-04-20 18:21:20,245 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Read 217 byte(s)
> 2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> RECV: [conn:17945207] ch=0 ConnectionStartOk(clientProperties={product=qpid 
> python client, qpid.client_version=unidentified, qpid.client_ppid=22599, 
> qpid.client_process=qpid-python-test, platform=posix, qpid.client_pid=10619}, 
> mechanism=PLAIN, response="\x00guest\x00guest")
> 2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> SEND: [conn:17945207] ch=0 ConnectionTune(channelMax=256, maxFrameSize=65535, 
> heartbeatMin=0, heartbeatMax=65535)
> 2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> FLUSH: [conn:17945207]
> 2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Written 24 bytes
> 2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Written 0 bytes
> 2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Read 0 byte(s)
> 2015-04-20 18:21:20,247 DEBUG [IO-/127.0.0.1:55801] 
>

[jira] [Updated] (QPID-6504) [Pthon Client 0-10] Client can send Test qpid_tests.broker_0_10.exchange.MiscellaneousErrorsTests.testDefaultAccessUnbind fails sporadically due to timeout on connection c

2016-10-19 Thread Alex Rudyy (JIRA) 

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

Alex Rudyy updated QPID-6504:
-
Summary: [Pthon Client 0-10] Client can send Test 
qpid_tests.broker_0_10.exchange.MiscellaneousErrorsTests.testDefaultAccessUnbind
 fails sporadically due to timeout on connection close  (was: Test 
qpid_tests.broker_0_10.exchange.MiscellaneousErrorsTests.testDefaultAccessUnbind
 fails sporadically due to timeout on connection close)

> [Pthon Client 0-10] Client can send Test 
> qpid_tests.broker_0_10.exchange.MiscellaneousErrorsTests.testDefaultAccessUnbind
>  fails sporadically due to timeout on connection close
> ---
>
> Key: QPID-6504
> URL: https://issues.apache.org/jira/browse/QPID-6504
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Client
>Affects Versions: 0.8, 0.10, 0.12, 0.14, 0.16, 0.18, 0.20, 0.22, 0.24, 
> 0.26, 0.28, 0.30, 0.32, qpid-java-6.0
>Reporter: Alex Rudyy
>
> The test after receiving an exception in response to unbind command for 
> default exchange verifies the exception error code and proceeds  to tearDown 
> where connection is closed. It sends ConnectionClose command and continues 
> receiving and responding sub-sequent commands/controls from the broker. The 
> broker itself after sending an exception to client attempts to close the 
> broker side session by sending  SessionRequestTimeout(timeout=0) and 
> SessionDetach. Immediately after that, the Broker receives ConnectionClose 
> and sends ConnectionCloseOk followed by socket close. At the same time 
> client, receives SessionRequestTimeout and attempts to send a response but 
> socket is closed on Broker side. As result, the client does not manage to 
> reply on  SessionRequestTimeout and it seems cannot receive  
> ConnectionCloseOK.It looks like the "broken pipe" is reported before client 
> can receive ConnectionCloseOK.
> The symptoms described above indicate about client side defect. 
> Broker logs for the test 
> qpid_tests.broker_0_10.exchange.MiscellaneousErrorsTests.testDefaultAccessUnbind
> {noformat}
> 2015-04-20 18:21:20,241 INFO  [IO-/127.0.0.1:55801] (connection.open) - 
> [con:596(/127.0.0.1:55801)] CON-1001 : Open
> 2015-04-20 18:21:20,241 INFO  [IO-/127.0.0.1:55801] (connection.open) - 
> [con:596(/127.0.0.1:55801)] CON-1001 : Open : Protocol Version : 0-10
> 2015-04-20 18:21:20,241 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> RECV: [conn:17945207] AMQP.1 0-10
> 2015-04-20 18:21:20,241 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> SEND: [conn:17945207] AMQP.1 0-10
> 2015-04-20 18:21:20,241 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> SEND: [conn:17945207] ch=0 ConnectionStart(serverProperties={product=qpid, 
> qpid.build=Unversioned directory, qpid.instance_name=Broker, 
> qpid.message_compression_supported=true, qpid.features=[qpid.jms-selector], 
> qpid.federation_tag=ebf99d76-03f1-43e8-bbeb-a2c4a134ad1c, 
> version=6.0.0-SNAPSHOT}, mechanisms=[PLAIN, CRAM-MD5], locales=[en_US])
> 2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> FLUSH: [conn:17945207]
> 2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Written 321 bytes
> 2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Written 0 bytes
> 2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Read 0 byte(s)
> 2015-04-20 18:21:20,242 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Written 0 bytes
> 2015-04-20 18:21:20,245 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Written 0 bytes
> 2015-04-20 18:21:20,245 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Read 217 byte(s)
> 2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> RECV: [conn:17945207] ch=0 ConnectionStartOk(clientProperties={product=qpid 
> python client, qpid.client_version=unidentified, qpid.client_ppid=22599, 
> qpid.client_process=qpid-python-test, platform=posix, qpid.client_pid=10619}, 
> mechanism=PLAIN, response="\x00guest\x00guest")
> 2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> SEND: [conn:17945207] ch=0 ConnectionTune(channelMax=256, maxFrameSize=65535, 
> heartbeatMin=0, heartbeatMax=65535)
> 2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] (transport.Connection) - 
> FLUSH: [conn:17945207]
> 2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Written 24 bytes
> 2015-04-20 18:21:20,246 DEBUG [IO-/127.0.0.1:55801] 
> (transport.NonBlockingConnection) - Written 0 bytes
> 2015-04-20 18:21:20,246 DEBUG

[jira] [Commented] (QPID-7465) [Java Broker] Stop ServerEncoder from unnecessarily allocating ByteBuffers

2016-10-19 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-7465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588942#comment-15588942
 ] 

ASF subversion and git services commented on QPID-7465:
---

Commit 1765609 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1765609 ]

QPID-7465: [Java Broker] Stop ServerEncoder from unnecessarily allocating 
ByteBuffers

> [Java Broker] Stop ServerEncoder from unnecessarily allocating ByteBuffers
> --
>
> Key: QPID-7465
> URL: https://issues.apache.org/jira/browse/QPID-7465
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Lorenz Quack
> Attachments: QPID-7465.diff, QPID-7465_v2.diff, QPID-7465_v2.diff
>
>
> As reported by [this email 
> thread|http://qpid.2158936.n2.nabble.com/java-broker-6-0-2-OOM-tp7651831.html]
>  the broker can currently run out of direct memory without flow-to-disk ever 
> kicking in.
> A defect in {{SeverEncoder#init()}} means that we allocate a new 8 kB direct 
> bytebuffer everytime it is called (i.e. on every AMQP 0-10 method or 
> command). This is wasteful and in some cases the GC does not collect these 
> direct byte buffers fast enough leading to the OOM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: qpid-jms with C++ Broker - Does it support ByteMessage types from java?

2016-10-19 Thread Bill Gercken 
Thanks Robbie,

I think that is the direction I am going to go in this morning (create a
separate stand alone example) to see if I can resolve the issue.

It may be something with the class path in my project as there are other
message classes using the proton API for other work.

The other thing that is weird, is that when I do produce ByteMessages my
consumer goes bonkers and gets into a GC frenzy and eventually produces a  GC
overhead message shown below.

Hopefully, the stand alone version will work and it is related to something
else. I will post future questions to the users list.

Thanks again,
-bill


Connection ExceptionListener fired, exiting.
javax.jms.JMSException: GC overhead limit exceeded
at
org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:86)
at
org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:108)
at
org.apache.qpid.jms.JmsConnection.onAsyncException(JmsConnection.java:1362)
at
org.apache.qpid.jms.JmsConnection.onProviderException(JmsConnection.java:1346)
at
org.apache.qpid.jms.JmsConnection.onConnectionFailure(JmsConnection.java:1219)
at
org.apache.qpid.jms.provider.amqp.AmqpProvider.fireProviderException(AmqpProvider.java:922)
at
org.apache.qpid.jms.provider.amqp.AmqpProvider$18.run(AmqpProvider.java:719)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: GC overhead limit exceeded
at
org.apache.qpid.jms.util.IOExceptionSupport.create(IOExceptionSupport.java:45)
... 9 more
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
at
io.netty.buffer.UnpooledHeapByteBuf.(UnpooledHeapByteBuf.java:46)
at
io.netty.buffer.UnpooledUnsafeHeapByteBuf.(UnpooledUnsafeHeapByteBuf.java:29)
at
io.netty.buffer.UnpooledByteBufAllocator.newHeapBuffer(UnpooledByteBufAllocator.java:59)
at
io.netty.buffer.AbstractByteBufAllocator.heapBuffer(AbstractByteBufAllocator.java:160)
at
io.netty.buffer.AbstractByteBufAllocator.heapBuffer(AbstractByteBufAllocator.java:151)
at
org.apache.qpid.jms.transports.netty.PartialPooledByteBufAllocator.ioBuffer(PartialPooledByteBufAllocator.java:70)
at
io.netty.channel.DefaultMaxMessagesRecvByteBufAllocator$MaxMessageHandle.allocate(DefaultMaxMessagesRecvByteBufAllocator.java:73)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:117)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:610)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:551)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:465)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:437)
at
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873)
at
io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
... 1 more


On Wed, Oct 19, 2016 at 8:29 AM, Robbie Gemmell 
wrote:

> I'm not aware of any issues doing this, and I just modified the
> HelloWorld example to use BytesMessage (with and without writing
> content) and ran it against the 1.35.0 C++ broker without issue. I'd
> be surprised if the older broker made a difference, but its possible I
> guess.
>
> Perhaps you can try looking at the logs to see if anything pops out.
> Beyond the regular logging, if you run the client or broker with
> PN_TRACE_FRM=true environment variable set you should see some
> protocol trace logging to the console from Proton (which they both use
> for their AMQP 1.0 support) which may further help in seeing whats
> going on.
>
> Questions like this are better suited to the users@ list rather than
> dev@, plus theres a bigger audience and less other activity happening
> to get in the way there.
>
> Robbie
>
> On 19 October 2016 at 01:06, bgercken  wrote:
> > Hi
> >
> > I am using qpid-jms (qpid-jms-client-0.20.0-SNAPSHOT.jar) with the C++
> qpid
> > broker version 0.34 from java.
> >
> > I can successfully package and receive standard Message and TextMessage
> > types but when I try to use a ByteMessage or a MapMessage type I never
> > receive the message.
> >
> > I have included two examples below. I can provide more information if
> > needed. I am hoping this is something simple that I am doing wrong.
> >
> > Thanks.
> > -bill

[jira] [Resolved] (QPID-7453) [Java Broker] Hand off selection task only if connection tasks need to be processed

2016-10-19 Thread Alex Rudyy (JIRA) 

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

Alex Rudyy resolved QPID-7453.
--
Resolution: Fixed

> [Java Broker] Hand off selection task only if connection tasks need to be 
> processed
> ---
>
> Key: QPID-7453
> URL: https://issues.apache.org/jira/browse/QPID-7453
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Assignee: Alex Rudyy
> Fix For: qpid-java-6.1
>
>
> Currently the selector thread always reschedules the selection task on the 
> workQueue.  In the case where the select was awoken for the purpose of 
> reregistering a connection on the selector, there will be no connection work 
> to be done, so the potential hand off to of the selection task will be 
> needless.
> We can simply optimise the algorithm to hand off responsibility for the 
> selection iff there is connection work that can be consumed by this thread.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-7453) [Java Broker] Hand off selection task only if connection tasks need to be processed

2016-10-19 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-7453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588912#comment-15588912
 ] 

ASF subversion and git services commented on QPID-7453:
---

Commit 1765606 from oru...@apache.org in branch 'java/trunk'
[ https://svn.apache.org/r1765606 ]

QPID-7453: Restore previous changes to reduce CPU utilization

> [Java Broker] Hand off selection task only if connection tasks need to be 
> processed
> ---
>
> Key: QPID-7453
> URL: https://issues.apache.org/jira/browse/QPID-7453
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Assignee: Alex Rudyy
> Fix For: qpid-java-6.1
>
>
> Currently the selector thread always reschedules the selection task on the 
> workQueue.  In the case where the select was awoken for the purpose of 
> reregistering a connection on the selector, there will be no connection work 
> to be done, so the potential hand off to of the selection task will be 
> needless.
> We can simply optimise the algorithm to hand off responsibility for the 
> selection iff there is connection work that can be consumed by this thread.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (PROTON-1329) [proton-j] remove the TestDecoder class

2016-10-19 Thread Robbie Gemmell (JIRA) 

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

Robbie Gemmell resolved PROTON-1329.

Resolution: Fixed

> [proton-j] remove the TestDecoder class
> ---
>
> Key: PROTON-1329
> URL: https://issues.apache.org/jira/browse/PROTON-1329
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-j
>Affects Versions: 0.15.0
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: 0.16.0
>
>
> There is a TestDecoder class that is used in a single test class, and just 
> wraps the main decoder. It adds very little value is currently erroneously 
> included in the main proton-j jar. It should just be removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1329) [proton-j] remove the TestDecoder class

2016-10-19 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on PROTON-1329:
-

Commit 1bbe43518b99fdeca100cc9c7f65ccdca00584bb in qpid-proton's branch 
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1bbe435 ]

PROTON-1329: remove the TestDecoder class


> [proton-j] remove the TestDecoder class
> ---
>
> Key: PROTON-1329
> URL: https://issues.apache.org/jira/browse/PROTON-1329
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-j
>Affects Versions: 0.15.0
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: 0.16.0
>
>
> There is a TestDecoder class that is used in a single test class, and just 
> wraps the main decoder. It adds very little value is currently erroneously 
> included in the main proton-j jar. It should just be removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (PROTON-1329) [proton-j] remove the TestDecoder class

2016-10-19 Thread Robbie Gemmell (JIRA) 
Robbie Gemmell created PROTON-1329:
--

 Summary: [proton-j] remove the TestDecoder class
 Key: PROTON-1329
 URL: https://issues.apache.org/jira/browse/PROTON-1329
 Project: Qpid Proton
  Issue Type: Task
  Components: proton-j
Affects Versions: 0.15.0
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
Priority: Minor
 Fix For: 0.16.0


There is a TestDecoder class that is used in a single test class, and just 
wraps the main decoder. It adds very little value is currently erroneously 
included in the main proton-j jar. It should just be removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-7465) [Java Broker] Stop ServerEncoder from unnecessarily allocating ByteBuffers

2016-10-19 Thread Lorenz Quack (JIRA) 

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

Lorenz Quack updated QPID-7465:
---
Attachment: QPID-7465_v2.diff

> [Java Broker] Stop ServerEncoder from unnecessarily allocating ByteBuffers
> --
>
> Key: QPID-7465
> URL: https://issues.apache.org/jira/browse/QPID-7465
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Lorenz Quack
> Attachments: QPID-7465.diff, QPID-7465_v2.diff, QPID-7465_v2.diff
>
>
> As reported by [this email 
> thread|http://qpid.2158936.n2.nabble.com/java-broker-6-0-2-OOM-tp7651831.html]
>  the broker can currently run out of direct memory without flow-to-disk ever 
> kicking in.
> A defect in {{SeverEncoder#init()}} means that we allocate a new 8 kB direct 
> bytebuffer everytime it is called (i.e. on every AMQP 0-10 method or 
> command). This is wasteful and in some cases the GC does not collect these 
> direct byte buffers fast enough leading to the OOM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-7465) [Java Broker] Stop ServerEncoder from unnecessarily allocating ByteBuffers

2016-10-19 Thread Lorenz Quack (JIRA) 

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

Lorenz Quack updated QPID-7465:
---
Attachment: QPID-7465_v2.diff

> [Java Broker] Stop ServerEncoder from unnecessarily allocating ByteBuffers
> --
>
> Key: QPID-7465
> URL: https://issues.apache.org/jira/browse/QPID-7465
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Lorenz Quack
> Attachments: QPID-7465.diff, QPID-7465_v2.diff
>
>
> As reported by [this email 
> thread|http://qpid.2158936.n2.nabble.com/java-broker-6-0-2-OOM-tp7651831.html]
>  the broker can currently run out of direct memory without flow-to-disk ever 
> kicking in.
> A defect in {{SeverEncoder#init()}} means that we allocate a new 8 kB direct 
> bytebuffer everytime it is called (i.e. on every AMQP 0-10 method or 
> command). This is wasteful and in some cases the GC does not collect these 
> direct byte buffers fast enough leading to the OOM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-7465) [Java Broker] Stop ServerEncoder from unnecessarily allocating ByteBuffers

2016-10-19 Thread Lorenz Quack (JIRA) 

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

Lorenz Quack updated QPID-7465:
---
Attachment: QPID-7465.diff

> [Java Broker] Stop ServerEncoder from unnecessarily allocating ByteBuffers
> --
>
> Key: QPID-7465
> URL: https://issues.apache.org/jira/browse/QPID-7465
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Lorenz Quack
> Attachments: QPID-7465.diff
>
>
> As reported by [this email 
> thread|http://qpid.2158936.n2.nabble.com/java-broker-6-0-2-OOM-tp7651831.html]
>  the broker can currently run out of direct memory without flow-to-disk ever 
> kicking in.
> A defect in {{SeverEncoder#init()}} means that we allocate a new 8 kB direct 
> bytebuffer everytime it is called (i.e. on every AMQP 0-10 method or 
> command). This is wasteful and in some cases the GC does not collect these 
> direct byte buffers fast enough leading to the OOM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-7465) [Java Broker] Stop ServerEncoder from unnecessarily allocating ByteBuffers

2016-10-19 Thread Lorenz Quack (JIRA) 
Lorenz Quack created QPID-7465:
--

 Summary: [Java Broker] Stop ServerEncoder from unnecessarily 
allocating ByteBuffers
 Key: QPID-7465
 URL: https://issues.apache.org/jira/browse/QPID-7465
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Reporter: Lorenz Quack


As reported by [this email 
thread|http://qpid.2158936.n2.nabble.com/java-broker-6-0-2-OOM-tp7651831.html] 
the broker can currently run out of direct memory without flow-to-disk ever 
kicking in.

A defect in {{SeverEncoder#init()}} means that we allocate a new 8 kB direct 
bytebuffer everytime it is called (i.e. on every AMQP 0-10 method or command). 
This is wasteful and in some cases the GC does not collect these direct byte 
buffers fast enough leading to the OOM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-531) Create an openstack horizon plugin

2016-10-19 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588669#comment-15588669
 ] 

ASF subversion and git services commented on DISPATCH-531:
--

Commit 0c58c3814866cbe60f13ff69ad73c74a4d8692aa in qpid-dispatch's branch 
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=0c58c38 ]

DISPATCH-531 Initial version of openstack horizon plugin


> Create an openstack horizon plugin
> --
>
> Key: DISPATCH-531
> URL: https://issues.apache.org/jira/browse/DISPATCH-531
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Console
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> Create a horizon plugin for the console. This is to be pip 
> installable/uninstallable in a devstack installation in the 
> /opt/stack/horizon directory.
> Not all console features need to be supported. The major functionality of the 
> overview and topology page should be supported.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-531) Create an openstack horizon plugin

2016-10-19 Thread Ernest Allen (JIRA) 
Ernest Allen created DISPATCH-531:
-

 Summary: Create an openstack horizon plugin
 Key: DISPATCH-531
 URL: https://issues.apache.org/jira/browse/DISPATCH-531
 Project: Qpid Dispatch
  Issue Type: Improvement
  Components: Console
Reporter: Ernest Allen
Assignee: Ernest Allen


Create a horizon plugin for the console. This is to be pip 
installable/uninstallable in a devstack installation in the /opt/stack/horizon 
directory.

Not all console features need to be supported. The major functionality of the 
overview and topology page should be supported.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: qpid-jms with C++ Broker - Does it support ByteMessage types from java?

2016-10-19 Thread Robbie Gemmell 
I'm not aware of any issues doing this, and I just modified the
HelloWorld example to use BytesMessage (with and without writing
content) and ran it against the 1.35.0 C++ broker without issue. I'd
be surprised if the older broker made a difference, but its possible I
guess.

Perhaps you can try looking at the logs to see if anything pops out.
Beyond the regular logging, if you run the client or broker with
PN_TRACE_FRM=true environment variable set you should see some
protocol trace logging to the console from Proton (which they both use
for their AMQP 1.0 support) which may further help in seeing whats
going on.

Questions like this are better suited to the users@ list rather than
dev@, plus theres a bigger audience and less other activity happening
to get in the way there.

Robbie

On 19 October 2016 at 01:06, bgercken  wrote:
> Hi
>
> I am using qpid-jms (qpid-jms-client-0.20.0-SNAPSHOT.jar) with the C++ qpid
> broker version 0.34 from java.
>
> I can successfully package and receive standard Message and TextMessage
> types but when I try to use a ByteMessage or a MapMessage type I never
> receive the message.
>
> I have included two examples below. I can provide more information if
> needed. I am hoping this is something simple that I am doing wrong.
>
> Thanks.
> -bill
>
> THIS WORKS:
>
> public void publishHostFinished( String hostName, String clientType,
> boolean success, String result ) {
> try {
> TextMessage message = session.createTextMessage();
> message.setBooleanProperty( "finished_state", 
> success);
> message.setStringProperty( "finished_result", result 
> );
> message.setStringProperty( "message_type", "FINISHED" 
> );
> publishHostTextMessage( message, hostName, 
> clientType, null );
> }
> catch( JMSException e ) {
> log.error( "Error while publishing finished for {} 
> client {}: {}",
> hostName, clientType, e.getLocalizedMessage() );
> }
> }
>
> private void publishHostTextMessage( TextMessage message, String hostName,
> String clientType, String body ) throws JMSException {
> message.setStringProperty( "host", hostName );
> message.setStringProperty( "client_type", clientType );
> message.setText( body );
> publisher.publish( message );
> }
>
> WHERE THIS WON'T:
>
> // TEST MESSAGE
> public void publishBufferedMessage( ) {
>
>
> System.out.println( "** PUBLISH BUFFERD 
> MESSAGE
> *" );
>
> Drive.Builder drive = Drive.newBuilder();
>
> drive.setSerial( "123-456-789" );
> drive.setComments( "This is drive: sda" );
> drive.setId(123);
> drive.setLabel( "DRIVE_LABEL" );
>
> drive.build();
>
> try {
>
> BytesMessage message = session.createBytesMessage();
>
> int messageSize = drive.build().getSerializedSize();
>
> message.setStringProperty( "message_type", "DRIVE_DATA" );
> message.setIntProperty( "message_encoded_size", messageSize );
>
> /**
> byte[] encodedMessage = new byte[messageSize];
>
> encodedMessage = drive.build().toByteArray();
>
> message.writeBytes( encodedMessage );
> **/
>
> publisher.publish( message );
>
> }
> catch( JMSException jmse ) {
> System.out.println( "error while publishing buffered 
> message: " +
> jmse.getLocalizedMessage() );
> }
> }
>
>
>
>
>
> --
> View this message in context: 
> http://qpid.2158936.n2.nabble.com/qpid-jms-with-C-Broker-Does-it-support-ByteMessage-types-from-java-tp7652144.html
> Sent from the Apache Qpid developers mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org