subject:"Error occurred during starting Camel because of cannot look up a processor from registry"

Re: Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-08 Thread Debraj Manna

For me I am able to get around this by removing  myTemplate from
jsonRPCProcesor and fileUploadProcessor. Now my jsonRPCProcessor look
something like below:-


  



  
  


 and annotated the ProducerTemplate in my code with @EndPointInject

@EndpointInject

protected ProducerTemplate myTemplate;

On Fri, Jul 8, 2016 at 12:24 PM, Tadayoshi Sato 
wrote:

> Hmm, this just works for me. Note "productHelper" also has the cyclic
> dependency.
>
> On Wed, Jul 6, 2016 at 5:56 PM, Debraj Manna 
> wrote:
>
> > No it is not working.
> >
> > I think the issue is not because of the separate xml files. It is because
> > jsonRPCProcessor is using myTemplate and myTemplate is defined in
> > camelContext and camelContext is using jsonRPCProcessor in routes.
> >
> > On Wed, Jul 6, 2016 at 2:16 PM, Tadayoshi Sato  >
> > wrote:
> >
> > > No, in the same camelContext.xml file but outside of .
> > > Doesn't that work for you?
> > >
> > > On Wed, Jul 6, 2016 at 5:34 PM, Debraj Manna  >
> > > wrote:
> > >
> > > > Are you saying  to define jsonRPCProcessor inside camelContext.
> > Something
> > > > like below:-
> > > >
> > > > http://camel.apache.org/schema/blueprint";
> > > > useMDCLogging="true">
> > > > 
> > > > * > > >
> > > >
> > >
> >
> class="com.j1.orchestratorservice.basecomponent.processor.JSONRPCProcessor">*
> > > > *...*
> > > > **
> > > >
> > > > 
> > > > http://0.0.0.0:/orchestratorservice
> "
> > />
> > > > 
> > > > 
> > > > 
> > > >  > > > uri="jetty:
> > > > http://0.0.0.0:8889/fileuploadservice?enableMultipartFilter=true"; />
> > > > 
> > > > 
> > > > ...
> > > > 
> > > >
> > > > On Wed, Jul 6, 2016 at 7:00 AM, Tadayoshi Sato <
> > sato.tadayo...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Hi Debraj,
> > > > >
> > > > > Then why can you not define jsonRPCProcessor in camelContext.xml
> > > instead
> > > > of
> > > > > blueprint.xml?  If this processor depends on a specific producer
> > > template
> > > > > ("myTemplate") == Camel context, then I see no reasons this
> producer
> > > can
> > > > be
> > > > > shared across multiple Camel contexts.
> > > > >
> > > > > On Tue, Jul 5, 2016 at 8:01 PM, Debraj Manna <
> > subharaj.ma...@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > Yeah Tadayoshi. jsonRPCProcessor is using myTemplate as shown
> > below:-
> > > > > >
> > > > > >  > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> class="com.j1.orchestratorservice.basecomponent.processor.JSONRPCProcessor">
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > >  > > > > > value-ref="createProductsWFInfo" />
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > >
> > > > > >
> > > > > > whereas myTemplate is defined in camelContext which in turn is
> > using
> > > > > > jsonRPCProcessor as shown below:-
> > > > > >
> > > > > > http://camel.apache.org/schema/blueprint";
> > > > > > useMDCLogging="true">
> > > > > > 
> > > > > > 
> > > > > > http://0.0.0.0:/orchestratorservice
> > > "
> > > > />
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > >  > > > > >
> > > > > > uri="jetty:
> > > > > > http://0.0.0.0:8889/fileuploadservice?enableMultipartFilter=true
> "
> > > > > > />
> > > > > > 
> > > > > > 
> > > > > > ...
> > > > > > 
> > > > > >
> > > > > >
> > > > > > I have tried to set the producer in my custom jsonRPCProcessor as
> > > > > mentioned
> > > > > > in this link
> > > > > > <
> > > > > >
> > > > >
> > > >
> > >
> >
> http://camel.apache.org/how-do-i-write-a-custom-processor-which-sends-multiple-messages.html
> > > > > > >.
> > > > > > Can someone suggest me some other way of setting the producer in
> my
> > > > > custom
> > > > > > jsonRPCProcessor so that it does not lead to any circular
> > dependency?
> > > > > >
> > > > > > On Tue, Jul 5, 2016 at 8:21 AM, Tadayoshi Sato <
> > > > sato.tadayo...@gmail.com
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > It looks like 'myTemplate' is defined in camelContext.xml, but
> > the
> > > > > Camel
> > > > > > > context then refers to 'jsonRPCProcessor' in blueprint.xml,
> which
> > > in
> > > > > > turns
> > > > > > > refers to 'myTemplate'. That should be the cyclic dependency in
> > > > > question.
> > > > > > >
> > > > > > > Hope this helps,
> > > > > > >
> > > > > > > Tadayoshi
> > > > > > >
> > > > > > > On Mon, Jul 4, 2016 at 10:27 PM, Debraj Manna <
> > > > > subharaj.ma...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > It seems the error is getting triggered because of some
> cyclic
> > > > > > > dependency.
> > > > > > > > But I am not able to figure out from the trace what is
> causing
> > > the
> > > > > > cyclic
> > > > > > > > dependency.
> > > >

Re: Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-07 Thread Tadayoshi Sato

Hmm, this just works for me. Note "productHelper" also has the cyclic
dependency.

On Wed, Jul 6, 2016 at 5:56 PM, Debraj Manna 
wrote:

> No it is not working.
>
> I think the issue is not because of the separate xml files. It is because
> jsonRPCProcessor is using myTemplate and myTemplate is defined in
> camelContext and camelContext is using jsonRPCProcessor in routes.
>
> On Wed, Jul 6, 2016 at 2:16 PM, Tadayoshi Sato 
> wrote:
>
> > No, in the same camelContext.xml file but outside of .
> > Doesn't that work for you?
> >
> > On Wed, Jul 6, 2016 at 5:34 PM, Debraj Manna 
> > wrote:
> >
> > > Are you saying  to define jsonRPCProcessor inside camelContext.
> Something
> > > like below:-
> > >
> > > http://camel.apache.org/schema/blueprint";
> > > useMDCLogging="true">
> > > 
> > > * > >
> > >
> >
> class="com.j1.orchestratorservice.basecomponent.processor.JSONRPCProcessor">*
> > > *...*
> > > **
> > >
> > > 
> > > http://0.0.0.0:/orchestratorservice";
> />
> > > 
> > > 
> > > 
> > >  > > uri="jetty:
> > > http://0.0.0.0:8889/fileuploadservice?enableMultipartFilter=true"; />
> > > 
> > > 
> > > ...
> > > 
> > >
> > > On Wed, Jul 6, 2016 at 7:00 AM, Tadayoshi Sato <
> sato.tadayo...@gmail.com
> > >
> > > wrote:
> > >
> > > > Hi Debraj,
> > > >
> > > > Then why can you not define jsonRPCProcessor in camelContext.xml
> > instead
> > > of
> > > > blueprint.xml?  If this processor depends on a specific producer
> > template
> > > > ("myTemplate") == Camel context, then I see no reasons this producer
> > can
> > > be
> > > > shared across multiple Camel contexts.
> > > >
> > > > On Tue, Jul 5, 2016 at 8:01 PM, Debraj Manna <
> subharaj.ma...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > Yeah Tadayoshi. jsonRPCProcessor is using myTemplate as shown
> below:-
> > > > >
> > > > >  > > > >
> > > > >
> > > >
> > >
> >
> class="com.j1.orchestratorservice.basecomponent.processor.JSONRPCProcessor">
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > >  > > > > value-ref="createProductsWFInfo" />
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > >
> > > > >
> > > > > whereas myTemplate is defined in camelContext which in turn is
> using
> > > > > jsonRPCProcessor as shown below:-
> > > > >
> > > > > http://camel.apache.org/schema/blueprint";
> > > > > useMDCLogging="true">
> > > > > 
> > > > > 
> > > > > http://0.0.0.0:/orchestratorservice
> > "
> > > />
> > > > > 
> > > > > 
> > > > > 
> > > > >  > > > >
> > > > > uri="jetty:
> > > > > http://0.0.0.0:8889/fileuploadservice?enableMultipartFilter=true";
> > > > > />
> > > > > 
> > > > > 
> > > > > ...
> > > > > 
> > > > >
> > > > >
> > > > > I have tried to set the producer in my custom jsonRPCProcessor as
> > > > mentioned
> > > > > in this link
> > > > > <
> > > > >
> > > >
> > >
> >
> http://camel.apache.org/how-do-i-write-a-custom-processor-which-sends-multiple-messages.html
> > > > > >.
> > > > > Can someone suggest me some other way of setting the producer in my
> > > > custom
> > > > > jsonRPCProcessor so that it does not lead to any circular
> dependency?
> > > > >
> > > > > On Tue, Jul 5, 2016 at 8:21 AM, Tadayoshi Sato <
> > > sato.tadayo...@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > It looks like 'myTemplate' is defined in camelContext.xml, but
> the
> > > > Camel
> > > > > > context then refers to 'jsonRPCProcessor' in blueprint.xml, which
> > in
> > > > > turns
> > > > > > refers to 'myTemplate'. That should be the cyclic dependency in
> > > > question.
> > > > > >
> > > > > > Hope this helps,
> > > > > >
> > > > > > Tadayoshi
> > > > > >
> > > > > > On Mon, Jul 4, 2016 at 10:27 PM, Debraj Manna <
> > > > subharaj.ma...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > It seems the error is getting triggered because of some cyclic
> > > > > > dependency.
> > > > > > > But I am not able to figure out from the trace what is causing
> > the
> > > > > cyclic
> > > > > > > dependency.
> > > > > > >
> > > > > > > On Jul 4, 2016 4:22 PM, "Debraj Manna" <
> subharaj.ma...@gmail.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > On placing a bundle (using camel) on Karaf I am seeing the
> > below
> > > > > > > > exception. The below exception comes only when the bundle is
> > > > started.
> > > > > > > After
> > > > > > > > that everything works fine. The exeception does not seem to
> > > effect
> > > > > our
> > > > > > > > functionality. The issue is coming on both camel 2.16.1
> > (deployed
> > > > on
> > > > > > > servicemix
> > > > > > > > 6.1.0) and camel 2.16.3 (deployed on servicemix 7.0.0M2).
> > > > > > > >
> > > > > > > > My blueprint is split into three files. A simplified

Re: Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-06 Thread Debraj Manna

No it is not working.

I think the issue is not because of the separate xml files. It is because
jsonRPCProcessor is using myTemplate and myTemplate is defined in
camelContext and camelContext is using jsonRPCProcessor in routes.

On Wed, Jul 6, 2016 at 2:16 PM, Tadayoshi Sato 
wrote:

> No, in the same camelContext.xml file but outside of .
> Doesn't that work for you?
>
> On Wed, Jul 6, 2016 at 5:34 PM, Debraj Manna 
> wrote:
>
> > Are you saying  to define jsonRPCProcessor inside camelContext. Something
> > like below:-
> >
> > http://camel.apache.org/schema/blueprint";
> > useMDCLogging="true">
> > 
> > * >
> >
> class="com.j1.orchestratorservice.basecomponent.processor.JSONRPCProcessor">*
> > *...*
> > **
> >
> > 
> > http://0.0.0.0:/orchestratorservice"; />
> > 
> > 
> > 
> >  > uri="jetty:
> > http://0.0.0.0:8889/fileuploadservice?enableMultipartFilter=true"; />
> > 
> > 
> > ...
> > 
> >
> > On Wed, Jul 6, 2016 at 7:00 AM, Tadayoshi Sato  >
> > wrote:
> >
> > > Hi Debraj,
> > >
> > > Then why can you not define jsonRPCProcessor in camelContext.xml
> instead
> > of
> > > blueprint.xml?  If this processor depends on a specific producer
> template
> > > ("myTemplate") == Camel context, then I see no reasons this producer
> can
> > be
> > > shared across multiple Camel contexts.
> > >
> > > On Tue, Jul 5, 2016 at 8:01 PM, Debraj Manna  >
> > > wrote:
> > >
> > > > Yeah Tadayoshi. jsonRPCProcessor is using myTemplate as shown below:-
> > > >
> > > >  > > >
> > > >
> > >
> >
> class="com.j1.orchestratorservice.basecomponent.processor.JSONRPCProcessor">
> > > > 
> > > > 
> > > > 
> > > > 
> > > >  > > > value-ref="createProductsWFInfo" />
> > > > 
> > > > 
> > > > 
> > > > 
> > > >
> > > >
> > > > whereas myTemplate is defined in camelContext which in turn is using
> > > > jsonRPCProcessor as shown below:-
> > > >
> > > > http://camel.apache.org/schema/blueprint";
> > > > useMDCLogging="true">
> > > > 
> > > > 
> > > > http://0.0.0.0:/orchestratorservice
> "
> > />
> > > > 
> > > > 
> > > > 
> > > >  > > >
> > > > uri="jetty:
> > > > http://0.0.0.0:8889/fileuploadservice?enableMultipartFilter=true";
> > > > />
> > > > 
> > > > 
> > > > ...
> > > > 
> > > >
> > > >
> > > > I have tried to set the producer in my custom jsonRPCProcessor as
> > > mentioned
> > > > in this link
> > > > <
> > > >
> > >
> >
> http://camel.apache.org/how-do-i-write-a-custom-processor-which-sends-multiple-messages.html
> > > > >.
> > > > Can someone suggest me some other way of setting the producer in my
> > > custom
> > > > jsonRPCProcessor so that it does not lead to any circular dependency?
> > > >
> > > > On Tue, Jul 5, 2016 at 8:21 AM, Tadayoshi Sato <
> > sato.tadayo...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > It looks like 'myTemplate' is defined in camelContext.xml, but the
> > > Camel
> > > > > context then refers to 'jsonRPCProcessor' in blueprint.xml, which
> in
> > > > turns
> > > > > refers to 'myTemplate'. That should be the cyclic dependency in
> > > question.
> > > > >
> > > > > Hope this helps,
> > > > >
> > > > > Tadayoshi
> > > > >
> > > > > On Mon, Jul 4, 2016 at 10:27 PM, Debraj Manna <
> > > subharaj.ma...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > It seems the error is getting triggered because of some cyclic
> > > > > dependency.
> > > > > > But I am not able to figure out from the trace what is causing
> the
> > > > cyclic
> > > > > > dependency.
> > > > > >
> > > > > > On Jul 4, 2016 4:22 PM, "Debraj Manna"  >
> > > > wrote:
> > > > > >
> > > > > > > On placing a bundle (using camel) on Karaf I am seeing the
> below
> > > > > > > exception. The below exception comes only when the bundle is
> > > started.
> > > > > > After
> > > > > > > that everything works fine. The exeception does not seem to
> > effect
> > > > our
> > > > > > > functionality. The issue is coming on both camel 2.16.1
> (deployed
> > > on
> > > > > > servicemix
> > > > > > > 6.1.0) and camel 2.16.3 (deployed on servicemix 7.0.0M2).
> > > > > > >
> > > > > > > My blueprint is split into three files. A simplified version of
> > > them
> > > > > are
> > > > > > > shown below:-
> > > > > > >
> > > > > > >
> > > > > > >1. blueprint.xml placed here
> > > > > > ><
> > > > > >
> > > https://gist.github.com/debraj-manna/42294561b9da22ce2281e6a9f3b22a34>
> > > > > > >.
> > > > > > >2. productBeans.xml placed here
> > > > > > ><
> > > > > >
> > > https://gist.github.com/debraj-manna/5c406f597f8b7248369b206ed1f93842>
> > > > > > >.
> > > > > > >3. camelContext.xml placed here
> > > > > > ><
> > > > > >
> > > https://gist.github.com/debraj-manna/4210653d661

Re: Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-06 Thread Tadayoshi Sato

No, in the same camelContext.xml file but outside of .
Doesn't that work for you?

On Wed, Jul 6, 2016 at 5:34 PM, Debraj Manna 
wrote:

