[
https://issues.apache.org/jira/browse/AXIS2-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-5517:
-----------------------------------
Fix Version/s: (was: 1.7.0)
1.7.1
> Unable to find corresponding context for the serviceGroupId: XXXXX error
> ------------------------------------------------------------------------
>
> Key: AXIS2-5517
> URL: https://issues.apache.org/jira/browse/AXIS2-5517
> Project: Axis2
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.6.2
> Reporter: Finn Baggesen
> Fix For: 1.7.1
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> It is possible when running axis in high-loaded system to get the error
> 'Unable to find corresponding context for the serviceGroupId: XXXXX'. This is
> caused by the serviceGroupContext does not have a timestamp and the cleanup
> process will in some cases invalidate the serviceGroupContext.
> Proposed change to kernel module
> (org.apache.axis2.context.ConfigurationContext.java)
> public void addServiceGroupContextIntoSoapSessionTable(
> ServiceGroupContext serviceGroupContext) {
> String id = serviceGroupContext.getId();
>
> /* Fix: Touch needs to be done before added to map */
> serviceGroupContext.touch();
> serviceGroupContextMap.put(id, serviceGroupContext);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
