February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9798) Undertow filter rewrite configuration error

by 구용 이 (JIRA)

구용 이 created WFLY-9798: -------------------------- Summary: Undertow filter rewrite configuration error Key: WFLY-9798 URL: https://issues.jboss.org/browse/WFLY-9798 Project: WildFly Issue Type: Bug Components: Web (Undertow) Environment: h2. Test environment 1. CentOS Linux release 7.4.1708 (Core) 2. wildfly-11.0.0.Final 3. wildfly-12.0.0.Alpha1-SNAPSHOT Reporter: 구용 이 Assignee: Stuart Douglas hi~ A URL in the form of "http://localhost/test1" should be rewritten to "http://localhost/abc/test1" h2. Configuration Undertow Subsystem <host ... <filter-ref name="rewrite-test" predicate="regex('^/test(.*)$')"/> ... <filters> <rewrite name="rewrite-test" target="/abc/test${1}.jsp" redirect="false"/> h2. Problems: server.log failure description: "WFLYCTL0211: Cannot resolve expression '/abc/test${1}.jsp'" Thank you -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-36) Support resolution of ${project.groupId} in the server-provisioning.xml file

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-36?page=com.atlassian.jira.plugin... ] Stuart Douglas resolved WFBUILD-36. ----------------------------------- Resolution: Done I believe the TODO was to try and find some way to auto-magically add all the properties that maven supports out of the box, however there does not appear to be any automatic way to do this. > Support resolution of ${project.groupId} in the server-provisioning.xml file > ---------------------------------------------------------------------------- > > Key: WFBUILD-36 > URL: https://issues.jboss.org/browse/WFBUILD-36 > Project: WildFly Build Tools > Issue Type: Enhancement > Reporter: Brian Stansberry > Assignee: Stuart Douglas > Priority: Minor > Fix For: 1.2.9.Final > > > The provisioning plugin allows parameterization of a feature pack's version via ```${project.version}``` but parameterizing the groupId via ```${project.groupId}``` isn't supported. My guess is something like this for groupId would do the trick: > https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning-m... > This would make it easier to use the same provisioning configs in different branches that have different maven groupIds. > I see the TODO about the project.version thing I linked above, and I understand I'm asking to expand a concept that the TODO indicates is suspect. So I won't be offended if this is rejected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-36) Support resolution of ${project.groupId} in the server-provisioning.xml file

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-36?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFBUILD-36: ---------------------------------- Fix Version/s: 1.2.9.Final > Support resolution of ${project.groupId} in the server-provisioning.xml file > ---------------------------------------------------------------------------- > > Key: WFBUILD-36 > URL: https://issues.jboss.org/browse/WFBUILD-36 > Project: WildFly Build Tools > Issue Type: Enhancement > Reporter: Brian Stansberry > Assignee: Stuart Douglas > Priority: Minor > Fix For: 1.2.9.Final > > > The provisioning plugin allows parameterization of a feature pack's version via ```${project.version}``` but parameterizing the groupId via ```${project.groupId}``` isn't supported. My guess is something like this for groupId would do the trick: > https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning-m... > This would make it easier to use the same provisioning configs in different branches that have different maven groupIds. > I see the TODO about the project.version thing I linked above, and I understand I'm asking to expand a concept that the TODO indicates is suspect. So I won't be offended if this is rejected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9796) Update Eclipselink module to public

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9796?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-9796: ---------------------------------------- [~smarlow] The org.apache.openjpa module has the same problem. > Update Eclipselink module to public > ----------------------------------- > > Key: WFLY-9796 > URL: https://issues.jboss.org/browse/WFLY-9796 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3595) SuspendOnSoftKillTestCase can fail intermittently

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3595?page=com.atlassian.jira.plugi... ] Stuart Douglas updated WFCORE-3595: ----------------------------------- Description: The issue is that TestUndertowService is designed for testing suspend/resume rather than an actual graceful shutdown. Because it attempts to perform a dispatch() and queue a task rather than just immediately setting a 503 response it is possible that this request will fail with a 500 response if the XNIO executor is in the process of shutting down. It would be better if this test checked for a 503 before the skip-graceful request is made. > SuspendOnSoftKillTestCase can fail intermittently > ------------------------------------------------- > > Key: WFCORE-3595 > URL: https://issues.jboss.org/browse/WFCORE-3595 > Project: WildFly Core > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > The issue is that TestUndertowService is designed for testing suspend/resume rather than an actual graceful shutdown. Because it attempts to perform a dispatch() and queue a task rather than just immediately setting a 503 response it is possible that this request will fail with a 500 response if the XNIO executor is in the process of shutting down. > It would be better if this test checked for a 503 before the skip-graceful request is made. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3595) SuspendOnSoftKillTestCase can fail intermittently

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-3595: -------------------------------------- Summary: SuspendOnSoftKillTestCase can fail intermittently Key: WFCORE-3595 URL: https://issues.jboss.org/browse/WFCORE-3595 Project: WildFly Core Issue Type: Bug Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9797) When in EE7 mode Undertow should report that it is a Servlet 3.1 container

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9797: ------------------------------------ Summary: When in EE7 mode Undertow should report that it is a Servlet 3.1 container Key: WFLY-9797 URL: https://issues.jboss.org/browse/WFLY-9797 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3594) Reload is racey with regard to reading the process state, which can cause intermittent test failures

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-3594: -------------------------------------- Summary: Reload is racey with regard to reading the process state, which can cause intermittent test failures Key: WFCORE-3594 URL: https://issues.jboss.org/browse/WFCORE-3594 Project: WildFly Core Issue Type: Bug Reporter: Stuart Douglas Assignee: Stuart Douglas This can cause failures as seen at: https://ci.wildfly.org/viewLog.html?buildId=88799&tab=buildResultsDiv&bui... The issue is that the reload operation offloads the actual reload operation to an executor, which means that it is possible to execute :reload operation followed immediately by reading the 'server-state' attribute and see a state of 'running', even though the server has not reloaded yet. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2210) Drools 7.3.0 serialization null pointer exceptions with sliding windows