> Are you saying  to define jsonRPCProcessor inside camelContext. Something
> like below:-
>
> http://camel.apache.org/schema/blueprint";
> useMDCLogging="true">
> 
> *
> class="com.j1.orchestratorservice.basecomponent.processor.JSONRPCProcessor">*
> *...*
> **
>
> 
> http://0.0.0.0:/orchestratorservice"; />
> 
> 
> 
>  uri="jetty:
> http://0.0.0.0:8889/fileuploadservice?enableMultipartFilter=true"; />
> 
> 
> ...
> 
>
> On Wed, Jul 6, 2016 at 7:00 AM, Tadayoshi Sato 
> wrote:
>
> > Hi Debraj,
> >
> > Then why can you not define jsonRPCProcessor in camelContext.xml instead
> of
> > blueprint.xml?  If this processor depends on a specific producer template
> > ("myTemplate") == Camel context, then I see no reasons this producer can
> be
> > shared across multiple Camel contexts.
> >
> > On Tue, Jul 5, 2016 at 8:01 PM, Debraj Manna 
> > wrote:
> >
> > > Yeah Tadayoshi. jsonRPCProcessor is using myTemplate as shown below:-
> > >
> > >  > >
> > >
> >
> class="com.j1.orchestratorservice.basecomponent.processor.JSONRPCProcessor">
> > > 
> > > 
> > > 
> > > 
> > >  > > value-ref="createProductsWFInfo" />
> > > 
> > > 
> > > 
> > > 
> > >
> > >
> > > whereas myTemplate is defined in camelContext which in turn is using
> > > jsonRPCProcessor as shown below:-
> > >
> > > http://camel.apache.org/schema/blueprint";
> > > useMDCLogging="true">
> > > 
> > > 
> > > http://0.0.0.0:/orchestratorservice";
> />
> > > 
> > > 
> > > 
> > >  > >
> > > uri="jetty:
> > > http://0.0.0.0:8889/fileuploadservice?enableMultipartFilter=true";
> > > />
> > > 
> > > 
> > > ...
> > > 
> > >
> > >
> > > I have tried to set the producer in my custom jsonRPCProcessor as
> > mentioned
> > > in this link
> > > <
> > >
> >
> http://camel.apache.org/how-do-i-write-a-custom-processor-which-sends-multiple-messages.html
> > > >.
> > > Can someone suggest me some other way of setting the producer in my
> > custom
> > > jsonRPCProcessor so that it does not lead to any circular dependency?
> > >
> > > On Tue, Jul 5, 2016 at 8:21 AM, Tadayoshi Sato <
> sato.tadayo...@gmail.com
> > >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > It looks like 'myTemplate' is defined in camelContext.xml, but the
> > Camel
> > > > context then refers to 'jsonRPCProcessor' in blueprint.xml, which in
> > > turns
> > > > refers to 'myTemplate'. That should be the cyclic dependency in
> > question.
> > > >
> > > > Hope this helps,
> > > >
> > > > Tadayoshi
> > > >
> > > > On Mon, Jul 4, 2016 at 10:27 PM, Debraj Manna <
> > subharaj.ma...@gmail.com>
> > > > wrote:
> > > >
> > > > > It seems the error is getting triggered because of some cyclic
> > > > dependency.
> > > > > But I am not able to figure out from the trace what is causing the
> > > cyclic
> > > > > dependency.
> > > > >
> > > > > On Jul 4, 2016 4:22 PM, "Debraj Manna" 
> > > wrote:
> > > > >
> > > > > > On placing a bundle (using camel) on Karaf I am seeing the below
> > > > > > exception. The below exception comes only when the bundle is
> > started.
> > > > > After
> > > > > > that everything works fine. The exeception does not seem to
> effect
> > > our
> > > > > > functionality. The issue is coming on both camel 2.16.1 (deployed
> > on
> > > > > servicemix
> > > > > > 6.1.0) and camel 2.16.3 (deployed on servicemix 7.0.0M2).
> > > > > >
> > > > > > My blueprint is split into three files. A simplified version of
> > them
> > > > are
> > > > > > shown below:-
> > > > > >
> > > > > >
> > > > > >1. blueprint.xml placed here
> > > > > ><
> > > > >
> > https://gist.github.com/debraj-manna/42294561b9da22ce2281e6a9f3b22a34>
> > > > > >.
> > > > > >2. productBeans.xml placed here
> > > > > ><
> > > > >
> > https://gist.github.com/debraj-manna/5c406f597f8b7248369b206ed1f93842>
> > > > > >.
> > > > > >3. camelContext.xml placed here
> > > > > ><
> > > > >
> > https://gist.github.com/debraj-manna/4210653d661beaee6beb87900c4f4911>
> > > > > >.
> > > > > >
> > > > > >
> > > > > > Can some please let me know why is this exception coming during
> > > bundle
> > > > > > start?
> > > > > >
> > > > > > The exception looks like below:-
> > > > > >
> > > > > > 2016-07-04 11:29:37,497 | ERROR | mix-6.1.0/deploy |
> > > > > BlueprintCamelContext
> > > > > >| 143 - org.apache.camel.camel-blueprint - 2.16.1 | {{
> > > > > bundle.id
> > > > > > ,143}{bundle.name
> > > > > ,org.apache.camel.camel-blueprint}{bundle.version,2.16.1}}
> > > > > > | Error occurred during starting Camel: CamelContext(camel-1) due
> > > > Failed
> > > > > t

Re: Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-06 Thread Debraj Manna

Are you saying  to define jsonRPCProcessor inside camelContext. Something
like below:-

http://camel.apache.org/schema/blueprint";
useMDCLogging="true">

**
*...*
**


http://0.0.0.0:/orchestratorservice"; />



http://0.0.0.0:8889/fileuploadservice?enableMultipartFilter=true"; />


...


On Wed, Jul 6, 2016 at 7:00 AM, Tadayoshi Sato 
wrote:

