August 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1870) ClientSocketWrapper constructors have a redundant call to createStreams()

by Ron Sigal (JIRA)

ClientSocketWrapper constructors have a redundant call to createStreams() ------------------------------------------------------------------------- Key: JBMESSAGING-1870 URL: https://issues.jboss.org/browse/JBMESSAGING-1870 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.8.GA, 1.4.0.SP3.CP12 Reporter: Ron Sigal Priority: Minor org.jboss.jms.client.remoting.ClientSocketWrapper is derived from org.jboss.remoting.transport.socket.ClientSocketWrapper. The constructors of the former look like public ClientSocketWrapper(Socket socket) throws IOException { super(socket); createStreams(socket, null); } public ClientSocketWrapper(Socket socket, Map metadata, Integer timeout) throws Exception { super(socket, metadata, timeout); createStreams(socket, metadata); } and the constructors of the latter look like public ClientSocketWrapper(Socket socket) throws IOException { super(socket); createStreams(socket, null); } public ClientSocketWrapper(Socket socket, Map metadata, Integer timeout) throws Exception { super(socket, timeout); createStreams(socket, metadata); } The calls to createStreams() in the JBossMessaging versions of ClientSocketWrapper is redundant. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1866) Adapt JBM tests to new failover model

by Yong Hao Gao (JIRA)

Adapt JBM tests to new failover model ------------------------------------- Key: JBMESSAGING-1866 URL: https://issues.jboss.org/browse/JBMESSAGING-1866 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Affects Versions: 1.4.8.GA, 1.4.0.SP3.CP12 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP13, 1.4.8.SP1 In jbm test suite some tests will fail if the 'keepOldFailoverModel' is set to false. This is because with new model, the failover for a dead node doesn't happen immediately. This affects all tests which expect a failover to happen after a certain timeout. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
11
0 / 0

[JBoss JIRA] Created: (AS7-1440) allow default persistence provider to be configured

by Scott Marlow (JIRA)

allow default persistence provider to be configured --------------------------------------------------- Key: AS7-1440 URL: https://issues.jboss.org/browse/AS7-1440 Project: Application Server 7 Issue Type: Feature Request Components: JPA / Hibernate Reporter: Scott Marlow Fix For: 7.1.0.Alpha1 Allow default persistence provider to be configured, so that a different provider could be used by default. This helps improve our JPA plugability (users preferred persistence provider can become the default). Without this feature, the user could instead make application changes to the persistence.xml to accomplish the same (not always possible if user cannot make app changes). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWEB-193) SeLinux policy for JBoss Enterprise Web Server

by Sam Weaver (JIRA)

SeLinux policy for JBoss Enterprise Web Server ---------------------------------------------- Key: JBWEB-193 URL: https://issues.jboss.org/browse/JBWEB-193 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Sam Weaver Assignee: Remy Maucherat Priority: Minor SeLinux causes JBoss EWS to stop working, or randomly fail to start. Therefore requesting an SeLinux policy for JBoss EWS. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
1
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

12 years, 3 months

3
14
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

12 years, 3 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

12 years, 3 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

12 years, 3 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

12 years, 3 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

12 years, 3 months

3
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2011