[jira] [Commented] (QPID-6146) Sending large persistent message to a DerbyVH caused the Broker to fail

2014-10-10 Thread Rob Godfrey (JIRA)

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

Rob Godfrey commented on QPID-6146:
---

Another aside: should we not upgrade our Derby dependency - we're using 
10.8.2.2 which is getting on for 3 years old now... 10.11.1.1 appears to be the 
latest. 

> Sending large persistent message to a DerbyVH caused the Broker to fail
> ---
>
> Key: QPID-6146
> URL: https://issues.apache.org/jira/browse/QPID-6146
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
> Environment: Mac OS X
> Darwin13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; 
> root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
> 1.7.0_45
>Reporter: Keith Wall
>
> I was able to cause the Broker by sending large persistent messages to the 
> Broker (using a DerbyVH).  My Java Client was non-transactional and there was 
> no consumer attached to the queue.  The message size was ~10MB.  The client 
> may have timed-out.
> I have been unable to reproduce again.
> {noformat}
> #
> # Exiting
> #
> 
> org.apache.qpid.server.store.StoreException: Error aborting transaction: No 
> current connection.
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore.abortTran(AbstractJDBCMessageStore.java:863)
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore.access$900(AbstractJDBCMessageStore.java:49)
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore$JDBCTransaction.abortTran(AbstractJDBCMessageStore.java:1267)
> at 
> org.apache.qpid.server.txn.AsyncAutoCommitTransaction.rollbackIfNecessary(AsyncAutoCommitTransaction.java:315)
> at 
> org.apache.qpid.server.txn.AsyncAutoCommitTransaction.enqueue(AsyncAutoCommitTransaction.java:274)
> at 
> org.apache.qpid.server.exchange.AbstractExchange.send(AbstractExchange.java:545)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.deliverCurrentMessageIfComplete(AMQChannel.java:408)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.publishContentBody(AMQChannel.java:518)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.contentBodyReceived(AMQProtocolEngine.java:692)
> at org.apache.qpid.framing.ContentBody.handle(ContentBody.java:72)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.frameReceived(AMQProtocolEngine.java:477)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.dataBlockReceived(AMQProtocolEngine.java:412)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.access$1100(AMQProtocolEngine.java:89)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:311)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:283)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:356)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:282)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:89)
> at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:133)
> at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:49)
> at 
> org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: java.sql.SQLNonTransientConnectionException: No current connection.
> at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.checkIfClosed(Unknown 
> Source)
> at 
> org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.rollback(Unknown Source)
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore.abortTran(AbstractJDBCMessageStore.java:858)
> ... 22 more
> Caused by: java.sql.SQLException: No current connection.
> at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
>  Source)
> ... 30 more
> Process

[jira] [Assigned] (QPID-6144) [Java Broker] Environment invalid JE exception occured while transferring Master

2014-10-10 Thread Alex Rudyy (JIRA)

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

Alex Rudyy reassigned QPID-6144:


Assignee: Keith Wall  (was: Alex Rudyy)

Keith,
Could you please review the changes?

> [Java Broker] Environment invalid JE exception occured while transferring 
> Master
> 
>
> Key: QPID-6144
> URL: https://issues.apache.org/jira/browse/QPID-6144
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30
>Reporter: Alex Rudyy
>Assignee: Keith Wall
>
> While running the java-bdb.0-9-1, experienced the following exception during 
> the MultiNodeTest.testTransferMasterWhilstMessagesInFlight which caused the 
> broker to die and the test to fail.
> {noformat}
> 
> #
> # Unhandled Exception java.lang.IllegalStateException: Attempt to use 
> non-open Environment object(). in Thread IoReceiver - /127.0.0.1:39306
> #
> # Exiting
> #
> 
> java.lang.IllegalStateException: Attempt to use non-open Environment object().
>   at 
> com.sleepycat.je.Environment.checkHandleIsValid(Environment.java:2193)
>   at 
> com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1347)
>   at com.sleepycat.je.Environment.beginTransaction(Environment.java:1319)
>   at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.removeMessage(AbstractBDBMessageStore.java:376)
>   at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.remove(AbstractBDBMessageStore.java:1436)
>   at 
> org.apache.qpid.server.message.AbstractServerMessageImpl.decrementReference(AbstractServerMessageImpl.java:101)
>   at 
> org.apache.qpid.server.message.AbstractServerMessageImpl.access$500(AbstractServerMessageImpl.java:37)
>   at 
> org.apache.qpid.server.message.AbstractServerMessageImpl$Reference.release(AbstractServerMessageImpl.java:275)
>   at 
> org.apache.qpid.server.exchange.AbstractExchange$2.onRollback(AbstractExchange.java:566)
>   at 
> org.apache.qpid.server.txn.LocalTransaction.doRollbackActions(LocalTransaction.java:270)
>   at 
> org.apache.qpid.server.txn.LocalTransaction.rollback(LocalTransaction.java:374)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.close(AMQChannel.java:739)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.close(AMQChannel.java:715)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeAllChannels(AMQProtocolEngine.java:942)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeSession(AMQProtocolEngine.java:981)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$3.run(AMQProtocolEngine.java:1035)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:356)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.runAsSubject(AMQProtocolEngine.java:223)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeSession(AMQProtocolEngine.java:1030)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closed(AMQProtocolEngine.java:1299)
>   at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.closed(MultiVersionProtocolEngine.java:117)
>   at 
> org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:222)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
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-6144) [Java Broker] Environment invalid JE exception occured while transferring Master

2014-10-10 Thread Alex Rudyy (JIRA)

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

Alex Rudyy updated QPID-6144:
-
Status: Reviewable  (was: In Progress)

> [Java Broker] Environment invalid JE exception occured while transferring 
> Master
> 
>
> Key: QPID-6144
> URL: https://issues.apache.org/jira/browse/QPID-6144
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>
> While running the java-bdb.0-9-1, experienced the following exception during 
> the MultiNodeTest.testTransferMasterWhilstMessagesInFlight which caused the 
> broker to die and the test to fail.
> {noformat}
> 
> #
> # Unhandled Exception java.lang.IllegalStateException: Attempt to use 
> non-open Environment object(). in Thread IoReceiver - /127.0.0.1:39306
> #
> # Exiting
> #
> 
> java.lang.IllegalStateException: Attempt to use non-open Environment object().
>   at 
> com.sleepycat.je.Environment.checkHandleIsValid(Environment.java:2193)
>   at 
> com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1347)
>   at com.sleepycat.je.Environment.beginTransaction(Environment.java:1319)
>   at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.removeMessage(AbstractBDBMessageStore.java:376)
>   at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.remove(AbstractBDBMessageStore.java:1436)
>   at 
> org.apache.qpid.server.message.AbstractServerMessageImpl.decrementReference(AbstractServerMessageImpl.java:101)
>   at 
> org.apache.qpid.server.message.AbstractServerMessageImpl.access$500(AbstractServerMessageImpl.java:37)
>   at 
> org.apache.qpid.server.message.AbstractServerMessageImpl$Reference.release(AbstractServerMessageImpl.java:275)
>   at 
> org.apache.qpid.server.exchange.AbstractExchange$2.onRollback(AbstractExchange.java:566)
>   at 
> org.apache.qpid.server.txn.LocalTransaction.doRollbackActions(LocalTransaction.java:270)
>   at 
> org.apache.qpid.server.txn.LocalTransaction.rollback(LocalTransaction.java:374)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.close(AMQChannel.java:739)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.close(AMQChannel.java:715)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeAllChannels(AMQProtocolEngine.java:942)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeSession(AMQProtocolEngine.java:981)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$3.run(AMQProtocolEngine.java:1035)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:356)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.runAsSubject(AMQProtocolEngine.java:223)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeSession(AMQProtocolEngine.java:1030)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closed(AMQProtocolEngine.java:1299)
>   at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.closed(MultiVersionProtocolEngine.java:117)
>   at 
> org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:222)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
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] [Assigned] (QPID-6144) [Java Broker] Environment invalid JE exception occured while transferring Master

2014-10-10 Thread Alex Rudyy (JIRA)

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

Alex Rudyy reassigned QPID-6144:


Assignee: Alex Rudyy

