Java Process display problem

[Former Member]

Hi All,

We have 1-PAS and 2-AAS in PI system.while checking the server process in the primary application server using JCMON all the process server 0 ,server 1 and ICM process are running state including all the AAS instance also.

But checking same thing in the http://<system>:50000/webdynpro/resources/sap.com/tc~lm~itsam~ui~mainframe~wd/FloorPlanApp?home=true

Here java process is not displaying for all the instances.

Kindly help me to solve this.

Thanks,

Priyanga G

[Former Member]

I am getting this problem after setting the parameter icm/HTTP/logging_0 to

PREFIX=/, LOGFILE=icmhttph.log, FILTER=SAPSMD, LOGFORMAT=SAPSMD2, MAXSIZEKB=10240,FILEWRAP=on, SWITCHTF=month.Can this be the reason?

[former_member182921]

Hi Rajam ,

Can you reset this entry and check .

Regards,

Abhishek

[former_member185239]

Hi Priyanga,

Kindly check the below sap note

1488147 - NWA Missing Instances and Java Server Processes

With Regards

Ashutosh Chaturvedi

[Former Member]

Hi,

As per the note

tc~lm~itsam~core~techsysreg is started.Problem is it is not shows the detail of the instance status.

It shows only instance which are running, In single instance have its own server process those details is not shown.

Example

instance1-All process are running

instance2-All process are running

while double click the instance1 in the below it should not shows the server0-running server2-running and icm- running for all the instance.

Thanks

Priyanga. G

[former_member185239]

Hi Priyanga,

Can you please paste the logs for server0 , default trace , application log.

With Regards

Ashutosh Chaturvedi

[Former Member]

Hi,

Kernel release:

kernel release                  721

patch number                  100

Thanks,

Priyanga G

[Sriram2009]

Hi Priyanga

Could you check this links

Java Instance - Administering Application Server Java - SAP Library

Adding and Removing Server Processes - Administration - SAP Library

Regards

Ram

[Former Member]

Hi Ashutosh,

server0.log

#2.#2013 08 28 13:51:50:711#+0200#Info#/System/Server/Deployment#
com.sap.dc_1006###C0000AA9958800000000000100003DD6###com.sap.engine.services.dc.cm.offline_phase.impl########Thread[main,5,main]#Plain##
[offline] :Starting Offline Phase of Deploy Controller#

#2.#2013 08 28 13:51:52:330#+0200#Info#/System/Server/Deployment#
com.sap.ASJ.dpl_dc.006308###C0000AA9958800000000000200003DD6###com.sap.engine.services.dc.util.readers.sdu_reader.impl########Thread[main,5,main]#Plain##
[offline] :Component property [name] [tc/signt/provider/appl] will be corrected to [tc~signt~provider~appl] because it contains charactes which are not allow
ed by the system. The parameter [{0}] will be trimmed. The spaces that surround it are not allowed.#

#2.#2013 08 28 13:51:52:341#+0200#Info#/System/Server/Deployment#
com.sap.ASJ.dpl_dc.006308###C0000AA9958800000000000300003DD6###com.sap.engine.services.dc.util.readers.sdu_reader.impl########Thread[main,5,main]#Plain##
[offline] :Component property [name] [tc/sapjra] will be corrected to [tc~sapjra] because it contains charactes which are not allowed by the system. The para
meter [{0}] will be trimmed. The spaces that surround it are not allowed.#

#2.#2013 08 28 13:51:52:348#+0200#Info#/System/Server/Deployment#
com.sap.ASJ.dpl_dc.006308###C0000AA9958800000000000400003DD6###com.sap.engine.services.dc.util.readers.sdu_reader.impl########Thread[main,5,main]#Plain##
[offline] :Component property [name] [tc/sec/saml2/idp/ump] will be corrected to [tc~sec~saml2~idp~ump] because it contains charactes which are not allowed b
y the system. The parameter [{0}] will be trimmed. The spaces that surround it are not allowed.#

