January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7903) Requests which are being proxied are not logged in access log

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7903?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-8326 to WFLY-7903: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7903 (was: JBEAP-8326) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Web (Undertow)) Affects Version/s: (was: 7.1.0.DR10) > Requests which are being proxied are not logged in access log > ------------------------------------------------------------- > > Key: WFLY-7903 > URL: https://issues.jboss.org/browse/WFLY-7903 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > If I defined undertow as proxy (with mod_cluster filter), and enable access-log then for requests against proxy which are at the end handled by one of the workers are not logged in access log. > There are logged only requests which are being directly handled by balancer (and not the one balanced to workers) > I believe that with enabled access log on balancer all requests should be logged. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7902) Credential Store integration into mail subsystem

by Peter Skopek (JIRA)

Peter Skopek created WFLY-7902: ---------------------------------- Summary: Credential Store integration into mail subsystem Key: WFLY-7902 URL: https://issues.jboss.org/browse/WFLY-7902 Project: WildFly Issue Type: Sub-task Reporter: Peter Skopek Assignee: Peter Skopek Credential Store integration into mail subsystem -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7901) Credential Store integration into wildfly subsystems which use password attribute

by Peter Skopek (JIRA)

Peter Skopek created WFLY-7901: ---------------------------------- Summary: Credential Store integration into wildfly subsystems which use password attribute Key: WFLY-7901 URL: https://issues.jboss.org/browse/WFLY-7901 Project: WildFly Issue Type: Task Reporter: Peter Skopek Assignee: Peter Skopek Tracking task -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4487) Unable to inject Web Service Context into CDI Interceptor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4487?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4487: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1210328|https://bugzilla.redhat.com/show_bug.cgi?id=1210328] from VERIFIED to CLOSED > Unable to inject Web Service Context into CDI Interceptor > --------------------------------------------------------- > > Key: WFLY-4487 > URL: https://issues.jboss.org/browse/WFLY-4487 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 9.0.0.Alpha1 > Reporter: Mustafa Musaji > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > Attachments: cdi-interceptors.zip > > > CDI Interceptor cannot inject Web Service context. > When trying to inject WebServiceContext in CDI Interceptor using @Resource annotation but it fails with: NameNotFoundException: env/org.example.MyInterceptor/webServiceContext -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1260) Allow System Property to override default First In First Out (FIFO) pooling behavior

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1260?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1260: ------------------------------------------------ Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1210571|https://bugzilla.redhat.com/show_bug.cgi?id=1210571] from VERIFIED to CLOSED > Allow System Property to override default First In First Out (FIFO) pooling behavior > ------------------------------------------------------------------------------------ > > Key: JBJCA-1260 > URL: https://issues.jboss.org/browse/JBJCA-1260 > Project: IronJacamar > Issue Type: Support Patch > Components: Core > Affects Versions: 1.0.32.Final > Reporter: Johnathon Lee > Assignee: Johnathon Lee > Fix For: 1.0.32.Final > > > Introduce a system property "filo-pool-behavior" to override (revert) the changes introduced by JBJCA-1005. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1730) Singleton service is not correctly being set in WILDFLY

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1730?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1730: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1367793|https://bugzilla.redhat.com/show_bug.cgi?id=1367793] from VERIFIED to CLOSED > Singleton service is not correctly being set in WILDFLY > ------------------------------------------------------- > > Key: WFCORE-1730 > URL: https://issues.jboss.org/browse/WFCORE-1730 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 3.0.0.Alpha5 > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > WILDFLY doesn't call ServiceLoader (META-INF/services/org.jboss.msc.service.ServiceActivator) when it is deployed in EAR/lib. The SingletonService (not a singleton EJB) is activated in the ServiceLoader so the SingletonService hasn't been activated from the first. It works as expected when deployed as an EJB (not in EAR/lib). > When the ServiceLoader is called, a message of "HATimerService will be installed!" is logged and the SingletonService will be activated. > $ fgrep -e HATimerService -e '[org.jboss.as.clustering.singleton]' domain/servers/server-one/log/server.log > 12:14:52,373 INFO [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATimerServiceActivator] (MSC service thread 1-7) HATimerService will be installed! > 12:14:56,251 INFO [org.jboss.as.clustering.singleton] (ServerService Thread Pool -- 54) JBAS010342: master:server-one/singleton elected as the singleton provider of the jboss.quickstart.ha.singleton.timer service > 12:14:56,251 INFO [org.jboss.as.clustering.singleton] (ServerService Thread Pool -- 54) JBAS010340: This node will now operate as the singleton provider of the jboss.quickstart.ha.singleton.timer service > 12:14:56,268 INFO [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATimerService] (MSC service thread 1-8) Start HASingleton timer service 'org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATim > erService' > 12:14:56,873 INFO [org.jboss.as.clustering.singleton] (notification-thread-0) JBAS010342: master:server-one/singleton elected as the singleton provider of the jboss.quickstart.ha.singleton.timer service -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1198) CLI does not resolve multiple properties if one property is undefined

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1198?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1198: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1289316|https://bugzilla.redhat.com/show_bug.cgi?id=1289316] from VERIFIED to CLOSED > CLI does not resolve multiple properties if one property is undefined > --------------------------------------------------------------------- > > Key: WFCORE-1198 > URL: https://issues.jboss.org/browse/WFCORE-1198 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.4.Final > Reporter: Chao Wang > Assignee: Chao Wang > Fix For: 2.0.5.Final > > > https://bugzilla.redhat.com/show_bug.cgi?id=1289316 description: > {noformat} > Multiple property substitution is working with EAP 6.4.3+, however, if a variable amongst the multiple variables is empty or has no value, then the subsequent property in the CLI command is not substituted. > For example : > cat props.properties > ----------------------------------------- > PROFILE-NAME=TestProfile > SERVER-INSTANCE-NUMBER=TestInstance > APP-VERSION= > VAR=test > ----------------------------------------- > cat test.cli : > --------------------------------------- > /host=master/server-config=${PROFILE-NAME}${APP-VERSION}${SERVER-INSTANCE-NUMBER}${VAR}:add(auto-start=true, group="${PROFILE-NAME}${APP-VERSION}-server-group") > --------------------------------------- > and if I execute "./jboss-cli.sh --connect --file=test.cli --properties=props.properties" then I have the following in the host.xml ": > ---------- > ... > <server name="TestProfile${SERVER-INSTANCE-NUMBER}test" group="TestProfile-server-group" auto-start="true"/> > ... > ----------- > Note APP-VERSION had no value, and so the subsequent SERVER-INSTANCE-NUMBER was not properly resolved > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-581) CLI accepts operation requests with addresses ending on resource types

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-581?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-581: ------------------------------------------------ Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1169342|https://bugzilla.redhat.com/show_bug.cgi?id=1169342] from VERIFIED to CLOSED > CLI accepts operation requests with addresses ending on resource types > ---------------------------------------------------------------------- > > Key: WFCORE-581 > URL: https://issues.jboss.org/browse/WFCORE-581 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha19 > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Fix For: 1.0.0.Beta1 > > > It doesn't concern the tab-completion. But if the address is entered manually and ends on a resource type, the generated operation request will target the parent resource. > [standalone@localhost:9999 /] echo-dmr /subsystem=logging/file-handler=:remove > { > "address" => [("subsystem" => "logging")], > "operation" => "remove" > } -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6152) EJB timer scheduler log an Exception for an already canceled timer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6152?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6152: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1305960|https://bugzilla.redhat.com/show_bug.cgi?id=1305960] from VERIFIED to CLOSED > EJB timer scheduler log an Exception for an already canceled timer > ------------------------------------------------------------------ > > Key: WFLY-6152 > URL: https://issues.jboss.org/browse/WFLY-6152 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Minor > Labels: timer, timers, timerservice > Fix For: 10.1.0.CR1, 10.1.0.Final > > > If a timer is canceled inside of the @timeout method the scheduler will log an ERROR if the timer duration is longer than the intervall and an overlapping execution should be fired. > This is due to internal validatons. > This will not happen if the timer is canceled by an external process, here the scheduler is removed. > The log message is like this: > ERROR [org.jboss.as.ejb3] (EJB default - 3) WFLYEJB0164: Exception running timer task for timer [id=0bd9870b-568b-42f5-9bda-e1525c3500aa timedObjectId=ejb30-timer.ejb30-timer.SimpleTimerBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@53ba1a7f initialExpiration=Tue Feb 09 17:19:32 CET 2016 intervalDuration(in milli sec)=5000 nextExpiration=Tue Feb 09 17:19:37 CET 2016 timerState=CANCELED info=SimpleTimerInfo description=A timer started every 5 seconds] on EJB ejb30-timer.ejb30-timer.SimpleTimerBean: javax.ejb.NoSuchObjectLocalException: WFLYEJB0331: Timer was canceled > at org.jboss.as.ejb3.timerservice.TimerImpl.assertTimerState(TimerImpl.java:459) > at org.jboss.as.ejb3.timerservice.TimerImpl.isPersistent(TimerImpl.java:215) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl.shouldRun(TimerServiceImpl.java:1117) > at org.jboss.as.ejb3.timerservice.TimerTask.run(TimerTask.java:124) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl$Task$1.run(TimerServiceImpl.java:1221) > at org.wildfly.extension.requestcontroller.RequestController$QueuedTask$1.run(RequestController.java:497) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5242) Inconsistent format for IPv6 addresses in server log

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5242?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5242: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1260566|https://bugzilla.redhat.com/show_bug.cgi?id=1260566] from VERIFIED to CLOSED > Inconsistent format for IPv6 addresses in server log > ---------------------------------------------------- > > Key: WFLY-5242 > URL: https://issues.jboss.org/browse/WFLY-5242 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Lyle Wang > Assignee: Chao Wang > Priority: Minor > Fix For: 10.0.0.CR1 > > > Description of problem: > When IPv6 is used, square brackets for IPv6 addresses are missed in some of log entries. Specifically, the address format from Undertow logs is different from those "WFLYSRV" logs. > How reproducible: > Always > Steps to Reproduce: > 1. Config IPv6 (example: https://docs.jboss.org/author/display/WFLY10/Interfaces+and+ports) > 2. Start WildFly and check the log > Actual results: > ---------------------------------------- > 2015-08-31 12:51:47,812 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /0:0:0:0:0:0:0:1:8080 > ...... > 2015-08-31 12:51:48,431 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9993/management > 2015-08-31 12:51:48,432 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://[::1]:9993 > ---------------------------------------- > In Undertow logs it's like "/0:0:0:0:0:0:0:1:8080" but in WildFly server logs "http://[::1]:9993/management" > Expected results: > Consistent format should be used for IPv6 address across different components and the address is enclosed in square brackets [ ]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 January 2017