Portal 6 Cluster - EJPSG0002E: Requested Member does not exist error

[Niall McLoughlin]

All

I have a two node Portal 6.0.1.1 cluster configured. The primary node is fine. The secondary node is throwing alot of errors referring to uid=wpsadmin,o=default organization.

The error is quite correct, in that that user in that container doesn't exist, but there is no reference to uid=wpsadmin,o=default organization defined anywhere in the Portal configuration.

Most of the references to this problem refer to WCM, which isn't installed in this case.

The first occourence of the error is on startup ( listed below ) and then seems to repeat whenever a new page is requested. If anyone has any ideas how to resolve this, I'd appreciate hearing them.

{code}
[13/02/09 13:40:44:484 GMT] 00000032 ApplicationMg A WSVR0221I: Application started: wps
[13/02/09 13:40:44:484 GMT] 0000006d ApplicationMg A WSVR0200I: Starting application: icmjcrear
[13/02/09 13:40:44:781 GMT] 0000006d WebGroup A SRVE0169I: Loading Web Module: icmjcradminwar.
[13/02/09 13:40:45:094 GMT] 0000006d RepositoryFac I com.ibm.icm.jcr.RepositoryFactory init Initializing RepositoryFactory.
[13/02/09 13:40:45:250 GMT] 0000006d RepositoryImp I com.ibm.icm.jcr.RepositoryImpl getRepository Loading Repository: Default.
[13/02/09 13:40:45:453 GMT] 0000006d ServletWrappe E Uncaught init() exception thrown by servlet InitServlet
[13/02/09 13:40:45:484 GMT] 0000006d WebExtensionP E Error occured while preparing theservlet for initialization. Check the error logs for details.
[13/02/09 13:40:45:500 GMT] 0000006d WebExtensionP E SRVE0026E: [Servlet Error]-[javax.servlet.ServletException: Unable to initialize RepositoryFactory due to exception of type: com.ibm.portal.puma.MemberNotFoundException with message: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,o=default organization.
at com.ibm.icm.jcr.init.InitServlet.init(InitServlet.java:57)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:310)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1696)
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:140)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:820)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:547)
at com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:419)
at com.ibm.ws.webcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:117)
at com.ibm.ws.webcontainer.VirtualHost.addWebApplication(VirtualHost.java:128)
at com.ibm.ws.webcontainer.WebContainer.addWebApp(WebContainer.java:939)
at com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:892)
at com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.java:167)
at com.ibm.ws.runtime.component.WebContainerImpl.start(WebContainerImpl.java:391)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1245)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1067)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:547)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:751)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:909)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2020)
at com.ibm.ws.runtime.component.ComponentImpl$_AsynchInitializer.run(ComponentImpl.java:304)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)
---- Begin backtrace for Nested Throwables
javax.jcr.RepositoryException: Unable to initialize RepositoryFactory due to exception of type: com.ibm.portal.puma.MemberNotFoundException with message: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,o=default organization.
at com.ibm.icm.jcr.RepositoryFactory.init(RepositoryFactory.java:311)
at com.ibm.icm.jcr.RepositoryFactory.getRepository(RepositoryFactory.java:663)
at com.ibm.icm.jcr.init.InitServlet.init(InitServlet.java:53)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:310)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1696)
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:140)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:820)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:547)
at com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:419)
at com.ibm.ws.webcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:117)
at com.ibm.ws.webcontainer.VirtualHost.addWebApplication(VirtualHost.java:128)
at com.ibm.ws.webcontainer.WebContainer.addWebApp(WebContainer.java:939)
at com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:892)
at com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.java:167)
at com.ibm.ws.runtime.component.WebContainerImpl.start(WebContainerImpl.java:391)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1245)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1067)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:547)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:751)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:909)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2020)
at com.ibm.ws.runtime.component.ComponentImpl$_AsynchInitializer.run(ComponentImpl.java:304)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)
Caused by: com.ibm.portal.puma.MemberNotFoundException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,o=default organization
at com.ibm.wps.services.puma.DefaultURManager.findUserById(DefaultURManager.java:281)
at com.ibm.wps.services.puma.PumaServiceImpl.findUserById(PumaServiceImpl.java:464)
at com.ibm.icm.jcr.service.member.WPSMemberManagerServiceImpl.init(WPSMemberManagerServiceImpl.java:117)
at com.ibm.icm.jcr.service.ServiceManagerImpl.init(ServiceManagerImpl.java:83)
at com.ibm.icm.jcr.RepositoryImpl.getRepository(RepositoryImpl.java:296)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at com.ibm.icm.jcr.RepositoryFactory.init(RepositoryFactory.java:181)
... 23 more
Caused by: com.ibm.websphere.wmm.exception.MemberNotFoundException: Member "[uid=wpsadmin,o=default organization / null, null]" is not found.
at com.ibm.ws.wmm.ldap.LdapBeanImpl.findByMemberId(LdapBeanImpl.java:900)
at com.ibm.ws.wmm.ldap.LdapAdapterImpl.getMember(LdapAdapterImpl.java:1251)
at com.ibm.ws.wmm.ldap.LdapAdapterImpl.getMember(LdapAdapterImpl.java:1284)
at com.ibm.ws.wmm.MemberRepositoryManager.getMember(MemberRepositoryManager.java:3357)
at com.ibm.ws.wmm.MemberRepositoryManager.getMember(MemberRepositoryManager.java:3194)
at com.ibm.ws.wmm.objectimpl.MemberServiceBeanBase.getMember(MemberServiceBeanBase.java:583)
at com.ibm.websphere.wmm.objects.EJSRemoteStatelessMemberService_14d751a3.getMember(Unknown Source)
at com.ibm.websphere.wmm.objects._MemberService_Stub.getMember(_MemberService_Stub.java:855)
at com.ibm.wps.services.puma.SystemWMMAccessBean$31.run(SystemWMMAccessBean.java:730)
at com.ibm.ws.security.auth.distContextManagerImpl.runAs(distContextManagerImpl.java:2771)
at com.ibm.ws.security.auth.distContextManagerImpl.runAsSystem(distContextManagerImpl.java:2667)
at com.ibm.wps.services.puma.SystemWMMAccessBean.getMember(SystemWMMAccessBean.java:736)
at com.ibm.wps.services.puma.DefaultURManager.findUserById(DefaultURManager.java:246)
... 33 more
{code}

