April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10094) [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10094?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-10094: --------------------------------------- Yes, problem is in libAio.so files provided from WF branch. > [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64 > ----------------------------------------------------------------- > > Key: WFLY-10094 > URL: https://issues.jboss.org/browse/WFLY-10094 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq, feature-branch-blocker > > LibAIO does not get loaded on RHEL 6 x86_64: > {code} > [hudson@rhel6-large-2723 bin]$ sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000 > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /tmp/jboss-eap > JAVA: java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > ... > 10:14:31,918 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 10:14:32,017 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/jboss-eap/standalone/data/activemq/journal,bindingsDirectory=/tmp/jboss-eap/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/jboss-eap/standalone/data/activemq/largemessages,pagingDirectory=/tmp/jboss-eap/standalone/data/activemq/paging) > 10:14:32,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal > ... > {code} > libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag. > Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) > Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10204) Missing file in openjdk-orb source jar

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-10204?page=com.atlassian.jira.plugin... ] Tomasz Adamski updated WFLY-10204: ---------------------------------- Security: (was: Red Hat Internal) > Missing file in openjdk-orb source jar > -------------------------------------- > > Key: WFLY-10204 > URL: https://issues.jboss.org/browse/WFLY-10204 > Project: WildFly > Issue Type: Bug > Components: IIOP > Affects Versions: 12.0.0.Final > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Fix For: 13.0.0.Beta1 > > > Java 9 specific class files in > /META-INF/versions/9/ folder > in the multi-release module > $JBOSS_HOME/modules/system/layers/base/javax/orb/api/main/openjdk-orb-8.0.8.Final-redhat-1.jar > are missing source file in jboss-eap-7.1.0.ER2.2-maven-repository.zip > Actually there are only .class (instead of expected .java) files in > jboss-eap-7.1.0.ER2.2-maven-repository.zip/jboss-eap-7.1.0.GA-maven-repository/maven-repository/org/jboss/openjdk-orb/openjdk-orb/8.0.8.Final-redhat-1/openjdk-orb-8.0.8.Final-redhat-1-sources.jar/META-INF/versions/9/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3715) JBOSS_HOME is unset in powershell scripts

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3715?page=com.atlassian.jira.plugi... ] Lin Gao updated WFCORE-3715: ---------------------------- Labels: downstream_dependency (was: ) > JBOSS_HOME is unset in powershell scripts > ----------------------------------------- > > Key: WFCORE-3715 > URL: https://issues.jboss.org/browse/WFCORE-3715 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Environment: Windows power-shell. > Reporter: Lin Gao > Assignee: Lin Gao > Labels: downstream_dependency > > When using ps1 (power-shell) scripts in a windows environment the JBOSS_HOME environment variable is always unset at the end. For example using the {{jboss-cli.ps1}} script. > That variable can be set by the user and this not be affected by the execution of the scripts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3715) JBOSS_HOME is unset in powershell scripts

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3715?page=com.atlassian.jira.plugi... ] Lin Gao reassigned WFCORE-3715: ------------------------------- Assignee: Lin Gao > JBOSS_HOME is unset in powershell scripts > ----------------------------------------- > > Key: WFCORE-3715 > URL: https://issues.jboss.org/browse/WFCORE-3715 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Environment: Windows power-shell. > Reporter: Lin Gao > Assignee: Lin Gao > > When using ps1 (power-shell) scripts in a windows environment the JBOSS_HOME environment variable is always unset at the end. For example using the {{jboss-cli.ps1}} script. > That variable can be set by the user and this not be affected by the execution of the scripts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3730) Use of relative-to in path in domain mode prevents the server from starting up.

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3730?page=com.atlassian.jira.plugi... ] Lin Gao updated WFCORE-3730: ---------------------------- Labels: downstream_dependency (was: ) > Use of relative-to in path in domain mode prevents the server from starting up. > ------------------------------------------------------------------------------- > > Key: WFCORE-3730 > URL: https://issues.jboss.org/browse/WFCORE-3730 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Teresa Miyar > Assignee: Brian Stansberry > Labels: downstream_dependency > > Server does not start on domain mode when setting relative-to in the path > {code:java} > <paths> > <path name="apps.log.dir" path="/apps/logs" relative-to="jboss.domain.base.dir"/> > </paths> > {code} > {code:java} > [Host Controller] 13:28:05,730 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/path=apps.log.dir' are not available: > [Host Controller] org.wildfly.management.path.jboss.domain.base.dir in context 'global'; Possible registration points for this capability: > [Host Controller] /host=master/path=* > [Host Controller] /host=master/server-config=*/path=* > [Host Controller] /path=* > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10181) Deadlock for threads executing org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.isEqual

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10181?page=com.atlassian.jira.plugin... ] Lin Gao updated WFLY-10181: --------------------------- Labels: downstream_dependency (was: ) > Deadlock for threads executing org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.isEqual > ------------------------------------------------------------------------------------------------ > > Key: WFLY-10181 > URL: https://issues.jboss.org/browse/WFLY-10181 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 12.0.0.Final > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Labels: downstream_dependency > Fix For: 13.0.0.Beta1 > > > Two or more threads hold one lock on an instance of java.util.Collections$SynchronizedMap and attempt to obtain a lock on a different instance (e.g. locks on 0x00000001d0d08bd8 and 0x00000001cea22628 in the example below) > "thread-one" ... > java.lang.Thread.State: BLOCKED (on object monitor) > at java.util.Collections$SynchronizedMap.get(Collections.java:2584) > waiting to lock <0x00000001cea22628> (a java.util.Collections$SynchronizedMap) > at java.util.AbstractMap.equals(AbstractMap.java:495) > at java.util.Collections$SynchronizedMap.equals(Collections.java:2631) > locked <0x00000001d0d08bd8> (a java.util.Collections$SynchronizedMap) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.isEqual(XAManagedConnectionFactory.java:563) > locked <0x00000001d0d08bd8> (a java.util.Collections$SynchronizedMap) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.equals(XAManagedConnectionFactory.java:598) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory$SubjectActions.doCheck(BaseWrapperManagedConnectionFactory.java:1397) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory$SubjectActions.addMatchingProperties(BaseWrapperManagedConnectionFactory.java:1508) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.getConnectionProperties(BaseWrapperManagedConnectionFactory.java:1135) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.matchManagedConnections(XAManagedConnectionFactory.java:533) > ... > at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138) > at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:66) > ... > "thread-two" ... > java.lang.Thread.State: BLOCKED (on object monitor) > at java.util.Collections$SynchronizedMap.size(Collections.java:2572) > waiting to lock <0x00000001d0d08bd8> (a java.util.Collections$SynchronizedMap) > at java.util.AbstractMap.equals(AbstractMap.java:482) > at java.util.Collections$SynchronizedMap.equals(Collections.java:2631) > locked <0x00000001cea22628> (a java.util.Collections$SynchronizedMap) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.isEqual(XAManagedConnectionFactory.java:563) > locked <0x00000001cea22628> (a java.util.Collections$SynchronizedMap) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.equals(XAManagedConnectionFactory.java:598) > ... [same stack as thread-one above] ... > at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138) > at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:66) > ... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10203) Upgrade JBossWS to 5.2.1.Final

by Alessio Soldano (JIRA)

Alessio Soldano created WFLY-10203: -------------------------------------- Summary: Upgrade JBossWS to 5.2.1.Final Key: WFLY-10203 URL: https://issues.jboss.org/browse/WFLY-10203 Project: WildFly Issue Type: Component Upgrade Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 13.0.0.Beta1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2460) Wrong dsl generation of constraints using globals in executable model

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2460: ----------------------------------- Summary: Wrong dsl generation of constraints using globals in executable model Key: DROOLS-2460 URL: https://issues.jboss.org/browse/DROOLS-2460 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2459) Wrong dsl generation of constraints using globals in executable model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2459?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2459. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/af9fa6da01e5f2946178007d8fd40e7... > Wrong dsl generation of constraints using globals in executable model > --------------------------------------------------------------------- > > Key: DROOLS-2459 > URL: https://issues.jboss.org/browse/DROOLS-2459 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2459) Wrong dsl generation of constraints using globals in executable model

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2459: ----------------------------------- Summary: Wrong dsl generation of constraints using globals in executable model Key: DROOLS-2459 URL: https://issues.jboss.org/browse/DROOLS-2459 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
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 April 2018