August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBBUILD-722) Thirdparty rebuild of dtd-parser 1.2-SNAPSHOT

by Paul Gier (JIRA)

Paul Gier created JBBUILD-722: --------------------------------- Summary: Thirdparty rebuild of dtd-parser 1.2-SNAPSHOT Key: JBBUILD-722 URL: https://issues.jboss.org/browse/JBBUILD-722 Project: JBoss Build System Issue Type: Task Components: Thirdparty Builds Reporter: Paul Gier Assignee: Paul Gier Fix For: Thirdparty Builds 2012 The 1.2-SNAPSHOT version of dtdparser is required by Jaxb 2.2.5 -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] (JBBUILD-723) Thirdparty rebuild of rngom 201103-SNAPSHOT

by Paul Gier (JIRA)

Paul Gier created JBBUILD-723: --------------------------------- Summary: Thirdparty rebuild of rngom 201103-SNAPSHOT Key: JBBUILD-723 URL: https://issues.jboss.org/browse/JBBUILD-723 Project: JBoss Build System Issue Type: Task Components: Thirdparty Builds Reporter: Paul Gier Assignee: Paul Gier Fix For: Thirdparty Builds 2012 rngom version 201103-SNAPSHOT is required by jaxb 2.2.5 -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-5283) CLONE - Parameter -server is not added for PC and HC when running on IBM JDK 6 and 7

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5283?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5283: ---------------------------------- Labels: (was: eap601candidate) > CLONE - Parameter -server is not added for PC and HC when running on IBM JDK 6 and 7 > ------------------------------------------------------------------------------------ > > Key: AS7-5283 > URL: https://issues.jboss.org/browse/AS7-5283 > Project: Application Server 7 > Issue Type: Bug > Components: Scripts > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP) > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > For IBM JDK 6 and 7 parameter -server is not added for PC and HC, server-one and server-two processes contain -server parameter. > On OracleJDK and OpenJDK it's added by default for domain.sh, in standalone.sh for IBM JDK parameter -server is added. > Problem is in domain.sh script, part starting with line 76. > IBM JDK 6 version output: > java version "1.6.0" > Java(TM) SE Runtime Environment (build pxi3260sr10fp1-20120321_01(SR10 FP1)) > IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr10fp1-20120202_101568 (JIT enabled, AOT enabled) > J9VM - 20120202_101568 > JIT - r9_20111107_21307ifx1 > GC - 20120202_AA) > JCL - 20120320_01 > IBM JDK 7 version output: > java version "1.7.0" > Java(TM) SE Runtime Environment (build pxi3270-20110827_01) > IBM J9 VM (build 2.6, JRE 1.7.0 Linux x86-32 20110810_88604 (JIT enabled, AOT enabled) > J9VM - R26_Java726_GA_20110810_1208_B88592 > JIT - r11_20110810_20466 > GC - R26_Java726_GA_20110810_1208_B88592 > J9CL - 20110810_88604) > JCL - 20110809_01 based on Oracle 7b147 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-3919) HornetQ causing deadlock when max-size-bytes reaches its limit

by Ove Ranheim (JIRA)

