[jira] [Updated] (CAMEL-7146) NPE in LevelDB component when aggregator completionSize = 1
[ https://issues.apache.org/jira/browse/CAMEL-7146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Burkard updated CAMEL-7146: -- Attachment: Camel-7146-stacktrace.txt The NPE stacktrace NPE in LevelDB component when aggregator completionSize = 1 --- Key: CAMEL-7146 URL: https://issues.apache.org/jira/browse/CAMEL-7146 Project: Camel Issue Type: Bug Components: camel-leveldb Affects Versions: 2.12.2 Reporter: Stefan Burkard Priority: Trivial Labels: aggregator Attachments: Camel-7146-stacktrace.txt A Camel aggregator with persistence repository of type LevelDB cannot have a completionSize of 1. If this is configured, every message produces a NPE with the attached stacktrace. I have also attached a small example project that shows the Exception. As soon as the completionSize is 1, it runs fine. This is just a minor flaw, since I cannot think about a really useful case with completionSize 1, but it technically works with other repository types. As an alternative (if completionSize 1 should not be used), Camel could throw an error during Context startup when completionSize 2. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CAMEL-7146) NPE in LevelDB component when aggregator completionSize = 1
Stefan Burkard created CAMEL-7146: - Summary: NPE in LevelDB component when aggregator completionSize = 1 Key: CAMEL-7146 URL: https://issues.apache.org/jira/browse/CAMEL-7146 Project: Camel Issue Type: Bug Components: camel-leveldb Affects Versions: 2.12.2 Reporter: Stefan Burkard Priority: Trivial Attachments: Camel-7146-stacktrace.txt A Camel aggregator with persistence repository of type LevelDB cannot have a completionSize of 1. If this is configured, every message produces a NPE with the attached stacktrace. I have also attached a small example project that shows the Exception. As soon as the completionSize is 1, it runs fine. This is just a minor flaw, since I cannot think about a really useful case with completionSize 1, but it technically works with other repository types. As an alternative (if completionSize 1 should not be used), Camel could throw an error during Context startup when completionSize 2. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CAMEL-7146) NPE in LevelDB component when aggregator completionSize = 1
[ https://issues.apache.org/jira/browse/CAMEL-7146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Burkard updated CAMEL-7146: -- Attachment: Camel-7146-example.tgz Example project that shows the behaviour with completionSize = 1 NPE in LevelDB component when aggregator completionSize = 1 --- Key: CAMEL-7146 URL: https://issues.apache.org/jira/browse/CAMEL-7146 Project: Camel Issue Type: Bug Components: camel-leveldb Affects Versions: 2.12.2 Reporter: Stefan Burkard Priority: Trivial Labels: aggregator Attachments: Camel-7146-example.tgz, Camel-7146-stacktrace.txt A Camel aggregator with persistence repository of type LevelDB cannot have a completionSize of 1. If this is configured, every message produces a NPE with the attached stacktrace. I have also attached a small example project that shows the Exception. As soon as the completionSize is 1, it runs fine. This is just a minor flaw, since I cannot think about a really useful case with completionSize 1, but it technically works with other repository types. As an alternative (if completionSize 1 should not be used), Camel could throw an error during Context startup when completionSize 2. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CAMEL-6836) Dead link to kotlin dsl page
[ https://issues.apache.org/jira/browse/CAMEL-6836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geert Schuring closed CAMEL-6836. - Dead link to kotlin dsl page Key: CAMEL-6836 URL: https://issues.apache.org/jira/browse/CAMEL-6836 Project: Camel Issue Type: Task Components: documentation Reporter: Geert Schuring Assignee: Claus Ibsen Priority: Trivial Labels: docuentation The link to kotlin on the DSL page is dead. Should probably be: https://github.com/koolio/kool/tree/master/kool-camel -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Deleted] (CAMEL-4421) Make Tracer tests simpler
[ https://issues.apache.org/jira/browse/CAMEL-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider deleted CAMEL-4421: --- Make Tracer tests simpler - Key: CAMEL-4421 URL: https://issues.apache.org/jira/browse/CAMEL-4421 Project: Camel Issue Type: Test Reporter: Christian Schneider Assignee: Christian Schneider Priority: Minor The current test around TracingTestBase are much too complicated. A test should be easy to understand and cleary communicate what it does and what results it expects. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CAMEL-6836) Dead link to kotlin dsl page
[ https://issues.apache.org/jira/browse/CAMEL-6836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13878422#comment-13878422 ] Geert Schuring commented on CAMEL-6836: --- Yep, works correctly now. Dead link to kotlin dsl page Key: CAMEL-6836 URL: https://issues.apache.org/jira/browse/CAMEL-6836 Project: Camel Issue Type: Task Components: documentation Reporter: Geert Schuring Assignee: Claus Ibsen Priority: Trivial Labels: docuentation The link to kotlin on the DSL page is dead. Should probably be: https://github.com/koolio/kool/tree/master/kool-camel -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Reopened] (CAMEL-7049) Cannot set JMSReplyTo with a topic destination when sending a message to a queue
[
https://issues.apache.org/jira/browse/CAMEL-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Lichtin reopened CAMEL-7049:
---
Unfortunately it doesn't seem to be fixed, at least not in 2.11.3.
I still see how it the 'normalization' switches from topic to queue:
JmsProducer | amel.component.jms.JmsProducer$2 328 | 126
- org.apache.camel.camel-jms - 2.11.3 | Normalized JMSReplyTo destination name
topic://xxx - xxx
JmsProducer | amel.component.jms.JmsProducer$2 344 | 126
- org.apache.camel.camel-jms - 2.11.3 | Creating JMSReplyTo queue: xxx
JmsProducer | amel.component.jms.JmsProducer$2 356 | 126
- org.apache.camel.camel-jms - 2.11.3 | Using JMSReplyTo destination:
queue://xxx
JmsProducer | amel.component.jms.JmsProducer$2 364 | 126
- org.apache.camel.camel-jms - 2.11.3 | Created javax.jms.Message:
ActiveMQMessage {commandId = 0, responseRequired = false, messageId = null,
originalDestination = null, originalTransactionId = null, producerId = null,
destination = null, transactionId = null, expiration = 0, timestamp = 0,
arrival = 0, brokerInTime = 0, brokerOutTime = 0, correlationId = null, replyTo
= queue://xxx, persistent = true, type = null, priority = 0, groupID = null,
groupSequence = 0, targetConsumerId = null, compressed = false, userID = null,
content = null, marshalledProperties = null, dataStructure = null,
redeliveryCounter = 0, size = 0, properties =
{breadcrumbId=ID-mlipc-54383-1390388987563-0-1, firedTime=Wed Jan 22 12:09:49
CET 2014}, readOnlyProperties = false, readOnlyBody = false, droppable = false}
Cannot set JMSReplyTo with a topic destination when sending a message to a
queue
Key: CAMEL-7049
URL: https://issues.apache.org/jira/browse/CAMEL-7049
Project: Camel
Issue Type: Bug
Components: camel-jms
Affects Versions: 2.11.1
Reporter: Martin Lichtin
Assignee: Claus Ibsen
Fix For: 2.11.3, 2.12.3, 2.13.0
The use case is about using Camel to communicate with the ActiveMQ
StatisticsPlugin:
Need to send a message and set 'JMSReplyTo' with a destination for the
response message(s). Doing this as part of a Camel processor:
in.setHeader(JMSReplyTo, topic://mydest);
This, however, results in the broker (ie. the statistics plugin) returning
messages to the mydest queue, as opposed to the topic.
The issue is that Camel starts fiddling with the 'JMSReplyTo' header.
Enabling trace level shows how Camel coerces the topic into a queue:
JmsProducer | amel.component.jms.JmsProducer$2 315 | 126 -
org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination name
topic://jmsqueuemonitor - jmsqueuemonitor
JmsProducer | amel.component.jms.JmsProducer$2 315 | 126 -
org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination name
topic://jmsqueuemonitor - jmsqueuemonitor
JmsProducer | amel.component.jms.JmsProducer$2 331 | 126 -
org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue:
jmsqueuemonitor
JmsProducer | amel.component.jms.JmsProducer$2 331 | 126 -
org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue:
jmsqueuemonitor
JmsProducer | amel.component.jms.JmsProducer$2 343 | 126 -
org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination:
queue://jmsqueuemonitor
JmsProducer | amel.component.jms.JmsProducer$2 343 | 126 -
org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination:
queue://jmsqueuemonitor
Camel seems to apply some logic that is faulty in this circumstance.
Just want to send a message to a queue and have that message carry a
'JMSReplyTo' value that should be left untouched.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Assigned] (CAMEL-6999) Camel component for dropbox integration
[ https://issues.apache.org/jira/browse/CAMEL-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned CAMEL-6999: Assignee: Bilgin Ibryam Camel component for dropbox integration --- Key: CAMEL-6999 URL: https://issues.apache.org/jira/browse/CAMEL-6999 Project: Camel Issue Type: New Feature Affects Versions: 2.12.1 Reporter: Giovanni Marigi Assignee: Bilgin Ibryam Priority: Minor Labels: camel, dropbox Fix For: Future Create a camel component (producers and consumers ) for dropbox integration -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CAMEL-7147) NullPointerException when chaining CXF/Jackson REST services in a Camel route
David van Balen created CAMEL-7147:
--
Summary: NullPointerException when chaining CXF/Jackson REST
services in a Camel route
Key: CAMEL-7147
URL: https://issues.apache.org/jira/browse/CAMEL-7147
Project: Camel
Issue Type: Bug
Components: camel-cxf, camel-jackson
Affects Versions: 2.12.0
Environment: Fuse ESB 6.1.0.alpha
Reporter: David van Balen
When chaining multiple REST service calls in a single camel route, using
Jackson as the JSON provider for CXF, the JacksonJsonProvider appears to lose
its thread local context between invocations, resulting in an NPE. The NPE
doesn't always occur at the same point. Sometimes one or both additional
services are successfully called before the thead local context disappears, but
other times neither service is called and an NPE is thrown as soon as the
initial service is invoked.
See attached zip archive for reproducer.
See camel-users thread for background:
http://camel.465427.n5.nabble.com/Questions-about-cxfrs-td5746294.html
Lib versions:
Camel: 2.12.0
Jackson: 1.9.10
CXF: 2.7.0
Full stacktrace:
11:40:51,678 | INFO | tp1806392083-718 | LoggingInInterceptor |
150 - org.apache.cxf.cxf-api - 2.7.0.redhat-610139 | Inbound Message
ID: 15
Address: http://localhost:8182/service1/service1path
Encoding: ISO-8859-1
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[*/*], accept-encoding=[gzip,deflate,sdch],
Accept-Language=[en-US,en;q=0.8], connection=[keep-alive], Content-Length=[23],
content-type=[application/json], Host=[localhost:8182],
Origin=[chrome-extension://fhjcajmcbmldlhcimfajhfbgofnpcjmb],
User-Agent=[Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/31.0.1650.63 Safari/537.36]}
Payload: {id:1,name:Fred}
--
11:40:51,679 | WARN | tp1806392083-718 | PhaseInterceptorChain|
150 - org.apache.cxf.cxf-api - 2.7.0.redhat-610139 | Interceptor for
{http://jackson.blueprint.camel.mycompany.com/}ServiceOne has thrown exception,
unwinding now
java.lang.NullPointerException
at
org.apache.cxf.jaxrs.impl.tl.ThreadLocalProviders.getContextResolver(ThreadLocalProviders.java:50)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.codehaus.jackson.jaxrs.JacksonJsonProvider.locateMapper(JacksonJsonProvider.java:633)[245:jackson-jaxrs:1.9.10]
at
org.codehaus.jackson.jaxrs.JacksonJsonProvider.readFrom(JacksonJsonProvider.java:413)[245:jackson-jaxrs:1.9.10]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBodyReader(JAXRSUtils.java:1280)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBody(JAXRSUtils.java:1231)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(JAXRSUtils.java:782)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:741)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:263)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:103)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)[150:org.apache.cxf.cxf-api:2.7.0.redhat-610139]
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)[150:org.apache.cxf.cxf-api:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:355)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:319)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:72)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1077)[93:org.eclipse.jetty.aggregate.jetty-all-server:8.1.9.v20130131]
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1013)[93:org.eclipse.jetty.aggregate.jetty-all-server:8.1.9.v20130131]
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)[93:org.eclipse.jetty.aggregate.jetty-all-server:8.1.9.v20130131]
at
[jira] [Updated] (CAMEL-7147) NullPointerException when chaining CXF/Jackson REST services in a Camel route
[
https://issues.apache.org/jira/browse/CAMEL-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David van Balen updated CAMEL-7147:
---
Attachment: CAMEL-7147.zip
Reproducer project, contains a camel route project (camel-blueprint-jackson), a
project with shared class (model), and two additional REST services to be
called by the camel route (service2 and service3).
NullPointerException when chaining CXF/Jackson REST services in a Camel route
-
Key: CAMEL-7147
URL: https://issues.apache.org/jira/browse/CAMEL-7147
Project: Camel
Issue Type: Bug
Components: camel-cxf, camel-jackson
Affects Versions: 2.12.0
Environment: Fuse ESB 6.1.0.alpha
Reporter: David van Balen
Labels: cxf, cxfrs, json, threadlocal
Attachments: CAMEL-7147.zip
When chaining multiple REST service calls in a single camel route, using
Jackson as the JSON provider for CXF, the JacksonJsonProvider appears to lose
its thread local context between invocations, resulting in an NPE. The NPE
doesn't always occur at the same point. Sometimes one or both additional
services are successfully called before the thead local context disappears,
but other times neither service is called and an NPE is thrown as soon as the
initial service is invoked.
See attached zip archive for reproducer (service2 and service3 are deployed
on JBoss AS 7.3.0).
See camel-users thread for background:
http://camel.465427.n5.nabble.com/Questions-about-cxfrs-td5746294.html
Lib versions:
Camel: 2.12.0
Jackson: 1.9.10
CXF: 2.7.0
Full stacktrace:
11:40:51,678 | INFO | tp1806392083-718 | LoggingInInterceptor |
150 - org.apache.cxf.cxf-api - 2.7.0.redhat-610139 | Inbound Message
ID: 15
Address: http://localhost:8182/service1/service1path
Encoding: ISO-8859-1
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[*/*], accept-encoding=[gzip,deflate,sdch],
Accept-Language=[en-US,en;q=0.8], connection=[keep-alive],
Content-Length=[23], content-type=[application/json], Host=[localhost:8182],
Origin=[chrome-extension://fhjcajmcbmldlhcimfajhfbgofnpcjmb],
User-Agent=[Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/31.0.1650.63 Safari/537.36]}
Payload: {id:1,name:Fred}
--
11:40:51,679 | WARN | tp1806392083-718 | PhaseInterceptorChain|
150 - org.apache.cxf.cxf-api - 2.7.0.redhat-610139 | Interceptor for
{http://jackson.blueprint.camel.mycompany.com/}ServiceOne has thrown
exception, unwinding now
java.lang.NullPointerException
at
org.apache.cxf.jaxrs.impl.tl.ThreadLocalProviders.getContextResolver(ThreadLocalProviders.java:50)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.codehaus.jackson.jaxrs.JacksonJsonProvider.locateMapper(JacksonJsonProvider.java:633)[245:jackson-jaxrs:1.9.10]
at
org.codehaus.jackson.jaxrs.JacksonJsonProvider.readFrom(JacksonJsonProvider.java:413)[245:jackson-jaxrs:1.9.10]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBodyReader(JAXRSUtils.java:1280)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBody(JAXRSUtils.java:1231)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(JAXRSUtils.java:782)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:741)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:263)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:103)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)[150:org.apache.cxf.cxf-api:2.7.0.redhat-610139]
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)[150:org.apache.cxf.cxf-api:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:355)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:319)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
[jira] [Updated] (CAMEL-7147) NullPointerException when chaining CXF/Jackson REST services in a Camel route
[
https://issues.apache.org/jira/browse/CAMEL-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David van Balen updated CAMEL-7147:
---
Attachment: (was: CAMEL-7147.zip)
NullPointerException when chaining CXF/Jackson REST services in a Camel route
-
Key: CAMEL-7147
URL: https://issues.apache.org/jira/browse/CAMEL-7147
Project: Camel
Issue Type: Bug
Components: camel-cxf, camel-jackson
Affects Versions: 2.12.0
Environment: Fuse ESB 6.1.0.alpha
Reporter: David van Balen
Labels: cxf, cxfrs, json, threadlocal
When chaining multiple REST service calls in a single camel route, using
Jackson as the JSON provider for CXF, the JacksonJsonProvider appears to lose
its thread local context between invocations, resulting in an NPE. The NPE
doesn't always occur at the same point. Sometimes one or both additional
services are successfully called before the thead local context disappears,
but other times neither service is called and an NPE is thrown as soon as the
initial service is invoked.
See attached zip archive for reproducer (service2 and service3 are deployed
on JBoss AS 7.3.0).
See camel-users thread for background:
http://camel.465427.n5.nabble.com/Questions-about-cxfrs-td5746294.html
Lib versions:
Camel: 2.12.0
Jackson: 1.9.10
CXF: 2.7.0
Full stacktrace:
11:40:51,678 | INFO | tp1806392083-718 | LoggingInInterceptor |
150 - org.apache.cxf.cxf-api - 2.7.0.redhat-610139 | Inbound Message
ID: 15
Address: http://localhost:8182/service1/service1path
Encoding: ISO-8859-1
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[*/*], accept-encoding=[gzip,deflate,sdch],
Accept-Language=[en-US,en;q=0.8], connection=[keep-alive],
Content-Length=[23], content-type=[application/json], Host=[localhost:8182],
Origin=[chrome-extension://fhjcajmcbmldlhcimfajhfbgofnpcjmb],
User-Agent=[Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/31.0.1650.63 Safari/537.36]}
Payload: {id:1,name:Fred}
--
11:40:51,679 | WARN | tp1806392083-718 | PhaseInterceptorChain|
150 - org.apache.cxf.cxf-api - 2.7.0.redhat-610139 | Interceptor for
{http://jackson.blueprint.camel.mycompany.com/}ServiceOne has thrown
exception, unwinding now
java.lang.NullPointerException
at
org.apache.cxf.jaxrs.impl.tl.ThreadLocalProviders.getContextResolver(ThreadLocalProviders.java:50)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.codehaus.jackson.jaxrs.JacksonJsonProvider.locateMapper(JacksonJsonProvider.java:633)[245:jackson-jaxrs:1.9.10]
at
org.codehaus.jackson.jaxrs.JacksonJsonProvider.readFrom(JacksonJsonProvider.java:413)[245:jackson-jaxrs:1.9.10]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBodyReader(JAXRSUtils.java:1280)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBody(JAXRSUtils.java:1231)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(JAXRSUtils.java:782)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:741)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:263)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:103)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)[150:org.apache.cxf.cxf-api:2.7.0.redhat-610139]
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)[150:org.apache.cxf.cxf-api:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:355)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:319)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:72)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1077)[93:org.eclipse.jetty.aggregate.jetty-all-server:8.1.9.v20130131]
at
[jira] [Updated] (CAMEL-7147) NullPointerException when chaining CXF/Jackson REST services in a Camel route
[
https://issues.apache.org/jira/browse/CAMEL-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David van Balen updated CAMEL-7147:
---
Attachment: CAMEL-7147.zip
Fixed logging issue in service3
NullPointerException when chaining CXF/Jackson REST services in a Camel route
-
Key: CAMEL-7147
URL: https://issues.apache.org/jira/browse/CAMEL-7147
Project: Camel
Issue Type: Bug
Components: camel-cxf, camel-jackson
Affects Versions: 2.12.0
Environment: Fuse ESB 6.1.0.alpha
Reporter: David van Balen
Labels: cxf, cxfrs, json, threadlocal
Attachments: CAMEL-7147.zip
When chaining multiple REST service calls in a single camel route, using
Jackson as the JSON provider for CXF, the JacksonJsonProvider appears to lose
its thread local context between invocations, resulting in an NPE. The NPE
doesn't always occur at the same point. Sometimes one or both additional
services are successfully called before the thead local context disappears,
but other times neither service is called and an NPE is thrown as soon as the
initial service is invoked.
See attached zip archive for reproducer (service2 and service3 are deployed
on JBoss AS 7.3.0).
See camel-users thread for background:
http://camel.465427.n5.nabble.com/Questions-about-cxfrs-td5746294.html
Lib versions:
Camel: 2.12.0
Jackson: 1.9.10
CXF: 2.7.0
Full stacktrace:
11:40:51,678 | INFO | tp1806392083-718 | LoggingInInterceptor |
150 - org.apache.cxf.cxf-api - 2.7.0.redhat-610139 | Inbound Message
ID: 15
Address: http://localhost:8182/service1/service1path
Encoding: ISO-8859-1
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[*/*], accept-encoding=[gzip,deflate,sdch],
Accept-Language=[en-US,en;q=0.8], connection=[keep-alive],
Content-Length=[23], content-type=[application/json], Host=[localhost:8182],
Origin=[chrome-extension://fhjcajmcbmldlhcimfajhfbgofnpcjmb],
User-Agent=[Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/31.0.1650.63 Safari/537.36]}
Payload: {id:1,name:Fred}
--
11:40:51,679 | WARN | tp1806392083-718 | PhaseInterceptorChain|
150 - org.apache.cxf.cxf-api - 2.7.0.redhat-610139 | Interceptor for
{http://jackson.blueprint.camel.mycompany.com/}ServiceOne has thrown
exception, unwinding now
java.lang.NullPointerException
at
org.apache.cxf.jaxrs.impl.tl.ThreadLocalProviders.getContextResolver(ThreadLocalProviders.java:50)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.codehaus.jackson.jaxrs.JacksonJsonProvider.locateMapper(JacksonJsonProvider.java:633)[245:jackson-jaxrs:1.9.10]
at
org.codehaus.jackson.jaxrs.JacksonJsonProvider.readFrom(JacksonJsonProvider.java:413)[245:jackson-jaxrs:1.9.10]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBodyReader(JAXRSUtils.java:1280)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBody(JAXRSUtils.java:1231)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(JAXRSUtils.java:782)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:741)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:263)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:103)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)[150:org.apache.cxf.cxf-api:2.7.0.redhat-610139]
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)[150:org.apache.cxf.cxf-api:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:355)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:319)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:72)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
[jira] [Updated] (CAMEL-7049) Cannot set JMSReplyTo with a topic destination when sending a message to a queue
[ https://issues.apache.org/jira/browse/CAMEL-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated CAMEL-7049: Fix Version/s: (was: 2.11.3) 2.11.4 Cannot set JMSReplyTo with a topic destination when sending a message to a queue Key: CAMEL-7049 URL: https://issues.apache.org/jira/browse/CAMEL-7049 Project: Camel Issue Type: Bug Components: camel-jms Affects Versions: 2.11.1 Reporter: Martin Lichtin Assignee: Claus Ibsen Fix For: 2.11.4, 2.12.3, 2.13.0 The use case is about using Camel to communicate with the ActiveMQ StatisticsPlugin: Need to send a message and set 'JMSReplyTo' with a destination for the response message(s). Doing this as part of a Camel processor: in.setHeader(JMSReplyTo, topic://mydest); This, however, results in the broker (ie. the statistics plugin) returning messages to the mydest queue, as opposed to the topic. The issue is that Camel starts fiddling with the 'JMSReplyTo' header. Enabling trace level shows how Camel coerces the topic into a queue: JmsProducer | amel.component.jms.JmsProducer$2 315 | 126 - org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination name topic://jmsqueuemonitor - jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 315 | 126 - org.apache.camel.camel-jms - 2.11.1 | Normalized JMSReplyTo destination name topic://jmsqueuemonitor - jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 331 | 126 - org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue: jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 331 | 126 - org.apache.camel.camel-jms - 2.11.1 | Creating JMSReplyTo queue: jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 343 | 126 - org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination: queue://jmsqueuemonitor JmsProducer | amel.component.jms.JmsProducer$2 343 | 126 - org.apache.camel.camel-jms - 2.11.1 | Using JMSReplyTo destination: queue://jmsqueuemonitor Camel seems to apply some logic that is faulty in this circumstance. Just want to send a message to a queue and have that message carry a 'JMSReplyTo' value that should be left untouched. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CAMEL-7147) NullPointerException when chaining CXF/Jackson REST services in a Camel route
[
https://issues.apache.org/jira/browse/CAMEL-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13879196#comment-13879196
]
David van Balen commented on CAMEL-7147:
Update:
Looks like, on the first invocation, all three services are called and the NPE
occurs when the entry-point service is sending its response. Upon subsequent
invocations, there is an immediate NPE during invocation of the entry-point
service.
NullPointerException when chaining CXF/Jackson REST services in a Camel route
-
Key: CAMEL-7147
URL: https://issues.apache.org/jira/browse/CAMEL-7147
Project: Camel
Issue Type: Bug
Components: camel-cxf, camel-jackson
Affects Versions: 2.12.0
Environment: Fuse ESB 6.1.0.alpha
Reporter: David van Balen
Labels: cxf, cxfrs, json, threadlocal
Attachments: CAMEL-7147.zip
When chaining multiple REST service calls in a single camel route, using
Jackson as the JSON provider for CXF, the JacksonJsonProvider appears to lose
its thread local context between invocations, resulting in an NPE. The NPE
doesn't always occur at the same point. Sometimes one or both additional
services are successfully called before the thead local context disappears,
but other times neither service is called and an NPE is thrown as soon as the
initial service is invoked.
See attached zip archive for reproducer (service2 and service3 are deployed
on JBoss AS 7.3.0).
See camel-users thread for background:
http://camel.465427.n5.nabble.com/Questions-about-cxfrs-td5746294.html
Lib versions:
Camel: 2.12.0
Jackson: 1.9.10
CXF: 2.7.0
Full stacktrace:
11:40:51,678 | INFO | tp1806392083-718 | LoggingInInterceptor |
150 - org.apache.cxf.cxf-api - 2.7.0.redhat-610139 | Inbound Message
ID: 15
Address: http://localhost:8182/service1/service1path
Encoding: ISO-8859-1
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[*/*], accept-encoding=[gzip,deflate,sdch],
Accept-Language=[en-US,en;q=0.8], connection=[keep-alive],
Content-Length=[23], content-type=[application/json], Host=[localhost:8182],
Origin=[chrome-extension://fhjcajmcbmldlhcimfajhfbgofnpcjmb],
User-Agent=[Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/31.0.1650.63 Safari/537.36]}
Payload: {id:1,name:Fred}
--
11:40:51,679 | WARN | tp1806392083-718 | PhaseInterceptorChain|
150 - org.apache.cxf.cxf-api - 2.7.0.redhat-610139 | Interceptor for
{http://jackson.blueprint.camel.mycompany.com/}ServiceOne has thrown
exception, unwinding now
java.lang.NullPointerException
at
org.apache.cxf.jaxrs.impl.tl.ThreadLocalProviders.getContextResolver(ThreadLocalProviders.java:50)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.codehaus.jackson.jaxrs.JacksonJsonProvider.locateMapper(JacksonJsonProvider.java:633)[245:jackson-jaxrs:1.9.10]
at
org.codehaus.jackson.jaxrs.JacksonJsonProvider.readFrom(JacksonJsonProvider.java:413)[245:jackson-jaxrs:1.9.10]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBodyReader(JAXRSUtils.java:1280)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBody(JAXRSUtils.java:1231)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameter(JAXRSUtils.java:782)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:741)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:263)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:103)[166:org.apache.cxf.cxf-rt-frontend-jaxrs:2.7.0.redhat-610139]
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)[150:org.apache.cxf.cxf-api:2.7.0.redhat-610139]
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)[150:org.apache.cxf.cxf-api:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:355)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:319)[176:org.apache.cxf.cxf-rt-transports-http-jetty:2.7.0.redhat-610139]
at
