-
1. Re: jboss catalina problem
adrian.brock Aug 26, 2002 10:55 AM (in response to kristofvcl)Have you tried this with 3.0.1?
Regards,
Adrian -
2. Re: jboss catalina problem
joelvogt Aug 26, 2002 9:53 PM (in response to kristofvcl)I've also had problems with 4.03, 4.04 seemed to be a better build.
-
3. Re: jboss catalina problem
kristofvcl Aug 27, 2002 5:40 AM (in response to kristofvcl)Now i've tried it with the 3.01 and catalina 4.04.
This time my datasource isn't bound.
When I check the startup of the server I only see the DefaultDS name that is bound.
I see the hsql and my datasource service but there names aren't bound.
The service worked on jboss3.0
Is there a change nescessary for binding the name in 3.01? -
4. Re: jboss catalina problem
kristofvcl Aug 27, 2002 6:02 AM (in response to kristofvcl)After checking the startup of JBOSS (3.01 with catalina 4.04)I encountered the following :
Cause: 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=Wdcis
state: CONFIGURED
I Depend On: jboss.jca:service=LocalTxDS,name=Wdcis
jboss.jca:service=LocalTxPool,name=Wdcis
jboss.jca:service=CachedConnectionManager
jboss.security:name=JaasSecurityManager
jboss.jca:service=RARDeployer
This part didn't occur in the jboss3.0.
I found on the net (sourceforge) that there are a bunch of people who are having the same problem.
Does this mean that it is a bug or is there something I missed?
I noticed that the LocalTxCM,name=Wdcis is the same as LocalTxDS,name=Wdcis. Is that a problem? -
5. Re: jboss catalina problem
adrian.brock Aug 27, 2002 6:22 AM (in response to kristofvcl)I think the ObjectName for Jaas changed.
Try
jboss.security:service=JaasSecurityManager
Regards,
Adrian -
6. Re: jboss catalina problem
kristofvcl Aug 27, 2002 8:47 AM (in response to kristofvcl)Thank you.
Both problems are solved now.
Regards
Kristof