Gert Vanthienen wrote: > > I don't see any real reason why your approach would not work. Running > this server connection inside a servicemix-bean POJO should work just > fine, I think. Perhaps something is wrong in the initialization order > of thing. You could fine-tune that by using the @PostConstruct and > @PreDestroy annotations. When the container is hanging at startup, > could you take a look at the threads through JMX or take a thread to > figure out what it is waiting for? >
Gert, I put the initialization of the server in a @PostConstruct marked method. I see in the log file that the server process is initialized. Nevertheless, when I depoy the SA it doesn't work. When I do a new start of the component via the osgi console (of course after stopping) the communication between mainframe and SMX4 works. The server process uses threads to handle incoming calls from the mainframe. Could this be the reason for problems? Also, it seems that other components (SA's) are influenced when the SA containing the server process is deployed. e.g. first deploying the SA which contains the server process. -> then deploying other components (SA's) -> the SA's are not callable -> I see in the console that the have only a status "Installed" and I'm not able to start the components There are also no error entries in the log. Can you imagine another (simple) solution to start the server process inside SMX4? TIA Martin -- View this message in context: http://www.nabble.com/Running-a-Server-inside-SMX4-%28mainframe-connection-server%29-tp21788302p21789695.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
