June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4929) JBoss7 Fails ASV Scan Report Attestation of Scan Compliance

by Carlos Oliva (JIRA)

Carlos Oliva created AS7-4929: --------------------------------- Summary: JBoss7 Fails ASV Scan Report Attestation of Scan Compliance Key: AS7-4929 URL: https://issues.jboss.org/browse/AS7-4929 Project: Application Server 7 Issue Type: Quality Risk Affects Versions: 7.0.2.Final Environment: Centos Reporter: Carlos Oliva Fix For: 7.0.2.SP1 ASV Scan Report Attestation of Scan Compliance. Vulnerabilities Noted for each IP Address https (tcp/443) GET /LETtoaCuluFoy4DePCwPLiT0HI1s36zHz9s712uSci 4zxnjnmPAmXpdcnGMYmVwDfBGtXI6zXgIJ1YC8lqJ0T YlUP8hajSNTWZJH7RUk1K6JHLGgGnDaMfSojaxweHvj cnRe3KKTJ8miLU3U3XnS4KZ4bihRqT2rIkowzQJHSk9 VbbQ26pdrzLoImGB4v9lqUFyewXsahnz55dwjEDBNRE ZEbS7b67a<font%20size=50>DEFACED<!--//-- : MyWebServer 1.0.2 is vulnerable to HTML injection. Upgrade to a later version. CVE-2002-1453 Medium 4.3 Fail http (tcp/80) GET /LNSAZoL2iuV3PmcrZl0W5YhMwILOBPbZwzEHVi5QAM dlOJcFL6Y0Ihv21bU7R3461Q80T3CFq9WqFvx3lfcgs MIZ4MDac8YVcxkBralskmulwlrf5JnvLuewKZ402AkB LBIK0CZY7ajOn7U9xzZ0LAgwAzrUaw9UViczNtTyvEK hm7WnyF5dfR084QH966s324XgjXktxVXXaqe7xtf3d5 bTukJXDoo<font%20size=50>DEFACED<!--//-- : MyWebServer 1.0.2 is vulnerable to HTML injection. Upgrade to a later version. CVE-2002-1453 -- 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, 6 months

4
15
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1820) Remove references to "UsingBatchUpdates" from the *-persistence-service.xml files and the documentation.

by Justin Bertram (JIRA)

Remove references to "UsingBatchUpdates" from the *-persistence-service.xml files and the documentation. -------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1820 URL: https://jira.jboss.org/browse/JBMESSAGING-1820 Project: JBoss Messaging Issue Type: Task Components: Configuration and Management, Documentation and Training Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP10 Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 1.4.0.SP3.CP11, 1.4.8.GA This feature was removed in JBoss Messaging 1.4.0.CR2, but the documentation and configuration files were never updated. -- 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, 6 months

3
14
0 / 0

[JBoss JIRA] (AS7-4301) JBOSS 7.1.1 turkish locale problem at startup

by Serkan Yıldırım (JIRA)

Serkan Yıldırım created AS7-4301: ------------------------------------ Summary: JBOSS 7.1.1 turkish locale problem at startup Key: AS7-4301 URL: https://issues.jboss.org/browse/AS7-4301 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.1.Final Environment: Windows 7 x64 Java 1.6 update 26 Locale: Turkish Reporter: Serkan Yıldırım Assignee: Jason Greene Hi, When i run standalone.bat with turkish locale, i got exception below. If I change locale to english, it starts with no problem. However, it is not a good solution to give locale as parameter at startup I think. Our environment works in Turkish locale for example. We want JBOSS AS to run in turkish locale also. When i looked at the exception, i saw that in ThreadsParser class at line 882, there is a code piece like: 882 unit = Enum.valueOf(TimeUnit.class, value.toUpperCase()); At this line in upperCase method, 'i' is converted to capital letter I with dot above when locale is turkish due to information at "http://docs.oracle.com/javase/1.4.2/docs/api/java/lang/String.html#toUppe..." Therefore enum is not found and we got exception. If we give locale english as parameter to jboss as at startup, conversion is done correctly at the code above and enum is found. Calling "D:\Development\Servers\jboss-as-7.1.1.Final\bin\standalone.conf.bat" =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: D:\Development\Servers\jboss-as-7.1.1.Final JAVA: C:\Program Files (x86)\Java\jdk1.6.0_26\bin\java JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun. rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djb oss.server.default.config=standalone.xml -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n =============================================================================== Listening for transport dt_socket at address: 8787 13:42:59,798 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA 13:43:00,496 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA 13:43:00,532 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting 13:43:02,146 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceExcepti on: JBAS014676: Failed to parse configuration at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.1.1.Final.jar :7.1.1.Final] at org.jboss.as.server.ServerService.boot(ServerService.java:266) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Fina l] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] Caused by: java.lang.IllegalArgumentException: No enum const class java.util.concurrent.TimeUnit.M¦LL¦SECONDS at java.lang.Enum.valueOf(Enum.java:196) [rt.jar:1.6.0_26] at org.jboss.as.threads.ThreadsParser.parseTimeSpec(ThreadsParser.java:874) at org.jboss.as.threads.ThreadsParser.parseUnboundedQueueThreadPool(ThreadsParser.java:518) at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.parseThreadPools(EJB3Subsystem12Parser.java:1103) at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.readElement(EJB3Subsystem12Parser.java:297) at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.readElement(EJB3Subsystem12Parser.java:55) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:894) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:330) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:127) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:100) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.1.Final.jar :7.1.1.Final] ... 3 more 13:43:02,160 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. 13:43:02,179 INFO [org.jboss.as] JBAS015950: JBoss AS 7.1.1.Final "Brontes" stopped in 2ms Press any key to continue . . . -- 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, 6 months

6
12
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, 6 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, 6 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, 6 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, 6 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, 6 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, 6 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, 6 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 June 2012