October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12728) remove unneeded dependencies from jpa/hibernate5_3/pom.xml

by Scott Marlow (Jira)

Scott Marlow created WFLY-12728: ----------------------------------- Summary: remove unneeded dependencies from jpa/hibernate5_3/pom.xml Key: WFLY-12728 URL: https://issues.jboss.org/browse/WFLY-12728 Project: WildFly Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Remove unneeded Infinispan/ORM dependencies + dependencyManagement, in jpa/hibernate5_3/pom.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12711) Avoid jaxb-api dependency convergence errors from Hibernate Search ORM

by Romain Pelisse (Jira)

[ https://issues.jboss.org/browse/WFLY-12711?page=com.atlassian.jira.plugin... ] Romain Pelisse updated WFLY-12711: ---------------------------------- Labels: downstream_dependency (was: ) > Avoid jaxb-api dependency convergence errors from Hibernate Search ORM > ---------------------------------------------------------------------- > > Key: WFLY-12711 > URL: https://issues.jboss.org/browse/WFLY-12711 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Optional > Labels: downstream_dependency > Fix For: 19.0.0.Beta1 > > > I've seen a case in another branch where the maven enforcer plugin reported a dependency convergence error due to Hibernate Search ORM using a different version of jaxb-api versus other deps. I'm cleaning that up via an exclusion (JBEAP-17851) and if it happened there it might happen some day here. Since WF controls the version of jaxb-api in dependencyManagement might as well harden against this happening by adding the exclude to master too. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4705) Drools/Kie-Server/Busines-Central 7.28.0 Is getting a 403 when kie-server accesses the websocket controller on business-central

by Danny Rucker (Jira)

[ https://issues.jboss.org/browse/DROOLS-4705?page=com.atlassian.jira.plugi... ] Danny Rucker closed DROOLS-4705. -------------------------------- Resolution: Done > Drools/Kie-Server/Busines-Central 7.28.0 Is getting a 403 when kie-server accesses the websocket controller on business-central > ------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4705 > URL: https://issues.jboss.org/browse/DROOLS-4705 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.24.0.Final, 7.25.0.Final, 7.28.0.Final > Environment: Linux, JDK8, and Wildfly 14.0.1 > Reporter: Danny Rucker > Assignee: Maciej Swiderski > Priority: Major > Fix For: 7.23.0.Final > > > We're upgrading our business-central server from 7.23.0 to 7.28.0. We're noticing that our kie-servers can no longer connect via websocket to business-central: > Server logs: > {quote} > Oct 28 12:56:43 business-central-1 business-central[18870]: #033[0m#033[0m12:56:43,962 INFO [org.kie.server.controller.websocket.notification.WebSocketNotificationService] (Thread-123) WebSocket notify on updated :: Updated server template{serverTemplate=ServerTemplateKey{id='host.subdomain.x.com', name='host.subdomain.x.com'}, resetBeforeUpdate=false} > Oct 28 12:56:43 business-central-1 business-central[18870]: #033[0m#033[0m12:56:43,963 INFO [org.kie.server.controller.websocket.notification.WebSocketNotificationService] (Thread-123) WebSocket notify on instance disconnected :: ServerInstanceDisconnected{serverInstanceId='host.subdomain.x.com@host.subdomain.x.com:36204'} > {quote} > Client logs: > {quote} > Oct 28 20:21:53 host kie-server[1375]: #033[0m#033[33m20:21:53,090 WARN [org.kie.server.common.KeyStoreHelperUtil] (KieServer-ControllerConnect) Unable to load key store. Using password from configuration > Oct 28 20:21:53 host kie-server[1375]: #033[0m#033[33m20:21:53,146 WARN [org.kie.server.controller.websocket.client.WebSocketKieServerControllerImpl] (KieServer-ControllerConnect) Exception encountered while syncing with controller at wss://business-central-1.x.com/business-central/websocket/controller/host... error Invalid response code 403 > {quote} > The actual break occurred between 7.23.0 and 7.24.0, as 7.24.0 produces the same error message: Invalid response code 403. > The user that kie-server is connecting to business-central with has kie-server as a group, but that doesn't seem to help. We're running business-central on Wildfly 14.0.1. > I'm looking through the commits for a web.xml change for filtering web reources but can't seem to find anything. Actually, I'm not even sure which github project I should be looking in: https://github.com/kiegroup > tcpdump from 7.24.0+ versions(none worked): > {quote} > GET /business-central/websocket/controller/apps-3-staging HTTP/1.1 > Authorization: Basic <base64-stuff-here> > Sec-WebSocket-Key: YZ5r8liCJKut6VJ2YG7sPQ== > Connection: upgrade > Sec-WebSocket-Version: 13 > Upgrade: websocket > Host: localhost:8080 > HTTP/1.1 403 Forbidden > Expires: 0 > Cache-Control: no-cache, no-store, must-revalidate > X-Powered-By: JSP/2.3 > Set-Cookie: JSESSIONID=cBz0q1sK09Fq2jtXA8Mad1FHPKxvQ38akKGNMP9R.business-central-1; path=/business-central; HttpOnly; Max-Age=0; Expires=Thu, 01-Jan-1970 00:00:00 GMT > Pragma: no-cache > Date: Mon, 28 Oct 2019 18:23:21 GMT > Connection: keep-alive > Content-Type: text/html;charset=UTF-8 > Content-Length: 1102 > Content-Language: en- > {quote} > tcpdump from 7.23.0 version(which works): > {quote} > GET /business-central/websocket/controller/apps-3-staging HTTP/1.1 > Authorization: Basic <base64-stuff-here> > Sec-WebSocket-Key: yhykxYXh0z+KF0Zv/8P76g== > Connection: upgrade > Sec-WebSocket-Version: 13 > Host: localhost:8080 > Upgrade: websocket > HTTP/1.1 101 Switching Protocols > Connection: Upgrade > Set-Cookie: JSESSIONID=UCZsXbdV1ZUjTBTOcbP9j-ppd3y2NH0mzOqPQcjP.business-central; path=/business-central; HttpOnly > Sec-WebSocket-Location: wss://business-central-1/business-central/websocket/controller/apps-3-staging > X-XSS-Protection: 1; mode=block > Upgrade: WebSocket > X-FRAME-OPTIONS: SAMEORIGIN > Sec-WebSocket-Accept: 6qSH/TZNvoukpIE+ZJYulWzGge0= > Date: Mon, 28 Oct 2019 17:21:57 GMT > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12718) Clustering: replicated-cache sampling errors

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12718?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-12718: --------------------------------------- [~tommaso-borgato] There are about 100.000 sessions created on the server. It looks as though the cookies are not being sent and every request creates a new session eventually running out of memory. {noformat} [rhusar@ribera tmp]$ curl https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... | grep "New session created" | wc -l % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 15.0M 100 15.0M 0 0 4866k 0 0:00:03 0:00:03 --:--:-- 4864k 25171 [rhusar@ribera tmp]$ curl https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... | grep "New session created" | wc -l % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 11.3M 100 11.3M 0 0 2942k 0 0:00:03 0:00:03 --:--:-- 2941k 24741 [rhusar@ribera tmp]$ curl https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... | grep "New session created" | wc -l % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 28.6M 100 28.6M 0 0 4714k 0 0:00:06 0:00:06 --:--:-- 6606k 21061 [rhusar@ribera tmp]$ curl https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... | grep "New session created" | wc -l % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 4596k 100 4596k 0 0 2000k 0 0:00:02 0:00:02 --:--:-- 1999k 23242 {noformat} > Clustering: replicated-cache sampling errors > -------------------------------------------- > > Key: WFLY-12718 > URL: https://issues.jboss.org/browse/WFLY-12718 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Tommasso Borgato > Assignee: Paul Ferraro > Priority: Blocker > > The issue is about replicated-cache in fail-over tests. > WildFly is started in clustered mode using a replicated cache for replicating HTTP session data across cluster nodes; all 4 nodes in the cluster are initialized with the following cli script: > {noformat} > embed-server --server-config=standalone-ha.xml > /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add() > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add() > /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl) > {noformat} > The test is run with wildfly-18.0.0.Final.zip; > The same tests run with version wildfly-17.0.1.Final.zip do not have any problem; > hence this looks like a regression; > As usual, we test that the serial value stored in the replicated cache is incremented at every call: when this is not true, we say we have a sampling error; > Here are the runs that exhibit this issue: > - **22.82% Fail Rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#23|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#24|https://eap-qe-jenkins.r...] > We also repeated the tests to make sure it can be reproduced: > - **22.75% Fail rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#26|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#25|https://eap-qe-jenkins.r...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12718) Clustering: replicated-cache sampling errors

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12718?page=com.atlassian.jira.plugin... ] Radoslav Husar edited comment on WFLY-12718 at 10/29/19 1:24 PM: ----------------------------------------------------------------- [~tommaso-borgato] There are about 100.000 sessions created on the cluster. It looks as though the cookies are not being sent and every request creates a new session eventually running out of memory. {noformat} [rhusar@ribera tmp]$ curl https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... | grep "New session created" | wc -l % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 15.0M 100 15.0M 0 0 4866k 0 0:00:03 0:00:03 --:--:-- 4864k 25171 [rhusar@ribera tmp]$ curl https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... | grep "New session created" | wc -l % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 11.3M 100 11.3M 0 0 2942k 0 0:00:03 0:00:03 --:--:-- 2941k 24741 [rhusar@ribera tmp]$ curl https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... | grep "New session created" | wc -l % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 28.6M 100 28.6M 0 0 4714k 0 0:00:06 0:00:06 --:--:-- 6606k 21061 [rhusar@ribera tmp]$ curl https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... | grep "New session created" | wc -l % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 4596k 100 4596k 0 0 2000k 0 0:00:02 0:00:02 --:--:-- 1999k 23242 {noformat} was (Author: rhusar): [~tommaso-borgato] There are about 100.000 sessions created on the server. It looks as though the cookies are not being sent and every request creates a new session eventually running out of memory. {noformat} [rhusar@ribera tmp]$ curl https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... | grep "New session created" | wc -l % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 15.0M 100 15.0M 0 0 4866k 0 0:00:03 0:00:03 --:--:-- 4864k 25171 [rhusar@ribera tmp]$ curl https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... | grep "New session created" | wc -l % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 11.3M 100 11.3M 0 0 2942k 0 0:00:03 0:00:03 --:--:-- 2941k 24741 [rhusar@ribera tmp]$ curl https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... | grep "New session created" | wc -l % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 28.6M 100 28.6M 0 0 4714k 0 0:00:06 0:00:06 --:--:-- 6606k 21061 [rhusar@ribera tmp]$ curl https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... | grep "New session created" | wc -l % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 4596k 100 4596k 0 0 2000k 0 0:00:02 0:00:02 --:--:-- 1999k 23242 {noformat} > Clustering: replicated-cache sampling errors > -------------------------------------------- > > Key: WFLY-12718 > URL: https://issues.jboss.org/browse/WFLY-12718 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Tommasso Borgato > Assignee: Paul Ferraro > Priority: Blocker > > The issue is about replicated-cache in fail-over tests. > WildFly is started in clustered mode using a replicated cache for replicating HTTP session data across cluster nodes; all 4 nodes in the cluster are initialized with the following cli script: > {noformat} > embed-server --server-config=standalone-ha.xml > /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add() > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add() > /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl) > {noformat} > The test is run with wildfly-18.0.0.Final.zip; > The same tests run with version wildfly-17.0.1.Final.zip do not have any problem; > hence this looks like a regression; > As usual, we test that the serial value stored in the replicated cache is incremented at every call: when this is not true, we say we have a sampling error; > Here are the runs that exhibit this issue: > - **22.82% Fail Rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#23|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#24|https://eap-qe-jenkins.r...] > We also repeated the tests to make sure it can be reproduced: > - **22.75% Fail rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#26|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#25|https://eap-qe-jenkins.r...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4705) Drools/Kie-Server/Busines-Central 7.28.0 Is getting a 403 when kie-server accesses the websocket controller on business-central

by Danny Rucker (Jira)

[ https://issues.jboss.org/browse/DROOLS-4705?page=com.atlassian.jira.plugi... ] Danny Rucker commented on DROOLS-4705: -------------------------------------- Thank you very much, that solved our issue. I will close this ticket now. > Drools/Kie-Server/Busines-Central 7.28.0 Is getting a 403 when kie-server accesses the websocket controller on business-central > ------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4705 > URL: https://issues.jboss.org/browse/DROOLS-4705 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.24.0.Final, 7.25.0.Final, 7.28.0.Final > Environment: Linux, JDK8, and Wildfly 14.0.1 > Reporter: Danny Rucker > Assignee: Maciej Swiderski > Priority: Major > Fix For: 7.23.0.Final > > > We're upgrading our business-central server from 7.23.0 to 7.28.0. We're noticing that our kie-servers can no longer connect via websocket to business-central: > Server logs: > {quote} > Oct 28 12:56:43 business-central-1 business-central[18870]: #033[0m#033[0m12:56:43,962 INFO [org.kie.server.controller.websocket.notification.WebSocketNotificationService] (Thread-123) WebSocket notify on updated :: Updated server template{serverTemplate=ServerTemplateKey{id='host.subdomain.x.com', name='host.subdomain.x.com'}, resetBeforeUpdate=false} > Oct 28 12:56:43 business-central-1 business-central[18870]: #033[0m#033[0m12:56:43,963 INFO [org.kie.server.controller.websocket.notification.WebSocketNotificationService] (Thread-123) WebSocket notify on instance disconnected :: ServerInstanceDisconnected{serverInstanceId='host.subdomain.x.com@host.subdomain.x.com:36204'} > {quote} > Client logs: > {quote} > Oct 28 20:21:53 host kie-server[1375]: #033[0m#033[33m20:21:53,090 WARN [org.kie.server.common.KeyStoreHelperUtil] (KieServer-ControllerConnect) Unable to load key store. Using password from configuration > Oct 28 20:21:53 host kie-server[1375]: #033[0m#033[33m20:21:53,146 WARN [org.kie.server.controller.websocket.client.WebSocketKieServerControllerImpl] (KieServer-ControllerConnect) Exception encountered while syncing with controller at wss://business-central-1.x.com/business-central/websocket/controller/host... error Invalid response code 403 > {quote} > The actual break occurred between 7.23.0 and 7.24.0, as 7.24.0 produces the same error message: Invalid response code 403. > The user that kie-server is connecting to business-central with has kie-server as a group, but that doesn't seem to help. We're running business-central on Wildfly 14.0.1. > I'm looking through the commits for a web.xml change for filtering web reources but can't seem to find anything. Actually, I'm not even sure which github project I should be looking in: https://github.com/kiegroup > tcpdump from 7.24.0+ versions(none worked): > {quote} > GET /business-central/websocket/controller/apps-3-staging HTTP/1.1 > Authorization: Basic <base64-stuff-here> > Sec-WebSocket-Key: YZ5r8liCJKut6VJ2YG7sPQ== > Connection: upgrade > Sec-WebSocket-Version: 13 > Upgrade: websocket > Host: localhost:8080 > HTTP/1.1 403 Forbidden > Expires: 0 > Cache-Control: no-cache, no-store, must-revalidate > X-Powered-By: JSP/2.3 > Set-Cookie: JSESSIONID=cBz0q1sK09Fq2jtXA8Mad1FHPKxvQ38akKGNMP9R.business-central-1; path=/business-central; HttpOnly; Max-Age=0; Expires=Thu, 01-Jan-1970 00:00:00 GMT > Pragma: no-cache > Date: Mon, 28 Oct 2019 18:23:21 GMT > Connection: keep-alive > Content-Type: text/html;charset=UTF-8 > Content-Length: 1102 > Content-Language: en- > {quote} > tcpdump from 7.23.0 version(which works): > {quote} > GET /business-central/websocket/controller/apps-3-staging HTTP/1.1 > Authorization: Basic <base64-stuff-here> > Sec-WebSocket-Key: yhykxYXh0z+KF0Zv/8P76g== > Connection: upgrade > Sec-WebSocket-Version: 13 > Host: localhost:8080 > Upgrade: websocket > HTTP/1.1 101 Switching Protocols > Connection: Upgrade > Set-Cookie: JSESSIONID=UCZsXbdV1ZUjTBTOcbP9j-ppd3y2NH0mzOqPQcjP.business-central; path=/business-central; HttpOnly > Sec-WebSocket-Location: wss://business-central-1/business-central/websocket/controller/apps-3-staging > X-XSS-Protection: 1; mode=block > Upgrade: WebSocket > X-FRAME-OPTIONS: SAMEORIGIN > Sec-WebSocket-Accept: 6qSH/TZNvoukpIE+ZJYulWzGge0= > Date: Mon, 28 Oct 2019 17:21:57 GMT > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12726) [18.0.x] Update jackson-databind to 2.9.10.1

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12726?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-12726: --------------------------------------- Assignee: Brian Stansberry (was: Rostislav Svoboda) > [18.0.x] Update jackson-databind to 2.9.10.1 > -------------------------------------------- > > Key: WFLY-12726 > URL: https://issues.jboss.org/browse/WFLY-12726 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Priority: Major > Fix For: 18.0.1.Final > > > Update jackson-databind to 2.9.10.1 > https://github.com/FasterXML/jackson-databind/releases -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12726) [18.0.x] Update jackson-databind to 2.9.10.1

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12726?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12726: ------------------------------------ Fix Version/s: 18.0.1.Final (was: 19.0.0.Beta1) > [18.0.x] Update jackson-databind to 2.9.10.1 > -------------------------------------------- > > Key: WFLY-12726 > URL: https://issues.jboss.org/browse/WFLY-12726 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Priority: Major > Fix For: 18.0.1.Final > > > Update jackson-databind to 2.9.10.1 > https://github.com/FasterXML/jackson-databind/releases -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12726) [18.0.x] Update jackson-databind to 2.9.10.1

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12726?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12726: ------------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/12732) > [18.0.x] Update jackson-databind to 2.9.10.1 > -------------------------------------------- > > Key: WFLY-12726 > URL: https://issues.jboss.org/browse/WFLY-12726 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Priority: Major > Fix For: 18.0.1.Final > > > Update jackson-databind to 2.9.10.1 > https://github.com/FasterXML/jackson-databind/releases -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12727) Upgrade Netty to 4.1.42

by Emmanuel Hugonnet (Jira)

Emmanuel Hugonnet created WFLY-12727: ---------------------------------------- Summary: Upgrade Netty to 4.1.42 Key: WFLY-12727 URL: https://issues.jboss.org/browse/WFLY-12727 Project: WildFly Issue Type: Component Upgrade Components: JMS Affects Versions: 18.0.0.Final Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Upgrade Netty to 4.1.42 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019