[jira] [Updated] (AMQ-4123) Improve MQTT Inactivity Monitoring

[ https://issues.apache.org/jira/browse/AMQ-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-4123: -- Component/s: Transport Affects Version/s: 5.7.0 Fix Version/s: 5.8.0 > Improve MQTT

[jira] [Updated] (AMQ-4123) Improve MQTT Inactivity Monitoring

[ https://issues.apache.org/jira/browse/AMQ-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Posta updated AMQ-4123: - Component/s: (was: Message Store) > Improve MQTT Inactivity Monitoring > --

[jira] [Created] (AMQ-4123) Improve MQTT Inactivity Monitoring

Christian Posta created AMQ-4123: Summary: Improve MQTT Inactivity Monitoring Key: AMQ-4123 URL: https://issues.apache.org/jira/browse/AMQ-4123 Project: ActiveMQ Issue Type: Bug Com

[jira] [Commented] (AMQ-4106) STOMP+NIO and Heartbeats gives consistent InactivityIOException

[ https://issues.apache.org/jira/browse/AMQ-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481830#comment-13481830 ] Timothy Bish commented on AMQ-4106: --- Was able to reproduce some issue in a JUnit, will tak

[jira] [Assigned] (AMQ-4106) STOMP+NIO and Heartbeats gives consistent InactivityIOException

[ https://issues.apache.org/jira/browse/AMQ-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned AMQ-4106: - Assignee: Timothy Bish > STOMP+NIO and Heartbeats gives consistent InactivityIOException >

[jira] [Updated] (AMQ-4106) STOMP+NIO and Heartbeats gives consistent InactivityIOException

[ https://issues.apache.org/jira/browse/AMQ-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-4106: -- Fix Version/s: 5.8.0 > STOMP+NIO and Heartbeats gives consistent InactivityIOException >

Re: [DISCUSS] - AcitveMQ 5.7.1 release

+1 We might also consider rolling any patches for the lease db locker. When I had tested the original patch against oracle, it was working okay but folks are now reporting that the functionality is broken in 5.7 On Oct 22, 2012, at 6:01, Claus Ibsen wrote: > Hi > > Yes I know we recently did

[jira] [Created] (AMQ-4122) Lease Database Locker failover broken

st.h created AMQ-4122: - Summary: Lease Database Locker failover broken Key: AMQ-4122 URL: https://issues.apache.org/jira/browse/AMQ-4122 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.7.0

Jenkins build is still unstable: ActiveMQ-Java7 #42

See

Jenkins build is still unstable: ActiveMQ-Java7 » ActiveMQ :: Core #42

See

Jenkins build is still unstable: ActiveMQ-Java7 » ActiveMQ :: LevelDB #42

See

Jenkins build is still unstable: ActiveMQ-Java7 » ActiveMQ :: Assembly #42

See

Re: [DISCUSS] - AcitveMQ 5.7.1 release

+1 On Mon, 2012-10-22 at 15:01 +0200, Claus Ibsen wrote: > Hi > > Yes I know we recently did a 5.7.0 release. However since we got some > bug fixes, and also there were some files missing in the binary kits > that has since been fixed. > > As one of the goals for 5.8.0 is to reduce the activemq

[jira] [Updated] (AMQ-3485) Transacted Session returns invalid MessageConsumer after the first MessageConsumer for the same destiantion. Bug introduced in 5.5.0 - working ok in 4.1.2

[ https://issues.apache.org/jira/browse/AMQ-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pablo La Greca updated AMQ-3485: Comment: was deleted (was: Dejan thanks!. Somebody with common sense finally.) > Transacted Sess

[jira] [Commented] (AMQ-3485) Transacted Session returns invalid MessageConsumer after the first MessageConsumer for the same destiantion. Bug introduced in 5.5.0 - working ok in 4.1.2

[ https://issues.apache.org/jira/browse/AMQ-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481353#comment-13481353 ] Pablo La Greca commented on AMQ-3485: - Dejan thanks!. Somebody with common sense finally

Re: [DISCUSS] - AcitveMQ 5.7.1 release

+1 ... we should branch off the tag and back port those improvements. On Mon, Oct 22, 2012 at 9:01 AM, Claus Ibsen wrote: > Hi > > Yes I know we recently did a 5.7.0 release. However since we got some > bug fixes, and also there were some files missing in the binary kits > that has since been fi

[DISCUSS] - AcitveMQ 5.7.1 release

Hi Yes I know we recently did a 5.7.0 release. However since we got some bug fixes, and also there were some files missing in the binary kits that has since been fixed. As one of the goals for 5.8.0 is to reduce the activemq-core and move stuff to separate transports / stores / spring-xbean etc.

[jira] [Resolved] (AMQ-3996) NIO + SSL: Client certificates are null

[ https://issues.apache.org/jira/browse/AMQ-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-3996. --- Resolution: Fixed This is now fixed on trunk. > NIO + SSL: Client certificates are nu

Re: [DISCUSS] - ActiveMQ out of the box - Should not include the demos

+1 I would even go a step further and say we should generate a securer (unique) ssl key store for each broker instance and enable ssl by default. That would require running a command to complete setup or to create a new broker instance similar to how Apollo creates new broker instances. On Mon

[DISCUSS] - ActiveMQ out of the box - Should not include the demos

Hi 1) If you run ActiveMQ out of the box, eg by bin/activemq from the binary distribution. Then it startup with the demo applications. I would suggest to let the out of the box startup be just the broker + web console. If people would like to run the demo applications, then they can run the broke

[jira] [Reopened] (AMQ-3485) Transacted Session returns invalid MessageConsumer after the first MessageConsumer for the same destiantion. Bug introduced in 5.5.0 - working ok in 4.1.2

[ https://issues.apache.org/jira/browse/AMQ-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac reopened AMQ-3485: Assignee: Dejan Bosanac It looks like a bug. The expectation that you can close and open new consum

[jira] [Comment Edited] (AMQ-1063) Journaled JDBC checkpoint fails with java.io.IOException: Already started.

[ https://issues.apache.org/jira/browse/AMQ-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481287#comment-13481287 ] Petr Nídl edited comment on AMQ-1063 at 10/22/12 10:18 AM: --- I've a

[jira] [Comment Edited] (AMQ-1063) Journaled JDBC checkpoint fails with java.io.IOException: Already started.

[ https://issues.apache.org/jira/browse/AMQ-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481287#comment-13481287 ] Petr Nídl edited comment on AMQ-1063 at 10/22/12 10:17 AM: --- I've a

[jira] [Commented] (AMQ-1063) Journaled JDBC checkpoint fails with java.io.IOException: Already started.

[ https://issues.apache.org/jira/browse/AMQ-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481287#comment-13481287 ] Petr Nídl commented on AMQ-1063: I've analyzed the problem for 5.6.0 release. It happens whe