June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3866) CLI pom has an unneeded dependency on MSC, causing MSC to get included in the shaded jboss-cli-client.jar

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3866?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3866: -------------------------------- Fix Version/s: 6.0.0.Alpha2 (was: 6.0.0.Alpha1) > CLI pom has an unneeded dependency on MSC, causing MSC to get included in the shaded jboss-cli-client.jar > ---------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3866 > URL: https://issues.jboss.org/browse/WFCORE-3866 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 6.0.0.Alpha2 > > > The cli/pom.xml has this in the "dependencies" section: > {code} >  > <dependency> > <groupId>org.jboss.msc</groupId> > <artifactId>jboss-msc</artifactId> > </dependency> > {code} > But that's out of date. The analysis for WFCORE-3765 showed that any need for MSC is only on the "embedded server" side, loaded by JBoss Modules, and is not on the embedding app side, needed on the classpath. There used to be use of MSC on the embedding app side but that was removed long ago. > Fixing this will reduce the size of the jboss-cli-client.jar. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3858) Add model version 4.0.0 to the Elytron Subsystem version.

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3858?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3858: -------------------------------- Fix Version/s: 6.0.0.Alpha2 (was: 6.0.0.Alpha1) > Add model version 4.0.0 to the Elytron Subsystem version. > --------------------------------------------------------- > > Key: WFCORE-3858 > URL: https://issues.jboss.org/browse/WFCORE-3858 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 6.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3806) Eliminate code that was using transitive MSC dependencies

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3806?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3806: -------------------------------- Fix Version/s: 6.0.0.Alpha2 (was: 6.0.0.Alpha1) > Eliminate code that was using transitive MSC dependencies > --------------------------------------------------------- > > Key: WFCORE-3806 > URL: https://issues.jboss.org/browse/WFCORE-3806 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 6.0.0.Alpha2 > > > Prior MSC 1.2.8 stability monitors were reporting problems if > some transitive dependency wasn't available. This has changed > since MSC 1.2.8. There is no notion of transitive > dependencies in JBoss MSC anymore. If stability monitor detects > a problem it is always immediate dependency of monitored controller. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2475) Upgrade Jackson dependencies.

by Maciej Swiderski (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2475?page=com.atlassian.jira.plugi... ] Maciej Swiderski commented on DROOLS-2475: ------------------------------------------ see discussion in this jira https://issues.jboss.org/browse/JBPM-7288 > Upgrade Jackson dependencies. > ----------------------------- > > Key: DROOLS-2475 > URL: https://issues.jboss.org/browse/DROOLS-2475 > Project: Drools > Issue Type: Bug > Reporter: Petar Tahchiev > Assignee: Maciej Swiderski > Priority: Critical > > Hello, > I'm not sure this is the right place to report this, but I couldn't find a better one. In my project I'm using: > {code} > <dependency> > <groupId>org.kie.server</groupId> > <artifactId>kie-server-jms</artifactId> > <version>7.7.0.Final</version> > </dependency> > {code} > and I believe you guys are using jackson version 2.8.9: > https://github.com/kiegroup/kie-soup/blob/master/pom.xml#L56 > which is already 1 year old. In my app some third-party dependencies are bringing jackson 2.9.5 and because of this mismatch I get the following exception when I run my app: > {code} > Caused by: java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig.with(Lcom/fasterxml/jackson/databind/AnnotationIntrospector;)Lcom/fasterxml/jackson/databind/SerializationConfig; > at org.kie.server.api.marshalling.json.JSONMarshaller.configureMarshaller(JSONMarshaller.java:153) > at org.kie.server.api.marshalling.json.JSONMarshaller.<init>(JSONMarshaller.java:128) > at org.kie.server.api.marshalling.BaseMarshallerBuilder.build(BaseMarshallerBuilder.java:43) > at org.kie.server.api.marshalling.MarshallerFactory.getMarshaller(MarshallerFactory.java:52) > at org.kie.server.client.impl.AbstractKieServicesClientImpl.<init>(AbstractKieServicesClientImpl.java:83) > at org.kie.server.client.impl.KieServicesClientImpl.<init>(KieServicesClientImpl.java:71) > at org.kie.server.client.KieServicesFactory.newKieServicesClient(KieServicesFactory.java:101) > at com.nemesis.platform.module.ruleservices.config.RuleServicesModuleAutoConfiguration.defaultKieServicesClient(RuleServicesModuleAutoConfiguration.java:160) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3915) Fix test suite modules parent relation

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFCORE-3915: ----------------------------------- Summary: Fix test suite modules parent relation Key: WFCORE-3915 URL: https://issues.jboss.org/browse/WFCORE-3915 Project: WildFly Core Issue Type: Bug Components: Build System Affects Versions: 5.0.0.Final Reporter: Jeff Mesnil Assignee: Jeff Mesnil 3 modules inside Core test suite uses wildfly-core-parent as their parent instead of wildfly-core-testsuite: * shared * test-runner * vault-test-feature-pack One consequence is that when Core is released, these 3 artifacts are included in the release while they should not be (no other test suite modules is part of a release) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10526) AuthenticationTestCase requires unnecessary set of permissions

