Changerequest already closed when transfering transport list

[Former Member]

Hi,

Our developers are releasing a transferlist to the CMS (NWDI) system for transport, but it fails with Details "ChangeRequest: <id> is already closed."

The entire error message in the integration build is

"Sent on..

Unable to establish connection to CMS server <url>

Unable to transfer the following transport lists:

<Name of transport> (send time=, component=, id=)

Details: ChangeRequest: <id> already closed

Details: Read timed out"

The connection to CMS is established as one can see in the logs of the JDI system.

There are two stack traces which indicate the failure

User=CMSadm Msg=release changelists for original changes: <change name> response failed Exc=com.sap.cms.util.exception.organizer.CMSOrganizerException: ChangeRequest: <id> already closed

releaseChangelists failed

[EXCEPTION]

com.sap.cms.util.exception.organizer.CMSOrganizerException: ChangeRequest: <id> already closed

at com.sap.cms.pcs.organizer.manager.ReleaseManager.releaseChangelists001(ReleaseManager.java:165)

at com.sap.cms.pcs.organizer.proxy.CmsOrganizerProxyBean.releaseChangelists(CmsOrganizerProxyBean.java:122)

at com.sap.cms.pcs.organizer.proxy.LocalCmsOrganizerProxyLocalObjectImpl20.releaseChangelists(LocalCmsOrganizerProxyLocalObjectImpl20.java:374)

at com.sap.cms.pcs.serverAPI.OrganizerDispatcher.invokeMethod(OrganizerDispatcher.java:100)

at com.sap.cms.pcs.serverAPI.CMSAdapter.cmsExec(CMSAdapter.java:189)

at com.sap.cms.pcs.serverAPI.CmsOrganizerAdapter.doPost(CmsOrganizerAdapter.java:84)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: com.sap.cms.util.exception.request.CmsChangelistCreateException: ChangeRequest: <id> already closed

at com.sap.cms.pcs.request.RequestManager.addChangeLists(RequestManager.java:115)

at com.sap.cms.pcs.organizer.manager.ReleaseManager.addChangelists(ReleaseManager.java:1062)

at com.sap.cms.pcs.organizer.manager.ReleaseManager.releaseChangelists002(ReleaseManager.java:239)

at com.sap.cms.pcs.organizer.manager.ReleaseManager.releaseChangelists001(ReleaseManager.java:147)

... 21 more

Caused by: com.sap.cms.pcs.request.changerequest.CmsChangeRequestClosedException: ChangeRequest: <id> already closed

at com.sap.cms.pcs.request.changerequest.ChangeRequest.addChangelist(ChangeRequest.java:140)

at com.sap.cms.pcs.request.RequestManager.addChangeLists(RequestManager.java:108)

... 24 more

add item SC_CR <SC bane> Version JDI <version> failed

[EXCEPTION]

javax.ejb.DuplicateKeyException: Primary key already exists

at com.sap.cms.pcs.transport.registry.SqlJQueue.create(SqlJQueue.sqlj:44)

at com.sap.cms.pcs.transport.registry.QueueRegistry.addItems(QueueRegistry.java:126)

at com.sap.cms.pcs.transport.queuehandler.QueueHandler.addToQueue(QueueHandler.java:554)

at com.sap.cms.pcs.transport.queuehandler.QueueHandler.addToQueue(QueueHandler.java:512)

at com.sap.cms.pcs.PropMgr.engine.PropQueueHandler.addToQueues(PropQueueHandler.java:118)

at com.sap.cms.pcs.PropMgr.engine.PropQueueHandler.addToImportQueues(PropQueueHandler.java:51)

at com.sap.cms.pcs.PropMgr.engine.PropagationEngine.publishRequests(PropagationEngine.java:266)

at com.sap.cms.pcs.PropMgr.engine.PropagationEngine.moveRequestsOverTransition(PropagationEngine.java:393)

at com.sap.cms.pcs.PropMgr.engine.PropagationEngine.followTransitionsFromState(PropagationEngine.java:352)

at com.sap.cms.pcs.PropMgr.engine.PropagationEngine.analyzeEntryPoint(PropagationEngine.java:216)

at com.sap.cms.pcs.PropMgr.engine.PropagationEngine.propagateRequestsForExport(PropagationEngine.java:153)

at com.sap.cms.pcs.PropMgr.PropagationManager.propagateExportedRequests(PropagationManager.java:219)

at com.sap.cms.pcs.organizer.manager.ReleaseManager.propagateChangeRequest(ReleaseManager.java:1240)

at com.sap.cms.pcs.organizer.manager.ReleaseManager.restartExportByChangelists(ReleaseManager.java:516)

at com.sap.cms.pcs.organizer.proxy.CmsOrganizerProxyBean.restartExportByChangelists(CmsOrganizerProxyBean.java:455)

at com.sap.cms.pcs.organizer.proxy.LocalCmsOrganizerProxyLocalObjectImpl20.restartExportByChangelists(LocalCmsOrganizerProxyLocalObjectImpl20.java:968)

at com.sap.cms.pcs.serverAPI.OrganizerDispatcher.invokeMethod(OrganizerDispatcher.java:281)

at com.sap.cms.pcs.serverAPI.CMSAdapter.cmsExec(CMSAdapter.java:189)

at com.sap.cms.pcs.serverAPI.CmsOrganizerAdapter.doPost(CmsOrganizerAdapter.java:84)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Any suggestion on how to handle such situations ?

The transport list is not in the import queue to consolidation in CMS.

PS JDI version is NW04s SP8

Regards

Dagfinn

[Former Member · Accepted solution]

Hi,

Check SAP note 898330

And..see

Following blog may be useful.

/people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms

Did u create CMS USER ? Just go thru following link.

http://help.sap.com/saphelp_nw2004s/helpdata/en/88/311041b59bef23e10000000a155106/frameset.htm

Als Please see the below links..

Regards

Chilla...

<i>Points rewarded if it is useful..</i>

[Former Member · Accepted solution]

Hi,

Thanks for the suggestion, but they really didn't solve the problem.

The XI transports have been running without problems for a long time, and other transport lists can be transported.

Based on the error message, the system has registered the changerequest(transport list) as already transport/closed. This doesn't correspond to the view the developer or CMS track has.

What I am wondering on, is if a new transport list must be built up from scratch for this change.

Dagfinn

[Former Member]

Needed workaround (split XI transport into multiple packages, not good).CTS+ will be the saviour

[Former Member]

check your connection of CMS server and our NWDI or user transport list are ocnnected properly to CMS