login-conf.xml is not a deployable package. There needs to be exactly one
of them in server/[config]/conf.
I think someone changed the incomplete deployment warnings to only occur
once, so even though the login-conf.xml is still not deployed after you
redeploy the oracle-xa-service.xml you don't get notified of the actual
state of the server. I think your experience is a good illustration of why
always reporting ALL the deployment problems is the clearest and most
satisfactory solution.
INIT_WAITING_DEPLOYER means there has been an attempt to deploy the
package, but currently there are no deployers that know what to do with it.
If a deployer that recognizes that package type gets deployed, your
package will be deployed.
thanks
david jencks
On 2002.09.03 12:57:01 -0400 Bruce Snyder wrote:
> I'm using JBoss 3.01 on Linux. I've configured and deployed the
> oracle-xa-service.xml, login-conf.xml and the jboss-xa.rar was
> already deployed. Upon starting up JBoss, I'm receiving a state of
> INIT_WAITING_DEPLOYER. I can only find a reference to this in the source
> and there are no notes about its meaning. Can someone tell me what it
> means? Here is the full output of the error:
>
> -----------------------------------------------------------
> ...
> 14:35:24,221 INFO [MainDeployer] Starting deployment of package:
> file:/opt/jboss-3.0.1/server/default/deploy/login-conf.xml
> 14:35:24,223 INFO [MainDeployer] deployment waiting for deployer:
> file:/opt/jboss-3.0.1/server/default/deploy/login-conf.xml
> 14:35:24,223 INFO [MainDeployer] Deployment of package:
> file:/opt/jboss-3.0.1/server/default/deploy/login-conf.xml is waiting for
> an appropriate deployer.
> 14:35:24,226 ERROR [URLDeploymentScanner] MBeanException: Exception in
> MBean operation 'checkIncompleteDeployments()'
> Cause: Incomplete Deployment listing:
> Packages waiting for a deployer:
> [org.jboss.deployment.DeploymentInfo@d5c1b5f2 {
> url=file:/opt/jboss-3.0.1/server/default/deploy/login-conf.xml }
> deployer: null
> status: null
> state: INIT_WAITING_DEPLOYER
> watch: file:/opt/jboss-3.0.1/server/default/deploy/login-conf.xml
> lastDeployed: 1030480524223
> lastModified: 1030480524000
> mbeans:
> ]Incompletely deployed packages:
> [org.jboss.deployment.DeploymentInfo@d5c1b5f2 {
> url=file:/opt/jboss-3.0.1/server/default/deploy/login-conf.xml }
> deployer: null
> status: null
> state: INIT_WAITING_DEPLOYER
> watch: file:/opt/jboss-3.0.1/server/default/deploy/login-conf.xml
> lastDeployed: 1030480524223
> lastModified: 1030480524000
> mbeans:
> ]MBeans waiting for classes:
> <none>
> MBeans waiting for other MBeans:
> <none>
> ...
> -----------------------------------------------------------
>
>
> Upon changing a value in the oracle-xa-service.xml the service is
> redeployed and it appears to be OK. Here is the output that appears from
> the redeployment:
>
> -----------------------------------------------------------
> 14:39:29,825 INFO [MainDeployer] Undeploying
> file:/opt/jboss-3.0.1/server/default/deploy/oracle-xa-service.xml
> 14:39:29,826 INFO [XATxConnectionManager] Stopping
> 14:39:29,826 INFO [XATxConnectionManager] shutting down pool:
> org.jboss.resource.connectionmanager.XATxConnectionManager@71680f
> 14:39:29,827 INFO [XATxConnectionManager] Stopped
> 14:39:29,827 INFO [JBossManagedConnectionPool] Stopping
> 14:39:29,827 INFO [JBossManagedConnectionPool] Stopped
> 14:39:29,828 INFO [XATxConnectionManager] Destroying
> 14:39:29,829 INFO [JCAManagedConnectionFactory]
> JCAManagedConnectionFactory.preDeregister(): JCAManagedConnectionFactory
> 14:39:29,830 INFO [JCAConnectionFactory]
> JCAConnectionFactory.preDeregister(): JCAConnectionFactory
> 14:39:29,830 INFO [XATxConnectionManager] Destroyed
> 14:39:29,831 INFO [JBossManagedConnectionPool] Destroying
> 14:39:29,831 INFO [JBossManagedConnectionPool] Destroyed
> 14:39:29,833 INFO [MainDeployer] Cleaned Deployment
> file:/opt/jboss-3.0.1/server/default/deploy/oracle-xa-service.xml
> 14:39:29,833 INFO [MainDeployer] Undeployed
> file:/opt/jboss-3.0.1/server/default/deploy/oracle-xa-service.xml
> 14:39:29,834 INFO [MainDeployer] Starting deployment of package:
> file:/opt/jboss-3.0.1/server/default/deploy/oracle-xa-service.xml
> 14:39:29,869 WARN [ServiceController]
> jboss.jca:service=XATxDS,name=XAOracleDS does not implement any Service
> methods
> 14:39:29,871 INFO [JBossManagedConnectionPool] Creating
> 14:39:29,872 INFO [JBossManagedConnectionPool] Created
> 14:39:29,872 INFO [XATxConnectionManager] Creating
> 14:39:29,879 INFO [XATxConnectionManager] Created
> 14:39:29,880 INFO [JBossManagedConnectionPool] Starting
> 14:39:29,880 INFO [JBossManagedConnectionPool] Started
> 14:39:29,889 INFO [XATxConnectionManager] Starting
> 14:39:29,896 INFO [XAOracleDS] Bound connection factory for resource
> adapter 'Minerva JDBC XATransaction ResourceAdapter' to JNDI name
> 'java:/XAOracleDS'
> 14:39:29,896 INFO [XATxConnectionManager] Started
> 14:39:29,896 INFO [MainDeployer] Deployed package:
> file:/opt/jboss-3.0.1/server/default/deploy/oracle-xa-service.xml
> -----------------------------------------------------------
>
> What is going on here? Is this service waiting for something? Can someone
> tell me if this XA JDBC service is properly deployed and ready to use?
>
> Bruce
> --
> perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user