> [Java Broker] Environment invalid JE exception occured while transferring 
> Master
> 
>
> Key: QPID-6144
> URL: https://issues.apache.org/jira/browse/QPID-6144
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>
> While running the java-bdb.0-9-1, experienced the following exception during 
> the MultiNodeTest.testTransferMasterWhilstMessagesInFlight which caused the 
> broker to die and the test to fail.
> {noformat}
> 
> #
> # Unhandled Exception java.lang.IllegalStateException: Attempt to use 
> non-open Environment object(). in Thread IoReceiver - /127.0.0.1:39306
> #
> # Exiting
> #
> 
> java.lang.IllegalStateException: Attempt to use non-open Environment object().
>   at 
> com.sleepycat.je.Environment.checkHandleIsValid(Environment.java:2193)
>   at 
> com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1347)
>   at com.sleepycat.je.Environment.beginTransaction(Environment.java:1319)
>   at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.removeMessage(AbstractBDBMessageStore.java:376)
>   at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.remove(AbstractBDBMessageStore.java:1436)
>   at 
> org.apache.qpid.server.message.AbstractServerMessageImpl.decrementReference(AbstractServerMessageImpl.java:101)
>   at 
> org.apache.qpid.server.message.AbstractServerMessageImpl.access$500(AbstractServerMessageImpl.java:37)
>   at 
> org.apache.qpid.server.message.AbstractServerMessageImpl$Reference.release(AbstractServerMessageImpl.java:275)
>   at 
> org.apache.qpid.server.exchange.AbstractExchange$2.onRollback(AbstractExchange.java:566)
>   at 
> org.apache.qpid.server.txn.LocalTransaction.doRollbackActions(LocalTransaction.java:270)
>   at 
> org.apache.qpid.server.txn.LocalTransaction.rollback(LocalTransaction.java:374)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.close(AMQChannel.java:739)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.close(AMQChannel.java:715)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeAllChannels(AMQProtocolEngine.java:942)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeSession(AMQProtocolEngine.java:981)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$3.run(AMQProtocolEngine.java:1035)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:356)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.runAsSubject(AMQProtocolEngine.java:223)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeSession(AMQProtocolEngine.java:1030)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closed(AMQProtocolEngine.java:1299)
>   at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.closed(MultiVersionProtocolEngine.java:117)
>   at 
> org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:222)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
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-6144) [Java Broker] Environment invalid JE exception occured while transferring Master

2014-10-10 Thread ASF subversion and git services (JIRA)

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

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

Commit 1630956 from oru...@apache.org in branch 'qpid/trunk'
[ https://svn.apache.org/r1630956 ]

QPID-6144: Throw ConnectionScopedRuntimeException for IllegalStateException 
thrown from JE environment on restart

> [Java Broker] Environment invalid JE exception occured while transferring 
> Master
> 
>
> Key: QPID-6144
> URL: https://issues.apache.org/jira/browse/QPID-6144
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30
>Reporter: Alex Rudyy
>
> While running the java-bdb.0-9-1, experienced the following exception during 
> the MultiNodeTest.testTransferMasterWhilstMessagesInFlight which caused the 
> broker to die and the test to fail.
> {noformat}
> 
> #
> # Unhandled Exception java.lang.IllegalStateException: Attempt to use 
> non-open Environment object(). in Thread IoReceiver - /127.0.0.1:39306
> #
> # Exiting
> #
> 
> java.lang.IllegalStateException: Attempt to use non-open Environment object().
>   at 
> com.sleepycat.je.Environment.checkHandleIsValid(Environment.java:2193)
>   at 
> com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1347)
>   at com.sleepycat.je.Environment.beginTransaction(Environment.java:1319)
>   at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.removeMessage(AbstractBDBMessageStore.java:376)
>   at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.remove(AbstractBDBMessageStore.java:1436)
>   at 
> org.apache.qpid.server.message.AbstractServerMessageImpl.decrementReference(AbstractServerMessageImpl.java:101)
>   at 
> org.apache.qpid.server.message.AbstractServerMessageImpl.access$500(AbstractServerMessageImpl.java:37)
>   at 
> org.apache.qpid.server.message.AbstractServerMessageImpl$Reference.release(AbstractServerMessageImpl.java:275)
>   at 
> org.apache.qpid.server.exchange.AbstractExchange$2.onRollback(AbstractExchange.java:566)
>   at 
> org.apache.qpid.server.txn.LocalTransaction.doRollbackActions(LocalTransaction.java:270)
>   at 
> org.apache.qpid.server.txn.LocalTransaction.rollback(LocalTransaction.java:374)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.close(AMQChannel.java:739)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.close(AMQChannel.java:715)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeAllChannels(AMQProtocolEngine.java:942)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeSession(AMQProtocolEngine.java:981)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$3.run(AMQProtocolEngine.java:1035)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:356)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.runAsSubject(AMQProtocolEngine.java:223)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeSession(AMQProtocolEngine.java:1030)
>   at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closed(AMQProtocolEngine.java:1299)
>   at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.closed(MultiVersionProtocolEngine.java:117)
>   at 
> org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:222)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
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-6140) [C++ Messaging] UI Gotchya in Hello World example

2014-10-10 Thread ASF subversion and git services (JIRA)

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

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

Commit 1630945 from c...@apache.org in branch 'qpid/trunk'
[ https://svn.apache.org/r1630945 ]

QPID-6140: [C++ Messaging] hello_world does not define Messaging i/f completely
Add qpidtypes to hello_world and hello_xml example link library list so that 
users can execute any Messaging function straight away.

> [C++ Messaging] UI Gotchya in Hello World example
> -
>
> Key: QPID-6140
> URL: https://issues.apache.org/jira/browse/QPID-6140
> Project: Qpid
>  Issue Type: Improvement
>  Components: Qpid Examples
>Affects Versions: 0.30
> Environment: Fedora 19, trunk build
>Reporter: Chuck Rolke
>
> Modifying hello_world.cpp to add a simple property to a message 
> {noformat}
> Message message("Hello world");
> message.getProperties()["id"] = 1;
> {noformat}
> fails:
> {noformat}
> Linking CXX executable hello_world
> /usr/bin/ld: CMakeFiles/hello_world.dir/hello_world.o: undefined reference to 
> symbol '_ZN4qpid5types7VariantC1ERKS1_'
> /usr/bin/ld: note: '_ZN4qpid5types7VariantC1ERKS1_' is defined in DSO 
> /home/chug/git/qpid/build/src/libqpidtypes.so.1 so try adding it to the 
> linker command line
> /home/chug/git/qpid/build/src/libqpidtypes.so.1: could not read symbols: 
> Invalid operation
> collect2: error: ld returned 1 exit status
> make[2]: *** [examples/messaging/hello_world] Error 1
> make[1]: *** [examples/messaging/CMakeFiles/hello_world.dir/all] Error 2
> make: *** [all] Error 2
> *** Failure: Exit code 2 ***
> {noformat}
> What? What's with qpid::types::Variant? The user is adding a property as 
> specified in the Messaging API spec.
> To fix this a user must find hello_world in the cmake file and add 
> 'qpidtypes' as a link library, rerun cmake, and then rebuild. Strictly 
> speaking qpidtypes isn't needed for the simplest hello_world case. That said, 
> qpidtypes is linked to qpidmessaging and must be available for hello_world to 
> run.
> Adding qpidtypes to hello_world's target_link_libraries will help new users 
> experiment with Qpid Messaging more fluently.



--
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-6146) Sending large persistent message to a DerbyVH caused the Broker to fail

2014-10-10 Thread Rob Godfrey (JIRA)

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

Rob Godfrey commented on QPID-6146:
---

Don't suppose you have the derby.log from when this occurred?  A bit of 
Googling suggests that this tends to occur when there has been a prior error in 
Derby.

As an aside to that we should look at trying to redirect the derby logs into 
the standard Qpid logs...  Not sure if there is a better mechanism than setting 
a system property: 
http://db.apache.org/derby/docs/10.3/tuning/rtunproper35028.html#rtunproper35028