Ove Ranheim created AS7-3919: -------------------------------- Summary: HornetQ causing deadlock when max-size-bytes reaches its limit Key: AS7-3919 URL: https://issues.jboss.org/browse/AS7-3919 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.0.Final Reporter: Ove Ranheim Assignee: Andy Taylor Priority: Critical Fix For: 7.1.1.Final I have journal-file-size set to 10 Mb and max-size-bytes set 10 Mb, with a address policy of BLOCK. When my sendMailQueue reaches its limit a deadlock occurs. This is further emphasized in the JBossAS Forum reference. Here's a snippet from jstack after HornetQ crashes. {noformat} Found one Java-level deadlock: ============================= "Thread-878 (HornetQ-client-global-threads-1151364488)": waiting to lock monitor 0x0000000041df8640 (object 0x00000000ea17d6e0, a java.lang.Object), which is held by "Thread-873 (HornetQ-client-global-threads-1151364488)" "Thread-873 (HornetQ-client-global-threads-1151364488)": waiting to lock monitor 0x000000004107c8b8 (object 0x00000000ea17d6d0, a java.lang.Object), which is held by "Thread-878 (HornetQ-client-global-threads-1151364488)" Java stack information for the threads listed above: =================================================== "Thread-878 (HornetQ-client-global-threads-1151364488)": at org.hornetq.core.client.impl.ClientSessionFactoryImpl.close(ClientSessionFactoryImpl.java:461) - waiting to lock <0x00000000ea17d6e0> (a java.lang.Object) - locked <0x00000000ea17d6d0> (a java.lang.Object) at org.hornetq.core.client.impl.ServerLocatorImpl.doClose(ServerLocatorImpl.java:1294) at org.hornetq.core.client.impl.ServerLocatorImpl.close(ServerLocatorImpl.java:1238) at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.close(HornetQXAResourceWrapper.java:392) at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.connectionFailed(HornetQXAResourceWrapper.java:232) at org.hornetq.core.client.impl.ClientSessionFactoryImpl.callFailureListeners(ClientSessionFactoryImpl.java:905) at org.hornetq.core.client.impl.ClientSessionFactoryImpl.failoverOrReconnect(ClientSessionFactoryImpl.java:690) - locked <0x00000000f0222060> (a java.lang.Object) at org.hornetq.core.client.impl.ClientSessionFactoryImpl.handleConnectionFailure(ClientSessionFactoryImpl.java:556) at org.hornetq.core.client.impl.ClientSessionFactoryImpl.access$000(ClientSessionFactoryImpl.java:79) at org.hornetq.core.client.impl.ClientSessionFactoryImpl$1.run(ClientSessionFactoryImpl.java:386) at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) 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:662) "Thread-873 (HornetQ-client-global-threads-1151364488)": at org.hornetq.core.client.impl.ClientSessionFactoryImpl.close(ClientSessionFactoryImpl.java:458) - waiting to lock <0x00000000ea17d6d0> (a java.lang.Object) at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.close(HornetQXAResourceWrapper.java:391) at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.connectionFailed(HornetQXAResourceWrapper.java:232) at org.hornetq.core.client.impl.ClientSessionFactoryImpl.callFailureListeners(ClientSessionFactoryImpl.java:905) at org.hornetq.core.client.impl.ClientSessionFactoryImpl.failoverOrReconnect(ClientSessionFactoryImpl.java:690) - locked <0x00000000ea17d6e0> (a java.lang.Object) at org.hornetq.core.client.impl.ClientSessionFactoryImpl.handleConnectionFailure(ClientSessionFactoryImpl.java:556) at org.hornetq.core.client.impl.ClientSessionFactoryImpl.access$000(ClientSessionFactoryImpl.java:79) at org.hornetq.core.client.impl.ClientSessionFactoryImpl$1.run(ClientSessionFactoryImpl.java:386) at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) 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:662) Found 1 deadlock. {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

13 years, 9 months

5
18
0 / 0

[JBoss JIRA] (AS7-5303) TS: Determine correct behavior of surefire and failsafe regarding ignoring <includes> when running single test.

by Jakub Senko (JIRA)

Jakub Senko created AS7-5303: -------------------------------- Summary: TS: Determine correct behavior of surefire and failsafe regarding ignoring <includes> when running single test. Key: AS7-5303 URL: https://issues.jboss.org/browse/AS7-5303 Project: Application Server 7 Issue Type: Bug Components: Test Suite Reporter: Jakub Senko Assignee: Ondrej Zizka Currently, Test Suite is using surefire plugin to run integration tests. Failsafe is more suitable to do this, and the goal is to migrate from surefire to failsafe for IT. However, there is a difference in how surefire and failsafe behaves when running a single test from CLI. Surefire ignores <includes> pattern by default. This is optional (http://jira.codehaus.org/browse/SUREFIRE-806). Failsafe does not ignore <includes> thus will not execute some tests that surefire would. Currently, this is not optional (http://jira.codehaus.org/browse/SUREFIRE-856). It needs to be decided whether to ignore <includes> by default, in which case http://jira.codehaus.org/browse/SUREFIRE-856 needs to be resolved before migrating to failsafe (https://jira.jboss.org/browse/AS7-4065), or not. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] (HIBERNATE-136) Hibernate 4.1.5.SP1 is not compatible with Java 1.5, it throws java.lang.UnsupportedClassVersionError: org/hibernate/ejb/HibernatePersistence : unsupported classversion 50.0

by Kirill Linnik (JIRA)

