Gert Vanthienen wrote: > > Very strange. Have you tried with DEBUG logging to see if that > changes things or gives you any additional feedback? > > If you're deploying in SMX4, you can probably just create an OSGi > bundle and create the service through a Spring configuration file in > META-INF/spring.You can get a reference to the NMR using Spring DM > (<osgi:reference id="nmr" > interface="org.apache.servicemix.nmr.api.NMR" /> and inject that into > you connector bean to interact directly with the NMR, avoiding JBI > packaging and classloading entirely. >
Testing: I did testing to pin down what's going on -> here my steps working with SMX4 (fuse-esb-4.0.0.3 -> windows xp prof) -> removing data directory -> cleaning deploy directory (only activemq-broker.xml is present) -> starting SMX with debug option -> console -> switch to log -> set Log Level to DEBUG -> deploying of my mainframe communication SA (merkur.esb.host.communication.sa-1.0-SNAPSHOT.zip) Then I tried to call SMX from mainframe (with NO success) I switched to OSGI console and saw that my SA was in state "Active". The I tried to stop it. After I executed the command the console was frozen. I attached the log to this post (from the moment when my SA was deployed). I saw no irregularities. After a time the component is callable from the mainframe. But the console is still frozen. Also when I try to deploy another SA it has no effect. I see nothing in the log file. >From my point of view. For any reason: the functionality of the mainframe server part disturbs SMX. But I've no idea what I can do... :-( To your advice to create an OSGi bundle I'm not really an expert in OSGI. So I think it would be a pain to try this until it works (although the whole SMX stuff I did was not easy and painful). Until now I work with maven and this hides the whole OSGI part. When I've no other option I would spend the time. But the mainframe connection part works perfectly outside of SMX. It is (again) really frustrating to spend so much time to get all parts under a common system. TIA Regards, Martin http://www.nabble.com/file/p21807638/smxlog.txt smxlog.txt -- View this message in context: http://www.nabble.com/Running-a-Server-inside-SMX4-%28mainframe-connection-server%29-tp21788302p21807638.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
