Yes, I think that you should similar entries on instance#2 indicating the
remote service sucessfully registered.
So I found out why my service is not being registered on instance#2 ... when
it is deployed on instance#2, it only gets 'installed'. When I try to start
it with 'osig:start <id>'. I get:
The bundle could not be resolved. Reason: Missing Constraint:
Import-Package: META-INF.cxf.transport.nmr; version="0.0.0"
... which is really confusing since the same bundle can be deployed and
started successfully on instance#1.
I believe the reason may have something to do (either directly or
indirectly) with instance#2 having a different configuration in activemq.xml
to create the cluster (different port numbers, etc.). To prove this, I
copied instance#1 somewhere and changed the activemq.xml (and also the rmi
port in some karaf config file) to the same config as instance#2, and the
problem
So maybe this points to the cluster being incorrectly configured ... even
though I'm getting the handshake log entries in the log like you were (...
Network connection between vm://pritam#0 and
tcp://dolphin/192.168.2.96:61616(aditya) has been established. ).
I am also seeing a log entry that is troubling:
08:42:45,342 | INFO | Event Dispatcher | ultOsgiApplicationContextCreator |
ultOsgiApplicationContextCreator 67 | Discovered configurations
{osgibundle:/META-INF/spring/*.xml} in bundle [null (localhost-broker.xml)]
You may want to look at your log for any errors having to do MBeans.
BTW, I have no idea how to fix the Missing Constraint issue because the
'META-INF.cxf.transport.nmr' is indeed in the <Import-Package> section of
the pom.
Possibly there is an uninstalled osgi feature that we're missing, that can
be installed from the console.
I sure wish the genius that created the SMX 4 clustering capability would
enlighten us.
- Bret
--
View this message in context:
http://old.nabble.com/Servicemix-4.2-clustering-issues.-tp28729394p28731954.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
