- This topic has 4 replies, 2 voices, and was last updated 19 years, 12 months ago by
Scott Anderson.
-
AuthorPosts
-
kcopeMemberI’ve variations of this problem in various forums but I have yet to see a solution that works for me, so if i’m posting something that has been resolved countless times on this forum, please reply with the link I need. Otherwise, here’s the deal:
When I deploy my CMP bean (using Eclipse 3.0.2, MyEclipse 3.8.4, JBOSS 4.0.2 and MS SQL Server 2000) I get the following error in the console from JBOSS:14:25:18,628 INFO [EjbModule] Deploying Simple
14:25:21,096 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
org.jboss.resource.JBossResourceException: Could not create connection; – nested throwable: (java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:161)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:508)
atetc…..
Down the final
14:25:22,174 ERROR [URLDeploymentScanner] Incomplete Deployment listing:— MBeans waiting for other MBeans —
ObjectName: jboss.j2ee:jndiName=ejb/Simple,service=EJB
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Error while fixing table name; – nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; – nested throwable: (java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.); – nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; – nested throwable: (java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.)))— MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM —
ObjectName: jboss.j2ee:jndiName=ejb/Simple,service=EJB
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Error while fixing table name; – nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; – nested throwable: (java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.); – nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; – nested throwable: (java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.)))Here are the contents of my mssql-ds.xml file:
<?xml version=”1.0″ encoding=”UTF-8″?>
<!– ===================================================================== –>
<!– –>
<!– JBoss Server Configuration –>
<!– –>
<!– ===================================================================== –><!– $Id: mssql-ds.xml,v 1.3 2004/09/15 14:37:40 loubyansky Exp $ –>
<!– ======================================================================–>
<!– New ConnectionManager setup for Microsoft SQL Server 2000 driver –>
<!– You may download the latest Microsoft JDBC driver from *Microsoft* –>
<!– http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/MSDN-FILES/027/001/779/msdncompositedoc.xml&frame=true –>
<!– ===================================================================== –><datasources>
<local-tx-datasource>
<jndi-name>MSSQLDS</jndi-name>
<connection-url>jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=TestingCMPDB</connection-url>
<driver-class>com.microsoft.jdbc.sqlserver.SQLServerDriver</driver-class>
<user-name>username1</user-name>
<password>password1</password>
<!– sql to call when connection is created
<new-connection-sql>some arbitrary sql</new-connection-sql>
–><!– sql to call on an existing pooled connection when it is obtained from pool
<check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
–><!– corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) –>
<metadata>
<type-mapping>MS SQLSERVER2000</type-mapping>
</metadata>
</local-tx-datasource></datasources>
Anyways, thanks for any help anyone can give me on this one, I’ve really been baning my head against it.
June 29, 2005 at 4:31 pm #231954
Scott AndersonParticipantLooks like you either didn’t start up SQL Server externally before launching the server, or you didn’t
add the MSSQL driver jar to your JBoss configuration (Window > Preferences > MyEclipse > Application Servers > JBoss 4 > Paths)June 30, 2005 at 10:57 am #232009
kcopeMemberSQL Server is definatley running, and I checked the PATH setting as u suggested. I added all three SQL Server Jar files to the PATH just to be sure. Still no go, I cheked the SQL Server instance, it is running on the default 1433. Any other suggestions?
Thanks again.
June 30, 2005 at 3:24 pm #232049
kcopeMemberI found the problem, SQL server needed service pak 3 installed, after that it worked fine. Thanks to anyone who took a look at this for me.
July 1, 2005 at 8:11 am #232085
Scott AndersonParticipantAnd thank you for following up with the solution so we have a searchable record to help others.
-
AuthorPosts