August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2022) TS: Coverage reports

by Ondrej Zizka (Created) (JIRA)

TS: Coverage reports -------------------- Key: AS7-2022 URL: https://issues.jboss.org/browse/AS7-2022 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Affects Versions: 7.1.0.Alpha1 Reporter: Ondrej Zizka Assignee: Ondrej Zizka There are some coverage jobs in Hudson: * Aggregated: https://hudson.qa.jboss.com/hudson//view/JBoss%20AS/job/jboss-as7-code-co... * Per module: https://hudson.qa.jboss.com/hudson/view/JBoss AS/job/JBoss-AS-7.0.x-unit-coverage/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

9
42
0 / 0

[JBoss JIRA] (AS7-4704) Cannot deploy exploded .jar inside exploded .war

by Adrian Mitev (JIRA)

Adrian Mitev created AS7-4704: --------------------------------- Summary: Cannot deploy exploded .jar inside exploded .war Key: AS7-4704 URL: https://issues.jboss.org/browse/AS7-4704 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Adrian Mitev Hi all! I deploy my app as an exploded war there in WEB-INF/lib there is a jar deployed as exploded folder. However when the server starts I get the following exception: 17:59:15,423 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."MyApp.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."MyApp.war".STRUCTURE: Failed to process phase STRUCTURE of deployment "MyApp.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018037: Failed to process WEB-INF/lib: "/C:/Users/amitev/Desktop/mse2012/jboss-as-7.1.1.Final/standalone/deployments/MyApp.war/WEB-INF/lib/Module1.jar" at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.deploy(WarStructureDeploymentProcessor.java:120) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] ... 5 more Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018037: Failed to process WEB-INF/lib: "/C:/Users/amitev/Desktop/mse2012/jboss-as-7.1.1.Final/standalone/deployments/MyApp.war/WEB-INF/lib/Module1.jar" at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createWebInfLibResources(WarStructureDeploymentProcessor.java:175) at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createResourceRoots(WarStructureDeploymentProcessor.java:153) at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.deploy(WarStructureDeploymentProcessor.java:114) ... 6 more Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.6.0_24] at java.util.zip.ZipFile.<init>(ZipFile.java:127) [rt.jar:1.6.0_24] at java.util.jar.JarFile.<init>(JarFile.java:135) [rt.jar:1.6.0_24] at java.util.jar.JarFile.<init>(JarFile.java:99) [rt.jar:1.6.0_24] at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:97) at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:83) at org.jboss.vfs.VFS.mountZip(VFS.java:408) at org.jboss.vfs.VFS.mountZip(VFS.java:434) at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createWebInfLibResources(WarStructureDeploymentProcessor.java:170) ... 8 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

4
11
0 / 0

[JBoss JIRA] (AS7-5304) NPE in org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.createBeanDeploymentArchive deploying war with WEB-INF/beans.xml but no WEB-INF/classes

by Marek Schmidt (JIRA)

Marek Schmidt created AS7-5304: ---------------------------------- Summary: NPE in org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.createBeanDeploymentArchive deploying war with WEB-INF/beans.xml but no WEB-INF/classes Key: AS7-5304 URL: https://issues.jboss.org/browse/AS7-5304 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Environment: AS 7.2.0.Alpha1-SNAPSHOT 2012-08-03 a97a04dbc9b57a18e4baf6bcc32ba1c4f589c974 Reporter: Marek Schmidt Assignee: Stuart Douglas Fix For: 7.2.0.Alpha1 Attempting to deploy a WAR with only WEB-INF/beans.xml fails, if WEB-INF/classes directory not present in the WAR. {noformat} 13:38:34,534 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" started in 3686ms - Started 135 of 211 services (75 services are passive or on-demand) 13:42:03,156 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test.war" 13:42:03,339 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment test.war 13:42:03,341 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."test.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "test.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24] at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24] Caused by: java.lang.NullPointerException at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.createBeanDeploymentArchive(BeanArchiveProcessor.java:168) at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.deploy(BeanArchiveProcessor.java:97) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] ... 5 more 13:42:03,356 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS015870: Deploy of deployment "test.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"test.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment \"test.war\" Caused by: java.lang.NullPointerException"}} 13:42:03,371 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment test.war in 14ms {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2791) Spring's JpaTransactionManager should be used instead of both: DroolsSpringTransactionManager and DroolsSpringJpaManager

by Anatoly Polinsky (JIRA)

