[JBoss JIRA] (AS7-5111) Data Source Error Specifics are Lacking
by Jim Tyrrell (JIRA)
Jim Tyrrell created AS7-5111:
--------------------------------
Summary: Data Source Error Specifics are Lacking
Key: AS7-5111
URL: https://issues.jboss.org/browse/AS7-5111
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Affects Versions: 7.1.2.Final (EAP)
Reporter: Jim Tyrrell
Assignee: Heiko Braun
Start up a host-slave with something like:
./domain.sh --host-config=host-master.xml
Update the host-slave.xml with a 29999 in place of the 9999 management port so we can easily run on the same machine.
Start it with:
./domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1
Crate and login with an admin user on the console:
Go to the manage deployments tab and upload mysql-connector-java-5.1.20-bin.jar. I assume any driver will work, but this test case is with MySQL.
In the console you should see the following:
[Server:server-two] 14:15:02,689 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "mysql-connector-java-5.1.20-bin.jar"
[Server:server-one] 14:15:02,700 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "mysql-connector-java-5.1.20-bin.jar"
[Server:server-one] 14:15:02,884 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
[Server:server-one] 14:15:02,893 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011907: Register module: Module "deployment.mysql-connector-java-5.1.20-bin.jar:main" from Service Module Loader
[Server:server-two] 14:15:02,895 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
[Server:server-two] 14:15:02,903 INFO [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011907: Register module: Module "deployment.mysql-connector-java-5.1.20-bin.jar:main" from Service Module Loader
[Server:server-one] 14:15:03,048 INFO [org.jboss.as.server] (host-controller-connection-threads - 2) JBAS018559: Deployed "mysql-connector-java-5.1.20-bin.jar"
[Server:server-two] 14:15:03,049 INFO [org.jboss.as.server] (host-controller-connection-threads - 2) JBAS018559: Deployed "mysql-connector-java-5.1.20-bin.jar"
Showing the jar file has been deployed.
Now create a JNDI name for it in the console...
Make sure you select a profile that works, in this example full or full-ha will work.
Any Name: SampleDS
JNDI Name of: java:/IntegrationDatasource
Connection URL: jdbc:mysql://localhost:3306/greenfield
Username: root
Password: blank
At this point it does not matter that MySQL is not installed..and that of course the user does not exist...as we will not see this misconfiguration show up at all.
Once I save this off and enable it I see something like this in my console:
[Server:server-one] 14:19:29,411 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:/IntegrationDatasource]
Great it is bound...but...
Lets deploy an application...SampleApp.war
You see it has deployed:
[Server:server-one] 14:21:15,633 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "SampleApp.war"
[Server:server-two] 14:21:15,634 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "SampleApp.war"
[Server:server-two] 14:21:15,889 INFO [org.jboss.as.osgi] (MSC service thread 1-7) JBAS011907: Register module: Module "deployment.SampleApp.war:main" from Service Module Loader
[Server:server-one] 14:21:15,916 INFO [org.jboss.as.osgi] (MSC service thread 1-3) JBAS011907: Register module: Module "deployment.SampleApp.war:main" from Service Module Loader
[Server:server-two] 14:21:15,998 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /SampleApp
[Server:server-one] 14:21:16,024 INFO [org.jboss.web] (MSC service thread 1-6) JBAS018210: Registering web context: /SampleApp
[Server:server-one] 14:21:16,080 INFO [org.jboss.as.server] (host-controller-connection-threads - 5) JBAS018559: Deployed "SampleApp.war"
[Server:server-two] 14:21:16,082 INFO [org.jboss.as.server] (host-controller-connection-threads - 5) JBAS018559: Deployed "SampleApp.war"
Going to this URL:
http://localhost:8080/SampleApp/
I see this in my web browser:
java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/IntegrationDatasource
[Server:server-one] 14:22:04,161 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http-/127.0.0.1:8080-2) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
[Server:server-one] at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:277)
[Server:server-one] at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:235)
[Server:server-one] at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:761)
[Server:server-one] at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:343)
[Server:server-one] at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:397)
[Server:server-one] at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:365)
[Server:server-one] at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:329)
[Server:server-one] at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:302)
[Server:server-one] at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:464)
[Server:server-one] at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:139)
[Server:server-one] at org.apache.jsp.index_jsp._jspService(index_jsp.java:73)
[Server:server-one] at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1]
[Server:server-one] at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1]
[Server:server-one] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
[Server:server-one] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:]
[Server:server-one] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_32]
[Server:server-one] Caused by: java.sql.SQLException: Access denied for user 'root'@'localhost' (using password: NO)
[Server:server-one] at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)
[Server:server-one] at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4096)
[Server:server-one] at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4028)
[Server:server-one] at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:951)
[Server:server-one] at com.mysql.jdbc.MysqlIO.proceedHandshakeWithPluggableAuthentication(MysqlIO.java:1717)
[Server:server-one] at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1276)
[Server:server-one] at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2395)
[Server:server-one] at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2428)
[Server:server-one] at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2213)
[Server:server-one] at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:797)
[Server:server-one] at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47)
[Server:server-one] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.6.0_32]
[Server:server-one] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [rt.jar:1.6.0_32]
[Server:server-one] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [rt.jar:1.6.0_32]
[Server:server-one] at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [rt.jar:1.6.0_32]
[Server:server-one] at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
[Server:server-one] at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:389)
[Server:server-one] at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:305)
[Server:server-one] at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:249)
[Server:server-one] ... 29 more
[Server:server-one]
[Server:server-one] 14:22:04,170 ERROR [stderr] (http-/127.0.0.1:8080-2) java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/IntegrationDatasource
[Server:server-one] 14:22:04,170 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:147)
[Server:server-one] 14:22:04,170 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.jsp.index_jsp._jspService(index_jsp.java:73)
[Server:server-one] 14:22:04,171 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
[Server:server-one] 14:22:04,171 ERROR [stderr] (http-/127.0.0.1:8080-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[Server:server-one] 14:22:04,171 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
[Server:server-one] 14:22:04,171 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
[Server:server-one] 14:22:04,172 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
[Server:server-one] 14:22:04,172 ERROR [stderr] (http-/127.0.0.1:8080-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[Server:server-one] 14:22:04,172 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
[Server:server-one] 14:22:04,172 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
[Server:server-one] 14:22:04,173 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
[Server:server-one] 14:22:04,173 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
[Server:server-one] 14:22:04,173 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
[Server:server-one] 14:22:04,173 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
[Server:server-one] 14:22:04,174 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[Server:server-one] 14:22:04,174 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[Server:server-one] 14:22:04,174 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
[Server:server-one] 14:22:04,178 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[Server:server-one] 14:22:04,178 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)
[Server:server-one] 14:22:04,178 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)
[Server:server-one] 14:22:04,178 ERROR [stderr] (http-/127.0.0.1:8080-2) at java.lang.Thread.run(Thread.java:662)
[Server:server-one] 14:22:04,179 ERROR [stderr] (http-/127.0.0.1:8080-2) Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/IntegrationDatasource
[Server:server-one] 14:22:04,179 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:390)
[Server:server-one] 14:22:04,179 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:302)
[Server:server-one] 14:22:04,180 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:464)
[Server:server-one] 14:22:04,180 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:139)
[Server:server-one] 14:22:04,180 ERROR [stderr] (http-/127.0.0.1:8080-2) ... 20 more
[Server:server-one] 14:22:04,181 ERROR [stderr] (http-/127.0.0.1:8080-2) Caused by: javax.resource.ResourceException: IJ000658: Unexpected throwable while trying to create a connection: null
[Server:server-one] 14:22:04,181 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:371)
[Server:server-one] 14:22:04,181 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:397)
[Server:server-one] 14:22:04,181 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:365)
[Server:server-one] 14:22:04,182 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:329)
[Server:server-one] 14:22:04,182 ERROR [stderr] (http-/127.0.0.1:8080-2) ... 23 more
[Server:server-one] 14:22:04,182 ERROR [stderr] (http-/127.0.0.1:8080-2) Caused by: javax.resource.ResourceException: Could not create connection
[Server:server-one] 14:22:04,182 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:277)
[Server:server-one] 14:22:04,183 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:235)
[Server:server-one] 14:22:04,183 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:761)
[Server:server-one] 14:22:04,183 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:343)
[Server:server-one] 14:22:04,184 ERROR [stderr] (http-/127.0.0.1:8080-2) ... 26 more
[Server:server-one] 14:22:04,184 ERROR [stderr] (http-/127.0.0.1:8080-2) Caused by: java.sql.SQLException: Access denied for user 'root'@'localhost' (using password: NO)
[Server:server-one] 14:22:04,184 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)
[Server:server-one] 14:22:04,184 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4096)
[Server:server-one] 14:22:04,184 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4028)
[Server:server-one] 14:22:04,185 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:951)
[Server:server-one] 14:22:04,185 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.MysqlIO.proceedHandshakeWithPluggableAuthentication(MysqlIO.java:1717)
[Server:server-one] 14:22:04,185 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1276)
[Server:server-one] 14:22:04,185 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2395)
[Server:server-one] 14:22:04,186 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2428)
[Server:server-one] 14:22:04,186 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2213)
[Server:server-one] 14:22:04,186 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:797)
[Server:server-one] 14:22:04,186 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47)
[Server:server-one] 14:22:04,187 ERROR [stderr] (http-/127.0.0.1:8080-2) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[Server:server-one] 14:22:04,187 ERROR [stderr] (http-/127.0.0.1:8080-2) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[Server:server-one] 14:22:04,187 ERROR [stderr] (http-/127.0.0.1:8080-2) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[Server:server-one] 14:22:04,187 ERROR [stderr] (http-/127.0.0.1:8080-2) at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
[Server:server-one] 14:22:04,188 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
[Server:server-one] 14:22:04,188 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:389)
[Server:server-one] 14:22:04,188 ERROR [stderr] (http-/127.0.0.1:8080-2) at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:305)
[Server:server-one] 14:22:04,188 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:249)
[Server:server-one] 14:22:04,188 ERROR [stderr] (http-/127.0.0.1:8080-2) ... 29 more
[Server:server-one] 14:22:04,189 ERROR [stderr] (http-/127.0.0.1:8080-2) error message
After this long stream of messages I finally figure out I have a user problem:
We need a validate JDBC Connection in the Console.
A validation should automatically occur when I create/deploy the datasource, the fact that it is bound is not enough, we need to make sure it works. That way I can fix the connection if I am having any issues before I deploy my war file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (AS7-4862) Remote EJB SFSB load balancing still very suboptimal
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-4862:
-----------------------------------
Summary: Remote EJB SFSB load balancing still very suboptimal
Key: AS7-4862
URL: https://issues.jboss.org/browse/AS7-4862
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.2.Final (EAP)
Reporter: Radoslav Husar
Assignee: jaikiran pai
Fix For: 7.1.3.Final (EAP)
Looking at the load-balancing again, it seems still wrong. Checking the logs, servers were started *and cluster was formed* ~10 seconds prior to starting the client and load-balancing was roughly:
* node perf18: ~50% of sessions
* node perf19: 0
* node perf20: 0
* node perf21: ~50% of sessions
I let all the session to be created in one minute (not all at once).
The nodes were also specified in the properties.
{noformat}
node perf18
[JBossINF] 07:01:53,991 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (CacheService lifecycle - 1) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
node perf19
[JBossINF] 07:01:53,781 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-19,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
node perf20
[JBossINF] 07:01:53,781 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-14,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
node perf21
[JBossINF] 07:01:53,780 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-12,null) ISPN000094: Received new cluster view: [perf19/ejb|3] [perf19/ejb, perf21/ejb, perf20/ejb, perf18/ejb]
controller node
2012/05/22 07:02:02:932 EDT [DEBUG][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Setting thread count: 2000, was: 0
2012/05/22 07:02:53:731 EDT [DEBUG][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - All runners (2000) started in 50799 milliseconds
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (AS7-5946) jboss-ejb3.xml faults fail silently and result in a hanging thread
by Stephen Coy (JIRA)
Stephen Coy created AS7-5946:
--------------------------------
Summary: jboss-ejb3.xml faults fail silently and result in a hanging thread
Key: AS7-5946
URL: https://issues.jboss.org/browse/AS7-5946
Project: Application Server 7
Issue Type: Bug
Components: EE, EJB
Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1
Environment: MacOS X 10.8.2
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10-428-11M3811)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01-428, mixed mode)
Reporter: Stephen Coy
Assignee: David Lloyd
Attachments: migration-demo.tar.gz
The attached maven application project has a subtle typo in a JNDI name in the jboss-ejb3.xml file.
The deployment process results in a hanging thread shown below. There are no diagnostic log messages at all to indicate what the problem could be.
A second consequence of this hung thread is that the server process can only be terminated with a "kill -9 <pid>".
Note that it is deliberately a JEE5 compatible application.
"management-handler-thread - 4" prio=5 tid=7f843c0bf000 nid=0x10a866000 in Object.wait() [10a864000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <7d42d05f8> (a org.jboss.as.controller.ContainerStateMonitor)
at java.lang.Object.wait(Object.java:485)
at org.jboss.as.controller.ContainerStateMonitor.awaitContainerStateChangeReport(ContainerStateMonitor.java:158)
- locked <7d42d05f8> (a org.jboss.as.controller.ContainerStateMonitor)
at org.jboss.as.controller.ModelControllerImpl.awaitContainerStateChangeReport(ModelControllerImpl.java:442)
at org.jboss.as.controller.OperationContextImpl.awaitModelControllerContainerMonitor(OperationContextImpl.java:147)
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:261)
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211)
at org.jboss.as.server.deployment.DeploymentHandlerUtil$1.execute(DeploymentHandlerUtil.java:123)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397)
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284)
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211)
at org.jboss.as.server.deployment.DeploymentDeployHandler.execute(DeploymentDeployHandler.java:75)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397)
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284)
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211)
at org.jboss.as.server.deployment.DeploymentAddHandler.execute(DeploymentAddHandler.java:168)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397)
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284)
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211)
at org.jboss.as.controller.CompositeOperationHandler.execute(CompositeOperationHandler.java:85)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397)
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284)
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211)
at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:473)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397)
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284)
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:126)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:111)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Locked ownable synchronizers:
- <7d42a5150> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
- <7d4f3b598> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JGRP-1545) UNICAST2: message sent before channel is connected leads to exception
by Bela Ban (JIRA)
Bela Ban created JGRP-1545:
------------------------------
Summary: UNICAST2: message sent before channel is connected leads to exception
Key: JGRP-1545
URL: https://issues.jboss.org/browse/JGRP-1545
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.3
When a *unicast* request is received before the first view is received (which sets the channel to connected), and a response to the request is sent, then the response sending throws an exception as the channel hasn't yet been connected (see stack trace below).
Reason:
What happens when a channel is created is:
- JChannel.connect() is called by the user
- As part of this, start() is called in every protocol
- UDP.start() creates the sockets and starts the socket listener which will receive messages from now on and pass them up
- Connect() now sends a JOIN request to the coordinator and receives the JOIN response or become singleton member
- In either case, a new view is installed, which sets the channel to connected
If, between starting the socket listener and setting the channel to connected, a *unicast* message is received, and it sends a response then you'll get the behavior below.
In NAKACK2, this doesn't happen, as all messages received in the same time frame are queued and replayed when the channel becomes connected.
I could implement the same behavior for UNICAST2, but I'd like to know more about how you got into this situation. What were the steps executed ?
The only way this could happen I can think of is that the coordinator sent a unicast message to P right after it sent the JOIN response to P, e.g. in the view change which includes P. Does this happen in Infinispan code ?
{quote}
13:29:45,467 ERROR (OOB-1,ISPN,NodeB-50197:) [UNICAST2] couldn't deliver OOB message [dst: NodeB-50197, src: NodeA-40526 (3 headers), size=118 bytes, flags=OOB|DONT_BUNDLE]
java.lang.IllegalStateException: channel is not connected
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.down(MessageDispatcher.java:621)
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:535)
at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:390)
at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:248)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:604)
at org.jgroups.JChannel.up(JChannel.java:688)
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1020)
at org.jgroups.protocols.FRAG2.up(FRAG2.java:181)
at org.jgroups.protocols.FC.up(FC.java:479)
at org.jgroups.protocols.pbcast.GMS.up(GMS.java:896)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:244)
at org.jgroups.protocols.UNICAST2.handleDataReceived(UNICAST2.java:736)
at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:414)
at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:606)
at org.jgroups.protocols.MERGE2.up(MERGE2.java:205)
at org.jgroups.protocols.Discovery.up(Discovery.java:359)
at org.jgroups.protocols.TP.passMessageUp(TP.java:1294)
at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1857)
at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1830)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (AS7-5913) RAR (inbound adapter) inside EAR does not see JAR files in EAR/lib
by Juan José Olmedilla Arregui (JIRA)
Juan José Olmedilla Arregui created AS7-5913:
------------------------------------------------
Summary: RAR (inbound adapter) inside EAR does not see JAR files in EAR/lib
Key: AS7-5913
URL: https://issues.jboss.org/browse/AS7-5913
Project: Application Server 7
Issue Type: Bug
Environment: JBoss 7.1.2 on Windows 7 and Windos Vista
Reporter: Juan José Olmedilla Arregui
-I have a RAR file and EJB JAR inside my EAR.
The RAR includes several JAR libraries only used by it which are packed within it.
- The EJB JAR includes an MDB that receives the inbound messages from the Resource Adapter and therefore needs to have access to the same MessageListener interface which is in the common JAR file library included in EAR/lib.
- The RAR has a dependency on the common MessageListener interface included in the JAR file sitting in EAR/lib
- The project is a maven multi-module project using maven jar (for the commong library where the interface is), ejb, ear and rar plugins
- Things I have tried:
1. Including "compile" dependency to the common jar in both, the EJB JAR and RAR. It does not work because it includes two copies of the jar, one in the EAR/lib and one inside the RAR, it deploys but later it fails when a message is received because there are two different bytecodes for the same class.
2. Including a Dependency in the MANIFEST of the RAR pointing to deployment.EARNAME.ear.MYLIBNAME.jar. It does not find that dependency
3. Including a Dependency in the MANIFEST of the RAR pointing to deployment.EARNAME.ear.lib.MYLIBNAME.jar. It does not find that deployment
4. Including the dependency as "provided" in the EJB project as in the RAR, including in both MANIFEST's a dependency on "deployment.MYLIBNAME.jar" and deploying separately the MYLIBNAME.jar and EARNAME.ear. This works but I want a solution that allows me to pack everything in one single EAR file
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months