On Sat, Jun 23, 2001 at 01:04:08PM +0100, Julian Gosnell wrote:
> I've just put a new JBoss-2.2.2_Jetty-3.1.RC5 (no.5) into CVS. you can get it by
>going to :
>
>
>http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/binaries/JBoss-2.2.2_Jetty-3.1.RC5-5.tgz
>
> click on Revision 1.1 and it should start to download (Netscape) failing this try
>e.g. "Save as" on the link.
Thank you, I will try it. If you don't hear from me again you'll know
it worked <g>
As a matter of interest, does this mean there is no real difference
between Unix and Windows distributions?
> This should definitely fix the 2nd Exception that you are getting, which is my fault
>:-), however the first one is a mystery. Seeing as Jetty is not
> mentioned on it's stacktrace I'm tempted to say that it is nothing to do with me.
I believe you are right.
> I can only assume that JBossMQ is telling you the truth and that it's configuration
>IS invalid. When JBoss_Jetty is built it simply copies JBoss into one
> subdir, Jetty into another, installs a jar or two and sets up the Jetty config. It
>doesn't mess around with JBossMQ or anything else.
>
> Try run.bat without the 'jetty'. this should run JBoss without Jetty. You won't be
>able to deploy your WebApps, but you should be able to see if you still
> get the JBossMQ Exception. I would be interested to know.
Just tried it and I get the same problem with the default config.
> Do you get the JBossMQ error before or after deploying ?
It happens just before deployment. Continuing from the end of the
exception that I sent earlier;
[JBossMQ] at org.jboss.Main.main(Main.java:117)
[JBossMQ] Started
[DefaultJMSProvider] Starting
[DefaultJMSProvider] JMS provider Adapter DefaultJMSProvider bound to
java:/DefaultJMSProvider
[DefaultJMSProvider] Started
[StdJMSPool] Starting
[StdJMSPool] JMS provider Adapter StdJMSPool bound to java:/StdJMSPool
[StdJMSPool] Started
[J2EE Deployer Default] Starting
[J2EE Deployer Default] Cleaning up deployment directory
[J2EE Deployer Default] Started
[Auto deploy] Starting
[Auto deploy] Watching D:\java\JBoss\JBoss-2.2.2_Jetty-3.1.RC5\jboss\deploy
[Auto deploy] Auto deploy of
file:/D:/java/JBoss/JBoss-2.2.2_Jetty-3.1.RC5/jboss/deploy/interest.jar
[J2EE Deployer Default] Deploy J2EE application:
file:/D:/java/JBoss/JBoss-2.2.2_Jetty-3.1.RC5/jboss/deploy/interest.jar
[J2EE Deployer Default] Create application interest.jar
[J2EE Deployer Default] install module interest.jar
[Container factory]
Deploying:file:/D:/java/JBoss/JBoss-2.2.2_Jetty-3.1.RC5/jboss/tmp/deploy/Default/interest.jar
[Verifier] Verifying
file:/D:/java/JBoss/JBoss-2.2.2_Jetty-3.1.RC5/jboss/tmp/deploy/Default/interest.jar/ejb1001.jar
[Verifier] Interest: Verified.
[Container factory] Deploying Interest
...etc...
> Are copying your ears into the deploy dir before or after startup, or using the JMX
>deployer ?
The jars are in the deploy dir before startup.
I also get the exception if I do not have any jars in the deploy
directory.
Cheers
Bent D
--
Bent Dalager - [EMAIL PROTECTED] - http://www.pvv.org/~bcd
powered by emacs
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
