WarpConnector: Invalid packet with type 1

[tmorris1]

I'm at wit's end on this one. Does anyone have a suggestion?

II and Tomcat seem to be talking but socket errors...

2003-11-03 13:18:56 [org.apache.catalina.connector.warp.WarpConnector] Connection from /127.0.0.1:1064 to /127.0.0.1:8008
2003-11-03 13:18:56 [org.apache.catalina.connector.warp.WarpConfigurationHandler] Invalid packet with type 1
2003-11-03 13:18:56 [org.apache.catalina.connector.warp.WarpConnection] Exception on socket
java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at org.apache.catalina.connector.warp.WarpConnection.send(Unknown Source)
at org.apache.catalina.connector.warp.WarpConfigurationHandler.handle(Unknown Source)
at org.apache.catalina.connector.warp.WarpConnection.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)


Here's the meat of the server.xml file:

<!-- Define an Apache-Connector Service -->

<Service name=&quot;Tomcat-Apache&quot;>
<Connector ClassName=&quot;org.apache.ajp.tomcat4.Ajp13Connector&quot;
port=&quot;8009&quot; minProcessors=&quot;5&quot; maxProcessors=&quot;75&quot;
enableLookups=&quot;true&quot; appBase=&quot;webapps&quot;
acceptCount=&quot;10&quot; debug=&quot;0&quot;/>
<Connector className=&quot;org.apache.catalina.connector.warp.WarpConnector&quot;
port=&quot;8008&quot; minProcessors=&quot;5&quot; maxProcessors=&quot;75&quot;
enableLookups=&quot;true&quot; appBase=&quot;webapps&quot;
acceptCount=&quot;10&quot; debug=&quot;0&quot;/>
<Engine className=&quot;org.apache.catalina.connector.warp.WarpEngine&quot;
name=&quot;Apache&quot; debug=&quot;0&quot;>
<Logger className=&quot;org.apache.catalina.logger.FileLogger&quot;
prefix=&quot;apache_log.&quot; suffix=&quot;.txt&quot;
timestamp=&quot;true&quot;/>
<Realm className=&quot;org.apache.catalina.realm.MemoryRealm&quot; />
</Engine> </Service>
</Server>


And the meat of the workers.properties file:

worker.list=ajp12, ajp13
#worker.list=ajp13

# ajp13 connector communicating on port 8009
#
worker.ajp13.port=8009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13
worker.ajp13.lbfactor=50
worker.ajp13.cachesize=10
worker.ajp13.cache_timeout=600
worker.ajp13.socket_keepalive=1
worker.ajp13.socket_timeout=300

# ajp12 communicates on port 8008
#
worker.ajp12.port=8008
worker.ajp12.host=localhost
worker.ajp12.type=ajp12
worker.ajp12.lbfactor=1
worker.ajp12.cachesize=10
worker.ajp12.cache_timeout=600
worker.ajp12.socket_keepalive=1
worker.ajp12.socket_timeout=300

#
# load balancing
#
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers=ajp12, ajp13

And the uriworkers.properties file:

/mpdbapp/*=ajp13
/mpdbapp/*.jsp=ajp13
/*.jsp=ajp13
*.jsp=ajp13


Here's the last few lines of the ISAPI log (debug level):

[Mon Nov 03 13:18:56 2003] [jk_isapi_plugin.c (426)]: Into jk_ws_service_t::read
[Mon Nov 03 13:18:56 2003] [jk_ajp12_worker.c (459)]: ajpv12_handle_request, read 12 bytes
[Mon Nov 03 13:18:56 2003] [jk_ajp12_worker.c (467)]: ajpv12_handle_request, sent 12 bytes
[Mon Nov 03 13:18:56 2003] [jk_ajp12_worker.c (477)]: ajpv12_handle_request done
[Mon Nov 03 13:18:56 2003] [jk_ajp12_worker.c (148)]: In jk_endpoint_t::service, sent request
[Mon Nov 03 13:18:56 2003] [jk_ajp12_worker.c (493)]: Into ajpv12_handle_response
[Mon Nov 03 13:18:56 2003] [jk_ajp12_worker.c (507)]: ajpv12_handle_response, read

[Mon Nov 03 13:18:56 2003] [jk_ajp12_worker.c (522)]: ajpv12_handle_response, no value supplied
[Mon Nov 03 13:18:56 2003] [jk_isapi_plugin.c (724)]: HttpExtensionProc error, service() failed
[Mon Nov 03 13:18:56 2003] [jk_ajp12_worker.c (163)]: Into jk_endpoint_t::done

 

[tmorris1]

I figured out the solution on my own. All I had to do was to configure Tomcat for SSL. My web application was configured in IIS 5.0 with a server certificate and was sending SSL packets to Tomcat. Since Tomcat wasn't listening or expecting the packets in this format, the Warp connector was bombing. Other connectors such as Coyote and Ajp13 had reported &quot;bad signature on packet&quot;. Once an connector was established on port 8443 for SSL, the problem was resolved. Thanks for such an underwhelming response on Tech-Tips. Hopefully this thread will help someone.