Ir al contenido principal

WebSphere WSSecurityException error WSVR0009E



El error WSVR0009E,  WSSecurityException es lanzado  cuando  trato de iniciar un Nodo de un Cluster,

#sh startNode.sh


[12/15/11 11:22:07:499 PET] 00000000 WsServerImpl  E   WSVR0009E: Error occurred during startup
com.ibm.ws.exception.RuntimeError: com.ibm.websphere.security.WSSecurityException: null; nested exception is: 
com.ibm.websphere.security.EntryNotFoundException
at com.ibm.ws.security.core.distSecurityComponentImpl.start(distSecurityComponentImpl.java:476)
at com.ibm.ws.security.core.SecurityComponentImpl.start(SecurityComponentImpl.java:104)
at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:538)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:503)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:298)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:214)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:666)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
at org.eclipse.core.launcher.Main.run(Main.java:981)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:340)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:110)
Caused by: com.ibm.websphere.security.WSSecurityException: null; nested exception is: 
com.ibm.websphere.security.EntryNotFoundException
at com.ibm.ws.security.auth.ContextManagerImpl.initialize(ContextManagerImpl.java:2907)
at com.ibm.ws.security.auth.ContextManagerImpl.initialize(ContextManagerImpl.java:2919)
at com.ibm.ws.security.core.SecurityContext.enable(SecurityContext.java:83)
at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:681)
at com.ibm.ws.security.core.distSecurityComponentImpl.start(distSecurityComponentImpl.java:449)
... 30 more
Caused by: com.ibm.websphere.security.WSSecurityException: null; nested exception is: 
com.ibm.websphere.security.EntryNotFoundException
at com.ibm.ws.security.auth.ContextManagerImpl.getServerSubjectInternal(ContextManagerImpl.java:2609)
at com.ibm.ws.security.auth.ContextManagerImpl.getServerSubjectInternal(ContextManagerImpl.java:2254)
at com.ibm.ws.security.auth.ContextManagerImpl.initialize(ContextManagerImpl.java:2891)
... 34 more
Caused by: com.ibm.websphere.security.auth.WSLoginFailedException: null; nested exception is: 
com.ibm.websphere.security.EntryNotFoundException
at com.ibm.ws.security.ltpa.LTPAServerObject.authenticate(LTPAServerObject.java:998)
at com.ibm.ws.security.server.lm.ltpaLoginModule.login(ltpaLoginModule.java:646)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:795)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:209)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:709)
at java.security.AccessController.doPrivileged(AccessController.java:251)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:706)
at javax.security.auth.login.LoginContext.login(LoginContext.java:603)
at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:354)
at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:4078)
at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3768)
at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3764)
at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3526)
at com.ibm.ws.security.auth.ContextManagerImpl.getServerSubjectInternal(ContextManagerImpl.java:2579)
... 36 more
Caused by: java.rmi.RemoteException: null; nested exception is: 
com.ibm.websphere.security.EntryNotFoundException
at com.ibm.ws.security.registry.UserRegistryImpl.createCredential(UserRegistryImpl.java:845)
at com.ibm.ws.security.ltpa.LTPAServerObject.authenticate(LTPAServerObject.java:974)
... 53 more
Caused by: com.ibm.websphere.security.EntryNotFoundException
at com.ibm.ws.wim.registry.util.UniqueIdBridge.getUniqueUserId(UniqueIdBridge.java:251)
at com.ibm.ws.wim.registry.WIMUserRegistry$6.run(WIMUserRegistry.java:365)
at com.ibm.ws.wim.security.authz.jacc.JACCSecurityManager.runAsSuperUser(JACCSecurityManager.java:435)
at com.ibm.ws.wim.security.authz.ProfileSecurityManager.runAsSuperUser(ProfileSecurityManager.java:964)
at com.ibm.ws.wim.registry.WIMUserRegistry.getUniqueUserId(WIMUserRegistry.java:348)
at com.ibm.ws.security.registry.UserRegistryImpl.createCredential(UserRegistryImpl.java:770)
... 54 more
Caused by: com.ibm.websphere.wim.exception.EntityNotFoundException: CWWIM4538E  Multiple principals were found for the 'wpsadmin' principal name.
at com.ibm.ws.wim.registry.util.UniqueIdBridge.getUniqueUserId(UniqueIdBridge.java:230)
... 59 more
[12/15/11 11:22:12:557 PET] 00000000 distSecurityC I   securityServiceStarted is false
[12/15/11 11:22:12:580 PET] 00000000 CGBridgeSubsc I   CWRCB0104I: The core group bridge service has stopped the subscription router.
[12/15/11 11:22:12:594 PET] 00000000 CGBridgeServi I   CWRCB0103I: The core group bridge service has stopped.
[12/15/11 11:22:12:617 PET] 00000000 DCSStackImpl  I   DCSV8011I: DCS Stack DefaultCoreGroup at Member wpscell01\wpsnode1\nodeagent: Member received a request for shutdown.
[12/15/11 11:22:12:683 PET] 00000000 TCPChannel    I   TCPC0002I: TCP Channel TCP_1 has stopped listening on host *  (IPv6) port 9353.




