August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2848) Make the Verifier Web Worker connector reusable for different V&V types

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2848?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-2848: --------------------------------- Description: Actions needed for this: * Rename DTable verifier to dtableverifier * Make a register for web workers that finds the right backend providers with CDI * Create webworker service module into kie-wb-common that delivers the correct web worker files based on the module name. (can be reused by non-verifier web workers) * Change the Web worker servlet path from "verifier" to "webworker" * Make the drools-wb-verifier-webworker provide the web worker so the the web worker service picks it up. > Make the Verifier Web Worker connector reusable for different V&V types > ----------------------------------------------------------------------- > > Key: DROOLS-2848 > URL: https://issues.jboss.org/browse/DROOLS-2848 > Project: Drools > Issue Type: Task > Components: DMN Editor, Guided Decision Table Editor, verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Labels: drools-tools > > Actions needed for this: > * Rename DTable verifier to dtableverifier > * Make a register for web workers that finds the right backend providers with CDI > * Create webworker service module into kie-wb-common that delivers the correct web worker files based on the module name. (can be reused by non-verifier web workers) > * Change the Web worker servlet path from "verifier" to "webworker" > * Make the drools-wb-verifier-webworker provide the web worker so the the web worker service picks it up. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-118) [Artemis 2.x upgrade] Transaction remained in prepared state

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFWIP-118?page=com.atlassian.jira.plugin.... ] Erich Duda commented on WFWIP-118: ---------------------------------- I've just reproduced this issue \[1\] with Wildfly master which uses Artemis 1.5.x so the issue is not caused by Artemis upgrade. \[1\] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/mnovak-verifier-... > [Artemis 2.x upgrade] Transaction remained in prepared state > ------------------------------------------------------------ > > Key: WFWIP-118 > URL: https://issues.jboss.org/browse/WFWIP-118 > Project: WildFly WIP > Issue Type: Bug > Reporter: Erich Duda > Assignee: Kabir Khan > Priority: Blocker > > *Scenario* > * Start group A of two servers (node-1 and node-3) Servers are not in cluster. > * Send messages to queue on node-1. > * Start another group B of two servers(node-2 and node-4). Servers are not in cluster. > * Deploy mdb on both servers in A group. This mdb reads messages from local queue and perform insert into oracle 11 gr2 database, and also sends messages to remote queue on group B. > * Mdb deployed on nodes in group B inserts messages from local queue to oracle 11 gr2 database. > * Kill server node-1. Restart failed node. Process all messages and verify both mdbs performed database insert > After node-1 is killed and restarted, there are still transactions in prepare state and they are not cleared in 10 minutes. The transactions remains on servers from group B. > Logs from test can be found in build - https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/mnovak-verifier-... > *Investigation of issue is in progress. It is not known what component causes it.* > Clebert looked at the logs but there weren't traces from Arjuna. The above build contains also Arjuna traces. Copy paste Clebert's analyses. > {quote}I looked at the output from the clients, and filtered the processing > for one XA that's never commited.. > I looked for the XID on > base64:AAAAAAAAAAAAAP__ChBkGmqipH1benkDAAAJdQAAAAMAAAAAAAAAAAAAAAAAAP__ChBkGmqipH1benkDAAAJaDUyODcHAgIA > and filtered the onMessage that generated it (attached the log as > processingOneMessage.txt): > This XID was never commited simply because the TM never did it. > Probably because of some issue on the JDBC.. but there are no errors, > no exceptions.. totally clean on artemis side. > There are no logging for TM or the MDB itself to correlate other > failures. With the information I have I am certain there were nothing > from Artemis side that would have caused it. > In any case.. this is not replicated at all.. and not related to 87. > This is simply the TM getting confused for some issue on the JDBC. > As far as I am concerned I have fixed the replicated shutdown case. > and i will send PRs upstream now.{quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-118) Transaction remained in prepared state

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFWIP-118?page=com.atlassian.jira.plugin.... ] Erich Duda updated WFWIP-118: ----------------------------- Summary: Transaction remained in prepared state (was: [Artemis 2.x upgrade] Transaction remained in prepared state) > Transaction remained in prepared state > -------------------------------------- > > Key: WFWIP-118 > URL: https://issues.jboss.org/browse/WFWIP-118 > Project: WildFly WIP > Issue Type: Bug > Reporter: Erich Duda > Assignee: Kabir Khan > Priority: Blocker > > *Scenario* > * Start group A of two servers (node-1 and node-3) Servers are not in cluster. > * Send messages to queue on node-1. > * Start another group B of two servers(node-2 and node-4). Servers are not in cluster. > * Deploy mdb on both servers in A group. This mdb reads messages from local queue and perform insert into oracle 11 gr2 database, and also sends messages to remote queue on group B. > * Mdb deployed on nodes in group B inserts messages from local queue to oracle 11 gr2 database. > * Kill server node-1. Restart failed node. Process all messages and verify both mdbs performed database insert > After node-1 is killed and restarted, there are still transactions in prepare state and they are not cleared in 10 minutes. The transactions remains on servers from group B. > Logs from test can be found in build - https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/mnovak-verifier-... > *Investigation of issue is in progress. It is not known what component causes it.* > Clebert looked at the logs but there weren't traces from Arjuna. The above build contains also Arjuna traces. Copy paste Clebert's analyses. > {quote}I looked at the output from the clients, and filtered the processing > for one XA that's never commited.. > I looked for the XID on > base64:AAAAAAAAAAAAAP__ChBkGmqipH1benkDAAAJdQAAAAMAAAAAAAAAAAAAAAAAAP__ChBkGmqipH1benkDAAAJaDUyODcHAgIA > and filtered the onMessage that generated it (attached the log as > processingOneMessage.txt): > This XID was never commited simply because the TM never did it. > Probably because of some issue on the JDBC.. but there are no errors, > no exceptions.. totally clean on artemis side. > There are no logging for TM or the MDB itself to correlate other > failures. With the information I have I am certain there were nothing > from Artemis side that would have caused it. > In any case.. this is not replicated at all.. and not related to 87. > This is simply the TM getting confused for some issue on the JDBC. > As far as I am concerned I have fixed the replicated shutdown case. > and i will send PRs upstream now.{quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10722) Update MyFaces to 2.3.1, EE 8 compliant

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFLY-10722?page=com.atlassian.jira.plugin... ] Dmitrii Tikhomirov reassigned WFLY-10722: ----------------------------------------- Assignee: Dmitrii Tikhomirov (was: Farah Juma) > Update MyFaces to 2.3.1, EE 8 compliant > --------------------------------------- > > Key: WFLY-10722 > URL: https://issues.jboss.org/browse/WFLY-10722 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Affects Versions: 13.0.0.Final > Reporter: Erick de Oliveira Leal > Assignee: Dmitrii Tikhomirov > > Currently, MyFaces defaults to 2.2.11, it makes sense update it to 2.3.1. Since it is compliant to EE 8. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10901) CLI client in jconsole doesn't work with JDK11

