[JBoss JIRA] Created: (JBBOOT-131) Log Bootstrap Descriptors at DEBUG
by Andrew Lee Rubinger (JIRA)
Log Bootstrap Descriptors at DEBUG
----------------------------------
Key: JBBOOT-131
URL: https://jira.jboss.org/jira/browse/JBBOOT-131
Project: JBoss Bootstrap
Issue Type: Task
Components: impl-mc
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Fix For: 2.1.0-alpha-5
Should be friendlier at DEBUG:
18:41:03,978 INFO [AbstractMCServerBase] Starting Microcontainer, Bootstrap Descriptors: [[UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/vfs.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/classloader.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/stdio.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/kernel.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/aop.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/jmx.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/deployers.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/profile.xml]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBAS-7790) Undeployment of an .ear through HDScanner leads to a deploy() call on the deleted deployment
by jaikiran pai (JIRA)
Undeployment of an .ear through HDScanner leads to a deploy() call on the deleted deployment
--------------------------------------------------------------------------------------------
Key: JBAS-7790
URL: https://jira.jboss.org/jira/browse/JBAS-7790
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ProfileService
Environment: JBoss AS trunk r102035
Reporter: jaikiran pai
Assignee: Scott M Stark
On the current AS trun (r102035):
- Start the "default" profile of the server with a .ear file in the deploy folder
- Once the server has completely started, delete the .ear from the deploy folder
- HDScanner is triggered and it undeploys the deleted .ear *but also* triggers a deploy on this deleted .ear which results in:
19:54:18,225 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Parse: name=file:///NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/jbas-7760-earone.ear state=PreParse mode=Manual requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error during deploy: file:///NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/jbas-7760-earone.ear
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:185)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1857)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1575)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1516)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:377)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1066)
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1305)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1229)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1122)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:649)
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:2008)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1101)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NullPointerException
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:149)
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:127)
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:115)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
... 26 more
19:54:18,227 WARN [org.jboss.system.server.profileservice.hotdeploy.HDScanner] Failed to process changes: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
file:///NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/jbas-7760-earone.ear
*** DEPLOYMENTS IN ERROR: Name -> Error
file:///NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/jbas-7760-earone.ear -> org.jboss.deployers.spi.DeploymentException: Error during deploy: file:///NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/jbas-7760-earone.ear
Notice that the NPE is triggered through the deploy() flow. A quick look at the code indicates that this is because the org.jboss.system.server.profileservice.repository.HotDeploymentRepository on a call to getModifiedDeployments() returns that .ear as both REMOVED as well as MODIFIED. It returns it as modified because the call to getModifiedDeployments() internally leads to checkForAdditions() method which uses a *cached* VirtualFile for the "deploy" folder. This cached VirtualFile returns the .ear as one of the deployments, even after the deployment has been removed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBAS-7644) Enforce unique names for EE modules within an application
by Brian Stansberry (JIRA)
Enforce unique names for EE modules within an application
---------------------------------------------------------
Key: JBAS-7644
URL: https://jira.jboss.org/jira/browse/JBAS-7644
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-6.0.0.M2
Implement following from EE8.1.1:
All Java EE modules have a name. The name can be explicitly set in the
deployment descriptor for the module. If not set, the name of the module is the
pathname of the module in the ear file with any filename extension (.jar, .war,
.rar) removed, but with any directory names included. The name of a module
must be unique within an application. If and only if the name is not unique (e.g.,
because two names are identical after removing different filename extensions) the
deployment tool may choose new unique names for any of the conflicting
modules; module names that do not conflict must not be changed. The algorithm
for choosing unique names in such a case is product specific.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBAS-7267) Add missing artifacts to the dependency chain
by Andrew Lee Rubinger (JIRA)
Add missing artifacts to the dependency chain
---------------------------------------------
Key: JBAS-7267
URL: https://jira.jboss.org/jira/browse/JBAS-7267
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1
A dependence upon the following should transitively bring in everything AS needs for the runtime:
<!-- AS modules and 3rdparty deps -->
<dependency>
<groupId>org.jboss.jbossas</groupId>
<artifactId>jboss-as-build</artifactId>
<version>${version.org.jboss.jbossas}</version>
<type>pom</type>
</dependency>
However, some modules are in the distribution which are not part of this chain. The following are a list of offenders manually added into the Embedded POM:
<dependency>
<groupId>org.jboss.jbossas</groupId>
<artifactId>jboss-as-management</artifactId>
<version>${version.org.jboss.jbossas}</version>
<classifier>jsr77</classifier>
</dependency>
<dependency>
<groupId>jboss.web</groupId>
<artifactId>jsp-api</artifactId>
<version>${version.jboss.web}</version>
</dependency>
<dependency>
<groupId>jboss.web</groupId>
<artifactId>el-api</artifactId>
<version>${version.jboss.web}</version>
</dependency>
<dependency>
<groupId>jboss.web</groupId>
<artifactId>jasper-jdt</artifactId>
<version>${version.jboss.web}</version>
</dependency>
<dependency>
<groupId>jboss.messaging</groupId>
<artifactId>jboss-messaging</artifactId>
<version>${version.jboss.messaging}</version>
</dependency>
<dependency>
<groupId>org.jboss.slf4j</groupId>
<artifactId>slf4j-jboss-logging</artifactId>
<version>${version.org.slf4j_slf4j.jboss.logging}</version>
</dependency>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBAS-7631) NPE in EjbReferenceResolverBase.getMatch() method
by Richard Opalka (JIRA)
NPE in EjbReferenceResolverBase.getMatch() method
-------------------------------------------------
Key: JBAS-7631
URL: https://jira.jboss.org/jira/browse/JBAS-7631
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Reporter: Richard Opalka
Assignee: jaikiran pai
Fix For: JBossAS-6.0.0.M2
The following commit broke JBossWS/EJB3 integration:
http://fisheye.jboss.org/changelog/JBossAS/?cs=99498
Server side error is:
22:03:33,178 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception: org.jboss.wsf.common.injection.InjectionException: Cannot inject field annotated with @EJB annotation: private org.jboss.test.ws.jaxws.ejb3Integration.injection.shared.BeanIface org.jboss.test.ws.jaxws.ejb3Integration.injection.shared.handlers.TestHandler.bean1
at org.jboss.wsf.common.injection.InjectionException.rethrow(InjectionException.java:106)
at org.jboss.wsf.common.injection.InjectionHelper.injectEJBAnnotatedAccessibleObjects(InjectionHelper.java:367)
at org.jboss.wsf.common.injection.InjectionHelper.injectResources(InjectionHelper.java:111)
at org.jboss.ws.core.jaxws.handler.HandlerResolverImpl.addHandler(HandlerResolverImpl.java:174)
at org.jboss.ws.core.jaxws.handler.HandlerResolverImpl.initHandlerChain(HandlerResolverImpl.java:152)
at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:89)
at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:125)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:172)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:502)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:299)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:206)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:336)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:366)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:872)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NullPointerException
at org.jboss.ejb3.common.resolvers.spi.EjbReferenceResolverBase.getMatch(EjbReferenceResolverBase.java:104)
at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.find(ScopedEJBReferenceResolver.java:44)
at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:56)
at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.findWithin(ScopedEJBReferenceResolver.java:77)
at org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver.resolveEjb(ScopedEJBReferenceResolver.java:83)
at org.jboss.webservices.integration.injection.EJBBeanReferenceResolver.resolveField(EJBBeanReferenceResolver.java:88)
at org.jboss.wsf.common.injection.resolvers.AbstractReferenceResolver.resolve(AbstractReferenceResolver.java:80)
at org.jboss.wsf.common.injection.InjectionHelper.injectEJBAnnotatedAccessibleObjects(InjectionHelper.java:361)
... 29 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (EJBTHREE-2062) Fix the removedislocal testcase
by jaikiran pai (JIRA)
Fix the removedislocal testcase
-------------------------------
Key: EJBTHREE-2062
URL: https://jira.jboss.org/jira/browse/EJBTHREE-2062
Project: EJB 3.0
Issue Type: Task
Components: testsuite
Reporter: jaikiran pai
Assignee: jaikiran pai
The removedislocal testcase is failing with:
Error deploying removedislocal-test.jar: EJBTHREE-2020: No InjectionCallbackStack defined for domain org.jboss.aop.Domain@344986 of jboss.j2ee:jar=removedislocal-test.jar,name=StatelessBean,service=EJB3
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:189)
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:59)
at org.jboss.deployers.vfs.spi.deployer.AbstractSimpleVFSRealDeployer.deploy(AbstractSimpleVFSRealDeployer.java:56)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
This testcase uses its own server configuration, specifically the ejb3-interceptors-aop.xml maintained at ejb3/trunk/testsuite/src/test/resources/test-configs/removedislocal/deploy
We'll have to fix that ejb3-interceptors-aop.xml to include the InjectionCallbackStack
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months