November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3098) UX: Add support for data object List

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3098: -------------------------------- Summary: UX: Add support for data object List (was: UX: Add support for map and list) > UX: Add support for data object List > ------------------------------------ > > Key: DROOLS-3098 > URL: https://issues.jboss.org/browse/DROOLS-3098 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to be able to use Data Objects that contain Lists and Maps -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11391) server.log is erased when application fails to start

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11391?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-11391: --------------------------------------- Component/s: Logging Assignee: (was: Jason Greene) This needs clear reproducer instructions that don't require figuring out how to install keycloak. Simply putting an unresolvable expression in some config attribute in our stock standalone.xml doesn't cause this, at least not with current master. > server.log is erased when application fails to start > ---------------------------------------------------- > > Key: WFLY-11391 > URL: https://issues.jboss.org/browse/WFLY-11391 > Project: WildFly > Issue Type: Bug > Components: Logging > Affects Versions: 14.0.1.Final, 13.0.0.Final > Reporter: Vlastislav Ramik > Priority: Major > > After upgrade from Wildfly 11 to 13 we face an issue described in KEYCLOAK-8821. > For us it is not a blocker but could be for wildfly, so for that case creating this one. I'm not 100% sure the cause is in the wildfly itself, I need to investigate it further before I could tell more. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4237) Update KeyStoresTestCase and CertificateAuthoritiesTestCase now that AcmeClientSpi has been updated to use POST-as-GET requests

by Farah Juma (Jira)

Farah Juma created WFCORE-4237: ---------------------------------- Summary: Update KeyStoresTestCase and CertificateAuthoritiesTestCase now that AcmeClientSpi has been updated to use POST-as-GET requests Key: WFCORE-4237 URL: https://issues.jboss.org/browse/WFCORE-4237 Project: WildFly Core Issue Type: Task Components: Test Suite Reporter: Farah Juma Assignee: Farah Juma Update {{KeyStoresTestCase}} and {{CertificateAuthoritiesTestCase}} now that {{AcmeClientSpi}} has been updated to use POST-as-GET requests (see ELY-1693). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-86) Create an exception filter

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/LOGMGR-86?page=com.atlassian.jira.plugin.... ] David Lloyd commented on LOGMGR-86: ----------------------------------- Of course this can be easily done with a custom Filter implementation. > Create an exception filter > -------------------------- > > Key: LOGMGR-86 > URL: https://issues.jboss.org/browse/LOGMGR-86 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: James Perkins > Priority: Major > > For now this is just a thought so that users can filter messages based on an exception in the stack trace. Currently it's not possible to use a regex filter as the stack trace is not used in when testing for matches and it probably shouldn't be used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-530) Fix failing tests

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-530: ------------------------------------ Summary: Fix failing tests Key: SWSQE-530 URL: https://issues.jboss.org/browse/SWSQE-530 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/python-ui-tests-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-530) Fix failing tests

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-530?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-530: -------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/110 > Fix failing tests > ----------------- > > Key: SWSQE-530 > URL: https://issues.jboss.org/browse/SWSQE-530 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/python-ui-tests-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10864) MP Health reports UP when there is port collision for port 8080

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10864?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10864: ----------------------------------------- IMHO if we do anything like this we should keep it very simple, a la our OS health probes at https://github.com/jboss-openshift/cct_module/blob/master/os-eap-probes/a..., which basically check server-state, whether there were errors at boot, whether any deployments are failed. I could also see tracking whether MSC stability could not be reached when executing a mgmt op and failing if that had occurred, as the server is in an unknowable state at that point. If the server booted cleanly and it hasn't subsequently gotten into an MSC unstable state, then if something isn't working "right" that either means a a valid configuration, but just not what the user really wanted, or the user executed a management op that failed but they said the flag that prevented rollback. The latter I see little point in trying to account for as it's a silly thing to do on a system that someone would want to monitor for health. Checking for valid but not really what was wanted configuration (oops, I forgot to add an undertow listener on 808!!) seems like endless work. Note I believe the checks I linked above would find the port collision issue as it would prevent clean boot. > MP Health reports UP when there is port collision for port 8080 > --------------------------------------------------------------- > > Key: WFLY-10864 > URL: https://issues.jboss.org/browse/WFLY-10864 > Project: WildFly > Issue Type: Bug > Components: MP Health > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > MP Health reports UP when there is port collision for port 8080. > I have simple python app to acquire port 8080 and once it runs I start WF server > {code} > import SimpleHTTPServer > import SocketServer > PORT = 8080 > Handler = SimpleHTTPServer.SimpleHTTPRequestHandler > httpd = SocketServer.TCPServer(("127.0.0.1", PORT), Handler) > print "serving at port", PORT > httpd.serve_forever() > {code} > WF reports Address already in use /127.0.0.1:8080, deployments are not deployed. > Accessing http://localhost:9990/health/ reports "outcome":"UP" > I think this is wrong and DOWN should be reported. > Spec is misleading because it says {{A producer without health check procedures installed MUST returns positive overall outcome (i.e. HTTP 200)}} but it silently assumes server started correctly. > I believe authors of the spec expected that if there is some trouble like port collision the server doesn't start, WildFly is a bit further as it allows to boot even if some services are not started properly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11243) Update WildFlyCustomJtaPlatform#locateTransactionSynchronizationRegistry to use a direct reference to the TransactionSynchronizationRegistry

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11243?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-11243: -------------------------------- Description: This addresses what is likely a performance issue in how the TransactionSynchronizationRegistry is looked up for (JPA container managed) persistence contexts used inside of JTA transactions. > Update WildFlyCustomJtaPlatform#locateTransactionSynchronizationRegistry to use a direct reference to the TransactionSynchronizationRegistry > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11243 > URL: https://issues.jboss.org/browse/WFLY-11243 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 14.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 15.0.0.CR1 > > > This addresses what is likely a performance issue in how the TransactionSynchronizationRegistry is looked up for (JPA container managed) persistence contexts used inside of JTA transactions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11243) Update WildFlyCustomJtaPlatform#locateTransactionSynchronizationRegistry to use a direct reference to the TransactionSynchronizationRegistry

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11243?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-11243: -------------------------------- Affects Version/s: 14.0.0.Final > Update WildFlyCustomJtaPlatform#locateTransactionSynchronizationRegistry to use a direct reference to the TransactionSynchronizationRegistry > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11243 > URL: https://issues.jboss.org/browse/WFLY-11243 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 14.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 15.0.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11243) Update WildFlyCustomJtaPlatform#locateTransactionSynchronizationRegistry to use a direct reference to the TransactionSynchronizationRegistry

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11243?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-11243: -------------------------------- Issue Type: Task (was: Feature Request) > Update WildFlyCustomJtaPlatform#locateTransactionSynchronizationRegistry to use a direct reference to the TransactionSynchronizationRegistry > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11243 > URL: https://issues.jboss.org/browse/WFLY-11243 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 15.0.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

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