Bugs item #570030, was opened at 2002-06-17 09:36
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=570030&group_id=22866
Category: JBossCX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Howard Lewis Ship (hship)
Assigned to: David Jencks (d_jencks)
>Summary: MBean dependency problems not reported
Initial Comment:
I'm in the middle of upgrading from JBoss 2.4.3 to JBoss
3.0.0. I like much
of what I see, but I'm having trouble clearing one key
hurdle.
My database is driven by McKoiDB 0.92; I created a
simple MBean to start
McKoi as a thread inside JBoss, and created a
datasource for it:
[2.4.3 jboss.jcml]
<mbean code="net.sf.tapestry.contrib.mckoi.McKoiDB"
name="DefaultDomain:service=McKoiDB">
<attribute name="RootPath">../db</attribute>
<attribute
name="ConfigPath">../db/vlib.conf</attribute>
</mbean>
<mbean code="org.jboss.jdbc.JdbcProvider"
name="DefaultDomain:service=JdbcProvider,name=McK
oiDB">
<attribute
name="Drivers">com.mckoi.JDBCDriver</attribute>
</mbean>
<mbean code="org.jboss.jdbc.XADataSourceLoader"
name="DefaultDomain:service=XADataSource,name=XA
Vlib">
<attribute name="PoolName">McKoiDB</attribute>
<attribute
name="DataSourceClass">org.jboss.pool.jdbc.xa.wrapp
er.XADataSourceImpl</attr
ibute>
<attribute name="Properties"/>
<attribute
name="URL">jdbc:mckoi://localhost/</attribute>
<attribute
name="GCMinIdleTime">1200000</attribute>
<attribute name="JDBCUser">admin</attribute>
<attribute name="MaxSize">10</attribute>
<attribute name="Password">secret</attribute>
<attribute name="GCEnabled">false</attribute>
<attribute name="InvalidateOnError">false</attribute>
<attribute name="TimestampUsed">false</attribute>
<attribute name="Blocking">true</attribute>
<attribute name="GCInterval">120000</attribute>
<attribute name="IdleTimeout">1800000</attribute>
<attribute
name="IdleTimeoutEnabled">false</attribute>
<attribute name="LoggingEnabled">false</attribute>
<attribute
name="MaxIdleTimeoutPercent">1.0</attribute>
<attribute name="MinSize">0</attribute>
</mbean>
Now, everything's changed in 3.0.0; I've been blindly
attempting to hack the
sample HSQL service into a McKoi service:
<server>
<!--
=========================================
=========================== -->
<!-- New ConnectionManager setup for default hsql dbs --
>
<!-- Build jmx-api (build/build.sh all) and view for config
documentation -->
<!--
=========================================
=========================== -->
<mbean
code="org.jboss.resource.connectionmanager.LocalTxCo
nnectionManager"
name="jboss.jca:service=LocalTxCM,name=McKoiDBDa
taSource">
<depends>
<mbean code="net.sf.tapestry.contrib.mckoi.McKoiDB"
name="jboss:service=McKoiDB">
<attribute
name="RootPath">../server/tapestry/db</attribute>
<attribute
name="ConfigPath">../server/tapestry/db/vlib.conf</attrib
ute>
</mbean>
</depends>
<depends optional-attribute-
name="ManagedConnectionFactoryName">
<!--embedded mbean-->
<mbean
code="org.jboss.resource.connectionmanager.RARDeplo
yment"
name="jboss.jca:service=LocalTxDS,name=McKoiDBDa
taSource">
<attribute name="JndiName">McKoiDB</attribute>
<attribute
name="ManagedConnectionFactoryProperties">
<properties>
<config-property name="ConnectionURL"
type="java.lang.String">jdbc:mckoi://localhost/</config-
property>
<config-property name="DriverClass"
type="java.lang.String">com.mckoi.JDBCDriver</config-
property>
<config-property name="UserName"
type="java.lang.String">admin</config-property>
<config-property name="Password"
type="java.lang.String">secret</config-property>
</properties>
</attribute>
<!--Below here are advanced properties -->
<!--hack-->
<depends
optional-attribute-
name="OldRarDeployment">jboss.jca:service=RARDepl
oyment,n
ame=JBoss LocalTransaction JDBC Wrapper</depends>
<depends>jboss:service=McKoiDB</depends>
</mbean>
</depends>
<depends optional-attribute-
name="ManagedConnectionPool">
<!--embedded mbean-->
<mbean
code="org.jboss.resource.connectionmanager.JBossMan
agedConnectionPool"
name="jboss.jca:service=LocalTxPool,name=McKoiDB"
>
<attribute name="MinSize">0</attribute>
<attribute name="MaxSize">50</attribute>
<attribute
name="BlockingTimeoutMillis">5000</attribute>
<attribute name="IdleTimeoutMinutes">15</attribute>
<!--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)-->
<attribute name="Criteria">ByContainer</attribute>
</mbean>
</depends>
<depends
optional-attribute-
name="CachedConnectionManager">jboss.jca:service=C
achedCo
nnectionManager</depends>
<depends
optional-attribute-
name="JaasSecurityManagerService">jboss.security:na
me=Jaa
sSecurityManager</depends>
<attribute
name="TransactionManager">java:/TransactionManager<
/attribute>
<!--make the rar deploy! hack till better deployment-->
<depends>jboss.jca:service=RARDeployer</depends>
</mbean>
</server>
When I start up JBoss, things look ok:
08:33:55,757 INFO [MainDeployer] Starting deployment
of package:
file:/C:/Work/jboss-3.0.0/server/tapestry/deploy/mckoi-
service.xml
08:33:56,879 WARN [ServiceController]
jboss.jca:service=LocalTxDS,name=McKoiDBDataSourc
e does not implement any
Service methods
08:33:56,889 WARN [ServiceController]
jboss.jca:service=LocalTxDS,name=McKoiDBDataSourc
e does not implement any
Service methods
08:33:56,899 INFO [JBossManagedConnectionPool]
Creating
08:33:56,899 INFO [JBossManagedConnectionPool]
Created
08:33:58,631 INFO [STDOUT] TCP JDBC Server
(multi_threaded) on port: 9157
08:33:58,631 INFO [STDOUT] .
08:33:58,631 INFO [STDOUT] Boot time: 1642ms.
08:33:58,642 INFO [JBossManagedConnectionPool]
Starting
08:33:58,652 INFO [JBossManagedConnectionPool]
Started
08:33:58,662 INFO [MainDeployer] Successfully
completed deployment of
package: file:/C:/Work/jboss-
3.0.0/server/tapestry/deploy/mckoi-service.xml
And I've verified that McKoi database is running, but my
EAR (containing my
CMP entity EJBs) doesn't deploy:
08:34:10,348 INFO [MainDeployer] Starting deployment
of package:
file:/C:/Work/jboss-3.0.0/server/tapestry/deploy/Vlib.ear
08:34:10,368 INFO [EARDeployer] Init J2EE application:
file:/C:/Work/jboss-3.0.0/server/tapestry/deploy/Vlib.ear
08:34:11,991 INFO [EjbModule] Creating
08:34:12,051 INFO [EjbModule] Deploying Person
08:34:12,842 INFO [EjbModule] Deploying Book
08:34:12,882 INFO [EjbModule] Deploying Publisher
08:34:13,032 INFO [EjbModule] Deploying KeyAllocator
08:34:13,122 INFO [EjbModule] Deploying BookQuery
08:34:13,363 INFO [EjbModule] Deploying Operations
08:34:14,975 WARN [ServiceController] Ignoring
request to destroy
non-existant service:
jboss.j2ee:service=EJB,jndiName=vlib/Book
08:34:14,985 WARN [ServiceController] Ignoring
request to destroy
non-existant service:
jboss.j2ee:service=EJB,jndiName=vlib/Person
08:34:14,995 INFO [EjbModule] Remove JSR-77 EJB
Module:
jboss.management.single:J2EEApplication=Vlib.ear,J2E
EServer=Single,j2eeType=
EJBModule,name=VlibBeans.jar
08:34:15,005 ERROR [EjbModule] Initialization failed
org.jboss.deployment.DeploymentException: Error: can't
find data source:
java:/McKoiDB; - nested throwable:
(javax.naming.NameNotFoundException:
McKoiDB not bound)
at
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.
<init>(JDBCEntityBrid
ge.java:99)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.creat
e(JDBCStoreManager.java
:332)
at
org.jboss.ejb.plugins.CMPPersistenceManager.create
(CMPPersistenceManager.jav
a:155)
at org.jboss.ejb.EntityContainer.create
(EntityContainer.java:337)
at org.jboss.ejb.Container.invoke
(Container.java:789)
at org.jboss.ejb.EntityContainer.invoke
(EntityContainer.java:1055)
at
org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:491)
And its right, McKoiDB isn't bound into JNDI (verified
with JNDIView).
----------------------------------------------------------------------
>Comment By: Howard Lewis Ship (hship)
Date: 2002-06-27 07:23
Message:
Logged In: YES
user_id=26816
I'm satisfied ... my problem is solved. You should close this
bug if you have a different one covering the dependcy
problems.
----------------------------------------------------------------------
Comment By: Howard Lewis Ship (hship)
Date: 2002-06-17 14:23
Message:
Logged In: YES
user_id=26816
My previous hunch is confirmed ... once I deploy a few more
of the RARs and services, things start to work.
I noticed in the dev mailing list that there is already a
discussion about tracking and reporting incomplete
deployments.
----------------------------------------------------------------------
Comment By: David Jencks (d_jencks)
Date: 2002-06-17 14:10
Message:
Logged In: YES
user_id=60525
My reading of your log extract makes me thing that
jboss-local-jdbc.rar is missing from your deploy folder.
As far as dependency management, I just added the mbean
operations I recommended in my last post, which should show
you the stalled mbean and what it is waiting for. I think I
will make the deployment scanner report after every scan
that deploys something whether there are any deployment
problems shown in these lists.
----------------------------------------------------------------------
Comment By: Howard Lewis Ship (hship)
Date: 2002-06-17 13:49
Message:
Logged In: YES
user_id=26816
I've taken a fresh look at this, after having a weekend off.
I think I may be on to something. The service (and the
related EAR) is not being deployed into the default JBoss
configuration, its being deployed into a new configuration
named tapestry.
My Ant install script copies selected portions of the default
configuration (and adds additional poritions) ... I believe the
root of the problem is that some of the JDBC-related RARs
are not deployed.
The MBean is never getting started because it is waiting for
the other MBeans, provided by the RAR,to deploy ... which
they never will.
If so, I'll be able to fix it by addining additional RARs.
I think this will likely be the case ... in which case, the *real*
problem is that the dependency logic needs work.
We should be getting some kind of warning that necessary
MBeans don't exist ... I realize that this is somewhat difficult.
Certainly, by the time the server emits its startup message
though, all MBeans defined by all services, .sars or .rars
should be up and running; at this point, a list of all MBeans
that are waiting (due to the dependencies) could be produced,
along with the MBean they are dependant on (including
whether the MBean even exists).
Anyway, I'll play some more to confirm this hypothesis.
----------------------------------------------------------------------
Comment By: Howard Lewis Ship (hship)
Date: 2002-06-17 11:37
Message:
Logged In: YES
user_id=26816
I turned on trace-level logging for org.jboss.system and
org.jboss.deployment. Here's the section for the mckoi
service.
2002-06-17 11:32:03,533 INFO
[org.jboss.deployment.MainDeployer] Starting deployment of
package: file:/C:/jboss-3.0.0/server/tapestry/deploy/mckoi-
service.xml
2002-06-17 11:32:03,533 DEBUG
[org.jboss.deployment.MainDeployer] Starting deployment
(init step) of package at: file:/C:/jboss-
3.0.0/server/tapestry/deploy/mckoi-service.xml
2002-06-17 11:32:03,613 DEBUG
[org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with
url file:/C:/jboss-
3.0.0/server/tapestry/tmp/deploy/server/tapestry/deploy/mckoi-
service.xml/49.mckoi-service.xml
2002-06-17 11:32:03,613 DEBUG
[org.jboss.mx.loading.UnifiedLoaderRepository]
UnifiedLoaderRepository adding
org.jboss.mx.loading.UnifiedClassLoader@aae86e{
url=file:/C:/jboss-
3.0.0/server/tapestry/tmp/deploy/server/tapestry/deploy/mckoi-
service.xml/49.mckoi-service.xml }
2002-06-17 11:32:03,613 TRACE
[org.jboss.system.ServiceController] Scanning for newly
supplied classes for waiting mbeans
2002-06-17 11:32:03,613 DEBUG
[org.jboss.deployment.MainDeployer] using deployer
org.jboss.deployment.SARDeployer@c931fc
2002-06-17 11:32:03,683 DEBUG
[org.jboss.deployment.SARDeployer] about to copy 0 local
directories
2002-06-17 11:32:03,683 DEBUG
[org.jboss.deployment.MainDeployer] found 0 subpackages of
file:/C:/jboss-3.0.0/server/tapestry/deploy/mckoi-service.xml
2002-06-17 11:32:03,683 DEBUG
[org.jboss.deployment.MainDeployer] Watching new file:
file:/C:/jboss-3.0.0/server/tapestry/deploy/mckoi-service.xml
2002-06-17 11:32:03,683 DEBUG
[org.jboss.deployment.MainDeployer] create step for
deployment file:/C:/jboss-3.0.0/server/tapestry/deploy/mckoi-
service.xml
2002-06-17 11:32:03,683 DEBUG
[org.jboss.deployment.SARDeployer] Deploying SAR, create
step: url file:/C:/jboss-3.0.0/server/tapestry/deploy/mckoi-
service.xml
2002-06-17 11:32:03,693 DEBUG
[org.jboss.deployment.SARDeployer] Registering service
UCL=jmx.loading:UCL=11200622
2002-06-17 11:32:03,693 DEBUG
[org.jboss.mx.loading.UnifiedLoaderRepository]
UnifiedLoaderRepository skipping duplicate
org.jboss.mx.loading.UnifiedClassLoader@aae86e{
url=file:/C:/jboss-
3.0.0/server/tapestry/tmp/deploy/server/tapestry/deploy/mckoi-
service.xml/49.mckoi-service.xml }
2002-06-17 11:32:03,703 DEBUG
[org.jboss.system.ServiceCreator] About to create bean:
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource
2002-06-17 11:32:03,703 DEBUG
[org.jboss.system.ServiceCreator] code:
org.jboss.resource.connectionmanager.LocalTxConnectionMa
nager
2002-06-17 11:32:04,044 DEBUG
[org.jboss.system.ServiceCreator] Created bean:
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource
2002-06-17 11:32:04,044 DEBUG
[org.jboss.system.ServiceCreator] About to create bean:
jboss:service=McKoiDB
2002-06-17 11:32:04,044 DEBUG
[org.jboss.system.ServiceCreator] code:
net.sf.tapestry.contrib.mckoi.McKoiDB
2002-06-17 11:32:04,124 DEBUG
[org.jboss.system.ServiceCreator] Created bean:
jboss:service=McKoiDB
2002-06-17 11:32:04,304 DEBUG
[org.jboss.system.ServiceConfigurator] RootPath set
to ../server/tapestry/db in jboss:service=McKoiDB
2002-06-17 11:32:04,424 DEBUG
[org.jboss.system.ServiceConfigurator] ConfigPath set
to ../server/tapestry/db/vlib.conf in jboss:service=McKoiDB
2002-06-17 11:32:04,424 DEBUG
[org.jboss.system.ServiceController] recording that
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource
depends on jboss:service=McKoiDB
2002-06-17 11:32:04,424 DEBUG
[org.jboss.system.ServiceConfigurator] considering
<anonymous> with object name jboss:service=McKoiDB
2002-06-17 11:32:04,424 DEBUG
[org.jboss.system.ServiceCreator] About to create bean:
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
2002-06-17 11:32:04,424 DEBUG
[org.jboss.system.ServiceCreator] code:
org.jboss.resource.connectionmanager.RARDeployment
2002-06-17 11:32:04,695 DEBUG
[org.jboss.system.ServiceCreator] Created bean:
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
2002-06-17 11:32:04,825 DEBUG
[org.jboss.system.ServiceConfigurator] JndiName set to
McKoiDB in
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
2002-06-17 11:32:04,835 DEBUG
[org.jboss.system.ServiceConfigurator]
ManagedConnectionFactoryProperties set to <properties>
<config-property name="ConnectionURL"
type="java.lang.String">jdbc:mckoi://localhost/</config-
property>
<config-property name="DriverClass"
type="java.lang.String">com.mckoi.JDBCDriver</config-
property>
<config-property name="UserName"
type="java.lang.String">admin</config-property>
<config-property name="Password"
type="java.lang.String" />
</properties> in
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
2002-06-17 11:32:04,835 DEBUG
[org.jboss.system.ServiceController] recording that
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
depends on jboss.jca:service=RARDeployment,name=JBoss
LocalTransaction JDBC Wrapper
2002-06-17 11:32:04,835 DEBUG
[org.jboss.system.ServiceConfigurator] considering
OldRarDeployment with object name
jboss.jca:service=RARDeployment,name=JBoss
LocalTransaction JDBC Wrapper
2002-06-17 11:32:04,835 DEBUG
[org.jboss.system.ServiceController] recording that
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
depends on jboss:service=McKoiDB
2002-06-17 11:32:04,835 DEBUG
[org.jboss.system.ServiceConfigurator] considering
<anonymous> with object name jboss:service=McKoiDB
2002-06-17 11:32:04,835 DEBUG
[org.jboss.system.ServiceController] recording that
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource
depends on
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
2002-06-17 11:32:04,835 DEBUG
[org.jboss.system.ServiceConfigurator] considering
ManagedConnectionFactoryName with object name
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
2002-06-17 11:32:04,835 DEBUG
[org.jboss.system.ServiceCreator] About to create bean:
jboss.jca:service=LocalTxPool,name=McKoiDB
2002-06-17 11:32:04,835 DEBUG
[org.jboss.system.ServiceCreator] code:
org.jboss.resource.connectionmanager.JBossManagedConne
ctionPool
2002-06-17 11:32:05,005 DEBUG
[org.jboss.system.ServiceCreator] Created bean:
jboss.jca:service=LocalTxPool,name=McKoiDB
2002-06-17 11:32:05,025 DEBUG
[org.jboss.system.ServiceConfigurator] MinSize set to 0 in
jboss.jca:service=LocalTxPool,name=McKoiDB
2002-06-17 11:32:05,035 DEBUG
[org.jboss.system.ServiceConfigurator] MaxSize set to 50 in
jboss.jca:service=LocalTxPool,name=McKoiDB
2002-06-17 11:32:05,035 DEBUG
[org.jboss.system.ServiceConfigurator] BlockingTimeoutMillis
set to 5000 in jboss.jca:service=LocalTxPool,name=McKoiDB
2002-06-17 11:32:05,045 DEBUG
[org.jboss.system.ServiceConfigurator] IdleTimeoutMinutes
set to 15 in jboss.jca:service=LocalTxPool,name=McKoiDB
2002-06-17 11:32:05,185 DEBUG
[org.jboss.system.ServiceConfigurator] Criteria set to
ByContainer in
jboss.jca:service=LocalTxPool,name=McKoiDB
2002-06-17 11:32:05,185 DEBUG
[org.jboss.system.ServiceController] recording that
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource
depends on jboss.jca:service=LocalTxPool,name=McKoiDB
2002-06-17 11:32:05,195 DEBUG
[org.jboss.system.ServiceConfigurator] considering
ManagedConnectionPool with object name
jboss.jca:service=LocalTxPool,name=McKoiDB
2002-06-17 11:32:05,195 DEBUG
[org.jboss.system.ServiceController] recording that
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource
depends on jboss.jca:service=CachedConnectionManager
2002-06-17 11:32:05,195 DEBUG
[org.jboss.system.ServiceConfigurator] considering
CachedConnectionManager with object name
jboss.jca:service=CachedConnectionManager
2002-06-17 11:32:05,195 DEBUG
[org.jboss.system.ServiceController] recording that
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource
depends on jboss.security:name=JaasSecurityManager
2002-06-17 11:32:05,195 DEBUG
[org.jboss.system.ServiceConfigurator] considering
JaasSecurityManagerService with object name
jboss.security:name=JaasSecurityManager
2002-06-17 11:32:05,326 DEBUG
[org.jboss.system.ServiceConfigurator] TransactionManager
set to java:/TransactionManager in
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource
2002-06-17 11:32:05,326 DEBUG
[org.jboss.system.ServiceController] recording that
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource
depends on jboss.jca:service=RARDeployer
2002-06-17 11:32:05,326 DEBUG
[org.jboss.system.ServiceConfigurator] considering
<anonymous> with object name
jboss.jca:service=RARDeployer
2002-06-17 11:32:05,326 DEBUG
[org.jboss.system.ServiceController] waiting in create
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource
waiting on jboss:service=McKoiDB
2002-06-17 11:32:05,326 DEBUG
[org.jboss.system.ServiceController] waiting in create
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource
waiting on
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
2002-06-17 11:32:05,326 WARN
[org.jboss.system.ServiceController]
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
does not implement any Service methods
2002-06-17 11:32:05,336 DEBUG
[org.jboss.system.ServiceController] waiting in create
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
waiting on jboss.jca:service=RARDeployment,name=JBoss
LocalTransaction JDBC Wrapper
2002-06-17 11:32:05,336 WARN
[org.jboss.system.ServiceController]
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
does not implement any Service methods
2002-06-17 11:32:05,336 DEBUG
[org.jboss.system.ServiceController] waiting in create
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
waiting on jboss.jca:service=RARDeployment,name=JBoss
LocalTransaction JDBC Wrapper
2002-06-17 11:32:05,336 INFO
[org.jboss.resource.connectionmanager.JBossManagedConne
ctionPool] Creating
2002-06-17 11:32:05,346 INFO
[org.jboss.resource.connectionmanager.JBossManagedConne
ctionPool] Created
2002-06-17 11:32:05,346 DEBUG
[org.jboss.system.ServiceController] waiting in create
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource
waiting on
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
2002-06-17 11:32:05,346 DEBUG
[org.jboss.deployment.MainDeployer] Done with create step
of deploying mckoi-service.xml
2002-06-17 11:32:05,346 DEBUG
[org.jboss.deployment.MainDeployer] start step for
deployment file:/C:/jboss-3.0.0/server/tapestry/deploy/mckoi-
service.xml
2002-06-17 11:32:05,346 DEBUG
[org.jboss.deployment.SARDeployer] Deploying SAR, start
step: url file:/C:/jboss-3.0.0/server/tapestry/deploy/mckoi-
service.xml
2002-06-17 11:32:05,346 DEBUG
[org.jboss.system.ServiceController] waiting in start
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource on
jboss:service=McKoiDB
2002-06-17 11:32:08,761 INFO [STDOUT] TCP JDBC Server
(multi_threaded) on port: 9157
2002-06-17 11:32:08,761 INFO [STDOUT] .
2002-06-17 11:32:08,761 INFO [STDOUT] Boot time:
3225ms.
2002-06-17 11:32:08,761 DEBUG
[org.jboss.system.ServiceController] waiting in start
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource on
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
2002-06-17 11:32:08,771 DEBUG
[org.jboss.system.ServiceController] waiting in start
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource on
jboss.jca:service=RARDeployment,name=JBoss
LocalTransaction JDBC Wrapper
2002-06-17 11:32:08,771 DEBUG
[org.jboss.system.ServiceController] waiting in start
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource on
jboss.jca:service=RARDeployment,name=JBoss
LocalTransaction JDBC Wrapper
2002-06-17 11:32:08,771 INFO
[org.jboss.resource.connectionmanager.JBossManagedConne
ctionPool] Starting
2002-06-17 11:32:08,781 INFO
[org.jboss.resource.connectionmanager.JBossManagedConne
ctionPool] Started
2002-06-17 11:32:08,781 DEBUG
[org.jboss.system.ServiceController] waiting in start
jboss.jca:service=LocalTxCM,name=McKoiDBDataSource on
jboss.jca:service=LocalTxDS,name=McKoiDBDataSource
2002-06-17 11:32:08,781 DEBUG
[org.jboss.deployment.MainDeployer] Final (start) deployment
step successfully completed on package: mckoi-service.xml
2002-06-17 11:32:08,781 INFO
[org.jboss.deployment.MainDeployer] Successfully
completed deployment of package: file:/C:/jboss-
3.0.0/server/tapestry/deploy/mckoi-service.xml
----------------------------------------------------------------------
Comment By: Howard Lewis Ship (hship)
Date: 2002-06-17 10:55
Message:
Logged In: YES
user_id=26816
The MBean is for McKoi 0.92 and the licensing is
problematic ... I have it as LGPL but it should be GPL (since
it directly references code in McKoi, which is GPL). There
are discussions going on inside the McKoi community to
move this code into McKoi proper, which will bypass the
licensing problem.
----------------------------------------------------------------------
Comment By: David Jencks (d_jencks)
Date: 2002-06-17 10:45
Message:
Logged In: YES
user_id=60525
If you contribute your McKoi database mbean and attach the
mckoi-service.xml file I will look into this. I'd like to
provide Mckoi integration as well as hsqldb since I discover
hsqldb has ___NO___ transaction isolation.
Meanwhile I suggest you get Branch_3_0 from cvs and see if
you can learn anything from
MainDeployer.listIncompletelyDeployed and
ServiceController.listIncompletelyDeployed.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=570030&group_id=22866
-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
