el context,
as there is a bunch of stuff you need to do this so its correct."
--
View this message in context:
http://camel.465427.n5.nabble.com/Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194p5794547.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I did not see the problem. It is clear the list "direct-vm".
How to use camel-scr affects the "direct-vm"?
--
View this message in context:
http://camel.465427.n5.nabble.com/Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194p5794330.html
Sent from the Camel
7.n5.nabble.com/Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194p5794297.html
Sent from the Camel - Users mailing list archive at Nabble.com.
t;> at org.apache.camel.component.directvm.DirectVmProducer.
>> process(DirectVmProducer.java:56)[53:org.apache.camel.camel-core:2.17.3]
>>
>>
>> Why component "direct-vm:makeDoc" was stopped from another CamelContext?
>>
>> The error is repeat
Opened error on this topic https://issues.apache.org/jira/browse/CAMEL-10880
--
View this message in context:
http://camel.465427.n5.nabble.com/Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194p5794280.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Got a call stack is a list of all the cleaning system "dicect-vm"
In the mode "debug" error caught a third call karaf shell command.
--
View this message in context:
http://camel.465427.n5.nabble.com/Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194p57
context:
http://camel.465427.n5.nabble.com/Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194p5794246.html
Sent from the Camel - Users mailing list archive at Nabble.com.
;
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/Stop-component-direct-vm-
> from-another-OSGI-camelContext-tp5794194p5794231.html
> To start a new topic under Camel - Users,
ring & Blueprint uses proxy. It does not consider that the component is
not available. Breaking to him and takes off in the most unexpected place.
SCR is predicted in this regard.
--
View this message in context:
http://camel.465427.n5.nabble.com/Stop-component-direct-vm-from-another-OSGI-came
team from the second OSGI bundle will work one more time.
We are waiting for 5-7 seconds. Execute the command. There is a mistake.
--
View this message in context:
http://camel.465427.n5.nabble.com/Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194p5794229.html
Sent from the Camel
he same JVM.
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/Stop-component-direct-vm-
> from-another-OSGI-camelContext-tp5794194p5794206.html
> To start a new topic
e same JVM.
--
View this message in context:
http://camel.465427.n5.nabble.com/Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194p5794206.html
Sent from the Camel - Users mailing list archive at Nabble.com.
>
> Why component "direct-vm:makeDoc" was stopped from another CamelContext?
>
> The error is repeated in the next versions
> camel 2.17.3
> camel 2.18.2
>
>
>
>
> Aleksey
>
> --
> If you reply to this email, your message w
ext versions
camel 2.17.3
camel 2.18.2
Aleksey
--
View this message in context:
http://camel.465427.n5.nabble.com/Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194.html
Sent from the Camel - Users mailing list archive at Nabble.com.
14 matches
Mail list logo