disp+work not completely started

[Former Member]

Hello,

We are on SAP PI 7.11 running on HP-UX...

When I check the SAP NetWaever Administrator --> Java EE instances --> OS processes, I see the disp+work has status: running, but dialog info queue unavailable, AS java: all processes running - yellow LED; warning.

I've read several log files and threads on SDN, but found no solution.

Any advise is appreciated!

Thanks a lot.

Dimitri

ps: all messages pass the SAP PI system without any problem.

[sunny_pahuja2 · Accepted solution]

Hi,

For this problem, you can check SAP Note 396309 Dispatcher remains yellow, although the system is running and SAP Note 72248 NT: Dispatcher in status 'Yellow',SAP system running.

Thanks

Sunny

[Former Member · Accepted solution]

Dear Sunny,

I checked them both, bot nothing in there.

Now, I was looking into /usr/sap/<SAPSID>/DVEBMGS03/work and found some logs files stating this:

*** Trace file opened at 20100914 133533 METDST, by dispwork+

**** Versions SAP-REL 711,0,67 RFC-VER U 3 1121034 MT-SL

======> Password logon no longer possible - too many failed attempts

ABAP Programm: SAPLSPILSI (Transaction: )

Called function module: SPI_LS_INIT_READ_STACK

User: PISUPER (Client: 001)

Destination: PMIIP3001 (handle: 2, 94221857, {4C8F5972-57B1-724E-E100-0000C0A8A31E})

SERVER> RFC Server Session (handle: 1, 94220852, {4C8F3B8A-37D0-4F87-E100-0000C0A8A31E})

SERVER> Caller host:

SERVER> Caller transaction code: (Caller Program: SPI_CS_COLLECT)

SERVER> Called function module: SPI_LS_PARALLEL_READ_ALL

Any idea?

Thanks

Dimitri

[tomas-krojzl · Accepted solution]

Hello,

it is very important to see if you have problem somewhere or not - is both ABAP and Java working properly?

If yes it is critical and you must follow errors in log files.

If not it might be problem in getting correct status - which is not so critical as first case.

In the log above you can see that user PISUPER in client: 001 is locked because of too many logon attepmts. You need to see which RFC, JCo or external program is using this user to connect and ensure correct password is used. Then you can go to SU01 and unlock the user.

In case everything is working correctly it is very likely that this problem is not connected to yellow status as status is not obtained from loggin inside SAP using users.

Best regards.

[tomas-krojzl · Accepted solution]

Hello,

try to review sapstarstrv logs to find any hint why system is yellow.. it is possible that this has something to do with shared memory accesibility..

Best regards.

[Former Member · Accepted solution]

Hello Tomas,

I checked the sapstarstrv.log and the sapstarstrv.old, but nothing special there.

Do you have other suggestions?

Kind regards,

Dimitri

[tomas-krojzl · Accepted solution]

Hello,

it is very difficult to investigate such issue..

My opinion is that it is very likely that this is "just" cosmetic error - as long as all in PI is fully functional I would not put this problem a very high priority.

Is this problem new (since last startup)? Or do you have this problem for longer time (over multiple startups)?

What was last change done to the system before this happened (maybe kernel upgrade)?

There is possibility that complete stop of SAP (checking all processes are down) and cleaning shared memory, cleaning shared libraries, etc. and then starting the system up would resolve the problem - but as long as everything is functional I do not believe it is good tradeoff (especially for production system).

In parallel to this analysis you might want to check Java logs in /usr/sap/<SID>/<instance>/j2ee/cluster/<node>/log (use log viewer). Maybe you will have some warnings (probably not even errors) from NetWeaver administrator that will suggest where might be the problem - what checking actions did not go through so that status is taked as yellow. But to be honest I am sceptical you will identify root cause.

Note: You might need to increase trace level for Java logs.

Best regards.

[Former Member · Accepted solution]

Hello Tomas,

I looked at the SAP MMC on Unix via [http://<host>:5<sysnr>13/] and found this error:

DpHdlDeadWp: Wxx (pid=xxxx) terminated automatically.

Does that ring a bell?

When I click on my host in the SAP MMC, I get this error:

javax.xml.rpc.soap.SOAPFaultException: DpExtProcAttach failed

+ at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:737)+

+ at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:860)+

+ at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1439)+

+ at com.sap.managementconsole.soap.sap.sapcontrol.SAPControlStub.ABAPGetWPTable(SAPControlStub.java:2381)+

