trouble getting quickstarts to run

[hcurtis]

When I am trying to run the quickstarts in version 4.3, I am getting the following error. Are there any recommendations for resolving this error? I am attempting to start the quickstarts in a Windows XP environment, and am using the standalone server included in the JBoss ESB distribution.

[qsjava] javax.naming.CommunicationException: Could not obtain connection to
any of these urls: localhost:1099 and discovery failed with error: javax.naming.
CommunicationException: Receive timed out [Root exception is java.net.SocketTime
outException: Receive timed out] [Root exception is javax.naming.CommunicationEx
ception: Failed to connect to server localhost:1099 [Root exception is javax.nam
ing.ServiceUnavailableException: Failed to connect to server localhost:1099 [Roo
t exception is java.net.ConnectException: Connection refused: connect]]]

[beve]

Hi,

did you simply run the run.bat script with no arguments or did you specify a bind address with the '-b' flag?

Do you have a firewall running?

Regards,

/Daniel

[hcurtis]

I simply ran run.bat with no parameters. And, I specifically disabled my firewall.

I have found other topics in this forum about this error that I'm experiencing and tried the following suggestion :

In jboss-esb.xml, I added jndi-URL="jnp://localhost:1099" in the <jms-provider> tag.

Any suggestions you have would be greatly appreciated!

[kconner]

The ConnectionRefused tells us that the service is not accessible on the localhost interface. The reasons for this could be as follows

The service is not running
The service is blocked by a firewall
The service is bound to a different interface or port

It appears that there is no firewall configured and, assuming that the service is running, that leaves the last option.

The first thing you need to check is whether you actually have a loopback interface or not as I believe windows doesn't always include one.

ipconfig /a

The second is to see whether you have something running on port 1099.

netstat -an

The above commands should show you the interfaces and open ports on your system, can you check those to see if everything is in order?

You could also try the following as a direct test of that port

telnet localhost 1099

[hcurtis]

I did not have a loopback interface, however, I just installed the Microsoft Loopback Adaptor and verified its installation using ipconfig /all

The output from netstat -an indicated that port 1099 is not in use

telnet localhost 1099 fails with the message
Connecting To localhost...Could not open connection to the host, on port 1099: Connect failed

Running run.bat in the bin directory is what starts the standalone ESB server right? When I run it, it's quite quick and comes right back to the command prompt.

[kconner]

run.bat will run the server and bring up the service listening on port 1099. You should try the telnet once the server is running.

It looks as if the original issue was the missing loopback adapter, what happens if you now run the server and try the quickstarts?

[hcurtis]

I don't think the server is starting up properly. When I execute run.bat in the bin directory, I am almost immediately returned to the command prompt. If the server was truely being started, I would have expected not to be returned to the command prompt.

After executing run.bat (after setting up the loopback adaptor) telnet localhost 1099 still failed.

[burrsutter]

an easy test to see if the server is up and running:
using a browser to hit http://localhost:8080
then the jmx-console/web-console and look for the ESB related services/MBeans.

That is always my first test to see if my server is "up" then I try the helloworld quickstart.

[kconner]

"hcurtis" wrote:
I don't think the server is starting up properly. When I execute run.bat in the bin directory, I am almost immediately returned to the command prompt. If the server was truely being started, I would have expected not to be returned to the command prompt.

I would not have expected you to have been returned to the command prompt, you should have seen a lot of console output as the server started.

Which version of java are you using? What do you get when you execute

java -version

Another thing to try would be to enable the echo for the bat file. My windows is rusty but I believe all that is required is to edit the run.bat and change the first line to the following

rem @echo off

The telnet command will work if the server is running.

[hcurtis]

just to close the loop on this ....

the problem was with the JAVA_HOME setting which included the bin directory. One the bin directory was removed from the env var, the server started right up and the quickstarts were successfully executed.

[kconner]

Okay, that makes sense. Presumably the bat script could not find the java executable in that case.