Hi,
We installed xmatters alarmpoint 4.1.0 build.696 on Windows 2008 R2 VM node.
Alarmpoint installed succesfully and the jetty web server is accessible with the default url http://server/alarmpoint/signOn.do
Now we are fronting the Alarmpoint (Jetty) webserver with IIS (7.5) on the localhost itself.
We used the documentation from Alarmpoint and implemented the Jakarta Isapi Redirector solution by manually steps. And we explicit configured the application pool for 32 bits applications, as Alarmpoint is.
After a IIS restart we see that the isapi_redirect.dll is not loaded and we get eventID errors 2214 and 2268. On the M$ site they say that the dll is mostly not correct.
http://technet.microsoft.com/en-us/library/dd349245(WS.10).aspx
So it could be because of the version that Alarmpoint delivers, but also with the newest 32 bits version of isapi_redirect.dll we get the same problem.
After that we loaded the 64 bits version and this one is working correctly in IIS 7.5. We can acces the http://localhost:81/jkmanager page correctly, but the http://localhost:81/alarmpoint/ is not working.
We get the following error in our browser. Also with setting a isapi timeout it still occurs.
502 - Web server received an invalid response while acting as a gateway or proxy server.
In the isapi.log ( debugmode) we see the error below.
[Thu Jul 21 09:49:23.490 2011] [3332:6292] [info] ajp_connection_tcp_get_message::jk_ajp_common.c (1266): (alarmpoint) can't receive the response header message from tomcat, tomcat (127.0.0.1:8899) has forced a connection close for socket 536
[Thu Jul 21 09:49:23.491 2011] [3332:6292] [error] ajp_get_reply::jk_ajp_common.c (2118): (alarmpoint) Tomcat is down or refused connection. No response has been sent to the client (yet)
[Thu Jul 21 09:49:23.492 2011] [3332:6292] [info] ajp_service::jk_ajp_common.c (2607): (alarmpoint) sending request to tomcat failed (recoverable), (attempt=1)
In the webserver main/error logs we see the following
main.log
2011-07-21 08:15:33,784 [main] INFO - AJP13 is not a secure protocol. Please protect port 8899
2011-07-21 08:15:33,789 [main] INFO - Started Ajp13SocketConnector@0.0.0.0:8899
errors.log
2011-07-21 09:49:23,484 [pool-1-thread-7] ERROR org.mortbay.log - handle failed
java.lang.NullPointerException
at org.mortbay.jetty.ajp.Ajp13Connection$RequestHandler.parsedRequestAttribute(Ajp13Connection.java:181)
at org.mortbay.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:397)
at org.mortbay.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:142)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:227)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2011-07-21 09:49:23,654 [pool-1-thread-8] ERROR org.mortbay.log - handle failed
java.lang.NullPointerException
at org.mortbay.jetty.ajp.Ajp13Connection$RequestHandler.parsedRequestAttribute(Ajp13Connection.java:181)
at org.mortbay.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:397)
at org.mortbay.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:142)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:227)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
See attachments for more info.
Does anyone has allready got this working (with 32 bits isapi_redirect.dll) on Windows 2008 R2?
Is this tested when Windows 2008 R2 support was delivered?
With the 64 bits isapi_redirect the forwarding function is working, but not accepted by the jetty server ( mostly because of this is a 32 bits webserver).