You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Hans G Knudsen (JIRA)" <ji...@apache.org> on 2008/04/24 14:03:21 UTC
[jira] Commented: (SANDESHA2-133) Memory Leak using Replay Model
[ https://issues.apache.org/jira/browse/SANDESHA2-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591999#action_12591999 ]
Hans G Knudsen commented on SANDESHA2-133:
------------------------------------------
Hi!
The test service + client I supplied for
https://issues.apache.org/jira/browse/SANDESHA2-146
can be used to test this by calling
new ReplayEchoClient().run(true, false, "rm");
/hans
> Memory Leak using Replay Model
> ------------------------------
>
> Key: SANDESHA2-133
> URL: https://issues.apache.org/jira/browse/SANDESHA2-133
> Project: Sandesha2
> Issue Type: Bug
> Affects Versions: 1.4
> Environment: Axis2 / Sandesha2 trunk
> Reporter: Hans G Knudsen
>
> Hi!
> Sessions does not get cleaned up when the client is set up to use Replay Model.
> The log line :
> 2008-01-07 13:51:26,663 [WARN] org.apache.sandesha2.workers.Sender - A WS-Reliable messaging protocol message 7 has been waiting for a MakeConnection call. The message will continue to wait, but there may be a problem with the client configuration.
> is written every minute well beyond the SequenceRemovalTimeout ...
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org