[jira] [Assigned] (CAMEL-8841) camel:context-inflight returns 'Object name cannot be null'
[
https://issues.apache.org/jira/browse/CAMEL-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-8841:
--
Assignee: Claus Ibsen
camel:context-inflight returns 'Object name cannot be null'
---
Key: CAMEL-8841
URL: https://issues.apache.org/jira/browse/CAMEL-8841
Project: Camel
Issue Type: Bug
Components: karaf, tooling
Affects Versions: 2.15.1, 2.15.2
Environment: Karaf 3.0.3
Reporter: Martin Lichtin
Assignee: Claus Ibsen
Fix For: 2.16.0, 2.15.3
Attachments: patchfile.txt
{noformat}
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
karaf log:exception-display
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:569)[:1.8.0_45]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:638)[:1.8.0_45]
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)[karaf-jmx-boot.jar:]
at com.sun.proxy.$Proxy0.isRegistered(Unknown Source)[:]
at
org.apache.camel.commands.AbstractLocalCamelController.browseInflightExchanges(AbstractLocalCamelController.java:186)
at
org.apache.camel.commands.ContextInflightCommand.performContextCommand(ContextInflightCommand.java:56)
at
org.apache.camel.commands.AbstractContextCommand.executeLocal(AbstractContextCommand.java:74)
at
org.apache.camel.commands.AbstractContextCommand.execute(AbstractContextCommand.java:42)
at
org.apache.camel.karaf.commands.ContextInflight.doExecute(ContextInflight.java:40)
at
org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
at
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:208)
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.runConsole(ShellFactoryImpl.java:158)[52:org.apache.karaf.shell.ssh:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1$1.run(ShellFactoryImpl.java:133)
at java.security.AccessController.doPrivileged(Native
Method)[:1.8.0_45]
at
org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:57)[26:org.apache.karaf.jaas.modules:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.run(ShellFactoryImpl.java:129)[52:org.apache.karaf.shell.ssh:3.0.3]
Caused by: java.lang.IllegalArgumentException: Object name cannot be null
... 30 more
{noformat}
I think when combining the object name
SetObjectName set = mBeanServer.queryNames(new
ObjectName(agent.getMBeanObjectDomainName() +
:type=services,name=DefaultInflightRepository,*), null);
The :context=context-name part seems missing.
The query should be something like
org.apache.camel:context=context-name,type=services,name=DefaultInflightRepository
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8873) Management api for ErrorHandler to expose stats about pending exchanges scheduled for redelivery
Claus Ibsen created CAMEL-8873: -- Summary: Management api for ErrorHandler to expose stats about pending exchanges scheduled for redelivery Key: CAMEL-8873 URL: https://issues.apache.org/jira/browse/CAMEL-8873 Project: Camel Issue Type: New Feature Components: camel-core, jmx Reporter: Claus Ibsen Fix For: 2.16.0, Future See nabble http://camel.465427.n5.nabble.com/DeadLetterQueue-Access-the-object-before-shutDown-tp5768069p5768244.html We could expose some more stats on ManagedErrorHandlerMBean to include details about number of pending exchanges for redelivery, and a tabular list with the list of exchanges etc. Currently end users can get some details from the inflight repo but that is generic. You may want to pin down on exchanges pending for redelivery in the error handlers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8871) null body after exception from transform method
[
https://issues.apache.org/jira/browse/CAMEL-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14585654#comment-14585654
]
Claus Ibsen commented on CAMEL-8871:
The same problem is potential in setBody / setHeader. Fixing a few others as
well.
null body after exception from transform method
---
Key: CAMEL-8871
URL: https://issues.apache.org/jira/browse/CAMEL-8871
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.2
Reporter: Hans Orbaan
Assignee: Claus Ibsen
Priority: Minor
Fix For: 2.16.0, 2.15.3
Attachments: ExceptionToErrorRouteTest.java
When an exception is thrown from a transform method I lose the content of the
message body. This behaviour is unexpected because it does not happen when an
exception is thrown from a bean call.
.bean(ErrorBean.class, ErrorBean.METHOD)
Vs.
.transform().method(ErrorBean.class, ErrorBean.METHOD)
I have a testcase that I will try to get attached but here are the routes:
{code:java}
if (testTransformExceptionToErrorRoute.equals(getTestMethodName())) {
from(START)
.routeId(exception.test.transform)
.transform().method(ErrorBean.class, ErrorBean.METHOD)
.to(END);
} else {
from(START)
.routeId(exception.test.bean)
.bean(ErrorBean.class, ErrorBean.METHOD)
.to(END);
}
public static class ErrorBean {
private static final String METHOD = throwException;
public static void throwException(Exchange exchange) {
String body = exchange.getIn().getBody(String.class);
Assertions.assertThat(body).isEqualTo(BODY);
throw new NullPointerException();
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8872) Camel-Hazelcast: Add new operations HazelcastAtomicNumber producer
Andrea Cosentino created CAMEL-8872: --- Summary: Camel-Hazelcast: Add new operations HazelcastAtomicNumber producer Key: CAMEL-8872 URL: https://issues.apache.org/jira/browse/CAMEL-8872 Project: Camel Issue Type: Improvement Components: camel-hazelcast Reporter: Andrea Cosentino Priority: Minor Fix For: 2.16.0 There are some new operations supported by Hazelcast IAtomicLong that can be added to HazelcastAtomicNumber producer. These operations are: - compareAndSet - getAndAdd - getAndIncrement -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8841) camel:context-inflight returns 'Object name cannot be null'
[
https://issues.apache.org/jira/browse/CAMEL-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8841:
---
Priority: Minor (was: Major)
camel:context-inflight returns 'Object name cannot be null'
---
Key: CAMEL-8841
URL: https://issues.apache.org/jira/browse/CAMEL-8841
Project: Camel
Issue Type: Bug
Components: karaf, tooling
Affects Versions: 2.15.1, 2.15.2
Environment: Karaf 3.0.3
Reporter: Martin Lichtin
Assignee: Claus Ibsen
Priority: Minor
Fix For: 2.16.0, 2.15.3
Attachments: patchfile.txt
{noformat}
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
karaf log:exception-display
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:569)[:1.8.0_45]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:638)[:1.8.0_45]
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)[karaf-jmx-boot.jar:]
at com.sun.proxy.$Proxy0.isRegistered(Unknown Source)[:]
at
org.apache.camel.commands.AbstractLocalCamelController.browseInflightExchanges(AbstractLocalCamelController.java:186)
at
org.apache.camel.commands.ContextInflightCommand.performContextCommand(ContextInflightCommand.java:56)
at
org.apache.camel.commands.AbstractContextCommand.executeLocal(AbstractContextCommand.java:74)
at
org.apache.camel.commands.AbstractContextCommand.execute(AbstractContextCommand.java:42)
at
org.apache.camel.karaf.commands.ContextInflight.doExecute(ContextInflight.java:40)
at
org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
at
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:208)
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.runConsole(ShellFactoryImpl.java:158)[52:org.apache.karaf.shell.ssh:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1$1.run(ShellFactoryImpl.java:133)
at java.security.AccessController.doPrivileged(Native
Method)[:1.8.0_45]
at
org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:57)[26:org.apache.karaf.jaas.modules:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.run(ShellFactoryImpl.java:129)[52:org.apache.karaf.shell.ssh:3.0.3]
Caused by: java.lang.IllegalArgumentException: Object name cannot be null
... 30 more
{noformat}
I think when combining the object name
SetObjectName set = mBeanServer.queryNames(new
ObjectName(agent.getMBeanObjectDomainName() +
:type=services,name=DefaultInflightRepository,*), null);
The :context=context-name part seems missing.
The query should be something like
org.apache.camel:context=context-name,type=services,name=DefaultInflightRepository
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-8841) camel:context-inflight returns 'Object name cannot be null'
[
https://issues.apache.org/jira/browse/CAMEL-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-8841.
Resolution: Fixed
Thanks for the patch.
camel:context-inflight returns 'Object name cannot be null'
---
Key: CAMEL-8841
URL: https://issues.apache.org/jira/browse/CAMEL-8841
Project: Camel
Issue Type: Bug
Components: karaf, tooling
Affects Versions: 2.15.1, 2.15.2
Environment: Karaf 3.0.3
Reporter: Martin Lichtin
Assignee: Claus Ibsen
Priority: Minor
Fix For: 2.16.0, 2.15.3
Attachments: patchfile.txt
{noformat}
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
karaf log:exception-display
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:569)[:1.8.0_45]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:638)[:1.8.0_45]
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)[karaf-jmx-boot.jar:]
at com.sun.proxy.$Proxy0.isRegistered(Unknown Source)[:]
at
org.apache.camel.commands.AbstractLocalCamelController.browseInflightExchanges(AbstractLocalCamelController.java:186)
at
org.apache.camel.commands.ContextInflightCommand.performContextCommand(ContextInflightCommand.java:56)
at
org.apache.camel.commands.AbstractContextCommand.executeLocal(AbstractContextCommand.java:74)
at
org.apache.camel.commands.AbstractContextCommand.execute(AbstractContextCommand.java:42)
at
org.apache.camel.karaf.commands.ContextInflight.doExecute(ContextInflight.java:40)
at
org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
at
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:208)
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.runConsole(ShellFactoryImpl.java:158)[52:org.apache.karaf.shell.ssh:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1$1.run(ShellFactoryImpl.java:133)
at java.security.AccessController.doPrivileged(Native
Method)[:1.8.0_45]
at
org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:57)[26:org.apache.karaf.jaas.modules:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.run(ShellFactoryImpl.java:129)[52:org.apache.karaf.shell.ssh:3.0.3]
Caused by: java.lang.IllegalArgumentException: Object name cannot be null
... 30 more
{noformat}
I think when combining the object name
SetObjectName set = mBeanServer.queryNames(new
ObjectName(agent.getMBeanObjectDomainName() +
:type=services,name=DefaultInflightRepository,*), null);
The :context=context-name part seems missing.
The query should be something like
org.apache.camel:context=context-name,type=services,name=DefaultInflightRepository
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-8871) null body after exception from transform method
[
https://issues.apache.org/jira/browse/CAMEL-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-8871.
Resolution: Fixed
Thanks for reporting and the test case
null body after exception from transform method
---
Key: CAMEL-8871
URL: https://issues.apache.org/jira/browse/CAMEL-8871
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.2
Reporter: Hans Orbaan
Assignee: Claus Ibsen
Priority: Minor
Fix For: 2.16.0, 2.15.3
Attachments: ExceptionToErrorRouteTest.java
When an exception is thrown from a transform method I lose the content of the
message body. This behaviour is unexpected because it does not happen when an
exception is thrown from a bean call.
.bean(ErrorBean.class, ErrorBean.METHOD)
Vs.
.transform().method(ErrorBean.class, ErrorBean.METHOD)
I have a testcase that I will try to get attached but here are the routes:
{code:java}
if (testTransformExceptionToErrorRoute.equals(getTestMethodName())) {
from(START)
.routeId(exception.test.transform)
.transform().method(ErrorBean.class, ErrorBean.METHOD)
.to(END);
} else {
from(START)
.routeId(exception.test.bean)
.bean(ErrorBean.class, ErrorBean.METHOD)
.to(END);
}
public static class ErrorBean {
private static final String METHOD = throwException;
public static void throwException(Exchange exchange) {
String body = exchange.getIn().getBody(String.class);
Assertions.assertThat(body).isEqualTo(BODY);
throw new NullPointerException();
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8872) Camel-Hazelcast: Add new operations to HazelcastAtomicNumber producer
[ https://issues.apache.org/jira/browse/CAMEL-8872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-8872: Description: There are some new operations supported by Hazelcast IAtomicLong that can be added to HazelcastAtomicNumber producer. These operations are: - compareAndSet - getAndAdd was: There are some new operations supported by Hazelcast IAtomicLong that can be added to HazelcastAtomicNumber producer. These operations are: - compareAndSet - getAndAdd - getAndIncrement Camel-Hazelcast: Add new operations to HazelcastAtomicNumber producer - Key: CAMEL-8872 URL: https://issues.apache.org/jira/browse/CAMEL-8872 Project: Camel Issue Type: Improvement Components: camel-hazelcast Reporter: Andrea Cosentino Assignee: Andrea Cosentino Priority: Minor Fix For: 2.16.0 There are some new operations supported by Hazelcast IAtomicLong that can be added to HazelcastAtomicNumber producer. These operations are: - compareAndSet - getAndAdd -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8870) Remove version from URL in Maven web archetype
[ https://issues.apache.org/jira/browse/CAMEL-8870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8870. Resolution: Fixed Assignee: Claus Ibsen Thanks for the PR Remove version from URL in Maven web archetype -- Key: CAMEL-8870 URL: https://issues.apache.org/jira/browse/CAMEL-8870 Project: Camel Issue Type: Improvement Components: tooling Affects Versions: 2.16.0 Reporter: Andrew Block Assignee: Claus Ibsen Priority: Minor Fix For: 2.16.0 The archteype currently generates a project where the version is required to be entered when accessing the deployed application. Removing the requirement of specifying the version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8872) Camel-Hazelcast: Add new operations to HazelcastAtomicNumber producer
[ https://issues.apache.org/jira/browse/CAMEL-8872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-8872: Summary: Camel-Hazelcast: Add new operations to HazelcastAtomicNumber producer (was: Camel-Hazelcast: Add new operations HazelcastAtomicNumber producer) Camel-Hazelcast: Add new operations to HazelcastAtomicNumber producer - Key: CAMEL-8872 URL: https://issues.apache.org/jira/browse/CAMEL-8872 Project: Camel Issue Type: Improvement Components: camel-hazelcast Reporter: Andrea Cosentino Assignee: Andrea Cosentino Priority: Minor Fix For: 2.16.0 There are some new operations supported by Hazelcast IAtomicLong that can be added to HazelcastAtomicNumber producer. These operations are: - compareAndSet - getAndAdd - getAndIncrement -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8872) Camel-Hazelcast: Add new operations HazelcastAtomicNumber producer
[ https://issues.apache.org/jira/browse/CAMEL-8872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-8872: --- Assignee: Andrea Cosentino Camel-Hazelcast: Add new operations HazelcastAtomicNumber producer -- Key: CAMEL-8872 URL: https://issues.apache.org/jira/browse/CAMEL-8872 Project: Camel Issue Type: Improvement Components: camel-hazelcast Reporter: Andrea Cosentino Assignee: Andrea Cosentino Priority: Minor Fix For: 2.16.0 There are some new operations supported by Hazelcast IAtomicLong that can be added to HazelcastAtomicNumber producer. These operations are: - compareAndSet - getAndAdd - getAndIncrement -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8874) camel-blueprint-archetypes should have test dependency of camel-test-blueprint
[ https://issues.apache.org/jira/browse/CAMEL-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-8874: Fix Version/s: (was: 2.14.4) camel-blueprint-archetypes should have test dependency of camel-test-blueprint -- Key: CAMEL-8874 URL: https://issues.apache.org/jira/browse/CAMEL-8874 Project: Camel Issue Type: Bug Components: camel-archetypes Affects Versions: 2.15.0, 2.15.1, 2.15.2 Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.16.0, 2.15.3 The camel-test-blueprint dependency scope should be test, otherwise bundle plugin could import the packages of pojosr framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8874) camel-blueprint-archetypes should have test dependency of camel-test-blueprint
[ https://issues.apache.org/jira/browse/CAMEL-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-8874: Fix Version/s: 2.16.0 camel-blueprint-archetypes should have test dependency of camel-test-blueprint -- Key: CAMEL-8874 URL: https://issues.apache.org/jira/browse/CAMEL-8874 Project: Camel Issue Type: Bug Components: camel-archetypes Affects Versions: 2.14.3, 2.15.2 Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.16.0, 2.15.3, 2.14.4 The camel-test-blueprint dependency scope should be test, otherwise bundle plugin could import the packages of pojosr framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8874) camel-blueprint-archetypes should have test dependency of camel-test-blueprint
[ https://issues.apache.org/jira/browse/CAMEL-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-8874: Summary: camel-blueprint-archetypes should have test dependency of camel-test-blueprint (was: camel-blueprint-archetypes should have test dependency of ) camel-blueprint-archetypes should have test dependency of camel-test-blueprint -- Key: CAMEL-8874 URL: https://issues.apache.org/jira/browse/CAMEL-8874 Project: Camel Issue Type: Bug Components: camel-archetypes Affects Versions: 2.14.3, 2.15.2 Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.16.0, 2.15.3, 2.14.4 The camel-test-blueprint dependency scope should be test, otherwise bundle plugin could import the packages of pojosr framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8874) camel-blueprint-archetypes should have test dependency of camel-test-blueprint
[ https://issues.apache.org/jira/browse/CAMEL-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-8874: Affects Version/s: (was: 2.14.3) 2.15.0 2.15.1 camel-blueprint-archetypes should have test dependency of camel-test-blueprint -- Key: CAMEL-8874 URL: https://issues.apache.org/jira/browse/CAMEL-8874 Project: Camel Issue Type: Bug Components: camel-archetypes Affects Versions: 2.15.0, 2.15.1, 2.15.2 Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.16.0, 2.15.3 The camel-test-blueprint dependency scope should be test, otherwise bundle plugin could import the packages of pojosr framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8874) camel-blueprint-archetypes should have test dependency of camel-test-blueprint
[ https://issues.apache.org/jira/browse/CAMEL-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14586159#comment-14586159 ] Willem Jiang commented on CAMEL-8874: - Applied the patch into camel master and camel-2.15.x branch. camel-blueprint-archetypes should have test dependency of camel-test-blueprint -- Key: CAMEL-8874 URL: https://issues.apache.org/jira/browse/CAMEL-8874 Project: Camel Issue Type: Bug Components: camel-archetypes Affects Versions: 2.15.0, 2.15.1, 2.15.2 Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.16.0, 2.15.3 The camel-test-blueprint dependency scope should be test, otherwise bundle plugin could import the packages of pojosr framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8874) camel-blueprint-archetypes should have test dependency of camel-test-blueprint
[ https://issues.apache.org/jira/browse/CAMEL-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-8874. - Resolution: Fixed camel-blueprint-archetypes should have test dependency of camel-test-blueprint -- Key: CAMEL-8874 URL: https://issues.apache.org/jira/browse/CAMEL-8874 Project: Camel Issue Type: Bug Components: camel-archetypes Affects Versions: 2.15.0, 2.15.1, 2.15.2 Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.16.0, 2.15.3 The camel-test-blueprint dependency scope should be test, otherwise bundle plugin could import the packages of pojosr framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-8855) camel-jpa - Add support for JPA producer to delete records
[
https://issues.apache.org/jira/browse/CAMEL-8855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14586205#comment-14586205
]
Andrea Cosentino edited comment on CAMEL-8855 at 6/15/15 3:37 PM:
--
Thank you for reporting and opening this JIRA issue :-)
was (Author: ancosen):
Thank you for reporting and opening this JIRA issue:-)
camel-jpa - Add support for JPA producer to delete records
--
Key: CAMEL-8855
URL: https://issues.apache.org/jira/browse/CAMEL-8855
Project: Camel
Issue Type: New Feature
Components: camel-jpa
Affects Versions: 2.15.2
Reporter: Tadayoshi Sato
Assignee: Andrea Cosentino
Currently, camel-jpa producer
{code:java}
to(jpa:MyEntity?...)
{code}
can only invoke {{EntityManager.persist()}} or {{EntityManager.merge()}}, but
sometimes users want to send JPA entities to camel-jpa producer to delete
them from the database, i.e. invoke {{EntityManager.remove()}}.
Maybe, introducing {{remove}} option to JPA producer is sufficient like this:
{code:java}
to(jpa:MyEntity?remove=true)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8855) camel-jpa - Add support for JPA producer to delete records
[
https://issues.apache.org/jira/browse/CAMEL-8855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14586205#comment-14586205
]
Andrea Cosentino commented on CAMEL-8855:
-
Thank you for reporting and opening this JIRA issue:-)
camel-jpa - Add support for JPA producer to delete records
--
Key: CAMEL-8855
URL: https://issues.apache.org/jira/browse/CAMEL-8855
Project: Camel
Issue Type: New Feature
Components: camel-jpa
Affects Versions: 2.15.2
Reporter: Tadayoshi Sato
Assignee: Andrea Cosentino
Currently, camel-jpa producer
{code:java}
to(jpa:MyEntity?...)
{code}
can only invoke {{EntityManager.persist()}} or {{EntityManager.merge()}}, but
sometimes users want to send JPA entities to camel-jpa producer to delete
them from the database, i.e. invoke {{EntityManager.remove()}}.
Maybe, introducing {{remove}} option to JPA producer is sufficient like this:
{code:java}
to(jpa:MyEntity?remove=true)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-8872) Camel-Hazelcast: Add new operations to HazelcastAtomicNumber producer
[ https://issues.apache.org/jira/browse/CAMEL-8872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-8872. - Resolution: Fixed Related commits: http://git-wip-us.apache.org/repos/asf/camel/commit/68c62b68 http://git-wip-us.apache.org/repos/asf/camel/commit/11883ff7 http://git-wip-us.apache.org/repos/asf/camel/commit/75745c5a Camel-Hazelcast: Add new operations to HazelcastAtomicNumber producer - Key: CAMEL-8872 URL: https://issues.apache.org/jira/browse/CAMEL-8872 Project: Camel Issue Type: Improvement Components: camel-hazelcast Reporter: Andrea Cosentino Assignee: Andrea Cosentino Priority: Minor Fix For: 2.16.0 There are some new operations supported by Hazelcast IAtomicLong that can be added to HazelcastAtomicNumber producer. These operations are: - compareAndSet - getAndAdd -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8874) camel-blueprint-archetypes
Willem Jiang created CAMEL-8874: --- Summary: camel-blueprint-archetypes Key: CAMEL-8874 URL: https://issues.apache.org/jira/browse/CAMEL-8874 Project: Camel Issue Type: Bug Components: camel-archetypes Affects Versions: 2.15.2, 2.14.3 Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.15.3, 2.14.4 The camel-test-blueprint dependency scope should be test, otherwise bundle plugin could import the packages of pojosr framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8874) camel-blueprint-archetypes should have test dependency of
[ https://issues.apache.org/jira/browse/CAMEL-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-8874: Summary: camel-blueprint-archetypes should have test dependency of (was: camel-blueprint-archetypes) camel-blueprint-archetypes should have test dependency of -- Key: CAMEL-8874 URL: https://issues.apache.org/jira/browse/CAMEL-8874 Project: Camel Issue Type: Bug Components: camel-archetypes Affects Versions: 2.14.3, 2.15.2 Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.16.0, 2.15.3, 2.14.4 The camel-test-blueprint dependency scope should be test, otherwise bundle plugin could import the packages of pojosr framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8875) Keep getting -- Cannot acuire read lock
[ https://issues.apache.org/jira/browse/CAMEL-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14587357#comment-14587357 ] Willem Jiang commented on CAMEL-8875: - Please use the mailing list to discuss the issue first. You doesn't show us the camel route and you should use the same version of camel components. Keep getting -- Cannot acuire read lock --- Key: CAMEL-8875 URL: https://issues.apache.org/jira/browse/CAMEL-8875 Project: Camel Issue Type: Bug Affects Versions: 2.14.0 Reporter: Nayana Devanandan Priority: Critical I have a single jetty server and I keep getting the below in logs. WARN org.apache.camel.component.file.strategy.FileChangedExclusiveReadLockStrategy - Cannot acquire read lock within 5000 millis. Will skip the file: GenericFile List of maven dependencies in the project !-- Camel Dependencies -- dependency groupIdorg.apache.camel/groupId artifactIdcamel-core/artifactId version2.14.0/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-spring/artifactId version2.14.0/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-stream/artifactId version2.14.0/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-cxf/artifactId version2.14.0/version !-- use the same version as your Camel core version -- /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-http4/artifactId version2.14.0/version !-- use the same version as your Camel core version -- /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-zipfile/artifactId version2.12.2/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-csv/artifactId version2.12.2/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-metrics/artifactId version2.14.0/version /dependency dependency groupIdorg.apache-extras.camel-extra/groupId artifactIdcamel-jcifs/artifactId version2.13.3/version !-- use the same version as your Camel core version -- /dependency -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8875) Keep getting -- Cannot acuire read lock
[ https://issues.apache.org/jira/browse/CAMEL-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-8875: Priority: Major (was: Critical) Keep getting -- Cannot acuire read lock --- Key: CAMEL-8875 URL: https://issues.apache.org/jira/browse/CAMEL-8875 Project: Camel Issue Type: Bug Affects Versions: 2.14.0 Reporter: Nayana Devanandan I have a single jetty server and I keep getting the below in logs. WARN org.apache.camel.component.file.strategy.FileChangedExclusiveReadLockStrategy - Cannot acquire read lock within 5000 millis. Will skip the file: GenericFile List of maven dependencies in the project !-- Camel Dependencies -- dependency groupIdorg.apache.camel/groupId artifactIdcamel-core/artifactId version2.14.0/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-spring/artifactId version2.14.0/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-stream/artifactId version2.14.0/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-cxf/artifactId version2.14.0/version !-- use the same version as your Camel core version -- /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-http4/artifactId version2.14.0/version !-- use the same version as your Camel core version -- /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-zipfile/artifactId version2.12.2/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-csv/artifactId version2.12.2/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-metrics/artifactId version2.14.0/version /dependency dependency groupIdorg.apache-extras.camel-extra/groupId artifactIdcamel-jcifs/artifactId version2.13.3/version !-- use the same version as your Camel core version -- /dependency -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8876) Add an option for HttpProducer to ignore response body avoiding stream caching
Willem Jiang created CAMEL-8876: --- Summary: Add an option for HttpProducer to ignore response body avoiding stream caching Key: CAMEL-8876 URL: https://issues.apache.org/jira/browse/CAMEL-8876 Project: Camel Issue Type: Improvement Components: camel-http, camel-http4 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.16.0 Sometime the user just want to check the response code and don't want to read the response, we can enable this kind of feature with the option ignoreRequestBody. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8875) Keeps getting Cannot acuire read lock
Nayana Devanandan created CAMEL-8875: Summary: Keeps getting Cannot acuire read lock Key: CAMEL-8875 URL: https://issues.apache.org/jira/browse/CAMEL-8875 Project: Camel Issue Type: Bug Affects Versions: 2.14.0 Reporter: Nayana Devanandan I have a single jetty server and I keep getting the below in logs. WARN org.apache.camel.component.file.strategy.FileChangedExclusiveReadLockStrategy - Cannot acquire read lock within 5000 millis. Will skip the file: GenericFile List of maven dependencies in the project !-- Camel Dependencies -- dependency groupIdorg.apache.camel/groupId artifactIdcamel-core/artifactId version2.14.0/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-spring/artifactId version2.14.0/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-stream/artifactId version2.14.0/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-cxf/artifactId version2.14.0/version !-- use the same version as your Camel core version -- /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-http4/artifactId version2.14.0/version !-- use the same version as your Camel core version -- /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-zipfile/artifactId version2.12.2/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-csv/artifactId version2.12.2/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-metrics/artifactId version2.14.0/version /dependency dependency groupIdorg.apache-extras.camel-extra/groupId artifactIdcamel-jcifs/artifactId version2.13.3/version !-- use the same version as your Camel core version -- /dependency -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8875) Keep getting -- Cannot acuire read lock
[ https://issues.apache.org/jira/browse/CAMEL-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nayana Devanandan updated CAMEL-8875: - Summary: Keep getting -- Cannot acuire read lock (was: Keeps getting Cannot acuire read lock) Keep getting -- Cannot acuire read lock --- Key: CAMEL-8875 URL: https://issues.apache.org/jira/browse/CAMEL-8875 Project: Camel Issue Type: Bug Affects Versions: 2.14.0 Reporter: Nayana Devanandan I have a single jetty server and I keep getting the below in logs. WARN org.apache.camel.component.file.strategy.FileChangedExclusiveReadLockStrategy - Cannot acquire read lock within 5000 millis. Will skip the file: GenericFile List of maven dependencies in the project !-- Camel Dependencies -- dependency groupIdorg.apache.camel/groupId artifactIdcamel-core/artifactId version2.14.0/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-spring/artifactId version2.14.0/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-stream/artifactId version2.14.0/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-cxf/artifactId version2.14.0/version !-- use the same version as your Camel core version -- /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-http4/artifactId version2.14.0/version !-- use the same version as your Camel core version -- /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-zipfile/artifactId version2.12.2/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-csv/artifactId version2.12.2/version /dependency dependency groupIdorg.apache.camel/groupId artifactIdcamel-metrics/artifactId version2.14.0/version /dependency dependency groupIdorg.apache-extras.camel-extra/groupId artifactIdcamel-jcifs/artifactId version2.13.3/version !-- use the same version as your Camel core version -- /dependency -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8841) camel:context-inflight returns 'Object name cannot be null'
[
https://issues.apache.org/jira/browse/CAMEL-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Lichtin updated CAMEL-8841:
--
Attachment: patchfile.txt
camel:context-inflight returns 'Object name cannot be null'
---
Key: CAMEL-8841
URL: https://issues.apache.org/jira/browse/CAMEL-8841
Project: Camel
Issue Type: Bug
Components: karaf, tooling
Affects Versions: 2.15.1, 2.15.2
Environment: Karaf 3.0.3
Reporter: Martin Lichtin
Fix For: 2.16.0, 2.15.3
Attachments: patchfile.txt
{noformat}
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
karaf log:exception-display
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:569)[:1.8.0_45]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:638)[:1.8.0_45]
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)[karaf-jmx-boot.jar:]
at com.sun.proxy.$Proxy0.isRegistered(Unknown Source)[:]
at
org.apache.camel.commands.AbstractLocalCamelController.browseInflightExchanges(AbstractLocalCamelController.java:186)
at
org.apache.camel.commands.ContextInflightCommand.performContextCommand(ContextInflightCommand.java:56)
at
org.apache.camel.commands.AbstractContextCommand.executeLocal(AbstractContextCommand.java:74)
at
org.apache.camel.commands.AbstractContextCommand.execute(AbstractContextCommand.java:42)
at
org.apache.camel.karaf.commands.ContextInflight.doExecute(ContextInflight.java:40)
at
org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
at
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:208)
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.runConsole(ShellFactoryImpl.java:158)[52:org.apache.karaf.shell.ssh:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1$1.run(ShellFactoryImpl.java:133)
at java.security.AccessController.doPrivileged(Native
Method)[:1.8.0_45]
at
org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:57)[26:org.apache.karaf.jaas.modules:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.run(ShellFactoryImpl.java:129)[52:org.apache.karaf.shell.ssh:3.0.3]
Caused by: java.lang.IllegalArgumentException: Object name cannot be null
... 30 more
{noformat}
I think when combining the object name
SetObjectName set = mBeanServer.queryNames(new
ObjectName(agent.getMBeanObjectDomainName() +
:type=services,name=DefaultInflightRepository,*), null);
The :context=context-name part seems missing.
The query should be something like
org.apache.camel:context=context-name,type=services,name=DefaultInflightRepository
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8871) null body after exception from transform method
Hans Orbaan created CAMEL-8871:
--
Summary: null body after exception from transform method
Key: CAMEL-8871
URL: https://issues.apache.org/jira/browse/CAMEL-8871
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.2
Reporter: Hans Orbaan
Priority: Critical
When an exception is thrown from a transform method I lose the content of the
message body. This behaviour is unexpected because it does not happen when an
exception is thrown from a bean call.
.bean(ErrorBean.class, ErrorBean.METHOD)
Vs.
.transform().method(ErrorBean.class, ErrorBean.METHOD)
I have a testcase that I will try to get attached but here are the routes:
{code:java}
if (testTransformExceptionToErrorRoute.equals(getTestMethodName())) {
from(START)
.routeId(exception.test.transform)
.transform().method(ErrorBean.class, ErrorBean.METHOD)
.to(END);
} else {
from(START)
.routeId(exception.test.bean)
.bean(ErrorBean.class, ErrorBean.METHOD)
.to(END);
}
public static class ErrorBean {
private static final String METHOD = throwException;
public static void throwException(Exchange exchange) {
String body = exchange.getIn().getBody(String.class);
Assertions.assertThat(body).isEqualTo(BODY);
throw new AssertionError();
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8841) camel:context-inflight returns 'Object name cannot be null'
[
https://issues.apache.org/jira/browse/CAMEL-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14585620#comment-14585620
]
Martin Lichtin commented on CAMEL-8841:
---
BTW, I see a regression in 2.16-SNAPSHOT with regards to Blueprint config files.
For example:
{noformat}
camelContext id=myContext
xmlns=http://camel.apache.org/schema/blueprint;
xsi:schemaLocation=http://camel.apache.org/schema/blueprint
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
depends-on=jms,PROPAGATION_REQUIRED
{noformat}
gives
{noformat}
org.osgi.service.blueprint.container.ComponentDefinitionException: Unresolved
ref/idref to component: jms,PROPAGATION_REQUIRED
{noformat}
It no longer seems to understand the depends-on in case of more than one
reference mentioned.
As far as I remember, the separator could be comma or space.
camel:context-inflight returns 'Object name cannot be null'
---
Key: CAMEL-8841
URL: https://issues.apache.org/jira/browse/CAMEL-8841
Project: Camel
Issue Type: Bug
Components: karaf, tooling
Affects Versions: 2.15.1, 2.15.2
Environment: Karaf 3.0.3
Reporter: Martin Lichtin
Fix For: 2.16.0, 2.15.3
Attachments: patchfile.txt
{noformat}
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
karaf log:exception-display
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:569)[:1.8.0_45]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:638)[:1.8.0_45]
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)[karaf-jmx-boot.jar:]
at com.sun.proxy.$Proxy0.isRegistered(Unknown Source)[:]
at
org.apache.camel.commands.AbstractLocalCamelController.browseInflightExchanges(AbstractLocalCamelController.java:186)
at
org.apache.camel.commands.ContextInflightCommand.performContextCommand(ContextInflightCommand.java:56)
at
org.apache.camel.commands.AbstractContextCommand.executeLocal(AbstractContextCommand.java:74)
at
org.apache.camel.commands.AbstractContextCommand.execute(AbstractContextCommand.java:42)
at
org.apache.camel.karaf.commands.ContextInflight.doExecute(ContextInflight.java:40)
at
org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
at
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:208)
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.runConsole(ShellFactoryImpl.java:158)[52:org.apache.karaf.shell.ssh:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1$1.run(ShellFactoryImpl.java:133)
at java.security.AccessController.doPrivileged(Native
Method)[:1.8.0_45]
at
org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:57)[26:org.apache.karaf.jaas.modules:3.0.3]
at
[jira] [Updated] (CAMEL-8871) null body after exception from transform method
[
https://issues.apache.org/jira/browse/CAMEL-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hans Orbaan updated CAMEL-8871:
---
Attachment: ExceptionToErrorRouteTest.java
CamelTestSupport test that shows the difference between exception from
different calls. I would expect both tests to succeed and both methods to show
the same exception behavior.
null body after exception from transform method
---
Key: CAMEL-8871
URL: https://issues.apache.org/jira/browse/CAMEL-8871
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.2
Reporter: Hans Orbaan
Priority: Critical
Attachments: ExceptionToErrorRouteTest.java
When an exception is thrown from a transform method I lose the content of the
message body. This behaviour is unexpected because it does not happen when an
exception is thrown from a bean call.
.bean(ErrorBean.class, ErrorBean.METHOD)
Vs.
.transform().method(ErrorBean.class, ErrorBean.METHOD)
I have a testcase that I will try to get attached but here are the routes:
{code:java}
if (testTransformExceptionToErrorRoute.equals(getTestMethodName())) {
from(START)
.routeId(exception.test.transform)
.transform().method(ErrorBean.class, ErrorBean.METHOD)
.to(END);
} else {
from(START)
.routeId(exception.test.bean)
.bean(ErrorBean.class, ErrorBean.METHOD)
.to(END);
}
public static class ErrorBean {
private static final String METHOD = throwException;
public static void throwException(Exchange exchange) {
String body = exchange.getIn().getBody(String.class);
Assertions.assertThat(body).isEqualTo(BODY);
throw new AssertionError();
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8871) null body after exception from transform method
[
https://issues.apache.org/jira/browse/CAMEL-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8871:
---
Priority: Minor (was: Critical)
null body after exception from transform method
---
Key: CAMEL-8871
URL: https://issues.apache.org/jira/browse/CAMEL-8871
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.2
Reporter: Hans Orbaan
Priority: Minor
Attachments: ExceptionToErrorRouteTest.java
When an exception is thrown from a transform method I lose the content of the
message body. This behaviour is unexpected because it does not happen when an
exception is thrown from a bean call.
.bean(ErrorBean.class, ErrorBean.METHOD)
Vs.
.transform().method(ErrorBean.class, ErrorBean.METHOD)
I have a testcase that I will try to get attached but here are the routes:
{code:java}
if (testTransformExceptionToErrorRoute.equals(getTestMethodName())) {
from(START)
.routeId(exception.test.transform)
.transform().method(ErrorBean.class, ErrorBean.METHOD)
.to(END);
} else {
from(START)
.routeId(exception.test.bean)
.bean(ErrorBean.class, ErrorBean.METHOD)
.to(END);
}
public static class ErrorBean {
private static final String METHOD = throwException;
public static void throwException(Exchange exchange) {
String body = exchange.getIn().getBody(String.class);
Assertions.assertThat(body).isEqualTo(BODY);
throw new AssertionError();
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8871) null body after exception from transform method
[
https://issues.apache.org/jira/browse/CAMEL-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8871:
---
Fix Version/s: 2.15.3
2.16.0
null body after exception from transform method
---
Key: CAMEL-8871
URL: https://issues.apache.org/jira/browse/CAMEL-8871
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.2
Reporter: Hans Orbaan
Priority: Minor
Fix For: 2.16.0, 2.15.3
Attachments: ExceptionToErrorRouteTest.java
When an exception is thrown from a transform method I lose the content of the
message body. This behaviour is unexpected because it does not happen when an
exception is thrown from a bean call.
.bean(ErrorBean.class, ErrorBean.METHOD)
Vs.
.transform().method(ErrorBean.class, ErrorBean.METHOD)
I have a testcase that I will try to get attached but here are the routes:
{code:java}
if (testTransformExceptionToErrorRoute.equals(getTestMethodName())) {
from(START)
.routeId(exception.test.transform)
.transform().method(ErrorBean.class, ErrorBean.METHOD)
.to(END);
} else {
from(START)
.routeId(exception.test.bean)
.bean(ErrorBean.class, ErrorBean.METHOD)
.to(END);
}
public static class ErrorBean {
private static final String METHOD = throwException;
public static void throwException(Exchange exchange) {
String body = exchange.getIn().getBody(String.class);
Assertions.assertThat(body).isEqualTo(BODY);
throw new NullPointerException();
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8871) null body after exception from transform method
[
https://issues.apache.org/jira/browse/CAMEL-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hans Orbaan updated CAMEL-8871:
---
Description:
When an exception is thrown from a transform method I lose the content of the
message body. This behaviour is unexpected because it does not happen when an
exception is thrown from a bean call.
.bean(ErrorBean.class, ErrorBean.METHOD)
Vs.
.transform().method(ErrorBean.class, ErrorBean.METHOD)
I have a testcase that I will try to get attached but here are the routes:
{code:java}
if (testTransformExceptionToErrorRoute.equals(getTestMethodName())) {
from(START)
.routeId(exception.test.transform)
.transform().method(ErrorBean.class, ErrorBean.METHOD)
.to(END);
} else {
from(START)
.routeId(exception.test.bean)
.bean(ErrorBean.class, ErrorBean.METHOD)
.to(END);
}
public static class ErrorBean {
private static final String METHOD = throwException;
public static void throwException(Exchange exchange) {
String body = exchange.getIn().getBody(String.class);
Assertions.assertThat(body).isEqualTo(BODY);
throw new NullPointerException();
}
}
{code}
was:
When an exception is thrown from a transform method I lose the content of the
message body. This behaviour is unexpected because it does not happen when an
exception is thrown from a bean call.
.bean(ErrorBean.class, ErrorBean.METHOD)
Vs.
.transform().method(ErrorBean.class, ErrorBean.METHOD)
I have a testcase that I will try to get attached but here are the routes:
{code:java}
if (testTransformExceptionToErrorRoute.equals(getTestMethodName())) {
from(START)
.routeId(exception.test.transform)
.transform().method(ErrorBean.class, ErrorBean.METHOD)
.to(END);
} else {
from(START)
.routeId(exception.test.bean)
.bean(ErrorBean.class, ErrorBean.METHOD)
.to(END);
}
public static class ErrorBean {
private static final String METHOD = throwException;
public static void throwException(Exchange exchange) {
String body = exchange.getIn().getBody(String.class);
Assertions.assertThat(body).isEqualTo(BODY);
throw new AssertionError();
}
}
{code}
null body after exception from transform method
---
Key: CAMEL-8871
URL: https://issues.apache.org/jira/browse/CAMEL-8871
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.2
Reporter: Hans Orbaan
Priority: Minor
Fix For: 2.16.0, 2.15.3
Attachments: ExceptionToErrorRouteTest.java
When an exception is thrown from a transform method I lose the content of the
message body. This behaviour is unexpected because it does not happen when an
exception is thrown from a bean call.
.bean(ErrorBean.class, ErrorBean.METHOD)
Vs.
.transform().method(ErrorBean.class, ErrorBean.METHOD)
I have a testcase that I will try to get attached but here are the routes:
{code:java}
if (testTransformExceptionToErrorRoute.equals(getTestMethodName())) {
from(START)
.routeId(exception.test.transform)
.transform().method(ErrorBean.class, ErrorBean.METHOD)
.to(END);
} else {
from(START)
.routeId(exception.test.bean)
.bean(ErrorBean.class, ErrorBean.METHOD)
.to(END);
}
public static class ErrorBean {
private static final String METHOD = throwException;
public static void throwException(Exchange exchange) {
String body = exchange.getIn().getBody(String.class);
Assertions.assertThat(body).isEqualTo(BODY);
throw new NullPointerException();
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8871) null body after exception from transform method
[
https://issues.apache.org/jira/browse/CAMEL-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14585622#comment-14585622
]
Claus Ibsen commented on CAMEL-8871:
Use bean as workaround
null body after exception from transform method
---
Key: CAMEL-8871
URL: https://issues.apache.org/jira/browse/CAMEL-8871
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.2
Reporter: Hans Orbaan
Priority: Minor
Fix For: 2.16.0, 2.15.3
Attachments: ExceptionToErrorRouteTest.java
When an exception is thrown from a transform method I lose the content of the
message body. This behaviour is unexpected because it does not happen when an
exception is thrown from a bean call.
.bean(ErrorBean.class, ErrorBean.METHOD)
Vs.
.transform().method(ErrorBean.class, ErrorBean.METHOD)
I have a testcase that I will try to get attached but here are the routes:
{code:java}
if (testTransformExceptionToErrorRoute.equals(getTestMethodName())) {
from(START)
.routeId(exception.test.transform)
.transform().method(ErrorBean.class, ErrorBean.METHOD)
.to(END);
} else {
from(START)
.routeId(exception.test.bean)
.bean(ErrorBean.class, ErrorBean.METHOD)
.to(END);
}
public static class ErrorBean {
private static final String METHOD = throwException;
public static void throwException(Exchange exchange) {
String body = exchange.getIn().getBody(String.class);
Assertions.assertThat(body).isEqualTo(BODY);
throw new NullPointerException();
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-8871) null body after exception from transform method
[
https://issues.apache.org/jira/browse/CAMEL-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-8871:
--
Assignee: Claus Ibsen
null body after exception from transform method
---
Key: CAMEL-8871
URL: https://issues.apache.org/jira/browse/CAMEL-8871
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.2
Reporter: Hans Orbaan
Assignee: Claus Ibsen
Priority: Minor
Fix For: 2.16.0, 2.15.3
Attachments: ExceptionToErrorRouteTest.java
When an exception is thrown from a transform method I lose the content of the
message body. This behaviour is unexpected because it does not happen when an
exception is thrown from a bean call.
.bean(ErrorBean.class, ErrorBean.METHOD)
Vs.
.transform().method(ErrorBean.class, ErrorBean.METHOD)
I have a testcase that I will try to get attached but here are the routes:
{code:java}
if (testTransformExceptionToErrorRoute.equals(getTestMethodName())) {
from(START)
.routeId(exception.test.transform)
.transform().method(ErrorBean.class, ErrorBean.METHOD)
.to(END);
} else {
from(START)
.routeId(exception.test.bean)
.bean(ErrorBean.class, ErrorBean.METHOD)
.to(END);
}
public static class ErrorBean {
private static final String METHOD = throwException;
public static void throwException(Exchange exchange) {
String body = exchange.getIn().getBody(String.class);
Assertions.assertThat(body).isEqualTo(BODY);
throw new NullPointerException();
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8841) camel:context-inflight returns 'Object name cannot be null'
[
https://issues.apache.org/jira/browse/CAMEL-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14585502#comment-14585502
]
Claus Ibsen commented on CAMEL-8841:
the context name is not required to be unique in the entire jvm and also end
users can configure an explict name such as myCamel etc. Where as management
name must be unique in the JVM. Therefore these 2 can differ.
camel:context-inflight returns 'Object name cannot be null'
---
Key: CAMEL-8841
URL: https://issues.apache.org/jira/browse/CAMEL-8841
Project: Camel
Issue Type: Bug
Components: karaf, tooling
Affects Versions: 2.15.1, 2.15.2
Environment: Karaf 3.0.3
Reporter: Martin Lichtin
Fix For: 2.16.0, 2.15.3
{noformat}
karaf camel:context-inflight myCamelContext
Error executing command: Object name cannot be null
karaf log:exception-display
javax.management.RuntimeOperationsException: Object name cannot be null
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:569)[:1.8.0_45]
at
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:638)[:1.8.0_45]
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
at
org.apache.karaf.management.boot.KarafMBeanServerBuilder$MBeanInvocationHandler.invoke(KarafMBeanServerBuilder.java:80)[karaf-jmx-boot.jar:]
at com.sun.proxy.$Proxy0.isRegistered(Unknown Source)[:]
at
org.apache.camel.commands.AbstractLocalCamelController.browseInflightExchanges(AbstractLocalCamelController.java:186)
at
org.apache.camel.commands.ContextInflightCommand.performContextCommand(ContextInflightCommand.java:56)
at
org.apache.camel.commands.AbstractContextCommand.executeLocal(AbstractContextCommand.java:74)
at
org.apache.camel.commands.AbstractContextCommand.execute(AbstractContextCommand.java:42)
at
org.apache.camel.karaf.commands.ContextInflight.doExecute(ContextInflight.java:40)
at
org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.3]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at Proxy199cb572_c6d4_4d06_851e_3f55b795651b.execute(Unknown
Source)[:]
at
org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[25:org.apache.karaf.shell.console:3.0.3]
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)
at
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:208)
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.runConsole(ShellFactoryImpl.java:158)[52:org.apache.karaf.shell.ssh:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1$1.run(ShellFactoryImpl.java:133)
at java.security.AccessController.doPrivileged(Native
Method)[:1.8.0_45]
at
org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:57)[26:org.apache.karaf.jaas.modules:3.0.3]
at
org.apache.karaf.shell.ssh.ShellFactoryImpl$ShellImpl$1.run(ShellFactoryImpl.java:129)[52:org.apache.karaf.shell.ssh:3.0.3]
Caused by: java.lang.IllegalArgumentException: Object name cannot be null
... 30 more
{noformat}
I think when combining the object name
SetObjectName set = mBeanServer.queryNames(new
ObjectName(agent.getMBeanObjectDomainName() +
:type=services,name=DefaultInflightRepository,*), null);
The :context=context-name part seems missing.
The query should be something like
org.apache.camel:context=context-name,type=services,name=DefaultInflightRepository
--
