Hi Guys, I am using an Axis2 1.2 with Rampart 1.2 client that is connecting to a .NET based web service. I have found that when the client PC time is even slightly behind the server time then the Axis2/Rampart client will throw the following exception on receipt of a vaild response from the server:
Caused by: org.apache.axis2.AxisFault: The timestamp could not be validated at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:81) at org.apache.axis2.engine.Phase.invoke(Phase.java:383) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:131) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperatio n.java:378) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOpera tion.java:294) at com.mydials.DataSubmissionApiStub.About(DataSubmissionApiStub.java:183) at com.mydials.wshelper.MyDialsWSHelper.getAbout(MyDialsWSHelper.java:140) .NET based clients (running on the same client PC) do not suffer from this problem. Is there a Rampart policy setting or configuration context property that I can use to work around this? I have found that even if I synchronise the client and server pc's to the same internet time source (e.g. time.windows.com) then the difference in pc times can still be large enough to continue to raise this exception. Note that if I manually set the client PC's time to 30's after the servers time then the problem does not occur. Thanks and regards, Tim Munro
