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 "David Illsley (JIRA)" <ji...@apache.org> on 2008/03/02 22:26:50 UTC
[jira] Resolved: (SANDESHA2-68) soapenv:Header is sometimes not
filled for the CreateSequence request
[ https://issues.apache.org/jira/browse/SANDESHA2-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Illsley resolved SANDESHA2-68.
------------------------------------
Resolution: Cannot Reproduce
So much has changed since Sandesha2 1.0, it's really unlikely this problem still exists in the same form.
Please reopen if you can reproduce on Sandesha2 1.3 or a recent nightly.
Apologies for the long silence...
David
> soapenv:Header is sometimes not filled for the CreateSequence request
> ---------------------------------------------------------------------
>
> Key: SANDESHA2-68
> URL: https://issues.apache.org/jira/browse/SANDESHA2-68
> Project: Sandesha2
> Issue Type: Bug
> Environment: Sun Solaris 2.9, Java 5, Axis2 (1.1.1), Sandesha2 (1.0)
> Reporter: Michael Schick
> Attachments: Client.zip
>
>
> From time to time I observe the failure "Operation not found EPR is and WSA = null".
> If this error happens, then the first "createSequence" call does not seem to have any details in the soap header !
> Re-running exactly the same client without change works suddenly again.
> I see this error however more often, when log4j logging is set to ALL.
--
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