[JBoss JIRA] (DROOLS-3646) [DMN Designer] Updating two files in the editor raises an error
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3646?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3646:
--------------------------------
Description:
When users update a DMN file, don't save it, and try to update another DMN file, an error appears. See the following scenarios:
*1*
!1.gif|thumbnail!
*2*
!2.gif|thumbnail!
h2. Manual PR Test
Check updating two dmn files
- Switch the file via project explorer (/)
- Switch the file clicking asset name in the toolbar (/)
was:
When users update a DMN file, don't save it, and try to update another DMN file, an error appears. See the following scenarios:
*1*
!1.gif|thumbnail!
*2*
!2.gif|thumbnail!
h2. Manual PR Test
Check updating two dmn files
- Switch the file via project explorer
- Switch the file clicking asset name in the toolbar
> [DMN Designer] Updating two files in the editor raises an error
> ---------------------------------------------------------------
>
> Key: DROOLS-3646
> URL: https://issues.jboss.org/browse/DROOLS-3646
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.18.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: 1.gif, 2.gif
>
>
> When users update a DMN file, don't save it, and try to update another DMN file, an error appears. See the following scenarios:
> *1*
> !1.gif|thumbnail!
> *2*
> !2.gif|thumbnail!
> h2. Manual PR Test
> Check updating two dmn files
> - Switch the file via project explorer (/)
> - Switch the file clicking asset name in the toolbar (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (DROOLS-3646) [DMN Designer] Updating two files in the editor raises an error
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3646?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3646:
--------------------------------
Description:
When users update a DMN file, don't save it, and try to update another DMN file, an error appears. See the following scenarios:
*1*
!1.gif|thumbnail!
*2*
!2.gif|thumbnail!
h2. Manual PR Test
Check updating two dmn files
- Switch the file via project explorer
- Switch the file clicking asset name in the toolbar
was:
When users update a DMN file, don't save it, and try to update another DMN file, an error appears. See the following scenarios:
*1*
!1.gif|thumbnail!
*2*
!2.gif|thumbnail!
> [DMN Designer] Updating two files in the editor raises an error
> ---------------------------------------------------------------
>
> Key: DROOLS-3646
> URL: https://issues.jboss.org/browse/DROOLS-3646
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.18.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: 1.gif, 2.gif
>
>
> When users update a DMN file, don't save it, and try to update another DMN file, an error appears. See the following scenarios:
> *1*
> !1.gif|thumbnail!
> *2*
> !2.gif|thumbnail!
> h2. Manual PR Test
> Check updating two dmn files
> - Switch the file via project explorer
> - Switch the file clicking asset name in the toolbar
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11722) Internal Server Error (500) when using directory-listing in FileHandler
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-11722?page=com.atlassian.jira.plugin... ]
Chao Wang commented on WFLY-11722:
----------------------------------
{quote}However, no exception is logged in the output on WildFly.{quote}
Following your steps, I see this error on WFLY 15.0.1.Final server side:
{noformat}
14:03:02,054 ERROR [io.undertow.request] (default task-1) UT005071: Undertow request failed HttpServerExchange{ GET /folder/ request {Connection=[keep-alive], Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8], Accept-Language=[en-US,en;q=0.9,zh-CN;q=0.8,zh;q=0.7], Accept-Encoding=[gzip, deflate, br], User-Agent=[Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.109 Safari/537.36], Upgrade-Insecure-Requests=[1], Host=[127.0.0.1:8080]} response {}}: java.lang.RuntimeException: java.nio.file.NoSuchFileException: /home/wangc/software/wildfly/15/wildfly-15.0.1.Final/welcome-content/folder/bad
at io.undertow.core@2.0.15.Final//io.undertow.server.handlers.resource.PathResource.getLastModified(PathResource.java:62)
at io.undertow.core@2.0.15.Final//io.undertow.server.handlers.resource.DirectoryUtils.renderDirectoryListing(DirectoryUtils.java:139)
at io.undertow.core@2.0.15.Final//io.undertow.server.handlers.resource.DirectoryUtils.renderDirectoryListing(DirectoryUtils.java:162)
at io.undertow.core@2.0.15.Final//io.undertow.server.handlers.resource.ResourceHandler$1.handleRequest(ResourceHandler.java:233)
at io.undertow.core@2.0.15.Final//io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)
at io.undertow.core@2.0.15.Final//io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.nio.file.NoSuchFileException: /home/wangc/software/wildfly/15/wildfly-15.0.1.Final/welcome-content/folder/bad
at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
at java.base/sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55)
at java.base/sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:145)
at java.base/sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:99)
at java.base/java.nio.file.Files.readAttributes(Files.java:1763)
at java.base/java.nio.file.Files.getLastModifiedTime(Files.java:2314)
at io.undertow.core@2.0.15.Final//io.undertow.server.handlers.resource.PathResource.getLastModified(PathResource.java:60)
... 10 more
{noformat}
The error is clear to me as the NoSuchFileException indicates that it tried to get last modified time from non-existent path.
> Internal Server Error (500) when using directory-listing in FileHandler
> -----------------------------------------------------------------------
>
> Key: WFLY-11722
> URL: https://issues.jboss.org/browse/WFLY-11722
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 15.0.1.Final
> Reporter: Adam Krajcik
> Assignee: Flavia Rainone
> Priority: Major
>
> When I added a bad symlink to the *welcome-content* and allowed *directory-listing* in the file handler of the *welcome-content* server returns Internal Server Error (500) when accessing the folder containing the bad symlink. However, no exception is logged in the output on WildFly.
> I also tried to use simple example application - _File Serving_ from [Undertow Examples|https://github.com/undertow-io/undertow/tree/master/examples] where I can see the following exception when accessing the directory with the bad symlink:
> {code}
> java.lang.RuntimeException: java.nio.file.NoSuchFileException: /home/akrajcik/Pictures/pictures
> at io.undertow.server.handlers.resource.PathResource.getLastModified(PathResource.java:62)
> at io.undertow.server.handlers.resource.DirectoryUtils.renderDirectoryListing(DirectoryUtils.java:139)
> at io.undertow.server.handlers.resource.DirectoryUtils.renderDirectoryListing(DirectoryUtils.java:162)
> at io.undertow.server.handlers.resource.ResourceHandler$1.handleRequest(ResourceHandler.java:233)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.lang.Thread.run(Thread.java:811)
> Caused by: java.nio.file.NoSuchFileException: /home/akrajcik/Pictures/pictures
> at sun.nio.fs.UnixException.translateToIOException(UnixException.java:98)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:114)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:119)
> at sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:67)
> at sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:156)
> at sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:111)
> at java.nio.file.Files.readAttributes(Files.java:1748)
> at java.nio.file.Files.getLastModifiedTime(Files.java:2277)
> at io.undertow.server.handlers.resource.PathResource.getLastModified(PathResource.java:60)
> ... 8 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFCORE-4329) The launcher API may incorrectly assume the JVM is a non-modular JVM
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4329?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-4329:
---------------------------------------
Note that for a JRE the {{release}} file does not exist. It's only in the JDK. This would cause Java 8 to always launch a new process to validate whether this is a modular JVM or not.
> The launcher API may incorrectly assume the JVM is a non-modular JVM
> --------------------------------------------------------------------
>
> Key: WFCORE-4329
> URL: https://issues.jboss.org/browse/WFCORE-4329
> Project: WildFly Core
> Issue Type: Bug
> Components: Launcher
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
>
> The launcher API checks the {{$JAVA_HOME/jmods}} directory and if missing assumes it's a non-modular JVM, e.g. Java 8 or lower. In some cases this directory does not exist. We need a better way to determine the JVM version.
> It's done in the wildfly-maven-plugin like:
> {code}
> /**
> * Checks to see if the {@code javaHome} is a modular JVM.
> *
> * @param javaHome the Java Home if {@code null} an attempt to discover the Java Home will be done
> *
> * @return {@code true} if this is a modular environment
> */
> public static boolean isModularJvm(final Path javaHome) {
> boolean result;
> final List<String> cmd = new ArrayList<>();
> cmd.add(getJavaCommand(javaHome));
> cmd.add("--add-modules=java.se");
> cmd.add("-version");
> final ProcessBuilder builder = new ProcessBuilder(cmd);
> Process process = null;
> Path stdout = null;
> try {
> // Create a temporary file for stdout
> stdout = Files.createTempFile("stdout", ".txt");
> process = builder.redirectErrorStream(true)
> .redirectOutput(stdout.toFile()).start();
> if (process.waitFor(1, TimeUnit.SECONDS)) {
> result = process.exitValue() == 0;
> } else {
> if (LOGGER.isDebugEnabled()) {
> LOGGER.debug(getStdoutMessage("The process timed out waiting for the response.", stdout));
> }
> result = false;
> }
> } catch (IOException | InterruptedException e) {
> if (LOGGER.isDebugEnabled()) {
> LOGGER.debug(getStdoutMessage("The process ended in error.", stdout), e);
> }
> result = false;
> } finally {
> if (process != null && process.isAlive()) {
> process.destroyForcibly();
> }
> if (stdout != null) {
> try {
> Files.deleteIfExists(stdout);
> } catch (IOException ignore) {
> }
> }
> }
> return result;
> }
> {code}
> This works, however requires a new process to be created and launched which is not ideal.
> It does look like there might be a {{$JAVA_HOME/release}} file which looks like a properties file with the {{JAVA_VERSION}} property. However we need to determine if all vendors include this file.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11031) Json encoding of Access Log Events
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11031?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-11031:
--------------------------------------
Proposal document https://github.com/wildfly/wildfly-proposals/pull/176
> 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: James Perkins
> 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.12.1#712002)
5 years, 7 months