by Jan Kalina (JIRA)

Jan Kalina created WFLY-10526: --------------------------------- Summary: AuthenticationTestCase requires unnecessary set of permissions Key: WFLY-10526 URL: https://issues.jboss.org/browse/WFLY-10526 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 13.0.0.Final Reporter: Jan Kalina Assignee: Jan Kalina Priority: Minor AuthenticationTestCase in basic testsuite can be simply modified to require much smaller set of deployment permissions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10525) Upgrade to Galleon 1.0.1.Final and Galleon Plugins 1.0.1.Final

by Yeray Borges (JIRA)

Yeray Borges created WFLY-10525: ----------------------------------- Summary: Upgrade to Galleon 1.0.1.Final and Galleon Plugins 1.0.1.Final Key: WFLY-10525 URL: https://issues.jboss.org/browse/WFLY-10525 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Yeray Borges Assignee: Yeray Borges Upgrade releases of Galleon and WildFly Galleon plugins in wildfly. This upgrade will allow creating the correct file permissions defined by wildfly-core galleon-pack -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9364) Closing an EJBClientContext sometimes hangs causing high CPU usage

by crina boitor (JIRA)

[ https://issues.jboss.org/browse/WFLY-9364?page=com.atlassian.jira.plugin.... ] crina boitor commented on WFLY-9364: ------------------------------------ Hi, we also encountered a similar issue with Wildfly 10 and we are currently considering upgrading to XNIO 3.5.x. I wanted to know if the upgrade fixed the problem in your case. Thank you, Crina > Closing an EJBClientContext sometimes hangs causing high CPU usage > ------------------------------------------------------------------ > > Key: WFLY-9364 > URL: https://issues.jboss.org/browse/WFLY-9364 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.1.0.Final > Environment: Server: > - OS: > Red Hat Enterprise Linux Server release 7.2 (Maipo) > - JDK: > java version "1.8.0_144" > Java(TM) SE Runtime Environment (build 1.8.0_144-b01) > Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode) > - WildFly: > WildFly 10.1.0.Final > Client: > - OS: > Red Hat Enterprise Linux Server release 7.2 (Maipo) > - JDK: > java version "1.8.0_144" > Java(TM) SE Runtime Environment (build 1.8.0_144-b01) > Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode) > Reporter: Marius Tantareanu > Assignee: Jason Greene > Attachments: echo-client.zip, output_rhel7.txt, output_win10.txt, simple-ear.ear, td_rhel7.txt, td_win10.txt > > > EJBClientContext.close() sometimes hangs and causes high CPU usage. We have a WildFly client that uses EJB client API to invoke some EJBs remotely. > Basically the client executes the following actions in a loop: > - setup an EJBClientContext programatically > - create a JNDI context > - lookup an EJB and invoke some operations on it > - close the JNDI context and the EJBClientContext > After the client runs a few hundreds iterations (the actual number of iterations varies quite a lot from one run to another) it blocks while invoking EJBClientContext.close(). Also one XNIO thread in the client app is constantly consuming one CPU core (full thread dump from the client app is attached). I was only able to reproduce this when connecting over TLS (port 8443). When using the unsecure port (8080) the problem does not reproduce (or it reproduces much less frequently and I didn't run enough iterations to catch it). > Once the client app enters this state, top shows something like (notice the CPU usage of thread 12512): > >top -H -p 6463 > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 12512 root 20 0 11.527g 222680 13788 R 99.3 0.7 141:10.99 java > 6466 root 20 0 11.527g 222680 13788 S 0.3 0.7 0:07.05 java > 6467 root 20 0 11.527g 222680 13788 S 0.3 0.7 0:06.97 java > 6477 root 20 0 11.527g 222680 13788 S 0.3 0.7 0:04.24 java > 6463 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 6464 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:03.46 java > 6465 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:06.94 java > 6468 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:07.02 java > 6469 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:16.42 java > 6470 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.01 java > 6471 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.01 java > 6472 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 6473 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:06.87 java > 6474 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:06.70 java > 6475 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:03.09 java > 6476 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 12513 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 12514 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 12515 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 12516 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 12517 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 12518 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 12519 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 12520 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 12523 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 12524 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > 12597 root 20 0 11.527g 222680 13788 S 0.0 0.7 0:00.00 java > The thread that causes the CPU usage is the following: > "Remoting "config-based-ejb-client-endpoint" I/O-1" #6025 daemon prio=5 os_prio=0 tid=0x00007f2f709d3000 nid=0x30e0 runnable [0x00007f2e7f9be000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86) > - locked <0x00000005cc1844e8> (a sun.nio.ch.Util$3) > - locked <0x00000005cc19f258> (a java.util.Collections$UnmodifiableSet) > - locked <0x00000005cc184468> (a sun.nio.ch.EPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:515) > The client app main thread is blocked as below: > "main" #1 prio=5 os_prio=0 tid=0x00007f2f70008800 nid=0x1940 in Object.wait() [0x00007f2f76350000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.Object.wait(Object.java:502) > at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:190) > - locked <0x00000005cc18de48> (a java.lang.Object) > at org.jboss.ejb.client.remoting.ConnectionPool.safeClose(ConnectionPool.java:177) > at org.jboss.ejb.client.remoting.ConnectionPool.release(ConnectionPool.java:104) > - locked <0x00000005cbd369e0> (a org.jboss.ejb.client.remoting.ConnectionPool) > at org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection.close(ConnectionPool.java:198) > at org.jboss.ejb.client.remoting.RemotingConnectionManager.safeClose(RemotingConnectionManager.java:65) > - locked <0x00000005cc1a6840> (a java.util.Collections$SynchronizedRandomAccessList) > at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector$ContextCloseListener.contextClosed(ConfigBasedEJBClientContextSelector.java:220) > at org.jboss.ejb.client.EJBClientContext.close(EJBClientContext.java:1305) > - locked <0x00000005cc1a6888> (a org.jboss.ejb.client.EJBClientContext) > at com.microfocus.echoclient.EchoClient.disconnect(EchoClient.java:66) > at com.microfocus.echoclient.EchoClient.connectDisconnect(EchoClient.java:54) > at com.microfocus.echoclient.EchoClient.main(EchoClient.java:36) > The problem also reproduces on Windows (full thread dump of the client app is attached). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-263) Kiali Istio Checker Job may not be working

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/SWSQE-263?page=com.atlassian.jira.plugin.... ] Sunil kondkar commented on SWSQE-263: ------------------------------------- Pushed a fix for Kiali URL and if condition check. > Kiali Istio Checker Job may not be working > ------------------------------------------- > > Key: SWSQE-263 > URL: https://issues.jboss.org/browse/SWSQE-263 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Sunil kondkar > > I think Kiali Istio Checker is not running fine > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Istio-Chec... > Running > Current istio-ca pod status : Running > scripts/kiali/testscript.sh: line 55: [: too many arguments -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3913) HTTPSchemeServiceAuthModule contructor is not defined

by Hisanobu Okuda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3913?page=com.atlassian.jira.plugi... ] Hisanobu Okuda commented on WFCORE-3913: ---------------------------------------- As [~dlofthouse] suggested, adding the login-module-stack-ref, it works fine! {code} <security-domain name="jaspi" cache-type="default"> <authentication-jaspi> <login-module-stack name="dummy"> <login-module code="org.jboss.security.auth.spi.SimpleServerLoginModule" flag="optional"/> </login-module-stack> <auth-module code="org.wildfly.extension.undertow.security.jaspi.modules.HTTPSchemeServerAuthModule" login-module-stack-ref="dummy" /> </authentication-jaspi> </security-domain> {code} Please close this JIRA. > HTTPSchemeServiceAuthModule contructor is not defined > ----------------------------------------------------- > > Key: WFCORE-3913 > URL: https://issues.jboss.org/browse/WFCORE-3913 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.10.Final > Environment: - EAP7.1.0 > Reporter: Hisanobu Okuda > Assignee: Darran Lofthouse > Attachments: test.war > > > JASPI does not work, since HTTPSchemeServiceAuthModule contructor is not defined. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 June 2018