[JBoss-user] Exceptions starting and stopping JBoss-2.2.2_Jetty-3.1.RC5

2001-06-23 Thread bcd

I have installed JBoss-2.2.2_Jetty-3.1.RC5 on a Win98 box. I run it
from the command line using JDK 1.3.0-C (the one that came with
JBuilder4 Foundation). I use the following command;
run.bat jetty

jBoss starts up and it appears to run my two tutorial applications
(the Interest tutorial and the CDCollection tutorial). I can add CDs,
take it down, restart it and the CDs are still there (although the
CDCollection stops adding CDs after CD id 151 because 152 is a
duplicate and it doesn't handle this very gracefully).

However, I get one exception from jBoss as it starts up and another as
it comes back down again. I stop it using Ctrl-C in the DOS window I
started it from. On the assumption that exceptions are a bad thing,
here they are;


On startup (I haven't changed any config files):
[JBossMQ] Starting
[JBossMQ] Cannot start the JMS server ! Invalid configuration.
[JBossMQ] javax.jms.JMSException: Invalid configuration.
[JBossMQ]   at 
org.jbossmq.server.PersistenceManager.init(PersistenceManager.java:107)
[JBossMQ]   at org.jbossmq.server.StartServer.run(StartServer.java:170)
[JBossMQ]   at org.jbossmq.server.StartServer.start(StartServer.java:70)
[JBossMQ]   at 
org.jbossmq.server.JBossMQService.startService(JBossMQService.java:66)
[JBossMQ]   at 
org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:93)
[JBossMQ]   at java.lang.reflect.Method.invoke(Native Method)
[JBossMQ]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[JBossMQ]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[JBossMQ]   at org.jboss.util.ServiceControl.start(ServiceControl.java:97)
[JBossMQ]   at java.lang.reflect.Method.invoke(Native Method)
[JBossMQ]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[JBossMQ]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[JBossMQ]   at org.jboss.Main.init(Main.java:217)
[JBossMQ]   at org.jboss.Main$1.run(Main.java:121)
[JBossMQ]   at java.security.AccessController.doPrivileged(Native Method)
[JBossMQ]   at org.jboss.Main.main(Main.java:117)
[JBossMQ] Linked Exception:
[JBossMQ] javax.jms.JMSException: Could not open the queue's tranaction log: 
/D:/java/JBoss/JBoss-2.2.2_Jetty-3.1.RC5/jboss/db/jbossmq/transactions.dat
[JBossMQ]   at org.jbossmq.persistence.SpyTxLog.throwJMSException(SpyTxLog.java:95)
[JBossMQ]   at org.jbossmq.persistence.SpyTxLog.init(SpyTxLog.java:35)
[JBossMQ]   at 
org.jbossmq.server.PersistenceManager.init(PersistenceManager.java:104)
[JBossMQ]   at org.jbossmq.server.StartServer.run(StartServer.java:170)
[JBossMQ]   at org.jbossmq.server.StartServer.start(StartServer.java:70)
[JBossMQ]   at 
org.jbossmq.server.JBossMQService.startService(JBossMQService.java:66)
[JBossMQ]   at 
org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:93)
[JBossMQ]   at java.lang.reflect.Method.invoke(Native Method)
[JBossMQ]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[JBossMQ]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[JBossMQ]   at org.jboss.util.ServiceControl.start(ServiceControl.java:97)
[JBossMQ]   at java.lang.reflect.Method.invoke(Native Method)
[JBossMQ]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[JBossMQ]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[JBossMQ]   at org.jboss.Main.init(Main.java:217)
[JBossMQ]   at org.jboss.Main$1.run(Main.java:121)
[JBossMQ]   at java.security.AccessController.doPrivileged(Native Method)
[JBossMQ]   at org.jboss.Main.main(Main.java:117)
[JBossMQ] Started


I don't explicitly use JMS, so don't know if it's working or not.


When I shut down I get the following;

[Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/,ServletHandlerContext=0
[Jetty] Destroyed ForwardHandler in null
[Jetty] Destroyed ResourceHandler in null
[Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/cgi-bin,ServletHandlerContext=0
[Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/javadoc,ServletHandlerContext=0
[Jetty] Destroyed ResourceHandler in null
[Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/demo,ServletHandlerContext=0
[Jetty] Destroyed ForwardHandler in null
[Jetty] Destroyed ResourceHandler in null
[Jetty] Destroyed DumpHandler in null
[Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/jetty,WebApplicationContext=0
[Jetty] Destroyed SecurityHandler in null
[Jetty] Destroyed WebInfProtect
[Jetty] Destroyed ResourceHandler in null
[Jetty] Destroyed NotFoundHandler in null
[Jetty] Destroyed SecurityHandler in null
[Jetty] Destroyed WebInfProtect
[Jetty] Destroy SocketListener on 0.0.0.0:8080
[Jetty] Deregister com.mortbay.Jetty:name=Jetty,Jetty=0,SocketListener=0
[Jetty] 

Re: [JBoss-user] Exceptions starting and stopping JBoss-2.2.2_Jetty-3.1.RC5

2001-06-23 Thread bcd

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



Re: [JBoss-user] Exceptions starting and stopping JBoss-2.2.2_Jetty-3.1.RC5

2001-06-23 Thread David Castro-Diephouse

Hi.  It looks like this is the root cause...  Could it be a file locking 
issue on W98?  Look for the log it mentions - is it there? is it 
readable/writable?  Is there a problem with the slash before the D, or a 
missing directory?

Did you have this working on an earlier version? and if so what version? 
  I would agree with Jules that the stack trace does not indicate a 
Jetty problem.

 [JBossMQ] Linked Exception:
 [JBossMQ] javax.jms.JMSException: Could not open the queue's tranaction log: 
/D:/java/JBoss/JBoss-2.2.2_Jetty-3.1.RC5/jboss/db/jbossmq/transactions.dat
 [JBossMQ] at org.jbossmq.persistence.SpyTxLog.throwJMSException(SpyTxLog.java:95)
 [JBossMQ] at org.jbossmq.persistence.SpyTxLog.init(SpyTxLog.java:35)
 [JBossMQ] at 
org.jbossmq.server.PersistenceManager.init(PersistenceManager.java:104)
 [JBossMQ] at org.jbossmq.server.StartServer.run(StartServer.java:170)
 [JBossMQ] at org.jbossmq.server.StartServer.start(StartServer.java:70)
 [JBossMQ] at 
org.jbossmq.server.JBossMQService.startService(JBossMQService.java:66)
 [JBossMQ] at 
org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:93)
 [JBossMQ] at java.lang.reflect.Method.invoke(Native Method)
 [JBossMQ] at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
 [JBossMQ] at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
 [JBossMQ] at org.jboss.util.ServiceControl.start(ServiceControl.java:97)
 [JBossMQ] at java.lang.reflect.Method.invoke(Native Method)
 [JBossMQ] at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
 [JBossMQ] at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
 [JBossMQ] at org.jboss.Main.init(Main.java:217)
 [JBossMQ] at org.jboss.Main$1.run(Main.java:121)
 [JBossMQ] at java.security.AccessController.doPrivileged(Native Method)
 [JBossMQ] at org.jboss.Main.main(Main.java:117)
 [JBossMQ] Started
 
 
 I don't explicitly use JMS, so don't know if it's working or not.
 
 
 When I shut down I get the following;
 
 [Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/,ServletHandlerContext=0
 [Jetty] Destroyed ForwardHandler in null
 [Jetty] Destroyed ResourceHandler in null
 [Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/cgi-bin,ServletHandlerContext=0
 [Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/javadoc,ServletHandlerContext=0
 [Jetty] Destroyed ResourceHandler in null
 [Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/demo,ServletHandlerContext=0
 [Jetty] Destroyed ForwardHandler in null
 [Jetty] Destroyed ResourceHandler in null
 [Jetty] Destroyed DumpHandler in null
 [Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/jetty,WebApplicationContext=0
 [Jetty] Destroyed SecurityHandler in null
 [Jetty] Destroyed WebInfProtect
 [Jetty] Destroyed ResourceHandler in null
 [Jetty] Destroyed NotFoundHandler in null
 [Jetty] Destroyed SecurityHandler in null
 [Jetty] Destroyed WebInfProtect
 [Jetty] Destroy SocketListener on 0.0.0.0:8080
 [Jetty] Deregister com.mortbay.Jetty:name=Jetty,Jetty=0,SocketListener=0
 [Jetty] Destroying
 [Jetty] Destroying (jetty.mortbay.com)
 [Jetty] java.lang.NullPointerException
 [Jetty]   at com.mortbay.HTTP.HttpServer.destroy(HttpServer.java:229)
 [Jetty]   at org.jboss.jetty.JettyService.destroyService(JettyService.java:317)
 [Jetty]   at 
org.jboss.util.ServiceMBeanSupport.destroy(ServiceMBeanSupport.java:147)
 [Jetty]   at java.lang.reflect.Method.invoke(Native Method)
 [Jetty]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
 [Jetty]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
 [Jetty]   at org.jboss.util.ServiceControl.destroy(ServiceControl.java:172)
 [Jetty]   at java.lang.reflect.Method.invoke(Native Method)
 [Jetty]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
 [Jetty]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
 [Jetty]   at org.jboss.util.Shutdown.shutdownServices(Shutdown.java:96)
 [Jetty]   at org.jboss.util.Shutdown$1.run(Shutdown.java:56)
 [Jetty] Destroyed
 
 
 Is this all normal, or should I panic?
 
 Cheers
   Bent D
 



___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] Exceptions starting and stopping JBoss-2.2.2_Jetty-3.1.RC5

2001-06-23 Thread bcd

On Sat, Jun 23, 2001 at 09:22:39AM -0400, David Castro-Diephouse wrote:
 Hi.  It looks like this is the root cause...  Could it be a file locking 
 issue on W98?  Look for the log it mentions - is it there? is it 
 readable/writable?  Is there a problem with the slash before the D, or a 
 missing directory?

I didn't have a jboss/db/jbossmq directory. When I created one, jBoss
came up ok and it created a small army of files in it.

Presumably this directory should have been in the distribution
archive?

Thanks for the help.

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



RE: [JBoss-user] Exceptions starting and stopping JBoss-2.2.2_Jetty-3.1.RC5

2001-06-23 Thread Torsten Terp

Hi,

I have seen the same error with previous jboss-jetty revisions, and with the lastet
i discovered that simply making a directory called jbossmq in the jboss/db dir solved
the problem. I have just downloaded the 5th rev. and the same thing worked here...
Not all problems have complex solutions :-)

^terp



 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of David
 Castro-Diephouse
 Sent: Saturday, June 23, 2001 3:23 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-user] Exceptions starting and stopping
 JBoss-2.2.2_Jetty-3.1.RC5
 
 
 Hi.  It looks like this is the root cause...  Could it be a file locking 
 issue on W98?  Look for the log it mentions - is it there? is it 
 readable/writable?  Is there a problem with the slash before the D, or a 
 missing directory?
 
 Did you have this working on an earlier version? and if so what version? 
   I would agree with Jules that the stack trace does not indicate a 
 Jetty problem.
 
  [JBossMQ] Linked Exception:
  [JBossMQ] javax.jms.JMSException: Could not open the queue's tranaction log: 
 /D:/java/JBoss/JBoss-2.2.2_Jetty-3.1.RC5/jboss/db/jbossmq/transactions.dat
  [JBossMQ]   at org.jbossmq.persistence.SpyTxLog.throwJMSException(SpyTxLog.java:95)
  [JBossMQ]   at org.jbossmq.persistence.SpyTxLog.init(SpyTxLog.java:35)
  [JBossMQ]   at 
org.jbossmq.server.PersistenceManager.init(PersistenceManager.java:104)
  [JBossMQ]   at org.jbossmq.server.StartServer.run(StartServer.java:170)
  [JBossMQ]   at org.jbossmq.server.StartServer.start(StartServer.java:70)
  [JBossMQ]   at 
org.jbossmq.server.JBossMQService.startService(JBossMQService.java:66)
  [JBossMQ]   at 
org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:93)
  [JBossMQ]   at java.lang.reflect.Method.invoke(Native Method)
  [JBossMQ]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
  [JBossMQ]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
  [JBossMQ]   at org.jboss.util.ServiceControl.start(ServiceControl.java:97)
  [JBossMQ]   at java.lang.reflect.Method.invoke(Native Method)
  [JBossMQ]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
  [JBossMQ]   at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
  [JBossMQ]   at org.jboss.Main.init(Main.java:217)
  [JBossMQ]   at org.jboss.Main$1.run(Main.java:121)
  [JBossMQ]   at java.security.AccessController.doPrivileged(Native Method)
  [JBossMQ]   at org.jboss.Main.main(Main.java:117)
  [JBossMQ] Started
  
  
  I don't explicitly use JMS, so don't know if it's working or not.
  
  
  When I shut down I get the following;
  
  [Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/,ServletHandlerContext=0
  [Jetty] Destroyed ForwardHandler in null
  [Jetty] Destroyed ResourceHandler in null
  [Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/cgi-bin,ServletHandlerContext=0
  [Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/javadoc,ServletHandlerContext=0
  [Jetty] Destroyed ResourceHandler in null
  [Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/demo,ServletHandlerContext=0
  [Jetty] Destroyed ForwardHandler in null
  [Jetty] Destroyed ResourceHandler in null
  [Jetty] Destroyed DumpHandler in null
  [Jetty] Deregister 
com.mortbay.Jetty:name=Jetty,Jetty=0,context=/jetty,WebApplicationContext=0
  [Jetty] Destroyed SecurityHandler in null
  [Jetty] Destroyed WebInfProtect
  [Jetty] Destroyed ResourceHandler in null
  [Jetty] Destroyed NotFoundHandler in null
  [Jetty] Destroyed SecurityHandler in null
  [Jetty] Destroyed WebInfProtect
  [Jetty] Destroy SocketListener on 0.0.0.0:8080
  [Jetty] Deregister com.mortbay.Jetty:name=Jetty,Jetty=0,SocketListener=0
  [Jetty] Destroying
  [Jetty] Destroying (jetty.mortbay.com)
  [Jetty] java.lang.NullPointerException
  [Jetty] at com.mortbay.HTTP.HttpServer.destroy(HttpServer.java:229)
  [Jetty] at org.jboss.jetty.JettyService.destroyService(JettyService.java:317)
  [Jetty] at 
org.jboss.util.ServiceMBeanSupport.destroy(ServiceMBeanSupport.java:147)
  [Jetty] at java.lang.reflect.Method.invoke(Native Method)
  [Jetty] at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
  [Jetty] at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
  [Jetty] at org.jboss.util.ServiceControl.destroy(ServiceControl.java:172)
  [Jetty] at java.lang.reflect.Method.invoke(Native Method)
  [Jetty] at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
  [Jetty] at 
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
  [Jetty] at org.jboss.util.Shutdown.shutdownServices(Shutdown.java:96)
  [Jetty] at org.jboss.util.Shutdown$1.run(Shutdown.java:56)
  [Jetty] Destroyed
  
  
  Is this all normal, or should I panic?
  
  Cheers
  Bent D

Re: [JBoss-user] Exceptions starting and stopping JBoss-2.2.2_Jetty-3.1.RC5

2001-06-23 Thread Julian Gosnell

Thanks Guys,

I'll look into why my build sequence is stripping out this directory.

I'll make sure it doesn't happen in the next release.

Getting there, Slowly :-)


Jules


[EMAIL PROTECTED] wrote:

 On Sat, Jun 23, 2001 at 09:22:39AM -0400, David Castro-Diephouse wrote:
  Hi.  It looks like this is the root cause...  Could it be a file locking
  issue on W98?  Look for the log it mentions - is it there? is it
  readable/writable?  Is there a problem with the slash before the D, or a
  missing directory?

 I didn't have a jboss/db/jbossmq directory. When I created one, jBoss
 came up ok and it created a small army of files in it.

 Presumably this directory should have been in the distribution
 archive?

 Thanks for the help.

 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


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] Exceptions starting and stopping JBoss-2.2.2_Jetty-3.1.RC5

2001-06-23 Thread Scott M Stark

It may not be your build. It could be the tool the user is using
to unarchive. If either drops empty directories this problem
shows up.

- Original Message - 
From: Julian Gosnell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, June 23, 2001 7:16 AM
Subject: Re: [JBoss-user] Exceptions starting and stopping JBoss-2.2.2_Jetty-3.1.RC5


 Thanks Guys,
 
 I'll look into why my build sequence is stripping out this directory.
 
 I'll make sure it doesn't happen in the next release.
 
 Getting there, Slowly :-)
 
 
 Jules
 
 
 [EMAIL PROTECTED] wrote:
 
  On Sat, Jun 23, 2001 at 09:22:39AM -0400, David Castro-Diephouse wrote:
   Hi.  It looks like this is the root cause...  Could it be a file locking
   issue on W98?  Look for the log it mentions - is it there? is it
   readable/writable?  Is there a problem with the slash before the D, or a
   missing directory?
 
  I didn't have a jboss/db/jbossmq directory. When I created one, jBoss
  came up ok and it created a small army of files in it.
 
  Presumably this directory should have been in the distribution
  archive?
 
  Thanks for the help.
 
  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
 
 
 _
 Do You Yahoo!?
 Get your free @yahoo.com address at http://mail.yahoo.com
 
 
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-user
 


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] Exceptions starting and stopping JBoss-2.2.2_Jetty-3.1.RC5

2001-06-23 Thread Julian Gosnell

I'm just downloading the releases to check them.

Thanks Scott,



Jules

Scott M Stark wrote:

 It may not be your build. It could be the tool the user is using
 to unarchive. If either drops empty directories this problem
 shows up.

 - Original Message -
 From: Julian Gosnell [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Saturday, June 23, 2001 7:16 AM
 Subject: Re: [JBoss-user] Exceptions starting and stopping JBoss-2.2.2_Jetty-3.1.RC5

  Thanks Guys,
 
  I'll look into why my build sequence is stripping out this directory.
 
  I'll make sure it doesn't happen in the next release.
 
  Getting there, Slowly :-)
 
 
  Jules
 
 
  [EMAIL PROTECTED] wrote:
 
   On Sat, Jun 23, 2001 at 09:22:39AM -0400, David Castro-Diephouse wrote:
Hi.  It looks like this is the root cause...  Could it be a file locking
issue on W98?  Look for the log it mentions - is it there? is it
readable/writable?  Is there a problem with the slash before the D, or a
missing directory?
  
   I didn't have a jboss/db/jbossmq directory. When I created one, jBoss
   came up ok and it created a small army of files in it.
  
   Presumably this directory should have been in the distribution
   archive?
  
   Thanks for the help.
  
   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
 
 
  _
  Do You Yahoo!?
  Get your free @yahoo.com address at http://mail.yahoo.com
 
 
  ___
  JBoss-user mailing list
  [EMAIL PROTECTED]
  http://lists.sourceforge.net/lists/listinfo/jboss-user
 

 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-user


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] Exceptions starting and stopping JBoss-2.2.2_Jetty-3.1.RC5

2001-06-23 Thread Michael Bilow

The obvious solution would be to make sure that the directly is non-empty
in the distribution archive.  :-)

-- Mike


On 2001-06-23 at 08:36 -0700, Scott M Stark wrote:

 It may not be your build. It could be the tool the user is using
 to unarchive. If either drops empty directories this problem
 shows up.
 
 - Original Message - 
 From: Julian Gosnell [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Saturday, June 23, 2001 7:16 AM
 Subject: Re: [JBoss-user] Exceptions starting and stopping JBoss-2.2.2_Jetty-3.1.RC5
 
 
  Thanks Guys,
  
  I'll look into why my build sequence is stripping out this directory.
  
  I'll make sure it doesn't happen in the next release.
  
  Getting there, Slowly :-)
  
  
  Jules



___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user