Problem deploying webapps in trunk
by Brian Stansberry
Ben Wang and I are intermittently seeing this file permission problem
when starting an "all" server built from AS trunk. I thought it had gone
away after I updated yesterday, but apparently not, as it just happened
again. This is on a Win XP system, in case that's relevant. The app
being deployed here is ROOT.war; I believe Ben's seen it with a zipped
war as well.
2006-11-29 10:30:58,417 DEBUG [org.jboss.web.tomcat.tc6.WebAppLoader]
injectionContainer enabled and processing beginning with Tomcat
WebAppLoader
2006-11-29 10:30:58,448 ERROR
[org.apache.tomcat.util.modeler.BaseModelMBean] Exception invoking
method addChild
java.lang.RuntimeException: org.jboss.xb.binding.JBossXBException:
Failed to parse source: Permission denied
at
org.jboss.web.tomcat.tc6.TomcatInjectionContainer.processMetadata(Tomcat
InjectionContainer.java:264)
at
org.jboss.web.tomcat.tc6.WebAppLoader.start(WebAppLoader.java:104)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4198
)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.ja
va:760)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java
:297)
at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.apache.catalina.core.StandardContext.init(StandardContext.java:5285)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java
:297)
at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.web.tomcat.tc6.deployers.TomcatDeployment.performDeployInterna
l(TomcatDeployment.java:302)
at
org.jboss.web.tomcat.tc6.deployers.TomcatDeployment.performDeploy(Tomcat
Deployment.java:129)
at
org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeploymen
t.java:355)
at
org.jboss.web.deployers.WebModule.startModule(WebModule.java:88)
at org.jboss.web.deployers.WebModule.start(WebModule.java:66)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
a:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:18
4)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(S
tartStopLifecycleAction.java:42)
at
org.jboss.system.microcontainer.ServiceControllerContextAction.install(S
erviceControllerContextAction.java:46)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(Ab
stractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractC
ontrollerContext.java:226)
at
org.jboss.system.microcontainer.ServiceControllerContext.install(Service
ControllerContext.java:198)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractControll
er.java:709)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractC
ontroller.java:429)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstract
Controller.java:538)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstract
Controller.java:472)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractControlle
r.java:320)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractControlle
r.java:190)
at
org.jboss.system.ServiceController.doChange(ServiceController.java:656)
at
org.jboss.system.ServiceController.start(ServiceController.java:431)
at
org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:12
4)
at
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:8
5)
at
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:4
4)
at
org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer
.deploy(AbstractSimpleRealDeployer.java:53)
at
org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy
(AbstractSimpleDeployer.java:52)
at
org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(Deploy
erWrapper.java:145)
at
org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(Mai
nDeployerImpl.java:440)
at
org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDepl
oyerImpl.java:381)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfi
le(ProfileServiceBootstrap.java:366)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap
(ProfileServiceBootstrap.java:246)
at
org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstr
ap.java:89)
at
org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.jav
a:401)
at
org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:
340)
at org.jboss.Main.boot(Main.java:210)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse
source: Permission denied
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.
java:178)
at
org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:16
9)
at
org.jboss.web.metamodel.descriptor.WebDDObjectFactory.parse(WebDDObjectF
actory.java:86)
at
org.jboss.web.tomcat.tc6.TomcatInjectionContainer.processMetadata(Tomcat
InjectionContainer.java:256)
... 65 more
Caused by: java.io.IOException: Permission denied
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:194)
at
org.apache.xerces.impl.XMLEntityManager$RewindableInputStream.read(Unkno
wn Source)
at
sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)
at
sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source)
at org.apache.xerces.impl.XMLEntityScanner.skipSpaces(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dis
patch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno
wn Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.
java:174)
... 68 more
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry
IT executives: Red Hat still #1 for value
http://www.redhat.com/promo/vendor/
18 years
RE: [jboss-dev] Re: Fwd: AS 5 Beta 2 Discussion
by Galder Zamarreno
Does this mean there'll be a final EJB3 release for AS 4.2?
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
IT executives: Red Hat still #1 for value http://www.redhat.com/promo/vendor/
________________________________
From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Andrig T Miller
Sent: 29 November 2006 23:05
To: Scott M Stark
Cc: Scott M Stark; JBoss.org development list; JavaEE-TCK; Ivelin Ivanov
Subject: [jboss-dev] Re: Fwd: AS 5 Beta 2 Discussion
I agree. In fact, we specifically created 4.2 for these types of issues. With the inclusion of EJB 3 in 4.2 as fully supported technology, we should make this as clean as possible.
Andy
On Tue, 2006-11-28 at 11:11 -0800, Scott M Stark wrote:
Yes, its work to align the remoting uses. This has to be done for
jboss5, and ejb3 pulls this issue into 4.2. I don't see keeping the
legacy remoting layers as default as beneficial for 4.2.
Tom Elrod wrote:
>> 2. A related issue is alignment on jboss-remoting transports. There was
>> a jira issue to make the pooled invoker the default. The real question
>> is why don't we move to the unified invoker based on remoting to align
>> the transports between 4.2/5/ejb3.
>
> I was thinking the main reason we didn't switch to using unified
> invokers for 4.x was due to needing to update docs and training
> materials (since config would be completely different). However, if
> this is not an issue and would prefer to switch default to be unified
> invoker for 4.2, the change to standardjboss.xml, jboss-service.xml,
> and cluster-service.xml is simple (but still have the issue of where
> else needs to be changed, such as client user tx, testsuite, jmx
> invoker, etc.).
Andrig (Andy) Miller
VP, Engineering
JBoss, a division of Red Hat
18 years, 1 month
RE: [jboss-dev] JBossAS 4.2.0
by Dimitris Andreadis
The point is JbossAS 4.2.0.CR1 needs *a lot* of testing before it goes
out, so we need to have the messaging implementation available by
January, or else delay the whole thing.
> On a related note:
>
> What are people's thoughts on having JBoss Messaging 1.2 GA
> as the default messaging provider in AS 4.2 (as well as AS 5
> clearly), rather than JBoss MQ.
>
> By 4.2 GA we should be fully functional with clustering etc....
18 years, 1 month
