Hello,
I am getting this error during synchronization of Aris 9.8.11 with solman 7.2
The error occurs only when I transfer large chunks of data. But when I transfer same processes one by one, I am not getting this error. Has anyone encountered this error? The description of error is not informative, so we don't know where to look for the problem.
This is from synchronization log:
Error writing data to SAP. Erromessage from the SAP sytsem is: ResponseCode: 401
This is aris client log:
Tue Aug 27 10:33:06 ALMT 2019: node accepted: Operations Test
Tue Aug 27 10:34:20 ALMT 2019: java.lang.NullPointerException
Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.serverproxy.solar.ASM72Proxy.convert(ASM72Proxy.java:197)
Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.serverproxy.solar.ASM72Proxy.synchronize(ASM72Proxy.java:133)
Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.components.solar.logic.actions.ADownloadProjectAction.download(ADownloadProjectAction.java:166)
Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.components.solar.logic.actions.ADownloadProjectAction.execute(ADownloadProjectAction.java:74)
Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.framework.menuAccess.OperationActionManager.execute(OperationActionManager.java:107)
Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.framework.menuAccess.OperationActionManager.actionPerformed(OperationActionManager.java:76)
Tue Aug 27 10:34:20 ALMT 2019: at com.aris.framework.flamingo.api.common.AbstractCommandButton.fireActionPerformed(AbstractCommandButton.java:673)
Tue Aug 27 10:34:20 ALMT 2019: at com.aris.framework.flamingo.api.common.AbstractCommandButton$ActionHandler.actionPerformed(AbstractCommandButton.java:626)
Tue Aug 27 10:34:20 ALMT 2019: at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
Tue Aug 27 10:34:20 ALMT 2019: at com.aris.framework.flamingo.api.common.model.ActionRepeatableButtonModel.setPressed(ActionRepeatableButtonModel.java:126)
Tue Aug 27 10:34:20 ALMT 2019: at com.aris.framework.flamingo.internal.ui.common.BasicCommandButtonListener.mouseReleased(BasicCommandButtonListener.java:184)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:289)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:289)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Component.processMouseEvent(Component.java:6539)
Tue Aug 27 10:34:20 ALMT 2019: at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Component.processEvent(Component.java:6304)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Container.processEvent(Container.java:2239)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Component.dispatchEventImpl(Component.java:4889)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Container.dispatchEventImpl(Container.java:2297)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Component.dispatchEvent(Component.java:4711)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4904)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4535)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4476)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Container.dispatchEventImpl(Container.java:2283)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.Component.dispatchEvent(Component.java:4711)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:760)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue.access$500(EventQueue.java:97)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue$3.run(EventQueue.java:709)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue$3.run(EventQueue.java:703)
Tue Aug 27 10:34:20 ALMT 2019: at java.security.AccessController.doPrivileged(Native Method)
Tue Aug 27 10:34:20 ALMT 2019: at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
Tue Aug 27 10:34:20 ALMT 2019: at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:84)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue$4.run(EventQueue.java:733)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue$4.run(EventQueue.java:731)
Tue Aug 27 10:34:20 ALMT 2019: at java.security.AccessController.doPrivileged(Native Method)
Tue Aug 27 10:34:20 ALMT 2019: at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventQueue.dispatchEvent(EventQueue.java:730)
Tue Aug 27 10:34:20 ALMT 2019: at com.aris.modeling.client.container.common.AFocusManager.dispatchEvent(AFocusManager.java:164)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
Tue Aug 27 10:34:20 ALMT 2019: at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
Hi Di Smith,
This error "ResponseCode: 401" is coming from SAP system and shows in ARIS side.
Usually this means that error 401 "Unauthorized" appears when the session of the user is no valid in SAP side.
The time between the initial synchronization until this error I would say this is more than 1 hour, and can be the time of session in SAP side is limited.
In that case you have to contact the SAP administrator to help with this matter.
We had similar issues related to this error and the version ARIS 10 SR7 or higher fixed any timeout issue and also speed up the synchronization in general.
Other thing, we also had an customer where faced the same and he fixed the timeout in SAP side but also re-organized an process library which was using around 1500 process in a single folder. As best practices the new folders have been create in parallel of this process library to keep separated of one folder instead.
I hope this help you..
BR
Thank you for your reply. I just wanted to report that SAP Basis team finally could solve the issue. It was indeed a timeout problem. These two parameters needed to be changed to avoid the problem:
rdisp/plugin_auto_logout
http/security_session_timeout
as well as these ones:
icm/server_port[0] = PROT=HTTP PORT TIMEOUT PROCTIMEOUT
icm/server_port[2] = PROT=HTTPS PORT TIMEOUT PROCTIMEOUT