[JBoss JIRA] (DROOLS-2922) CSS: Pop-over menu for DMN decision tables.
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2922?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2922:
-----------------------------------
Sprint: 2018 Week 39-41 (was: 2018 Week 36-38)
> CSS: Pop-over menu for DMN decision tables.
> -------------------------------------------
>
> Key: DROOLS-2922
> URL: https://issues.jboss.org/browse/DROOLS-2922
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, pop-overc.png, pop-overcSpecs.png, select.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases from the DMN canvas view, as a user I want to:
> * Search a list of available data types from a decision table, as part of an input/selection process.
> * Select a data type inline from a decision table.
> * Have a means to rename the Decision (node.)
> * Have a means to access the Manage Data Types dialog.
> Notes:
> Design requires a Pop-over, which includes:
> * Form field labels for usability (context) and accessibility.
> * Variant 1 of the PF pop-over patterns, which supports a the pop-up title.
> * Drop down component with Live Search
> * "Manage" link opens a dialog.
> * Pop-up is initiated by a single-left mouse click within the respective decision table cell.
> * Design needs to be reasonably consistent with Stunner and PF components.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-1905) Use of the "%" sign in the title
by Enrique González Martínez (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1905?page=com.atlassian.jira.plugi... ]
Enrique González Martínez commented on DROOLS-1905:
---------------------------------------------------
I think i got this. The problem is the incosistence generated by dealing with the memory file system.
the one doing the transformation should be the compilation unit (EJC) as it is the adapter regarding to the FS.
> Use of the "%" sign in the title
> --------------------------------
>
> Key: DROOLS-1905
> URL: https://issues.jboss.org/browse/DROOLS-1905
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Affects Versions: 6.5.0.Final
> Reporter: Petr Farmakovsky
> Assignee: Enrique González Martínez
> Labels: drools-tools
> Attachments: 14-12-2016 19-28-17.gif
>
>
> When you save rules or other objects Drools Workbench allows the use of the "%" sign in the title. Opening of any rule results in an error if there is an object with title containing "%" sign in the repository.
> It is impossible to build and publish the project.
> Error message: URLDecoder: Illegal hex characters in escape (%) pattern - For input string: "s."
> !14-12-2016 19-28-17.gif!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2922) CSS: Pop-over menu for DMN decision tables.
by Sarah Rambacher (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2922?page=com.atlassian.jira.plugi... ]
Sarah Rambacher reassigned DROOLS-2922:
---------------------------------------
Assignee: Michael Anstis (was: Sarah Rambacher)
> CSS: Pop-over menu for DMN decision tables.
> -------------------------------------------
>
> Key: DROOLS-2922
> URL: https://issues.jboss.org/browse/DROOLS-2922
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, pop-overc.png, pop-overcSpecs.png, select.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases from the DMN canvas view, as a user I want to:
> * Search a list of available data types from a decision table, as part of an input/selection process.
> * Select a data type inline from a decision table.
> * Have a means to rename the Decision (node.)
> * Have a means to access the Manage Data Types dialog.
> Notes:
> Design requires a Pop-over, which includes:
> * Form field labels for usability (context) and accessibility.
> * Variant 1 of the PF pop-over patterns, which supports a the pop-up title.
> * Drop down component with Live Search
> * "Manage" link opens a dialog.
> * Pop-up is initiated by a single-left mouse click within the respective decision table cell.
> * Design needs to be reasonably consistent with Stunner and PF components.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11031) Json encoding of Access Log Events
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-11031?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-11031:
-----------------------------------------
Thanks [~fschmager] for the report. JSON logging is something we've been thinking about in the background a bit all summer and this is good input. An access log is different from a general server log in that the message has a usable structure. It seems obvious now that you mentioned it!
IIRC there may be a consumer side issue of some sort with nested structures; i.e. reading a "message" field that is itself complex JSON structure as opposed to a simple string. But I could be misremembering or that whatever is was might be fixed. We'll find out when this gets taken up.
> Json encoding of Access Log Events
> ----------------------------------
>
> Key: WFLY-11031
> URL: https://issues.jboss.org/browse/WFLY-11031
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Frank Schmager
> Assignee: Stuart Douglas
> Priority: Minor
>
> h1. Request
> It should be possible to emit access log events json encoded to allow log aggregation systems to ingest pre-parsed events for filtering and analytics.
> h1. Background
> Application logs can be emitted [json encoded|https://wildscribe.github.io/WildFly/13.0/subsystem/logging/json-formatter/index.html] allowing log aggregation systems like logstash/ELK to ingest and parse the events. This is especially important when working with containers, but anything requiring log aggregation would benefit. Not all log aggregation systems allow after-the-fact parsing of log events (e.g. Kibana) and developers don't have access to the log aggregator to install a parser like logstash/filebeat.
> [Access log events|https://wildscribe.github.io/WildFly/13.0/subsystem/undertow/server/host/setting/access-log/index.html], however, can't be json encoded. The whole log event can be, but what's important about access log events can't.
> h2. Example result
> There are many ways to encode the event into json. Ideally it would be configurable. One way would be to use {{message}}, but instead of it just containing a {{String}} it could contain json. However, abusing the {{message}} field might not work because it is of type {{String|text}}. So even if it contained valid json, it wouldn't be processed as such. Separate fields might need to be used. Using {{message}} is probably preferred because if not, what else would that field contain?
> {code:json}
> ...
> "@timestamp": "2018-09-14T20:59:37.530Z",
> ...
> "message": {
> "x-forwarded-for": "-",
> "remoteHost": "172.20.2.1",
> ...
> }
> ...
> # alternatively
> "x-forwarded-for": "-",
> "remoteHost": "172.20.2.1",
> "remoteUser": "200",
> "dateTime": "[14/Sep/2018:20:59:37 +0000]",
> "requestLine": "GET /auth/resources/4.4.0.final/login/keycloak/img/keycloak-bg.png HTTP/2.0",
> "status": "200",
> "bytesSent": "81862",
> "timeTaken": "10",
> "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36"
> ...
> {code}
> h2. Attempted Workaround
> Making the pattern look like json failed due to double quote escaping:
> {code:xml}
> <access-log pattern='{\"x-forwarded-for\":\"%{i,X-Forwarded-For}\",\"remoteHost\":\"%h\",\"remoteUser\":\"%s\",\"dateTime\":\"%t\",\"requestLine\":\"%r\",\"status\":\"%s\",\"bytesSent\":\"%b\",\"timeTaken\":\"%D\",\"userAgent\":\"%{i,User-Agent}\"}' use-server-log="true" />
> {code}
> h3. Result
> {code}
> ...
> "@timestamp": "2018-09-14T20:59:37.530Z",
> ...
> "message": "{\\\"x-forwarded-for\\\":\\\"-\\\",\\\"remoteHost\\\":\\\"172.20.2.1\\\",\\\"remoteUser\\\":\\\"200\\\",\\\"dateTime\\\":\\\"[14/Sep/2018:20:59:37 +0000]\\\",\\\"requestLine\\\":\\\"GET /auth/resources/4.4.0.final/login/keycloak/img/keycloak-bg.png HTTP/2.0\\\",\\\"status\\\":\\\"200\\\",\\\"bytesSent\\\":\\\"81862\\\",\\\"timeTaken\\\":\\\"10\\\",\\\"userAgent\\\":\\\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36\\\"}",
> {code}
> h2. Json formatting log configuration
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:logging:5.0">
> <console-handler name="CONSOLE">
> <level name="DEBUG"/>
> <formatter>
> <named-formatter name="JSON_FORMATTER"/>
> </formatter>
> </console-handler>
> ...
> <formatter name="JSON_FORMATTER">
> <json-formatter>
> <exception-output-type value="formatted"/>
> <key-overrides timestamp="@timestamp" loggerName="logger_name"/>
> <meta-data>
> <property name="@version" value="1"/>
> </meta-data>
> </json-formatter>
> </formatter>
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11031) Json encoding of Access Log Events
by Frank Schmager (JIRA)
[ https://issues.jboss.org/browse/WFLY-11031?page=com.atlassian.jira.plugin... ]
Frank Schmager commented on WFLY-11031:
---------------------------------------
[~brian.stansberry] No worries. Rename to your heart's content. I tried to be explicit and detailed in my description. It's all about the content of the access log {{message}} to be "json"-ed. It's no good having a standard {{127.0.0.1 - peter [9/Feb/2017:10:34:12 -0700] "GET /sample-image.png HTTP/2" 200 1479}} in {{message}}. Kibana doesn't support after-the-fact parsing so I can't analyze access log things. I need the individual components (remote host, bytes sent, status etc) as fields in json.
> Json encoding of Access Log Events
> ----------------------------------
>
> Key: WFLY-11031
> URL: https://issues.jboss.org/browse/WFLY-11031
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Frank Schmager
> Assignee: Stuart Douglas
> Priority: Minor
>
> h1. Request
> It should be possible to emit access log events json encoded to allow log aggregation systems to ingest pre-parsed events for filtering and analytics.
> h1. Background
> Application logs can be emitted [json encoded|https://wildscribe.github.io/WildFly/13.0/subsystem/logging/json-formatter/index.html] allowing log aggregation systems like logstash/ELK to ingest and parse the events. This is especially important when working with containers, but anything requiring log aggregation would benefit. Not all log aggregation systems allow after-the-fact parsing of log events (e.g. Kibana) and developers don't have access to the log aggregator to install a parser like logstash/filebeat.
> [Access log events|https://wildscribe.github.io/WildFly/13.0/subsystem/undertow/server/host/setting/access-log/index.html], however, can't be json encoded. The whole log event can be, but what's important about access log events can't.
> h2. Example result
> There are many ways to encode the event into json. Ideally it would be configurable. One way would be to use {{message}}, but instead of it just containing a {{String}} it could contain json. However, abusing the {{message}} field might not work because it is of type {{String|text}}. So even if it contained valid json, it wouldn't be processed as such. Separate fields might need to be used. Using {{message}} is probably preferred because if not, what else would that field contain?
> {code:json}
> ...
> "@timestamp": "2018-09-14T20:59:37.530Z",
> ...
> "message": {
> "x-forwarded-for": "-",
> "remoteHost": "172.20.2.1",
> ...
> }
> ...
> # alternatively
> "x-forwarded-for": "-",
> "remoteHost": "172.20.2.1",
> "remoteUser": "200",
> "dateTime": "[14/Sep/2018:20:59:37 +0000]",
> "requestLine": "GET /auth/resources/4.4.0.final/login/keycloak/img/keycloak-bg.png HTTP/2.0",
> "status": "200",
> "bytesSent": "81862",
> "timeTaken": "10",
> "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36"
> ...
> {code}
> h2. Attempted Workaround
> Making the pattern look like json failed due to double quote escaping:
> {code:xml}
> <access-log pattern='{\"x-forwarded-for\":\"%{i,X-Forwarded-For}\",\"remoteHost\":\"%h\",\"remoteUser\":\"%s\",\"dateTime\":\"%t\",\"requestLine\":\"%r\",\"status\":\"%s\",\"bytesSent\":\"%b\",\"timeTaken\":\"%D\",\"userAgent\":\"%{i,User-Agent}\"}' use-server-log="true" />
> {code}
> h3. Result
> {code}
> ...
> "@timestamp": "2018-09-14T20:59:37.530Z",
> ...
> "message": "{\\\"x-forwarded-for\\\":\\\"-\\\",\\\"remoteHost\\\":\\\"172.20.2.1\\\",\\\"remoteUser\\\":\\\"200\\\",\\\"dateTime\\\":\\\"[14/Sep/2018:20:59:37 +0000]\\\",\\\"requestLine\\\":\\\"GET /auth/resources/4.4.0.final/login/keycloak/img/keycloak-bg.png HTTP/2.0\\\",\\\"status\\\":\\\"200\\\",\\\"bytesSent\\\":\\\"81862\\\",\\\"timeTaken\\\":\\\"10\\\",\\\"userAgent\\\":\\\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36\\\"}",
> {code}
> h2. Json formatting log configuration
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:logging:5.0">
> <console-handler name="CONSOLE">
> <level name="DEBUG"/>
> <formatter>
> <named-formatter name="JSON_FORMATTER"/>
> </formatter>
> </console-handler>
> ...
> <formatter name="JSON_FORMATTER">
> <json-formatter>
> <exception-output-type value="formatted"/>
> <key-overrides timestamp="@timestamp" loggerName="logger_name"/>
> <meta-data>
> <property name="@version" value="1"/>
> </meta-data>
> </json-formatter>
> </formatter>
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2975) Unable to create a new project in KIE workbench 7.8.0 release onwards
by Senthil Kumar Kamaraj (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2975?page=com.atlassian.jira.plugi... ]
Senthil Kumar Kamaraj commented on DROOLS-2975:
-----------------------------------------------
Hi Mario,
Have you merged the fix for this issue. If yes, please specify the change id / commit id (fix details). So that, we will try to include the fix manually in 7.11 and unblock the current situation.
Thanks
Senthil
> Unable to create a new project in KIE workbench 7.8.0 release onwards
> ---------------------------------------------------------------------
>
> Key: DROOLS-2975
> URL: https://issues.jboss.org/browse/DROOLS-2975
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.8.0.Final, 7.9.0.Final, 7.10.0.Final
> Reporter: Senthil Kumar Kamaraj
> Assignee: Mario Fusco
> Priority: Blocker
>
> We have deployed KIE Workbench on Wildfly 11.
> We are unable to create a new project in the KIE workbench, it is throwing the below error
> Unable to complete your request. The following exception occurred: org.appformer.maven.integration.embedder.MavenEmbedderException: Failed to read artifact descriptor for com.thoughtworks.xstream:xstream:jar:1.4.10.
> The maven home is set properly and settings.xml is placed in maven home.
> The issue is there from KIE Workbench 7.8.0 release onwards.
> For more info, please refer the link below
> https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11031) Json encoding of Access Log Events
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-11031?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-11031:
-----------------------------------------
[~fschmager] I hope you don't mind that I changed the title of this slightly. Access logs can be JSON encoded, as you stated, but you're looking for another level. I saw the original title and thought "we support that already."
[~jamezp] FYI.
> Json encoding of Access Log Events
> ----------------------------------
>
> Key: WFLY-11031
> URL: https://issues.jboss.org/browse/WFLY-11031
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Frank Schmager
> Assignee: Stuart Douglas
> Priority: Minor
>
> h1. Request
> It should be possible to emit access log events json encoded to allow log aggregation systems to ingest pre-parsed events for filtering and analytics.
> h1. Background
> Application logs can be emitted [json encoded|https://wildscribe.github.io/WildFly/13.0/subsystem/logging/json-formatter/index.html] allowing log aggregation systems like logstash/ELK to ingest and parse the events. This is especially important when working with containers, but anything requiring log aggregation would benefit. Not all log aggregation systems allow after-the-fact parsing of log events (e.g. Kibana) and developers don't have access to the log aggregator to install a parser like logstash/filebeat.
> [Access log events|https://wildscribe.github.io/WildFly/13.0/subsystem/undertow/server/host/setting/access-log/index.html], however, can't be json encoded. The whole log event can be, but what's important about access log events can't.
> h2. Example result
> There are many ways to encode the event into json. Ideally it would be configurable. One way would be to use {{message}}, but instead of it just containing a {{String}} it could contain json. However, abusing the {{message}} field might not work because it is of type {{String|text}}. So even if it contained valid json, it wouldn't be processed as such. Separate fields might need to be used. Using {{message}} is probably preferred because if not, what else would that field contain?
> {code:json}
> ...
> "@timestamp": "2018-09-14T20:59:37.530Z",
> ...
> "message": {
> "x-forwarded-for": "-",
> "remoteHost": "172.20.2.1",
> ...
> }
> ...
> # alternatively
> "x-forwarded-for": "-",
> "remoteHost": "172.20.2.1",
> "remoteUser": "200",
> "dateTime": "[14/Sep/2018:20:59:37 +0000]",
> "requestLine": "GET /auth/resources/4.4.0.final/login/keycloak/img/keycloak-bg.png HTTP/2.0",
> "status": "200",
> "bytesSent": "81862",
> "timeTaken": "10",
> "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36"
> ...
> {code}
> h2. Attempted Workaround
> Making the pattern look like json failed due to double quote escaping:
> {code:xml}
> <access-log pattern='{\"x-forwarded-for\":\"%{i,X-Forwarded-For}\",\"remoteHost\":\"%h\",\"remoteUser\":\"%s\",\"dateTime\":\"%t\",\"requestLine\":\"%r\",\"status\":\"%s\",\"bytesSent\":\"%b\",\"timeTaken\":\"%D\",\"userAgent\":\"%{i,User-Agent}\"}' use-server-log="true" />
> {code}
> h3. Result
> {code}
> ...
> "@timestamp": "2018-09-14T20:59:37.530Z",
> ...
> "message": "{\\\"x-forwarded-for\\\":\\\"-\\\",\\\"remoteHost\\\":\\\"172.20.2.1\\\",\\\"remoteUser\\\":\\\"200\\\",\\\"dateTime\\\":\\\"[14/Sep/2018:20:59:37 +0000]\\\",\\\"requestLine\\\":\\\"GET /auth/resources/4.4.0.final/login/keycloak/img/keycloak-bg.png HTTP/2.0\\\",\\\"status\\\":\\\"200\\\",\\\"bytesSent\\\":\\\"81862\\\",\\\"timeTaken\\\":\\\"10\\\",\\\"userAgent\\\":\\\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36\\\"}",
> {code}
> h2. Json formatting log configuration
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:logging:5.0">
> <console-handler name="CONSOLE">
> <level name="DEBUG"/>
> <formatter>
> <named-formatter name="JSON_FORMATTER"/>
> </formatter>
> </console-handler>
> ...
> <formatter name="JSON_FORMATTER">
> <json-formatter>
> <exception-output-type value="formatted"/>
> <key-overrides timestamp="@timestamp" loggerName="logger_name"/>
> <meta-data>
> <property name="@version" value="1"/>
> </meta-data>
> </json-formatter>
> </formatter>
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11031) Json encoding of Access Log Events
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-11031?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11031:
------------------------------------
Summary: Json encoding of Access Log Events (was: Json encoding of Access Logs)
> Json encoding of Access Log Events
> ----------------------------------
>
> Key: WFLY-11031
> URL: https://issues.jboss.org/browse/WFLY-11031
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Frank Schmager
> Assignee: Stuart Douglas
> Priority: Minor
>
> h1. Request
> It should be possible to emit access log events json encoded to allow log aggregation systems to ingest pre-parsed events for filtering and analytics.
> h1. Background
> Application logs can be emitted [json encoded|https://wildscribe.github.io/WildFly/13.0/subsystem/logging/json-formatter/index.html] allowing log aggregation systems like logstash/ELK to ingest and parse the events. This is especially important when working with containers, but anything requiring log aggregation would benefit. Not all log aggregation systems allow after-the-fact parsing of log events (e.g. Kibana) and developers don't have access to the log aggregator to install a parser like logstash/filebeat.
> [Access log events|https://wildscribe.github.io/WildFly/13.0/subsystem/undertow/server/host/setting/access-log/index.html], however, can't be json encoded. The whole log event can be, but what's important about access log events can't.
> h2. Example result
> There are many ways to encode the event into json. Ideally it would be configurable. One way would be to use {{message}}, but instead of it just containing a {{String}} it could contain json. However, abusing the {{message}} field might not work because it is of type {{String|text}}. So even if it contained valid json, it wouldn't be processed as such. Separate fields might need to be used. Using {{message}} is probably preferred because if not, what else would that field contain?
> {code:json}
> ...
> "@timestamp": "2018-09-14T20:59:37.530Z",
> ...
> "message": {
> "x-forwarded-for": "-",
> "remoteHost": "172.20.2.1",
> ...
> }
> ...
> # alternatively
> "x-forwarded-for": "-",
> "remoteHost": "172.20.2.1",
> "remoteUser": "200",
> "dateTime": "[14/Sep/2018:20:59:37 +0000]",
> "requestLine": "GET /auth/resources/4.4.0.final/login/keycloak/img/keycloak-bg.png HTTP/2.0",
> "status": "200",
> "bytesSent": "81862",
> "timeTaken": "10",
> "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36"
> ...
> {code}
> h2. Attempted Workaround
> Making the pattern look like json failed due to double quote escaping:
> {code:xml}
> <access-log pattern='{\"x-forwarded-for\":\"%{i,X-Forwarded-For}\",\"remoteHost\":\"%h\",\"remoteUser\":\"%s\",\"dateTime\":\"%t\",\"requestLine\":\"%r\",\"status\":\"%s\",\"bytesSent\":\"%b\",\"timeTaken\":\"%D\",\"userAgent\":\"%{i,User-Agent}\"}' use-server-log="true" />
> {code}
> h3. Result
> {code}
> ...
> "@timestamp": "2018-09-14T20:59:37.530Z",
> ...
> "message": "{\\\"x-forwarded-for\\\":\\\"-\\\",\\\"remoteHost\\\":\\\"172.20.2.1\\\",\\\"remoteUser\\\":\\\"200\\\",\\\"dateTime\\\":\\\"[14/Sep/2018:20:59:37 +0000]\\\",\\\"requestLine\\\":\\\"GET /auth/resources/4.4.0.final/login/keycloak/img/keycloak-bg.png HTTP/2.0\\\",\\\"status\\\":\\\"200\\\",\\\"bytesSent\\\":\\\"81862\\\",\\\"timeTaken\\\":\\\"10\\\",\\\"userAgent\\\":\\\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36\\\"}",
> {code}
> h2. Json formatting log configuration
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:logging:5.0">
> <console-handler name="CONSOLE">
> <level name="DEBUG"/>
> <formatter>
> <named-formatter name="JSON_FORMATTER"/>
> </formatter>
> </console-handler>
> ...
> <formatter name="JSON_FORMATTER">
> <json-formatter>
> <exception-output-type value="formatted"/>
> <key-overrides timestamp="@timestamp" loggerName="logger_name"/>
> <meta-data>
> <property name="@version" value="1"/>
> </meta-data>
> </json-formatter>
> </formatter>
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFCORE-4116) JDK 10: illegal reflective access
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4116?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-4116:
-------------------------------------
Component/s: Server
> JDK 10: illegal reflective access
> ---------------------------------
>
> Key: WFCORE-4116
> URL: https://issues.jboss.org/browse/WFCORE-4116
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Affects Versions: 6.0.0.Final, 6.0.2.Final
> Reporter: Thorsten Moeller
> Assignee: Jason Greene
>
> Using WF14 and Oracle JDK 10.0.2, there is an illegal reflective access warning while WF boots:
> {code}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.as.server.deployment.reflect.ClassReflectionIndex (jar:file:/Users/.../wildfly-14.0.0.Final/modules/system/layers/base/org/jboss/as/server/main/wildfly-server-6.0.1.Final.jar!/) to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of org.jboss.as.server.deployment.reflect.ClassReflectionIndex
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFCORE-4116) JDK 10: illegal reflective access
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4116?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved WFLY-11032 to WFCORE-4116:
-------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-4116 (was: WFLY-11032)
Affects Version/s: 6.0.2.Final
6.0.0.Final
(was: 14.0.0.Final)
> JDK 10: illegal reflective access
> ---------------------------------
>
> Key: WFCORE-4116
> URL: https://issues.jboss.org/browse/WFCORE-4116
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 6.0.2.Final, 6.0.0.Final
> Reporter: Thorsten Moeller
> Assignee: Jason Greene
>
> Using WF14 and Oracle JDK 10.0.2, there is an illegal reflective access warning while WF boots:
> {code}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.as.server.deployment.reflect.ClassReflectionIndex (jar:file:/Users/.../wildfly-14.0.0.Final/modules/system/layers/base/org/jboss/as/server/main/wildfly-server-6.0.1.Final.jar!/) to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of org.jboss.as.server.deployment.reflect.ClassReflectionIndex
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months