Kirill Linnik created HIBERNATE-136: --------------------------------------- Summary: Hibernate 4.1.5.SP1 is not compatible with Java 1.5, it throws java.lang.UnsupportedClassVersionError: org/hibernate/ejb/HibernatePersistence : unsupported classversion 50.0 Key: HIBERNATE-136 URL: https://issues.jboss.org/browse/HIBERNATE-136 Project: Hibernate Integration Issue Type: Bug Environment: Sun Microsystems Java 1.5, build 22 Weblogic 9.2.4 Reporter: Kirill Linnik Assignee: Steve Ebersole -- 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, 9 months

2
6
0 / 0

[JBoss JIRA] (AS7-4293) Support property expansion in redirect-port attribute of the web system's connector

by Sven-Jørgen Karlsen (JIRA)

Sven-Jørgen Karlsen created AS7-4293: ---------------------------------------- Summary: Support property expansion in redirect-port attribute of the web system's connector Key: AS7-4293 URL: https://issues.jboss.org/browse/AS7-4293 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.1.Final Environment: Standalone JBoss AS 7 on RHEL Linux and Windows 7 Enterprise x64 Reporter: Sven-Jørgen Karlsen Assignee: Remy Maucherat Priority: Optional The connector element of the web subsystem doesn't support property expansion, forcing you to hardwire the port number. E.g., writing: ... <subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host"> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="${jboss.web.https.port}"/> ... causes a NumberFormatException. Runtime properties for this attribute was supported in previous versions. Another problem is that there is no predefined property with the above name. An alternative solution is to allow a reference to a socket binding groups in the attribute value, as discussed in http://community.jboss.org/thread/176339 -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] (AS7-4080) @Ignored tests (tracking)

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-4080: --------------------------------- Summary: @Ignored tests (tracking) Key: AS7-4080 URL: https://issues.jboss.org/browse/AS7-4080 Project: Application Server 7 Issue Type: Tracker Components: Test Suite Affects Versions: 7.1.1.Final Reporter: Ondrej Zizka Assignee: Ondrej Zizka Fix For: 7.1.2.Final -- 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, 9 months

2
10
0 / 0

[JBoss JIRA] (AS7-4011) TS: Bad approach used as fallback mechanism for gathering IP address

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-4011?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka resolved AS7-4011. ------------------------------- Resolution: Duplicate Issue JBPAPP-8337 > TS: Bad approach used as fallback mechanism for gathering IP address > -------------------------------------------------------------------- > > Key: AS7-4011 > URL: https://issues.jboss.org/browse/AS7-4011 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 7.1.1.Final > Reporter: Pavel Janousek > Assignee: Ondrej Zizka > Priority: Minor > > There are several places in TS where we can see similar code like this: > {code} > static final String someIPproperty = System.getProperty("<some key>", "localhost"); > {code} > or > {code} > static final String someIPproperty = System.getProperty("<some key>", "127.0.0.1"); > {code} > As you can see above, this fallback mechanism is bound in this case (key value isn't found) to IPv4 only IP address at all. This approach is bad because we can run in other network stack - IPv6 is presented in these days - and in this case the such testcase fails with some strange error due to this issue. > I think we have two option how to resolve this issue: > # Don't use fallback mechanism at all and fix (= remove) them in present testcases > # Create auxiliary class which return 127.0.0.1 or ::1 string (but not string "localhost" because we can't be sure how it is translated (*)) > (*) common setup in Linux is to translate localhost -> 127.0.0.1 and localhost6 -> ::1 > Ad 1) I prefer this option because some forget/miss setting is very easy to catch > Ad 2) This auxiliary class should need to make some magic decision in which IP network stack mode we are now running and return IPv4 or IPv6 lookpack address accordingly. > I've been asking for decision in jboss-as7-dev mailing list [[1|http://lists.jboss.org/pipermail/jboss-as7-dev/2012-March/005449.html]] and we should wait for feedback from developers for final decision how to fix this issue. > [1] http://lists.jboss.org/pipermail/jboss-as7-dev/2012-March/005449.html -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-855) Fungal 0.11.0.Beta11

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-855: ------------------------------------- Summary: Fungal 0.11.0.Beta11 Key: JBJCA-855 URL: https://issues.jboss.org/browse/JBJCA-855 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Beta2 -- 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, 9 months

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