You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by k....@gmail.com on 2019/12/02 13:49:27 UTC
Debugging and tracing camel-3.0.0 on OSGi
Hello.
Is there any way to trace or debug the camel routes in 3.0.0 when starting camel context through OSGi Blueprint?
I tried looking for BacklogDebugger/BacklogTracer MBeans on JMX without any luck (though I can see the context/processor/routes there).
Debug/trace tabs just gone missing from my hawtio console after update from 2.24. I only managed to find an issue https://issues.apache.org/jira/browse/CAMEL-13759
stating that "There is already the newer backlog debugger that hawtio and other tools uses for debugging.", so I believe there must be a way to make it work somehow.
Setting trace=true on camelContext only creates a DefaultTracer, which does not seem to be reporting any notifications through JMX.
Using Java 11 + Karaf 4.2.7 + Hawtio 2.8.0 + Camel 3.0.0.
P.S.> It looks like the blueprint xsd for 3.0.0 is missing from the http://camel.apache.org/schema/blueprint/ at all. Is there any other place where the schemas reside (besides the camel-blueprint jar)?
Thanks in advance,
Konstantin Chernov.
Re: Debugging and tracing camel-3.0.0 on OSGi
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Ah okay yeah lets added an option to set this easy in <camelContext>
On Tue, Dec 3, 2019 at 1:07 PM <k....@gmail.com> wrote:
>
> Hi,
>
> Looks like setting backlogTracing on context only turns on the tracing possibility.
> Shouldn't there be another option backlogDebugging=true|false ?
>
> Konstantin Chernov.
>
> -----Original Message-----
> From: k.j.chernov@gmail.com <k....@gmail.com>
> Sent: Monday, December 2, 2019 10:13 PM
> To: users@camel.apache.org
> Subject: RE: Debugging and tracing camel-3.0.0 on OSGi
>
> Thanks!
>
> https://issues.apache.org/jira/browse/CAMEL-14240
>
>
> Konstantin Chernov.
>
> -----Original Message-----
> From: Claus Ibsen <cl...@gmail.com>
> Sent: Monday, December 2, 2019 10:01 PM
> To: users@camel.apache.org
> Subject: Re: Debugging and tracing camel-3.0.0 on OSGi
>
> Hi
>
> Yeah you are welcome to create a JIRA to add backlogTracing=true|false to spring and blueprint xml
>
> On Mon, Dec 2, 2019 at 3:34 PM <k....@gmail.com> wrote:
> >
> > Hi.
> >
> > Thank you very much, I managed to turn the debugger on using:
> >
> > public class DebuggerEnablerBean {
> > public DebuggerEnablerBean(CamelContext camelContext) {
> > camelContext.setDebugging(true);
> > }
> > }
> >
> > and instantiating this bean in xml:
> > <bean id="debugEnablerBean" class="package.DebuggerEnablerBean">
> > <argument ref="camel-context-id" />
> > </bean>
> >
> > and it even works now in hawtio!
> >
> > But is there any way to do this directly from blueprint xml, without using java? The way I did it looks like a very dirty hack for me.
> > Maybe there should be an option like "trace=true" (say, "debug=true") on camelContext?
> >
> >
> > Konstantin Chernov.
> >
> > -----Original Message-----
> > From: Claus Ibsen <cl...@gmail.com>
> > Sent: Monday, December 2, 2019 9:13 PM
> > To: users@camel.apache.org
> > Subject: Re: Debugging and tracing camel-3.0.0 on OSGi
> >
> > I logged a ticket about the missing XSDs
> > https://issues.apache.org/jira/browse/CAMEL-14239
> >
> > On Mon, Dec 2, 2019 at 3:07 PM Claus Ibsen <cl...@gmail.com> wrote:
> > >
> > > Hi
> > >
> > > You need to turn on tracing before starting Camel in Camel 3 to have JMX tracer.
> > >
> > > context.setBacklogTracing(true);
> > >
> > >
> > > And the poor mans debugger is a feature we no longer want to provide
> > > out of the box in Camel and its removed.
> > >
> > >
> > >
> > > On Mon, Dec 2, 2019 at 2:49 PM <k....@gmail.com> wrote:
> > > >
> > > > Hello.
> > > >
> > > > Is there any way to trace or debug the camel routes in 3.0.0 when starting camel context through OSGi Blueprint?
> > > > I tried looking for BacklogDebugger/BacklogTracer MBeans on JMX without any luck (though I can see the context/processor/routes there).
> > > > Debug/trace tabs just gone missing from my hawtio console after
> > > > update from 2.24. I only managed to find an issue
> > > > https://issues.apache.org/jira/browse/CAMEL-13759
> > > > stating that "There is already the newer backlog debugger that hawtio and other tools uses for debugging.", so I believe there must be a way to make it work somehow.
> > > > Setting trace=true on camelContext only creates a DefaultTracer, which does not seem to be reporting any notifications through JMX.
> > > >
> > > > Using Java 11 + Karaf 4.2.7 + Hawtio 2.8.0 + Camel 3.0.0.
> > > >
> > > > P.S.> It looks like the blueprint xsd for 3.0.0 is missing from the http://camel.apache.org/schema/blueprint/ at all. Is there any other place where the schemas reside (besides the camel-blueprint jar)?
> > > >
> > > > Thanks in advance,
> > > > Konstantin Chernov.
> > > >
> > > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
RE: Debugging and tracing camel-3.0.0 on OSGi
Posted by k....@gmail.com.
Hi,
Looks like setting backlogTracing on context only turns on the tracing possibility.
Shouldn't there be another option backlogDebugging=true|false ?
Konstantin Chernov.
-----Original Message-----
From: k.j.chernov@gmail.com <k....@gmail.com>
Sent: Monday, December 2, 2019 10:13 PM
To: users@camel.apache.org
Subject: RE: Debugging and tracing camel-3.0.0 on OSGi
Thanks!
https://issues.apache.org/jira/browse/CAMEL-14240
Konstantin Chernov.
-----Original Message-----
From: Claus Ibsen <cl...@gmail.com>
Sent: Monday, December 2, 2019 10:01 PM
To: users@camel.apache.org
Subject: Re: Debugging and tracing camel-3.0.0 on OSGi
Hi
Yeah you are welcome to create a JIRA to add backlogTracing=true|false to spring and blueprint xml
On Mon, Dec 2, 2019 at 3:34 PM <k....@gmail.com> wrote:
>
> Hi.
>
> Thank you very much, I managed to turn the debugger on using:
>
> public class DebuggerEnablerBean {
> public DebuggerEnablerBean(CamelContext camelContext) {
> camelContext.setDebugging(true);
> }
> }
>
> and instantiating this bean in xml:
> <bean id="debugEnablerBean" class="package.DebuggerEnablerBean">
> <argument ref="camel-context-id" />
> </bean>
>
> and it even works now in hawtio!
>
> But is there any way to do this directly from blueprint xml, without using java? The way I did it looks like a very dirty hack for me.
> Maybe there should be an option like "trace=true" (say, "debug=true") on camelContext?
>
>
> Konstantin Chernov.
>
> -----Original Message-----
> From: Claus Ibsen <cl...@gmail.com>
> Sent: Monday, December 2, 2019 9:13 PM
> To: users@camel.apache.org
> Subject: Re: Debugging and tracing camel-3.0.0 on OSGi
>
> I logged a ticket about the missing XSDs
> https://issues.apache.org/jira/browse/CAMEL-14239
>
> On Mon, Dec 2, 2019 at 3:07 PM Claus Ibsen <cl...@gmail.com> wrote:
> >
> > Hi
> >
> > You need to turn on tracing before starting Camel in Camel 3 to have JMX tracer.
> >
> > context.setBacklogTracing(true);
> >
> >
> > And the poor mans debugger is a feature we no longer want to provide
> > out of the box in Camel and its removed.
> >
> >
> >
> > On Mon, Dec 2, 2019 at 2:49 PM <k....@gmail.com> wrote:
> > >
> > > Hello.
> > >
> > > Is there any way to trace or debug the camel routes in 3.0.0 when starting camel context through OSGi Blueprint?
> > > I tried looking for BacklogDebugger/BacklogTracer MBeans on JMX without any luck (though I can see the context/processor/routes there).
> > > Debug/trace tabs just gone missing from my hawtio console after
> > > update from 2.24. I only managed to find an issue
> > > https://issues.apache.org/jira/browse/CAMEL-13759
> > > stating that "There is already the newer backlog debugger that hawtio and other tools uses for debugging.", so I believe there must be a way to make it work somehow.
> > > Setting trace=true on camelContext only creates a DefaultTracer, which does not seem to be reporting any notifications through JMX.
> > >
> > > Using Java 11 + Karaf 4.2.7 + Hawtio 2.8.0 + Camel 3.0.0.
> > >
> > > P.S.> It looks like the blueprint xsd for 3.0.0 is missing from the http://camel.apache.org/schema/blueprint/ at all. Is there any other place where the schemas reside (besides the camel-blueprint jar)?
> > >
> > > Thanks in advance,
> > > Konstantin Chernov.
> > >
> > >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
RE: Debugging and tracing camel-3.0.0 on OSGi
Posted by k....@gmail.com.
Thanks!
https://issues.apache.org/jira/browse/CAMEL-14240
Konstantin Chernov.
-----Original Message-----
From: Claus Ibsen <cl...@gmail.com>
Sent: Monday, December 2, 2019 10:01 PM
To: users@camel.apache.org
Subject: Re: Debugging and tracing camel-3.0.0 on OSGi
Hi
Yeah you are welcome to create a JIRA to add backlogTracing=true|false to spring and blueprint xml
On Mon, Dec 2, 2019 at 3:34 PM <k....@gmail.com> wrote:
>
> Hi.
>
> Thank you very much, I managed to turn the debugger on using:
>
> public class DebuggerEnablerBean {
> public DebuggerEnablerBean(CamelContext camelContext) {
> camelContext.setDebugging(true);
> }
> }
>
> and instantiating this bean in xml:
> <bean id="debugEnablerBean" class="package.DebuggerEnablerBean">
> <argument ref="camel-context-id" />
> </bean>
>
> and it even works now in hawtio!
>
> But is there any way to do this directly from blueprint xml, without using java? The way I did it looks like a very dirty hack for me.
> Maybe there should be an option like "trace=true" (say, "debug=true") on camelContext?
>
>
> Konstantin Chernov.
>
> -----Original Message-----
> From: Claus Ibsen <cl...@gmail.com>
> Sent: Monday, December 2, 2019 9:13 PM
> To: users@camel.apache.org
> Subject: Re: Debugging and tracing camel-3.0.0 on OSGi
>
> I logged a ticket about the missing XSDs
> https://issues.apache.org/jira/browse/CAMEL-14239
>
> On Mon, Dec 2, 2019 at 3:07 PM Claus Ibsen <cl...@gmail.com> wrote:
> >
> > Hi
> >
> > You need to turn on tracing before starting Camel in Camel 3 to have JMX tracer.
> >
> > context.setBacklogTracing(true);
> >
> >
> > And the poor mans debugger is a feature we no longer want to provide
> > out of the box in Camel and its removed.
> >
> >
> >
> > On Mon, Dec 2, 2019 at 2:49 PM <k....@gmail.com> wrote:
> > >
> > > Hello.
> > >
> > > Is there any way to trace or debug the camel routes in 3.0.0 when starting camel context through OSGi Blueprint?
> > > I tried looking for BacklogDebugger/BacklogTracer MBeans on JMX without any luck (though I can see the context/processor/routes there).
> > > Debug/trace tabs just gone missing from my hawtio console after
> > > update from 2.24. I only managed to find an issue
> > > https://issues.apache.org/jira/browse/CAMEL-13759
> > > stating that "There is already the newer backlog debugger that hawtio and other tools uses for debugging.", so I believe there must be a way to make it work somehow.
> > > Setting trace=true on camelContext only creates a DefaultTracer, which does not seem to be reporting any notifications through JMX.
> > >
> > > Using Java 11 + Karaf 4.2.7 + Hawtio 2.8.0 + Camel 3.0.0.
> > >
> > > P.S.> It looks like the blueprint xsd for 3.0.0 is missing from the http://camel.apache.org/schema/blueprint/ at all. Is there any other place where the schemas reside (besides the camel-blueprint jar)?
> > >
> > > Thanks in advance,
> > > Konstantin Chernov.
> > >
> > >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Debugging and tracing camel-3.0.0 on OSGi
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Yeah you are welcome to create a JIRA to add backlogTracing=true|false
to spring and blueprint xml
On Mon, Dec 2, 2019 at 3:34 PM <k....@gmail.com> wrote:
>
> Hi.
>
> Thank you very much, I managed to turn the debugger on using:
>
> public class DebuggerEnablerBean {
> public DebuggerEnablerBean(CamelContext camelContext) {
> camelContext.setDebugging(true);
> }
> }
>
> and instantiating this bean in xml:
> <bean id="debugEnablerBean" class="package.DebuggerEnablerBean">
> <argument ref="camel-context-id" />
> </bean>
>
> and it even works now in hawtio!
>
> But is there any way to do this directly from blueprint xml, without using java? The way I did it looks like a very dirty hack for me.
> Maybe there should be an option like "trace=true" (say, "debug=true") on camelContext?
>
>
> Konstantin Chernov.
>
> -----Original Message-----
> From: Claus Ibsen <cl...@gmail.com>
> Sent: Monday, December 2, 2019 9:13 PM
> To: users@camel.apache.org
> Subject: Re: Debugging and tracing camel-3.0.0 on OSGi
>
> I logged a ticket about the missing XSDs
> https://issues.apache.org/jira/browse/CAMEL-14239
>
> On Mon, Dec 2, 2019 at 3:07 PM Claus Ibsen <cl...@gmail.com> wrote:
> >
> > Hi
> >
> > You need to turn on tracing before starting Camel in Camel 3 to have JMX tracer.
> >
> > context.setBacklogTracing(true);
> >
> >
> > And the poor mans debugger is a feature we no longer want to provide
> > out of the box in Camel and its removed.
> >
> >
> >
> > On Mon, Dec 2, 2019 at 2:49 PM <k....@gmail.com> wrote:
> > >
> > > Hello.
> > >
> > > Is there any way to trace or debug the camel routes in 3.0.0 when starting camel context through OSGi Blueprint?
> > > I tried looking for BacklogDebugger/BacklogTracer MBeans on JMX without any luck (though I can see the context/processor/routes there).
> > > Debug/trace tabs just gone missing from my hawtio console after
> > > update from 2.24. I only managed to find an issue
> > > https://issues.apache.org/jira/browse/CAMEL-13759
> > > stating that "There is already the newer backlog debugger that hawtio and other tools uses for debugging.", so I believe there must be a way to make it work somehow.
> > > Setting trace=true on camelContext only creates a DefaultTracer, which does not seem to be reporting any notifications through JMX.
> > >
> > > Using Java 11 + Karaf 4.2.7 + Hawtio 2.8.0 + Camel 3.0.0.
> > >
> > > P.S.> It looks like the blueprint xsd for 3.0.0 is missing from the http://camel.apache.org/schema/blueprint/ at all. Is there any other place where the schemas reside (besides the camel-blueprint jar)?
> > >
> > > Thanks in advance,
> > > Konstantin Chernov.
> > >
> > >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
RE: Debugging and tracing camel-3.0.0 on OSGi
Posted by k....@gmail.com.
Hi.
Thank you very much, I managed to turn the debugger on using:
public class DebuggerEnablerBean {
public DebuggerEnablerBean(CamelContext camelContext) {
camelContext.setDebugging(true);
}
}
and instantiating this bean in xml:
<bean id="debugEnablerBean" class="package.DebuggerEnablerBean">
<argument ref="camel-context-id" />
</bean>
and it even works now in hawtio!
But is there any way to do this directly from blueprint xml, without using java? The way I did it looks like a very dirty hack for me.
Maybe there should be an option like "trace=true" (say, "debug=true") on camelContext?
Konstantin Chernov.
-----Original Message-----
From: Claus Ibsen <cl...@gmail.com>
Sent: Monday, December 2, 2019 9:13 PM
To: users@camel.apache.org
Subject: Re: Debugging and tracing camel-3.0.0 on OSGi
I logged a ticket about the missing XSDs
https://issues.apache.org/jira/browse/CAMEL-14239
On Mon, Dec 2, 2019 at 3:07 PM Claus Ibsen <cl...@gmail.com> wrote:
>
> Hi
>
> You need to turn on tracing before starting Camel in Camel 3 to have JMX tracer.
>
> context.setBacklogTracing(true);
>
>
> And the poor mans debugger is a feature we no longer want to provide
> out of the box in Camel and its removed.
>
>
>
> On Mon, Dec 2, 2019 at 2:49 PM <k....@gmail.com> wrote:
> >
> > Hello.
> >
> > Is there any way to trace or debug the camel routes in 3.0.0 when starting camel context through OSGi Blueprint?
> > I tried looking for BacklogDebugger/BacklogTracer MBeans on JMX without any luck (though I can see the context/processor/routes there).
> > Debug/trace tabs just gone missing from my hawtio console after
> > update from 2.24. I only managed to find an issue
> > https://issues.apache.org/jira/browse/CAMEL-13759
> > stating that "There is already the newer backlog debugger that hawtio and other tools uses for debugging.", so I believe there must be a way to make it work somehow.
> > Setting trace=true on camelContext only creates a DefaultTracer, which does not seem to be reporting any notifications through JMX.
> >
> > Using Java 11 + Karaf 4.2.7 + Hawtio 2.8.0 + Camel 3.0.0.
> >
> > P.S.> It looks like the blueprint xsd for 3.0.0 is missing from the http://camel.apache.org/schema/blueprint/ at all. Is there any other place where the schemas reside (besides the camel-blueprint jar)?
> >
> > Thanks in advance,
> > Konstantin Chernov.
> >
> >
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Debugging and tracing camel-3.0.0 on OSGi
Posted by Claus Ibsen <cl...@gmail.com>.
I logged a ticket about the missing XSDs
https://issues.apache.org/jira/browse/CAMEL-14239
On Mon, Dec 2, 2019 at 3:07 PM Claus Ibsen <cl...@gmail.com> wrote:
>
> Hi
>
> You need to turn on tracing before starting Camel in Camel 3 to have JMX tracer.
>
> context.setBacklogTracing(true);
>
>
> And the poor mans debugger is a feature we no longer want to provide
> out of the box in Camel and its removed.
>
>
>
> On Mon, Dec 2, 2019 at 2:49 PM <k....@gmail.com> wrote:
> >
> > Hello.
> >
> > Is there any way to trace or debug the camel routes in 3.0.0 when starting camel context through OSGi Blueprint?
> > I tried looking for BacklogDebugger/BacklogTracer MBeans on JMX without any luck (though I can see the context/processor/routes there).
> > Debug/trace tabs just gone missing from my hawtio console after update from 2.24. I only managed to find an issue https://issues.apache.org/jira/browse/CAMEL-13759
> > stating that "There is already the newer backlog debugger that hawtio and other tools uses for debugging.", so I believe there must be a way to make it work somehow.
> > Setting trace=true on camelContext only creates a DefaultTracer, which does not seem to be reporting any notifications through JMX.
> >
> > Using Java 11 + Karaf 4.2.7 + Hawtio 2.8.0 + Camel 3.0.0.
> >
> > P.S.> It looks like the blueprint xsd for 3.0.0 is missing from the http://camel.apache.org/schema/blueprint/ at all. Is there any other place where the schemas reside (besides the camel-blueprint jar)?
> >
> > Thanks in advance,
> > Konstantin Chernov.
> >
> >
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Debugging and tracing camel-3.0.0 on OSGi
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
You need to turn on tracing before starting Camel in Camel 3 to have JMX tracer.
context.setBacklogTracing(true);
And the poor mans debugger is a feature we no longer want to provide
out of the box in Camel and its removed.
On Mon, Dec 2, 2019 at 2:49 PM <k....@gmail.com> wrote:
>
> Hello.
>
> Is there any way to trace or debug the camel routes in 3.0.0 when starting camel context through OSGi Blueprint?
> I tried looking for BacklogDebugger/BacklogTracer MBeans on JMX without any luck (though I can see the context/processor/routes there).
> Debug/trace tabs just gone missing from my hawtio console after update from 2.24. I only managed to find an issue https://issues.apache.org/jira/browse/CAMEL-13759
> stating that "There is already the newer backlog debugger that hawtio and other tools uses for debugging.", so I believe there must be a way to make it work somehow.
> Setting trace=true on camelContext only creates a DefaultTracer, which does not seem to be reporting any notifications through JMX.
>
> Using Java 11 + Karaf 4.2.7 + Hawtio 2.8.0 + Camel 3.0.0.
>
> P.S.> It looks like the blueprint xsd for 3.0.0 is missing from the http://camel.apache.org/schema/blueprint/ at all. Is there any other place where the schemas reside (besides the camel-blueprint jar)?
>
> Thanks in advance,
> Konstantin Chernov.
>
>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2