I have same problem with SecureConversation token.
Application is CXF 2.4.1. client inside Spring context. It's consuming WS
(after SecureConversation handshake) from .NET server (WCF). It's
automaticaly downloading xml messages from .NET server every 5 min.
Everything runs OK during f.e. 2-3 days and suddenly I got SOAP Fault:
The message could not be processed. This is most likely because the action
'urn:scb-bailiffs-common:2011-04-20/ICommonServiceFunctions/RetrieveMessagesByTypeID'
is incorrect or because the message contains an invalid or expired security
context token or because there is a mismatch between bindings. The security
context token would be invalid if the service aborted the channel due to
inactivity. To prevent the service from aborting idle sessions prematurely
increase the Receive timeout on the service endpoint's binding.
>From .NEt server I got >
2011-12-12 09:49:43,396 DEBUG [org.apache.cxf.transport.http.HTTPConduit]
{org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-0} -
Header fields:
null: [HTTP/1.1 500 Internal Server Error]
Date: [Mon, 12 Dec 2011 08:49:43 GMT]
Content-Length: [1094]
Content-Type: [application/soap+xml; charset=utf-8]
Server: [Microsoft-IIS/7.5]
X-Powered-By: [ASP.NET]
... and all next WS calls returns same SOAP Fault. After restart
spring/server .. WS-SC running OK again.
Is it SC Token automaticaly renewed in CXF - after any connection/session
problem ?
Thanks for any advice ...
Martin
--
View this message in context:
http://cxf.547215.n5.nabble.com/The-security-context-token-is-expired-or-is-not-valid-ERROR-tp5076527p5120253.html
Sent from the cxf-user mailing list archive at Nabble.com.