** El error es debido a que el  nodo no levanta por que tiene credenciales invalidos, error en la utentificacion LTPA***


Solucion:


Se debe configurar la seguridad correctamente en el  Deployment Manager. Luego sincronizar el nodo.


#sh syncNode.sh IP_Deployment_Manager PUERTO_SOAP


#sh syncNode.sh 172.16.2.76 10003




ADMU0116I: Tool information is being logged in file
           /usr/IBM/WebSphere/ProcServer/profiles/wpsnode1/logs/syncNode.log
ADMU0128I: Starting tool with the wpsnode1 profile
Realm/Cell Name:
Username: wpsadmin
Password:                                                                                                                                                    ADMU0401I: Begin syncNode operation for node wpsnode1 with Deployment Manager
           172.16.2.76: 10003
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node wpsnode1 has been synchronized with
           Deployment Manager 172.16.2.76: 10003






**Luego  iniciar el Nodo*****


# sh startNode.sh


ADMU0116I: Tool information is being logged in file
           /usr/IBM/WebSphere/ProcServer/profiles/wpsnode1/logs/nodeagent/startServer.log
ADMU0128I: Starting tool with the wpsnode1 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 4718634




Ver el siguiente Link para mas informacion.
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=%2Fcom.ibm.websphere.nd.multiplatform.doc%2Finfo%2Fae%2Fae%2Frxml_syncnode.html

Comentarios

Publicar un comentario

Entradas populares de este blog

Primer CodeLab de Web Services con Mule ESB, JAX WS, SOAP, WSDL, Spring

Primer CodeLab de Web Services usando [ Mule ESB , JAX WS , SOAP , WSDL , Spring ]. en este post no hablaré nada teórico sobre Mule , ya que ello lo pueden encontrar Googleando, será un lab totalmente práctico. Requisitos: - JDK  1.6 - MuleStudio - soapUI Paso a Paso para crear Web Services con Mule : 1. Crear proyecto Mule ( MuleStudio ):  Next > Next > Next > Finish 2.- Crear el Objeto Producto.java package com.dmotta.mule.labuno.mulelabuno.bo; import java.io.Serializable; public class Producto implements Serializable { private String id; private String nombre; private String marca; private String descripcion; public Producto() { } public Producto(String id, String nombre, String marca, String descripcion) { this.id=id; this.nombre=nombre; this.marca=marca; this.descripcion=descripcion; } //getters/setters } 3.- Crear la Interface que publicará los métodos listarProductos() y getDetalleProdu...
2 comentarios
Leer más

RESTful Webservices con Java (Jersey / JAX-RS) - Tutorial Uno

REST con Java (JAX-RS) usando Jersey Este articulo explica como desarrollar RESTful web services en Java con JAX-RS implementacion de Jersey. En este ejemplo se usara SpringSource Tools Suite(Eclipse Helios), Java 1.6, SpringSource TC Server and JAX-RS 1.1. (Jersey 1.4). 1. REST - Representational State Transfer 1.1 Informacion General: En una Arquitectura REST tipicamente se tiene un REST server , el cual provee acceso a los Clientes REST  que acceden a consultar, modificar un Recurso REST . REST permite que los recursos sean presentados en diferentes tipos de datos, "text, html, xml, JSON" .  El Cliente REST  puede generar una peticion de un tipo de dato via el protocolo HTTP. 1.2. HTTP metodos Los metodos estandar HTTP usados en en REST son  PUT, GET, POST, DELETE. 1.3. RESTFul webservices Un RESTFul webservices es basados en metodos HTTP y en el concepto REST.  Por lo general se define URI base para los servicios, los MIME-types sus...
4 comentarios
Leer más