October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5222) Insufficient log info for failed deployments

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5222: ----------------------------------- Summary: Insufficient log info for failed deployments Key: AS7-5222 URL: https://issues.jboss.org/browse/AS7-5222 Project: Application Server 7 Issue Type: Bug Components: Server Reporter: Thomas Diesler Assignee: Jason Greene Fix For: 7.2.0.Alpha1 I have a deployment that fails with {code} 12:06:25,717 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS015870: Deploy of deployment "example-webapp.wab" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"example-webapp.wab\".REGISTER Missing[JBAS014861: <one or more transitive dependencies>]"]} 12:06:25,737 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment example-webapp.wab in 18ms {code} It doesn't say which dependencies are missing -- 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

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] (AS7-5716) Improve logging of deployment failures

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5716: ------------------------------------- Summary: Improve logging of deployment failures Key: AS7-5716 URL: https://issues.jboss.org/browse/AS7-5716 Project: Application Server 7 Issue Type: Enhancement Components: Domain Management Affects Versions: 7.1.3.Final (EAP) Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 7.2.0.Alpha1 Minor improvements related to logging of failures of deployment operations: 1) Log at ERROR, not INFO. 2) The deployment scanner independently logs failures of initial deploy at ERROR. But it doesn't log other failures (e.g. redeploy, undeploy.) Remove this logging as it will be redundant once the main logging is at ERROR. 3) Use the multi-line formatted version of ModelNode.toString() instead of leaving everything on one line. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-5715) Improve ServiceVerificationHandler missing dependency reporting

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5715: ------------------------------------- Summary: Improve ServiceVerificationHandler missing dependency reporting Key: AS7-5715 URL: https://issues.jboss.org/browse/AS7-5715 Project: Application Server 7 Issue Type: Enhancement Components: Domain Management Affects Versions: 7.1.3.Final (EAP) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 The reporting of missing services by the ServiceVerificationHandler is overly verbose and sometimes hides more important information in a mountain of detail. To improve: 1) Reporting of services that could not start due to a transitive missing dependency should be reported in a separate property in the failure description ModelNode object than the failure of services that have immediate unavailable dependencies. 2) If any services are missing transitive dependencies, the SVH should scan the ServiceContainer looking for any services that could not start due to an immediate dependency being missing. Use those to create a global list of missing services to include with the "transitive missing" failure description. That's better data than the current "JBAS014861: <one or more transitive dependencies>". 3) Improve the formatting of the list of services that are missing transitive dependencies, to make it less mindlessly repetitive. 4) Probably most importantly, tracking any services names already reported as being missing or failed in the overall SVH failure description. When the global list of missing services is prepared in 2) above, compare it to this list. If the two sets are identical, don't bother reporting the "missing transitive dependency" problems. That information is unlikely to be useful, since the problem services are already reported in the "missing immediate dependency" section of the failure description. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9435) Compile JBoss 6.1 with JDK 6

by Frank Langelage (JIRA)

Compile JBoss 6.1 with JDK 6 ---------------------------- Key: JBAS-9435 URL: https://issues.jboss.org/browse/JBAS-9435 Project: Legacy JBoss Application Server 6 Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Affects Versions: 6.0.0.Final Reporter: Frank Langelage Assignee: Paul Gier JBoss AS 6.x requires JDK 6 AFAIK. But the source is compiled with source / target 1.5. To change this I changed pom.xml like this: Index: jboss-head/pom.xml =================================================================== --- jboss-head/pom.xml (revision 111957) +++ jboss-head/pom.xml (working copy) @@ -51,8 +51,8 @@ <artifactId>maven-compiler-plugin</artifactId> <version>2.3.2</version> <configuration> - <source>1.5</source> - <target>1.5</target> + <source>1.6</source> + <target>1.6</target> <showDeprecation>false</showDeprecation> <showWarnings>false</showWarnings> </configuration> To compile successfully I had to change one file: Index: jboss-head/varia/src/main/java/org/jboss/jdbc/HypersonicDatabase.java =================================================================== --- jboss-head/varia/src/main/java/org/jboss/jdbc/HypersonicDatabase.java (revision 111957) +++ jboss-head/varia/src/main/java/org/jboss/jdbc/HypersonicDatabase.java (working copy) @@ -36,7 +36,7 @@ /** * Integration with <a href="http://sourceforge.net/projects/hsqldb">HSQLDB</a> * - * @author <a href="mailto:rickard.oberg@telkel.com">Rickard ï¿½berg</a> + * @author <a href="mailto:rickard.oberg@telkel.com">Rickard Öberg</a> * @author <a href="mailto:Scott_Stark@displayscape.com">Scott Stark</a>. * @author <a href="mailto:pf@iprobot.com">Peter Fagerlund</a> * @author <a href="mailto:jason@planet57.com">Jason Dillon</a> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8326) Invalid dependency in jboss-as-jmxpom

