[
https://issues.apache.org/jira/browse/AMQ-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233495#comment-14233495
]
Timothy Bish commented on AMQ-5405:
---
Moved trunk onto 0.30 to aid in some other
[
https://issues.apache.org/jira/browse/AMQ-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5474.
-
Resolution: Duplicate
This code has been fixed in later releases.
> Broken ConsumerIdKey compara
[
https://issues.apache.org/jira/browse/AMQ-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5470:
--
Attachment: AMQ-5470.patch
Some intial work that might be the way to resolve this.
> AMQP - dela
[
https://issues.apache.org/jira/browse/AMQ-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231825#comment-14231825
]
Timothy Bish commented on AMQ-5405:
---
Current trunk code sees a test failure with 0.30
Timothy Bish created AMQ-5470:
-
Summary: AMQP - delayed authentication from SASL connect leads to
race on client end.
Key: AMQ-5470
URL: https://issues.apache.org/jira/browse/AMQ-5470
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231656#comment-14231656
]
Timothy Bish commented on AMQ-5379:
---
Can we just encourage them to move onto a later
[
https://issues.apache.org/jira/browse/AMQ-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231504#comment-14231504
]
Timothy Bish commented on AMQ-5379:
---
I'd agree with Robbie's analysis her
[
https://issues.apache.org/jira/browse/AMQ-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5462:
--
Issue Type: Improvement (was: Bug)
> dead code in method createSession of class ActiveMQConnect
[
https://issues.apache.org/jira/browse/AMQ-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5405:
--
Affects Version/s: (was: 5.11.0)
5.10.0
> Update the AMQP JMS client used
[
https://issues.apache.org/jira/browse/AMQ-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5405:
--
Fix Version/s: (was: Unscheduled)
5.11.0
> Update the AMQP JMS client used
[
https://issues.apache.org/jira/browse/AMQCPP-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQCPP-556.
-
Resolution: Fixed
Fix Version/s: 3.9.0
3.8.4
patch tested and applied
[
https://issues.apache.org/jira/browse/AMQ-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5467.
---
Resolution: Fixed
Patched reviewed and applied. Thanks!
> AMQP transaction may fail to commit,
[
https://issues.apache.org/jira/browse/AMQ-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5464.
---
Resolution: Fixed
Patch applied with thanks.
> enable use of 'Configuration' Terminus
[
https://issues.apache.org/jira/browse/AMQ-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229863#comment-14229863
]
Timothy Bish commented on AMQ-5466:
---
Would advise testing against a 5.11-SNAPSHOT if
[
https://issues.apache.org/jira/browse/AMQ-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5466:
--
Priority: Major (was: Critical)
> Lost persistent message sent to detached consumer bef
[
https://issues.apache.org/jira/browse/AMQ-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-4155:
--
Comment: was deleted
(was: This is not a bug. Currently ActiveMQ is spring dependency when you use
the
[
https://issues.apache.org/jira/browse/AMQ-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5439.
---
Resolution: Fixed
Updated docs.
> updateClusterFilter doc sample; not using correct regular express
[
https://issues.apache.org/jira/browse/AMQ-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226221#comment-14226221
]
Timothy Bish commented on AMQ-3370:
---
If it is a feature you really want then coni
[
https://issues.apache.org/jira/browse/AMQ-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226216#comment-14226216
]
Timothy Bish commented on AMQ-5430:
---
Are you using the Java baed LevelDB implementa
[
https://issues.apache.org/jira/browse/AMQ-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5444.
---
Resolution: Fixed
Fix Version/s: 5.11.0
Assignee: Timothy Bish
Fixed so that the
[
https://issues.apache.org/jira/browse/AMQ-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225229#comment-14225229
]
Timothy Bish commented on AMQ-5381:
---
There is no plan for a 5.10.1 release at this
[
https://issues.apache.org/jira/browse/AMQ-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5442.
---
Resolution: Fixed
Fix Version/s: 5.11.0
Assignee: Timothy Bish
Added check before
[
https://issues.apache.org/jira/browse/AMQ-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5436.
---
Resolution: Fixed
Fix Version/s: 5.11.0
Assignee: Timothy Bish
Patch applied. Closes
[
https://issues.apache.org/jira/browse/AMQ-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5435:
--
Description:
I am using jdbc master/slave with lease database lock.
I found if I call broker.stop to
[
https://issues.apache.org/jira/browse/AMQ-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5447.
---
Resolution: Fixed
Fix Version/s: 5.11.0
Patch applied.
> Memory Leak after shutdown embe
[
https://issues.apache.org/jira/browse/AMQ-5456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5456.
---
Resolution: Fixed
Patch applied, thanks!
> AMQP messages accepted transactionally by a consumer sho
[
https://issues.apache.org/jira/browse/AMQ-5456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish reassigned AMQ-5456:
-
Assignee: Timothy Bish
> AMQP messages accepted transactionally by a consumer should retain
[
https://issues.apache.org/jira/browse/ACTIVEMQ6-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish moved AMQ-5451 to ACTIVEMQ6-45:
Component/s: (was: AMQP)
Affects Version/s: (was: 6.0.0
[
https://issues.apache.org/jira/browse/AMQ-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14223506#comment-14223506
]
Timothy Bish commented on AMQ-5453:
---
Can you clarify what version of ActiveMQ you
[
https://issues.apache.org/jira/browse/AMQCPP-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQCPP-555.
---
Resolution: Incomplete
Not enough to go on here.
> AcE427
> --
>
>
[
https://issues.apache.org/jira/browse/AMQNET-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish moved AMQ-5432 to AMQNET-494:
--
Component/s: (was: Broker)
ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5423.
---
Resolution: Fixed
Fixed on trunk
> STOMP protocol converter tracks pending ACKS but doesn't re
Timothy Bish created AMQ-5423:
-
Summary: STOMP protocol converter tracks pending ACKS but doesn't
remove the state once ACK'd
Key: AMQ-5423
URL: https://issues.apache.org/jira/browse/AMQ-5423
[
https://issues.apache.org/jira/browse/AMQ-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5421.
---
Resolution: Fixed
Fixed on trunk
> AbortSlowAckConsumerStratagy can cause errors due to concurr
Timothy Bish created AMQ-5421:
-
Summary: AbortSlowAckConsumerStratagy can cause errors due to
concurrent access to internal state
Key: AMQ-5421
URL: https://issues.apache.org/jira/browse/AMQ-5421
Project
[
https://issues.apache.org/jira/browse/AMQ-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5221.
-
Resolution: Duplicate
Fix Version/s: (was: 5.11.0)
Newer issue which is working to address the
[
https://issues.apache.org/jira/browse/AMQ-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5032.
---
Resolution: Fixed
This has been fixed with the recent update to Proton-J 0.8
> AMQP Message Exp
[
https://issues.apache.org/jira/browse/AMQ-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5278.
---
Resolution: Fixed
This is fixed with the update to the new Proton-J 0.8 version.
> Proton
[
https://issues.apache.org/jira/browse/AMQ-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5410.
-
Resolution: Not a Problem
This is not an issue with the broker, for architecture questions please ask on
[
https://issues.apache.org/jira/browse/AMQ-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194598#comment-14194598
]
Timothy Bish commented on AMQ-5419:
---
Please add a junit test case to demonstrate
[
https://issues.apache.org/jira/browse/AMQ-5324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5324.
-
Resolution: Cannot Reproduce
No test case available to reproduce. Recommend that you try a later relase of
[
https://issues.apache.org/jira/browse/AMQ-5332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5332.
-
Resolution: Won't Fix
There is no plan to add support for older specs at this time. If you can
cre
[
https://issues.apache.org/jira/browse/AMQ-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193143#comment-14193143
]
Timothy Bish commented on AMQ-5382:
---
Root cause is related to the fact that the
[
https://issues.apache.org/jira/browse/AMQ-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193139#comment-14193139
]
Timothy Bish commented on AMQ-5410:
---
>From a quick glance my assumption is that me
[
https://issues.apache.org/jira/browse/AMQ-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5418.
-
Resolution: Duplicate
> MQTT Subscriber is able to receive messages published after unsubscr
[
https://issues.apache.org/jira/browse/AMQ-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5374.
---
Resolution: Fixed
Assignee: Timothy Bish
We are now on 0.8 which has the fixes needed for this
[
https://issues.apache.org/jira/browse/AMQ-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5346.
---
Resolution: Fixed
Updated trunk to use official 0.8 now that it has been released
> Update Proton
[
https://issues.apache.org/jira/browse/AMQ-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5402.
-
Resolution: Won't Fix
Fix Version/s: (was: 5.11.0)
> enable support for using byte v
[
https://issues.apache.org/jira/browse/AMQ-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish reopened AMQ-5402:
---
The JMS -> AMQP mapping appears to be moving in a different direction now, I am
going to remove this
[
https://issues.apache.org/jira/browse/AMQ-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5407.
---
Resolution: Fixed
Fix Version/s: 5.11.0
Assignee: Timothy Bish
Added matching option
[
https://issues.apache.org/jira/browse/AMQ-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5371:
--
Attachment: AMQ5371.patch
This should do what you are looking for. What we need is some tests around
[
https://issues.apache.org/jira/browse/AMQ-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5406.
---
Resolution: Fixed
Fix Version/s: 5.11.0
Assignee: Timothy Bish
Added configuration
[
https://issues.apache.org/jira/browse/AMQ-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5406:
--
Priority: Minor (was: Major)
> Support of jms.consumerExpiryCheck=false to avoid JMS Consumers ignor
[
https://issues.apache.org/jira/browse/AMQ-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5405:
--
Attachment: AMQ5405.patch
Patch that updates the client and gets all the SSL tests passing.
> Update
Timothy Bish created AMQ-5405:
-
Summary: Update the AMQP JMS client used in tests from 0.26 to 0.30
Key: AMQ-5405
URL: https://issues.apache.org/jira/browse/AMQ-5405
Project: ActiveMQ
Issue Type
[
https://issues.apache.org/jira/browse/AMQ-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5397.
-
Resolution: Cannot Reproduce
Attempt to reproduce but could not. If you can provide a unit test that shows
[
https://issues.apache.org/jira/browse/AMQ-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5390.
-
Resolution: Not a Problem
Added new test to the test suite to show that things are working as expected
[
https://issues.apache.org/jira/browse/AMQ-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5381.
---
Resolution: Fixed
Fix Version/s: 5.11.0
Assignee: Timothy Bish
Fixed on trunk
[
https://issues.apache.org/jira/browse/AMQ-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5389.
---
Resolution: Fixed
Fix Version/s: 5.11.0
Assignee: Timothy Bish
Fixed on trunk
[
https://issues.apache.org/jira/browse/AMQ-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5387.
---
Resolution: Fixed
Fix Version/s: (was: NEEDS_REVIEW)
5.11.0
[
https://issues.apache.org/jira/browse/AMQ-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5396.
---
Resolution: Fixed
Fix Version/s: 5.11.0
Assignee: Timothy Bish
Reviewed the patch a bit
[
https://issues.apache.org/jira/browse/AMQ-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5365.
---
Resolution: Fixed
Fix Version/s: 5.11.0
patch applied with some modification to catch all cases
[
https://issues.apache.org/jira/browse/AMQ-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5402.
---
Resolution: Fixed
Patch applied, thanks!
> enable support for using byte values in destination t
[
https://issues.apache.org/jira/browse/AMQ-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5403.
---
Resolution: Fixed
Patch applied, thanks!
> remove extra expiration and timestamp manipulaton wh
[
https://issues.apache.org/jira/browse/AMQ-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish reassigned AMQ-5402:
-
Assignee: Timothy Bish
> enable support for using byte values in destination type annotati
[
https://issues.apache.org/jira/browse/AMQ-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish reassigned AMQ-5403:
-
Assignee: Timothy Bish
> remove extra expiration and timestamp manipulaton which will ca
[
https://issues.apache.org/jira/browse/AMQ-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5401.
---
Resolution: Fixed
fixed on trunk
> AMQP transport handling of durable consumer unsubscribe
Timothy Bish created AMQ-5401:
-
Summary: AMQP transport handling of durable consumer unsubscribe
if incorrect
Key: AMQ-5401
URL: https://issues.apache.org/jira/browse/AMQ-5401
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5398.
-
Resolution: Invalid
Questions should be posted to the users list.
> How do I configure a automa
[
https://issues.apache.org/jira/browse/AMQ-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173793#comment-14173793
]
Timothy Bish commented on AMQ-4940:
---
I don't think anyone would object
[
https://issues.apache.org/jira/browse/AMQ-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173791#comment-14173791
]
Timothy Bish commented on AMQ-5397:
---
You might want to try out the 5.11-SNAPSHOT bu
[
https://issues.apache.org/jira/browse/AMQ-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5391.
---
Resolution: Fixed
Fix temp queue creation, avoid an NPE
> Support for anonymous style producers
[
https://issues.apache.org/jira/browse/AMQ-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish reopened AMQ-5391:
---
Small issue introduced that affect temporary destinations
> Support for anonymous style producers in A
[
https://issues.apache.org/jira/browse/AMQ-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5391.
---
Resolution: Fixed
Feature added on trunk.
> Support for anonymous style producers in A
[
https://issues.apache.org/jira/browse/AMQ-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171567#comment-14171567
]
Timothy Bish commented on AMQ-5391:
---
Implemented this feature on trunk, default name
[
https://issues.apache.org/jira/browse/AMQ-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171232#comment-14171232
]
Timothy Bish commented on AMQ-4585:
---
You'll need to try and raise the priorit
[
https://issues.apache.org/jira/browse/AMQ-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5395.
---
Resolution: Fixed
Fixed on trunk
> AmqpJMSVendor clips destination names if no prefix
Timothy Bish created AMQ-5395:
-
Summary: AmqpJMSVendor clips destination names if no prefix set
Key: AMQ-5395
URL: https://issues.apache.org/jira/browse/AMQ-5395
Project: ActiveMQ
Issue Type
[
https://issues.apache.org/jira/browse/AMQ-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170740#comment-14170740
]
Timothy Bish commented on AMQ-4585:
---
There are fixes to both the client and the
[
https://issues.apache.org/jira/browse/AMQ-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5392.
-
Resolution: Invalid
This is a question better suited for the users mailing list.
> Active MQ to
Timothy Bish created AMQ-5391:
-
Summary: Support for anonymous style producers in AMQP
Key: AMQ-5391
URL: https://issues.apache.org/jira/browse/AMQ-5391
Project: ActiveMQ
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/AMQ-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167653#comment-14167653
]
Timothy Bish commented on AMQ-5387:
---
It's simpler if you just attach the test
On 10/10/2014 11:08 AM, Clebert Suconic wrote:
I feel like someone at the first day on a new job here :) (Where's the
coffee place?.. where's the bathroom? :) )
Is there anyone from infra who can help us setup that? I will need some
help from any veterans here on finding the right person or ma
+1 for a separate repository.
On 10/10/2014 10:16 AM, Hadrian Zbarcea wrote:
Do we want a separate repository (my preference) or a branch in the
current one?
For the former case, I think infra@ needs to create the repo, then we
could import it.
Can we reach a lazy consensus, do we need/want a
[
https://issues.apache.org/jira/browse/AMQ-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5385.
---
Resolution: Fixed
Fix applied and test case added on trunk
> MQTT Link Stealing fails when cli
[
https://issues.apache.org/jira/browse/AMQ-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5385:
--
Fix Version/s: 5.11.0
> MQTT Link Stealing fails when client reconnects more than o
[
https://issues.apache.org/jira/browse/AMQ-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish reassigned AMQ-5385:
-
Assignee: Timothy Bish
> MQTT Link Stealing fails when client reconnects more than o
[
https://issues.apache.org/jira/browse/AMQ-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157998#comment-14157998
]
Timothy Bish commented on AMQ-5381:
---
Recommend you create a JUnit test case to repro
On 09/29/2014 02:21 PM, cfaini wrote:
Hey there. I have been starting to work with ActiveMQ-cpp. Originally it
worked perfectly for me in my tests. However, I recently had to change my
environment and compiler from Solaris 10 w/ gcc-4.3.2 to Solaris 11 w/
gcc-4.5.2. I was able to get the ActiveMQ
[
https://issues.apache.org/jira/browse/AMQNET-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQNET-490:
Issue Type: New Feature (was: Bug)
> Stomp Client 1.5.4 error creating subscription to topic
[
https://issues.apache.org/jira/browse/AMQNET-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154815#comment-14154815
]
Timothy Bish commented on AMQNET-490:
-
You're welcome to work on creatin
[
https://issues.apache.org/jira/browse/AMQ-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153339#comment-14153339
]
Timothy Bish commented on AMQ-5346:
---
Applied patch, thanks!
> Update Proton to
[
https://issues.apache.org/jira/browse/AMQ-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5373.
---
Resolution: Fixed
Fix Version/s: 5.11.0
Test updated to not use a fixed port
[
https://issues.apache.org/jira/browse/AMQNET-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152011#comment-14152011
]
Timothy Bish commented on AMQNET-490:
-
Questions like that should go to the Ap
[
https://issues.apache.org/jira/browse/AMQNET-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151840#comment-14151840
]
Timothy Bish commented on AMQNET-490:
-
HornetQ uses different destination names
[
https://issues.apache.org/jira/browse/AMQNET-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQNET-490.
---
Resolution: Not a Problem
> Stomp Client 1.5.4 error creating subscription to topic on JBoss Horn
On 09/27/2014 10:53 PM, xinsheng wrote:
Hi Tabish,
Do you really want leave me alone...
--
View this message in context:
http://activemq.2283324.n4.nabble.com/did-the-isDuplicate-memory-leak-tp4685768p4685944.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
If you think
On 09/26/2014 04:08 PM, vromero wrote:
Found this dummy page,
https://cwiki.apache.org/confluence/display/ACTIVEMQ/TEST . It has been
there since 2007 but it adds no value.
Looks like I have only editions permisions. Could someone with the right
permissions please remove it?
Thanks
--
View t
[
https://issues.apache.org/jira/browse/AMQ-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-5369.
-
Resolution: Invalid
This is not a bug report, just a stack trace. Also the versions number has no
+1
On 09/24/2014 11:44 AM, Gary Tully wrote:
we need to formally vote to:
1) accept the code grant from RedHat for hornetq[1]
2) invite the active core committers (Clebert Suconic, Andy Taylor, Justin
Bertram, Youg Hao Gao, Martyn Taylor) from hornetq to become activemq
committers.
For backg
701 - 800 of 6926 matches
Mail list logo