> Sending large persistent message to a DerbyVH caused the Broker to fail
> ---
>
> Key: QPID-6146
> URL: https://issues.apache.org/jira/browse/QPID-6146
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
> Environment: Mac OS X
> Darwin13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; 
> root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
> 1.7.0_45
>Reporter: Keith Wall
>
> I was able to cause the Broker by sending large persistent messages to the 
> Broker (using a DerbyVH).  My Java Client was non-transactional and there was 
> no consumer attached to the queue.  The message size was ~10MB.  The client 
> may have timed-out.
> I have been unable to reproduce again.
> {noformat}
> #
> # Exiting
> #
> 
> org.apache.qpid.server.store.StoreException: Error aborting transaction: No 
> current connection.
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore.abortTran(AbstractJDBCMessageStore.java:863)
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore.access$900(AbstractJDBCMessageStore.java:49)
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore$JDBCTransaction.abortTran(AbstractJDBCMessageStore.java:1267)
> at 
> org.apache.qpid.server.txn.AsyncAutoCommitTransaction.rollbackIfNecessary(AsyncAutoCommitTransaction.java:315)
> at 
> org.apache.qpid.server.txn.AsyncAutoCommitTransaction.enqueue(AsyncAutoCommitTransaction.java:274)
> at 
> org.apache.qpid.server.exchange.AbstractExchange.send(AbstractExchange.java:545)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.deliverCurrentMessageIfComplete(AMQChannel.java:408)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.publishContentBody(AMQChannel.java:518)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.contentBodyReceived(AMQProtocolEngine.java:692)
> at org.apache.qpid.framing.ContentBody.handle(ContentBody.java:72)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.frameReceived(AMQProtocolEngine.java:477)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.dataBlockReceived(AMQProtocolEngine.java:412)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.access$1100(AMQProtocolEngine.java:89)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:311)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:283)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:356)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:282)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:89)
> at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:133)
> at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:49)
> at 
> org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: java.sql.SQLNonTransientConnectionException: No current connection.
> at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.checkIfClosed(Unknown 
> Source)
> at 
> org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.rollback(Unknown Source)
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore.abortTran(AbstractJDBCMessageStore.java:858)
> ... 22 more
> Caused by: java.sql.SQLException: No 

[jira] [Updated] (QPID-6146) Sending large persistent message to a DerbyVH cause the Broker to fail

2014-10-10 Thread Keith Wall (JIRA)

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

Keith Wall updated QPID-6146:
-
Summary: Sending large persistent message to a DerbyVH cause the Broker to 
fail  (was: Sending large persistent message to the DerbyVH cause the Broker to 
fail)

> Sending large persistent message to a DerbyVH cause the Broker to fail
> --
>
> Key: QPID-6146
> URL: https://issues.apache.org/jira/browse/QPID-6146
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
> Environment: Mac OS X
> Darwin13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; 
> root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
> 1.7.0_45
>Reporter: Keith Wall
>
> I was able to cause the Broker by sending large persistent messages to the 
> Broker (using a DerbyVH).  My Java Client was non-transactional and there was 
> no consumer attached to the queue.  The message size was ~10MB.  The client 
> may have timed-out.
> I have been unable to reproduce again.
> {noformat}
> #
> # Exiting
> #
> 
> org.apache.qpid.server.store.StoreException: Error aborting transaction: No 
> current connection.
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore.abortTran(AbstractJDBCMessageStore.java:863)
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore.access$900(AbstractJDBCMessageStore.java:49)
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore$JDBCTransaction.abortTran(AbstractJDBCMessageStore.java:1267)
> at 
> org.apache.qpid.server.txn.AsyncAutoCommitTransaction.rollbackIfNecessary(AsyncAutoCommitTransaction.java:315)
> at 
> org.apache.qpid.server.txn.AsyncAutoCommitTransaction.enqueue(AsyncAutoCommitTransaction.java:274)
> at 
> org.apache.qpid.server.exchange.AbstractExchange.send(AbstractExchange.java:545)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.deliverCurrentMessageIfComplete(AMQChannel.java:408)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.publishContentBody(AMQChannel.java:518)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.contentBodyReceived(AMQProtocolEngine.java:692)
> at org.apache.qpid.framing.ContentBody.handle(ContentBody.java:72)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.frameReceived(AMQProtocolEngine.java:477)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.dataBlockReceived(AMQProtocolEngine.java:412)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.access$1100(AMQProtocolEngine.java:89)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:311)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:283)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:356)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:282)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:89)
> at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:133)
> at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:49)
> at 
> org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: java.sql.SQLNonTransientConnectionException: No current connection.
> at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.checkIfClosed(Unknown 
> Source)
> at 
> org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.rollback(Unknown Source)
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore.abortTran(AbstractJDBCMessageStore.java:858)
> ... 22 more
> Caused by: java.sql.SQLException: No current connection.
> at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
>  Source)
> ... 30 more
> Process finished with exit code 1
> {noformat}



--
This message

[jira] [Updated] (QPID-6146) Sending large persistent message to a DerbyVH caused the Broker to fail

2014-10-10 Thread Keith Wall (JIRA)

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

Keith Wall updated QPID-6146:
-
Summary: Sending large persistent message to a DerbyVH caused the Broker to 
fail  (was: Sending large persistent message to a DerbyVH cause the Broker to 
fail)

> Sending large persistent message to a DerbyVH caused the Broker to fail
> ---
>
> Key: QPID-6146
> URL: https://issues.apache.org/jira/browse/QPID-6146
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
> Environment: Mac OS X
> Darwin13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; 
> root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
> 1.7.0_45
>Reporter: Keith Wall
>
> I was able to cause the Broker by sending large persistent messages to the 
> Broker (using a DerbyVH).  My Java Client was non-transactional and there was 
> no consumer attached to the queue.  The message size was ~10MB.  The client 
> may have timed-out.
> I have been unable to reproduce again.
> {noformat}
> #
> # Exiting
> #
> 
> org.apache.qpid.server.store.StoreException: Error aborting transaction: No 
> current connection.
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore.abortTran(AbstractJDBCMessageStore.java:863)
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore.access$900(AbstractJDBCMessageStore.java:49)
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore$JDBCTransaction.abortTran(AbstractJDBCMessageStore.java:1267)
> at 
> org.apache.qpid.server.txn.AsyncAutoCommitTransaction.rollbackIfNecessary(AsyncAutoCommitTransaction.java:315)
> at 
> org.apache.qpid.server.txn.AsyncAutoCommitTransaction.enqueue(AsyncAutoCommitTransaction.java:274)
> at 
> org.apache.qpid.server.exchange.AbstractExchange.send(AbstractExchange.java:545)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.deliverCurrentMessageIfComplete(AMQChannel.java:408)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQChannel.publishContentBody(AMQChannel.java:518)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.contentBodyReceived(AMQProtocolEngine.java:692)
> at org.apache.qpid.framing.ContentBody.handle(ContentBody.java:72)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.frameReceived(AMQProtocolEngine.java:477)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.dataBlockReceived(AMQProtocolEngine.java:412)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.access$1100(AMQProtocolEngine.java:89)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:311)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:283)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:356)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:282)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:89)
> at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:133)
> at 
> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:49)
> at 
> org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: java.sql.SQLNonTransientConnectionException: No current connection.
> at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown 
> Source)
> at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.checkIfClosed(Unknown 
> Source)
> at 
> org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.rollback(Unknown Source)
> at 
> org.apache.qpid.server.store.AbstractJDBCMessageStore.abortTran(AbstractJDBCMessageStore.java:858)
> ... 22 more
> Caused by: java.sql.SQLException: No current connection.
> at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
>  Source)
> ... 30 more
> Process finished with exit code 1
> {noformat}



--
This messag

[jira] [Created] (QPID-6146) Sending large persistent message to the DerbyVH cause the Broker to fail

2014-10-10 Thread Keith Wall (JIRA)
Keith Wall created QPID-6146:


 Summary: Sending large persistent message to the DerbyVH cause the 
Broker to fail
 Key: QPID-6146
 URL: https://issues.apache.org/jira/browse/QPID-6146
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
 Environment: Mac OS X
Darwin13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; 
root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
1.7.0_45

Reporter: Keith Wall


I was able to cause the Broker by sending large persistent messages to the 
Broker (using a DerbyVH).  My Java Client was non-transactional and there was 
no consumer attached to the queue.  The message size was ~10MB.  The client may 
have timed-out.

I have been unable to reproduce again.

{noformat}
#
# Exiting
#

