[Installation, Configuration & Deployment] - Deploying EJB Projects
by russray
When I start my server, you can see the EJBs are deploying like there should, but shortly afterwards, errors start appearing like below.
| INFO [BaseLocalProxyFactory] Bound EJB LocalHome 'TaskStatusEJB' to jndi 'local/TaskStatusEJB'
| 14:18:49,347 WARN [StatelessSessionContainer] Could not restore ejb timers
| javax.management.RuntimeMBeanException
| at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:176)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.ejb.Container.restoreTimers(Container.java:766)
| at org.jboss.ejb.SessionContainer.startService(SessionContainer.java:410)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy48.start(Unknown Source)
| at org.jboss.ejb.EjbModule.startService(EjbModule.java:429)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy33.start(Unknown Source)
| at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:662)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
| at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
| at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy34.start(Unknown Source)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy6.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy5.deploy(Unknown Source)
| at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
| at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
| at org.jboss.Main.boot(Main.java:200)
| at org.jboss.Main$1.run(Main.java:490)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.lang.NullPointerException
| at org.jboss.ejb.txtimer.DatabasePersistencePolicy.listTimerHandles(DatabasePersistencePolicy.java:164)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy22.listTimerHandles(Unknown Source)
| at org.jboss.ejb.txtimer.EJBTimerServiceImpl.restoreTimers(EJBTimerServiceImpl.java:408)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| ... 143 more
|
This must be a setting within JBoss that I have not setup properly. Can someone please guide me?
Thanks for taking the time to read and answer my post,
Russ
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986979#3986979
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986979
19Â years, 7Â months
[Security & JAAS/JBoss] - Cannot authenticate using LdapExtLoginModule against AD
by zzzz8
Hi,
When a user attempts to login using LdapExtLoginModule, I get the following error:
2006-11-17 11:38:41,041 DEBUG [org.jboss.security.auth.spi.LdapExtLoginModule] Bad password for username=johndoe
| javax.naming.CommunicationException: mycompany.com:636 [Root exception is java.net.SocketException: Default SSL context init failed: null]
| at com.sun.jndi.ldap.Connection.<init>(Connection.java:194)
| at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
| at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1578)
| at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2596)
| at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283)
| at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
| at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
| at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
| at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
| at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
| at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
| at javax.naming.InitialContext.init(InitialContext.java:223)
| at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
| at org.jboss.security.auth.spi.LdapExtLoginModule.constructInitialLdapContext(LdapExtLoginModule.java:524)
| at org.jboss.security.auth.spi.LdapExtLoginModule.createLdapInitContext(LdapExtLoginModule.java:334)
| at org.jboss.security.auth.spi.LdapExtLoginModule.validatePassword(LdapExtLoginModule.java:229)
| at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:210)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
| at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
| at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
| at java.security.AccessController.doPrivileged(Native Method)
| at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
| at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
| at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:601)
| at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:535)
| at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344)
| at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:491)
| at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:257)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:416)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.net.SocketException: Default SSL context init failed: null
| at javax.net.ssl.DefaultSSLSocketFactory.createSocket(SSLSocketFactory.java:156)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at com.sun.jndi.ldap.Connection.createSocket(Connection.java:311)
| at com.sun.jndi.ldap.Connection.<init>(Connection.java:181)
| ... 43 more
| 2006-11-17 11:38:41,041 TRACE [org.jboss.security.auth.spi.LdapExtLoginModule] abort
| 2006-11-17 11:38:41,041 TRACE [org.jboss.security.plugins.JaasSecurityManager.MyCompanyLDAP] Login failure
| javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required
| at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:213)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
| at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
| at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
| at java.security.AccessController.doPrivileged(Native Method)
| at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
| at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
| at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:601)
| at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:535)
| at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344)
| at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:491)
| at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:257)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:416)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: javax.naming.CommunicationException: mycompany.com:636 [Root exception is java.net.SocketException: Default SSL context init failed: null]
| at com.sun.jndi.ldap.Connection.<init>(Connection.java:194)
| at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
| at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1578)
| at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2596)
| at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283)
| at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
| at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
| at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
| at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
| at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
| at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
| at javax.naming.InitialContext.init(InitialContext.java:223)
| at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
| at org.jboss.security.auth.spi.LdapExtLoginModule.constructInitialLdapContext(LdapExtLoginModule.java:524)
| at org.jboss.security.auth.spi.LdapExtLoginModule.createLdapInitContext(LdapExtLoginModule.java:334)
| at org.jboss.security.auth.spi.LdapExtLoginModule.validatePassword(LdapExtLoginModule.java:229)
| at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:210)
| ... 27 more
| Caused by: java.net.SocketException: Default SSL context init failed: null
| at javax.net.ssl.DefaultSSLSocketFactory.createSocket(SSLSocketFactory.java:156)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at com.sun.jndi.ldap.Connection.createSocket(Connection.java:311)
| at com.sun.jndi.ldap.Connection.<init>(Connection.java:181)
| ... 43 more
Here's my configuration:
<application-policy name="MyCompanyLDAP">
| <authentication>
| <login-module code="org.jboss.security.auth.spi.LdapExtLoginModule" flag="required" >
| <!--
| Some AD configurations may require searching against
| the Global Catalog on port 3268 instead of the usual
| port 389. This is most likely when the AD forest
| includes multiple domains.
| -->
| <module-option name="java.naming.provider.url">ldaps://mycompany:636</module-option>
| <module-option name="bindDN">domain\tester</module-option>
| <module-option name="bindCredential">password</module-option>
| <module-option name="baseCtxDN">dc=mycompany,dc=com</module-option>
| <module-option name="baseFilter">(sAMAccountName={0})</module-option>
| <module-option name="rolesCtxDN">ou=accounts,dc=mycompany,dc=com</module-option>
| <module-option name="roleFilter">(sAMAccountName={0})</module-option>
| <module-option name="roleAttributeID">memberOf</module-option>
| <module-option name="roleAttributeIsDN">true</module-option>
| <module-option name="roleNameAttributeID">cn</module-option>
| <module-option name="roleRecursion">-1</module-option>
| <module-option name="searchScope">SUBTREE_SCOPE</module-option>
| <module-option name="java.naming.security.protocol">ssl</module-option>
| </login-module>
| </authentication>
| </application-policy>
Another interesting thing is that if I remove the java.naming.security.protocol property (i.e. do not use SSL) in the configuration and change the provider URL to ldap://mycompany:389, then it works! Obviously, this begs the question - does my company support ldaps listening at port 636. And the logs don't indicate anything wrong with the trust store...
Please help! Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986977#3986977
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986977
19Â years, 7Â months
[JBossWS] - Error With Runtime generation of WSDL With Headers
by mjrother
I have tried this with jboss 4.0.5 native and with jbossws 1.0.4. I have successfully used an annotated stateless ejb for web services with document / literal / bare configuration. I am now attempting to add a header to each web service request.
Here is the class :
@WebService(name = "test", targetNamespace = "http://com.test", serviceName = "test")
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.BARE)
@Stateless
public class TestService {
@WebMethod
public void logout(@WebParam(name="header", header=true) String value, @WebParam(name="parameters", header=false) String request){
}
@WebMethod
public void logout2(@WebParam(name="header2", header=true) String value, @WebParam(name="test", header=false) String request){
}
}
Note that web service logout works fine. logout2 has problems. As I interpret the problem is with the messages
The code generation always names the body element "parameters". So the only way to get it to work is to name the body element "parameters".
Is there a work around for now>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986976#3986976
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986976
19Â years, 7Â months
[EJB/JBoss] - EJBTimerService persistent timers intermittently lost
by fishervï¼ teoco.com
We are using EJBTimerService w/database persistence policy as provided in the distribution in ejb-deployer.xml. The system generally works, with timers persisted and recovered over many server restarts and timer expirations.
[Versions we are using: JBoss 4.0.5.GA, Hibernate 3.2.0, EJB 2.1, Oracle 9.2]
Over various trials, we have observed all of the TIMER table rows deleted after a random amount of time, from 10 minutes to several hours. All of the timers are deleted, even though many of them are weekly, and were nowhere near expiration. The timers vanish from the TIMERS table while the server is still running. Calling javax.ejb.TimerService.getTimers in the running server still shows the timers, but listing the contents of TIMERS table shows nothing. When the server is restarted, because the timers have dropped out of the table, they are not instantiated in the newly started server.
We added this to log4j.xml:
<category name="org.jboss.ejb.txtimer">
| <priority value="TRACE"/>
| </category>
|
No timer-related exceptions shown in the log. During the time period shown in the log below, the timer rows were deleted from the TIMERS table. The log shows no variation in TimerImpl activity.
Have others reported an issue like this? Is there a way to get more logging from Timer code?
TIA,
Vick
2006-11-17 10:58:49,807 DEBUG http-0.0.0.0-18080-1 [EJBTimerServiceImpl] createTimerService: org.jboss.ejb.txtimer.TimerServiceImpl@11e8e72
2006-11-17 10:58:50,010 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: created
2006-11-17 10:58:50,026 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: started_in_tx
2006-11-17 10:58:50,057 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: created
2006-11-17 10:58:50,057 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: started_in_tx
2006-11-17 10:58:50,073 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: created
2006-11-17 10:58:50,088 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: started_in_tx
2006-11-17 10:58:50,104 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: created
2006-11-17 10:58:50,104 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: started_in_tx
2006-11-17 10:58:50,104 DEBUG http-0.0.0.0-18080-1 [TimerImpl] commit: [id=1,target=[target=jboss.j2ee:jndiName=cc/NotificationController,service=EJB],remaining=223269896,periode=604800000,started_in_tx]
2006-11-17 10:58:50,104 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: active
2006-11-17 10:58:50,104 DEBUG http-0.0.0.0-18080-1 [TimerImpl] commit: [id=2,target=[target=jboss.j2ee:jndiName=cc/NotificationController,service=EJB],remaining=313269896,periode=604800000,started_in_tx]
2006-11-17 10:58:50,104 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: active
2006-11-17 10:58:50,104 DEBUG http-0.0.0.0-18080-1 [TimerImpl] commit: [id=3,target=[target=jboss.j2ee:jndiName=cc/NotificationController,service=EJB],remaining=518469896,periode=604800000,started_in_tx]
2006-11-17 10:58:50,104 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: active
2006-11-17 10:58:50,104 DEBUG http-0.0.0.0-18080-1 [TimerImpl] commit: [id=4,target=[target=jboss.j2ee:jndiName=cc/NotificationController,service=EJB],remaining=838869896,periode=1209600000,started_in_tx]
2006-11-17 10:58:50,104 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: active
2006-11-17 10:58:50,166 DEBUG http-0.0.0.0-18080-1 [EJBTimerServiceImpl] createTimerService: org.jboss.ejb.txtimer.TimerServiceImpl@9b5b2f
2006-11-17 10:58:50,166 INFO http-0.0.0.0-18080-1 [TimerManager] [ com.teoco.cc.services.timer.TimerManager.initializeTimers(TimerManager.java:92) ] ENTER
2006-11-17 10:58:50,166 INFO http-0.0.0.0-18080-1 [TimerManager] [ com.teoco.cc.services.timer.TimerManager.initializeTimers(TimerManager.java:96) ] Found 0 timers in DB.
2006-11-17 10:58:50,166 INFO http-0.0.0.0-18080-1 [TimerManager] [ com.teoco.cc.services.timer.TimerManager.initializeTimers(TimerManager.java:97) ] Found 1 timers in config.
2006-11-17 10:58:50,182 INFO http-0.0.0.0-18080-1 [TimerManager] [ com.teoco.cc.services.timer.TimerManager.initializeTimers(TimerManager.java:172) ] Creating timer: Name: CorrespondenceTimer, Period name: Minute, Period count: 1, Day of Week Name: null, Day of Week Int: 0, Hour of Day: 0, First Expiration Date: Fri Nov 17 10:59:50 EST 2006, Most Recent Expiration Date: None, Period (Minutes): 1
2006-11-17 10:58:50,182 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: created
2006-11-17 10:58:50,229 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: started_in_tx
2006-11-17 10:58:50,307 DEBUG http-0.0.0.0-18080-1 [TimerImpl] commit: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=59844,periode=60000,started_in_tx]
2006-11-17 10:58:50,307 DEBUG http-0.0.0.0-18080-1 [TimerImpl] setTimerState: active
2006-11-17 10:59:50,152 DEBUG Timer-7 [TimerImpl] run: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=-1,periode=60000,active]
2006-11-17 10:59:50,152 DEBUG Timer-7 [TimerImpl] setTimerState: in_timeout
2006-11-17 10:59:51,808 DEBUG Timer-7 [TimerImpl] commit: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=58343,periode=60000,in_timeout]
2006-11-17 10:59:51,808 DEBUG Timer-7 [TimerImpl] setTimerState: active
2006-11-17 11:00:50,152 DEBUG Timer-7 [TimerImpl] run: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=-1,periode=60000,active]
2006-11-17 11:00:50,152 DEBUG Timer-7 [TimerImpl] setTimerState: in_timeout
2006-11-17 11:00:50,965 DEBUG Timer-7 [TimerImpl] commit: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=59186,periode=60000,in_timeout]
2006-11-17 11:00:50,965 DEBUG Timer-7 [TimerImpl] setTimerState: active
2006-11-17 11:01:50,153 DEBUG Timer-7 [TimerImpl] run: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=-2,periode=60000,active]
2006-11-17 11:01:50,153 DEBUG Timer-7 [TimerImpl] setTimerState: in_timeout
2006-11-17 11:01:51,325 DEBUG Timer-7 [TimerImpl] commit: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=58826,periode=60000,in_timeout]
2006-11-17 11:01:51,325 DEBUG Timer-7 [TimerImpl] setTimerState: active
2006-11-17 11:02:50,154 DEBUG Timer-7 [TimerImpl] run: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=-3,periode=60000,active]
2006-11-17 11:02:50,154 DEBUG Timer-7 [TimerImpl] setTimerState: in_timeout
2006-11-17 11:02:50,966 DEBUG Timer-7 [TimerImpl] commit: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=59185,periode=60000,in_timeout]
2006-11-17 11:02:50,966 DEBUG Timer-7 [TimerImpl] setTimerState: active
2006-11-17 11:03:50,155 DEBUG Timer-7 [TimerImpl] run: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=-4,periode=60000,active]
2006-11-17 11:03:50,155 DEBUG Timer-7 [TimerImpl] setTimerState: in_timeout
2006-11-17 11:03:51,326 DEBUG Timer-7 [TimerImpl] commit: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=58825,periode=60000,in_timeout]
2006-11-17 11:03:51,326 DEBUG Timer-7 [TimerImpl] setTimerState: active
2006-11-17 11:04:50,155 DEBUG Timer-7 [TimerImpl] run: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=-4,periode=60000,active]
2006-11-17 11:04:50,155 DEBUG Timer-7 [TimerImpl] setTimerState: in_timeout
2006-11-17 11:04:51,171 DEBUG Timer-7 [TimerImpl] commit: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=58980,periode=60000,in_timeout]
2006-11-17 11:04:51,171 DEBUG Timer-7 [TimerImpl] setTimerState: active
2006-11-17 11:05:50,156 DEBUG Timer-7 [TimerImpl] run: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=-5,periode=60000,active]
2006-11-17 11:05:50,156 DEBUG Timer-7 [TimerImpl] setTimerState: in_timeout
2006-11-17 11:05:51,016 DEBUG Timer-7 [TimerImpl] commit: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=59135,periode=60000,in_timeout]
2006-11-17 11:05:51,016 DEBUG Timer-7 [TimerImpl] setTimerState: active
2006-11-17 11:06:50,157 DEBUG Timer-7 [TimerImpl] run: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=-6,periode=60000,active]
2006-11-17 11:06:50,157 DEBUG Timer-7 [TimerImpl] setTimerState: in_timeout
2006-11-17 11:06:51,157 DEBUG Timer-7 [TimerImpl] commit: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=58994,periode=60000,in_timeout]
2006-11-17 11:06:51,157 DEBUG Timer-7 [TimerImpl] setTimerState: active
2006-11-17 11:07:50,158 DEBUG Timer-7 [TimerImpl] run: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=-7,periode=60000,active]
2006-11-17 11:07:50,158 DEBUG Timer-7 [TimerImpl] setTimerState: in_timeout
2006-11-17 11:07:51,314 DEBUG Timer-7 [TimerImpl] commit: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=58837,periode=60000,in_timeout]
2006-11-17 11:07:51,314 DEBUG Timer-7 [TimerImpl] setTimerState: active
2006-11-17 11:08:50,158 DEBUG Timer-7 [TimerImpl] run: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=-7,periode=60000,active]
2006-11-17 11:08:50,158 DEBUG Timer-7 [TimerImpl] setTimerState: in_timeout
2006-11-17 11:08:51,158 DEBUG Timer-7 [TimerImpl] commit: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=58993,periode=60000,in_timeout]
2006-11-17 11:08:51,158 DEBUG Timer-7 [TimerImpl] setTimerState: active
2006-11-17 11:09:50,456 DEBUG Timer-7 [TimerImpl] run: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=-305,periode=60000,active]
2006-11-17 11:09:50,456 DEBUG Timer-7 [TimerImpl] setTimerState: in_timeout
2006-11-17 11:09:51,722 DEBUG Timer-7 [TimerImpl] commit: [id=5,target=[target=jboss.j2ee:jndiName=cc/ClaimCorrespondenceController,service=EJB],remaining=58429,periode=60000,in_timeout]
2006-11-17 11:09:51,722 DEBUG Timer-7 [TimerImpl] setTimerState: active
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986971#3986971
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986971
19Â years, 7Â months
[JBossWS] - JBossWS1.0.4 doesn't work with JBossAS4.0.4GA
by zhi_hui
I tried to follow JBossWS1.0.4 installation intructions to install JBossWS1.0.4 on top of JBossAS4.0.4GA.
1. Copy lib/jbossws-client.jar to $JBOSS_HOME/client/
2. extracted jbossws.sar to jbossws.sar directory under $JBOSS_HOME/server/default/deploy/
3. download jboss-xml-binding.jar from http://repository.jboss.com/jboss/jbossxb/1.0.0.CR7/lib
4. replace the jboss-xml-binding.jar file in $JBOSS_HOME/client and $JBOSS_HOME/lib with the downloaded one.
After that, I tried to start JBoss, but I saw a lot of exceptions, and http://localhost:8080/jbossws could not be reached. Am I missing anything in the steps? any comments are appreciated.
Part of the exception messages are
-------------------------------------------------------------------------
2006-11-18 02:37:46,187 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Try loading config as XML, url=file:/D:/work/test/jboss-4.0.4.GA/server/default/conf/login-config.xml
2006-11-18 02:37:46,203 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Failed to load config as XML
org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser
at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:100)
at org.jboss.security.auth.login.XMLLoginConfigImpl.loadXMLConfig(XMLLoginConfigImpl.java:319)
at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:287)
...
...
Caused by: org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parser
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJBossXBParser.java:96)
at org.jboss.xb.binding.UnmarshallerImpl.(UnmarshallerImpl.java:55)
at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:96)
... 52 more
Caused by: javax.xml.parsers.ParserConfigurationException: Feature 'http://apache.org/xml/features/xinclude' is not recognized.
at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.(SaxJBossXBParser.java:92)
... 54 more
2006-11-18 02:37:46,203 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Try loading config as Sun format, url=file:/D:/work/test/jboss-4.0.4.GA/server/default/conf/login-config.xml
2006-11-18 02:37:46,218 WARN [org.jboss.security.auth.login.XMLLoginConfigImpl] End loadConfig, failed to load config: file:/D:/work/test/jboss-4.0.4.GA/server/default/conf/login-config.xml
org.jboss.security.auth.login.ParseException: Encountered "<?xml" at line 1, column 1.
Was expecting one of:
...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986966#3986966
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986966
19Â years, 7Â months
[JBoss Seam] - install SEAM and Portal together?
by paulharrington
We are starting a project and wish to use SEAM in a JBoss portal environment. I was looking through the documentation for the 2 technologies, to work out which versions to install.
In the jboss seam FAQ (http://labs.jboss.com/portal/jbossseam/faq) it states
Q: What JBoss AS do I need to run Seam?
A: Since Seam requires the latest edition of EJB3, you need to install JBoss AS from the latest JEMS installer. Make sure that you select the "ejb3" or "ejb3+clustering" profile to include EJB3 support
However,
In the jboss portal 2.6 reference guide it states:
Warning
Make sure to download the JBoss AS Zip version. DO NOT ATTEMPT to deploy JBoss Portal on the installer version of JBoss AS! We are currently working on aligning the Application installer with JBoss Portal.
This suggests they currently can?t be installed together, because one must be installed using the installer, and the other cannot be installed using the installer.
Can anyone clarify how I can install the two technologies together, and if so can I use the latest versions Jboss 2.6 DR, and SEAM 1.1 BETA 2, or should I install earlier versions of one, or both?
Thanks
Paul Harrington
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986962#3986962
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986962
19Â years, 7Â months