-
Bug
-
Resolution: Won't Do
-
Major
-
jboss-fuse-6.3
-
None
-
%
-
Sprint 7 - towards CR2
When one creates bundle with
- following camel routes
- camel connects to two AMQ Brokers
- camel can't connect to those brokers (firewall Drop or there is nothing listening on given port)
- bundle deployed to fuse fabric / child container with profile
one ends up with "deadlock" where container is forewer stuck in "installing" state
JBossFuse:fafram@root> container-list
[id] [version] [type] [connected] [profiles] [provision status]
root* 1.0 karaf yes fabric success
fabric-ensemble-0000-1
jboss-fuse-full
child1 1.0 karaf yes default installing
okw-xlate-customer
because fabric agent thread is waiting for camel jms consumer threads which are blocked by fabric thread
more about dumpling (http://olivergondza.github.io/dumpling/cli.html)
Listing of selected threads along with stack traces: stacktrace.txt
./dumpling.sh blocking-tree --in=process:19752 "fabric-agent-86.0.1-deployer-4-thread-1" #236 prio=5 tid=140581529976832 nid=21787 "Camel (xlate-customer) thread #1 - JmsConsumer[cholesterol]" #378 daemon prio=5 tid=140581330354176 nid=23876 "Camel (xlate-customer) thread #2 - JmsConsumer[calcium]" #395 daemon prio=5 tid=140581393455104 nid=24025
From this point it's not possible to assign or unassign any fabric profile from child container.
- is related to
-
AMQ-5588 Loading...
-
