cancel
Showing results for 
Search instead for 
Did you mean: 

sap.com/CAF 12 - SOLUTION MANAGER 4.0 SR2 - SP12 deployment issue

franco_tassone
Explorer
0 Kudos
93

Dear all,

in our Solution Manager system we're moving our SP stack level from 10 to 12.

We could successfully deploy via JSPM all the needed components except sap.com/CAF 12, here's the relevant part of the JSPM log:

Jul 23, 2007 8:57:44 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

Jul 23, 2007 8:59:37 AM Info: Begin of log messages of the target system:

07/07/23 08:57:44 - ***********************************************************

07/07/23 08:57:47 - Start updating EAR file...

07/07/23 08:57:47 - start-up mode is lazy

07/07/23 08:57:47 - EAR file updated successfully for 63ms.

07/07/23 08:57:47 - Start updating...

07/07/23 08:57:47 - EAR file uploaded to server for 47ms.

07/07/23 08:59:37 - ERROR: Not updated. Deploy Service returned ERROR:

java.rmi.RemoteException: Cannot deploy application sap.com/caf~km.proxies..

Reason: Webservices common deployment exception! The reason is: Error occured, trying to update ws clients for application sap.com/caf~km.proxies. . Additional info: ; nested exception is: java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occured, trying to update ws clients for application sap.com/caf~km.proxies. . Additional info:

at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateProcessor.updateWSClients(WSClientsUpdateProcessor.java:162)

at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateProcessor.updateWSClients(WSClientsUpdateProcessor.java:118)

at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateProcessor.updateWSClients(WSClientsUpdateProcessor.java:104)

at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateProcessor.updateWSClients(WSClientsUpdateProcessor.java:77)

at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateManager.makeUpdate(WSClientsUpdateManager.java:53)

at com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate(WSDeployer.java:275)

at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)

at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)

at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)

at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)

at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)

at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)

at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)

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)

...

I've found an interesting, Note 956443 - In NW04s deploy of Java WS with security fails, but here they speak about SP6 and we're already at 10, moving to 12... so I'm not sure.

Any advice will be greatly appreciated.

Franco.

Accepted Solutions (0)

Answers (3)

Answers (3)

franco_tassone
Explorer
0 Kudos

Deal all,

thanks for all the suggestion.

Even though we tried all the advices we received the solution came from Note 941595 - Download J2SE 1.4.2 for the x64 : we switched to JDK version 1.4.2_15 and sap.com/CAF was deployed just smoothly as all the other SPs.

Again thank you !

Franco.

franco_tassone
Explorer
0 Kudos

Hi Ashutosh,

thanks a lot for answering.

I've tried the note 956443 finally, but no luck, nothing changed....

Opening a ticket to SAP...

Cheers.

Franco.

Former Member
0 Kudos

Hi

In JSPM, uncheck the CAF components and deploy all others first and then restart the JSPM and the server., Then deploy just the CAF components seperately.

I faced the same issue before, doing this way it worked!

Thanks

Subbu

Former Member
0 Kudos

Hi Franco,

Have you tried applying Note 956443.?This is helpfull as lots of issue has been resolved even for higher versions.

Also kindly check the files genetated under META-INF directory.Kindly check that

there should not be any dublicate files.If they are,kindly remmove them from there

and try again.

If still it does not work,open a CSN message under BC-ESI-WS-JAV.

Regards,

Ashutosh