Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

SDM hangs with error in jvm_sdm.out

Hi everybody

When I start remotegui.bat it gives following error in <b>jvm_sdm.out</b> file. It opens first tab but If I try to change tab then it hangs.

java.lang.IndexOutOfBoundsException: Index: 512, Size: 512

at java.util.ArrayList.RangeCheck(ArrayList.java:507)

at java.util.ArrayList.get(ArrayList.java:324)

at com.sap.sdm.app.proc.undeployment.impl.DeploymentGraphSorter.sortByName(DeploymentGraphSorter.java:134)

at com.sap.sdm.app.proc.undeployment.impl.DeploymentGraphSorter.sortSdaActions(DeploymentGraphSorter.java:65)

at com.sap.sdm.app.proc.undeployment.impl.DeploymentGraphBuilder.build(DeploymentGraphBuilder.java:46)

at com.sap.sdm.app.proc.undeployment.impl.UndeploymentProcessImpl.<init>(UndeploymentProcessImpl.java:21)

at com.sap.sdm.app.proc.undeployment.impl.FactoryImpl.createProcess(FactoryImpl.java:16)

at com.sap.sdm.app.view.proc.undeployment.impl.local.FactoryImpl.createProcess(FactoryImpl.java:16)

at com.sap.sdm.app.view.proc.undeployment.impl.remote.server.InitialCallBackImpl.createInitialObject(InitialCallBackImpl.java:25)

at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:57)

at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)

at com.sap.sdm.gui.server.GuiAdminRoleCmdProcessor.process(GuiAdminRoleCmdProcessor.java:72)

at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)

at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)

at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)

at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)

at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)

at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)

at java.lang.Thread.run(Thread.java:534)

Please help. Thanks in advance.

Raktim

replied

hi Raktim,

Looks like there is a problem with the java heap size. There are two solutions proposed in OSS notes 824357 & 756084. I guess 824357 will be the best work-around for ur problem.

Check it out and let us know..

Rgds

Ak.

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question