+ at com.sap.managementconsole.dataloader.soap.sap.SAPSOAPDataLoader.getABABWorkProcessTable(SAPSOAPDataLoader.java:495)+

+ at com.sap.managementconsole.common.data.WorkProcessTable.loadChildren(WorkProcessTable.java:32)+

+ at com.sap.managementconsole.operations.LoadOperation.execute(LoadOperation.java:32)+

+ at com.sap.managementconsole.operations.LoadInstanceOverviewData.execute(LoadInstanceOverviewData.java:37)+

+ at com.sap.managementconsole.common.DataLoader.executeAllQueuedOperations(DataLoader.java:670)+

+ at com.sap.managementconsole.common.ThreadPoolDataLoader$DataLoaderTask.execute(ThreadPoolDataLoader.java:127)+

+ at com.sap.managementconsole.common.ThreadPoolManager$ThreadPoolElement.run(ThreadPoolManager.java:276)+

+ at java.lang.Thread.run(Unknown Source)+

When I click on AS ABAP WP table, I get this error:

javax.xml.rpc.soap.SOAPFaultException: DpExtProcAttach failed

+ at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:737)+

+ at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:860)+

+ at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1439)+

+ at com.sap.managementconsole.soap.sap.sapcontrol.SAPControlStub.ABAPGetWPTable(SAPControlStub.java:2381)+

+ at com.sap.managementconsole.dataloader.soap.sap.SAPSOAPDataLoader.getABABWorkProcessTable(SAPSOAPDataLoader.java:495)+

+ at com.sap.managementconsole.common.data.WorkProcessTable.loadChildren(WorkProcessTable.java:32)+

+ at com.sap.managementconsole.operations.LoadOperation.execute(LoadOperation.java:32)+

+ at com.sap.managementconsole.operations.AuthorizedOperation.execute(AuthorizedOperation.java:55)+

+ at com.sap.managementconsole.common.DataLoader.executeAllQueuedOperations(DataLoader.java:670)+

+ at com.sap.managementconsole.common.ThreadPoolDataLoader$DataLoaderTask.execute(ThreadPoolDataLoader.java:127)+

+ at com.sap.managementconsole.common.ThreadPoolManager$ThreadPoolElement.run(ThreadPoolManager.java:276)+

+ at java.lang.Thread.run(Unknown Source)+

When I click on AS JAVA, I do not see any memory statistics.

So there is something wrong...

Kind regards,

Dimitri

[p330068]

Hi Dimitri,

Please update compatible JAVA_HOME system enviromental variable in my computer (My computer > Properties >> Advance >> Startup and Recovery >> Enviromental Variable >> System Variables >> Add new JAVA_HOME parameter with path for installed Java JDK)

Also update your server IP address and host name in host file entry at (Start > RUN > drivers > etc > host file) and update the service file like sapms<SID> 36<systemnumber>/tcp (Start > RUN > drivers > etc > services and add an entry)

Then please check database server services (Start > Run > Services.msc >> Start your database services manually and change properties as automatic)

Then try to start the server and check it.

Regards

Arun Jaiswal

[Former Member]

Hi Arun,

Maybe I forgot to mention, but we are on a HP-UX operating system.

Kind regards,

Dimitri

[Former Member]

As per another thread you got below error:

>>DpHdlDeadWp: W55 (pid=27851) terminated automatically

Can you please check the W55 log file?

[Former Member]

I did a find on 'ERROR' and this is the feedback:

A *** ERROR => RFC ======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679

Transaction program not registered

A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1730

CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679

Transaction program not registered

And concerning the PID=27851, I found this:

dev_w55:M pid 27851

dev_w55:M ThWpRestart: restart wp (pid=27851) automatically

dev_w55.old:M *** WARNING => PfICompleteRec: OS CPU-time problem (30000 > 27851) pfxxstat.c 3974

Kind regards,

Dimitri

[Former Member]

Are you using SAPMMC from your UNIX server or Windows server?

[Former Member]

On a HP-UX Unix machine via [http://<host>:port/] where port = 5<SYSNR>13.

[Former Member]

Any help is appreciated.

Thanks a lot.

Dimtri

[Former Member]

Hi Dimitri,

did you able to find the cause of this issue and solution for it? I am also accessing sapmc with http://<host>:5<SYSNT>13 and have exactly same error.

Pravin

[Former Member]

Hi Pravin,

Currently, I'm working on the setup of a Solution Manager system and once that system is available I will try to find the root cause.

In the meantime, I looked around a little bit and it seems to be a problem with the Java heap.

Kind regards,

Dimitri