[jboss-cvs] jboss-docs/adminguide/docbook/en/modules ...
Sam Griffith
sam.griffith at jboss.com
Mon Mar 26 13:09:07 EDT 2007
User: sgriffith
Date: 07/03/26 13:09:07
Modified: adminguide/docbook/en/modules appendix-alternative_DBs.xml
Log:
Fixed some more formating errors
Revision Changes Path
1.8 +132 -62 jboss-docs/adminguide/docbook/en/modules/appendix-alternative_DBs.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: appendix-alternative_DBs.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-docs/adminguide/docbook/en/modules/appendix-alternative_DBs.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- appendix-alternative_DBs.xml 26 Mar 2007 16:12:02 -0000 1.7
+++ appendix-alternative_DBs.xml 26 Mar 2007 17:09:07 -0000 1.8
@@ -6,9 +6,9 @@
JBoss utilizes the Hypersonic database as it's default database. While this is good for development and prototyping, for production odds are that you or your company will require another database to be used for production. This appendix covers how to configure JBoss to use an alternative database. For our sample, we've chosen MySQL 5. It's free and readily available for most platforms in use today.
</para>
</section>
- <section id="mysql">
- <title>Using MySQL as the Alternative DB</title>
- <section>
+ <section id="mysql"><title>Using MySQL as the Alternative DB</title>
+
+ <section id="setting-up-mysql">
<title>
Setting up MySQL
</title>
@@ -79,7 +79,7 @@
</para>
</section>
- <section>
+ <section id="adding-mysql-jdbc-driver">
<title>Adding the MySQL JDBC driver</title>
<para>
For the JBoss Application Server and our applications to use the MySQL database, we also need to install the MySQL JDBC drivers. They can be obtained from: <literal>http://www.mysql.com/products/connector/j/</literal>. For our 5.0.27 version download we need the 5.0 versions which can be obtained from <literal>http://dev.mysql.com/downloads/connector/j/5.0.html</literal>. The download contains documentation, etc. for the JDBC connector, but you really only need the <literal>mysql-connector-java-5.0.4-bin.jar</literal> file to get MySQL to with with and be used by JBoss. You'll need to copy that jar file to your JBoss servers <literal>lib</literal> directory. We copied it to our <literal>server/default/lib</literal> directory. This file will now be loaded when JBoss starts up. So if you have the JBoss server running, you'll need to shut down and restart before this jar is available for the App Server to use.
@@ -214,7 +214,7 @@
</para>
</section>
- <section>
+ <section id="creating-datasource-for-mysql">
<title>
Creating a DataSource for MySQL
</title>
@@ -294,10 +294,13 @@
]]>
</programlisting>
</para>
- <para>When you save the file you should see the datasource be bound by JBoss in the console output like below. Each time you save the file the datasource will be bound and unbound, so you may see multiple entries like below.
+ <para>
+ When you save the file you should see the datasource be bound by JBoss in the console output like below. Each time you save the file the datasource will be bound and unbound, so you may see multiple entries like below.
<programlisting>
+<![CDATA[
15:57:26,891 INFO [WrapperDataSourceService] Bound ConnectionManager
'jboss.jca:service=DataSourceBinding,name=MySqlDS' to JNDI name 'java:MySqlDS'
+]]>
</programlisting>
</para>
<para>
@@ -305,10 +308,11 @@
</para>
</section>
- <section>
+ <section id="linking-mysql-datasource-to-your-application">
<title>Linking a Datasource to your Application</title>
<para>
For individual applications JBoss looks for a <literal>jbosscmp-jdbc.xml</literal> file in your applications deployment. To configure your application to use MySQL, look for a jbosscmp-jdbc.xml deployment descriptor in your applications jars files and then make sure the jbosscmp-jdbc settings are like so:
+ </para>
<programlisting>
<![CDATA[
<jbosscmp-jdbc>
@@ -320,6 +324,7 @@
</jbosscmp-jdbc>
]]>
</programlisting>
+ <para>
Although the <literal>datasource-mapping</literal> is optional, it is nice to know the type of the datasource, as this ties directly back to the type-mapping of the data-source.
</para>
<para>For a full set of default datasource mappings look in <literal>.../server/default/conf/standardjbosscmp-jdbc.xml</literal>. In that file you can look for the <literal>mySQL</literal> type mapping.
@@ -329,7 +334,7 @@
</para>
</section>
- <section>
+ <section id="changing-defaultds-to-mysql-for-all-of-jboss">
<title>Changing the DefaultDS for all of JBoss</title>
<para>
To make our <literal>jboss</literal> database now support the app server we need to create the system administrator user <literal>sa</literal> user on our system. We can do that with this set of MySQL commands which are like the ones we did before but for the <literal>sa</literal> user:
@@ -373,7 +378,8 @@
<!-- Use the security domain defined in conf/login-config.xml -->
<!-- Should really make a security domain for MySQL -->
<security-domain>MySqlDbRealm</security-domain>
- <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <!-- corresponding type-mapping in the
+ standardjbosscmp-jdbc.xml (optional) -->
<metadata>
<type-mapping>mySQL</type-mapping>
</metadata>
@@ -385,17 +391,21 @@
<para>
Now we need to go change the <literal>.../server/default/conf/standardjaws.xml</literal> file so that the following elements have the correct values.
<programlisting>
+<![CDATA[
<datasource>java:/DefaultDB</datasource>
<type-mapping>mySQL</type-mapping>
+]]>
</programlisting>
</para>
<para>
Now we need to go change the <literal>.../server/default/conf/standardjbosscmp-jdbc.xml file so that the following elements have the correct values.</literal>
<programlisting>
+<![CDATA[
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>mySQL</datasource-mapping>
<fk-constraint>true</fk-constraint>
+]]>
</programlisting>
</para>
@@ -428,27 +438,42 @@
15:55:03,062 INFO [Server] Home URL: file:/Users/sgriffith/jboss-4.2.0.CR1/
15:55:03,065 INFO [Server] Patch URL: null
15:55:03,066 INFO [Server] Server Name: default
-15:55:03,066 INFO [Server] Server Home Dir: /Users/sgriffith/jboss-4.2.0.CR1/server/default
-15:55:03,067 INFO [Server] Server Home URL: file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/
-15:55:03,067 INFO [Server] Server Log Dir: /Users/sgriffith/jboss-4.2.0.CR1/server/default/log
-15:55:03,068 INFO [Server] Server Temp Dir: /Users/sgriffith/jboss-4.2.0.CR1/server/default/tmp
+15:55:03,066 INFO [Server] Server Home Dir: /Users/sgriffith/jboss-4.2.0.CR1/server
+ /default
+15:55:03,067 INFO [Server] Server Home URL: file:/Users/sgriffith/jboss-4.2.0.CR1
+ /server/default/
+15:55:03,067 INFO [Server] Server Log Dir: /Users/sgriffith/jboss-4.2.0.CR1/server
+ /default/log
+15:55:03,068 INFO [Server] Server Temp Dir: /Users/sgriffith/jboss-4.2.0.CR1/server
+ /default/tmp
15:55:03,069 INFO [Server] Root Deployment Filename: jboss-service.xml
15:55:04,125 INFO [ServerInfo] Java version: 1.5.0_06,Apple Computer, Inc.
-15:55:04,126 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_06-64,"Apple Computer, Inc."
+15:55:04,126 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_06-64,
+ "Apple Computer, Inc."
15:55:04,126 INFO [ServerInfo] OS-System: Mac OS X 10.4.7,ppc
15:55:05,479 INFO [Server] Core system initialized
-15:55:10,464 INFO [WebService] Using RMI server codebase: http://Sam-Griffiths.local:8083/
-15:55:10,593 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
-15:55:12,404 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
-15:55:12,404 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
+15:55:10,464 INFO [WebService] Using RMI server codebase:
+ http://Sam-Griffiths.local:8083/
+15:55:10,593 INFO [Log4jService$URLWatchTimerTask] Configuring from URL:
+ resource:jboss-log4j.xml
+15:55:12,404 INFO [TransactionManagerService] JBossTS Transaction Service
+ (JTA version) - JBoss Inc.
+15:55:12,404 INFO [TransactionManagerService] Setting up property manager
+ MBean and JMX layer
15:55:12,640 INFO [TransactionManagerService] Starting recovery manager
15:55:13,196 INFO [TransactionManagerService] Recovery manager started
-15:55:13,197 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
+15:55:13,197 INFO [TransactionManagerService] Binding TransactionManager
+ JNDI Reference
15:55:21,607 INFO [ServiceEndpointManager] jbossws-1.2.0.CR2 (date=200701061621)
15:55:24,157 INFO [Embedded] Catalina naming disabled
-15:55:24,275 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
-15:55:24,278 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
-15:55:24,781 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
+15:55:24,275 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in
+ the classpath. Will load the default rule set.
+15:55:24,278 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in
+ the classpath. Will load the default rule set.
+15:55:24,781 INFO [AprLifecycleListener] The Apache Tomcat Native library which
+ allows optimal performance in production environments was not found on the
+ java.library.path: .:/Library/Java/Extensions:/System/Library/Java
+ /Extensions:/usr/lib/java
15:55:25,099 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-8080
15:55:25,101 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-8009
15:55:25,102 INFO [Catalina] Initialization processed in 820 ms
@@ -456,22 +481,36 @@
15:55:25,109 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.0.snapshot
15:55:25,255 INFO [StandardHost] XML validation disabled
15:55:25,287 INFO [Catalina] Server startup in 185 ms
-15:55:25,665 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
-15:55:27,358 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
-15:55:28,189 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.sar/ROOT.war/
-15:55:28,498 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp3387jbossws-context-exp.war/
-15:55:28,842 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
+15:55:25,665 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy
+ /http-invoker.sar/invoker.war/
+15:55:27,358 INFO [WebappLoader] Dual registration of jndi stream handler: factory
+ already defined
+15:55:28,189 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy
+ /jboss-web.sar/ROOT.war/
+15:55:28,498 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy
+ /tmp3387jbossws-context-exp.war/
+15:55:28,842 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy
+ /jms/jbossmq-httpil.sar/jbossmq-httpil.war/
15:55:29,282 WARN [DeployerInterceptorJSE] Cannot load servlet class: org.jboss.web.tomcat.tc5.StatusServlet
-15:55:31,180 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
+15:55:31,180 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy
+ /management/console-mgr.sar/web-console.war/
15:55:32,379 INFO [MailService] Mail Service bound to java:/Mail
-15:55:32,931 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
-15:55:33,096 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
-15:55:33,161 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
-15:55:33,316 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
-15:55:33,490 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
-15:55:33,547 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
-15:55:34,322 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
-15:55:34,990 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
+15:55:32,931 INFO [RARDeployment] Required license terms exist, view META-INF
+ /ra.xml in .../deploy/jboss-ha-local-jdbc.rar
+15:55:33,096 INFO [RARDeployment] Required license terms exist, view META-INF
+ /ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
+15:55:33,161 INFO [RARDeployment] Required license terms exist, view META-INF
+ /ra.xml in .../deploy/jboss-local-jdbc.rar
+15:55:33,316 INFO [RARDeployment] Required license terms exist, view META-INF
+ /ra.xml in .../deploy/jboss-xa-jdbc.rar
+15:55:33,490 INFO [RARDeployment] Required license terms exist, view META-INF
+ /ra.xml in .../deploy/jms/jms-ra.rar
+15:55:33,547 INFO [RARDeployment] Required license terms exist, view META-INF
+ /ra.xml in .../deploy/mail-ra.rar
+15:55:34,322 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
+ 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
+15:55:34,990 INFO [WrapperDataSourceService] Bound ConnectionManager
+ 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
15:55:38,116 INFO [A] Bound to JNDI name: queue/A
15:55:38,123 INFO [B] Bound to JNDI name: queue/B
15:55:38,129 INFO [C] Bound to JNDI name: queue/C
@@ -481,12 +520,15 @@
15:55:38,291 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
15:55:38,298 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
15:55:38,307 INFO [testQueue] Bound to JNDI name: queue/testQueue
-15:55:38,488 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
+15:55:38,488 INFO [UILServerILService] JBossMQ UIL service available
+ at : /0.0.0.0:8093
15:55:38,562 INFO [DLQ] Bound to JNDI name: queue/DLQ
-15:55:38,743 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
+15:55:38,743 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console,
+ warUrl=.../deploy/jmx-console.war/
15:55:39,245 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-8080
15:55:39,376 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-8009
-15:55:39,480 INFO [Server] JBoss (MX MicroKernel) [4.2.0.CR1 (build: SVNTag=JBoss_4_2_0_CR1 date=200701180935)] Started in 36s:405ms
+15:55:39,480 INFO [Server] JBoss (MX MicroKernel) [4.2.0.CR1
+ (build: SVNTag=JBoss_4_2_0_CR1 date=200701180935)] Started in 36s:405ms
</programlisting>
Now we have JBoss using MySQL as it's default datasource and starting up with no errors.
</para>
@@ -558,7 +600,8 @@
<programlisting>
org.postgresql.Driver Information
Repository cache version:
-org.postgresql.Driver(f688e8).ClassLoader=org.jboss.mx.loading.UnifiedClassLoader3 at da817b{ url=null ,addedOrder=2}
+org.postgresql.Driver(f688e8).ClassLoader=org.jboss.mx.loading.
+ UnifiedClassLoader3 at da817b{ url=null ,addedOrder=2}
..org.jboss.mx.loading.UnifiedClassLoader3 at da817b{ url=null ,addedOrder=2}
....file:/Users/sgriffith/jboss-4.2.0.GA/server/default/lib/activation.jar
....file:/Users/sgriffith/jboss-4.2.0.GA/server/default/lib/antlr.jar
@@ -668,7 +711,8 @@
++++ClassLoader: null
++++Null CodeSource
-### Instance0 found in UCL: org.jboss.mx.loading.UnifiedClassLoader3 at da817b{ url=null ,addedOrder=2}
+### Instance0 found in UCL: org.jboss.mx.loading.
+ UnifiedClassLoader3 at da817b{ url=null ,addedOrder=2}
</programlisting>
</para>
</section>
@@ -690,11 +734,13 @@
<driver-class>org.postgresql.Driver</driver-class>
<user-name>x</user-name>
<password>y</password>
- <!-- sql to call when connection is created. Can be anything, select 1 is valid for PostgreSQL
+ <!-- sql to call when connection is created. Can be anything, select 1
+ is valid for PostgreSQL
<new-connection-sql>select 1</new-connection-sql>
-->
- <!-- sql to call on an existing pooled connection when it is obtained from pool. Can be anything, select 1 is valid for PostgreSQL
+ <!-- sql to call on an existing pooled connection when it is obtained
+ from pool. Can be anything, select 1 is valid for PostgreSQL
<check-valid-connection-sql>select 1</check-valid-connection-sql>
-->
@@ -741,7 +787,8 @@
</para>
<para>When you save the file you should see the datasource be bound by JBoss in the console output like below. Each time you save the file the datasource will be bound and unbound, so you may see multiple entries like below.
<programlisting>
-05:53:24,421 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=PostgresDS' to JNDI name 'java:PostgresDS'
+05:53:24,421 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
+ 'jboss.jca:service=DataSourceBinding,name=PostgresDS' to JNDI name 'java:PostgresDS'
</programlisting>
</para>
<para>
@@ -814,17 +861,21 @@
<para>
Now we need to go change the <literal>.../server/default/conf/standardjaws.xml</literal> file so that the following elements have the correct values.
<programlisting>
+<![CDATA[
<datasource>java:/DefaultDS</datasource>
<type-mapping>PostgreSQL</type-mapping>
+]]>
</programlisting>
</para>
<para>
Now we need to go change the <literal>.../server/default/conf/standardjbosscmp-jdbc.xml file so that the following elements have the correct values.</literal>
<programlisting>
+<![CDATA[
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>PostgreSQL</datasource-mapping>
<fk-constraint>true</fk-constraint>
+]]>
</programlisting>
</para>
@@ -851,14 +902,16 @@
JAVA: java
- JAVA_OPTS: -Dprogram.name=run.sh -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
+ JAVA_OPTS: -Dprogram.name=run.sh -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000
+ -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: /Users/sgriffith/jboss-4.2.0.GA/bin/run.jar
=========================================================================
08:08:39,651 INFO [Server] Starting JBoss (MX MicroKernel)...
-08:08:39,682 INFO [Server] Release ID: JBoss [Trinity] 4.2.0.CR1 (build: SVNTag=JBoss_4_2_0_CR1 date=200701180935)
+08:08:39,682 INFO [Server] Release ID: JBoss [Trinity] 4.2.0.CR1
+ (build: SVNTag=JBoss_4_2_0_CR1 date=200701180935)
08:08:39,718 INFO [Server] Home Dir: /Users/sgriffith/jboss-4.2.0.GA
08:08:39,719 INFO [Server] Home URL: file:/Users/sgriffith/jboss-4.2.0.GA/
08:08:39,721 INFO [Server] Patch URL: null
@@ -881,7 +934,9 @@
08:08:50,425 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
08:08:59,011 INFO [EJB3Deployer] Starting java:comp multiplexer
08:09:04,147 INFO [ServiceEndpointManager] jbossws-1.2.0.SP1 (build=200703111125)
-08:09:08,909 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
+08:09:08,909 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal
+ performance in production environments was not found on the
+ java.library.path: .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
08:09:09,293 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
08:09:09,301 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
08:09:09,301 INFO [Catalina] Initialization processed in 1692 ms
@@ -889,26 +944,40 @@
08:09:09,308 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.0.CR1
08:09:09,561 INFO [Catalina] Server startup in 259 ms
08:09:10,022 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
-08:09:12,530 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/08:09:13,332 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp64413jbossws-context-exp.war/
-08:09:13,947 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
-08:09:17,258 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
+08:09:12,530 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar
+ /invoker.war/08:09:13,332 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp
+ /deploy/tmp64413jbossws-context-exp.war/
+08:09:13,947 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms
+ /jbossmq-httpil.sar/jbossmq-httpil.war/
+08:09:17,258 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management
+ /console-mgr.sar/web-console.war/
08:09:19,185 INFO [MailService] Mail Service bound to java:/Mail
-08:09:19,972 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
-08:09:20,207 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
-08:09:20,427 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
-08:09:20,760 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
-08:09:21,049 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
-08:09:21,292 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
+08:09:19,972 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy
+ /jboss-ha-local-jdbc.rar
+08:09:20,207 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy
+ /jboss-ha-xa-jdbc.rar
+08:09:20,427 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy
+ /jboss-local-jdbc.rar
+08:09:20,760 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy
+ /jboss-xa-jdbc.rar
+08:09:21,049 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy
+ /jms/jms-ra.rar
+08:09:21,292 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy
+ /quartz-ra.rar
08:09:21,426 INFO [QuartzResourceAdapter] start quartz!!!
08:09:21,758 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
08:09:23,286 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
08:09:23,293 INFO [RAMJobStore] RAMJobStore initialized.
-08:09:23,294 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
+08:09:23,294 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from
+ default resource file in Quartz package: 'quartz.properties'
08:09:23,299 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
08:09:23,300 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
-08:09:25,492 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
-08:09:27,139 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
-08:09:27,564 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=PostgresDS' to JNDI name 'java:PostgresDS'
+08:09:25,492 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
+ 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
+08:09:27,139 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
+ 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
+08:09:27,564 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
+ 'jboss.jca:service=DataSourceBinding,name=PostgresDS' to JNDI name 'java:PostgresDS'
08:09:28,283 INFO [A] Bound to JNDI name: queue/A
08:09:28,291 INFO [B] Bound to JNDI name: queue/B
08:09:28,420 INFO [C] Bound to JNDI name: queue/C
@@ -922,7 +991,8 @@
08:09:29,240 INFO [DLQ] Bound to JNDI name: queue/DLQ
08:09:29,472 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
08:09:30,262 INFO [TomcatDeployer] deploy, ctxPath=/quote, warUrl=.../tmp/deploy/tmp64443quote-exp.war/
-08:09:31,086 WARN [JARDeployer] Failed to add deployable jar: file:/Users/sgriffith/jboss-4.2.0.GA/server/default/tmp/deploy/tmp64444jmsclear
+08:09:31,086 WARN [JARDeployer] Failed to add deployable jar: file:/Users/sgriffith
+ /jboss-4.2.0.GA/server/default/tmp/deploy/tmp64444jmsclear
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:203)
More information about the jboss-cvs-commits
mailing list