Re: Problem mixing connectors TCP & HTTP

We had a similar problem few days ago with the embedded JNDI....
take a look to the con figuration file openjms.xml
and change the line
<ServerConfiguration host="localhost" embeddedJNDI="true" />

to:
<ServerConfiguration host="real_IP" embeddedJNDI="true" />

hope it helps

* Ermengol *

Fernando Zuriaga wrote:
> Hi, I have an openjms server (0.7.7-alpha1) configured with two
> conectors: one for http clients (tunnel servlet) and one for local
> access (TCP). The configuration file is:
>
> <Configuration>
>   <!-- Optional. This represents the default configuration  -->
>   <ServerConfiguration host="XXXXXXXXX" embeddedJNDI="true" />
change localhost to your IP
> javax.naming.ServiceUnavailableException: Failed to connect to
> URI=tcp://66.35.250.177:3035/ [Root exception is org.exolab.jms.net.c
> onnector.ConnectException: Failed to connect to URI=tcp://66.35.250.177:3035/]
>
> I don't know why openjms try to connect to 66.35.250.177 ???. I want
> to connect to localhost, I don't write this Ip direcction into my
> program.
>   



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click