question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error from the customized swagger API connector.

See original GitHub issue

Can you please please itake a look at this issue?? The swagger worked fine on the master on FEB.23, but now it does not work. I need to demo to a LARGE audience next week, this is a big event.

---------------------------------------------------------------------------------------------------------------------------------------
--
  | RouteId              ProcessorId          Processor                                                                        Elapsed (ms)
  | [i-L70Hbp3w6m_36vOl] [i-L70Hbp3w6m_36vOl] [sjms-sjms-1://queue:postwitter                                                ] [         4]
  | [i-L70Hbp3w6m_36vOl] [-L70HNDLioNdvYvlnZ] [Processor@0x352e5a82                                                          ] [         1]
  | [i-L70Hbp3w6m_36vOl] [-L70HYxNioNdvYvlnZ] [atlas:mapping-step-2.json?sourceMapName=Syndesis.CAPTURED_OUT_MESSAGES_MAP    ] [         1]
  | [i-L70Hbp3w6m_36vOl] [-L70HYxNioNdvYvlnZ] [Processor@0x2a4e939a                                                          ] [         0]
  | [i-L70Hbp3w6m_36vOl] [-L70HXdJioNdvYvlnZ] [swagger-operation-3?operationId=operation-0                                   ] [         1]
  | Stacktrace
  | ---------------------------------------------------------------------------------------------------------------------------------------
  | java.lang.IllegalArgumentException: Invalid uri: /hireinasia/tweetjob. If you are forwarding/bridging http endpoints, then enable the bridgeEndpoint option on the endpoint: http4://customizetwitter-fuseignite.52.230.124.252.nip.io/twitter/update
  | at org.apache.camel.component.http4.HttpProducer.createMethod(HttpProducer.java:476) ~[camel-http4-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.component.http4.HttpProducer.process(HttpProducer.java:113) ~[camel-http4-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) ~[camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.component.rest.RestProducer.process(RestProducer.java:86) ~[camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.Pipeline.process(Pipeline.java:138) [camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.Pipeline.process(Pipeline.java:101) [camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.component.connector.ConnectorProducer.process(ConnectorProducer.java:45) ~[camel-connector-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148) ~[camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.InterceptorToAsyncProcessorBridge.process(InterceptorToAsyncProcessorBridge.java:67) ~[camel-core-2.20.1.jar!/:2.20.1]
  | at io.syndesis.integration.runtime.logging.IntegrationLoggingInterceptStrategy.lambda$wrapProcessorInInterceptors$0(IntegrationLoggingInterceptStrategy.java:45) ~[integration-runtime-1.3-SNAPSHOT.jar!/:1.3-SNAPSHOT]
  | at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) ~[camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.InterceptorToAsyncProcessorBridge.process(InterceptorToAsyncProcessorBridge.java:76) ~[camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:110) ~[camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548) ~[camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201) [camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.Pipeline.process(Pipeline.java:138) [camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.Pipeline.process(Pipeline.java:101) [camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201) [camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.Pipeline.process(Pipeline.java:138) [camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.Pipeline.process(Pipeline.java:101) [camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:109) [camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.processor.Pipeline.process(Pipeline.java:80) [camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.component.sjms.consumer.InOnlyMessageHandler.handleMessage(InOnlyMessageHandler.java:65) [camel-sjms-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.component.sjms.consumer.AbstractMessageHandler.onMessage(AbstractMessageHandler.java:86) [camel-sjms-2.20.1.jar!/:2.20.1]
  | at org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1401) [activemq-client-5.14.5.jar!/:5.14.5]
  | at org.apache.activemq.ActiveMQMessageConsumer.iterate(ActiveMQMessageConsumer.java:1572) [activemq-client-5.14.5.jar!/:5.14.5]
  | at org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:191) [activemq-client-5.14.5.jar!/:5.14.5]
  | at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133) [activemq-client-5.14.5.jar!/:5.14.5]
  | at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48) [activemq-client-5.14.5.jar!/:5.14.5]
  | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151]
  | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151]
  | at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]
  | {"exchange":"i-L70K1Yy5BLj4VwAS8z_z","status":"done","failed":true}
  | 2018-03-07 16:38:35.523 ERROR 1 --- [ Session Task-3] o.a.activemq.ActiveMQMessageConsumer     : ID:i-twitterfeed-2-4qsz4-45950-1520440270154-1:1:1:1 Exception while processing message: ID:hireinasia-app-1-jr8sg-34417-1520438705171-1:2:1:1:1
  | org.apache.camel.RuntimeCamelException: java.lang.NullPointerException
  | at org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1831) ~[camel-core-2.20.1.jar!/:2.20.1]
  | at org.apache.camel.component.sjms.consumer.AbstractMessageHandler.onMessage(AbstractMessageHandler.java:113) ~[camel-sjms-2.20.1.jar!/:2.20.1]
  | at org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1401) [activemq-client-5.14.5.jar!/:5.14.5]
  | at org.apache.activemq.ActiveMQMessageConsumer.iterate(ActiveMQMessageConsumer.java:1572) [activemq-client-5.14.5.jar!/:5.14.5]
  | at org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:191) [activemq-client-5.14.5.jar!/:5.14.5]
  | at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133) [activemq-client-5.14.5.jar!/:5.14.5]
  | at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48) [activemq-client-5.14.5.jar!/:5.14.5]
  | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151]
  | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151]
  | at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]
  | Caused by: java.lang.NullPointerException: null
  | at org.apache.camel.component.sjms.consumer.AbstractMessageHandler.onMessage(AbstractMessageHandler.java:88) ~[camel-sjms-2.20.1.jar!/:2.20.1]
  | ... 8 common frames omitted

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:18 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
davsclauscommented, Mar 8, 2018

The logic of the code in camel-sjms and how you can get that NPE indicate its when you have configured synchronous=true on the sjms endpoint. Not sure if Syndesis connector does that somewhere. The NPE is fixed in next Camel release.

1reaction
davsclauscommented, Mar 8, 2018

Logged a ticket about the NPE in camel-sjms https://issues.apache.org/jira/browse/CAMEL-12335

Read more comments on GitHub >

github_iconTop Results From Across the Web

Mysterious error in custom connector appearing aft...
I went to go in an add another action to a custom connector I have. ... Specified swagger has the following errors: 'Definition...
Read more >
Create custom connector for own API
In this blog post you will learn how to set up a custom connector for a custom API hosted in Azure using Azure...
Read more >
Troubleshooting Power Apps Custom Connector Issues
If you've created your custom connector from an OpenAPI definition file (aka Swagger) or a Postman collection, one of the most common reasons...
Read more >
Swagger for Facebook Connector Has Errors #790 - GitHub
Go to Data--> Custom connections tab. Click on new custom connectors icon. ... Swagger for Facebook Connector Has Errors #790.
Read more >
Re: PowerBI Swagger found on Github causing issues...
Power BI + Power Automate API Connector I did not have issues. ... custom connector in the Admin portal, I receive the error...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found