Closed glassfishrobot closed 15 years ago
@glassfishrobot Commented @amyroh said: I confirm that with the latest workspace, JkCoyoteHandler fails to instantiate and am looking into it.
Unable to start web container LifecycleException: PWC3986: Protocol handler instantiation failed: java.lang.ClassNotFoundException: org.apache.jk.server.JkCoyoteHandler at org.apache.catalina.connector.Connector.initialize(Connector.java:1613) at com.sun.enterprise.web.connector.coyote.PECoyoteConnector.initialize(PECoyoteConnector.java:781) at com.sun.enterprise.web.WebConnector.initialize(WebConnector.java:58)
@glassfishrobot Commented @amyroh said: Sending web/web-core/osgi.bundle Transmitting file data . Committed revision 25042.
@glassfishrobot Commented jluehe said: Updated target milestone
@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-7222
@glassfishrobot Commented Reported by shaline@java.net
@glassfishrobot Commented Marked as fixed on Monday, March 2nd 2009, 3:38:20 am
V3 Build used: GlassFish promoted b37.
The requests sent to apache are not being forwarded to glassfish with both the supported modJK configurations like jkEnabled=true http-listener property and enableJK system property. On the same setup, if I replace the GlassFish with the prelude build, everything works as expected. This is a regression from prelude.
The below 2 configurations were used:
1. asadmin set server.http-service.http-listener.jk-connector.property.jkEnabled=true
2. (deprecated command provided for backward compatibility)
asadmin create-jvm-options -Dcom.sun.enterprise.web.connector.enableJK=8009
The apache and mod_jk versions used are: Apache httpd 2.2.6 and mod_jk 1.2.26-httpd-2.2.6.so .
Environment
Operating System: All Platform: All
Affected Versions
[V3]