I've been seeing something like this too, could you send it to me also?
I think there may be a problem with the URLClassloaders getting stuck if
they have a startup problem and then you can never get rid of them. Will
try to look soon.
Thanks
david jencks
On 2001.09.19 17:38:53 -0400 Julian Gosnell wrote:
> David Maplesden wrote:
>
> > Hi Julian,
> >
> > Most of your problems are coming from the fact that service deployment
> has
> > only really been half done, there are several issues directly relating
> to
> > your comments below that need to be sorted out.
> >
> > Briefly then...
> >
> > > I am working on packaging up the Jetty service into an archive.
> > >
> > > I have some questions...
> > >
> > > 1. Should I call it a SAR or a JSR ?
> >
> > Whichever you want, I think I am begining to prefer .sar
> >
> > >
> > > 2. should I deploy it to ./deploy or ./deploy/lib ?
> > >
> >
> > Probably in ./deploy/lib as this way you are guaranteed that it will be
> > deployed before any EAR's in ./deploy. This is one of the outstanding
> > issues with deployment at the moment, we have no way of specifying
> > dependencies between sar's and ear's and rar's.
> >
> > > 3. Can I include jars in it (I tried top level dir and META-INF/lib -
> > > no joy) - how ?
> > >
> >
> > You can't currently include jars, you should be able to in my opinion,
> but
> > currently you can't.
> >
> > > 4. Should Jetty's configuration be done in the archive, nicely
> > > packaged, but awkward to edit, or in ./conf/default, easy to edit but
> > > ... - or both ?
> > >
> >
> > Whichever you think is best. I personally think there should be room
> for a
> > directory structure in a sar that gets expanded when it is deployed.
> This
> > way you can include it in your sar and then it gets expanded to where
> > someone can easily edit it. There would be issues with redeployment
> but
> > they shouldn't be hard to resolve.
> >
> > > 5. It only seems to deploy some of the time - other
> > > times I get :
> > >
> > > java.net.MalformedURLException: no protocol:
> > > META-INF/jboss-service.xml
> > > at java.net.URL.<init>(URL.java:473)
> > > at java.net.URL.<init>(URL.java:376)
> > > at java.net.URL.<init>(URL.java:330)
> > > at org.jboss.deployment.ServiceDeployer.getDocument(Unknown Source)
> > > at org.jboss.deployment.ServiceDeployer.deploy(Unknown Source)
> > > at java.lang.reflect.Method.invoke(Native Method)
> > > at
> > > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.
> > > java:1628)
> > >
> > > at
> > > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.
> > > java:1523)
> > >
> > > at org.jboss.deployment.AutoDeployer.deploy(Unknown Source)
> > > at org.jboss.deployment.AutoDeployer.run(Unknown Source)
> > > at java.lang.Thread.run(Thread.java:484)
> > > [AutoDeployer] Deployment
> > > failed:file:/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0
> > > alpha/deploy/lib/jetty.sar
> > >
> > > org.jboss.deployment.DeploymentException: No valid service.xml file
> > > foundno protocol: META-INF/jboss-service.xml
> > > at org.jboss.deployment.ServiceDeployer.deploy(Unknown Source)
> > > at java.lang.reflect.Method.invoke(Native Method)
> > > at
> > > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.
> > > java:1628)
> > >
> > > at
> > > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.
> > > java:1523)
> > >
> > > at org.jboss.deployment.AutoDeployer.deploy(Unknown Source)
> > > at org.jboss.deployment.AutoDeployer.run(Unknown Source)
> > > at java.lang.Thread.run(Thread.java:484)
> > >
> >
> > This final error should only occur if there is no jboss-service.xml
> file in
> > the sar's META-INF directory. Let us know if it occurs otherwise.
>
> OTHERWISE !
>
> If I take the same SAR file, which definitely HAS a jboss-service.xml
> file in
> it, it will sometimes deploy perfectly, othertimes, I get the above
> exception.
>
> Once I have got the exception out of a running JBoss, I have to restart
> it,
> since the file will never deploy successfully again.
>
> I can mail you the jetty.sar if you like.
>
> Jules
>
>
> >
> >
> > > And yet if I restart with the same service deployed - no
> > > problemo. Once the exception has been thrown, that seems to be
> > > it. Subsequent deployments all fail in the same manner.
> > >
> > >
> > > Any clues/pointers would be much appreciated,
> > >
> > >
> > >
> > > Jules
> > >
> >
> > Cheers
> >
> > David
> >
> > >
> > > _________________________________________________________
> > > Do You Yahoo!?
> > > Get your free @yahoo.com address at http://mail.yahoo.com
> > >
> > >
> > > _______________________________________________
> > > Jboss-development mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