Spring's JpaTransactionManager should be used instead of both: DroolsSpringTransactionManager and DroolsSpringJpaManager ------------------------------------------------------------------------------------------------------------------------ Key: JBRULES-2791 URL: https://jira.jboss.org/browse/JBRULES-2791 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL, FUTURE Environment: Spring Based Applications Reporter: Anatoly Polinsky Assignee: Mark Proctor Instead of having two different components: "DroolsSpringTransactionManager" and "DroolsSpringJpaManager" that aim to do the work of "org.springframework.orm.jpa.JpaTransactionManager", and trying to fit a JTA model into it, the Spring's "JpaTransactionManager" itself should be used. And instead of manually managing and constantly getting references to a "proper entity manager" from JpaManger within a SingleSessionCommandService, a @PersistenceContext should be injected. This will decouple SingleSessionCommandService from JpaManager interface, and will allow _any_ JPA provider to inject an entity manager. It has more benefits, such as trust in underline JPA providers ( e.g. Hibernate ) and Spring Transaction Management capabilities to manage the process that they are actually excellent at. /Anatoly -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
2
0 / 0

[JBoss JIRA] (JBCOMMON-128) Fix Regression introduced by JBCOMMON-106 in EAP 5.1.2

by Dimitris Andreadis (JIRA)

Dimitris Andreadis created JBCOMMON-128: ------------------------------------------- Summary: Fix Regression introduced by JBCOMMON-106 in EAP 5.1.2 Key: JBCOMMON-128 URL: https://issues.jboss.org/browse/JBCOMMON-128 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.18.GA Reporter: Dimitris Andreadis Assignee: Brad Maxwell Fix For: 2.2.20.GA Record in JBCommon JIRA the work done for jbpapp-8065 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
1
0 / 0

[JBoss JIRA] (JBCOMMON-126) NullPointerException when using PropertyMap concurrently

by Michael Pradel (JIRA)

Michael Pradel created JBCOMMON-126: --------------------------------------- Summary: NullPointerException when using PropertyMap concurrently Key: JBCOMMON-126 URL: https://issues.jboss.org/browse/JBCOMMON-126 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.18.GA Environment: All environments Reporter: Michael Pradel PropertyMap extends Properties, which is a thread-safe class, but it doesn't preserve its thread safety. This leads to surprising crashes if you have a reference of type Properties (documented as thread-safe) that turns out to be a PropertyMap (not thread-safe). Here's a simplified example that shows how we hit this bug: final Properties p = getProps(); p.setProperty("a", "b"); Thread t1 = new Thread(new Runnable() { public void run() { p.remove("a"); } }); Thread t2 = new Thread(new Runnable() { public void run() { p.clear(); } }); t1.start(); t2.start(); try { t1.join(); t2.join(); } catch (InterruptedException e) { e.printStackTrace(); } Properties getProps() { // return new Properties(); // OK return new PropertyMap(); // leads to NullPointerException } The code runs fine if getProps returns Properties (as it should, because Properties is thread-safe), but raises a NullPointerException if getProps returns a PropertyMap. Are you aware of this inconsistency? It seems that the safest way of extending Properties is to make methods that override synchronized methods synchronized. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCOMMON-114) Warning for non File URLs should also check for vfszip URLs

by Darran Lofthouse (JIRA)

Warning for non File URLs should also check for vfszip URLs ----------------------------------------------------------- Key: JBCOMMON-114 URL: https://jira.jboss.org/browse/JBCOMMON-114 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.17.GA Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 2.2.18.GA Within the resolveSystemIDasURL method the following check is performed: - if (warnOnNonFileURLs && url.getProtocol().equalsIgnoreCase("file") == false) { log.warn("Trying to resolve systemId as a non-file URL: " + systemId); } With the introduction of vfszip URLs from JBoss 5 these should also be checked and the warning skipped if it is a vfszip URL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCOMMON-123) CLONE - Release jboss-common-core 2.2.18

by Dimitris Andreadis (JIRA)

CLONE - Release jboss-common-core 2.2.18 ---------------------------------------- Key: JBCOMMON-123 URL: https://issues.jboss.org/browse/JBCOMMON-123 Project: JBoss Common Issue Type: Release Security Level: Public (Everyone can see) Components: common-core (2.x) Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Fix For: 2.2.18.GA -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
3
0 / 0

[JBoss JIRA] (JBCOMMON-127) Extend JBossEntityResolver to also implement LSResourceResolver

by Dimitris Andreadis (JIRA)

Dimitris Andreadis created JBCOMMON-127: ------------------------------------------- Summary: Extend JBossEntityResolver to also implement LSResourceResolver Key: JBCOMMON-127 URL: https://issues.jboss.org/browse/JBCOMMON-127 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: common-core (2.x) Reporter: Dimitris Andreadis Assignee: Thomas Diesler Fix For: 2.2.19.GA Extend JBossEntityResolver to also implement LSResourceResolver. Thomas performed this addition without any JIRA record (too bad), so I'm adding this after the fact. I'm removing also an unnecessary dependency that had crept into the change: import com.sun.org.apache.xpath.internal.operations.Bool; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
1
0 / 0

[JBoss JIRA] (EJBTHREE-2275) PreDestroy lifecycle callback not called when Activated EJB3 SFSB removal timeout is reached

by Brad Maxwell (JIRA)

11 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2012