Deploying java libraries

Hi Experts,

I have created new track in DI and trying to deploy Jtech, Jee and jbuild components under tab Development. When I try to deploy, It fails saying buildspace status is "Priviledged". I also went to CBS and set this back to "Open". But again it automatically gets set to "Priviledged" and I am not able to deploy these libraries.

Has anybody faced the same problem ?

Please suggest solution.

Thanks & Regards,

Mehul

SAP Managed Tags:
NW Java Development Infrastructure (NWDI)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

Are there no requests running?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I didn't get you. Also the CMS and other DI related pages are too slow and

sometimes shows dump like..

com.sap.tc.webdynpro.services.session.LockException: Thread SAPEngine_Application_Thread[impl:3]_149 failed to acquire exclusive lock on client session ClientSession(id=(J2EE703257200)ID0310573650DB20173521691869534234End_13896156). Existing locks: LockingManager(ThreadName:SAPEngine_Application_Thread[impl:3]_149, exclusive client session lock: ClientSessionLock(SAPEngine_Application_Thread[impl:3]_89), shared client session locks: ClientSessionSharedLockManager([]), app session locks: ApplicationSessionLockManager([]), current request: sap.com/tc_SLCMS~WebUI/Cms).Hint: Take a thread dump of the server node to find the blocking thread that causes the problem.

Is there any way to get logs for this process?

-Mehul

Go to the CBS WebUI -> Requests link at the top -> Open Requests -> Filter Requests. Does CBS find any requests?

I tried to open CBS page but got dump as below.I am trying continuously and if page opens, I'll let you know about request. I am getting the same dump in CMS also. Should I restart server? any suggestions?

500 Internal Server Error

SAP NetWeaver Application Server 7.00/Java AS 7.00

Failed to process request. Please contact your system administrator.

[Hide]

Error Summary

While processing the current request, an exception occured which could not be handled by the application or the framework.

If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).

Root Cause

The initial exception that caused the request to fail, was:

com.sap.tc.webdynpro.services.session.LockException: Thread SAPEngine_Application_Thread[impl:3]_145 failed to acquire exclusive lock on client session ClientSession(id=(J2EE703257200)ID0310573650DB20173521691869534234End_13896156). Existing locks: LockingManager(ThreadName:SAPEngine_Application_Thread[impl:3]_145, exclusive client session lock: ClientSessionLock(SAPEngine_Application_Thread[impl:3]_89), shared client session locks: ClientSessionSharedLockManager([]), app session locks: ApplicationSessionLockManager([]), current request: sap.com/tc.CBS.WebUI/WebUI).Hint: Take a thread dump of the server node to find the blocking thread that causes the problem.

at com.sap.tc.webdynpro.clientserver.session.ClientSession$LockingManager.lock(ClientSession.java:1512)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:233)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)

... 16 more

Give it a restart, see if that helps.

I restarted. Now not getting dump. I checked the requests and there is one request under open request tab.

Request ID Request State Request Type Owner

593 QUEUED INIT_COMPARTMENT Administrator

Make sure that the idleStart property of the CBS Service is set to 'false' (in Visual Administrator/NWA).

It was set to TRUE. I have now reset it to false. Just checking now deploying libraries and will get back soon. Anything else I need to confirm for resolution?

Edited by: Mehul Prajapati on Mar 5, 2008 3:52 PM

Did you restart the service? Perhaps it's wise to first check if the queued INIT_COMPARTMENT request is now processing/finished.

The process is still on "Queued" state. My admin user has been locked and not getting unlocked. I tried resetting password and unlocking all the way still i am not able to login. And in deploying libraries, It failed with following dump.

Info:Starting Step CBS-make at 2008-03-05 10:06:27.0794 -5:00

Error:CBS error on retrieving current mode:

caused by:User not authorized. (Service call exception; nested exception is:

com.sap.tc.cbs.client.error.CommunicationException: User not authorized. (Service call exception; nested exception is:

at com.sap.tc.cbs.client.impl.BuildSpace.getInputMode(BuildSpace.java:215)

at com.sap.cms.tcs.client.CBSCommunicator.getInputMode(CBSCommunicator.java:258)

at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:85)

at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)

at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)

at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)

at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)

at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:227)

at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:634)

at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:103)

at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:584)

at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:560)

at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1244)

at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1198)

at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2215)

at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:881)

at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2390)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)

at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:714)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

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:401)

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

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

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

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

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

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

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

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:

java.rmi.RemoteException: Service call exception; nested exception is:

at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.getInputMode(CBSHttpSOAPBindingStub.java:1551)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.tc.cbs.client.impl.BuildServer$1.invoke(BuildServer.java:490)

at $Proxy173.getInputMode(Unknown Source)

at com.sap.tc.cbs.client.impl.BuildSpace.getInputMode(BuildSpace.java:213)