[
https://issues.apache.org/jira/browse/ODE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Riou resolved ODE-529.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Matthieu Riou
I've added the empty close method. Committed in the 1.x branch.
> Prevent StackOverflowError when deploying on Websphere 6.1
> ----------------------------------------------------------
>
> Key: ODE-529
> URL: https://issues.apache.org/jira/browse/ODE-529
> Project: ODE
> Issue Type: Improvement
> Affects Versions: 1.2
> Reporter: Gary McWilliams
> Assignee: Matthieu Riou
> Fix For: 1.3
>
>
> There is "potential" for a loop condition (leading to a StackOverflowError)
> on WAS 6.1. I present here the results of finding through working with IBM on
> this issue. Our client did suffer from the StackOverflowError, but I resolved
> that by modifying the Axis-2 code
> (https://issues.apache.org/jira/browse/AXIS2-3791). However it could also be
> caused by an ODE issue rather than an Axis2 issue:
> The class hierarchy is
> ODEAxisServlet extends AxisServlet extends HttpServlet which extends Generic
> servlet.
> ODEAxisServlet implements init(config) which calls super.init(config) This
> resolves to AxisServlet init(config) which calls super.init(config) This
> resolves to GenericServlet init(config) which calls init() AxisServlet
> implements init(), but ODEAxisServlet does not, so this resolves to
> AxisServlet init() which calls init(config) ODEAxisServlet implements
> init(config) so this resolves to that method and the loop starts.
> Given that GenericServlet has always been implemented like this without any
> issues reported the real problem appears to be in AxisServlet because its
> init method calls init(config). However the easiest fix may be for
> ODEAxisServlet to implement an empty init() method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
