FYI, related fixes:
MWS-24425 (MWS_10.1_Fix8 )
My webMethods Server might fail to authenticate LDAP users although the users are valid and present in the LDAP directory.
The issue is resolved.
MWS-23569 (MWS_10.1_Fix7 )
When using a My webMethods Server cluster with Universal Messaging as the JMS provider, My webMethods Server might fail to synchronize role membership updates across the nodes of the
cluster. This issue occurs when updating the role membership of LDAP users.
The issue is resolved.
Your issue does not appear on 9.9 (I’ve tested).
Best regards,
@Gerardo - this is pertinent information on a silver platter. Thank you very much.
Our MWS patchlevel is MWS_10.1_Fix6. The problems you described for MWS_10.1_Fix7 and 8 come very close to describing our problem. We do use UM, and it was an LDAP user whose role was being adjusted. The only difference is I encountered this problem on a single node MWS (not a cluster), and between MWS and IS (not between nodes in an MWS cluster). But I have a sense IS is accessing old MWS role membership information, and these patches may fix the problem.
@Yogesh – yes, we have UM messaging as the default messaging for IS
@Mahesh – Thanks. I assume you mean this MWS file: /MWS/server/default/config/cluster.xml. It’s contents seems OK:
------------------
This is my complete xml where UM server is configured.
<?xml version="1.0" encoding="UTF-8"?><Cluster clusterId="-1858469550" deploymentSymmetrical="false" distributedEventsEnabled="true" frontEndSecurePort="-1" frontEndUrl="http://localhost:8585" jndiProviderUrl="nsp://localhost:9000">
<!-- lists all physical servers in the cluster -->
<Category name="servers">
<Component class="com.webmethods.portal.system.cluster.impl.Server" enabled="true" name="Mahesh-PC-node60243" nodeType="MWS"><Properties host="localhost" name="http" port="8585"/><Properties host="localhost" name="https" port="0"/><Role name="autodeploy"/><Role name="search"/><Role name="taskengine"/><Role name="notification"/></Component></Category>
</Cluster>
If the file seems identical then the SAG patch fix should resolve your issue. Let us know how you go so it will be helpful to me and others.