> Hi Debraj,
>
> Then why can you not define jsonRPCProcessor in camelContext.xml instead of
> blueprint.xml?  If this processor depends on a specific producer template
> ("myTemplate") == Camel context, then I see no reasons this producer can be
> shared across multiple Camel contexts.
>
> On Tue, Jul 5, 2016 at 8:01 PM, Debraj Manna 
> wrote:
>
> > Yeah Tadayoshi. jsonRPCProcessor is using myTemplate as shown below:-
> >
> >  >
> >
> class="com.j1.orchestratorservice.basecomponent.processor.JSONRPCProcessor">
> > 
> > 
> > 
> > 
> >  > value-ref="createProductsWFInfo" />
> > 
> > 
> > 
> > 
> >
> >
> > whereas myTemplate is defined in camelContext which in turn is using
> > jsonRPCProcessor as shown below:-
> >
> > http://camel.apache.org/schema/blueprint";
> > useMDCLogging="true">
> > 
> > 
> > http://0.0.0.0:/orchestratorservice"; />
> > 
> > 
> > 
> >  >
> > uri="jetty:
> > http://0.0.0.0:8889/fileuploadservice?enableMultipartFilter=true";
> > />
> > 
> > 
> > ...
> > 
> >
> >
> > I have tried to set the producer in my custom jsonRPCProcessor as
> mentioned
> > in this link
> > <
> >
> http://camel.apache.org/how-do-i-write-a-custom-processor-which-sends-multiple-messages.html
> > >.
> > Can someone suggest me some other way of setting the producer in my
> custom
> > jsonRPCProcessor so that it does not lead to any circular dependency?
> >
> > On Tue, Jul 5, 2016 at 8:21 AM, Tadayoshi Sato  >
> > wrote:
> >
> > > Hi,
> > >
> > > It looks like 'myTemplate' is defined in camelContext.xml, but the
> Camel
> > > context then refers to 'jsonRPCProcessor' in blueprint.xml, which in
> > turns
> > > refers to 'myTemplate'. That should be the cyclic dependency in
> question.
> > >
> > > Hope this helps,
> > >
> > > Tadayoshi
> > >
> > > On Mon, Jul 4, 2016 at 10:27 PM, Debraj Manna <
> subharaj.ma...@gmail.com>
> > > wrote:
> > >
> > > > It seems the error is getting triggered because of some cyclic
> > > dependency.
> > > > But I am not able to figure out from the trace what is causing the
> > cyclic
> > > > dependency.
> > > >
> > > > On Jul 4, 2016 4:22 PM, "Debraj Manna" 
> > wrote:
> > > >
> > > > > On placing a bundle (using camel) on Karaf I am seeing the below
> > > > > exception. The below exception comes only when the bundle is
> started.
> > > > After
> > > > > that everything works fine. The exeception does not seem to effect
> > our
> > > > > functionality. The issue is coming on both camel 2.16.1 (deployed
> on
> > > > servicemix
> > > > > 6.1.0) and camel 2.16.3 (deployed on servicemix 7.0.0M2).
> > > > >
> > > > > My blueprint is split into three files. A simplified version of
> them
> > > are
> > > > > shown below:-
> > > > >
> > > > >
> > > > >1. blueprint.xml placed here
> > > > ><
> > > >
> https://gist.github.com/debraj-manna/42294561b9da22ce2281e6a9f3b22a34>
> > > > >.
> > > > >2. productBeans.xml placed here
> > > > ><
> > > >
> https://gist.github.com/debraj-manna/5c406f597f8b7248369b206ed1f93842>
> > > > >.
> > > > >3. camelContext.xml placed here
> > > > ><
> > > >
> https://gist.github.com/debraj-manna/4210653d661beaee6beb87900c4f4911>
> > > > >.
> > > > >
> > > > >
> > > > > Can some please let me know why is this exception coming during
> > bundle
> > > > > start?
> > > > >
> > > > > The exception looks like below:-
> > > > >
> > > > > 2016-07-04 11:29:37,497 | ERROR | mix-6.1.0/deploy |
> > > > BlueprintCamelContext
> > > > >| 143 - org.apache.camel.camel-blueprint - 2.16.1 | {{
> > > > bundle.id
> > > > > ,143}{bundle.name
> > > > ,org.apache.camel.camel-blueprint}{bundle.version,2.16.1}}
> > > > > | Error occurred during starting Camel: CamelContext(camel-1) due
> > > Failed
> > > > to
> > > > > create route orchestrator-service-route at: >>>
> > > > > process[ref:jsonRPCProcessor] <<< in route:
> > > > > Route(orchestrator-service-route)[[From[jetty:http://0.0.0.0...
> > > because
> > > > > of Cannot lookup: jsonRPCProcessor from registry:
> > > > > org.apache.camel.blueprint.BlueprintContainerRegistry@7b081b97
> with
> > > > > expected type: interface org.apache.camel.Processor due:
> > > > > [BeanRecipe[name='myTemplate'],
> > > > > BeanRecipe[name='.camelBlueprint.bean.factory.myTemplate'],
> > > > > BeanRecipe[name='camel-1'], BeanRecipe[name='myTemplate']]
> > > > > org.apache.ca

Re: Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-05 Thread Tadayoshi Sato

Hi Debraj,

Then why can you not define jsonRPCProcessor in camelContext.xml instead of
blueprint.xml?  If this processor depends on a specific producer template
("myTemplate") == Camel context, then I see no reasons this producer can be
shared across multiple Camel contexts.

On Tue, Jul 5, 2016 at 8:01 PM, Debraj Manna 
wrote:

> Yeah Tadayoshi. jsonRPCProcessor is using myTemplate as shown below:-
>
> 
> class="com.j1.orchestratorservice.basecomponent.processor.JSONRPCProcessor">
> 
> 
> 
> 
>  value-ref="createProductsWFInfo" />
> 
> 
> 
> 
>
>
> whereas myTemplate is defined in camelContext which in turn is using
> jsonRPCProcessor as shown below:-
>
> http://camel.apache.org/schema/blueprint";
> useMDCLogging="true">
> 
> 
> http://0.0.0.0:/orchestratorservice"; />
> 
> 
> 
> 
> uri="jetty:
> http://0.0.0.0:8889/fileuploadservice?enableMultipartFilter=true";
> />
> 
> 
> ...
> 
>
>
> I have tried to set the producer in my custom jsonRPCProcessor as mentioned
> in this link
> <
> http://camel.apache.org/how-do-i-write-a-custom-processor-which-sends-multiple-messages.html
> >.
> Can someone suggest me some other way of setting the producer in my custom
> jsonRPCProcessor so that it does not lead to any circular dependency?
>
> On Tue, Jul 5, 2016 at 8:21 AM, Tadayoshi Sato 
> wrote:
>
> > Hi,
> >
> > It looks like 'myTemplate' is defined in camelContext.xml, but the Camel
> > context then refers to 'jsonRPCProcessor' in blueprint.xml, which in
> turns
> > refers to 'myTemplate'. That should be the cyclic dependency in question.
> >
> > Hope this helps,
> >
> > Tadayoshi
> >
> > On Mon, Jul 4, 2016 at 10:27 PM, Debraj Manna 
> > wrote:
> >
> > > It seems the error is getting triggered because of some cyclic
> > dependency.
> > > But I am not able to figure out from the trace what is causing the
> cyclic
> > > dependency.
> > >
> > > On Jul 4, 2016 4:22 PM, "Debraj Manna" 
> wrote:
> > >
> > > > On placing a bundle (using camel) on Karaf I am seeing the below
> > > > exception. The below exception comes only when the bundle is started.
> > > After
> > > > that everything works fine. The exeception does not seem to effect
> our
> > > > functionality. The issue is coming on both camel 2.16.1 (deployed on
> > > servicemix
> > > > 6.1.0) and camel 2.16.3 (deployed on servicemix 7.0.0M2).
> > > >
> > > > My blueprint is split into three files. A simplified version of them
> > are
> > > > shown below:-
> > > >
> > > >
> > > >1. blueprint.xml placed here
> > > ><
> > > https://gist.github.com/debraj-manna/42294561b9da22ce2281e6a9f3b22a34>
> > > >.
> > > >2. productBeans.xml placed here
> > > ><
> > > https://gist.github.com/debraj-manna/5c406f597f8b7248369b206ed1f93842>
> > > >.
> > > >3. camelContext.xml placed here
> > > ><
> > > https://gist.github.com/debraj-manna/4210653d661beaee6beb87900c4f4911>
> > > >.
> > > >
> > > >
> > > > Can some please let me know why is this exception coming during
> bundle
> > > > start?
> > > >
> > > > The exception looks like below:-
> > > >
> > > > 2016-07-04 11:29:37,497 | ERROR | mix-6.1.0/deploy |
> > > BlueprintCamelContext
> > > >| 143 - org.apache.camel.camel-blueprint - 2.16.1 | {{
> > > bundle.id
> > > > ,143}{bundle.name
> > > ,org.apache.camel.camel-blueprint}{bundle.version,2.16.1}}
> > > > | Error occurred during starting Camel: CamelContext(camel-1) due
> > Failed
> > > to
> > > > create route orchestrator-service-route at: >>>
> > > > process[ref:jsonRPCProcessor] <<< in route:
> > > > Route(orchestrator-service-route)[[From[jetty:http://0.0.0.0...
> > because
> > > > of Cannot lookup: jsonRPCProcessor from registry:
> > > > org.apache.camel.blueprint.BlueprintContainerRegistry@7b081b97 with
> > > > expected type: interface org.apache.camel.Processor due:
> > > > [BeanRecipe[name='myTemplate'],
> > > > BeanRecipe[name='.camelBlueprint.bean.factory.myTemplate'],
> > > > BeanRecipe[name='camel-1'], BeanRecipe[name='myTemplate']]
> > > > org.apache.camel.FailedToCreateRouteException: Failed to create route
> > > > orchestrator-service-route at: >>> process[ref:jsonRPCProcessor] <<<
> in
> > > > route: Route(orchestrator-service-route)[[From[jetty:http://0.0.0.0.
> ..
> > > > because of Cannot lookup: jsonRPCProcessor from registry:
> > > > org.apache.camel.blueprint.BlueprintContainerRegistry@7b081b97 with
> > > > expected type: interface org.apache.camel.Processor due:
> > > > [BeanRecipe[name='myTemplate'],
> > > > BeanRecipe[name='.camelBlueprint.bean.factory.myTemplate'],
> > > > BeanRecipe[name='camel-1'], BeanRecipe[name='myTemplate']]
> > > > at
> > > >
> > >
> >
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1072)
> > > > at
> > > >
> > >
> >
> org.apache.camel.model.RouteDefinition.addRoutes(Rout

Re: Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-05 Thread Debraj Manna

Yeah Tadayoshi. jsonRPCProcessor is using myTemplate as shown below:-













whereas myTemplate is defined in camelContext which in turn is using
jsonRPCProcessor as shown below:-

http://camel.apache.org/schema/blueprint";
useMDCLogging="true">


http://0.0.0.0:/orchestratorservice"; />



http://0.0.0.0:8889/fileuploadservice?enableMultipartFilter=true";
/>


...



I have tried to set the producer in my custom jsonRPCProcessor as mentioned
in this link
.
Can someone suggest me some other way of setting the producer in my custom
jsonRPCProcessor so that it does not lead to any circular dependency?

On Tue, Jul 5, 2016 at 8:21 AM, Tadayoshi Sato 
wrote:

> Hi,
>
> It looks like 'myTemplate' is defined in camelContext.xml, but the Camel
> context then refers to 'jsonRPCProcessor' in blueprint.xml, which in turns
> refers to 'myTemplate'. That should be the cyclic dependency in question.
>
> Hope this helps,
>
> Tadayoshi
>
> On Mon, Jul 4, 2016 at 10:27 PM, Debraj Manna 
> wrote:
>
> > It seems the error is getting triggered because of some cyclic
> dependency.
> > But I am not able to figure out from the trace what is causing the cyclic
> > dependency.
> >
> > On Jul 4, 2016 4:22 PM, "Debraj Manna"  wrote:
> >
> > > On placing a bundle (using camel) on Karaf I am seeing the below
> > > exception. The below exception comes only when the bundle is started.
> > After
> > > that everything works fine. The exeception does not seem to effect our
> > > functionality. The issue is coming on both camel 2.16.1 (deployed on
> > servicemix
> > > 6.1.0) and camel 2.16.3 (deployed on servicemix 7.0.0M2).
> > >
> > > My blueprint is split into three files. A simplified version of them
> are
> > > shown below:-
> > >
> > >
> > >1. blueprint.xml placed here
> > ><
> > https://gist.github.com/debraj-manna/42294561b9da22ce2281e6a9f3b22a34>
> > >.
> > >2. productBeans.xml placed here
> > ><
> > https://gist.github.com/debraj-manna/5c406f597f8b7248369b206ed1f93842>
> > >.
> > >3. camelContext.xml placed here
> > ><
> > https://gist.github.com/debraj-manna/4210653d661beaee6beb87900c4f4911>
> > >.
> > >
> > >
> > > Can some please let me know why is this exception coming during bundle
> > > start?
> > >
> > > The exception looks like below:-
> > >
> > > 2016-07-04 11:29:37,497 | ERROR | mix-6.1.0/deploy |
> > BlueprintCamelContext
> > >| 143 - org.apache.camel.camel-blueprint - 2.16.1 | {{
> > bundle.id
> > > ,143}{bundle.name
> > ,org.apache.camel.camel-blueprint}{bundle.version,2.16.1}}
> > > | Error occurred during starting Camel: CamelContext(camel-1) due
> Failed
> > to
> > > create route orchestrator-service-route at: >>>
> > > process[ref:jsonRPCProcessor] <<< in route:
> > > Route(orchestrator-service-route)[[From[jetty:http://0.0.0.0...
> because
> > > of Cannot lookup: jsonRPCProcessor from registry:
> > > org.apache.camel.blueprint.BlueprintContainerRegistry@7b081b97 with
> > > expected type: interface org.apache.camel.Processor due:
> > > [BeanRecipe[name='myTemplate'],
> > > BeanRecipe[name='.camelBlueprint.bean.factory.myTemplate'],
> > > BeanRecipe[name='camel-1'], BeanRecipe[name='myTemplate']]
> > > org.apache.camel.FailedToCreateRouteException: Failed to create route
> > > orchestrator-service-route at: >>> process[ref:jsonRPCProcessor] <<< in
> > > route: Route(orchestrator-service-route)[[From[jetty:http://0.0.0.0...
> > > because of Cannot lookup: jsonRPCProcessor from registry:
> > > org.apache.camel.blueprint.BlueprintContainerRegistry@7b081b97 with
> > > expected type: interface org.apache.camel.Processor due:
> > > [BeanRecipe[name='myTemplate'],
> > > BeanRecipe[name='.camelBlueprint.bean.factory.myTemplate'],
> > > BeanRecipe[name='camel-1'], BeanRecipe[name='myTemplate']]
> > > at
> > >
> >
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1072)
> > > at
> > >
> >
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:196)
> > > at
> > >
> >
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:947)
> > > at
> > >
> >
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3258)
> > > at
> > >
> >
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:2981)
> > > at
> > >
> >
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:175)
> > > at
> > >
> >
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2812)
> > > at
> > >
> >
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2808)
> > > at
> > >
> >
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoade

Re: Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-04 Thread Tadayoshi Sato

Hi,

It looks like 'myTemplate' is defined in camelContext.xml, but the Camel
context then refers to 'jsonRPCProcessor' in blueprint.xml, which in turns
refers to 'myTemplate'. That should be the cyclic dependency in question.

Hope this helps,

Tadayoshi

On Mon, Jul 4, 2016 at 10:27 PM, Debraj Manna 
wrote:

> It seems the error is getting triggered because of some cyclic dependency.
> But I am not able to figure out from the trace what is causing the cyclic
> dependency.
>
> On Jul 4, 2016 4:22 PM, "Debraj Manna"  wrote:
>
> > On placing a bundle (using camel) on Karaf I am seeing the below
> > exception. The below exception comes only when the bundle is started.
> After
> > that everything works fine. The exeception does not seem to effect our
> > functionality. The issue is coming on both camel 2.16.1 (deployed on
> servicemix
> > 6.1.0) and camel 2.16.3 (deployed on servicemix 7.0.0M2).
> >
> > My blueprint is split into three files. A simplified version of them are
> > shown below:-
> >
> >
> >1. blueprint.xml placed here
> ><
> https://gist.github.com/debraj-manna/42294561b9da22ce2281e6a9f3b22a34>
> >.
> >2. productBeans.xml placed here
> ><
> https://gist.github.com/debraj-manna/5c406f597f8b7248369b206ed1f93842>
> >.
> >3. camelContext.xml placed here
> ><
> https://gist.github.com/debraj-manna/4210653d661beaee6beb87900c4f4911>
> >.
> >
> >
> > Can some please let me know why is this exception coming during bundle
> > start?
> >
> > The exception looks like below:-
> >
> > 2016-07-04 11:29:37,497 | ERROR | mix-6.1.0/deploy |
> BlueprintCamelContext
> >| 143 - org.apache.camel.camel-blueprint - 2.16.1 | {{
> bundle.id
> > ,143}{bundle.name
> ,org.apache.camel.camel-blueprint}{bundle.version,2.16.1}}
> > | Error occurred during starting Camel: CamelContext(camel-1) due Failed
> to
> > create route orchestrator-service-route at: >>>
> > process[ref:jsonRPCProcessor] <<< in route:
> > Route(orchestrator-service-route)[[From[jetty:http://0.0.0.0... because
> > of Cannot lookup: jsonRPCProcessor from registry:
> > org.apache.camel.blueprint.BlueprintContainerRegistry@7b081b97 with
> > expected type: interface org.apache.camel.Processor due:
> > [BeanRecipe[name='myTemplate'],
> > BeanRecipe[name='.camelBlueprint.bean.factory.myTemplate'],
> > BeanRecipe[name='camel-1'], BeanRecipe[name='myTemplate']]
> > org.apache.camel.FailedToCreateRouteException: Failed to create route
> > orchestrator-service-route at: >>> process[ref:jsonRPCProcessor] <<< in
> > route: Route(orchestrator-service-route)[[From[jetty:http://0.0.0.0...
> > because of Cannot lookup: jsonRPCProcessor from registry:
> > org.apache.camel.blueprint.BlueprintContainerRegistry@7b081b97 with
> > expected type: interface org.apache.camel.Processor due:
> > [BeanRecipe[name='myTemplate'],
> > BeanRecipe[name='.camelBlueprint.bean.factory.myTemplate'],
> > BeanRecipe[name='camel-1'], BeanRecipe[name='myTemplate']]
> > at
> >
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1072)
> > at
> >
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:196)
> > at
> >
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:947)
> > at
> >
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3258)
> > at
> >
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:2981)
> > at
> >
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:175)
> > at
> >
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2812)
> > at
> >
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2808)
> > at
> >
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:2831)
> > at
> >
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:2808)
> > at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> > at
> >
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:2777)
> > at
> >
> org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:180)[143:org.apache.camel.camel-blueprint:2.16.1]
> > at
> >
> org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:212)[143:org.apache.camel.camel-blueprint:2.16.1]
> > at
> >
> org.apache.camel.blueprint.BlueprintCamelContext.serviceChanged(BlueprintCamelContext.java:150)[143:org.apache.camel.camel-blueprint:2.16.1]
> > at
> >
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)[org.apache.felix.framework-4.2.1.jar:]
> > at
> >
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)[org.apache.felix.framework-4.2.1.jar:]
> > at
> >
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)[org.apache.felix.framework-4.2.

Re: Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-04 Thread Debraj Manna

It seems the error is getting triggered because of some cyclic dependency.
But I am not able to figure out from the trace what is causing the cyclic
dependency.

On Jul 4, 2016 4:22 PM, "Debraj Manna"  wrote:

> On placing a bundle (using camel) on Karaf I am seeing the below
> exception. The below exception comes only when the bundle is started. After
> that everything works fine. The exeception does not seem to effect our
> functionality. The issue is coming on both camel 2.16.1 (deployed on 
> servicemix
> 6.1.0) and camel 2.16.3 (deployed on servicemix 7.0.0M2).
>
> My blueprint is split into three files. A simplified version of them are
> shown below:-
>
>
>1. blueprint.xml placed here
>
>.
>2. productBeans.xml placed here
>
>.
>3. camelContext.xml placed here
>
>.
>
>
> Can some please let me know why is this exception coming during bundle
> start?
>
> The exception looks like below:-
>
> 2016-07-04 11:29:37,497 | ERROR | mix-6.1.0/deploy | BlueprintCamelContext
>| 143 - org.apache.camel.camel-blueprint - 2.16.1 | {{bundle.id
> ,143}{bundle.name,org.apache.camel.camel-blueprint}{bundle.version,2.16.1}}
> | Error occurred during starting Camel: CamelContext(camel-1) due Failed to
> create route orchestrator-service-route at: >>>
> process[ref:jsonRPCProcessor] <<< in route:
> Route(orchestrator-service-route)[[From[jetty:http://0.0.0.0... because
> of Cannot lookup: jsonRPCProcessor from registry:
> org.apache.camel.blueprint.BlueprintContainerRegistry@7b081b97 with
> expected type: interface org.apache.camel.Processor due:
> [BeanRecipe[name='myTemplate'],
> BeanRecipe[name='.camelBlueprint.bean.factory.myTemplate'],
> BeanRecipe[name='camel-1'], BeanRecipe[name='myTemplate']]
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> orchestrator-service-route at: >>> process[ref:jsonRPCProcessor] <<< in
> route: Route(orchestrator-service-route)[[From[jetty:http://0.0.0.0...
> because of Cannot lookup: jsonRPCProcessor from registry:
> org.apache.camel.blueprint.BlueprintContainerRegistry@7b081b97 with
> expected type: interface org.apache.camel.Processor due:
> [BeanRecipe[name='myTemplate'],
> BeanRecipe[name='.camelBlueprint.bean.factory.myTemplate'],
> BeanRecipe[name='camel-1'], BeanRecipe[name='myTemplate']]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1072)
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:196)
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:947)
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3258)
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:2981)
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:175)
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2812)
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2808)
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:2831)
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:2808)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:2777)
> at
> org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:180)[143:org.apache.camel.camel-blueprint:2.16.1]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:212)[143:org.apache.camel.camel-blueprint:2.16.1]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.serviceChanged(BlueprintCamelContext.java:150)[143:org.apache.camel.camel-blueprint:2.16.1]
> at
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)[org.apache.felix.framework-4.2.1.jar:]
> at
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)[org.apache.felix.framework-4.2.1.jar:]
> at
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)[org.apache.felix.framework-4.2.1.jar:]
> at
> org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4419)[org.apache.felix.framework-4.2.1.jar:]
> at
> org.apache.felix.framework.Felix.registerService(Felix.java:3423)[org.apache.felix.framework-4.2.1.jar:]
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:352)
> at
> org.apache.camel.blueprint.BlueprintCamelContext.init(BlueprintCamelContext.java:100)[143:org.apache.camel.cam

Error occurred during starting Camel because of cannot look up a processor from registry

2016-07-04 Thread Debraj Manna

On placing a bundle (using camel) on Karaf I am seeing the below exception.
The below exception comes only when the bundle is started. After that
everything works fine. The exeception does not seem to effect our
functionality. The issue is coming on both camel 2.16.1 (deployed on servicemix
6.1.0) and camel 2.16.3 (deployed on servicemix 7.0.0M2).

My blueprint is split into three files. A simplified version of them are
shown below:-


   1. blueprint.xml placed here
   .
   2. productBeans.xml placed here
   .
   3. camelContext.xml placed here
   .


Can some please let me know why is this exception coming during bundle
start?

The exception looks like below:-

2016-07-04 11:29:37,497 | ERROR | mix-6.1.0/deploy | BlueprintCamelContext
   | 143 - org.apache.camel.camel-blueprint - 2.16.1 | {{bundle.id
,143}{bundle.name,org.apache.camel.camel-blueprint}{bundle.version,2.16.1}}
| Error occurred during starting Camel: CamelContext(camel-1) due Failed to
create route orchestrator-service-route at: >>>
process[ref:jsonRPCProcessor] <<< in route:
Route(orchestrator-service-route)[[From[jetty:http://0.0.0.0... because of
Cannot lookup: jsonRPCProcessor from registry:
org.apache.camel.blueprint.BlueprintContainerRegistry@7b081b97 with
expected type: interface org.apache.camel.Processor due:
[BeanRecipe[name='myTemplate'],
BeanRecipe[name='.camelBlueprint.bean.factory.myTemplate'],
BeanRecipe[name='camel-1'], BeanRecipe[name='myTemplate']]
org.apache.camel.FailedToCreateRouteException: Failed to create route
orchestrator-service-route at: >>> process[ref:jsonRPCProcessor] <<< in
route: Route(orchestrator-service-route)[[From[jetty:http://0.0.0.0...
because of Cannot lookup: jsonRPCProcessor from registry:
org.apache.camel.blueprint.BlueprintContainerRegistry@7b081b97 with
expected type: interface org.apache.camel.Processor due:
[BeanRecipe[name='myTemplate'],
BeanRecipe[name='.camelBlueprint.bean.factory.myTemplate'],
BeanRecipe[name='camel-1'], BeanRecipe[name='myTemplate']]
at
org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1072)
at
org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:196)
at
org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:947)
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3258)
at
org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:2981)
at
org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:175)
at
org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2812)
at
org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2808)
at
org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:2831)
at
org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:2808)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:2777)
at
org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:180)[143:org.apache.camel.camel-blueprint:2.16.1]
at
org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:212)[143:org.apache.camel.camel-blueprint:2.16.1]
at
org.apache.camel.blueprint.BlueprintCamelContext.serviceChanged(BlueprintCamelContext.java:150)[143:org.apache.camel.camel-blueprint:2.16.1]
at
org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)[org.apache.felix.framework-4.2.1.jar:]
at
org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)[org.apache.felix.framework-4.2.1.jar:]
at
org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)[org.apache.felix.framework-4.2.1.jar:]
at
org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4419)[org.apache.felix.framework-4.2.1.jar:]
at
org.apache.felix.framework.Felix.registerService(Felix.java:3423)[org.apache.felix.framework-4.2.1.jar:]
at
org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)
at
org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:352)
at
org.apache.camel.blueprint.BlueprintCamelContext.init(BlueprintCamelContext.java:100)[143:org.apache.camel.camel-blueprint:2.16.1]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_77]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_77]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_77]
at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_77]
at
org.apache.aries.blueprint.utils.ReflectionUtils.in

Re: Error occurred during starting Camel because of cannot look up a processor from registry

Re: Error occurred during starting Camel because of cannot look up a processor from registry

Re: Error occurred during starting Camel because of cannot look up a processor from registry

Re: Error occurred during starting Camel because of cannot look up a processor from registry

Re: Error occurred during starting Camel because of cannot look up a processor from registry

Re: Error occurred during starting Camel because of cannot look up a processor from registry

Re: Error occurred during starting Camel because of cannot look up a processor from registry

Re: Error occurred during starting Camel because of cannot look up a processor from registry

Re: Error occurred during starting Camel because of cannot look up a processor from registry

Error occurred during starting Camel because of cannot look up a processor from registry

10 matches

Site Navigation

Mail list logo

Footer information