[JBoss JIRA] (WFLY-12071) Internal Server Error when RuntimeName differs from war name
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12071?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-12071:
---------------------------------
Description:
If i deploy my war with a RunitmeName different from war name i can't access to metrics anymore
{code}
16:41:10,034 ERROR [org.jboss.as.controller.management-operation] (management I/O-2) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
("deployment" => "Service.war"),
("subsystem" => "jpa"),
("hibernate-persistence-unit" => "Service.war#ServicePU")
]) - failure description: "WFLYCTL0216: Management resource '[(\"deployment\" => \"Service.war\")]' not found"
16:41:10,036 ERROR [io.undertow.request] (management I/O-2) UT005071: Undertow request failed HttpServerExchange{ GET /metrics request {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8], Accept-Language=[fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3], Cache-Control=[max-age=0], Accept-Encoding=[gzip, deflate], User-Agent=[Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0], Connection=[keep-alive], Authorization=[Digest username="admin", realm="ManagementRealm", nonce="AAAAAwACPO8QTKglHGxK75nH/tWEJNwZnyss0vGY7w35xUfiKxWDJ20sgiE=", uri="/metrics", algorithm=MD5, response="b4f94dcefe97de8c2d57cff48469ad59", opaque="00000000000000000000000000000000", qop=auth, nc=00000011, cnonce="341c28b0026477d6"], Cookie=[__utma=111872281.212550125.1524648661.1555397901.1555580515.57; __utmz=111872281.1524648661.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); _ga=GA1.1.212550125.1524648661; _gid=GA1.1.374185288.1557750159; __utmc=111872281], Upgrade-Insecure-Requests=[1], Host=[localhost:9990]} response {Access-Control-Allow-Origin=[*], Access-Control-Allow-Headers=[origin, content-type, accept, authorization], Access-Control-Allow-Credentials=[true], Content-Type=[text/plain], Access-Control-Allow-Methods=[GET, POST, PUT, DELETE, OPTIONS, HEAD], Access-Control-Max-Age=[1209600]}}: java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute second-level-cache-hit-count on [
("subsystem" => "jpa"),
("hibernate-persistence-unit" => "Service.war#ServicePU")
]: "WFLYCTL0216: Management resource '[(\"deployment\" => \"Service.war\")]' not found".
at org.wildfly.extension.microprofile.metrics.MetricCollector.lambda$collectResourceMetrics0$0(MetricCollector.java:143)
at org.wildfly.extension.microprofile.metrics.PrometheusCollector.collect(PrometheusCollector.java:51)
at io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.findNextElement(CollectorRegistry.java:183)
at io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.<init>(CollectorRegistry.java:147)
at io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.<init>(CollectorRegistry.java:168)
at io.prometheus.client.CollectorRegistry.metricFamilySamples(CollectorRegistry.java:130)
at org.wildfly.extension.microprofile.metrics.MetricsContextService$1.handleRequest(MetricsContextService.java:100)
at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51)
at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35)
at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91)
at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211)
at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92)
at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78)
at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49)
at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57)
at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75)
at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:662)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364)
at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:162)
at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:100)
at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:57)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291)
at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:131)
at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
{code}
was:
If i deploy my war with a RunitmeName different from war name i can't access to metrics anymore
16:41:10,034 ERROR [org.jboss.as.controller.management-operation] (management I/O-2) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
("deployment" => "Service.war"),
("subsystem" => "jpa"),
("hibernate-persistence-unit" => "Service.war#ServicePU")
]) - failure description: "WFLYCTL0216: Management resource '[(\"deployment\" => \"Service.war\")]' not found"
16:41:10,036 ERROR [io.undertow.request] (management I/O-2) UT005071: Undertow request failed HttpServerExchange{ GET /metrics request {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8], Accept-Language=[fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3], Cache-Control=[max-age=0], Accept-Encoding=[gzip, deflate], User-Agent=[Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0], Connection=[keep-alive], Authorization=[Digest username="admin", realm="ManagementRealm", nonce="AAAAAwACPO8QTKglHGxK75nH/tWEJNwZnyss0vGY7w35xUfiKxWDJ20sgiE=", uri="/metrics", algorithm=MD5, response="b4f94dcefe97de8c2d57cff48469ad59", opaque="00000000000000000000000000000000", qop=auth, nc=00000011, cnonce="341c28b0026477d6"], Cookie=[__utma=111872281.212550125.1524648661.1555397901.1555580515.57; __utmz=111872281.1524648661.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); _ga=GA1.1.212550125.1524648661; _gid=GA1.1.374185288.1557750159; __utmc=111872281], Upgrade-Insecure-Requests=[1], Host=[localhost:9990]} response {Access-Control-Allow-Origin=[*], Access-Control-Allow-Headers=[origin, content-type, accept, authorization], Access-Control-Allow-Credentials=[true], Content-Type=[text/plain], Access-Control-Allow-Methods=[GET, POST, PUT, DELETE, OPTIONS, HEAD], Access-Control-Max-Age=[1209600]}}: java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute second-level-cache-hit-count on [
("subsystem" => "jpa"),
("hibernate-persistence-unit" => "Service.war#ServicePU")
]: "WFLYCTL0216: Management resource '[(\"deployment\" => \"Service.war\")]' not found".
at org.wildfly.extension.microprofile.metrics.MetricCollector.lambda$collectResourceMetrics0$0(MetricCollector.java:143)
at org.wildfly.extension.microprofile.metrics.PrometheusCollector.collect(PrometheusCollector.java:51)
at io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.findNextElement(CollectorRegistry.java:183)
at io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.<init>(CollectorRegistry.java:147)
at io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.<init>(CollectorRegistry.java:168)
at io.prometheus.client.CollectorRegistry.metricFamilySamples(CollectorRegistry.java:130)
at org.wildfly.extension.microprofile.metrics.MetricsContextService$1.handleRequest(MetricsContextService.java:100)
at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51)
at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35)
at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91)
at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211)
at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92)
at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78)
at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49)
at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57)
at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75)
at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:662)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364)
at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:162)
at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:100)
at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:57)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291)
at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:131)
at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
> Internal Server Error when RuntimeName differs from war name
> ------------------------------------------------------------
>
> Key: WFLY-12071
> URL: https://issues.jboss.org/browse/WFLY-12071
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Affects Versions: 16.0.0.Final
> Reporter: Maximilien Wiktorowski
> Assignee: Michal Petrov
> Priority: Major
>
> If i deploy my war with a RunitmeName different from war name i can't access to metrics anymore
> {code}
> 16:41:10,034 ERROR [org.jboss.as.controller.management-operation] (management I/O-2) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("deployment" => "Service.war"),
> ("subsystem" => "jpa"),
> ("hibernate-persistence-unit" => "Service.war#ServicePU")
> ]) - failure description: "WFLYCTL0216: Management resource '[(\"deployment\" => \"Service.war\")]' not found"
> 16:41:10,036 ERROR [io.undertow.request] (management I/O-2) UT005071: Undertow request failed HttpServerExchange{ GET /metrics request {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8], Accept-Language=[fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3], Cache-Control=[max-age=0], Accept-Encoding=[gzip, deflate], User-Agent=[Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0], Connection=[keep-alive], Authorization=[Digest username="admin", realm="ManagementRealm", nonce="AAAAAwACPO8QTKglHGxK75nH/tWEJNwZnyss0vGY7w35xUfiKxWDJ20sgiE=", uri="/metrics", algorithm=MD5, response="b4f94dcefe97de8c2d57cff48469ad59", opaque="00000000000000000000000000000000", qop=auth, nc=00000011, cnonce="341c28b0026477d6"], Cookie=[__utma=111872281.212550125.1524648661.1555397901.1555580515.57; __utmz=111872281.1524648661.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); _ga=GA1.1.212550125.1524648661; _gid=GA1.1.374185288.1557750159; __utmc=111872281], Upgrade-Insecure-Requests=[1], Host=[localhost:9990]} response {Access-Control-Allow-Origin=[*], Access-Control-Allow-Headers=[origin, content-type, accept, authorization], Access-Control-Allow-Credentials=[true], Content-Type=[text/plain], Access-Control-Allow-Methods=[GET, POST, PUT, DELETE, OPTIONS, HEAD], Access-Control-Max-Age=[1209600]}}: java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute second-level-cache-hit-count on [
> ("subsystem" => "jpa"),
> ("hibernate-persistence-unit" => "Service.war#ServicePU")
> ]: "WFLYCTL0216: Management resource '[(\"deployment\" => \"Service.war\")]' not found".
> at org.wildfly.extension.microprofile.metrics.MetricCollector.lambda$collectResourceMetrics0$0(MetricCollector.java:143)
> at org.wildfly.extension.microprofile.metrics.PrometheusCollector.collect(PrometheusCollector.java:51)
> at io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.findNextElement(CollectorRegistry.java:183)
> at io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.<init>(CollectorRegistry.java:147)
> at io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.<init>(CollectorRegistry.java:168)
> at io.prometheus.client.CollectorRegistry.metricFamilySamples(CollectorRegistry.java:130)
> at org.wildfly.extension.microprofile.metrics.MetricsContextService$1.handleRequest(MetricsContextService.java:100)
> at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51)
> at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35)
> at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91)
> at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211)
> at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92)
> at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78)
> at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49)
> at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57)
> at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75)
> at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:662)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364)
> at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:162)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:100)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:57)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:131)
> at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (LOGMGR-254) JDK11, Warning when starting WildFly with logmanager in bootclasspath
by James Perkins (Jira)
[ https://issues.jboss.org/browse/LOGMGR-254?page=com.atlassian.jira.plugin... ]
James Perkins commented on LOGMGR-254:
--------------------------------------
One option would be that we split the logger finder out to it's own maven module. I'm not sure if this is a good idea or not for a micro release, but it would be possible to do.
> JDK11, Warning when starting WildFly with logmanager in bootclasspath
> ---------------------------------------------------------------------
>
> Key: LOGMGR-254
> URL: https://issues.jboss.org/browse/LOGMGR-254
> Project: JBoss Log Manager
> Issue Type: Bug
> Reporter: Jean Francois Denise
> Assignee: James Perkins
> Priority: Major
>
> Using JDK11, add the following property when starting standalone.sh:
> {code}
> -Djboss.modules.system.pkgs=org.jboss.logmanager
> -Xbootclasspath/a:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.10.Final.jar:$JBOSS_HOME/modules/system/layers/base/org/wildfly/common/main/wildfly-common-1.5.1.Final.jar
> -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dsun.util.logging.disableCallerCheck=true
> {code}
> You will notice the following warning:
> {code}
> May 15, 2019 4:49:11 PM java.lang.System$LoggerFinder lambda$accessProvider$0
> WARNING: Failed to instantiate LoggerFinder provider; Using default.
> {code}
> To display the root cause add:
> {{-Djdk.logger.finder.error=ERROR}}
> Changing the {{standalone.conf}} to the following should show the warning:
> {code}
> if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then
> JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman"
> fi
> JBOSS_MODULES_SYSTEM_PKGS="org.jboss.logmanager,jdk.nashorn.api,com.sun.crypto.provider,$JBOSS_MODULES_SYSTEM_PKGS"
> if [ "x$JAVA_OPTS" = "x" ]; then
> JAVA_OPTS="-Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true"
> JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
> else
> echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"
> fi
> BOOT_CP=()
> BOOT_CP=("$(find $JBOSS_HOME/modules -type f -name "jboss-logmanager-*.jar")")
> BOOT_CP+=("$(find $JBOSS_HOME/modules -type f -name "wildfly-common*.jar")")
> for f in $(find $JBOSS_HOME/modules -type f -name "javax.json-*.jar"); do
> BOOT_CP+=("$f")
> done
> x="-Xbootclasspath/a"
> for p in "${BOOT_CP[@]}"; do
> x+=":$p"
> done
> JAVA_OPTS="-Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dsun.util.logging.disableCallerCheck=true $x $JAVA_OPTS"
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (LOGMGR-254) JDK11, Warning when starting WildFly with logmanager in bootclasspath
by James Perkins (Jira)
[ https://issues.jboss.org/browse/LOGMGR-254?page=com.atlassian.jira.plugin... ]
James Perkins commented on LOGMGR-254:
--------------------------------------
I'm going to leave this open for now however there isn't much we can do about it unless we no longer want to provide a {{java.lang.System.LoggerProvider}}. The reason is the current JAR is a MR JAR with the base being Java 8. In the Java portion we have a {{org.jboss.logmanager.JBossLoggerProvider}} and a {{META-INF/services/java.lang.System$LoggerProvider}}. In normal situations this works fine, however the boot class path does not support MR JAR's so this warning is printed.
> JDK11, Warning when starting WildFly with logmanager in bootclasspath
> ---------------------------------------------------------------------
>
> Key: LOGMGR-254
> URL: https://issues.jboss.org/browse/LOGMGR-254
> Project: JBoss Log Manager
> Issue Type: Bug
> Reporter: Jean Francois Denise
> Assignee: James Perkins
> Priority: Major
>
> Using JDK11, add the following property when starting standalone.sh:
> {code}
> -Djboss.modules.system.pkgs=org.jboss.logmanager
> -Xbootclasspath/a:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.10.Final.jar:$JBOSS_HOME/modules/system/layers/base/org/wildfly/common/main/wildfly-common-1.5.1.Final.jar
> -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dsun.util.logging.disableCallerCheck=true
> {code}
> You will notice the following warning:
> {code}
> May 15, 2019 4:49:11 PM java.lang.System$LoggerFinder lambda$accessProvider$0
> WARNING: Failed to instantiate LoggerFinder provider; Using default.
> {code}
> To display the root cause add:
> {{-Djdk.logger.finder.error=ERROR}}
> Changing the {{standalone.conf}} to the following should show the warning:
> {code}
> if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then
> JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman"
> fi
> JBOSS_MODULES_SYSTEM_PKGS="org.jboss.logmanager,jdk.nashorn.api,com.sun.crypto.provider,$JBOSS_MODULES_SYSTEM_PKGS"
> if [ "x$JAVA_OPTS" = "x" ]; then
> JAVA_OPTS="-Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true"
> JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
> else
> echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"
> fi
> BOOT_CP=()
> BOOT_CP=("$(find $JBOSS_HOME/modules -type f -name "jboss-logmanager-*.jar")")
> BOOT_CP+=("$(find $JBOSS_HOME/modules -type f -name "wildfly-common*.jar")")
> for f in $(find $JBOSS_HOME/modules -type f -name "javax.json-*.jar"); do
> BOOT_CP+=("$f")
> done
> x="-Xbootclasspath/a"
> for p in "${BOOT_CP[@]}"; do
> x+=":$p"
> done
> JAVA_OPTS="-Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dsun.util.logging.disableCallerCheck=true $x $JAVA_OPTS"
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-4036) DMN rule task property enhancements
by Elizabeth Clayton (Jira)
Elizabeth Clayton created DROOLS-4036:
-----------------------------------------
Summary: DMN rule task property enhancements
Key: DROOLS-4036
URL: https://issues.jboss.org/browse/DROOLS-4036
Project: Drools
Issue Type: Story
Components: Stunner
Reporter: Elizabeth Clayton
Assignee: Elizabeth Clayton
Attachments: Screen Shot 2019-05-03 at 1.53.33 PM.png, Screen Shot 2019-05-03 at 7.31.32 AM.png
Currently, the user has to know all properties from the head or find them in DMN Modeler which is too long and error-prone task. Define input fields that allow fields/properties to be pre-populated to streamline experience for the user.
Properties that need be set:
* DMN file selector: The Namespace is provided in the background.
* Decision name (optional field): Decision service, Decision, or _blank_.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (LOGMGR-254) JDK11, Warning when starting WildFly with logmanager in bootclasspath
by James Perkins (Jira)
[ https://issues.jboss.org/browse/LOGMGR-254?page=com.atlassian.jira.plugin... ]
James Perkins updated LOGMGR-254:
---------------------------------
Description:
Using JDK11, add the following property when starting standalone.sh:
{code}
-Djboss.modules.system.pkgs=org.jboss.logmanager
-Xbootclasspath/a:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.10.Final.jar:$JBOSS_HOME/modules/system/layers/base/org/wildfly/common/main/wildfly-common-1.5.1.Final.jar
-Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dsun.util.logging.disableCallerCheck=true
{code}
You will notice the following warning:
{code}
May 15, 2019 4:49:11 PM java.lang.System$LoggerFinder lambda$accessProvider$0
WARNING: Failed to instantiate LoggerFinder provider; Using default.
{code}
To display the root cause add:
{{-Djdk.logger.finder.error=ERROR}}
Changing the {{standalone.conf}} to the following should show the warning:
{code}
if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then
JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman"
fi
JBOSS_MODULES_SYSTEM_PKGS="org.jboss.logmanager,jdk.nashorn.api,com.sun.crypto.provider,$JBOSS_MODULES_SYSTEM_PKGS"
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true"
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
else
echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"
fi
BOOT_CP=()
BOOT_CP=("$(find $JBOSS_HOME/modules -type f -name "jboss-logmanager-*.jar")")
BOOT_CP+=("$(find $JBOSS_HOME/modules -type f -name "wildfly-common*.jar")")
for f in $(find $JBOSS_HOME/modules -type f -name "javax.json-*.jar"); do
BOOT_CP+=("$f")
done
x="-Xbootclasspath/a"
for p in "${BOOT_CP[@]}"; do
x+=":$p"
done
JAVA_OPTS="-Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dsun.util.logging.disableCallerCheck=true $x $JAVA_OPTS"
{code}
was:
Using JDK11, add the following property when starting standalone.sh:
-Djboss.modules.system.pkgs=org.jboss.logmanager
-Xbootclasspath/a:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.10.Final.jar:$JBOSS_HOME/modules/system/layers/base/org/wildfly/common/main/wildfly-common-1.5.1.Final.jar
-Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dsun.util.logging.disableCallerCheck=true
You will notice the following warning:
May 15, 2019 4:49:11 PM java.lang.System$LoggerFinder lambda$accessProvider$0
WARNING: Failed to instantiate LoggerFinder provider; Using default.
To display the root cause add:
-Djdk.logger.finder.error=ERROR
> JDK11, Warning when starting WildFly with logmanager in bootclasspath
> ---------------------------------------------------------------------
>
> Key: LOGMGR-254
> URL: https://issues.jboss.org/browse/LOGMGR-254
> Project: JBoss Log Manager
> Issue Type: Bug
> Reporter: Jean Francois Denise
> Assignee: James Perkins
> Priority: Major
>
> Using JDK11, add the following property when starting standalone.sh:
> {code}
> -Djboss.modules.system.pkgs=org.jboss.logmanager
> -Xbootclasspath/a:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.10.Final.jar:$JBOSS_HOME/modules/system/layers/base/org/wildfly/common/main/wildfly-common-1.5.1.Final.jar
> -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dsun.util.logging.disableCallerCheck=true
> {code}
> You will notice the following warning:
> {code}
> May 15, 2019 4:49:11 PM java.lang.System$LoggerFinder lambda$accessProvider$0
> WARNING: Failed to instantiate LoggerFinder provider; Using default.
> {code}
> To display the root cause add:
> {{-Djdk.logger.finder.error=ERROR}}
> Changing the {{standalone.conf}} to the following should show the warning:
> {code}
> if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then
> JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman"
> fi
> JBOSS_MODULES_SYSTEM_PKGS="org.jboss.logmanager,jdk.nashorn.api,com.sun.crypto.provider,$JBOSS_MODULES_SYSTEM_PKGS"
> if [ "x$JAVA_OPTS" = "x" ]; then
> JAVA_OPTS="-Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true"
> JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
> else
> echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"
> fi
> BOOT_CP=()
> BOOT_CP=("$(find $JBOSS_HOME/modules -type f -name "jboss-logmanager-*.jar")")
> BOOT_CP+=("$(find $JBOSS_HOME/modules -type f -name "wildfly-common*.jar")")
> for f in $(find $JBOSS_HOME/modules -type f -name "javax.json-*.jar"); do
> BOOT_CP+=("$f")
> done
> x="-Xbootclasspath/a"
> for p in "${BOOT_CP[@]}"; do
> x+=":$p"
> done
> JAVA_OPTS="-Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dsun.util.logging.disableCallerCheck=true $x $JAVA_OPTS"
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (LOGMGR-254) JDK11, Warning when starting WildFly with logmanager in bootclasspath
by James Perkins (Jira)
[ https://issues.jboss.org/browse/LOGMGR-254?page=com.atlassian.jira.plugin... ]
James Perkins moved WFLY-12082 to LOGMGR-254:
---------------------------------------------
Project: JBoss Log Manager (was: WildFly)
Key: LOGMGR-254 (was: WFLY-12082)
Component/s: (was: Logging)
> JDK11, Warning when starting WildFly with logmanager in bootclasspath
> ---------------------------------------------------------------------
>
> Key: LOGMGR-254
> URL: https://issues.jboss.org/browse/LOGMGR-254
> Project: JBoss Log Manager
> Issue Type: Bug
> Reporter: Jean Francois Denise
> Assignee: James Perkins
> Priority: Major
>
> Using JDK11, add the following property when starting standalone.sh:
> -Djboss.modules.system.pkgs=org.jboss.logmanager
> -Xbootclasspath/a:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.10.Final.jar:$JBOSS_HOME/modules/system/layers/base/org/wildfly/common/main/wildfly-common-1.5.1.Final.jar
> -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dsun.util.logging.disableCallerCheck=true
> You will notice the following warning:
> May 15, 2019 4:49:11 PM java.lang.System$LoggerFinder lambda$accessProvider$0
> WARNING: Failed to instantiate LoggerFinder provider; Using default.
> To display the root cause add:
> -Djdk.logger.finder.error=ERROR
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months