[
https://issues.apache.org/jira/browse/AMQ-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish reassigned AMQ-3635:
-
Assignee: Timothy Bish
> JmsTopicConnector checks for presence of localClientId then uses
> ou
[
https://issues.apache.org/jira/browse/AMQ-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish reassigned AMQ-2455:
-
Assignee: Timothy Bish (was: Rob Davies)
> Need a facility to retry jms connections to a forei
[
https://issues.apache.org/jira/browse/AMQ-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish reassigned AMQ-3606:
-
Assignee: Dejan Bosanac
Dejan, can you take a look at the supplied patch and see if its in order?
[
https://issues.apache.org/jira/browse/AMQ-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish reassigned AMQ-3137:
-
Assignee: Timothy Bish
> Outbound bridges should handle remote connectivity problems at startup
[
https://issues.apache.org/jira/browse/AMQ-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193140#comment-13193140
]
Marc Schöchlin commented on AMQ-2453:
-
The script is included in the distribution.
Why
[
https://issues.apache.org/jira/browse/AMQ-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
metatech updated AMQ-3681:
--
Attachment: amq_stopping_slave.patch
> DatabaseLocker should first cancel locking SQL statement before closin
DatabaseLocker should first cancel locking SQL statement before closing the SQL
connection
--
Key: AMQ-3681
URL: https://issues.apache.org/jira/browse/AMQ-3681
Pr
[
https://issues.apache.org/jira/browse/AMQ-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
metatech updated AMQ-3681:
--
Description:
ActiveMQ is configured in a Master/Slave configuration with an Oracle database :
http://activemq.apa
+1
On Wed, Jan 25, 2012 at 5:45 AM, Hiram Chirino wrote:
> Hi Everyone,
>
> I think Apollo has reached that point where it's ready to go out into the
> world as a 1.0 release. I've
> been pounding it the last few weeks and finally the last of the bugs that I
> know about have been shaken out.
>
+1
On Tue, 2012-01-24 at 23:45 -0500, Hiram Chirino wrote:
> Hi Everyone,
>
> I think Apollo has reached that point where it's ready to go out into the
> world as a 1.0 release. I've
> been pounding it the last few weeks and finally the last of the bugs that I
> know about have been shaken out.
+1
It looks great. Congrats on getting it to this milestone.
On 25 January 2012 04:45, Hiram Chirino wrote:
> Hi Everyone,
>
> I think Apollo has reached that point where it's ready to go out into the
> world as a 1.0 release. I've
> been pounding it the last few weeks and finally the last of t
+1
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Wed, Jan 25, 2012 at 5:45 AM, Hiram Chirino wrote:
> Hi
[
https://issues.apache.org/jira/browse/AMQ-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-3679.
Resolution: Fixed
Thanks for spotting this, it fixed now with svn revision 1235685
We'll need to mak
[
https://issues.apache.org/jira/browse/AMQ-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac reassigned AMQ-3679:
--
Assignee: Dejan Bosanac
> Bad osgi metadata for activeio-core introduced with fix for AMQ-346
14 matches
Mail list logo