Title: RE: [JBoss-user] SQL SERVERPOOL NAME BINDING HANGS the JBOSS initialization process (using weblogic jdbc driver )
I tried using wl driver once, didn't manage to make it work fully, but the first obstacle similar to your symptoms was that the licence file was not found on classpath.
I fixed the situation by putting the jar with the driver explicitly on the classpath in run.bat file.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 17, 2001 12:09 PM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] SQL SERVERPOOL NAME BINDING HANGS the
> JBOSS initialization process (using weblogic jdbc driver )
>
>
> Hi
>
> Which is the real URl syntax in the jboss.cml file for a Weblogic Type
> Driver 4 based
> connection pool - beacuse I have a troublesome situation
> namely that the
> BINDING of the SQL SERVERPOOL HANGS the JBOSS initialization process.
>
>
> Note that the driver signature in the weblogic.jar file is
> weblogic.jdbc.mssqlserver4.Driver
> ( i have put the jar in the lib/ext dir )and
>
> name="Drivers">org.hsql.jdbcDriver,org.enhydra.instantdb.jdbc.
idbDriver,webl
> ogic.jdbc.mssqlserver4.Driver
>
> ## JBOSS JCML (w/TOMCAT) ##
>
>
> name="DefaultDomain:service=XADataSource,name=SQLServerPool">
>
> name="DataSourceClass">org.opentools.minerva.jdbc.xa.wrapper.X
> ADataSourceImp
> l
> SQLServerPool
>
>
>
> name="URL">jdbc:weblogic:mssqlserver4:vnserverdb@localhost:143
> 3
> ^^^ where is this
> JBOSS advised order
> coming from - is it NOT supposed to be
> relevant to the
> signature of
> the driver class ?? ^
> ..
>
>
> then the JDBC driver is indeed loaded up AND the
> [SQLServerPool] is
> Initialized ...
> JBOSS 2.2.1. with Tomcat ...
> [JDBC provider] Loaded
> JDBC-driver:weblogic.jdbc.mssqlserver4.Driver
> <<<<<<<<<<<<<< OK
> .
> [SQLServerPool] Initializing
> [SQLServerPool] Initialized
> <<<<<<<<<<<<<<<<<<< OK
> .
> .. BUT
> ...
> the SQL BINDING does not happen - it just HANGS in there:
>
> [JDBC provider] Starting
> [JDBC provider] Started
> [Hypersonic] ..
> [InstantDB] XA Connection pool InstantDB bound to java:/InstantDB
> ...
> #[DefaultDS] Starting
> [DefaultDS] XA Connection pool DefaultDS bound to java:/DefaultDS
> [DefaultDS] Started
> [SQLServerPool] Starting
> [SQLServerPool] XA Connection pool SQLServerPool bound to
> java:/SQLServerPool ??
> @ IT HANGS HERE
> @@@
>
>
> and in strandardjaws.xml I have :
>
> ## in STANDARDJAWS.XML #
>
>
> java:/SQLServerPool
> MS SQLSERVER
> commented OUT
> commented OUT
>
> ..
> ..
> .
>
> I did not modif. jboss.conf because the JBOSS
> documentation for 2.2.1 says
> I shouldn't put anything
> in there ...
>
>
> Any ideas anybody, please ?
> Do I need to declare smth else in other config. files ??
> (APART from jboss.jcml AND standardjaws.xml ???)
> is JBOSS_AUTO.JCML involved in this ?
>
> TiA
>
> Val N.
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.251 / Virus Database: 124 - Release Date: 26/04/2001
>
>
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
