No matching credentials in Subject

[essington]

With the CVS version from this morning 8/19/2002 I have had my PostgreSQL data sources(that worked perfectly prior to today) pitch the following [root] exception.

javax.resource.ResourceException: No matching credentials in Subject!
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.getConnectionProperties(BaseWrapperManagedConnectionFactory.java:238)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:134)
at org.jboss.resource.connectionmanager.RARDeployment.createManagedConnection(RARDeployment.java:726)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:548)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy22.createManagedConnection(Unknown Source)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnection(InternalManagedConnectionPool.java:254)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:101)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:342)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:535)
at org.jboss.resource.connectionmanager.LocalTxConnectionManager.getManagedConnection(LocalTxConnectionManager.java:224)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:600)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:880)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:102)
at com.grcs.hedgehog.ejb.session.GetDBDataBean.bench(GetDBDataBean.java:273)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:606)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:186)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:77)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:108)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:179)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:61)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:204)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:154)
at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:303)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:351)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:81)
at $Proxy54.bench(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:347)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:225)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:263)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:154)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:121)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:288)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:543)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:356)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:315)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:553)
at org.mortbay.jetty.servlet.WebApplicationHandler.handle(WebApplicationHandler.java:200)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1648)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1598)
at org.mortbay.http.HttpServer.service(HttpServer.java:872)
at org.jboss.jetty.Jetty.service(Jetty.java:531)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:784)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:941)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:799)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:187)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:294)
at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:741)
at java.lang.Thread.run(Thread.java:496)

I have not changed my security domain in the login-config.xml file, nor have I changed my postgres-ds.xml file. This happens when getConnection() is called and prevents the use of the database completely.

has any one else seen this? Is there a solution?

thanks
-jason

[davidjencks]

Can you look and see if the mbean name generated by processing *-ds.xml still matches the one in your login-conf?

When was the last working version checked out?

thanks

[essington]

--Can you look and see if the mbean name generated by processing *-ds.xml still matches the one in your login-conf?

Yup looks the same to me:
<module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=jdbc/ReadOnlyDS</module-option>

and

J2EEApplication= ,J2EEServer=Local,ServiceModule=readOnly-ds.xml,j2eeType=MBean,name=jboss.jca%3aservice%3dLocalTxCM%2cname%3djdbc/ReadOnlyDS

--When was the last working version checked out?

friday was my previous update from cvs (HEAD) and it was working. In trying to find a solution I did revive my old -service.xml file for this datasource and it suffered the same symptoms, if that makes any difference.

I did back off to the 3.2 branch last night and that cured my problem.

Thanks

-jason