by Martin Höller (JIRA)

Invalid dependency in jboss-as-jmxpom ------------------------------------- Key: JBAS-8326 URL: https://jira.jboss.org/browse/JBAS-8326 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-5.1.0.GA Environment: Maven 2.0.10, JBossAS 5.1.0.GA Reporter: Martin Höller Assignee: Dimitris Andreadis The maven module with groupId "org.jboss.jbossas" and artifactId "jboss-as-jmx" has a dependency to jboss-as-j2se. This might be ok. However, the dependency is declared twice, the second time with a type of "test-jar" but not with scope test. This prevents it from beeing used as a dependency in an EAR, as the maven-ear-plugin doesn't know (and shouldn't need to know) how to handle artifacts of type test-jar. It probably should't be packaged in an EAR anyway, but the dependency nevertheless seems wrong. -- 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

13 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-8117) Rename folder prefix in distribution zip from jboss to jboss-as

by Dan Allen (JIRA)

Rename folder prefix in distribution zip from jboss to jboss-as --------------------------------------------------------------- Key: JBAS-8117 URL: https://jira.jboss.org/browse/JBAS-8117 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Dan Allen Assignee: Paul Gier We complain that people still refer to AS as just JBoss but you gotta admit that we're not encouraging them not to considering that the AS download is just called jboss and expands just as jboss. The dist zipfile name (jboss-as-distribution-6.0.0.20100429-M3.zip) is consistent with the renaming. However, when you unzip it, the top-level directory (i.e. JBOSS_HOME) name is "jboss-6.0.0.20100429-M3". Can't we change this to "jboss-as-6.0.0.20100429-M3", or even better to "jboss-as-6.0.0.M3" (I don't think the date is necessary), for future releases? -- 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

13 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-8070) The build.sh and build.bat scripts should be updated to use M2_HOME instead of MAVEN_HOME

by Paul Gier (JIRA)

The build.sh and build.bat scripts should be updated to use M2_HOME instead of MAVEN_HOME ----------------------------------------------------------------------------------------- Key: JBAS-8070 URL: https://jira.jboss.org/browse/JBAS-8070 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Paul Gier Assignee: Paul Gier Fix For: 6.0.0.M4 The build.sh and build.bat scripts should be updated to use M2_HOME instead of MAVEN_HOME -- 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

13 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-607) AS testsuite test targets don't work on windows

by Alexey Loubyansky (JIRA)

AS testsuite test targets don't work on windows ----------------------------------------------- Key: JBBUILD-607 URL: https://jira.jboss.org/jira/browse/JBBUILD-607 Project: JBoss Build System Issue Type: Bug Components: Targets and Tasks Reporter: Alexey Loubyansky Since we've switched to maven repository classpath for testsuite classpath, the classpath got too long to work on windows. So, it either has to be shorter or a manifest-only jar can be created that would reference all the jars and dirs. The problem with the manifest-only jar is that there must be relative path from the jar location to all the other jars and dirs that need to be included in the classpath. Taking into account that the relative path might not exist (e.g. the AS checkout and maven local repo can be on different drives) the jar might not work. (Although, right now on my windows machine fixed it with generating the manifest-only jar.) -- 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

13 years, 8 months

3
5
0 / 0

[JBoss JIRA] (JBEE-105) Create a JBoss version of the JavaBeans activation framework (javax.activation) API

by Paul Gier (JIRA)

Paul Gier created JBEE-105: ------------------------------ Summary: Create a JBoss version of the JavaBeans activation framework (javax.activation) API Key: JBEE-105 URL: https://issues.jboss.org/browse/JBEE-105 Project: JBoss JavaEE Spec APIs Issue Type: Feature Request Components: general Reporter: Paul Gier Assignee: Paul Gier Fix For: No Release The JBoss jaxr-api jar current depends on the javax.activation package. -- 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

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-357) Eclipse PDE integration into Maven and unit test failure

by Mark Proctor (JIRA)

Eclipse PDE integration into Maven and unit test failure -------------------------------------------------------- Key: JBBUILD-357 URL: http://jira.jboss.com/jira/browse/JBBUILD-357 Project: JBoss Build System Issue Type: Bug Components: Maven Reporter: Mark Proctor Assigned To: Paul Gier Eclipse plugin building and testing is automated by ant, executed by the Eclipse antRunner. Inside of Maven we have antRunner called in two different phases. When the test phase has unit test failures, they are not propagated up to maven, so failures are not flagged and a sucecssful build reported. Look in the drools-eclipse module of jboss rules for more details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2012