I reproduce on Linux lot of time but not always (really weird) using Felix.
After switching to Equinox (etc/custom.properties using
karaf.framework=equinox), I can't reproduce the issue:
karaf@root> features:install camel-nmr
Refreshing bundles org.apache.servicemix.document (81)
karaf@root>
So the issue is not linked to ServiceMix itself. I think that we go to
the release like this and update to new Karaf/Felix version in the next
release.
Regards
JB
On 02/14/2011 03:43 PM, Kurt Westerfeld wrote:
Just another bit of info...if I use the org.apache.servicemix/apache-servicemix/
and do the following after startup, this distro works:
karaf@root> features:install camel-nmr
Refreshing bundles org.apache.servicemix.document (78)
Notice the "Refreshing bundles..."....that must be the reason for the shutdown?
No idea about that. To me, I'd say its more likely the wsn2005 component is the culprit
on the deadlock during shutdown.
Jean-Baptiste Onofré<[email protected]> 2/14/2011 9:14 AM>>>
The release is now canceled.
I'm fixing the ODE issue first and take a look on the second one (I will
certainly raise a Jira about that).
Regards
JB
On 02/14/2011 03:14 PM, Kurt Westerfeld wrote:
(New, non-ODE issue I found just now).
I'm not sure this is expected or not, or what to make of this, but I
just did the following (causing shutdown + deadlock):
- download distro
- run bin/karaf
- wait for system to settle down
- perform "features:install camel-nmr"
The system attempts to shutdown at this point. During shutdown, with a
three-way a thread deadlock between two wsn2005 threads and the karaf
shell console thread (the shell becomes unresponsive):
Found one Java-level deadlock:
=============================
"pool-component.servicemix-wsn2005.consumer-thread-4":
waiting to lock monitor 0x00000000328272e0 (object 0x0000000028bdd5a0, a
org.apache.servicemix.wsn.component.WSNComponent),
which is held by "pool-component.servicemix-wsn2005.consumer-thread-2"
"pool-component.servicemix-wsn2005.consumer-thread-2":
waiting to lock monitor 0x0000000032828c78 (object 0x000000000ba26770, a
org.apache.servicemix.nmr.management.ManagementAgent),
which is held by "Karaf Shell Console Thread"
"Karaf Shell Console Thread":
waiting to lock monitor 0x000000002cf2b7b8 (object 0x0000000028c1f290, a
org.apache.servicemix.common.DefaultServiceUnit),
which is held by "pool-component.servicemix-wsn2005.consumer-thread-2"
I tried repeating this issue and it is 100% reproducible. I blew away
the "data" directory, retried, and blew away the entire bundle,
re-unzipped, and tried this, and it is definitely happening. I believe
the shutdown starts because something is not in the system repo that
camel-nmr needs, but I can't imagine why.
>>> " Jean-Baptiste Onofré"<[email protected]> 2/13/2011 9:49 AM>>>
Hi,
We solved 113 issues in this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311208&version=12315741
<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311208&version=12315741>
NB: comparing to the previous 4.3.0 vote, this new one include support
of ODE 1.3.5.
Staging repository:
https://repository.apache.org/content/repositories/orgapacheservicemix-058/
The RELEASE-NOTE file in included in the release and up to date.
Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)
This vote will be open for 72 hours.
Thanks,
Regards
JB