#2.#2013 08 28 13:51:52:359#+0200#Info#/System/Server/Deployment#
com.sap.ASJ.dpl_dc.006308###C0000AA9958800000000000500003DD6###com.sap.engine.services.dc.util.readers.sdu_reader.impl########Thread[main,5,main]#Plain##
[offline] :Component property [name] [tc/esi/esp/itsam/ui/logging/wd] will be corrected to [tc~esi~esp~itsam~ui~logging~wd] because it contains charactes whi
ch are not allowed by the system. The parameter [{0}] will be trimmed. The spaces that surround it are not allowed.#

application log

#2.#2014 03 20 13:54:33:699#+00#Info#/Applications/ECS/Application/tc/ResourceAdapter/configuration#
##ecs.com/com.ecs.aii.af.tc.ra#C0000AA995880037000027DC000074DD#1801050000001835##com.ecs.aii.af.plmi.adapter.ra.ifcs.ChannelConfigurator.publishConfigurationData#deploy_service#0##7DE6FEC7A6EE11E3B75B0050568A219C#9bd1b7a1a6ee11e3a37b0000001b7b5a#7de6fec7a6ee11e3b75b0050568a219c#0#Thread[Thread-42,5,ApplicationThreadGroup]#Plain##
ConfigurationTopicId = <tc_adapter>#

#2.#2014 03 20 13:54:33:707#+00#Info#/Applications/ECS/Application/tc/ResourceAdapter/configuration#
##ecs.com/com.ecs.aii.af.tc.ra#C0000AA995880037000027DD000074DD#1801050000001835##com.ecs.aii.af.plmi.adapter.ra.ifcs.ChannelConfigurator.publishConfigurationData#deploy_service#0##7DE6FEC7A6EE11E3B75B0050568A219C#9bd1b7a1a6ee11e3a37b0000001b7b5a#7de6fec7a6ee11e3b75b0050568a219c#0#Thread[Thread-42,5,ApplicationThreadGroup]#Plain##
Configuration message sent.#

default trace

#EP-PIN-PRT#tc~epbc~prtc~api#C0000AA99588001A000000150000051B#1801050000003300##com.sap.portal.prt.runtime.broker#deploy_service#0##81CB16E5924E11E39BE4000000
1B7B5A#81cb16e5924e11e39be40000001b7b5a#A77CB44B924E11E3BD410000001B7B5B#0#Deploy Parallel Start Thread 2#Plain##
[PortalAppBroker.getPortalService() failed com.sap.portal.resourcerepository|RepositoryNotificationService
[EXCEPTION]
com.sap.portal.prt.om.ObjectNotAvailableException: Object: [com.sap.portal.resourcerepository|RepositoryNotificationService] load failed
        at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:246)
        at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
        at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
        at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
        at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
        at com.sap.portal.prt.broker.PortalModuleItem.load(PortalModuleItem.java:226)
        at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
        at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
        at com.sap.portal.prt.broker.PortalAppBroker.getPortalModule(PortalAppBroker.java:323)
        at com.sap.portal.prt.container.PortalLifecycleHandler.onStart(PortalLifecycleHandler.java:51)
        at com.sap.engine.services.servlets_jsp.server.deploy.impl.WebContainerProvider.start(WebContainerProvider.java:707)
        at com.sap.engine.services.servlets_jsp.server.deploy.impl.WCEAppThreadInitializer.run(WCEAppThreadInitializer.java:77)
        at com.sap.engine.services.servlets_jsp.server.deploy.StartAction.initWCEComponents(StartAction.java:396)
        at com.sap.engine.services.servlets_jsp.server.deploy.StartAction.prepareStart(StartAction.java:207)
        at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.prepareStart(WebContainer.java:588)
        at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:508)
        at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:395)
        at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:331)
        at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:558)
        at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocal(ParallelAdapter.java:335)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:2386)
        at com.sap.engine.services.deploy.server.prl.ParallelApplicationStartTraverser.startApplication(ParallelApplicationStartTraverser.java:268)
        at com.sap.engine.services.deploy.server.prl.ParallelApplicationStartTraverser.access$100(ParallelApplicationStartTraverser.java:45)
        at com.sap.engine.services.deploy.server.prl.ParallelApplicationStartTraverser$StartApplicationPriviligedAction.run(ParallelApplicationStartTraverser.
java:347)
        at com.sap.engine.services.deploy.server.prl.ParallelApplicationStartTraverser$StartApplicationPriviligedAction.run(ParallelApplicationStartTraverser.
java:334)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:337)
        at com.sap.engine.services.deploy.server.prl.ParallelApplicationStartTraverser.execute(ParallelApplicationStartTraverser.java:250)
        at com.sap.engine.services.deploy.server.prl.ParallelApplicationThread.run(ParallelApplicationThread.java:62)
        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:185)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.portal.prt.broker.PortalServiceInstantiationException: Could not instantiate implementation class com.sap.portal.resource.repository.Reposi
