[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)
4 years, 10 months
[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)
4 years, 10 months
[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)
4 years, 10 months