Hi Andrei, answers and comment inline. Il giorno 28/gen/2013, alle ore 16.09, Andrei Shakirin ha scritto:
> Hi, > > I am analysing problem regarding UsertTestITCase.issueSYNCOPE279(). > It is reproducible in following situations: > > 1) Run it as single test: mvn -Pdev -DwaitForCheck=false -Dit.test= > UserTestITCase# issueSYNCOPE279 Wow, strange, I implemented using these options ... > Because of some reasons this test is succeed in case if > AuthenticationTestITCase,ResourceTestITCase,RoleTestITCase,SchemaTestITCase,UserRequestTestITCase > were executed before (interesting :) ) This is really strange. issueSYNCOPE279 shouldn't have any dependency. Please, take a look at the code: it simply create a new profile giving it an ad-hoc resource (never used before). > 2) If all core integration tests is running under JDK 1.7 > 3) With some other conditions. > > My analysis shows that the end reason is that SOAP connector (using CXF > client) receives HTML as response for test() invocation: > > 15:47:46.041 DEBUG > org.identityconnectors.framework.api.operations.GetApiOp.getObject Exception: > javax.xml.ws.soap.SOAPFaultException: Response was of unexpected text/html > ContentType. Incoming portion of HTML stream: OK > at > org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:156) > ~[cxf-rt-frontend-jaxws-2.7.0.jar:2.7.0] > at $Proxy196.checkAlive(Unknown Source) ~[na:na] > at > org.connid.bundles.soap.WebServiceConnection.test(WebServiceConnection.java:89) > ~[na:na] > at > org.connid.bundles.soap.WebServiceConnector.checkAlive(WebServiceConnector.java:169) > ~[na:na] > at > org.identityconnectors.framework.impl.api.local.ConnectorPoolManager$ConnectorPoolHandler.testObject(ConnectorPoolManager.java:105) > ~[framework-internal-1.3.2.jar:na] This exception occurs after the Timeout. It is thrown by the "zombie" task. > Therefore propagation of resource "ws-target-resource-3" is failed with > following error: > > 15:46:55.221 ERROR > org.apache.syncope.core.propagation.impl.AbstractPropagationTaskExecutor - > Exception during provision on resource ws-target-resource-3 > org.apache.syncope.core.propagation.TimeoutException: Request timeout > at > org.apache.syncope.core.propagation.impl.ConnectorFacadeProxy.getObject(ConnectorFacadeProxy.java:380) > ~[ConnectorFacadeProxy.class:na] > at > org.apache.syncope.core.propagation.impl.AbstractPropagationTaskExecutor.getRemoteObject(AbstractPropagationTaskExecutor.java:438) > ~[AbstractPropagationTaskExecutor.class:na] > at > org.apache.syncope.core.propagation.impl.AbstractPropagationTaskExecutor.execute(AbstractPropagationTaskExecutor.java:288) > ~[AbstractPropagationTaskExecutor.class:na] This is the expected exception: it should be handled and returned as a SyncopeClientErrorException. > Could you give a hint how to investigate this connector invocation error? > To which instance SOAP connector sends test() request? Why it sometimes > answers with HTML? It is not a really soap resource: it is a servlet returning "OK" after a delay of 60 seconds. Syncope shouldn't take care of the result because it comes after the timeout. Regards, F.
