February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1404) Upgrade Undertow to 1.3.18.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1404?page=com.atlassian.jira.plugi... ] Stuart Douglas moved JBEAP-3504 to WFCORE-1404: ----------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1404 (was: JBEAP-3504) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: (was: Web (Undertow)) Target Release: (was: 7.0.0.GA) > Upgrade Undertow to 1.3.18.Final > -------------------------------- > > Key: WFCORE-1404 > URL: https://issues.jboss.org/browse/WFCORE-1404 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Blocker > > Changelog https://issues.jboss.org/projects/UNDERTOW/versions/12329565 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6241) Setting of non-existing factory class to connector service can cause ActiveMQ crash

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-6241?page=com.atlassian.jira.plugin.... ] Lin Gao reassigned WFLY-6241: ----------------------------- Assignee: Lin Gao (was: Jeff Mesnil) > Setting of non-existing factory class to connector service can cause ActiveMQ crash > ----------------------------------------------------------------------------------- > > Key: WFLY-6241 > URL: https://issues.jboss.org/browse/WFLY-6241 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Critical > > When setting non-existing factory class to connector service, no validation is done and during startup after reload service will fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1403) UDP Syslog handler cannot log first message after reconnect

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1403?page=com.atlassian.jira.plugi... ] James Perkins closed WFCORE-1403. --------------------------------- Resolution: Rejected This is working as expected. It's the way that {{java.net.DatagramSocket.send()}} is implemented. The first invocation on a down server doesn't raise and error. The second invocation raises the error and the third invocation works as expected. > UDP Syslog handler cannot log first message after reconnect > ----------------------------------------------------------- > > Key: WFCORE-1403 > URL: https://issues.jboss.org/browse/WFCORE-1403 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Ondrej Lukas > Assignee: James Perkins > Attachments: logging-deployment.war > > > In case when logging to syslog through UDP protocol is configured and syslog port becomes unreachable then after syslog restart first message can be thrown away. It happens when odd number of messages is attempted to be logged during syslog is unreachable. It is caused when port unreachable is returned during logging attempt, then another log attempt automatically fail even if syslog server has been started meanwhile. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1403) UDP Syslog handler cannot log first message after reconnect

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1403?page=com.atlassian.jira.plugi... ] James Perkins moved WFLY-6242 to WFCORE-1403: --------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1403 (was: WFLY-6242) Component/s: Logging (was: Logging) > UDP Syslog handler cannot log first message after reconnect > ----------------------------------------------------------- > > Key: WFCORE-1403 > URL: https://issues.jboss.org/browse/WFCORE-1403 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Ondrej Lukas > Assignee: James Perkins > Attachments: logging-deployment.war > > > In case when logging to syslog through UDP protocol is configured and syslog port becomes unreachable then after syslog restart first message can be thrown away. It happens when odd number of messages is attempted to be logged during syslog is unreachable. It is caused when port unreachable is returned during logging attempt, then another log attempt automatically fail even if syslog server has been started meanwhile. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1402) Add support for metaspacesize to jvm options and remove permgen

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1402?page=com.atlassian.jira.plugi... ] Ken Wills updated WFCORE-1402: ------------------------------ Fix Version/s: 3.0.0.Alpha1 > Add support for metaspacesize to jvm options and remove permgen > --------------------------------------------------------------- > > Key: WFCORE-1402 > URL: https://issues.jboss.org/browse/WFCORE-1402 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 3.0.0.Alpha1 > > > We could display the configured Metaspace values, and we should remove the now deprecated permgen values. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1402) Add support for metaspacesize to jvm options and remove permgen

by Ken Wills (JIRA)

