Connection problems between IS and MWS

, ,
1

Sometimes, usually after some server, either IS or MWS, restart a problem constantly happen when performing operations in the MWS Monitor over process instances. For exemple, resubmit, suspend or stop a process instance. It also happens for example enabling for execution a process model. All those actions perform the same kind of behavior.

Well, when this happens (happens till a IS restart is done), I get the following server log:

[14753]2008-05-19 17:53:35 WEST [MON.0119.0000T] ******** filter: [INCLUDEALL]

[14752]2008-05-19 17:53:35 WEST [MON.0119.0000T] ******** DLS perm list length: 1

[14751]2008-05-19 17:53:35 WEST [MON.0119.0000T] getting model DLS list…

[14750]2008-05-19 17:53:35 WEST [MON.0119.0000T] ******** DLS: ((()) OR (()) OR (()) OR (()))

[14749]

[14748] at java.lang.Thread.run(Thread.java:595)

[14747] at com.wm.util.pool.PooledThread.run(PooledThread.java:112)

[14746] at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:327)

[14745] at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:186)

[14744] at com.wm.app.b2b.server.HTTPSOAPHandler.process(HTTPSOAPHandler.java:130)

[14743] at com.wm.app.b2b.server.HTTPSOAPHandler._process(HTTPSOAPHandler.java:493)

[14742] at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:119)

[14741] at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:237)

[14740] at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:381)

[14739] at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:535)

[14738] at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:621)

[14737] at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:30)

[14736] at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:228)

[14735] at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:51)

[14734] at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:241)

[14733] at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)

[14732] at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)

[14731] at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:630)

[14730] at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:403)

[14729] at java.lang.reflect.Method.invoke(Method.java:585)

[14728] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

[14727] at sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)

[14726] at wm.server.soap.rpc(soap.java:927)

[14725] at com.wm.app.b2b.server.Service.doInvoke(Service.java:588)

[14724] at com.wm.app.b2b.server.Service.doInvoke(Service.java:639)

[14723] at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:104)

[14722] at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:237)

[14721] at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:381)

[14720] at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:535)

[14719] at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:621)

[14718] at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:30)

[14717] at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:228)

[14716] at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:51)

[14715] at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:241)

[14714] at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)

[14713] at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)

[14712] at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:630)

[14711] at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:403)

[14710] at java.lang.reflect.Method.invoke(Method.java:585)

[14709] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

[14708] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

[14707] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

[14706] at ws.monitor.process.model.saveProcessModel(model.java:150)

[14705] at com.wm.monitor.app.Permissions.isPrivilegeGranted(Permissions.java:1146)

[14704] at com.webMethods.caf.portalclient.dir.PCDirectoryHelper.lookupPrincipalByID(PCDirectoryHelper.java:103)

[14703] at $Proxy2.lookupprincipalbyid(Unknown Source)

[14702] at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invoke(WSClientDynamicProxy.java:216)

[14701] at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.getCompatibleException(WSClientDynamicProxy.java:397)

[14700]2008-05-19 17:53:33 WEST [MON.0119.1501I] Error checking portal privilege: electric.util.WrappedException: java.rmi.RemoteException: HTTP error response: Unauthorized

[14699]2008-05-19 17:53:33 WEST [MON.0119.1501E] Error checking portal privilege: electric.util.WrappedException: java.rmi.RemoteException: HTTP error response: Unauthorized

[14698]2008-05-19 17:53:33 WEST [MON.0119.0000T] *** PortalClient initialized.

[14697]2008-05-19 17:53:33 WEST [MON.0119.0000T] *** privAlias: webm.apps.config.process.list

[14696]2008-05-19 17:53:33 WEST [MON.0119.0000T] *** portalURL: http://vfptmvnotst72:5858

Do any of you experienced this before? Any clue of what could generate such an error. Please note the following line:

[14699]2008-05-19 17:53:33 WEST [MON.0119.1501E] Error checking portal privilege: electric.util.WrappedException: java.rmi.RemoteException: HTTP error response: Unauthorized

I’m not able to find out what is causing the problem, but unfortunately, it’s there and happens kind of randomly (after IS restarts).

Cheers!

2

Hi we get the same issue, and have raised a service request for it. It also happens randomly and is fixed by IS restart.
Have you been able to resolve the issue?

I have run HTTP traces for when Monitor sends an authentication request to MwS (to authenticate the MwS user)
For this I believe it uses the information you enter on the Monitor package home page. When broken it seems to send a code as if the username and password were blank.

ie in working state:

POST /services/bizPolicy/system HTTP/1.1
…
SOAPAction: “command/getvmid”
…
Authorization: Basic QWRtaW5pc3RyYXRvcjptYW5hZ2U=
<soap:envelope …=“” />

in broken state:

POST /services/bizPolicy/system HTTP/1.1
…
SOAPAction: “command/getvmid”
…
Authorization: Basic Og==

Basic Og== is what you get if you put blank user/password

Not sure how this happens though!

Hope this helps, please let me know if you have had any success

Cheers

3

so what i mean is, it seems that Monitor somehow “forgets” the user/password you entered on Monitor config screen, and only restarting the IS makes it reload them.

4

Hi I am also facing the same issue.

5

Have you had any luck with this.

I’m currently stuck as you are/were in that I get the error when trying to resubmit a service.

As you experience, an IS restart or WmMonitor reload fails to resolve the issue.

I’ll raise a support request but thought I’d check with you first in case you have managed to obtain a resolution.

Thanks.

6

Just an update to say I got past this issue by using the installer and selecting the Install by role (Integration developer). It installed various extra things (sorry I didnt record which) and when I restarted everything it worked. Well it gets past the previous ‘Unauthorised’ error but now I get a null pointer which Im investigating still.

In case it helps anyone.

7

Anyone solve this yet?

8

Im facing the same ussue as well

9

Hello All,

Thanks for your inputs on this issue.

We also faced this problem in 9.6 as well, to resolve this you need not to restart IS, just update MWS password in WmMonitor package homepage and reload that package.