-
1. Re: JBOSS & Windows 2003 (Server)
cvandyck Jun 23, 2004 12:24 PM (in response to pericodelgado)You should probably give some more information about your environment, such as a stacktrace, DDs, etc relevant to the problem.
-
2. Re: JBOSS & Windows 2003 (Server)
pericodelgado Jun 23, 2004 1:35 PM (in response to pericodelgado)Hi,
it is a part of all the nested exceptions throwed by JBoss (There are one for each Bean of my app):
2004-06-22 14:40:33,265 WARN [org.jboss.system.ServiceController] Problem starting service jboss.j2ee:jndiName=ejb/DepartamentoLocal,service=EJB
org.jboss.deployment.DeploymentException: Error while fixing table name; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (java.sql.SQLException: Connection refused: connect); - nested throwable: (org.jboss.resource.ResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Connection refused: connect)))
at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:67)
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.(JDBCEntityBridge.java:103)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:397)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:339)
at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:198)
at org.jboss.ejb.EntityContainer.start(EntityContainer.java:376)
at org.jboss.ejb.Container.invoke(Container.java:756)
at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1058)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
at $Proxy4.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:413)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy20.start(Unknown Source)
at org.jboss.ejb.EjbModule.startService(EjbModule.java:430)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
at $Proxy4.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:413)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy10.start(Unknown Source)
at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:395)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:806)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy3.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:435)
at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:656)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:261)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1003)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:413)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy2.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:230)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:814)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
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:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:222)
at org.jboss.Main.boot(Main.java:148)
at org.jboss.Main$1.run(Main.java:381)
at java.lang.Thread.run(Thread.java:536)
Caused by: org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (java.sql.SQLException: Connection refused: connect); - nested throwable: (org.jboss.resource.ResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Connection refused: connect))
at org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnection(LocalDataSource.java:106)
at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:38)
... 83 more
Caused by: org.jboss.resource.ResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Connection refused: connect)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:144)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnection(InternalManagedConnectionPool.java:259)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:106)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:323)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:467)
at org.jboss.resource.connectionmanager.LocalTxConnectionManager.getManagedConnection(LocalTxConnectionManager.java:221)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:532)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:822)
at org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnection(LocalDataSource.java:102)
... 84 more
Caused by: java.sql.SQLException: Connection refused: connect
at net.sourceforge.jtds.jdbc.TdsConnection.allocateTds(Unknown Source)
at net.sourceforge.jtds.jdbc.TdsConnection.(Unknown Source)
at net.sourceforge.jtds.jdbc.Driver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:133)
... 92 more -
3. Re: JBOSS & Windows 2003 (Server)
cvandyck Jun 23, 2004 2:11 PM (in response to pericodelgado)We've definitely seen this on some of our deployments, but it's rather going from machine to machine (yours is self contained..).
I'd recommend going into the network config under 2003 server (or whatever the software firewall equivalent is under 2k3 server) and making sure that localhost access on your sql server port is allowed. -
4. Re: JBOSS & Windows 2003 (Server)
pericodelgado Jun 23, 2004 2:14 PM (in response to pericodelgado)I've tested it and I connect to this SQL/Server through ODBC & OLE DB connection and it runs. The only connection that it's refusing is JDBC :|
Some idea? -
5. Re: JBOSS & Windows 2003 (Server)
cvandyck Jun 23, 2004 2:17 PM (in response to pericodelgado)It might be something wrong with your datasource config. Try posting your mssql-ds.xml file in between [ code ] ... [ / code ] tags.
-
6. Re: JBOSS & Windows 2003 (Server)
pericodelgado Jun 23, 2004 2:24 PM (in response to pericodelgado)The problem is that in Windows 2000 is running ok.
It's my Datasource config:
<config-property name="ConnectionURL" type="java.lang.String">jdbc:jtds:sqlserver://172.22.141.214:1433/IBCAMPAIGN</config-property>
<config-property name="DriverClass" type="java.lang.String">net.sourceforge.jtds.jdbc.Driver</config-property>
<!--set these only if you want only default logins, not through JAAS-->
<config-property name="UserName" type="java.lang.String">ibercaja</config-property>
<config-property name="Password" type="java.lang.String">ibercaja</config-property> -
7. Re: JBOSS & Windows 2003 (Server)
john_anderson_ii Jun 23, 2004 4:53 PM (in response to pericodelgado)If your MSSQL Server is on the same box as your Jboss Server, you might want to change the 172.22.141.214:1433 to localhost:1433 or 127.0.0.1:1433. If you do that and can then connect, you know you have a misconfiguration in your local firewalling policies or whatever. Also check to make sure the Database name is correct.
If all that fails, it might not be a bad idea to check with the JDBC driver supplier and see if they have any known issues with or patches out for Win2k3 -
8. Re: JBOSS & Windows 2003 (Server)
dannyyates Jun 24, 2004 4:00 AM (in response to pericodelgado)Have you read the jTDS documentation? Your JDBC URL is invalid.
-
9. Re: JBOSS & Windows 2003 (Server)
dannyyates Jun 24, 2004 4:02 AM (in response to pericodelgado)Eeek. My bad. Sorry, it's fine - I thought IBCAMPAIGN was an instance name, but it's a database name. Sorry.
-
10. Re: JBOSS & Windows 2003 (Server)
pericodelgado Jun 24, 2004 4:59 AM (in response to pericodelgado)I'd tried to change database IP to localhost or 127.0.0.1, but it didn't run. It's too strange because ODBC and OLE DB connection runs ok, furthermore I can't test a JDBC app test to solve the test...
-
11. Re: JBOSS & Windows 2003 (Server)
darranl Jun 24, 2004 9:11 AM (in response to pericodelgado)furthermore I can't test a JDBC app test to solve the test...
Why can't you, it would only be a few lines of code. -
12. Re: JBOSS & Windows 2003 (Server)
pericodelgado Jun 25, 2004 6:14 AM (in response to pericodelgado)Because, I have only these JDBC driver installed in W2003 machine... Now I'm in the office and I'll try to replicate the enviroment to try to make it run.
I'll post some news.
Thank you everybody