Ken Wills created WFCORE-1402: --------------------------------- Summary: Add support for metaspacesize to jvm options and remove permgen Key: WFCORE-1402 URL: https://issues.jboss.org/browse/WFCORE-1402 Project: WildFly Core Issue Type: Enhancement Reporter: Ken Wills We could display the configured Metaspace values, and we should remove the now deprecated permgen values. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1402) Add support for metaspacesize to jvm options and remove permgen

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1402?page=com.atlassian.jira.plugi... ] Ken Wills reassigned WFCORE-1402: --------------------------------- Assignee: Ken Wills > Add support for metaspacesize to jvm options and remove permgen > --------------------------------------------------------------- > > Key: WFCORE-1402 > URL: https://issues.jboss.org/browse/WFCORE-1402 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Ken Wills > Assignee: Ken Wills > > We could display the configured Metaspace values, and we should remove the now deprecated permgen values. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1401) TCP Syslog handler cannot log some messages after reconnect

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1401?page=com.atlassian.jira.plugi... ] James Perkins moved WFLY-6243 to WFCORE-1401: --------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1401 (was: WFLY-6243) Component/s: Logging (was: Logging) > TCP Syslog handler cannot log some messages after reconnect > ----------------------------------------------------------- > > Key: WFCORE-1401 > URL: https://issues.jboss.org/browse/WFCORE-1401 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Ondrej Lukas > Assignee: James Perkins > Attachments: logging-deployment.war > > > In case when logging to syslog through TCP protocol is configured and syslog port becomes unreachable then after syslog restart some messages can be thrown away. > It seems syslog handler needs to another two logs for correct closing original TCP connection. In case when syslog is restarted and > * no message is logged during syslog is unreachable then the first two messages will not be logged to syslog after syslog is running again > * one message is attempted to be logged during syslog is unreachable then the first message will not be logged to syslog after syslog is running again > * two and more messages are attempted to be logged during syslog is unreachable then everything is logged correctly after syslog is running again -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1401) TCP Syslog handler cannot log some messages after reconnect

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1401?page=com.atlassian.jira.plugi... ] James Perkins closed WFCORE-1401. --------------------------------- Resolution: Rejected This is the expected behavior. Here's what happens in the {{org.jboss.logmanager.handlers.SyslogHandler}}. * First message when the server is down is sent and no error is raised by the {{java.net.Socket}} therefore the syslog handler thinks all is okay * A second message is sent this time the {{java.net.Socket}} throws a {{java.net.SocketException: Broken pipe}}. The syslog handler reports this and the socket attempts to reconnect, but the message is not sent again. * The third message succeeds because the connection has once again been resestablished This works in your second scenario as well because the socket keeps attempting to connect. A successful connection is made by the time you send your third message. There is a possibility the message might not be sent until the fourth or fifth message even. It all depends on when the socket is reconnected. That said there is a setting, {{blockOnReconnect}} which defaults to {{false}}, that will guarantee the third message is logged. The handler will block until a connection has been reestablished. I would however only suggest this be used wrapped in an {{async-handler}} as you could stall the entire server until the connection has been reestablished. > TCP Syslog handler cannot log some messages after reconnect > ----------------------------------------------------------- > > Key: WFCORE-1401 > URL: https://issues.jboss.org/browse/WFCORE-1401 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Ondrej Lukas > Assignee: James Perkins > Attachments: logging-deployment.war > > > In case when logging to syslog through TCP protocol is configured and syslog port becomes unreachable then after syslog restart some messages can be thrown away. > It seems syslog handler needs to another two logs for correct closing original TCP connection. In case when syslog is restarted and > * no message is logged during syslog is unreachable then the first two messages will not be logged to syslog after syslog is running again > * one message is attempted to be logged during syslog is unreachable then the first message will not be logged to syslog after syslog is running again > * two and more messages are attempted to be logged during syslog is unreachable then everything is logged correctly after syslog is running again -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1369) Audit logging to TCP syslog is stopped after syslog restart

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1369?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-1369: --------------------------------------- Note the PR allows for a better reconnect, but the reconnect will not work as expected in the description of this issue. If a syslog server goes down or the connection is dropped it will take 2 messages sent before a third one will be logged. On the first message sent after a disruption will simply be ignored by the {{java.net.Socket}}. The second message sent will throw a {{java.net.SocketException: Broken pipe}}. This error is thrown by the syslog audit log handler and the connection state is reset indicating it should be reconnected. Finally the third message will go through. > Audit logging to TCP syslog is stopped after syslog restart > ----------------------------------------------------------- > > Key: WFCORE-1369 > URL: https://issues.jboss.org/browse/WFCORE-1369 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.10.Final > Reporter: Ondrej Lukas > Assignee: James Perkins > > In case when audit logging to TCP syslog is enabled and syslog server is restarted then audit logging to syslog is stopped. UDP works correctly. It can be related to issue [1]. > [1] https://issues.jboss.org/browse/LOGMGR-123 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016