Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
UserEJB has a meta-inf directory with a manifest file and ejb-jar.xml which apparently is missing. Since this is picked up by all other versions, I presume this is a bug in JBOSS? Wish I had time to debug JBOSS, since I'd love to learn the internals but unfortunately I don't. Any ideas on how to proceed? I can try playing with the meta-inf directory, it's no different than the other EJB jars that apparently are being picked up. I'll send the files in a private email, perhaps there's some obvious reason V4 is missing what the others can pick up. Thanks, Bob - Original Message - From: "Adrian Brock" <[EMAIL PROTECTED]> To: "rjh" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, September 01, 2003 6:24 AM Subject: Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP > 2003-08-30 15:40:55,032 DEBUG [org.jboss.deployment.XSLSubDeployer] > accepts: packageSuffix: null, urlStr: > file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/testImport27.ear/UserEJB.jar > 2003-08-30 15:40:55,032 DEBUG [org.jboss.deployment.JARDeployer] No > META-INF or > WEB-INF resource found, assuming it is for us > > It is just deploying it as a classes jar b > > On Mon, 2003-09-01 at 07:22, rjh wrote: > > Here's the server.log zipped, this is the 2nd message. > > > > Bob --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
You are too early in the log.
Look for the start phase of the DeploymentInfoURIResolver.
It creates all MBeans first, then starts them.
The exceptions you show are just noise.
Regards,
Adrian
On Sat, 2003-08-30 at 05:29, rjh wrote:
> > The DeploymentInfoURIResolver failed to start for some reason.
> >
> > { objectName: jboss.system:service=DeploymentInfoURIResolver
> > state: CREATED
> > Waiting for me:
> > jboss.net:service=WS4EEDeployer state: CREATED
> > } [EMAIL PROTECTED],
> >
> > check server/all/log/server.log for any debug exception traces.
> >
> > Regards,
> > Adrian
>
> Thanks, there are exceptions but I can't make sense of them, perhaps
> this will help
> diagnose the problem, these are at the top of the file, first mention
> of DeploymentInfoURIResolver,
> and then the exceptions shortly afterwards:
>
>
> 2003-08-29 20:29:49,375 DEBUG [org.jboss.system.ServiceController]
> Creating dependent components for:
> jboss.deployment:type=DeploymentScanner,flavor=URL dependents are: []
>
> 2003-08-29 20:29:49,375 DEBUG
> [org.jboss.management.j2ee.LocalJBossServerDomain] handleNotification:
> javax.management.Notification[source=jboss.system:service=ServiceDeployer,type=org.jboss.deployment.SubDeployer.create,sequenceNumber=17,timeStamp=1062203389375,message=null,userData={
> 'jboss-service.xml' URL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml' localURL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/conf/jboss-service.xml/1.jboss-service.xml'
> watching: 'file:/F:/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml'
> SubDeployer: [EMAIL PROTECTED] }]
>
> 2003-08-29 20:29:49,375 DEBUG [org.jboss.system.ServiceController]
> Creating service jboss.system:service=DeploymentInfoURIResolver
>
> 2003-08-29 20:29:49,375 DEBUG
> [org.jboss.management.j2ee.LocalJBossServerDomain] handleNotification:
> javax.management.Notification[source=jboss.system:service=ServiceController,type=
> org.jboss.system.ServiceMBean.create,sequenceNumber=18,timeStamp=1062203389375,message=null,userData=jboss.system:service=DeploymentInfoURIResolver]
>
> 2003-08-29 20:29:49,375 DEBUG
> [org.jboss.management.j2ee.factory.DefaultManagedObjectFactoryMap]
> Failed to find factory for event:
> javax.management.Notification[source=jboss.system:service=ServiceController,type=
> org.jboss.system.ServiceMBean.create,sequenceNumber=18,timeStamp=1062203389375,message=null,userData=jboss.system:service=DeploymentInfoURIResolver]
>
> 2003-08-29 20:29:49,375 DEBUG [org.jboss.system.ServiceController]
> Creating dependent components for:
> jboss.system:service=DeploymentInfoURIResolver dependents are: []
>
> 2003-08-29 20:29:49,390 DEBUG
> [org.jboss.management.j2ee.LocalJBossServerDomain] handleNotification:
> javax.management.Notification[source=jboss.system:service=ServiceDeployer,type=org.jboss.deployment.SubDeployer.create,sequenceNumber=18,timeStamp=1062203389390,message=null,userData={
> 'jboss-service.xml' URL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml' localURL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/conf/jboss-service.xml/1.jboss-service.xml'
> watching: 'file:/F:/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml'
> SubDeployer: [EMAIL PROTECTED] }]
>
> 2003-08-29 20:29:49,390 DEBUG
> [org.jboss.management.j2ee.LocalJBossServerDomain] handleNotification:
> javax.management.Notification[source=jboss.system:service=ServiceController,type=
> org.jboss.system.ServiceMBean.create,sequenceNumber=19,timeStamp=1062203389390,message=null,userData=jboss.deployment:name=file%3a/F%3a/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml,service=DeploymentInfo]
>
>
>
> ===
>
>
> 2003-08-29 20:29:49,531 DEBUG [org.jboss.management.j2ee.MBean]
> postRegister(), parent:
> jboss.management.local:J2EEServer=Local,j2eeType=ServiceModule,name=jboss-service.xml
> 2003-08-29 20:29:49,546 DEBUG [org.jboss.management.j2ee.MBean] Failed
> to initialze state from: jboss.rmi:type=RMIClassLoader
> java.lang.IllegalArgumentException: Unable to find operation
> getState()
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:133)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544)
> at
> org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:272)
> at $Proxy13.getState(Unknown Source)
> at org.jboss.management.j2ee.MBean.postCreation(MBean.java:156)
> at
> org.jboss.management.j2ee.J2EEManagedObject.postRegister(J2EEManagedObject.java:250)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invokePostRegister(AbstractMBeanInvoker.java:660)
> at
> org.jboss.mx.modelmbean.ModelMBeanInvoker.postRegister(ModelMBeanInvoker.java:342)
> at
> org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:323)
> at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
> at
> sun.reflect.
Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
2003-08-30 15:40:55,032 DEBUG [org.jboss.deployment.XSLSubDeployer] accepts: packageSuffix: null, urlStr: file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/testImport27.ear/UserEJB.jar 2003-08-30 15:40:55,032 DEBUG [org.jboss.deployment.JARDeployer] No META-INF or WEB-INF resource found, assuming it is for us It is just deploying it as a classes jar b On Mon, 2003-09-01 at 07:22, rjh wrote: > Here's the server.log zipped, this is the 2nd message. > > Bob --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
Hi,
Perhaps I should mention precicely what's going on. testImport27.ear is the
ear under discussion that's failing in V4, yet works on all other builds as
is. It contains
a few war's and jars, the TqmProj war references UserEJB.jar. UserEJB.jar
contains a few statlesss session beans, and you can see the error in the
console
log when the TqmProj war tries to access the session beans in UserEJB.jar,
it gets a message that JNDI can't find the local context. The UserEJB.jar
beans
are accessed locally, starting with local/ in it's service locator.
SurveySessionLocalHome surveySessionLocalHome =
(SurveySessionLocalHome)jndiContext.lookup("local/SurveySession");
I also note that while the other EJB file, EntityEJB.jar and the other war
files are mentioned in the
console output, UserEJB is saliently missing. UserEJB is mentioned and
seems to process in the
server.log file, so I don't know why it's missing in the console log. Also,
all of the EJBs in
both EJB jar files (UserEJB and EntityEJB) are referenced locally, it looks
as though
the local interfaces aren't registering with JNDI.
Thanks for any help on resloving this issue.
Bob
- Original Message -
From: "Adrian Brock" <[EMAIL PROTECTED]>
To: "rjh" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, August 31, 2003 6:19 PM
Subject: Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
> So what error do you get now?
> Posting things like "It doesn't work" won't get you many answers.
>
> Also including "vir*s" in an e-mail is automatically filtered into my
> junk folder. Turn off your cleaning response. Spam is bad enough
> without making it worse by responding to it.
>
> Regards,
> Adrian
>
> On Sat, 2003-08-30 at 22:17, rjh wrote:
> > Hi,
> >
> > Still doesn't work after changing JVM memory size to 512, other
problems.
> > Seems the
> > JNDI name still isn't registered and no 'local' JNDI context exists for
> > testImport27.ear
> > local interface EJBs (all have local interfaces).
> >
> > Thanks,
> > Bob
> >
> > P.S. The last jboss email-list send had a virus cleaned by my
newsreader.
> >
> > - Original Message -
> > From: "Adrian Brock" <[EMAIL PROTECTED]>
> > To: "rjh" <[EMAIL PROTECTED]>
> > Cc: <[EMAIL PROTECTED]>
> > Sent: Saturday, August 30, 2003 2:53 PM
> > Subject: Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
> >
> >
> > > You are only using the default 64M heap,
> > > from your original post:
> > >
> > > > JAVA_OPTS: -server -Dprogram.name=run.bat
> > >
> > > Add -Xmx512M or whatever size you want.
> > >
> > > The memory footprint of JBoss4 is a known issue
> > > that should be resolved by DR3
> > >
> > > Regards,
> > > Adrian
> > >
> > > On Sat, 2003-08-30 at 19:45, rjh wrote:
> > > > > On Sat, 2003-08-30 at 18:25, rjh wrote:
> > > > > > Adrain,
> > > > >
> > > > > I am not A drain :-)
> > > >
> > > > Sorry, you're actually quite helpful.
> > > >
> > > > >> [...]
> > > > >
> > > > > I can see jboss's ejbs starting.
> > > >
> > > > Attached are the console and logs when hot dropping
testImport27.ear.
> > > >
> > > > This is from the console, it shows out of memory but only 372MB out
of
> > 1.5GB
> > > > are used and I run very large programs all the time.
> > > >
> > > > Console
> > > > ===
> > > >
> > > > 13:21:44,578 INFO [Engine] StandardHost[localhost]: MAPPING
> > configuration
> > > > error for request URI / jmx-console
> > > > 14:34:20,438 INFO [MainDeployer] Starting deployment of package:
> > > > file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/testImport27.ear
> > > > 14:34:20,563 INFO [EARDeployer] Init J2EE application:
> > > > file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/testImport27.ear
> > > > 14:34:23,813 INFO [MainDeployer] Starting deployment of package:
> > > >
> >
file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar
> > > > 14:34:24,329 INFO [MainDeployer] Deployed package:
> > > >
> >
file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar
> > > > 14:34:24,329 INFO [MainDeployer] Package:
> > > >
> >
file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar
> > > > is already deployed
> > > > 14:34:28,344 ERROR [STDERR] java.lang.OutOfMemoryError
> > > >
> > > > Thanks again,
> > > > Bob
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
I'll try to send the logs one more time. As below, the EJBs aren't registered and JNDI access to them fails saying local context not found, all EJBs are access thru local interfaces. Hopefully the logs will get through, since there is no chance the jboss logs contain a virus, either the programs are mistaken or something caught in en route. I'm first sending the console unzipped, a 2nd post will contain the server.log zipped. Regards, Bob - Original Message - From: "Adrian Brock" <[EMAIL PROTECTED]> To: "rjh" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, August 31, 2003 6:19 PM Subject: Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP > So what error do you get now? > Posting things like "It doesn't work" won't get you many answers. > > Also including "vir*s" in an e-mail is automatically filtered into my > junk folder. Turn off your cleaning response. Spam is bad enough > without making it worse by responding to it. > > Regards, > Adrian > > On Sat, 2003-08-30 at 22:17, rjh wrote: > > Hi, > > > > Still doesn't work after changing JVM memory size to 512, other problems. > > Seems the > > JNDI name still isn't registered and no 'local' JNDI context exists for > > testImport27.ear > > local interface EJBs (all have local interfaces). > > > > Thanks, > > Bob > > > > P.S. The last jboss email-list send had a virus cleaned by my newsreader. > > > > - Original Message - > > From: "Adrian Brock" <[EMAIL PROTECTED]> > > To: "rjh" <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]> > > Sent: Saturday, August 30, 2003 2:53 PM > > Subject: Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP > > > > > > > You are only using the default 64M heap, > > > from your original post: > > > > > > > JAVA_OPTS: -server -Dprogram.name=run.bat > > > > > > Add -Xmx512M or whatever size you want. > > > > > > The memory footprint of JBoss4 is a known issue > > > that should be resolved by DR3 > > > > > > Regards, > > > Adrian > > > > > > On Sat, 2003-08-30 at 19:45, rjh wrote: > > > > > On Sat, 2003-08-30 at 18:25, rjh wrote: > > > > > > Adrain, > > > > > > > > > > I am not A drain :-) > > > > > > > > Sorry, you're actually quite helpful. > > > > > > > > >> [...] > > > > > > > > > > I can see jboss's ejbs starting. > > > > > > > > Attached are the console and logs when hot dropping testImport27.ear. > > > > > > > > This is from the console, it shows out of memory but only 372MB out of > > 1.5GB > > > > are used and I run very large programs all the time. > > > > > > > > Console > > > > === > > > > > > > > 13:21:44,578 INFO [Engine] StandardHost[localhost]: MAPPING > > configuration > > > > error for request URI / jmx-console > > > > 14:34:20,438 INFO [MainDeployer] Starting deployment of package: > > > > file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/testImport27.ear > > > > 14:34:20,563 INFO [EARDeployer] Init J2EE application: > > > > file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/testImport27.ear > > > > 14:34:23,813 INFO [MainDeployer] Starting deployment of package: > > > > > > file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar > > > > 14:34:24,329 INFO [MainDeployer] Deployed package: > > > > > > file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar > > > > 14:34:24,329 INFO [MainDeployer] Package: > > > > > > file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar > > > > is already deployed > > > > 14:34:28,344 ERROR [STDERR] java.lang.OutOfMemoryError > > > > > > > > Thanks again, > > > > Bob F:\jboss\jboss-4.0.0DR2\bin>run -c all === . JBoss Bootstrap Environment . JBOSS_HOME: F:\jboss\jboss-4.0.0DR2\bin\\.. . JAVA: C:\j2sdk1.4.1_02\\bin\java . JAVA_OPTS: -server -Xmx512M -Dprogram.name=run.bat . CLASSPATH: ;C:\j2sdk1.4.1_02\\lib\to
Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
So what error do you get now? Posting things like "It doesn't work" won't get you many answers. Also including "vir*s" in an e-mail is automatically filtered into my junk folder. Turn off your cleaning response. Spam is bad enough without making it worse by responding to it. Regards, Adrian On Sat, 2003-08-30 at 22:17, rjh wrote: > Hi, > > Still doesn't work after changing JVM memory size to 512, other problems. > Seems the > JNDI name still isn't registered and no 'local' JNDI context exists for > testImport27.ear > local interface EJBs (all have local interfaces). > > Thanks, > Bob > > P.S. The last jboss email-list send had a virus cleaned by my newsreader. > > - Original Message - > From: "Adrian Brock" <[EMAIL PROTECTED]> > To: "rjh" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Saturday, August 30, 2003 2:53 PM > Subject: Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP > > > > You are only using the default 64M heap, > > from your original post: > > > > > JAVA_OPTS: -server -Dprogram.name=run.bat > > > > Add -Xmx512M or whatever size you want. > > > > The memory footprint of JBoss4 is a known issue > > that should be resolved by DR3 > > > > Regards, > > Adrian > > > > On Sat, 2003-08-30 at 19:45, rjh wrote: > > > > On Sat, 2003-08-30 at 18:25, rjh wrote: > > > > > Adrain, > > > > > > > > I am not A drain :-) > > > > > > Sorry, you're actually quite helpful. > > > > > > >> [...] > > > > > > > > I can see jboss's ejbs starting. > > > > > > Attached are the console and logs when hot dropping testImport27.ear. > > > > > > This is from the console, it shows out of memory but only 372MB out of > 1.5GB > > > are used and I run very large programs all the time. > > > > > > Console > > > === > > > > > > 13:21:44,578 INFO [Engine] StandardHost[localhost]: MAPPING > configuration > > > error for request URI / jmx-console > > > 14:34:20,438 INFO [MainDeployer] Starting deployment of package: > > > file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/testImport27.ear > > > 14:34:20,563 INFO [EARDeployer] Init J2EE application: > > > file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/testImport27.ear > > > 14:34:23,813 INFO [MainDeployer] Starting deployment of package: > > > > file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar > > > 14:34:24,329 INFO [MainDeployer] Deployed package: > > > > file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar > > > 14:34:24,329 INFO [MainDeployer] Package: > > > > file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar > > > is already deployed > > > 14:34:28,344 ERROR [STDERR] java.lang.OutOfMemoryError > > > > > > Thanks again, > > > Bob --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
You are only using the default 64M heap, from your original post: > JAVA_OPTS: -server -Dprogram.name=run.bat Add -Xmx512M or whatever size you want. The memory footprint of JBoss4 is a known issue that should be resolved by DR3 Regards, Adrian On Sat, 2003-08-30 at 19:45, rjh wrote: > > On Sat, 2003-08-30 at 18:25, rjh wrote: > > > Adrain, > > > > I am not A drain :-) > > Sorry, you're actually quite helpful. > > >> [...] > > > > I can see jboss's ejbs starting. > > Attached are the console and logs when hot dropping testImport27.ear. > > This is from the console, it shows out of memory but only 372MB out of 1.5GB > are used and I run very large programs all the time. > > Console > === > > 13:21:44,578 INFO [Engine] StandardHost[localhost]: MAPPING configuration > error for request URI / jmx-console > 14:34:20,438 INFO [MainDeployer] Starting deployment of package: > file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/testImport27.ear > 14:34:20,563 INFO [EARDeployer] Init J2EE application: > file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/testImport27.ear > 14:34:23,813 INFO [MainDeployer] Starting deployment of package: > file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar > 14:34:24,329 INFO [MainDeployer] Deployed package: > file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar > 14:34:24,329 INFO [MainDeployer] Package: > file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar > is already deployed > 14:34:28,344 ERROR [STDERR] java.lang.OutOfMemoryError > > Thanks again, > Bob --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
> On Sat, 2003-08-30 at 18:25, rjh wrote: > > Adrain, > > I am not A drain :-) Sorry, you're actually quite helpful. >> [...] > > I can see jboss's ejbs starting. Attached are the console and logs when hot dropping testImport27.ear. This is from the console, it shows out of memory but only 372MB out of 1.5GB are used and I run very large programs all the time. Console === 13:21:44,578 INFO [Engine] StandardHost[localhost]: MAPPING configuration error for request URI / jmx-console 14:34:20,438 INFO [MainDeployer] Starting deployment of package: file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/testImport27.ear 14:34:20,563 INFO [EARDeployer] Init J2EE application: file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/testImport27.ear 14:34:23,813 INFO [MainDeployer] Starting deployment of package: file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar 14:34:24,329 INFO [MainDeployer] Deployed package: file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar 14:34:24,329 INFO [MainDeployer] Package: file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/testImport27.ear/66.testImport27.ear-contents/Utilities.jar is already deployed 14:34:28,344 ERROR [STDERR] java.lang.OutOfMemoryError Thanks again, Bob Logs0830.zip Description: Zip compressed data
Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
On Sat, 2003-08-30 at 18:25, rjh wrote:
> Adrain,
>
I am not A drain :-)
> Thanks for the comment, but the reason I'm writing is because my EAR with
> EJB doesn't work on the V4 release although it runs on all other releases
> on Tomcat and Jetty.
>
> I print the JNDI env from the ear and the EJBs aren't listed, which I assume
> is the first part of the problem, I can see when the ear is loaded that the
> EJBs are not registering. Again, the EJBs aren't running in V4 and the
> Ear file fails, this is not a hypothetical look at log files. My goal is to
> allow
> my ear to run, then I can add AOP examples and potentially begin the switch
> from EJB to AOP.
>
I see the EARDeployer has started from your log, but I can find no
mention of your .ear in the log.
I can see jboss's ejbs starting.
Regards,
Adrian
> EJBDeployer state is started, but again to be clear the ystem doesn't work
> and EJBs
> are not being loaded given an EJB ear file that runs under all aother Tomcat
> and Jetty
> versions.
>
> Thanks,
> Bob
>
> - Original Message -
> From: "Adrian Brock" <[EMAIL PROTECTED]>
> To: "rjh" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Saturday, August 30, 2003 2:08 AM
> Subject: Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
>
>
> > It is noise.
> >
> > The URI resolver is after the URL scanner in jboss-service.xml
> > When the scanner finishes it dumps not yet started mbeans.
> > I guess this is because whoever added it, couldn't work out the
> > dependencies.
> >
> > The URI resolver hasn't started yet (because it is listed afterwards.
> > If you look at the console you will see it starting after the
> > "incomplete" message followed by W2EE then the EJB deployer, etc.
> >
> > You can check it on the jmx-console, if you go to the MainDeployer
> > and click on the incompletely deployed mbeans operation.
> > It should show nothing.
> > Also if you look at the EJBDeployer it will be have state "Started"
> >
> > Regards,
> > Adrian
> >
> > On Sat, 2003-08-30 at 06:18, rjh wrote:
> > > Hi,
> > >
> > > I'm still having trouble locating the actual problem, I've attached the
> > > zipped server log.
> > >
> > > Thanks & Best Regards,
> > > Bob
> > >
> > > - Original Message -
> > > From: "Adrian Brock" <[EMAIL PROTECTED]>
> > > To: "rjh" <[EMAIL PROTECTED]>
> > > Cc: <[EMAIL PROTECTED]>
> > > Sent: Saturday, August 30, 2003 12:59 AM
> > > Subject: Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
> > >
> > >
> > > > You are too early in the log.
> > > > Look for the start phase of the DeploymentInfoURIResolver.
> > > > It creates all MBeans first, then starts them.
> > > >
> > > > The exceptions you show are just noise.
> > > >
> > > > Regards,
> > > > Adrian
> > > >
> > > > On Sat, 2003-08-30 at 05:29, rjh wrote:
> > > > > > The DeploymentInfoURIResolver failed to start for some reason.
> > > > > >
> > > > > > { objectName: jboss.system:service=DeploymentInfoURIResolver
> > > > > > state: CREATED
> > > > > > Waiting for me:
> > > > > > jboss.net:service=WS4EEDeployer state: CREATED
> > > > > > } [EMAIL PROTECTED],
> > > > > >
> > > > > > check server/all/log/server.log for any debug exception traces.
> > > > > >
> > > > > > Regards,
> > > > > > Adrian
> > > > >
> > > > > Thanks, there are exceptions but I can't make sense of them, perhaps
> > > > > this will help
> > > > > diagnose the problem, these are at the top of the file, first
> mention
> > > > > of DeploymentInfoURIResolver,
> > > > > and then the exceptions shortly afterwards:
> > > > >
> > > > >
> > > > > 2003-08-29 20:29:49,375 DEBUG [org.jboss.system.ServiceController]
> > > > > Creating dependent components for:
> > > > > jboss.deployment:type=DeploymentScanner,flavor=URL dependents are:
> []
> > > > >
> > > > > 2003-08-29 20:29:49,375 DEBUG
> > > > > [org.jboss.management.j2ee.LocalJBossServerDomain]
> handleNotification:
> > >
Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
Adrain,
Thanks for the comment, but the reason I'm writing is because my EAR with
EJB doesn't work on the V4 release although it runs on all other releases
on Tomcat and Jetty.
I print the JNDI env from the ear and the EJBs aren't listed, which I assume
is the first part of the problem, I can see when the ear is loaded that the
EJBs are not registering. Again, the EJBs aren't running in V4 and the
Ear file fails, this is not a hypothetical look at log files. My goal is to
allow
my ear to run, then I can add AOP examples and potentially begin the switch
from EJB to AOP.
EJBDeployer state is started, but again to be clear the ystem doesn't work
and EJBs
are not being loaded given an EJB ear file that runs under all aother Tomcat
and Jetty
versions.
Thanks,
Bob
- Original Message -
From: "Adrian Brock" <[EMAIL PROTECTED]>
To: "rjh" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, August 30, 2003 2:08 AM
Subject: Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
> It is noise.
>
> The URI resolver is after the URL scanner in jboss-service.xml
> When the scanner finishes it dumps not yet started mbeans.
> I guess this is because whoever added it, couldn't work out the
> dependencies.
>
> The URI resolver hasn't started yet (because it is listed afterwards.
> If you look at the console you will see it starting after the
> "incomplete" message followed by W2EE then the EJB deployer, etc.
>
> You can check it on the jmx-console, if you go to the MainDeployer
> and click on the incompletely deployed mbeans operation.
> It should show nothing.
> Also if you look at the EJBDeployer it will be have state "Started"
>
> Regards,
> Adrian
>
> On Sat, 2003-08-30 at 06:18, rjh wrote:
> > Hi,
> >
> > I'm still having trouble locating the actual problem, I've attached the
> > zipped server log.
> >
> > Thanks & Best Regards,
> > Bob
> >
> > - Original Message -
> > From: "Adrian Brock" <[EMAIL PROTECTED]>
> > To: "rjh" <[EMAIL PROTECTED]>
> > Cc: <[EMAIL PROTECTED]>
> > Sent: Saturday, August 30, 2003 12:59 AM
> > Subject: Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
> >
> >
> > > You are too early in the log.
> > > Look for the start phase of the DeploymentInfoURIResolver.
> > > It creates all MBeans first, then starts them.
> > >
> > > The exceptions you show are just noise.
> > >
> > > Regards,
> > > Adrian
> > >
> > > On Sat, 2003-08-30 at 05:29, rjh wrote:
> > > > > The DeploymentInfoURIResolver failed to start for some reason.
> > > > >
> > > > > { objectName: jboss.system:service=DeploymentInfoURIResolver
> > > > > state: CREATED
> > > > > Waiting for me:
> > > > > jboss.net:service=WS4EEDeployer state: CREATED
> > > > > } [EMAIL PROTECTED],
> > > > >
> > > > > check server/all/log/server.log for any debug exception traces.
> > > > >
> > > > > Regards,
> > > > > Adrian
> > > >
> > > > Thanks, there are exceptions but I can't make sense of them, perhaps
> > > > this will help
> > > > diagnose the problem, these are at the top of the file, first
mention
> > > > of DeploymentInfoURIResolver,
> > > > and then the exceptions shortly afterwards:
> > > >
> > > >
> > > > 2003-08-29 20:29:49,375 DEBUG [org.jboss.system.ServiceController]
> > > > Creating dependent components for:
> > > > jboss.deployment:type=DeploymentScanner,flavor=URL dependents are:
[]
> > > >
> > > > 2003-08-29 20:29:49,375 DEBUG
> > > > [org.jboss.management.j2ee.LocalJBossServerDomain]
handleNotification:
> > > >
> >
javax.management.Notification[source=jboss.system:service=ServiceDeployer,ty
> >
pe=org.jboss.deployment.SubDeployer.create,sequenceNumber=17,timeStamp=10622
> > 03389375,message=null,userData={ 'jboss-service.xml' URL:
> > 'file:/F:/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml'
localURL:
> >
'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/conf/jboss-s
> > ervice.xml/1.jboss-service.xml' watching:
> > 'file:/F:/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml'
> > SubDeployer: [EMAIL PROTECTED] }]
> > > >
> > > > 2003-08-29 20:29:49,375 DEBUG [org.jboss.system.ServiceController]
>
Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
> The
DeploymentInfoURIResolver failed to start for some reason.> > { objectName:
jboss.system:service=DeploymentInfoURIResolver> state: CREATED> Waiting for me:>
jboss.net:service=WS4EEDeployer state: CREATED>
} [EMAIL PROTECTED],> > check server/all/log/server.log for any debug
exception traces.> > Regards,>
Adrian
Thanks, there
are exceptions but I can't make sense of them, perhaps this will
help
diagnose the problem, these are at the top of the file, first mention of
DeploymentInfoURIResolver,
and then the exceptions shortly afterwards:
2003-08-29 20:29:49,375 DEBUG [org.jboss.system.ServiceController]
Creating dependent components for:
jboss.deployment:type=DeploymentScanner,flavor=URL dependents are: []
2003-08-29 20:29:49,375 DEBUG
[org.jboss.management.j2ee.LocalJBossServerDomain] handleNotification:
javax.management.Notification[source=jboss.system:service=ServiceDeployer,type=org.jboss.deployment.SubDeployer.create,sequenceNumber=17,timeStamp=1062203389375,message=null,userData={
'jboss-service.xml' URL:
'file:/F:/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml' localURL:
'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/conf/jboss-service.xml/1.jboss-service.xml'
watching: 'file:/F:/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml'
SubDeployer: [EMAIL PROTECTED] }]
2003-08-29 20:29:49,375 DEBUG [org.jboss.system.ServiceController]
Creating service jboss.system:service=DeploymentInfoURIResolver
2003-08-29 20:29:49,375 DEBUG
[org.jboss.management.j2ee.LocalJBossServerDomain] handleNotification:
javax.management.Notification[source=jboss.system:service=ServiceController,type=
org.jboss.system.ServiceMBean.create,sequenceNumber=18,timeStamp=1062203389375,message=null,userData=jboss.system:service=DeploymentInfoURIResolver]
2003-08-29 20:29:49,375 DEBUG
[org.jboss.management.j2ee.factory.DefaultManagedObjectFactoryMap] Failed to
find factory for event:
javax.management.Notification[source=jboss.system:service=ServiceController,type=
org.jboss.system.ServiceMBean.create,sequenceNumber=18,timeStamp=1062203389375,message=null,userData=jboss.system:service=DeploymentInfoURIResolver]
2003-08-29 20:29:49,375 DEBUG [org.jboss.system.ServiceController]
Creating dependent components for:
jboss.system:service=DeploymentInfoURIResolver dependents are: []
2003-08-29 20:29:49,390 DEBUG
[org.jboss.management.j2ee.LocalJBossServerDomain] handleNotification:
javax.management.Notification[source=jboss.system:service=ServiceDeployer,type=org.jboss.deployment.SubDeployer.create,sequenceNumber=18,timeStamp=1062203389390,message=null,userData={
'jboss-service.xml' URL:
'file:/F:/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml' localURL:
'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/conf/jboss-service.xml/1.jboss-service.xml'
watching: 'file:/F:/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml'
SubDeployer: [EMAIL PROTECTED] }]
2003-08-29 20:29:49,390 DEBUG
[org.jboss.management.j2ee.LocalJBossServerDomain] handleNotification:
javax.management.Notification[source=jboss.system:service=ServiceController,type=
org.jboss.system.ServiceMBean.create,sequenceNumber=19,timeStamp=1062203389390,message=null,userData=jboss.deployment:name=file%3a/F%3a/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml,service=DeploymentInfo]
===
2003-08-29 20:29:49,531 DEBUG
[org.jboss.management.j2ee.MBean] postRegister(), parent:
jboss.management.local:J2EEServer=Local,j2eeType=ServiceModule,name=jboss-service.xml2003-08-29
20:29:49,546 DEBUG [org.jboss.management.j2ee.MBean] Failed to initialze state
from: jboss.rmi:type=RMIClassLoaderjava.lang.IllegalArgumentException:
Unable to find operation getState() at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:133) at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544) at
org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:272) at
$Proxy13.getState(Unknown Source) at
org.jboss.management.j2ee.MBean.postCreation(MBean.java:156) at
org.jboss.management.j2ee.J2EEManagedObject.postRegister(J2EEManagedObject.java:250) at
org.jboss.mx.server.AbstractMBeanInvoker.invokePostRegister(AbstractMBeanInvoker.java:660) at
org.jboss.mx.modelmbean.ModelMBeanInvoker.postRegister(ModelMBeanInvoker.java:342) at
org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:323) at
sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
java.lang.reflect.Method.invoke(Method.java:324) at
org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72) at
org.jboss.mx.server.Invocation.dispatch(Invocation.java:45) at
org.jboss.mx.server.Invocation.invoke(Invocation.java:70) at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155
Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
It is noise.
The URI resolver is after the URL scanner in jboss-service.xml
When the scanner finishes it dumps not yet started mbeans.
I guess this is because whoever added it, couldn't work out the
dependencies.
The URI resolver hasn't started yet (because it is listed afterwards.
If you look at the console you will see it starting after the
"incomplete" message followed by W2EE then the EJB deployer, etc.
You can check it on the jmx-console, if you go to the MainDeployer
and click on the incompletely deployed mbeans operation.
It should show nothing.
Also if you look at the EJBDeployer it will be have state "Started"
Regards,
Adrian
On Sat, 2003-08-30 at 06:18, rjh wrote:
> Hi,
>
> I'm still having trouble locating the actual problem, I've attached the
> zipped server log.
>
> Thanks & Best Regards,
> Bob
>
> - Original Message -
> From: "Adrian Brock" <[EMAIL PROTECTED]>
> To: "rjh" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Saturday, August 30, 2003 12:59 AM
> Subject: Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
>
>
> > You are too early in the log.
> > Look for the start phase of the DeploymentInfoURIResolver.
> > It creates all MBeans first, then starts them.
> >
> > The exceptions you show are just noise.
> >
> > Regards,
> > Adrian
> >
> > On Sat, 2003-08-30 at 05:29, rjh wrote:
> > > > The DeploymentInfoURIResolver failed to start for some reason.
> > > >
> > > > { objectName: jboss.system:service=DeploymentInfoURIResolver
> > > > state: CREATED
> > > > Waiting for me:
> > > > jboss.net:service=WS4EEDeployer state: CREATED
> > > > } [EMAIL PROTECTED],
> > > >
> > > > check server/all/log/server.log for any debug exception traces.
> > > >
> > > > Regards,
> > > > Adrian
> > >
> > > Thanks, there are exceptions but I can't make sense of them, perhaps
> > > this will help
> > > diagnose the problem, these are at the top of the file, first mention
> > > of DeploymentInfoURIResolver,
> > > and then the exceptions shortly afterwards:
> > >
> > >
> > > 2003-08-29 20:29:49,375 DEBUG [org.jboss.system.ServiceController]
> > > Creating dependent components for:
> > > jboss.deployment:type=DeploymentScanner,flavor=URL dependents are: []
> > >
> > > 2003-08-29 20:29:49,375 DEBUG
> > > [org.jboss.management.j2ee.LocalJBossServerDomain] handleNotification:
> > >
> javax.management.Notification[source=jboss.system:service=ServiceDeployer,ty
> pe=org.jboss.deployment.SubDeployer.create,sequenceNumber=17,timeStamp=10622
> 03389375,message=null,userData={ 'jboss-service.xml' URL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml' localURL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/conf/jboss-s
> ervice.xml/1.jboss-service.xml' watching:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/conf/jboss-service.xml'
> SubDeployer: [EMAIL PROTECTED] }]
> > >
> > > 2003-08-29 20:29:49,375 DEBUG [org.jboss.system.ServiceController]
> > > Creating service jboss.system:service=DeploymentInfoURIResolver
> > >
> > > 2003-08-29 20:29:49,375 DEBUG
> > > [org.jboss.management.j2ee.LocalJBossServerDomain] handleNotification:
> > >
> javax.management.Notification[source=jboss.system:service=ServiceController,
> type=
> org.jboss.system.ServiceMBean.create,sequenceNumber=18,timeStamp=10622033893
> 75,message=null,userData=jboss.system:service=DeploymentInfoURIResolver]
> > >
> > > 2003-08-29 20:29:49,375 DEBUG
> > > [org.jboss.management.j2ee.factory.DefaultManagedObjectFactoryMap]
> > > Failed to find factory for event:
> > >
> javax.management.Notification[source=jboss.system:service=ServiceController,
> type=
> org.jboss.system.ServiceMBean.create,sequenceNumber=18,timeStamp=10622033893
> 75,message=null,userData=jboss.system:service=DeploymentInfoURIResolver]
> > >
> > > 2003-08-29 20:29:49,375 DEBUG [org.jboss.system.ServiceController]
> > > Creating dependent components for:
> > > jboss.system:service=DeploymentInfoURIResolver dependents are: []
> > >
> > > 2003-08-29 20:29:49,390 DEBUG
> > > [org.jboss.management.j2ee.LocalJBossServerDomain] handleNotification:
> > >
> javax.management.Notification[source=jboss.system:service=ServiceDeployer,ty
> pe=org.jboss.deployment.SubDeployer.create,sequenceNumber=
Re: [JBoss-user] jboss-4.0.0DR2 Fails to Startup Undex XP
The DeploymentInfoURIResolver failed to start for some reason.
{ objectName: jboss.system:service=DeploymentInfoURIResolver
state: CREATED
Waiting for me:
jboss.net:service=WS4EEDeployer state: CREATED
} [EMAIL PROTECTED],
check server/all/log/server.log for any debug exception traces.
Regards,
Adrian
On Sat, 2003-08-30 at 02:43, rjh wrote:
> After downloading jboss-4.0.0DR2, it won't startup out of the box
> without errors. Specifically,
> EJB fails. I'd hesitate to move to version 4 without the ability to
> run my existing systems.
> I'd like to run AOP examples and prepare to move my EJBs.
>
> Thanks,
> Bob
>
> [{ 'ClusteredHttpSessionEB.jar' URL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/jbossha-httpsession.sar/14.jbo
> lURL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/jbossha-httpsession.sar/14.jbossha-httpsession.sar-contents/C
> .0DR2/server/all/tmp/deploy/server/all/deploy/jbossha-httpsession.sar/14.jbossha-httpsession.sar-contents/ClusteredHttpSessionEB.jar'
> SubD
> boss-4.0.0DR2/server/all/deploy/ejb-management.jar' localURL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/ejb-m
> /jboss-4.0.0DR2/server/all/deploy/ejb-management.jar' SubDeployer:
> null }, { 'jmx-ejb-adaptor.jar' URL:
> 'file:/F:/jboss/jboss-4.0.0DR2/ser
> jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/jmx-ejb-adaptor.jar/64.jmx-ejb-adaptor.jar'
> watching: 'file:/F:/jboss/jboss-4.0.0DR
> Incompletely deployed packages:
> [{ 'ejb-management.jar' URL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/ejb-management.jar'
> localURL: 'file:/F:/jboss/jboss-4.0.0DR2
> .ejb-management.jar' watching:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/deploy/ejb-management.jar'
> SubDeployer: null }, { 'jmx-ejb-adapto
> mx-ejb-adaptor.jar' localURL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/jmx-ejb-adaptor.jar/64.jmx-ejb-adapto
> loy/jmx-ejb-adaptor.jar' SubDeployer: null }]
> MBeans waiting for classes:
>
> MBeans waiting for other MBeans:
>
> { objectName: jboss.system:service=DeploymentInfoURIResolver
> state: CREATED
> Waiting for me:
> jboss.net:service=WS4EEDeployer state: CREATED
> } [EMAIL PROTECTED],
>
> { objectName: jboss.net:service=WS4EEDeployer
> state: CREATED
> I am waiting for:
> jboss.net:service=WebServiceEntityResolver state: RUNNING,
> jboss.system:service=DeploymentInfoURIResolver state: CREATED,
> jboss.net:service=Axis state: RUNNING
> Waiting for me:
> jboss.ejb:service=EJBDeployer state: CREATED
> } [EMAIL PROTECTED],
>
> { objectName: jboss:service=ClusteredHttpSession
> state: CONFIGURED
> I am waiting for:
> jboss.j2ee:service=EJB,jndiName=clustering/HTTPSession state:
> NOTYETINSTALLED
> } [EMAIL PROTECTED],
>
> { objectName: jboss.ejb:service=EJBDeployer
> state: CREATED
> I am waiting for:
> jboss.net:service=WS4EEDeployer state: CREATED,
> jboss:service=WebService state: RUNNING,
> jboss.tm:service=TransactionManagerService state: RUNNING
> Waiting for me:
> jboss:service=FarmMember,partition=DefaultPartition state:
> CREATED,
> jboss.ejb:service=ActivationSpecDeployer state: CREATED
> } [EMAIL PROTECTED],
>
> { objectName: jboss.ejb:service=ActivationSpecDeployer
> state: CREATED
> I am waiting for:
> jboss.ejb:service=EJBEntityResolver state: RUNNING,
> jboss.jca:service=RaURIResolver state: RUNNING,
> jboss.ejb:service=EJBDeployer state: CREATED
> } [EMAIL PROTECTED],
>
> { objectName: jboss:service=FarmMember,partition=DefaultPartition
> state: CREATED
> I am waiting for:
> jboss.web:service=WebServer state: RUNNING,
> jboss.system:service=MainDeployer state: RUNNING,
> jboss:service=DefaultPartition state: RUNNING,
> jboss.ejb:service=EJBDeployer state: CREATED
> } [EMAIL PROTECTED],
>
> Cause: Incomplete Deployment listing:
> Packages waiting for a deployer:
> [{ 'ClusteredHttpSessionEB.jar' URL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/jbossha-httpsession.sar/14.jbo
> lURL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/jbossha-httpsession.sar/14.jbossha-httpsession.sar-contents/C
> .0DR2/server/all/tmp/deploy/server/all/deploy/jbossha-httpsession.sar/14.jbossha-httpsession.sar-contents/ClusteredHttpSessionEB.jar'
> SubD
> boss-4.0.0DR2/server/all/deploy/ejb-management.jar' localURL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/ejb-m
> /jboss-4.0.0DR2/server/all/deploy/ejb-management.jar' SubDeployer:
> null }, { 'jmx-ejb-adaptor.jar' URL:
> 'file:/F:/jboss/jboss-4.0.0DR2/ser
> jboss-4.0.0DR2/server/all/tmp/deploy/server/all/deploy/jmx-ejb-adaptor.jar/64.jmx-ejb-adaptor.jar'
> watching: 'file:/F:/jboss/jboss-4.0.0DR
> Incompletely deployed packages:
> [{ 'ejb-management.jar' URL:
> 'file:/F:/jboss/jboss-4.0.0DR2/server/all
