November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-916) Upgrade wagon-provider-api from 1.0 to at least 2.6, so it's since with the rest of the maven/aether dependencies

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-916?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer commented on DROOLS-916: ----------------------------------------------- The version of org.apache.maven.wagon:wagon-provider is declared in jboss-ip-bom as https://github.com/jboss-integration/jboss-integration-platform-bom/blob/... The only part where it is appears it is: https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/kie-... Thus as exclusion. The only artifacts that is ovwerwritten is jackrabbit https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/pom...., > Upgrade wagon-provider-api from 1.0 to at least 2.6, so it's since with the rest of the maven/aether dependencies > ----------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-916 > URL: https://issues.jboss.org/browse/DROOLS-916 > Project: Drools > Issue Type: Task > Affects Versions: 6.3.0.CR2 > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Minor > > This downgrade in our dependency looks pretty bad. > {code} > [INFO] | | +- org.apache.maven.wagon:wagon-provider-api:jar:1.0:test (version managed from 2.6) > [INFO] | | +- org.apache.maven.wagon:wagon-file:jar:2.6:test > [INFO] | | | +- commons-lang:commons-lang:jar:2.6:test > {code} > It's probably because the ip-bom overwrites the wagon-provider-api version to 1.0 (while transitively it's 2.6). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4850) ManagementClient.isServerInRunningState fails when server is stopped

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4850?page=com.atlassian.jira.plugin.... ] James Perkins resolved WFLY-4850. --------------------------------- Resolution: Done > ManagementClient.isServerInRunningState fails when server is stopped > -------------------------------------------------------------------- > > Key: WFLY-4850 > URL: https://issues.jboss.org/browse/WFLY-4850 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondřej Chaloupka > Assignee: James Perkins > > Scenario: server is stopped (killed), working with arquillian to check if server is started or not > Current implementation of the {{ManagementClient.isServerInRunningState}} catches only {{IOException}} (see [1]) and in such case false is returned. Otherwise exception is propagated upwards. > That's a problem in case that assertions are enabled - which is true statement for wildfly testsuite (see pom.xml, surefire configuration and {{<enableAssertions>true</enableAssertions>}}). As state of the server is checked with assertions as well [2] then test fails on such assertion instead of getting false as server is stopped. > In comparision with arquillian client for jboss-eap there is caught {{Throwable}} and returned false [3] which seems to me more correct. > Could you, please, forwardport arquillian client behaviour from JBoss EAP to WildFly? > [1] https://github.com/wildfly/wildfly-arquillian/blob/master/common/src/main... > [2] https://github.com/wildfly/wildfly-core/blob/master/protocol/src/main/jav... > [3] https://github.com/jbossas/jboss-eap/blob/6.x/arquillian/common/src/main/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-333) Allow peer identity to be associated with security identity

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-333?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-333. ----------------------------- Fix Version/s: 1.1.0.Beta2 Resolution: Done > Allow peer identity to be associated with security identity > ----------------------------------------------------------- > > Key: ELY-333 > URL: https://issues.jboss.org/browse/ELY-333 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-338) Mechanism realm awareness

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-338?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-338. ----------------------------- Fix Version/s: 1.1.0.Beta2 Resolution: Done > Mechanism realm awareness > ------------------------- > > Key: ELY-338 > URL: https://issues.jboss.org/browse/ELY-338 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI, Authentication Mechanisms > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Critical > Fix For: 1.1.0.Beta2 > > > Add support for mechanisms that allow selection from a set of realms. Provide reasonable fallback behavior when a mechanism does not allow realm selection, or for when the presented realm name is informational only. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-363) Add wrapping password key store to client

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-363?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-363. ----------------------------- Fix Version/s: 1.1.0.Beta2 Resolution: Done > Add wrapping password key store to client > ----------------------------------------- > > Key: ELY-363 > URL: https://issues.jboss.org/browse/ELY-363 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta2 > > > Add the capability to add an XML attribute which indicates that a key store in the configuration should be wrapped with a {{org.wildfly.security.keystore.WrappingPasswordKeyStore}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4939) WFLYEJB0467: The request was rejected as the container is suspended during server shutdown

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFLY-4939?page=com.atlassian.jira.plugin.... ] Romain Pelisse reassigned WFLY-4939: ------------------------------------ Assignee: Romain Pelisse (was: Radoslav Husar) > WFLYEJB0467: The request was rejected as the container is suspended during server shutdown > ------------------------------------------------------------------------------------------ > > Key: WFLY-4939 > URL: https://issues.jboss.org/browse/WFLY-4939 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 10.0.0.Alpha6, 10.0.0.Beta1 > Reporter: Michal Vinkler > Assignee: Romain Pelisse > > Seen in our failover tests (scenario shutdown) for remote stateful EJBs > Setup: 4 node cluster, one node at time is shutdown, while standalone clients keep calling the application. > When server is shutting down (via cli command ":shutdown"), it logs the following error message for each client invocation during suspend phase: > {code} > [JBossINF] [0m[0m12:36:39,319 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0211: Suspending server > [JBossINF] [0m[0m12:36:39,323 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested. > [JBossINF] [0m[31m12:36:39,346 ERROR [org.jboss.as.ejb3.invocation] (EJB default - 7) WFLYEJB0034: EJB Invocation failed on component RemoteStatefulSBImpl for method public abstract int org.jboss.test.clusterbench.common.ejb.CommonStatefulSB.getSerialAndIncrement(): org.jboss.as.ejb3.component.EJBComponentUnavailableException: WFLYEJB0467: The request was rejected as the container is suspended > [JBossINF] at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:50) > [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > [JBossINF] at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > [JBossINF] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > [JBossINF] at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > [JBossINF] at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > [JBossINF] at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > [JBossINF] at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > [JBossINF] at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > [JBossINF] at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > [JBossINF] at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > [JBossINF] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > [JBossINF] at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:331) > [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:69) > [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:202) > [JBossINF] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266) > [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [JBossINF] at java.lang.Thread.run(Thread.java:745) > [JBossINF] at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} > Server log: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5688) mod_cluster subsystem remains silent if connector set to http

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5688?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5688: --------------------------------- Labels: ux (was: ) > mod_cluster subsystem remains silent if connector set to http > ------------------------------------------------------------- > > Key: WFLY-5688 > URL: https://issues.jboss.org/browse/WFLY-5688 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 10.0.0.CR4 > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > Labels: ux > > If one sets mod_cluster subsystem {{connector="http"}} there is nothing in the log about any mod_cluster subsystem being initialized, no warning, nothing. It appears to be dead silent even with log level DEBUG. > When switched back to {{connector="ajp"}}, there are the well known comforting messages: > {noformat} > INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000001: Initializing mod_cluster version 1.3.1.Final > INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364 > {noformat} > Weird. Any obvious misconfiguration or explanation? The config is the default standalone-ha.xml otherwise. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5688) mod_cluster subsystem remains silent if connector set to http

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5688?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5688: --------------------------------- Issue Type: Feature Request (was: Bug) > mod_cluster subsystem remains silent if connector set to http > ------------------------------------------------------------- > > Key: WFLY-5688 > URL: https://issues.jboss.org/browse/WFLY-5688 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 10.0.0.CR4 > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > > If one sets mod_cluster subsystem {{connector="http"}} there is nothing in the log about any mod_cluster subsystem being initialized, no warning, nothing. It appears to be dead silent even with log level DEBUG. > When switched back to {{connector="ajp"}}, there are the well known comforting messages: > {noformat} > INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000001: Initializing mod_cluster version 1.3.1.Final > INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364 > {noformat} > Weird. Any obvious misconfiguration or explanation? The config is the default standalone-ha.xml otherwise. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5688) mod_cluster subsystem remains silent if connector set to http

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5688?page=com.atlassian.jira.plugin.... ] Radoslav Husar moved MODCLUSTER-459 to WFLY-5688: ------------------------------------------------- Project: WildFly (was: mod_cluster) Key: WFLY-5688 (was: MODCLUSTER-459) Affects Version/s: 10.0.0.CR4 (was: 1.3.1.Final) Fix Version/s: (was: 1.3.2.Alpha1) > mod_cluster subsystem remains silent if connector set to http > ------------------------------------------------------------- > > Key: WFLY-5688 > URL: https://issues.jboss.org/browse/WFLY-5688 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.CR4 > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > > If one sets mod_cluster subsystem {{connector="http"}} there is nothing in the log about any mod_cluster subsystem being initialized, no warning, nothing. It appears to be dead silent even with log level DEBUG. > When switched back to {{connector="ajp"}}, there are the well known comforting messages: > {noformat} > INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000001: Initializing mod_cluster version 1.3.1.Final > INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364 > {noformat} > Weird. Any obvious misconfiguration or explanation? The config is the default standalone-ha.xml otherwise. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5688) mod_cluster subsystem remains silent if connector set to http

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5688?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-5688: -------------------------------------- Moving to WFLY: this is not a modcluster project issue but integration. > mod_cluster subsystem remains silent if connector set to http > ------------------------------------------------------------- > > Key: WFLY-5688 > URL: https://issues.jboss.org/browse/WFLY-5688 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.CR4 > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > > If one sets mod_cluster subsystem {{connector="http"}} there is nothing in the log about any mod_cluster subsystem being initialized, no warning, nothing. It appears to be dead silent even with log level DEBUG. > When switched back to {{connector="ajp"}}, there are the well known comforting messages: > {noformat} > INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000001: Initializing mod_cluster version 1.3.1.Final > INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364 > {noformat} > Weird. Any obvious misconfiguration or explanation? The config is the default standalone-ha.xml otherwise. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 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 November 2015