I still haven't managed to get this to work, despite trying to use the
lightweight ftp component instead of servicemix-ftp, and packaging it up
into the lightweight container. 

I thought that I'd try a 2-way communication between 2 pojos while I hoped
somebody might have some ideas. Interestingly I'm getting the following
exception when pojo 1 sends to pojo 2 :

17:27:09,562 | ERROR |
pool-flow.jca.org.apache.servicemix.jca.{http://servicemix.apache.org/nftest}nfreceiver:nfreceiver-thread-2
| ActiveMQEndpointWorker   | vemq.ra.ActiveMQEndpointWorker  245 | Endpoint
connection to JMS broker failed: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.ConnectException: Connection
refused: connect

I've seen a post elsewhere suggesting that JMS problems could cause the
original not-initialised error.

I've disabled my firewall, and because I'm not on a network I've removed the 
discoveryUri="multicast://default" from the following line in activemq.xml
:-
<transportConnector uri="tcp://localhost:61616"
discoveryUri="multicast://default"/>
as suggested in the comments. 

Using a socket tracer I see 15 sockets have been made to port 61616, but
they're all in TIME_WAIT closing state after I try my pojo-pojo test. If I
don't run the test there are 15 connected sockets to port 61616, so there
isn't a problem with the port already in use etc. 

I'm running java 1.5, servicemix 3.1.2 on a Windows XP SP2 box.

I'm at my wits end now - any ideas would really be appreciated.

Cheers, 
BM




-- 
View this message in context: 
http://www.nabble.com/Error-calling-DONE-on-InOnly-message-tf4718625s12049.html#a13497777
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to