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

You need to have the same user id and password in IS and MWS.
If you can’t able view the monitor-> service /process instance check the IS remote server definition user id and password.

3

Not actually the issue. The resubmit works initially but periodically it then stops. A restart of the IS process usually corrects it. I saw from the Advantage site others were having this issue as well. I have a ticket in with webMethods also.

Has anyone else run into this and if so any resolution found other than restarting the IS process?

4

Hello,

We’ve resolved the issue (after a long time) with a WmMonitor that the SA support provided us (from the engineering department). It seems so resolve the problem. Ask the support for it (if you like I can also provide it to you)

After, we had another problem, but the thing is that, as said, the user in the Developer WmMonitor properties and MWS should be the same (with Administrator/manage) it should work fine. Pay atention to this cause I understimated this kind of things (the error message was a nullpointexeception!) and the problem then was as simple as configuration and permision problems.

5

Thanks for update. Good to know that the support folks have a fix or patch for it. I have a ticket in with them so I press a bit for the Eng. fix.

I’ve known about the permissions thing for a while unfortunately. Working with MWS over the past few years has been anything but fun. Not my favorite product. It does get a little better with each release and I’m hoping one day it will actually make it to a production caliber product. :wink:

6

Yes, my relationship with MWS wasn’t very good so far… But yes, it’s improving but slowly. But it is a fact that spiting the process monitoring into MWS + MwMonitor brought a lot of problems, especially related to authentications between servers and components…

Well, good luck with the sAG suport! :slight_smile:

Cheers!

7

Am facing the same issue in wm 712. Can any one suggest me how to resolve it ?

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.