[
https://issues.apache.org/jira/browse/CAMEL-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-6945.
-
Resolution: Fixed
Applied the patch into master and camel-2.12.x branches.
camel-netty-http
[
https://issues.apache.org/jira/browse/CAMEL-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-5790.
-
Resolution: Fixed
Fix Version/s: 2.13.0
Applied the patch into trunk.
aws-s3 should
Claus Ibsen created CAMEL-6946:
--
Summary: camel-netty - Use ConnectionException instead of
CamelException if cannot connect to remote server
Key: CAMEL-6946
URL: https://issues.apache.org/jira/browse/CAMEL-6946
[
https://issues.apache.org/jira/browse/CAMEL-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-6946.
Resolution: Fixed
Fix Version/s: 2.11.3
camel-netty - Use ConnectionException instead of
[
https://issues.apache.org/jira/browse/CAMEL-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13817231#comment-13817231
]
Claus Ibsen commented on CAMEL-6945:
I think we have a catch-22 situation here.
Yeah
[
https://issues.apache.org/jira/browse/CAMEL-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13817231#comment-13817231
]
Claus Ibsen edited comment on CAMEL-6945 at 11/8/13 12:40 PM:
--
Claus Ibsen created CAMEL-6947:
--
Summary: camel-rabbit - RabbitMQ producer should start|stop more
cleanly
Key: CAMEL-6947
URL: https://issues.apache.org/jira/browse/CAMEL-6947
Project: Camel
[
https://issues.apache.org/jira/browse/CAMEL-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-6947.
Resolution: Fixed
camel-rabbit - RabbitMQ producer should start|stop more cleanly
[
https://issues.apache.org/jira/browse/CAMEL-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-6909.
Resolution: Fixed
Thanks for the patch.
RabbitMQ Support for Exchange Type
[
https://issues.apache.org/jira/browse/CAMEL-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-6941:
---
Fix Version/s: 2.13.0
2.12.2
2.11.3
Assignee: Claus
[
https://issues.apache.org/jira/browse/CAMEL-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-6909:
---
Fix Version/s: 2.13.0
2.12.2
Assignee: Claus Ibsen
Issue Type:
[
https://issues.apache.org/jira/browse/CAMEL-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13817331#comment-13817331
]
Aki Yoshida commented on CAMEL-6940:
hi,
i can look into this.
but could you attach
Babak Vahdat created CAMEL-6948:
---
Summary: Releasing a non-singleton producer by ProducerCache
should not only stop the producer but also shutdown it as well if it is a
ShutdownableService
Key: CAMEL-6948
URL:
[
https://issues.apache.org/jira/browse/CAMEL-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat updated CAMEL-6948:
Fix Version/s: 2.11.3
Releasing a non-singleton producer by ProducerCache should not only stop
[
https://issues.apache.org/jira/browse/CAMEL-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Babak Vahdat resolved CAMEL-6948.
-
Resolution: Fixed
Releasing a non-singleton producer by ProducerCache should not only stop the
15 matches
Mail list logo