[
https://issues.apache.org/jira/browse/AXIS2-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678651#action_12678651
]
Gary McWilliams commented on AXIS2-3791:
----------------------------------------
I checked here:
http://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_3/modules/kernel/src/org/apache/axis2/transport/http/AxisServlet.java
the code is not changed. Of course, now I realise that 1.3 Axis2 is old, and
probably no longer maintained, and that the latest releases may well be a lot
better (there is no AxisServlet I can find, and OSGiAxisServlet does not
implement the init() method).
My background here is that Apache ODE ships with Axis2 1.3 built-in and that is
where I am seeing the problem. I have already submitted another patch to ODE
which may well alleviate this issue within ODE.
> Endlesloop in AxisServlet init (Websphere 6.1 deployment)
> ---------------------------------------------------------
>
> Key: AXIS2-3791
> URL: https://issues.apache.org/jira/browse/AXIS2-3791
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: transports
> Affects Versions: 1.3
> Environment: Solaris-10
> Websphere 6.1
> java version "1.5.0_13"
> Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_13-b05
> 20071004)
> Java HotSpot(TM) Server VM (build 1.5.0_13-b05, mixed mode)
> IBM Java ORB build orb50-20070915 (SR6)
> XML build XSLT4J Java 2.7.9
> XML build IBM JAXP 1.3.7
> XML build XML4J 4.4.11
> Reporter: martin voegeli
> Assignee: Deepal Jayasinghe
> Priority: Minor
> Attachments: diff.txt
>
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> Wrong usage of servlet init procedure leads to endlessloop, if container
> issues init method twice.
> =>
> http://java.sun.com/j2ee/1.4/docs/api/javax/servlet/GenericServlet.html#init(javax.servlet.ServletConfig)
>
> [5/7/08 14:55:37:535 MEST] 00000036 ServletWrappe E SRVE0100E: Did not
> realize init() exception thrown by servlet AxisServlet:
> java.lang.StackOverflowError
> at javax.servlet.GenericServlet.init(GenericServlet.java:256)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:413)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:487)
> at javax.servlet.GenericServlet.init(GenericServlet.java:256)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:413)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:487)
> AxisServlet.java:
> public void init(ServletConfig config) throws ServletException {
> 413 super.init(config);
> try {
> this.servletConfig = config;
> ...
> GenericServlet.java
> public void init(ServletConfig config)
> throws ServletException
> {
> this.config = config;
> init();
> }
> AxisServlet.java:487:
> /**
> * Convenient method to re-initialize the ConfigurationContext
> *
> * @throws ServletException
> */
> public void init() throws ServletException {
> if (this.servletConfig != null) {
> 487 init(this.servletConfig);
> }
> }
> After reinstalling the websphere server, the issue was resolved. Seems, that
> WAS6.1 has some buggy state too. Maybe you can handover the issue to IBM ;-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
