Ebase 4.4.1 - Problem using IIS7 with Tomcat7

[jig]

Hi All,

I have a IIS7 with ISAPI redirector to connect with Ebase 4.4.1 (tomcat7).

If I start Ebase using the batch file (stand alone mode) it works fine. But if I start Ebase as a service, I see:
Failed opening socket to (192.168.xxx.xxx:8009) (errno=60) in the IIS redirect log.

Anyone else facing or have come across this issue?

[Steve]

Hi Jig,

This might answer your question:

http://www.coderanch.com/t/517228/Tomca ... r-beginner

Could it be that the connector port inside the server.xml is not listening on port 8009?

Steve

[jig]

Hi Steve,

I had a look in server.xml. It has got 8009 and 8443:
<Define>
<Connector>

The strange thing is that it works in standalone mode but does not work when started as a service.

Just wondering if there is any difference in the way Ebase is bound to a network card/device when running in standalone mode or as a service?

Regards
Jignesh

[Steve]

Jig,

Just wondering if there is any difference in the way Ebase is bound to a network card/device when running in standalone mode or as a service?

I do not think so.

When you start the service through the services.
Run a "netstat -a" on the command line and check that the ports are listening.

I am also assuming that when you start the tomcat as a service, you can talk directly to the tomcat (i.e not got through IIS)?

Steve

[jig]

Hi Steve,

Good news! I had another issue on the server because of which I had to reboot...and this fixed the problem

But to answer your questions and if it benefits others, when I had this issue, I could directly access Tomcat i.e. without IIS.

Anyway, thanks for your help mate....it would be good to meet-up with you guys over beer

Cheers!
Regards
Jignesh

[Steve]

Jig,

Anyway, thanks for your help mate....it would be good to meet-up with you guys over beer

Only if you're paying

Steve

[jig]

Hi Steve,

Yep..I will buy!

Sorry mate but the problem just happened again...."deja vu"!

The following is the log from IIS

[Wed Mar 06 10:53:47.943 2013] [2832:2280] [info] jk_open_socket::jk_connect.c (626): connect to 192.168.83.131:8009 failed (errno=60)

[Wed Mar 06 10:53:47.945 2013] [2832:2280] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1008): Failed opening socket to (192.168.83.131:8009) (errno=60)

[Wed Mar 06 10:53:47.947 2013] [2832:2280] [error] ajp_send_request::jk_ajp_common.c (1630): (worker2) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=60)

[Wed Mar 06 10:53:47.947 2013] [2832:2280] [info] ajp_service::jk_ajp_common.c (2607): (worker2) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)

[Wed Mar 06 10:54:09.051 2013] [2832:2280] [info] jk_open_socket::jk_connect.c (626): connect to 192.168.83.131:8009 failed (errno=60)

[Wed Mar 06 10:54:09.055 2013] [2832:2280] [info] ajp_connect_to_endpoint::jk_ajp_common.c (1008): Failed opening socket to (192.168.83.131:8009) (errno=60)

[Wed Mar 06 10:54:09.056 2013] [2832:2280] [error] ajp_send_request::jk_ajp_common.c (1630): (worker2) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=60)

[Wed Mar 06 10:54:09.057 2013] [2832:2280] [info] ajp_service::jk_ajp_common.c (2607): (worker2) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)

[Wed Mar 06 10:54:09.058 2013] [2832:2280] [error] ajp_service::jk_ajp_common.c (2626): (worker2) connecting to tomcat failed.

[Wed Mar 06 10:54:09.059 2013] [2832:2280] [error] HttpExtensionProc::jk_isapi_plugin.c (2261): service() failed with http error 503

If I start tomcat in Standalone more..it works!

Regards
Jignesh

[Steve]

OK, you need to go back a post or two and run a netstat -a and check that port 8009 is open.

Also check your windows firewall. Might be something there? (Clutching at straws now, but worth a look)

Steve

[Steve]

Did you resolve this?

[jig]

Did not get a chance to look at it yet but I planning to look at it today evening.

Right now, its running in standalone mode

[jig]

Hi Steve,

I tried netstat - a and could see the port open.

As a last attempt, thought of playing with the firewall....All I did was stop the windows firewall and start it again....strange but this solved the problem.

Our Ebase now starts up as a service and IIS redirect works as well

Thanks!

Regards
Jignesh

[Steve]

Great news...

but strange all the same.

Steve