February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12679) Upgrade HAL from 3.2.1 to 3.2.2

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFLY-12679?page=com.atlassian.jira.plugi... ] Moulali Shikalwadi resolved WFLY-12679. --------------------------------------- Resolution: Out of Date As per above comment this issue is already solved. > Upgrade HAL from 3.2.1 to 3.2.2 > ------------------------------- > > Key: WFLY-12679 > URL: https://issues.redhat.com/browse/WFLY-12679 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Affects Versions: 18.0.0.Final > Reporter: Chao Wang > Assignee: Moulali Shikalwadi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12093) bug in tutorial "batch-processing" with column "End Time"

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-12093?page=com.atlassian.jira.plugi... ] Parul Sharma reassigned WFLY-12093: ----------------------------------- Assignee: Parul Sharma (was: Eduardo Martins) > bug in tutorial "batch-processing" with column "End Time" > --------------------------------------------------------- > > Key: WFLY-12093 > URL: https://issues.redhat.com/browse/WFLY-12093 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Environment: batch-processing > Reporter: Святослав Кремлёв > Assignee: Parul Sharma > Priority: Major > Attachments: 2019-05-18 23_16_51-Batch Processing.png > > > in file > org/jboss/as/quickstarts/batch/controller/JobData.java > {code} > public Date getEndTime() { > endTime = new Date(); > return endTime.getTime() == 0 ? null : endTime; > } > {code} > its returns current time every time, not the job endTime -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12679) Upgrade HAL from 3.2.1 to 3.2.2

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFLY-12679?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFLY-12679: ---------------------------------- Hi [~mshikalw], WFLY-12831 has already upgraded HAL to 3.2.4.Final, so we can resolve this as out of date. > Upgrade HAL from 3.2.1 to 3.2.2 > ------------------------------- > > Key: WFLY-12679 > URL: https://issues.redhat.com/browse/WFLY-12679 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Affects Versions: 18.0.0.Final > Reporter: Chao Wang > Assignee: Moulali Shikalwadi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13047) Flooding "not found in retransmission table" in server log too much in cluster and making application slow.

by Dheeraj Mishra (Jira)

[ https://issues.redhat.com/browse/WFLY-13047?page=com.atlassian.jira.plugi... ] Dheeraj Mishra commented on WFLY-13047: --------------------------------------- This is happening in customer environment also. so request you to have a look in priority. thanks much in advance. > Flooding "not found in retransmission table" in server log too much in cluster and making application slow. > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-13047 > URL: https://issues.redhat.com/browse/WFLY-13047 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 11.0.0.Final > Reporter: Dheeraj Mishra > Assignee: Brian Stansberry > Priority: Blocker > Attachments: log3.zip, standalone.xml > > > We have 24 JVM cluster using multicast and observing below error too much in server.log and it is making application slower. attaching logs for your reference. > 2020-02-02 02:22:07,839 WARN [org.jboss.as.clustering.jgroups.protocol.NAKACK2] (thread-1) JGRP000041: sol120_7433: message sol120_7403::1425 not found in retransmission table -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13047) Flooding "not found in retransmission table" in server log too much in cluster and making application slow.

by Dheeraj Mishra (Jira)

Dheeraj Mishra created WFLY-13047: ------------------------------------- Summary: Flooding "not found in retransmission table" in server log too much in cluster and making application slow. Key: WFLY-13047 URL: https://issues.redhat.com/browse/WFLY-13047 Project: WildFly Issue Type: Bug Components: EE Affects Versions: 11.0.0.Final Reporter: Dheeraj Mishra Assignee: Brian Stansberry Attachments: log3.zip, standalone.xml We have 24 JVM cluster using multicast and observing below error too much in server.log and it is making application slower. attaching logs for your reference. 2020-02-02 02:22:07,839 WARN [org.jboss.as.clustering.jgroups.protocol.NAKACK2] (thread-1) JGRP000041: sol120_7433: message sol120_7403::1425 not found in retransmission table -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12904) Create a quickstart for the ejb remoting and transaction recovery on OpenShift

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-12904?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka updated WFLY-12904: ------------------------------------ Git Pull Request: https://github.com/wildfly/quickstart/pull/372 > Create a quickstart for the ejb remoting and transaction recovery on OpenShift > ------------------------------------------------------------------------------ > > Key: WFLY-12904 > URL: https://issues.redhat.com/browse/WFLY-12904 > Project: WildFly > Issue Type: Task > Components: Quickstarts, Transactions > Affects Versions: 18.0.1.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > As the follow-up to the issue EAP7-1192 we need to have a quickstart which document the necessary steps to setup the OpenShift environment and to show how the scaledown recovery processing works. -- This message was sent by Atlassian Jira (v7.13.8#713008)

1 year, 7 months

1
0
0 / 0

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2020