toryNotificationService of Portal Service com.sap.portal.resourcerepository|RepositoryNotificationService because: Error occured during the after init functio
n of the service. Check the cause exception for more details.
        at com.sap.portal.prt.broker.PortalServiceItem.afterInit(PortalServiceItem.java:443)
        at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:220)
        at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
        at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
        ... 32 more
Caused by: com.sapportals.portal.prt.service.ServiceException: Error while retrieving service: com.sap.portal.resourcerepository.ResourceRepositorySrv
        at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:270)
        at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
        at com.sap.portal.resource.repository.RepositoryNotificationService.afterInit(RepositoryNotificationService.java:52)
        at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$1.service(RequestDispatcherFactory.java:428)
        at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
        at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.afterInit(RequestDispatcherFactory.java:413)
        at com.sap.portal.prt.broker.PortalServiceItem.afterInit(PortalServiceItem.java:435)
        ... 35 more
Caused by: com.sap.portal.prt.broker.PortalServiceNotFoundException: Could not retrieve portal service: com.sap.portal.resourcerepository|ResourceRepositorySr
v
        at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:503)
        at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
        at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
        ... 41 more
Caused by: com.sap.portal.prt.om.ObjectNotAvailableException: Object: [com.sap.portal.resourcerepository|ResourceRepositorySrv] load failed
        at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:246)
a011179p300:ppiadm 86> tail -f defaultTrace_00.3.trc
        at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

#

#2.#2014 03 20 12:54:21:478#+00#Error#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#
com.sap.ASJ.web.000137#BC-WD-JAV#sap.com/tc~wd~dispwda#C0000AA99588361B00000006000074DD#1801050000000004#sap.com/tc~wd~dispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#J2EE_ADMIN#11803##4E35DC4CB02A11E3C5A10000001B7B5A#bf58a769b02411e3a32e0000001b7b5a#bf58a769b02411e3a32e0000001b7b5a#0#Thread[HTTP Worker [@123649360],5,Dedicated_Application_Thread]#Plain##
Cannot process an HTTP request to servlet [forwardServlet] in [webdynpro/dispatcher] web application.
For more details on the problem please check traces searching by logId: C0000AA99588361B00000004000074DD#

Thanks,

Priyanga G

[former_member185239]

Hi Priyanga,

Click on all the instances and paste the application log from server0/log

With Regards

Ashutosh Chaturvedi

[Former Member]

Hi,

Sorry I din't get u.

you need instances which we have and server0 log files.

Thanks,

Priyanga G

[former_member185239]

Hi Priyanga,

Click on all the three instances in NWA , which will record all the activity in application log.

Paste the latest log.

With Regards

Ashutosh Chaturvedi

[Former Member]

Hi,

This is for 1st instance application log just now generated.

#2.#2014 03 20 14:09:33:736#+00#Info#/Applications/ECS/Application/tc/ResourceAdapter/configuration#

##ecs.com/com.ecs.aii.af.tc.ra#C0000AA995880037000027E6000074DD#1801050000001835##com.ecs.aii.af.plmi.adapter.ra.ifcs.ChannelConfigurator.publishConfigurationData#deploy_service#0##7DE6FEC7A6EE11E3B75B0050568A219C#9bd1b7a1a6ee11e3a37b0000001b7b5a#7de6fec7a6ee11e3b75b0050568a219c#0#Thread[Thread-42,5,ApplicationThreadGroup]#Plain##

Configuration message sent.#

#2.#2014 03 20 14:14:33:737#+00#Info#/Applications/ECS/Application/tc/ResourceAdapter/configuration#