by Manjunath S Paramesan (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2210?page=com.atlassian.jira.plugi... ] Manjunath S Paramesan commented on DROOLS-2210: ----------------------------------------------- [~tirelli] - I can confirm this issue occurs with 7.5.0.Final as well > Drools 7.3.0 serialization null pointer exceptions with sliding windows > ----------------------------------------------------------------------- > > Key: DROOLS-2210 > URL: https://issues.jboss.org/browse/DROOLS-2210 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.3.0.Final > Reporter: Manjunath S Paramesan > Assignee: Mario Fusco > Priority: Critical > > We have a fairly large rule-base with temporal reasoning and sliding windows. > While serializing the drools session we observe random null pointer exceptions as see below: > Exception in thread "pool-92-thread-98" java.lang.NullPointerException > at org.drools.core.rule.SlidingTimeWindow$BehaviorJobContextTimerOutputMarshaller.serialize(SlidingTimeWindow.java:323) > at org.drools.core.marshalling.impl.ProtobufOutputMarshaller.writeTimers(ProtobufOutputMarshaller.java:880) > at org.drools.core.marshalling.impl.ProtobufOutputMarshaller.serializeSession(ProtobufOutputMarshaller.java:210) > at org.drools.core.marshalling.impl.ProtobufOutputMarshaller.writeSession(ProtobufOutputMarshaller.java:118) > at org.drools.core.marshalling.impl.ProtobufMarshaller.marshall(ProtobufMarshaller.java:162) > at org.drools.core.marshalling.impl.ProtobufMarshaller.marshall(ProtobufMarshaller.java:146) > at com.mlnms.common.fmwk.drools.impl.DroolsClientImpl.backupKieSession(DroolsClientImpl.java:743) > at com.mlnms.common.fmwk.drools.impl.DroolsClientImpl.lambda$processStatefulEvents$0(DroolsClientImpl.java:506) > at java.lang.Thread.run(Thread.java:745) > 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) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3593) Intermittent failure in EarJBossDeploymentStructureTestCase in WF full

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-3593: -------------------------------------- Summary: Intermittent failure in EarJBossDeploymentStructureTestCase in WF full Key: WFCORE-3593 URL: https://issues.jboss.org/browse/WFCORE-3593 Project: WildFly Core Issue Type: Bug Components: Server Reporter: Stuart Douglas Assignee: Stuart Douglas Even though the bug manifests in full the problem is in core. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 February 2018