org.apache.qpid.server.store.StoreException: Error aborting transaction: No 
current connection.
at 
org.apache.qpid.server.store.AbstractJDBCMessageStore.abortTran(AbstractJDBCMessageStore.java:863)
at 
org.apache.qpid.server.store.AbstractJDBCMessageStore.access$900(AbstractJDBCMessageStore.java:49)
at 
org.apache.qpid.server.store.AbstractJDBCMessageStore$JDBCTransaction.abortTran(AbstractJDBCMessageStore.java:1267)
at 
org.apache.qpid.server.txn.AsyncAutoCommitTransaction.rollbackIfNecessary(AsyncAutoCommitTransaction.java:315)
at 
org.apache.qpid.server.txn.AsyncAutoCommitTransaction.enqueue(AsyncAutoCommitTransaction.java:274)
at 
org.apache.qpid.server.exchange.AbstractExchange.send(AbstractExchange.java:545)
at 
org.apache.qpid.server.protocol.v0_8.AMQChannel.deliverCurrentMessageIfComplete(AMQChannel.java:408)
at 
org.apache.qpid.server.protocol.v0_8.AMQChannel.publishContentBody(AMQChannel.java:518)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.contentBodyReceived(AMQProtocolEngine.java:692)
at org.apache.qpid.framing.ContentBody.handle(ContentBody.java:72)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.frameReceived(AMQProtocolEngine.java:477)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.dataBlockReceived(AMQProtocolEngine.java:412)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.access$1100(AMQProtocolEngine.java:89)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:311)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:283)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:356)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:282)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:89)
at 
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:133)
at 
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:49)
at 
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.sql.SQLNonTransientConnectionException: No current connection.
at 
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.checkIfClosed(Unknown 
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown 
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.rollback(Unknown Source)
at 
org.apache.qpid.server.store.AbstractJDBCMessageStore.abortTran(AbstractJDBCMessageStore.java:858)
... 22 more
Caused by: java.sql.SQLException: No current connection.
at 
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
at 
org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
 Source)
... 30 more

Process finished with exit code 1
{noformat}



--
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-6145) Write operational log messages when flow to disk activates/deactivates

2014-10-10 Thread ASF subversion and git services (JIRA)

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

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

Commit 1630926 from [~k-wall] in branch 'qpid/trunk'
[ https://svn.apache.org/r1630926 ]

QPID-6145: [Java Broker] Write operational log message when flow to disk 
activates/deactivates

> Write operational log messages when flow to disk activates/deactivates
> --
>
> Key: QPID-6145
> URL: https://issues.apache.org/jira/browse/QPID-6145
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Priority: Minor
>
> QPID-5965 introduced a flow to transient message to disk mechanism to prevent 
> the Java Broker filling all available heap with transient messages.   The 
> operational/diagnostic reasons it will be advantageous to have simple logging 
> to indicate when the mechanism activates/deactivates.
> This change will introduce such operational logging.



--
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-6145) Write operational log messages when flow to disk activates/deactivates

2014-10-10 Thread Keith Wall (JIRA)
Keith Wall created QPID-6145:


 Summary: Write operational log messages when flow to disk 
activates/deactivates
 Key: QPID-6145
 URL: https://issues.apache.org/jira/browse/QPID-6145
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Reporter: Keith Wall
Priority: Minor


QPID-5965 introduced a flow to transient message to disk mechanism to prevent 
the Java Broker filling all available heap with transient messages.   The 
operational/diagnostic reasons it will be advantageous to have simple logging 
to indicate when the mechanism activates/deactivates.

This change will introduce such operational logging.



--
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-6144) [Java Broker] Environment invalid JE exception occured while transferring Master

2014-10-10 Thread Alex Rudyy (JIRA)
Alex Rudyy created QPID-6144:


 Summary: [Java Broker] Environment invalid JE exception occured 
while transferring Master
 Key: QPID-6144
 URL: https://issues.apache.org/jira/browse/QPID-6144
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.30
Reporter: Alex Rudyy


While running the java-bdb.0-9-1, experienced the following exception during 
the MultiNodeTest.testTransferMasterWhilstMessagesInFlight which caused the 
broker to die and the test to fail.

{noformat}

#
# Unhandled Exception java.lang.IllegalStateException: Attempt to use non-open 
Environment object(). in Thread IoReceiver - /127.0.0.1:39306
#
# Exiting
#

java.lang.IllegalStateException: Attempt to use non-open Environment object().
at 
com.sleepycat.je.Environment.checkHandleIsValid(Environment.java:2193)
at 
com.sleepycat.je.Environment.beginTransactionInternal(Environment.java:1347)
at com.sleepycat.je.Environment.beginTransaction(Environment.java:1319)
at 
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.removeMessage(AbstractBDBMessageStore.java:376)
at 
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.remove(AbstractBDBMessageStore.java:1436)
at 
org.apache.qpid.server.message.AbstractServerMessageImpl.decrementReference(AbstractServerMessageImpl.java:101)
at 
org.apache.qpid.server.message.AbstractServerMessageImpl.access$500(AbstractServerMessageImpl.java:37)
at 
org.apache.qpid.server.message.AbstractServerMessageImpl$Reference.release(AbstractServerMessageImpl.java:275)
at 
org.apache.qpid.server.exchange.AbstractExchange$2.onRollback(AbstractExchange.java:566)
at 
org.apache.qpid.server.txn.LocalTransaction.doRollbackActions(LocalTransaction.java:270)
at 
org.apache.qpid.server.txn.LocalTransaction.rollback(LocalTransaction.java:374)
at 
org.apache.qpid.server.protocol.v0_8.AMQChannel.close(AMQChannel.java:739)
at 
org.apache.qpid.server.protocol.v0_8.AMQChannel.close(AMQChannel.java:715)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeAllChannels(AMQProtocolEngine.java:942)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeSession(AMQProtocolEngine.java:981)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$3.run(AMQProtocolEngine.java:1035)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:356)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.runAsSubject(AMQProtocolEngine.java:223)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closeSession(AMQProtocolEngine.java:1030)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.closed(AMQProtocolEngine.java:1299)
at 
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.closed(MultiVersionProtocolEngine.java:117)
at 
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:222)
at java.lang.Thread.run(Thread.java:745)
{noformat}



--
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] [Assigned] (QPID-6143) [Java Broker] Broker can crash on publishing/consuming messages during master transfer in BDB HA group

2014-10-10 Thread Alex Rudyy (JIRA)

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

Alex Rudyy reassigned QPID-6143:


Assignee: Alex Rudyy

> [Java Broker] Broker can crash on publishing/consuming messages during master 
> transfer in BDB HA group 
> ---
>
> Key: QPID-6143
> URL: https://issues.apache.org/jira/browse/QPID-6143
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>
> I built 3 node cluster and started a sample java app publishing and consuming 
> messages into/from a Master node.
> During publishing/consuming I was flipping mastership between 1st and 2d 
> nodes from 3d node using the following script
> {noformat}
> while true; do (curl --user admin:admin -X PUT  -d '{"role":"MASTER"}' 
> http://localhost:8082/api/latest/replicationnode/node3/node2; sleep 1; curl 
> -s --user admin:admin -X GET  
> http://localhost:8081/api/latest/virtualhostnode/node2 | grep "name\|role" ;  
> curl --user admin:admin -X PUT  -d '{"role":"MASTER"}' 
> http://localhost:8082/api/latest/replicationnode/node3/node1 ; sleep 1; curl 
> -s --user admin:admin -X GET  
> http://localhost:8080/api/latest/virtualhostnode/node1 | grep "name\|role") 
> done
> {noformat}
> In some cases, on message delivery when node was in a process of state change 
> from MASTER to REPLICA I've seen the following broker crush
> {noformat}
> 
> #
> # Unhandled Exception java.lang.IllegalStateException: Environment is not 
> valid in Thread pool-187-thread-21
> #
> # Exiting
> #
> 
> java.lang.IllegalStateException: Environment is not valid
> at 
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.openDatabase(ReplicatedEnvironmentFacade.java:460)
> at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.getMessageContentDb(AbstractBDBMessageStore.java:1057)
> at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.getAllContent(AbstractBDBMessageStore.java:579)
> at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.getContent(AbstractBDBMessageStore.java:1319)
> at 
> org.apache.qpid.server.message.AbstractServerMessageImpl.getContent(AbstractServerMessageImpl.java:171)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl$MessageContentSourceBody.writePayload(ProtocolOutputConverterImpl.java:251)
> at org.apache.qpid.framing.AMQFrame.writeFrames(AMQFrame.java:123)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl$CompositeAMQBodyBlock.writePayload(ProtocolOutputConverterImpl.java:468)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.asByteBuffer(AMQProtocolEngine.java:595)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.writeFrame(AMQProtocolEngine.java:709)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeFrame(ProtocolOutputConverterImpl.java:430)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDeliveryUnchanged(ProtocolOutputConverterImpl.java:207)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:141)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:101)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeDeliver(ProtocolOutputConverterImpl.java:78)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$WriteDeliverMethod.deliverToClient(AMQProtocolEngine.java:1626)
> at 
> org.apache.qpid.server.protocol.v0_8.ConsumerTarget_0_8.sendToClient(ConsumerTarget_0_8.java:513)
> at 
> org.apache.qpid.server.protocol.v0_8.ConsumerTarget_0_8$AckConsumer.send(ConsumerTarget_0_8.java:317)
> at 
> org.apache.qpid.server.queue.QueueConsumerImpl.send(QueueConsumerImpl.java:475)
> at 
> org.apache.qpid.server.queue.AbstractQueue.deliverMessage(AbstractQueue.java:1235)
> at 
> org.apache.qpid.server.queue.AbstractQueue.attemptDelivery(AbstractQueue.java:1989)
> at 
> org.apache.qpid.server.queue.AbstractQueue.processQueue(AbstractQueue.java:2160)
> at org.apache.qpid.server.queue.QueueRunner$1.run(QueueRunner.java:77)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:356)
> at org.apache.qpid.server.queue.QueueRunner.run(QueueRunner.java:68)
> 

