Re: mssql jdbc 2005 driver and Jboss 3.2.1 w/ jvm 1.3.1_12

Tharon,
You are correct, this driver only supports jvm 1.4 and up:
http://www.microsoft.com/downloads/details.aspx?familyid=e22bc83b-32ff-4474-a44a-22b6ae2c4e17&displaylang=en

System Requirement:
Java Development Kit: 1.4 or later

--
Angel Saenz-Badillos [MS] DataWorks
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
I am now blogging: http://weblogs.asp.net/angelsb/




"Tharon LeBlanc" <tleblanc@xxxxxxxxxxx> wrote in message
news:%23SokG7LLGHA.1124@xxxxxxxxxxxxxxxxxxxxxxx
i think i am getting this error because of the jvm i am running. can i use
this driver on a jboss server that only support jvm 1.3?

setup as follows:

mssql.xml in jboss\server\deploy directory -

<?xml version="1.0" encoding="UTF-8"?>

<!--
===================================================================== -->

-->
<!-- JBoss Server MSSQL data source
-->

-->
<!--
===================================================================== -->

<datasources>
<local-tx-datasource>
<!-- This represents customer #1 -->
<jndi-name>mssql1</jndi-name>

<connection-url>jdbc:sqlserver://192.168.0.146:1433;user=user;password=password;DatabaseName=ivr1</connection-url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
</local-tx-datasource>
</datasources>

code:

/**
* Returns a connection based on a context. Only used in class.
*/
private static void getConnection() {
final String METH_NAME = "DbConnection::getConnection() ";

try {
logger.debug(METH_NAME + ", Trying to get context: " + context);
Context ctx = new InitialContext();
DataSource ds = (DataSource) ctx.lookup(context);
conn = ds.getConnection();
} catch (SQLException e) {
errorCount++;
logger.error(METH_NAME + ", errorCount = " + errorCount);
logger.error(METH_NAME + ", " + e);
} catch (NamingException e) {
errorCount++;
logger.error(METH_NAME + ", errorCount = " + errorCount);
logger.error(METH_NAME + ", " + e);
}
}

context:
// contexts
final static String CONTEXT1 = "java:/mssql1";

error from Jboss:
blah blah... , javax.naming.NameNotFoundException: mssql1 not bound

thanks to all!





.

Relevant Pages

  • Re: User vs. Worker threads
    ... is shut down or the thread terminates itself by calling ... Driver routines that run in a process context other than that of the system ... It has all the worker threads. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Question about FILE_OBJECT
    ... I think your missing something First the driver is an ndis intermediate ... I.E. every time they allocated a new context object they ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Problem with matching kind of NDIS driver.
    ... When it comes to outgoing packets, the reasons why his task is infeasible ... context of different threads. ... NDIS IM filter that is located immediately below ... We are telling you that in a NDIS Intermediate driver the process ...
    (microsoft.public.development.device.drivers)
  • Re: Question about FILE_OBJECT
    ... NDIS IM is a driver that fully conforms to the model, ... I.E. every time they allocated a new context object they ...
    (microsoft.public.win32.programmer.kernel)
  • Re: User vs. Worker threads
    ... Use the NtCurrentProcessmacro to specify the ... Driver routines that run in a process context other than that of the system ... It has all the worker threads. ...
    (microsoft.public.win32.programmer.kernel)
Loading