000032021 - ITIM integration collector random failure using RSA Via L&G

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000032021
Applies ToRSA Product Set: Identity Management and Governance
 
IssueThe ITIM integration collector fails and reports the error message below in the aveksaAgent.log file.
ERROR (Thread-4) [com.aveksa.client.component.communication.ChangeListHandler] CLH70: 
com.aveksa.client.datacollector.agent.ServerUnavailableException: com.aveksa.server.agent.message.ConnectionException: java.net.BindException: Address already in use
at com.aveksa.client.component.communication.DefaultCommunicationManager.getChangeList(DefaultCommunicationManager.java:203)
at com.aveksa.client.component.communication.ChangeListHandler.getChangesFromServer(ChangeListHandler.java:235)
at com.aveksa.client.component.communication.ChangeListHandler.run(ChangeListHandler.java:129)
at com.aveksa.client.component.communication.DefaultCommunicationManager$1.run(DefaultCommunicationManager.java:543)
Caused by:
com.aveksa.server.agent.message.ConnectionException: java.net.BindException: Address already in use
at com.aveksa.server.agent.message.HTTPBroker.httpPost(HTTPBroker.java:158)
at com.aveksa.server.agent.message.HTTPBroker.send(HTTPBroker.java:85)
at com.aveksa.server.agent.message.ServerBroker.getChanges(ServerBroker.java:296)
at com.aveksa.client.datacollector.agent.ServiceManager.getChangeList(ServiceManager.java:123)
at com.aveksa.client.component.communication.DefaultCommunicationManager.getChangeList(DefaultCommunicationManager.java:195)
... 3 more
Caused by:
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:398)
at java.net.Socket.bind(Socket.java:582)
at java.net.Socket.<init>(Socket.java:392)
at java.net.Socket.<init>(Socket.java:267)
at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:79)
at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:121)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
at com.aveksa.server.agent.message.HTTPBroker.httpPost(HTTPBroker.java:155)
... 7 more

 
CauseThe ITIM agent fails to start due to the port being used by another process.
ResolutionTo resolve the issue, perform one of the actions below.
  • Change port of the other process to avoid conflicting with ITIM agent
  • Change the ITIM Agent port by editing the aveksa-plug-ins.xml file located under <AVEKSA_WAR_DIR>/WEB-INF/plug-ins/ ITIM2FulfillmentHandler/aveksa-plug-ins.xml
For example, on WebLogic and WebSphere you must edit the /aveksa-plug-ins.xml file in your customized EAR in the CUSTOMIZATION directory:
<CUSTOMIZATION>/aveksa_ear/aveksa.war/WEB-INF/plug-ins/ITIMFulfillmentHandler
Edit the aveksa-plug-ins file as follows:
Change <value>iiop://localhost:2809</value> for name platformURL to <value>iiop://ITIM_HOST:ITIM_NEW_PORT </value>
The file must be redeployed after the customization has been completed. 



See the installation guide for WebSphere or WebLogic for information about the customization of the RSA IAM Platform application.

Attachments

    Outcomes