[jira] [Assigned] (QPID-6143) [Java Broker] Broker can crash on publishing/consuming messages during master transfer in BDB HA group

2014-10-10 Thread Alex Rudyy (JIRA)

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

Alex Rudyy reassigned QPID-6143:


Assignee: Keith Wall  (was: Alex Rudyy)

Keith,

Could you please review committed changes?

> [Java Broker] Broker can crash on publishing/consuming messages during master 
> transfer in BDB HA group 
> ---
>
> Key: QPID-6143
> URL: https://issues.apache.org/jira/browse/QPID-6143
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30
>Reporter: Alex Rudyy
>Assignee: Keith Wall
>
> I built 3 node cluster and started a sample java app publishing and consuming 
> messages into/from a Master node.
> During publishing/consuming I was flipping mastership between 1st and 2d 
> nodes from 3d node using the following script
> {noformat}
> while true; do (curl --user admin:admin -X PUT  -d '{"role":"MASTER"}' 
> http://localhost:8082/api/latest/replicationnode/node3/node2; sleep 1; curl 
> -s --user admin:admin -X GET  
> http://localhost:8081/api/latest/virtualhostnode/node2 | grep "name\|role" ;  
> curl --user admin:admin -X PUT  -d '{"role":"MASTER"}' 
> http://localhost:8082/api/latest/replicationnode/node3/node1 ; sleep 1; curl 
> -s --user admin:admin -X GET  
> http://localhost:8080/api/latest/virtualhostnode/node1 | grep "name\|role") 
> done
> {noformat}
> In some cases, on message delivery when node was in a process of state change 
> from MASTER to REPLICA I've seen the following broker crush
> {noformat}
> 
> #
> # Unhandled Exception java.lang.IllegalStateException: Environment is not 
> valid in Thread pool-187-thread-21
> #
> # Exiting
> #
> 
> java.lang.IllegalStateException: Environment is not valid
> at 
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.openDatabase(ReplicatedEnvironmentFacade.java:460)
> at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.getMessageContentDb(AbstractBDBMessageStore.java:1057)
> at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.getAllContent(AbstractBDBMessageStore.java:579)
> at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.getContent(AbstractBDBMessageStore.java:1319)
> at 
> org.apache.qpid.server.message.AbstractServerMessageImpl.getContent(AbstractServerMessageImpl.java:171)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl$MessageContentSourceBody.writePayload(ProtocolOutputConverterImpl.java:251)
> at org.apache.qpid.framing.AMQFrame.writeFrames(AMQFrame.java:123)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl$CompositeAMQBodyBlock.writePayload(ProtocolOutputConverterImpl.java:468)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.asByteBuffer(AMQProtocolEngine.java:595)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.writeFrame(AMQProtocolEngine.java:709)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeFrame(ProtocolOutputConverterImpl.java:430)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDeliveryUnchanged(ProtocolOutputConverterImpl.java:207)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:141)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:101)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeDeliver(ProtocolOutputConverterImpl.java:78)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$WriteDeliverMethod.deliverToClient(AMQProtocolEngine.java:1626)
> at 
> org.apache.qpid.server.protocol.v0_8.ConsumerTarget_0_8.sendToClient(ConsumerTarget_0_8.java:513)
> at 
> org.apache.qpid.server.protocol.v0_8.ConsumerTarget_0_8$AckConsumer.send(ConsumerTarget_0_8.java:317)
> at 
> org.apache.qpid.server.queue.QueueConsumerImpl.send(QueueConsumerImpl.java:475)
> at 
> org.apache.qpid.server.queue.AbstractQueue.deliverMessage(AbstractQueue.java:1235)
> at 
> org.apache.qpid.server.queue.AbstractQueue.attemptDelivery(AbstractQueue.java:1989)
> at 
> org.apache.qpid.server.queue.AbstractQueue.processQueue(AbstractQueue.java:2160)
> at org.apache.qpid.server.queue.QueueRunner$1.run(QueueRunner.java:77)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:356)
> 

[jira] [Updated] (QPID-6143) [Java Broker] Broker can crash on publishing/consuming messages during master transfer in BDB HA group

2014-10-10 Thread Alex Rudyy (JIRA)

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

Alex Rudyy updated QPID-6143:
-
Status: Reviewable  (was: In Progress)