##ecs.com/com.ecs.aii.af.tc.ra#C0000AA995880037000027E7000074DD#1801050000001835##com.ecs.aii.af.plmi.adapter.ra.ifcs.ChannelConfigurator.publishConfigurationData#deploy_service#0##7DE6FEC7A6EE11E3B75B0050568A219C#9bd1b7a1a6ee11e3a37b0000001b7b5a#7de6fec7a6ee11e3b75b0050568a219c#0#Thread[Thread-42,5,ApplicationThreadGroup]#Plain##

Generating configuration message...#

#2.#2014 03 20 14:14:33:738#+00#Info#/Applications/ECS/Application/tc/ResourceAdapter/configuration#

##ecs.com/com.ecs.aii.af.tc.ra#C0000AA995880037000027E8000074DD#1801050000001835##com.ecs.aii.af.plmi.adapter.ra.ifcs.ChannelConfigurator.publishConfigurationData#deploy_service#0##7DE6FEC7A6EE11E3B75B0050568A219C#9bd1b7a1a6ee11e3a37b0000001b7b5a#7de6fec7a6ee11e3b75b0050568a219c#0#Thread[Thread-42,5,ApplicationThreadGroup]#Plain##

ConfigurationTopicId = <tc_adapter>#

#2.#2014 03 20 14:14:33:747#+00#Info#/Applications/ECS/Application/tc/ResourceAdapter/configuration#

##ecs.com/com.ecs.aii.af.tc.ra#C0000AA995880037000027E9000074DD#1801050000001835##com.ecs.aii.af.plmi.adapter.ra.ifcs.ChannelConfigurator.publishConfigurationData#deploy_service#0##7DE6FEC7A6EE11E3B75B0050568A219C#9bd1b7a1a6ee11e3a37b0000001b7b5a#7de6fec7a6ee11e3b75b0050568a219c#0#Thread[Thread-42,5,ApplicationThreadGroup]#Plain##

Configuration message sent.#

#2.#2014 03 20 14:19:33:748#+00#Info#/Applications/ECS/Application/tc/ResourceAdapter/configuration#

##ecs.com/com.ecs.aii.af.tc.ra#C0000AA995880037000027EA000074DD#1801050000001835##com.ecs.aii.af.plmi.adapter.ra.ifcs.ChannelConfigurator.publishConfigurationData#deploy_service#0##7DE6FEC7A6EE11E3B75B0050568A219C#9bd1b7a1a6ee11e3a37b0000001b7b5a#7de6fec7a6ee11e3b75b0050568a219c#0#Thread[Thread-42,5,ApplicationThreadGroup]#Plain##

Generating configuration message...#

#2.#2014 03 20 14:19:33:749#+00#Info#/Applications/ECS/Application/tc/ResourceAdapter/configuration#

##ecs.com/com.ecs.aii.af.tc.ra#C0000AA995880037000027EB000074DD#1801050000001835##com.ecs.aii.af.plmi.adapter.ra.ifcs.ChannelConfigurator.publishConfigurationData#deploy_service#0##7DE6FEC7A6EE11E3B75B0050568A219C#9bd1b7a1a6ee11e3a37b0000001b7b5a#7de6fec7a6ee11e3b75b0050568a219c#0#Thread[Thread-42,5,ApplicationThreadGroup]#Plain##

ConfigurationTopicId = <tc_adapter>#

#2.#2014 03 20 14:19:33:758#+00#Info#/Applications/ECS/Application/tc/ResourceAdapter/configuration#

##ecs.com/com.ecs.aii.af.tc.ra#C0000AA995880037000027EC000074DD#1801050000001835##com.ecs.aii.af.plmi.adapter.ra.ifcs.ChannelConfigurator.publishConfigurationData#deploy_service#0##7DE6FEC7A6EE11E3B75B0050568A219C#9bd1b7a1a6ee11e3a37b0000001b7b5a#7de6fec7a6ee11e3b75b0050568a219c#0#Thread[Thread-42,5,ApplicationThreadGroup]#Plain##

Configuration message sent.#

[Former Member]

Hello Priyanga G,

Can you let us know how your issue was resolved? I'm getting the same issue. Thanks.

[Former Member]

This issue was resolved after parameter service/protectedwebmethods was changed from SDEFAULT to DEFAULT.