on 07-23-2013 11:16 AM
Hi Gurus,
This is regarding an issue we are facing while transporting a Message Mapping object to PRD. We did not face the issue while we moved it to DEV. We are on the dual stack 7.3 version and following are the error details:
ClientServerException exception:Import failed: Internal error when importing object [Lcom.sap.aii.ib.bom.workspace.IWorkspace;@6cb2
d119
com.sap.aii.utilxi.misc.api.ResourceException: Import failed: Internal error when importing object [Lcom.sap.aii.ib.bom.workspace.I
Workspace;@6cb2d119
Caused by: com.sap.aii.utilxi.misc.api.ResourceException: Import failed: Internal error when importing object [Lcom.sap.aii.ib.bom.
workspace.IWorkspace;@6cb2d119
Caused by: com.sap.aii.ib.server.propagation.XIPropagationException: Internal error when importing object [Lcom.sap.aii.ib.bom.work
space.IWorkspace;@6cb2d119
Caused by: com.sap.aii.ib.server.pvcadapt.XIPropProviderException: Internal error when importing object [Lcom.sap.aii.ib.bom.worksp
ace.IWorkspace;@6cb2d119
#at com.sap.aii.ibrep.server.pvcadapt.XIRepPropMetaDataProvider.setData(XIRepPropMetaDataProvider.java:216)
#... 99 more
Caused by: com.sap.aii.ib.server.jms.MessageException: Cannot allocate connection.
Caused by: javax.jms.JMSException: Cannot allocate connection.
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: Error in ResourceSet.addAndEnlist(com.sap.engine.se
rvices.connector.resource.impl.HandleWrapper@62b4d37[Hashcode:171733297
resource.impl.MCEventHandler@43377060 -> com.sap.engine.services.jmsconnector.spi.TopicManagedConnectionImpl@58545b65(locTrSupp:fa
lse)).
Caused by: java.lang.IllegalStateException: Timer already cancelled.
Any help/advice would be appreciated.
Thank you,
Regards,
Rakesh.
Hi,
Check note 1617161 if it helps you. take a help from basis team also.
Regards,
Muniyappan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A Java restart solved the issue. We will wait untill the next transport has to be moved.
Thanks guys!
Regards,
Rakesh.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Muniyappan/Mark.
I am only trying to transport a Message Mapping and it does not involve any JMS related object.
The JMS error that is seen is internal to the PI system? And that is why you suggest the note? Do let us know.
Thank you,
Regards,
Rakesh.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Mark,
We are due for a SP upgrade soon. In the meantime, we tried importing another TR which failed with the following error:
"Unexpected error on server for system REPOSITORY with application REPOSITORY. Detailed information: Cannot allocate connection.. Server stack trace:"
I have tried looking this up but to no avail.
Regards,
Rakesh.
Hello Rakesh,
Increasing the number of JMS threads could help here. Go to NWA -> Configuration tab -> Infrastructure -> Java system properties -> service tab: JMS Connector -> maxConnections. For example, increase to 150.
Also check if you have the fixes in notes:
Regards
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.