> [Java Broker] Broker can crash on publishing/consuming messages during master 
> transfer in BDB HA group 
> ---
>
> Key: QPID-6143
> URL: https://issues.apache.org/jira/browse/QPID-6143
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>
> I built 3 node cluster and started a sample java app publishing and consuming 
> messages into/from a Master node.
> During publishing/consuming I was flipping mastership between 1st and 2d 
> nodes from 3d node using the following script
> {noformat}
> while true; do (curl --user admin:admin -X PUT  -d '{"role":"MASTER"}' 
> http://localhost:8082/api/latest/replicationnode/node3/node2; sleep 1; curl 
> -s --user admin:admin -X GET  
> http://localhost:8081/api/latest/virtualhostnode/node2 | grep "name\|role" ;  
> curl --user admin:admin -X PUT  -d '{"role":"MASTER"}' 
> http://localhost:8082/api/latest/replicationnode/node3/node1 ; sleep 1; curl 
> -s --user admin:admin -X GET  
> http://localhost:8080/api/latest/virtualhostnode/node1 | grep "name\|role") 
> done
> {noformat}
> In some cases, on message delivery when node was in a process of state change 
> from MASTER to REPLICA I've seen the following broker crush
> {noformat}
> 
> #
> # Unhandled Exception java.lang.IllegalStateException: Environment is not 
> valid in Thread pool-187-thread-21
> #
> # Exiting
> #
> 
> java.lang.IllegalStateException: Environment is not valid
> at 
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.openDatabase(ReplicatedEnvironmentFacade.java:460)
> at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.getMessageContentDb(AbstractBDBMessageStore.java:1057)
> at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.getAllContent(AbstractBDBMessageStore.java:579)
> at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.getContent(AbstractBDBMessageStore.java:1319)
> at 
> org.apache.qpid.server.message.AbstractServerMessageImpl.getContent(AbstractServerMessageImpl.java:171)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl$MessageContentSourceBody.writePayload(ProtocolOutputConverterImpl.java:251)
> at org.apache.qpid.framing.AMQFrame.writeFrames(AMQFrame.java:123)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl$CompositeAMQBodyBlock.writePayload(ProtocolOutputConverterImpl.java:468)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.asByteBuffer(AMQProtocolEngine.java:595)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.writeFrame(AMQProtocolEngine.java:709)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeFrame(ProtocolOutputConverterImpl.java:430)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDeliveryUnchanged(ProtocolOutputConverterImpl.java:207)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:141)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:101)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeDeliver(ProtocolOutputConverterImpl.java:78)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$WriteDeliverMethod.deliverToClient(AMQProtocolEngine.java:1626)
> at 
> org.apache.qpid.server.protocol.v0_8.ConsumerTarget_0_8.sendToClient(ConsumerTarget_0_8.java:513)
> at 
> org.apache.qpid.server.protocol.v0_8.ConsumerTarget_0_8$AckConsumer.send(ConsumerTarget_0_8.java:317)
> at 
> org.apache.qpid.server.queue.QueueConsumerImpl.send(QueueConsumerImpl.java:475)
> at 
> org.apache.qpid.server.queue.AbstractQueue.deliverMessage(AbstractQueue.java:1235)
> at 
> org.apache.qpid.server.queue.AbstractQueue.attemptDelivery(AbstractQueue.java:1989)
> at 
> org.apache.qpid.server.queue.AbstractQueue.processQueue(AbstractQueue.java:2160)
> at org.apache.qpid.server.queue.QueueRunner$1.run(QueueRunner.java:77)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:356)
> at org.apache.qpid.server.queue.QueueRunner.run(QueueRunner.

[jira] [Commented] (QPID-6143) [Java Broker] Broker can crash on publishing/consuming messages during master transfer in BDB HA group

2014-10-10 Thread ASF subversion and git services (JIRA)

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

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

Commit 1630922 from oru...@apache.org in branch 'qpid/trunk'
[ https://svn.apache.org/r1630922 ]

QPID-6143: Throw ConnectionScopedRuntimeException from 
ReplicatedEnvironmentFacade.openDatabase if facade is not opened or environment 
is invalid

> [Java Broker] Broker can crash on publishing/consuming messages during master 
> transfer in BDB HA group 
> ---
>
> Key: QPID-6143
> URL: https://issues.apache.org/jira/browse/QPID-6143
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30
>Reporter: Alex Rudyy
>
> I built 3 node cluster and started a sample java app publishing and consuming 
> messages into/from a Master node.
> During publishing/consuming I was flipping mastership between 1st and 2d 
> nodes from 3d node using the following script
> {noformat}
> while true; do (curl --user admin:admin -X PUT  -d '{"role":"MASTER"}' 
> http://localhost:8082/api/latest/replicationnode/node3/node2; sleep 1; curl 
> -s --user admin:admin -X GET  
> http://localhost:8081/api/latest/virtualhostnode/node2 | grep "name\|role" ;  
> curl --user admin:admin -X PUT  -d '{"role":"MASTER"}' 
> http://localhost:8082/api/latest/replicationnode/node3/node1 ; sleep 1; curl 
> -s --user admin:admin -X GET  
> http://localhost:8080/api/latest/virtualhostnode/node1 | grep "name\|role") 
> done
> {noformat}
> In some cases, on message delivery when node was in a process of state change 
> from MASTER to REPLICA I've seen the following broker crush
> {noformat}
> 
> #
> # Unhandled Exception java.lang.IllegalStateException: Environment is not 
> valid in Thread pool-187-thread-21
> #
> # Exiting
> #
> 
> java.lang.IllegalStateException: Environment is not valid
> at 
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.openDatabase(ReplicatedEnvironmentFacade.java:460)
> at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.getMessageContentDb(AbstractBDBMessageStore.java:1057)
> at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.getAllContent(AbstractBDBMessageStore.java:579)
> at 
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.getContent(AbstractBDBMessageStore.java:1319)
> at 
> org.apache.qpid.server.message.AbstractServerMessageImpl.getContent(AbstractServerMessageImpl.java:171)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl$MessageContentSourceBody.writePayload(ProtocolOutputConverterImpl.java:251)
> at org.apache.qpid.framing.AMQFrame.writeFrames(AMQFrame.java:123)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl$CompositeAMQBodyBlock.writePayload(ProtocolOutputConverterImpl.java:468)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.asByteBuffer(AMQProtocolEngine.java:595)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.writeFrame(AMQProtocolEngine.java:709)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeFrame(ProtocolOutputConverterImpl.java:430)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDeliveryUnchanged(ProtocolOutputConverterImpl.java:207)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:141)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:101)
> at 
> org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeDeliver(ProtocolOutputConverterImpl.java:78)
> at 
> org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$WriteDeliverMethod.deliverToClient(AMQProtocolEngine.java:1626)
> at 
> org.apache.qpid.server.protocol.v0_8.ConsumerTarget_0_8.sendToClient(ConsumerTarget_0_8.java:513)
> at 
> org.apache.qpid.server.protocol.v0_8.ConsumerTarget_0_8$AckConsumer.send(ConsumerTarget_0_8.java:317)
> at 
> org.apache.qpid.server.queue.QueueConsumerImpl.send(QueueConsumerImpl.java:475)
> at 
> org.apache.qpid.server.queue.AbstractQueue.deliverMessage(AbstractQueue.java:1235)
> at 
> org.apache.qpid.server.queue.AbstractQueue.attemptDelivery(AbstractQueue.java:1989)
> at 
> org.apache.qpid.server.queue.AbstractQueue.processQueue(AbstractQueue.java:2160)
> 

[jira] [Commented] (QPID-5535) Memory leak in Perl bindings when fetch() called with duration

2014-10-10 Thread Darryl L. Pierce (JIRA)

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

Darryl L. Pierce commented on QPID-5535:


Looking into this again, the memory leak is very specific. In testing I'm 
seeing a 33 byte steady leak, whatever the increment is. I set the duration to 
10ms and it was pretty quick. I set it to 1000ms and it takes far longer than 
30 seconds to leak. But not matter what it doesn't happen while messages are 
being sent.


> Memory leak in Perl bindings when fetch() called with duration
> --
>
> Key: QPID-5535
> URL: https://issues.apache.org/jira/browse/QPID-5535
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker, Perl Client
>Affects Versions: 0.24
> Environment: RHEL6/2.6.32-220.13.1.el6.x86_64 swig-1.3.40-6.el6
>Reporter: Hazel Bobrins
>Assignee: Darryl L. Pierce
> Attachments: drain_duration.pl
>
>
> When fetch() is called with a duration and no messages exist memory is leaked
> How to reproduce
> Create a queue
> Run attached code example
> Watch memory stats
> Example memory stats while running the above
> time,VmPeak,VmSize,VmHWM,VmRSS,VmData,VmStk
> 1391425166,236444,210368,15164,15164,81772,88
> 1391425171,236444,212212,16960,16960,83616,88
> 1391425176,236444,213928,18764,18764,85332,88
> 1391425181,236444,215764,20560,20560,87168,88
> 1391425186,236444,217608,22360,22360,89012,88
> 1391425191,236444,219324,24176,24176,90728,88
> 1391425196,236444,221172,25972,25972,92576,88
> 1391425201,236444,223016,27768,27768,94420,88
> 1391425206,236444,224732,29556,29556,96136,88
> Memory does not seem to be leaked if there are messages waiting on the queue 
> or if no duration is provided and messages are present on the queue.



--
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] (QPID-6134) Restarting a node that has detected an intruder should go back into the ERROR state not ACTIVE

2014-10-10 Thread Keith Wall (JIRA)

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

Keith Wall resolved QPID-6134.
--
   Resolution: Fixed
Fix Version/s: 0.31

Change looks reasonable to me.

> Restarting a node that has detected an intruder should go back into the ERROR 
> state not ACTIVE
> --
>
> Key: QPID-6134
> URL: https://issues.apache.org/jira/browse/QPID-6134
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Andrew MacBean
>Assignee: Andrew MacBean
> Fix For: 0.31
>
>
> Issue stems from doActivate method on AVHN calling activate() and then 
> setting state to ACTIVE unless an exception thrown. 
> Intruder detection doesnt throw an exception and so this case needs to be 
> handled to allow transition to ERRORED again.



--
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-6143) [Java Broker] Broker can crash on publishing/consuming messages during master transfer in BDB HA group

2014-10-10 Thread Alex Rudyy (JIRA)
Alex Rudyy created QPID-6143:


 Summary: [Java Broker] Broker can crash on publishing/consuming 
messages during master transfer in BDB HA group 
 Key: QPID-6143
 URL: https://issues.apache.org/jira/browse/QPID-6143
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.30
Reporter: Alex Rudyy


I built 3 node cluster and started a sample java app publishing and consuming 
messages into/from a Master node.