[Gabriel Boie]

If the first node is working properly, the second one should too. Have
you perform a full synchronization to ensure all the security settings
are pushed from the
DMGR to the nodes? Restart the DMGR and the nodeagents on each node
after a full synchronization and try again.

[ff...@us.ibm.com]

Check your icm.properties. It's under /jcr/lib/com/ibm/icm.

-FF

The postings on this site are my own and do not necessarily represent the positions, strategies or opinions of IBM.

[Niall McLoughlin]

Hi fang. That did the trick. Thank you.

I'm confused now through, as I'd assumed the federation process of the secondary node would ensure the configuration would match the primary.
That doesn't appear to be the case.

[ff...@us.ibm.com]

No. That directory is not covered by any mechanism available in WebSphere.

[Niall McLoughlin]

Thanks again fang. That leads to a wider question around Portal clustering. Once I have installed Portal in a secondary node, and federated the
node into the cluster, dmgr should ensure the portal on the secondary node assumes the configuration of the primary.

However, as you've pointed out some directories aren't covered. Also wpconfig.properties on the secondary portal does not contain any of the
configuration attributes from the primary but it is secured against the correct LDAP, DB configuration is correct and the portal is performing
as expected ( apart from the odd exception ).

So, does federating a portal node into a cluster only partially configure the new node ? Where does the portal on the secondary node pick up it's
configuration on startup ?

Thanks in advance.

[huntman25]

Hi,

In a clustered environment, the only files that are synchronized between nodes in a cluster are the files located under this directory:

/config/cells/cellName

and that's it. The Portal server directory is not sync'd (which is why you are required to apply fixes and fixpacks to all nodes in a cluster). A majority of the Portal startup configuration is stored in the WAS configuration (security in /config/cells/cellName/security.xml, database configuration in /config/cells/cellName/clusters/clusterName/resources.xml) so it will be sync'd between nodes.

JCR and the icmear application is a little different in that it depends on the icm.properties file, which is NOT part of the WAS configuration.

Having said that, you should never have to manually edit the icm.properties. What has actually happened is that it looks like a step was missed when building the cluster. On each secondary node, you are required to run the following WPSconfig script:

/WPSconfig.sh enable-jcr-security

This script updates the icm.properties file, along with a few other jcr-related files, with the proper configuration. This step is documented here in the Information Center (steps 2b and 2c):

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp?topic=/com.ibm.wp.ent.doc/wpf/clus_install_enable_ldap.html

and here in the Portal v6.0 cluster guide (page 62, step 13):

http://www-01.ibm.com/support/docview.wss?rs=688&ca=port&uid=swg21254849

Failure to do that step causes the exception you originally posted in this thread, and is also documented in this technote:

http://www-01.ibm.com/support/docview.wss?rs=688&ca=port&uid=swg21298464

Hope that helps!

~HT
The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM

[Niall McLoughlin]

Thanks httweed. That explains it very clearly. I'll double check my documented steps when I federated the second node.