[jira] [Reopened] (CAMEL-17524) Camel loading of resources using ClassResolver API doesn't work in OSGi enviroments
[ https://issues.apache.org/jira/browse/CAMEL-17524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Yeats reopened CAMEL-17524: Estimated Complexity: Moderate (was: Unknown) The fix that was originally applied did not fully resolve the issue. > Camel loading of resources using ClassResolver API doesn't work in OSGi > enviroments > --- > > Key: CAMEL-17524 > URL: https://issues.apache.org/jira/browse/CAMEL-17524 > Project: Camel > Issue Type: Bug > Components: osgi >Affects Versions: 3.14.0 >Reporter: Ryan Yeats >Priority: Minor > Fix For: 3.14.1, 3.15.0 > > > https://issues.apache.org/jira/browse/CAMEL-17116 changed how resources were > loaded in several components the problem being that now they don't use the > classloader of the class making the resource calls in OSGi environments. Its > a simple change to call the method loadResourceAsStream(String name, > ClassLoader loader) and passing in the calling classes class loader instead > of loadResourceAsStream(String name). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17524) Camel loading of resources using ClassResolver API doesn't work in OSGi enviroments
[ https://issues.apache.org/jira/browse/CAMEL-17524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480280#comment-17480280 ] Ryan Yeats commented on CAMEL-17524: Sorry, I would have put up a PR right when i wrote the ticket but it took me a while to get my development environment working for camel and everything good to build. I checked your fix and it looks like you missed ClassPathURIResolver.java resource loading call so I went ahead and pushed an additional PR up with that fix and a couple other places that may have the same issue. > Camel loading of resources using ClassResolver API doesn't work in OSGi > enviroments > --- > > Key: CAMEL-17524 > URL: https://issues.apache.org/jira/browse/CAMEL-17524 > Project: Camel > Issue Type: Bug > Components: osgi >Affects Versions: 3.14.0 >Reporter: Ryan Yeats >Priority: Minor > Fix For: 3.14.1, 3.15.0 > > > https://issues.apache.org/jira/browse/CAMEL-17116 changed how resources were > loaded in several components the problem being that now they don't use the > classloader of the class making the resource calls in OSGi environments. Its > a simple change to call the method loadResourceAsStream(String name, > ClassLoader loader) and passing in the calling classes class loader instead > of loadResourceAsStream(String name). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17524) Camel loading of resources using ClassResolver API doesn't work in OSGi enviroments
[ https://issues.apache.org/jira/browse/CAMEL-17524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Yeats updated CAMEL-17524: --- Affects Version/s: 3.14.0 Description: https://issues.apache.org/jira/browse/CAMEL-17116 changed how resources were loaded in several components the problem being that now they don't use the classloader of the class making the resource calls in OSGi environments. Its a simple change to call the method loadResourceAsStream(String name, ClassLoader loader) and passing in the calling classes class loader instead of loadResourceAsStream(String name). Summary: Camel loading of resources using ClassResolver API doesn't work in OSGi enviroments (was: Camel schematron) > Camel loading of resources using ClassResolver API doesn't work in OSGi > enviroments > --- > > Key: CAMEL-17524 > URL: https://issues.apache.org/jira/browse/CAMEL-17524 > Project: Camel > Issue Type: Bug >Affects Versions: 3.14.0 >Reporter: Ryan Yeats >Priority: Major > > https://issues.apache.org/jira/browse/CAMEL-17116 changed how resources were > loaded in several components the problem being that now they don't use the > classloader of the class making the resource calls in OSGi environments. Its > a simple change to call the method loadResourceAsStream(String name, > ClassLoader loader) and passing in the calling classes class loader instead > of loadResourceAsStream(String name). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17524) Camel schematron
Ryan Yeats created CAMEL-17524: -- Summary: Camel schematron Key: CAMEL-17524 URL: https://issues.apache.org/jira/browse/CAMEL-17524 Project: Camel Issue Type: Bug Reporter: Ryan Yeats -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-14033) multiple consumers for namedReplyTo results in a cryptic nullPointer
Ryan Yeats created CAMEL-14033: -- Summary: multiple consumers for namedReplyTo results in a cryptic nullPointer Key: CAMEL-14033 URL: https://issues.apache.org/jira/browse/CAMEL-14033 Project: Camel Issue Type: Bug Components: camel-sjms Affects Versions: 3.0.0.RC1 Reporter: Ryan Yeats Per [https://camel.apache.org/components/latest/sjms-component.html#_clustering] you should not have multiple inOut producerEndpoints using the same replyTo address but if you do it results in a cryptic null pointer exception it would be nice to have a better error message of some sort directing you to use a unique replyTo address or temporary queue. Additionally if the replyTo is a topic then I don't believe it should result in an error and it may be better to actually use a message selector for this case. java.lang.NullPointerException: nulljava.lang.NullPointerException: null at org.apache.camel.component.sjms.producer.InOutProducer$MessageConsumerResourcesFactory$1.onMessage(InOutProducer.java:103) ~[?:?] at org.apache.activemq.artemis.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:110) ~[254:org.apache.activemq.artemis-server-osgi:2.8.1] at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1031) ~[?:?] at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:50) ~[?:?] at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1154) ~[?:?] at org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42) ~[?:?] at org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31) ~[?:?] at org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66) ~[?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-10918) JMS 2.0 shared subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-10918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899909#comment-15899909 ] Ryan Yeats edited comment on CAMEL-10918 at 3/7/17 6:40 PM: Sounds good to me, I took a crack at it for sjms and tried to make it so that it would not be too much of a burden to maintain both. https://github.com/ryeats/camel/commit/7b5978fbf053abf14c3d4fc21507c027977caf32.patch I can put a PR up also if you like was (Author: ryeats): Sounds good to me, I took a crack at it and tried to make it so that it would not be too much of a burden to maintain the both. https://github.com/ryeats/camel/commit/7b5978fbf053abf14c3d4fc21507c027977caf32.patch > JMS 2.0 shared subscriptions > > > Key: CAMEL-10918 > URL: https://issues.apache.org/jira/browse/CAMEL-10918 > Project: Camel > Issue Type: New Feature > Components: camel-sjms >Reporter: Ryan Yeats > > This is presumptions of me and I apologize for that and will understand if > this is closed outright but I was going to fork camel-sjms and add support > for some JMS 2.0 for my own uses and during testing found out that it was > still backwards compatible and figured I would contribute it back if you guys > found it worth maintaining. > Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a > NoSuchMethodException as expected but everything else seemed to work. Also > tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. > Here is the changeset: > https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6.patch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10918) JMS 2.0 shared subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-10918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899909#comment-15899909 ] Ryan Yeats commented on CAMEL-10918: Sounds good to me, I took a crack at it and tried to make it so that it would not be too much of a burden to maintain the both. https://github.com/ryeats/camel/commit/7b5978fbf053abf14c3d4fc21507c027977caf32.patch > JMS 2.0 shared subscriptions > > > Key: CAMEL-10918 > URL: https://issues.apache.org/jira/browse/CAMEL-10918 > Project: Camel > Issue Type: New Feature > Components: camel-sjms >Reporter: Ryan Yeats > > This is presumptions of me and I apologize for that and will understand if > this is closed outright but I was going to fork camel-sjms and add support > for some JMS 2.0 for my own uses and during testing found out that it was > still backwards compatible and figured I would contribute it back if you guys > found it worth maintaining. > Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a > NoSuchMethodException as expected but everything else seemed to work. Also > tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. > Here is the changeset: > https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6.patch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10912) camel-sjms - Session object created from connection that gets closed
[
https://issues.apache.org/jira/browse/CAMEL-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899589#comment-15899589
]
Ryan Yeats commented on CAMEL-10912:
Thanks! we are using artemis as our broker, ill make some time to try the new
changes out.
> camel-sjms - Session object created from connection that gets closed
>
>
> Key: CAMEL-10912
> URL: https://issues.apache.org/jira/browse/CAMEL-10912
> Project: Camel
> Issue Type: Bug
> Components: camel-sjms
>Affects Versions: 2.18.2
>Reporter: Ryan Yeats
>Assignee: Claus Ibsen
> Fix For: 2.19.0
>
>
> This is not easy to reproduce I haven't been able to simplify it down from
> our code to recreate it but I can reliably cause it to happen. Basically if
> you hit a camel-sjms route with a spike of load from nothing and have a bunch
> of .toD("dynamic-${route}") it can create more connections than the pool
> allows then when a connection is returned it is closed and one of the routes
> will be using a session with a closed connection and will not work until it
> is restarted.
> The code in question:
> https://github.com/apache/camel/blob/camel-2.18.x/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/producer/InOnlyProducer.java#L51-L67
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-10918) JMS 2.0 shared subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-10918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894616#comment-15894616 ] Ryan Yeats edited comment on CAMEL-10918 at 3/3/17 4:12 PM: To be honest that is what I thought was going to happen which wouldn't have been a big deal for me since I am using artemis. Nevertheless I tested it with activemq and karaf and surprisingly it worked other than the no such method exception when I tried to do something only supported by JMS 2.0. The only troubling thing for me is its not clear to me exactly why that was possible either I thought I would get some sort of class miss-match exception. I'm tried it with both both oracle jdk and open jdk to make sure it wasn't something jdk specific also java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) openjdk version "1.8.0_121" OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-1~bpo8+1-b13) OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode) was (Author: ryeats): To be honest that is what I thought was going to happen which wouldn't have been a big deal for me since I am using artemis. Never the less I tested it with activemq and karaf and surprisingly it worked other than the no such method exception when I tried to do something only supported by JMS 2.0. The only troubling thing for me is its not clear to me exactly why that was possible either I thought I would get some sort of class miss-match exception. I'm tried it with both both oracle jdk and open jdk to make sure it wasn't something jdk specific also java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) openjdk version "1.8.0_121" OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-1~bpo8+1-b13) OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode) > JMS 2.0 shared subscriptions > > > Key: CAMEL-10918 > URL: https://issues.apache.org/jira/browse/CAMEL-10918 > Project: Camel > Issue Type: New Feature > Components: camel-sjms >Reporter: Ryan Yeats >Priority: Minor > > This is presumptions of me and I apologize for that and will understand if > this is closed outright but I was going to fork camel-sjms and add support > for some JMS 2.0 for my own uses and during testing found out that it was > still backwards compatible and figured I would contribute it back if you guys > found it worth maintaining. > Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a > NoSuchMethodException as expected but everything else seemed to work. Also > tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. > Here is the changeset: > https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6.patch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-10918) JMS 2.0 shared subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-10918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894616#comment-15894616 ] Ryan Yeats edited comment on CAMEL-10918 at 3/3/17 4:02 PM: To be honest that is what I thought was going to happen which wouldn't have been a big deal for me since I am using artemis. Never the less I tested it with activemq and karaf and surprisingly it worked other than the no such method exception when I tried to do something only supported by JMS 2.0. The only troubling thing for me is its not clear to me exactly why that was possible either I thought I would get some sort of class miss-match exception. I'm tried it with both both oracle jdk and open jdk to make sure it wasn't something jdk specific also java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) openjdk version "1.8.0_121" OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-1~bpo8+1-b13) OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode) was (Author: ryeats): To be honest that is what I thought was going to happen which wouldn't have been a big deal for me since I am using artemis but never the less I tested it with activemq and karaf and surprisingly it worked fine other than the no such method exception when I tried to do something only supported by JMS 2.0. The only troubling thing for me is its not clear to me exactly why that was possible either I thought I would get some sort of class miss-match exception. I'm tried it with both both oracle jdk and open jdk to make sure it wasn't something jdk specific also java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) openjdk version "1.8.0_121" OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-1~bpo8+1-b13) OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode) > JMS 2.0 shared subscriptions > > > Key: CAMEL-10918 > URL: https://issues.apache.org/jira/browse/CAMEL-10918 > Project: Camel > Issue Type: New Feature > Components: camel-sjms >Reporter: Ryan Yeats >Priority: Minor > > This is presumptions of me and I apologize for that and will understand if > this is closed outright but I was going to fork camel-sjms and add support > for some JMS 2.0 for my own uses and during testing found out that it was > still backwards compatible and figured I would contribute it back if you guys > found it worth maintaining. > Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a > NoSuchMethodException as expected but everything else seemed to work. Also > tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. > Here is the changeset: > https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6.patch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-10918) JMS 2.0 shared subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-10918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894616#comment-15894616 ] Ryan Yeats edited comment on CAMEL-10918 at 3/3/17 4:00 PM: To be honest that is what I thought was going to happen which wouldn't have been a big deal for me since I am using artemis but never the less I tested it with activemq and karaf and surprisingly it worked fine other than the no such method exception when I tried to do something only supported by JMS 2.0. The only troubling thing for me is its not clear to me exactly why that was possible either I thought I would get some sort of class miss-match exception. I'm tried it with both both oracle jdk and open jdk to make sure it wasn't jdk specific also java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) openjdk version "1.8.0_121" OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-1~bpo8+1-b13) OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode) was (Author: ryeats): To be honest that is what I thought was going to happen which wouldn't have been a big deal for me since I am using artemis but never the less I tested it with activemq and karaf and surprisingly it worked fine other than the no such method exception when I tried to do something only supported by JMS 2.0. The only troubling thing for me is its not clear to me exactly why that was possible either I thought I would get some sort of class miss-match exception. I'm tried it with both java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) and openjdk version "1.8.0_121" OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-1~bpo8+1-b13) OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode) > JMS 2.0 shared subscriptions > > > Key: CAMEL-10918 > URL: https://issues.apache.org/jira/browse/CAMEL-10918 > Project: Camel > Issue Type: New Feature > Components: camel-sjms >Reporter: Ryan Yeats >Priority: Minor > > This is presumptions of me and I apologize for that and will understand if > this is closed outright but I was going to fork camel-sjms and add support > for some JMS 2.0 for my own uses and during testing found out that it was > still backwards compatible and figured I would contribute it back if you guys > found it worth maintaining. > Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a > NoSuchMethodException as expected but everything else seemed to work. Also > tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. > Here is the changeset: > https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6.patch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-10918) JMS 2.0 shared subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-10918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894616#comment-15894616 ] Ryan Yeats edited comment on CAMEL-10918 at 3/3/17 4:00 PM: To be honest that is what I thought was going to happen which wouldn't have been a big deal for me since I am using artemis but never the less I tested it with activemq and karaf and surprisingly it worked fine other than the no such method exception when I tried to do something only supported by JMS 2.0. The only troubling thing for me is its not clear to me exactly why that was possible either I thought I would get some sort of class miss-match exception. I'm tried it with both both oracle jdk and open jdk to make sure it wasn't something jdk specific also java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) openjdk version "1.8.0_121" OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-1~bpo8+1-b13) OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode) was (Author: ryeats): To be honest that is what I thought was going to happen which wouldn't have been a big deal for me since I am using artemis but never the less I tested it with activemq and karaf and surprisingly it worked fine other than the no such method exception when I tried to do something only supported by JMS 2.0. The only troubling thing for me is its not clear to me exactly why that was possible either I thought I would get some sort of class miss-match exception. I'm tried it with both both oracle jdk and open jdk to make sure it wasn't jdk specific also java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) openjdk version "1.8.0_121" OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-1~bpo8+1-b13) OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode) > JMS 2.0 shared subscriptions > > > Key: CAMEL-10918 > URL: https://issues.apache.org/jira/browse/CAMEL-10918 > Project: Camel > Issue Type: New Feature > Components: camel-sjms >Reporter: Ryan Yeats >Priority: Minor > > This is presumptions of me and I apologize for that and will understand if > this is closed outright but I was going to fork camel-sjms and add support > for some JMS 2.0 for my own uses and during testing found out that it was > still backwards compatible and figured I would contribute it back if you guys > found it worth maintaining. > Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a > NoSuchMethodException as expected but everything else seemed to work. Also > tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. > Here is the changeset: > https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6.patch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10918) JMS 2.0 shared subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-10918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894616#comment-15894616 ] Ryan Yeats commented on CAMEL-10918: To be honest that is what I thought was going to happen which wouldn't have been a big deal for me since I am using artemis but never the less I tested it with activemq and karaf and surprisingly it worked fine other than the no such method exception when I tried to do something only supported by JMS 2.0. The only troubling thing for me is its not clear to me exactly why that was possible either I thought I would get some sort of class miss-match exception. I'm tried it with both java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) and openjdk version "1.8.0_121" OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-1~bpo8+1-b13) OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode) > JMS 2.0 shared subscriptions > > > Key: CAMEL-10918 > URL: https://issues.apache.org/jira/browse/CAMEL-10918 > Project: Camel > Issue Type: New Feature > Components: camel-sjms >Reporter: Ryan Yeats >Priority: Minor > > This is presumptions of me and I apologize for that and will understand if > this is closed outright but I was going to fork camel-sjms and add support > for some JMS 2.0 for my own uses and during testing found out that it was > still backwards compatible and figured I would contribute it back if you guys > found it worth maintaining. > Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a > NoSuchMethodException as expected but everything else seemed to work. Also > tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. > Here is the changeset: > https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6.patch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-10918) JMS 2.0 shared subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-10918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Yeats updated CAMEL-10918: --- Description: This is presumptions of me and I apologize for that and will understand if this is closed outright but I was going to fork camel-sjms and add support for some JMS 2.0 for my own uses and during testing found out that it was still backwards compatible and figured I would contribute it back if you guys found it worth maintaining. Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a NoSuchMethodException as expected but everything else seemed to work. Also tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. Here is the changeset: https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6.patch was: This is presumptions of me and I apologize for that and will understand if this is closed outright but I was going to fork camel-sjms and add support for some JMS 2.0 for my own uses and during testing found out that it was still backwards compatible and figured I would contribute it back if you guys found it worth maintaining. Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a NoSuchMethodException as expected but everything else seemed to work. Also tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. Here is the changeset: https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6 > JMS 2.0 shared subscriptions > > > Key: CAMEL-10918 > URL: https://issues.apache.org/jira/browse/CAMEL-10918 > Project: Camel > Issue Type: New Feature > Components: camel-sjms >Reporter: Ryan Yeats >Priority: Minor > > This is presumptions of me and I apologize for that and will understand if > this is closed outright but I was going to fork camel-sjms and add support > for some JMS 2.0 for my own uses and during testing found out that it was > still backwards compatible and figured I would contribute it back if you guys > found it worth maintaining. > Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a > NoSuchMethodException as expected but everything else seemed to work. Also > tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. > Here is the changeset: > https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6.patch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-10918) JMS 2.0 shared subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-10918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Yeats updated CAMEL-10918: --- Description: This is presumptions of me and I apologize for that and will understand if this is closed outright but I was going to fork camel-sjms and add support for some JMS 2.0 for my own uses and during testing found out that it was still backwards compatible and figured I would contribute it back if you guys found it worth maintaining. Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a NoSuchMethodException as expected but everything else seemed to work. Also tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. Here is the changeset: https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6 was: This is presumptions of me and I apologize for that and will understand if this is closed outright but I was going to fork camel-sjms and add support for some JMS 2.0 for my own uses and during testing found out that it was still backwards compatible and figured I would contribute it back if you guys found it worth maintaining. Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a NoSuchMethodException as expected but everything else seemed to work. Also tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6 > JMS 2.0 shared subscriptions > > > Key: CAMEL-10918 > URL: https://issues.apache.org/jira/browse/CAMEL-10918 > Project: Camel > Issue Type: New Feature > Components: camel-sjms >Reporter: Ryan Yeats >Priority: Minor > > This is presumptions of me and I apologize for that and will understand if > this is closed outright but I was going to fork camel-sjms and add support > for some JMS 2.0 for my own uses and during testing found out that it was > still backwards compatible and figured I would contribute it back if you guys > found it worth maintaining. > Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a > NoSuchMethodException as expected but everything else seemed to work. Also > tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. > Here is the changeset: > https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-10918) JMS 2.0 shared subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-10918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Yeats updated CAMEL-10918: --- Description: This is presumptions of me and I apologize for that and will understand if this is closed outright but I was going to fork camel-sjms and add support for some JMS 2.0 for my own uses and during testing found out that it was still backwards compatible and figured I would contribute it back if you guys found it worth maintaining. Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a NoSuchMethodException as expected but everything else seemed to work. Also tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6 was: This is presumptions of me and I apologize for that and will understand if this is closed outright but I was going to fork camel-sjms and add support for some JMS 2.0 for my own uses and during testing found out that it was still backwards compatible and figured I would contribute it back if you guys found it worth maintaining. Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a NoSuchMethodException as expected but everything else seemed to work. Also tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. > JMS 2.0 shared subscriptions > > > Key: CAMEL-10918 > URL: https://issues.apache.org/jira/browse/CAMEL-10918 > Project: Camel > Issue Type: New Feature > Components: camel-sjms >Reporter: Ryan Yeats >Priority: Minor > > This is presumptions of me and I apologize for that and will understand if > this is closed outright but I was going to fork camel-sjms and add support > for some JMS 2.0 for my own uses and during testing found out that it was > still backwards compatible and figured I would contribute it back if you guys > found it worth maintaining. > Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a > NoSuchMethodException as expected but everything else seemed to work. Also > tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. > https://github.com/ryeats/camel/commit/80f875572ffd2a16ec24d9302479201dc9b188f6 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-10918) JMS 2.0 shared subscriptions
Ryan Yeats created CAMEL-10918: -- Summary: JMS 2.0 shared subscriptions Key: CAMEL-10918 URL: https://issues.apache.org/jira/browse/CAMEL-10918 Project: Camel Issue Type: New Feature Components: camel-sjms Reporter: Ryan Yeats Priority: Minor This is presumptions of me and I apologize for that and will understand if this is closed outright but I was going to fork camel-sjms and add support for some JMS 2.0 for my own uses and during testing found out that it was still backwards compatible and figured I would contribute it back if you guys found it worth maintaining. Tested this on karaf 4.10 with activemq 5.14.3 shared subscriptions caused a NoSuchMethodException as expected but everything else seemed to work. Also tested on karaf 4.10 with artemis 1.5.1 shared subscriptions worked. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-10912) Session object created from connection that gets closed
Ryan Yeats created CAMEL-10912:
--
Summary: Session object created from connection that gets closed
Key: CAMEL-10912
URL: https://issues.apache.org/jira/browse/CAMEL-10912
Project: Camel
Issue Type: Bug
Components: camel-sjms
Affects Versions: 2.18.2
Reporter: Ryan Yeats
This is not easy to reproduce I haven't been able to simplify it down from our
code to recreate it but I can reliably cause it to happen. Basically if you
hit a camel-sjms route with a spike of load from nothing and have a bunch of
.toD("dynamic-${route}") it can create more connections than the pool allows
then when a connection is returned it is closed and one of the routes will be
using a session with a closed connection and will not work until it is
restarted.
The code in question:
https://github.com/apache/camel/blob/camel-2.18.x/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/producer/InOnlyProducer.java#L51-L67
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