During publishing/consuming I was flipping mastership between 1st and 2d nodes 
from 3d node using the following script
{noformat}
while true; do (curl --user admin:admin -X PUT  -d '{"role":"MASTER"}' 
http://localhost:8082/api/latest/replicationnode/node3/node2; sleep 1; curl -s 
--user admin:admin -X GET  
http://localhost:8081/api/latest/virtualhostnode/node2 | grep "name\|role" ;  
curl --user admin:admin -X PUT  -d '{"role":"MASTER"}' 
http://localhost:8082/api/latest/replicationnode/node3/node1 ; sleep 1; curl -s 
--user admin:admin -X GET  
http://localhost:8080/api/latest/virtualhostnode/node1 | grep "name\|role") done
{noformat}

In some cases, on message delivery when node was in a process of state change 
from MASTER to REPLICA I've seen the following broker crush

{noformat}

#
# Unhandled Exception java.lang.IllegalStateException: Environment is not valid 
in Thread pool-187-thread-21
#
# Exiting
#

java.lang.IllegalStateException: Environment is not valid
at 
org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.openDatabase(ReplicatedEnvironmentFacade.java:460)
at 
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.getMessageContentDb(AbstractBDBMessageStore.java:1057)
at 
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.getAllContent(AbstractBDBMessageStore.java:579)
at 
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.getContent(AbstractBDBMessageStore.java:1319)
at 
org.apache.qpid.server.message.AbstractServerMessageImpl.getContent(AbstractServerMessageImpl.java:171)
at 
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl$MessageContentSourceBody.writePayload(ProtocolOutputConverterImpl.java:251)
at org.apache.qpid.framing.AMQFrame.writeFrames(AMQFrame.java:123)
at 
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl$CompositeAMQBodyBlock.writePayload(ProtocolOutputConverterImpl.java:468)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.asByteBuffer(AMQProtocolEngine.java:595)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.writeFrame(AMQProtocolEngine.java:709)
at 
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeFrame(ProtocolOutputConverterImpl.java:430)
at 
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDeliveryUnchanged(ProtocolOutputConverterImpl.java:207)
at 
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:141)
at 
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeMessageDelivery(ProtocolOutputConverterImpl.java:101)
at 
org.apache.qpid.server.protocol.v0_8.output.ProtocolOutputConverterImpl.writeDeliver(ProtocolOutputConverterImpl.java:78)
at 
org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$WriteDeliverMethod.deliverToClient(AMQProtocolEngine.java:1626)
at 
org.apache.qpid.server.protocol.v0_8.ConsumerTarget_0_8.sendToClient(ConsumerTarget_0_8.java:513)
at 
org.apache.qpid.server.protocol.v0_8.ConsumerTarget_0_8$AckConsumer.send(ConsumerTarget_0_8.java:317)
at 
org.apache.qpid.server.queue.QueueConsumerImpl.send(QueueConsumerImpl.java:475)
at 
org.apache.qpid.server.queue.AbstractQueue.deliverMessage(AbstractQueue.java:1235)
at 
org.apache.qpid.server.queue.AbstractQueue.attemptDelivery(AbstractQueue.java:1989)
at 
org.apache.qpid.server.queue.AbstractQueue.processQueue(AbstractQueue.java:2160)
at org.apache.qpid.server.queue.QueueRunner$1.run(QueueRunner.java:77)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:356)
at org.apache.qpid.server.queue.QueueRunner.run(QueueRunner.java:68)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}



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

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

[jira] [Updated] (QPID-6115) Compile Qpid C++ on Solaris

2014-10-10 Thread Andreas Welchlin (JIRA)

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

Andreas Welchlin updated QPID-6115:
---
Attachment: solaris.patch

The Solaris patch file.

> Compile Qpid C++ on Solaris
> ---
>
> Key: QPID-6115
> URL: https://issues.apache.org/jira/browse/QPID-6115
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker, C++ Client
>Affects Versions: 0.28
> Environment: Solaris X86 with gcc
> uname -a: SunOS solaris 5.11 11.2 i86pc i386 i86pc
>Reporter: Andreas Welchlin
>Assignee: Andrew Stitcher
>  Labels: build
> Attachments: SystemInfo.cpp, solaris.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Qpid does not compile on Solaris. CMakeLists.txt and also 
> qpid/solaris/SystemInfo.cpp need to be enhanced.
> The Solaris linker has no argument like:
> "-Wl,--version-script=..."
> So it needs to be deactivated on Solaris in cpp/src/CMakeLists.txt by 
> changing the following:
> set (LINK_VERSION_SCRIPT_FLAG "-Wl,--version-script=${QPID_LINKMAP}") 
> needs to be replaced by:
>  if (NOT CMAKE_SYSTEM_NAME STREQUAL SunOS)
>   set (LINK_VERSION_SCRIPT_FLAG "-Wl,--version-script=${QPID_LINKMAP}")
>  endif (NOT CMAKE_SYSTEM_NAME STREQUAL SunOS) 
> The enhancements in SystemInfo.cpp are added as file.



--
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-6115) Compile Qpid C++ on Solaris

2014-10-10 Thread Andreas Welchlin (JIRA)

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

Andreas Welchlin commented on QPID-6115:


I created a patch file which has the diff between the official qpid-0.28.tar.gz 
and the Solaris changes (solaris.patch).

Sorry for the late reply!

> Compile Qpid C++ on Solaris
> ---
>
> Key: QPID-6115
> URL: https://issues.apache.org/jira/browse/QPID-6115
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker, C++ Client
>Affects Versions: 0.28
> Environment: Solaris X86 with gcc
> uname -a: SunOS solaris 5.11 11.2 i86pc i386 i86pc
>Reporter: Andreas Welchlin
>Assignee: Andrew Stitcher
>  Labels: build
> Attachments: SystemInfo.cpp
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Qpid does not compile on Solaris. CMakeLists.txt and also 
> qpid/solaris/SystemInfo.cpp need to be enhanced.
> The Solaris linker has no argument like:
> "-Wl,--version-script=..."
> So it needs to be deactivated on Solaris in cpp/src/CMakeLists.txt by 
> changing the following:
> set (LINK_VERSION_SCRIPT_FLAG "-Wl,--version-script=${QPID_LINKMAP}") 
> needs to be replaced by:
>  if (NOT CMAKE_SYSTEM_NAME STREQUAL SunOS)
>   set (LINK_VERSION_SCRIPT_FLAG "-Wl,--version-script=${QPID_LINKMAP}")
>  endif (NOT CMAKE_SYSTEM_NAME STREQUAL SunOS) 
> The enhancements in SystemInfo.cpp are added as file.



--
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-690) FailoverHandler does not have a delay between reconnection attempts.

2014-10-10 Thread ASF subversion and git services (JIRA)

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

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

Commit 1630826 from [~gsim] in branch 'proton/branches/examples'
[ https://svn.apache.org/r1630826 ]

QPID-690: object/list/hash changes affecting Windows components

> FailoverHandler does not have a delay between reconnection attempts.
> 
>
> Key: QPID-690
> URL: https://issues.apache.org/jira/browse/QPID-690
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Client
>Affects Versions: M2, M2.1
>Reporter: Martin Ritchie
>Assignee: Martin Ritchie
> Fix For: M2.1
>
> Attachments: Qpid-690.patch
>
>
> When a Connection Refused exception stops the TCP connection the set number 
> of retries can be quickly used up.
> By having a delay between connection attempts then the duration that 
> reconnection will occur over will be greatly improved.



--
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-6134) Restarting a node that has detected an intruder should go back into the ERROR state not ACTIVE

2014-10-10 Thread ASF subversion and git services (JIRA)

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

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

Commit 1630807 from [~macbean] in branch 'qpid/trunk'
[ https://svn.apache.org/r1630807 ]

QPID-6134: [Java Broker] added operational logging call to additional intruder 
detection logic

> Restarting a node that has detected an intruder should go back into the ERROR 
> state not ACTIVE
> --
>
> Key: QPID-6134
> URL: https://issues.apache.org/jira/browse/QPID-6134
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Andrew MacBean
>Assignee: Andrew MacBean
>
> Issue stems from doActivate method on AVHN calling activate() and then 
> setting state to ACTIVE unless an exception thrown. 
> Intruder detection doesnt throw an exception and so this case needs to be 
> handled to allow transition to ERRORED again.



--
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-658) NoLocal messages should be deleted when the queue is exclusive

2014-10-10 Thread ASF subversion and git services (JIRA)

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

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

