errors during startup
jonathan- Jul 24, 2002 3:45 PMI am trying to get MS SQLServer2000 to work with my JBoss 3.0.0 or 3.0.1RC1. With 3.0.0 I can get JBoss started and then I get an error after it creates the first table in the database so after much aggravation I decided to try 3.0.1RC1. Now I can't get JBoss to start... Below are the last bunch of lines upon startup...followed by my mssql-service.xml file.
Thanks for any help!!
Jonathan
14:46:32,815 INFO [MainDeployer] Deployed package: file:/home/jonathan/jboss-3.0.1RC1/server/default/deploy/jmx-console.war/
14:46:32,820 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
Packages waiting for a deployer:
Incompletely deployed packages:
MBeans waiting for classes:
MBeans waiting for other MBeans:
[ObjectName: jboss.jca:service=LocalTxCM,name=MSSQLDS
state: CONFIGURED
I Depend On: jboss.jca:service=LocalTxDS,name=MSSQLDS
jboss.jca:service=LocalTxPool,name=MSSQLDS
jboss.jca:service=CachedConnectionManager
jboss.security:name=JaasSecurityManager
jboss.jca:service=RARDeployer
Depends On Me: ]
14:46:32,830 INFO [URLDeploymentScanner] Started
14:46:32,830 INFO [MainDeployer] Deployed package: file:/home/jonathan/jboss-3.0.1RC1/server/default/conf/jboss-service.xml14:46:32,835 ERROR [Server] start failed
Incomplete Deployment listing:
Packages waiting for a deployer:
Incompletely deployed packages:
MBeans waiting for classes:
MBeans waiting for other MBeans:
[ObjectName: jboss.jca:service=LocalTxCM,name=MSSQLDS
state: CONFIGURED
I Depend On: jboss.jca:service=LocalTxDS,name=MSSQLDS
jboss.jca:service=LocalTxPool,name=MSSQLDS
jboss.jca:service=CachedConnectionManager
jboss.security:name=JaasSecurityManager
jboss.jca:service=RARDeployer
Depends On Me: ]
at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1081)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:583)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:565)
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:491)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:319)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:216)
at org.jboss.Main.boot(Main.java:142)
at org.jboss.Main$1.run(Main.java:375)
at java.lang.Thread.run(Thread.java:536)
14:46:32,866 ERROR [STDERR] Incomplete Deployment listing:
Packages waiting for a deployer:
Incompletely deployed packages:
MBeans waiting for classes:
MBeans waiting for other MBeans:
[ObjectName: jboss.jca:service=LocalTxCM,name=MSSQLDS
state: CONFIGURED
I Depend On: jboss.jca:service=LocalTxDS,name=MSSQLDS
jboss.jca:service=LocalTxPool,name=MSSQLDS
jboss.jca:service=CachedConnectionManager
jboss.security:name=JaasSecurityManager
jboss.jca:service=RARDeployer
Depends On Me: ]
14:46:32,870 ERROR [STDERR] at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1081)
14:46:32,871 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:583)
14:46:32,872 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:565)
14:46:32,872 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
14:46:32,873 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
14:46:32,874 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
14:46:32,875 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:324)
14:46:32,876 ERROR [STDERR] at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
14:46:32,877 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
14:46:32,877 ERROR [STDERR] at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:319)
14:46:32,878 ERROR [STDERR] at org.jboss.system.server.ServerImpl.start(ServerImpl.java:216)
14:46:32,879 ERROR [STDERR] at org.jboss.Main.boot(Main.java:142)
14:46:32,880 ERROR [STDERR] at org.jboss.Main$1.run(Main.java:375)
14:46:32,881 ERROR [STDERR] at java.lang.Thread.run(Thread.java:536)
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- ======================================================================-->
<!-- 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 -->
<!-- Build jmx-api (build/build.sh all) and view for config documentation -->
<!-- ===================================================================== -->
<!-- Include a login module configuration named MSSQLDbRealm.
Update your login-conf.xml, here is an example for a
ConfiguredIdentityLoginModule:
<application-policy name = "MSSQLDbRealm">
<login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
<module-option name = "principal">yourprincipal</module-option>
<module-option name = "userName">yourusername</module-option>
<module-option name = "password">yourpassword</module-option>
<module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=MSSQLDS</module-option>
</login-module>
</application-policy>
NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
module-option name = "managedConnectionFactoryName"
must match the object name of the ConnectionManager you are configuring here.
-->
<!--uncomment out this line if you are using the MSSQLDbRealm above
MSSQLDbRealm
-->
<depends optional-attribute-name="ManagedConnectionFactoryName">
<!--embedded mbean-->
MSSQLDS
<config-property name="ConnectionURL" type="java.lang.String">jdbc:microsoft:sqlserver://10.97.9.100:1433;DatabaseName=CoreDevel</config-property>
<config-property name="DriverClass" type="java.lang.String">com.microsoft.jdbc.sqlserver.SQLServerDriver</config-property>
<!--set these only if you want only default logins, not through JAAS-->
<config-property name="UserName" type="java.lang.String">xxx</config-property>
<config-property name="Password" type="java.lang.String">xxx</config-property>
<!--Below here are advanced properties -->
<!--hack-->
<depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper
<depends optional-attribute-name="ManagedConnectionPool">
<!--embedded mbean-->
0
50
5000
15
<!--criteria indicates if Subject (from security domain) or app supplied
parameters (such as from getConnection(user, pw)) are used to distinguish
connections in the pool. Choices are
ByContainerAndApplication (use both),
ByContainer (use Subject),
ByApplication (use app supplied params only),
ByNothing (all connections are equivalent, usually if adapter supports
reauthentication)-->
ByContainer
<depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager
<depends optional-attribute-name="JaasSecurityManagerService">jboss.security:name=JaasSecurityManager
java:/TransactionManager
<!--make the rar deploy! hack till better deployment-->
jboss.jca:service=RARDeployer