by Kabir Khan (JIRA)

Kabir Khan created WFLY-10901: --------------------------------- Summary: CLI client in jconsole doesn't work with JDK11 Key: WFLY-10901 URL: https://issues.jboss.org/browse/WFLY-10901 Project: WildFly Issue Type: Bug Components: Scripts Reporter: Marek Kopecký Assignee: Jean-Francois Denise Priority: Blocker CLI client in jconsole doesn't work with JDK11. JConsole uses CLI. CLI uses WildFlySecurityManager (Elytron 1.5.4.Final). WildFlySecurityManager uses sun.misc.Unsafe. Unsafe works just with adding of {{--add-modules=jdk.unsupported}} to JConsole: {code:diff} --- a/jconsole.sh +++ b/jconsole.sh @@ -79,4 +79,4 @@ CLASSPATH=$CLASSPATH:./bin/client/jboss-cli-client.jar echo CLASSPATH $CLASSPATH cd "$JBOSS_HOME" -$JAVA_HOME/bin/jconsole -J-Djava.class.path="$CLASSPATH" "$@" +$JAVA_HOME/bin/jconsole -J--add-modules=jdk.unsupported -J-Djava.class.path="$CLASSPATH" "$@" \ No newline at end of file {code} But "jdk.unsupported" module is not a correct fix. *Logs:* {noformat} Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError: sun/misc/Unsafe at org.wildfly.security.manager.WildFlySecurityManager.<clinit>(WildFlySecurityManager.java:122) at org.jboss.as.cli.CommandContextFactory.getInstance(CommandContextFactory.java:41) at org.jboss.as.cli.gui.ConnectDialog$2.actionPerformed(ConnectDialog.java:182) at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967) at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308) at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405) at java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) at java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279) at java.desktop/java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297) at java.desktop/java.awt.Component.processMouseEvent(Component.java:6631) at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342) at java.desktop/java.awt.Component.processEvent(Component.java:6396) at java.desktop/java.awt.Container.processEvent(Container.java:2263) at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840) at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918) at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547) at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307) at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) Caused by: java.lang.ClassNotFoundException: sun.misc.Unsafe at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ... 39 more {noformat} *cc:* [~kabirkhan], [~jamezp], [~darranl], [~mchoma], [~msvehla], [~okotek], [~rsvoboda] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1654) Convert build to create multi-release jar built on Java 9

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1654?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1654: ---------------------------------- Description: The earliest version this jar needs to be usable on is Java 8. > Convert build to create multi-release jar built on Java 9 > --------------------------------------------------------- > > Key: ELY-1654 > URL: https://issues.jboss.org/browse/ELY-1654 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Fix For: 1.6.1.CR1 > > > The earliest version this jar needs to be usable on is Java 8. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4055) Activate jdk.unsupported module on modular JDK by default

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4055?page=com.atlassian.jira.plugi... ] Jean-Francois Denise edited comment on WFCORE-4055 at 8/22/18 6:22 AM: ----------------------------------------------------------------------- Are you experiencing the issue on JDK11 in all cases? My investigations on JDK 11 show that the issue only shows up in the context of jconsole plugins (modular context). jdk.unsupported contained classes are resolved when running with JDK 11 and accessed from the classpath. was (Author: jdenise): Are you experiencing the issue on JDK11 in all cases? My investigations on JDK 11 show that the issue only shows up in the context of jconsole plugins. jdk.unsupported contained classes are resolved when running with JDK 11. > Activate jdk.unsupported module on modular JDK by default > --------------------------------------------------------- > > Key: WFCORE-4055 > URL: https://issues.jboss.org/browse/WFCORE-4055 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security, Server, Test Suite > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 6.0.0.CR3 > > > WildFlySecurityManager uses sun.misc.Unsafe. > Unsafe works only with jdk.unsupported module enabled. > jdk.unsupported is not resolved by default so we need to activate it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1657) Ensure whole project buildable on JDK 11

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1657: ------------------------------------- Summary: Ensure whole project buildable on JDK 11 Key: ELY-1657 URL: https://issues.jboss.org/browse/ELY-1657 Project: WildFly Elytron Issue Type: Task Components: Build Reporter: Darran Lofthouse Fix For: 1.6.1.CR1 This may be blocked on when we can remove support for Java 8 - although we could consider a build with Java 11 to exclude the Java 8 classes if that is possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1656) Ensure testsuite alone can be built and executed on Java 11

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1656: ------------------------------------- Summary: Ensure testsuite alone can be built and executed on Java 11 Key: ELY-1656 URL: https://issues.jboss.org/browse/ELY-1656 Project: WildFly Elytron Issue Type: Task Components: Build, Testsuite Reporter: Darran Lofthouse Fix For: 1.6.1.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1655) Provide Java 9 Implementation avoiding sun.reflect and sun.misc classes

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1655: ------------------------------------- Summary: Provide Java 9 Implementation avoiding sun.reflect and sun.misc classes Key: ELY-1655 URL: https://issues.jboss.org/browse/ELY-1655 Project: WildFly Elytron Issue Type: Task Components: Security Manager Reporter: Darran Lofthouse Fix For: 1.6.1.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018