Commit 1630802 from [~gsim] in branch 'proton/branches/examples'
[ https://svn.apache.org/r1630802 ]

QPID-658 Windows driver.c with selectors and selectables

> NoLocal messages should be deleted when the queue is exclusive
> --
>
> Key: QPID-658
> URL: https://issues.apache.org/jira/browse/QPID-658
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker, Java Client
>Affects Versions: M3
>Reporter: Arnaud Simon
>Assignee: Gordon Sim
> Fix For: 0.6
>
>
> For JMS we need the broker to delete messages of an exclusive queue that 
> cannot be delivered to the consumer because of Nolocal. This is a simple fix 
> for supporting the JMS notion of noLocal (topic only). 



--
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-6141) [JMS AMQP 1.0 Client] Calling recover on CLIENT_ACKNOWLEDGE asynchronous session will not replay messages

2014-10-10 Thread ASF subversion and git services (JIRA)

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

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

Commit 1630766 from [~godfrer] in branch 'qpid/trunk'
[ https://svn.apache.org/r1630766 ]

QPID-6141 : Fix recover() for onMessage client-ack sessions

> [JMS AMQP 1.0 Client] Calling recover on CLIENT_ACKNOWLEDGE asynchronous 
> session will not replay messages
> -
>
> Key: QPID-6141
> URL: https://issues.apache.org/jira/browse/QPID-6141
> Project: Qpid
>  Issue Type: Bug
>  Components: JMS AMQP 1.0 Client
>Affects Versions: 0.28, 0.30, 0.31
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
>
> Client ack sessions store messages to be replayed at the consumer.  These 
> messages are replayed when using receive() style processing, but not in 
> onMessage processing.



--
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-6142) NPE on startup if key permissions are wrong

2014-10-10 Thread Keith Wall (JIRA)
Keith Wall created QPID-6142:


 Summary: NPE on startup if key permissions are wrong
 Key: QPID-6142
 URL: https://issues.apache.org/jira/browse/QPID-6142
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.31
Reporter: Keith Wall


I was testing the AESKeyFile Encryptor and run into the following problem.  It 
looks like if the Broker cannot be opened then you'll get the NPE..

I had enabled the AESKeyFile, then deliberately chmod'd the .key file to have 
world readable permissions.  The Broker failed on restart with the following 
NPE.

{noformat}
log4j:WARN No appenders could be found for logger 
(org.apache.qpid.server.plugin.QpidServiceLoader).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
[Broker] BRK-1006 : Using configuration : 
/Users/keith/src/qpid/qpid/java/systests/target/qpid-broker/0.32-SNAPSHOT/work/config.json
[Broker] BRK-1007 : Using logging configuration : 
/Users/keith/src/qpid/qpid/java/systests/target/qpid-broker/0.32-SNAPSHOT/etc/log4j.xml
[Broker] BRK-1001 : Startup : Version: 0.32-SNAPSHOT Build: Unversioned 
directory
[Broker] BRK-1010 : Platform : JVM : Oracle Corporation version: 1.7.0_60-b19 
OS : Mac OS X version: 10.9.5 arch: x86_64
[Broker] BRK-1011 : Maximum Memory : 1,908,932,608 bytes
[Broker] BRK-1004 : Qpid Broker Ready
Exception during startup: java.lang.NullPointerException
java.lang.NullPointerException
at 
org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:89)
at org.apache.qpid.server.Broker.startupImpl(Broker.java:154)
at org.apache.qpid.server.Broker.access$000(Broker.java:52)
at org.apache.qpid.server.Broker$1.run(Broker.java:113)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at org.apache.qpid.server.Broker.startup(Broker.java:108)
at org.apache.qpid.server.Main.startBroker(Main.java:470)
at org.apache.qpid.server.Main.execute(Main.java:326)
at org.apache.qpid.server.Main.(Main.java:159)
at org.apache.qpid.server.Main.main(Main.java:150)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
{noformat}

The logs say:

{noformat}
2014-10-08 22:41:37,816 INFO  [main] (broker.startup) - [Broker] BRK-1001 : 
Startup : Version: 0.32-SNAPSHOT Build: Unversioned directory
2014-10-08 22:41:37,817 INFO  [main] (broker.platform) - [Broker] BRK-1010 : 
Platform : JVM : Oracle Corporation version: 1.7.0_60-b19 OS : Mac OS X 
version: 10.9.5 arch: x86_64
2014-10-08 22:41:37,818 INFO  [main] (broker.max_memory) - [Broker] BRK-1011 : 
Maximum Memory : 1,908,932,608 bytes
2014-10-08 22:41:37,871 ERROR [main] (model.AbstractConfiguredObject) - Failed 
to open object with name 'Broker'.  Object will be put into ERROR state.
java.lang.IllegalArgumentException: Key file 
'/Users/keith/src/qpid/qpid/java/systests/target/qpid-broker/0.32-SNAPSHOT/work/.keys/Broker_Broker.key'
 has incorrect permissions.  Only the owner should be able to read or write 
this file.
at 
org.apache.qpid.server.security.encryption.AESKeyFileEncrypterFactory.createEncrypter(AESKeyFileEncrypterFactory.java:99)
at 
org.apache.qpid.server.model.adapter.BrokerAdapter.postResolve(BrokerAdapter.java:141)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.doResolution(AbstractConfiguredObject.java:658)
at 
org.apache.qpid.server.model.AbstractConfiguredObject.open(AbstractConfiguredObject.java:415)
at 
org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:83)
at org.apache.qpid.server.Broker.startupImpl(Broker.java:154)
at org.apache.qpid.server.Broker.access$000(Broker.java:52)
at org.apache.qpid.server.Broker$1.run(Broker.java:113)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at org.apache.qpid.server.Broker.startup(Broker.java:108)
at org.apache.qpid.server.Main.startBroker(Main.java:470)
at org.apache.qpid.server.Main.execute(Main.java:326)
at org.apache.qpid.server.Main.(Main.java:159)
at org.apache.qpid.server.Main.main(Main.java:150)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.refl

[jira] [Updated] (QPID-6141) [JMS AMQP 1.0 Client] Calling recover on CLIENT_ACKNOWLEDGE asynchronous session will not replay messages

2014-10-10 Thread Rob Godfrey (JIRA)

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

Rob Godfrey updated QPID-6141:
--
Affects Version/s: (was: 0.32)
   0,31

> [JMS AMQP 1.0 Client] Calling recover on CLIENT_ACKNOWLEDGE asynchronous 
> session will not replay messages
> -
>
> Key: QPID-6141
> URL: https://issues.apache.org/jira/browse/QPID-6141
> Project: Qpid
>  Issue Type: Bug
>  Components: JMS AMQP 1.0 Client
>Affects Versions: 0.28, 0.30, 0.31
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
>
> Client ack sessions store messages to be replayed at the consumer.  These 
> messages are replayed when using receive() style processing, but not in 
> onMessage processing.



--
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-6141) [JMS AMQP 1.0 Client] Calling recover on CLIENT_ACKNOWLEDGE asynchronous session will not replay messages

2014-10-10 Thread Rob Godfrey (JIRA)

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

Rob Godfrey updated QPID-6141:
--
Affects Version/s: (was: 0,31)
   0.31

> [JMS AMQP 1.0 Client] Calling recover on CLIENT_ACKNOWLEDGE asynchronous 
> session will not replay messages
> -
>
> Key: QPID-6141
> URL: https://issues.apache.org/jira/browse/QPID-6141
> Project: Qpid
>  Issue Type: Bug
>  Components: JMS AMQP 1.0 Client
>Affects Versions: 0.28, 0.30, 0.31
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
>
> Client ack sessions store messages to be replayed at the consumer.  These 
> messages are replayed when using receive() style processing, but not in 
> onMessage processing.



--
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-6141) [JMS AMQP 1.0 Client] Calling recover on CLIENT_ACKNOWLEDGE asynchronous session will not replay messages

2014-10-10 Thread Rob Godfrey (JIRA)
Rob Godfrey created QPID-6141:
-

 Summary: [JMS AMQP 1.0 Client] Calling recover on 
CLIENT_ACKNOWLEDGE asynchronous session will not replay messages
 Key: QPID-6141
 URL: https://issues.apache.org/jira/browse/QPID-6141
 Project: Qpid
  Issue Type: Bug
  Components: JMS AMQP 1.0 Client
Affects Versions: 0.32, 0.28, 0.30
Reporter: Rob Godfrey
Assignee: Rob Godfrey


Client ack sessions store messages to be replayed at the consumer.  These 
messages are replayed when using receive() style processing, but not in 
onMessage processing.



--
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