[JBoss JIRA] (WFCORE-1647) Default app-name value of Syslog handler in Audit Logging violates specification
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1647?page=com.atlassian.jira.plugi... ]
Tomaz Cerar commented on WFCORE-1647:
-------------------------------------
You are positive this is still issue in version 3.0.0? As EAP7.0 uses 2.1.x versions.
Asking as issue like this was already reported and fixed some time ago. But it could be a regression
> Default app-name value of Syslog handler in Audit Logging violates specification
> --------------------------------------------------------------------------------
>
> Key: WFCORE-1647
> URL: https://issues.jboss.org/browse/WFCORE-1647
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha3
> Reporter: Jan Tymel
> Assignee: Brian Stansberry
>
> According to syslog specification[1] {{app-name}} cannot contain space character (" "). However, the default value in WildFly Core 3.0.0.Alpha3 is {{WildFly Core}}. This results in the syslog server is not able to capture Process ID from which the message was sent.
> E.g. following piece of information is captured {{WildFly[Core] (...)}} instead of {{WildFlyCore[795]}}
> Suggestions for improvement:
> Change default value {{WildFly Core}} to one without space character.
> Also please consider addition of check whether {{app-name}} contains space character.
> [1] https://tools.ietf.org/html/rfc5424#page-8
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6822) Not possible to overlay non existing file in WAR - mark the sub deployment which will be mounted exploded
by Lin Gao (JIRA)
Lin Gao created WFLY-6822:
-----------------------------
Summary: Not possible to overlay non existing file in WAR - mark the sub deployment which will be mounted exploded
Key: WFLY-6822
URL: https://issues.jboss.org/browse/WFLY-6822
Project: WildFly
Issue Type: Bug
Components: EE
Affects Versions: 10.0.0.Final
Reporter: Lin Gao
Assignee: Lin Gao
Priority: Critical
It is either bug in how deployments are treated or how overlay/vfs work.
Steps to reproduce:
1. deploy undexploded war with jar inside
2. add overlay that will add non existing file in jar
Result: exception:
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay WEB-INF/lib/overlayed.jar//META-INF/x/file.txt at WEB-INF/lib/overlayed.jar//META-INF/x/file.txt
Caused by: java.io.FileNotFoundException: /content/shell.war/WEB-INF/lib/overlayed.jar/META-INF/x/file.txt"}}
at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:67)
at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:37)
at org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayUtils.setupOverlay(OverlayUtils.java:76)
at org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayNonExistingResourceTestCase.testOverlay(OverlayNonExistingResourceTestCase.java:67)
Expectation:
should work. It actually does work, if war is really exploded or
'if(exploded)' part in overlay is removed from overlay processor and everything is handled via: https://github.com/stuartwdouglas/wildfly-core/blob/a75af9118c4062fafb899...
This is part of the fix of above issue, which depends on WFCORE-761.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6821) Not possible to overlay non existing file in WAR - mark the sub deployment which will be mounted exploded
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-6821?page=com.atlassian.jira.plugin.... ]
Lin Gao updated WFLY-6821:
--------------------------
Labels: downstream_dependency (was: )
> Not possible to overlay non existing file in WAR - mark the sub deployment which will be mounted exploded
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6821
> URL: https://issues.jboss.org/browse/WFLY-6821
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 10.0.0.Final
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Critical
> Labels: downstream_dependency
>
> It is either bug in how deployments are treated or how overlay/vfs work.
> Steps to reproduce:
> 1. deploy undexploded war with jar inside
> 2. add overlay that will add non existing file in jar
> Result: exception:
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay WEB-INF/lib/overlayed.jar//META-INF/x/file.txt at WEB-INF/lib/overlayed.jar//META-INF/x/file.txt
> Caused by: java.io.FileNotFoundException: /content/shell.war/WEB-INF/lib/overlayed.jar/META-INF/x/file.txt"}}
> at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:67)
> at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:37)
> at org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayUtils.setupOverlay(OverlayUtils.java:76)
> at org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayNonExistingResourceTestCase.testOverlay(OverlayNonExistingResourceTestCase.java:67)
> Expectation:
> should work. It actually does work, if war is really exploded or
> 'if(exploded)' part in overlay is removed from overlay processor and everything is handled via: https://github.com/stuartwdouglas/wildfly-core/blob/a75af9118c4062fafb899...
> This is part of the fix of above issue, which depends on WFCORE-761.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1647) Default app-name value of Syslog handler in Audit Logging violates specification
by Jan Tymel (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1647?page=com.atlassian.jira.plugi... ]
Jan Tymel updated WFCORE-1647:
------------------------------
Description:
According to syslog specification[1] {{app-name}} cannot contain space character (" "). However, the default value in WildFly Core 3.0.0.Alpha3 is {{WildFly Core}}. This results in the syslog server is not able to capture Process ID from which the message was sent.
E.g. following piece of information is captured {{WildFly[Core] (...)}} instead of {{WildFlyCore[795]}}
Suggestions for improvement:
Change default value {{WildFly Core}} to one without space character.
Also please consider addition of check whether {{app-name}} contains space character.
[1] https://tools.ietf.org/html/rfc5424#page-8
was:
According to syslog specification[1] {{app-name}} cannot contain space character (" "). However, the default value in EAP 7 is {{WildFly Core}}. This results in the syslog server is not able to capture Process ID from which the message was sent.
E.g. following piece of information is captured {{WildFly[Core] (...)}} instead of {{WildFlyCore[795]}}
Suggestions for improvement:
Change default value {{WildFly Core}} to one without space character.
Also please consider addition of check whether {{app-name}} contains space character.
[1] https://tools.ietf.org/html/rfc5424#page-8
> Default app-name value of Syslog handler in Audit Logging violates specification
> --------------------------------------------------------------------------------
>
> Key: WFCORE-1647
> URL: https://issues.jboss.org/browse/WFCORE-1647
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha3
> Reporter: Jan Tymel
> Assignee: Brian Stansberry
>
> According to syslog specification[1] {{app-name}} cannot contain space character (" "). However, the default value in WildFly Core 3.0.0.Alpha3 is {{WildFly Core}}. This results in the syslog server is not able to capture Process ID from which the message was sent.
> E.g. following piece of information is captured {{WildFly[Core] (...)}} instead of {{WildFlyCore[795]}}
> Suggestions for improvement:
> Change default value {{WildFly Core}} to one without space character.
> Also please consider addition of check whether {{app-name}} contains space character.
> [1] https://tools.ietf.org/html/rfc5424#page-8
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6821) Not possible to overlay non existing file in WAR - mark the sub deployment which will be mounted exploded
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-6821?page=com.atlassian.jira.plugin.... ]
Lin Gao commented on WFLY-6821:
-------------------------------
This Jira is created to track the changes in WildFly main repository.
After discussion in https://github.com/wildfly/wildfly-core/pull/1332, to fix this overlay problem, both WildFly core and WildFly will be changed.
> Not possible to overlay non existing file in WAR - mark the sub deployment which will be mounted exploded
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6821
> URL: https://issues.jboss.org/browse/WFLY-6821
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 10.0.0.Final
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Critical
>
> It is either bug in how deployments are treated or how overlay/vfs work.
> Steps to reproduce:
> 1. deploy undexploded war with jar inside
> 2. add overlay that will add non existing file in jar
> Result: exception:
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay WEB-INF/lib/overlayed.jar//META-INF/x/file.txt at WEB-INF/lib/overlayed.jar//META-INF/x/file.txt
> Caused by: java.io.FileNotFoundException: /content/shell.war/WEB-INF/lib/overlayed.jar/META-INF/x/file.txt"}}
> at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:67)
> at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:37)
> at org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayUtils.setupOverlay(OverlayUtils.java:76)
> at org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayNonExistingResourceTestCase.testOverlay(OverlayNonExistingResourceTestCase.java:67)
> Expectation:
> should work. It actually does work, if war is really exploded or
> 'if(exploded)' part in overlay is removed from overlay processor and everything is handled via: https://github.com/stuartwdouglas/wildfly-core/blob/a75af9118c4062fafb899...
> This is part of the fix of above issue, which depends on WFCORE-761.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1647) Default app-name value of Syslog handler in Audit Logging violates specification
by Jan Tymel (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1647?page=com.atlassian.jira.plugi... ]
Jan Tymel updated WFCORE-1647:
------------------------------
Steps to Reproduce:
1. Configure Audit Logging to log into (local) rsyslog and start server
{code}
<audit-log>
<formatters>
<json-formatter name="json-formatter"/>
</formatters>
<handlers>
<file-handler name="file" formatter="json-formatter" path="audit-log.log" relative-to="jboss.server.data.dir"/>
<syslog-handler name="syslog-handler" formatter="json-formatter">
<udp host="127.0.0.1" port="514"/>
</syslog-handler>
</handlers>
<logger log-boot="true" log-read-only="false" enabled="true">
<handlers>
<handler name="file"/>
<handler name="syslog-handler"/>
</handlers>
</logger>
</audit-log>
{code}
2. Look into /var/log/messages file
Note: the brackets must be escaped, JIRA doesn't allow me to stress it. Brackets {{[, ]}} used in {{grep}} command should be always preceded by a backslash
{{sudo grep "WildFly\[Core\]" /var/log/messages}} - there should be a few occurrences
{{sudo grep "WildFlyCore\[" /var/log/messages}} - there should be no occurences
3. Stop server, change configuration to use {{app-name}} without space character and start it again
{code}
<audit-log>
<formatters>
<json-formatter name="json-formatter"/>
</formatters>
<handlers>
<file-handler name="file" formatter="json-formatter" path="audit-log.log" relative-to="jboss.server.data.dir"/>
<syslog-handler name="syslog-handler" formatter="json-formatter" app-name="WildFlyCore">
<udp host="127.0.0.1" port="514"/>
</syslog-handler>
</handlers>
<logger log-boot="true" log-read-only="false" enabled="true">
<handlers>
<handler name="file"/>
<handler name="syslog-handler"/>
</handlers>
</logger>
</audit-log>
{code}
4. Look into /var/log/messages file again
Note: the brackets must be escaped, JIRA doesn't allow me to stress it. Bracket {{[}} used in {{grep}} command should be always preceded by a backslash
{{sudo grep "WildFlyCore\[" /var/log/messages}} - there should be a few occurrences (that contains PID) now
was:
1. Configure Audit Logging to log into (local) rsyslog and start server
{code}
<audit-log>
<formatters>
<json-formatter name="json-formatter"/>
</formatters>
<handlers>
<file-handler name="file" formatter="json-formatter" path="audit-log.log" relative-to="jboss.server.data.dir"/>
<syslog-handler name="syslog-handler" formatter="json-formatter">
<udp host="127.0.0.1" port="514"/>
</syslog-handler>
</handlers>
<logger log-boot="true" log-read-only="false" enabled="true">
<handlers>
<handler name="file"/>
<handler name="syslog-handler"/>
</handlers>
</logger>
</audit-log>
{code}
2. Look into /var/log/messages file
Note: the brackets must be escaped, JIRA doesn't allow me to stress it. Brackets {{[, ]}} used in {{grep}} command should be always preceded by a backslash
{{sudo grep "WildFly\[Core\]" /var/log/messages}} - there should be a few occurrences
{{sudo grep "WildFlyCore\[" /var/log/messages}} - there should be no occurences
3. Stop server, change configuration to use {{app-name}} without space character and start it again
{code}
<audit-log>
<formatters>
<json-formatter name="json-formatter"/>
</formatters>
<handlers>
<file-handler name="file" formatter="json-formatter" path="audit-log.log" relative-to="jboss.server.data.dir"/>
<syslog-handler name="syslog-handler" formatter="json-formatter" app-name="WildFlyCore">
<udp host="127.0.0.1" port="514"/>
</syslog-handler>
</handlers>
<logger log-boot="true" log-read-only="false" enabled="true">
<handlers>
<handler name="file"/>
<handler name="syslog-handler"/>
</handlers>
</logger>
</audit-log>
{code}
4. Look into /var/log/messages file again
Note: the brackets must be escaped, JIRA doesn't allow me to stress it. Bracket {{[}} used in {{grep}} command should be always preceded by a backslash
{{sudo grep "JBossEAP\[" /var/log/messages}} - there should be a few occurrences (that contains PID) now
> Default app-name value of Syslog handler in Audit Logging violates specification
> --------------------------------------------------------------------------------
>
> Key: WFCORE-1647
> URL: https://issues.jboss.org/browse/WFCORE-1647
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha3
> Reporter: Jan Tymel
> Assignee: Brian Stansberry
>
> According to syslog specification[1] {{app-name}} cannot contain space character (" "). However, the default value in EAP 7 is {{WildFly Core}}. This results in the syslog server is not able to capture Process ID from which the message was sent.
> E.g. following piece of information is captured {{WildFly[Core] (...)}} instead of {{WildFlyCore[795]}}
> Suggestions for improvement:
> Change default value {{WildFly Core}} to one without space character.
> Also please consider addition of check whether {{app-name}} contains space character.
> [1] https://tools.ietf.org/html/rfc5424#page-8
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1647) Default app-name value of Syslog handler in Audit Logging violates specification
by Jan Tymel (JIRA)
Jan Tymel created WFCORE-1647:
---------------------------------
Summary: Default app-name value of Syslog handler in Audit Logging violates specification
Key: WFCORE-1647
URL: https://issues.jboss.org/browse/WFCORE-1647
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.0.0.Alpha3
Reporter: Jan Tymel
Assignee: Brian Stansberry
According to syslog specification[1] {{app-name}} cannot contain space character (" "). However, the default value in EAP 7 is {{WildFly Core}}. This results in the syslog server is not able to capture Process ID from which the message was sent.
E.g. following piece of information is captured {{WildFly[Core] (...)}} instead of {{WildFlyCore[795]}}
Suggestions for improvement:
Change default value {{WildFly Core}} to one without space character.
Also please consider addition of check whether {{app-name}} contains space character.
[1] https://tools.ietf.org/html/rfc5424#page-8
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6821) Not possible to overlay non existing file in WAR - mark the sub deployment which will be mounted exploded
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-6821?page=com.atlassian.jira.plugin.... ]
Lin Gao updated WFLY-6821:
--------------------------
Description:
It is either bug in how deployments are treated or how overlay/vfs work.
Steps to reproduce:
1. deploy undexploded war with jar inside
2. add overlay that will add non existing file in jar
Result: exception:
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay WEB-INF/lib/overlayed.jar//META-INF/x/file.txt at WEB-INF/lib/overlayed.jar//META-INF/x/file.txt
Caused by: java.io.FileNotFoundException: /content/shell.war/WEB-INF/lib/overlayed.jar/META-INF/x/file.txt"}}
at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:67)
at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:37)
at org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayUtils.setupOverlay(OverlayUtils.java:76)
at org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayNonExistingResourceTestCase.testOverlay(OverlayNonExistingResourceTestCase.java:67)
Expectation:
should work. It actually does work, if war is really exploded or
'if(exploded)' part in overlay is removed from overlay processor and everything is handled via: https://github.com/stuartwdouglas/wildfly-core/blob/a75af9118c4062fafb899...
This is part of the fix of above issue, which depends on WFCORE-761.
was:
It is either bug in how deployments are treated or how overlay/vfs work.
Steps to reproduce:
1. deploy undexploded war with jar inside
2. add overlay that will add non existing file in jar
Result: exception:
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay WEB-INF/lib/overlayed.jar//META-INF/x/file.txt at WEB-INF/lib/overlayed.jar//META-INF/x/file.txt
Caused by: java.io.FileNotFoundException: /content/shell.war/WEB-INF/lib/overlayed.jar/META-INF/x/file.txt"}}
at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:67)
at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:37)
at org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayUtils.setupOverlay(OverlayUtils.java:76)
at org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayNonExistingResourceTestCase.testOverlay(OverlayNonExistingResourceTestCase.java:67)
Expectation:
should work. It actually does work, if war is really exploded or
'if(exploded)' part in overlay is removed from overlay processor and everything is handled via: https://github.com/stuartwdouglas/wildfly-core/blob/a75af9118c4062fafb899...
> Not possible to overlay non existing file in WAR - mark the sub deployment which will be mounted exploded
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6821
> URL: https://issues.jboss.org/browse/WFLY-6821
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 10.0.0.Final
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Critical
>
> It is either bug in how deployments are treated or how overlay/vfs work.
> Steps to reproduce:
> 1. deploy undexploded war with jar inside
> 2. add overlay that will add non existing file in jar
> Result: exception:
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay WEB-INF/lib/overlayed.jar//META-INF/x/file.txt at WEB-INF/lib/overlayed.jar//META-INF/x/file.txt
> Caused by: java.io.FileNotFoundException: /content/shell.war/WEB-INF/lib/overlayed.jar/META-INF/x/file.txt"}}
> at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:67)
> at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:37)
> at org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayUtils.setupOverlay(OverlayUtils.java:76)
> at org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayNonExistingResourceTestCase.testOverlay(OverlayNonExistingResourceTestCase.java:67)
> Expectation:
> should work. It actually does work, if war is really exploded or
> 'if(exploded)' part in overlay is removed from overlay processor and everything is handled via: https://github.com/stuartwdouglas/wildfly-core/blob/a75af9118c4062fafb899...
> This is part of the fix of above issue, which depends on WFCORE-761.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months