[JBoss JIRA] (WFLY-12085) [GSS](7.2.z) java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
by Emmanuel Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-12085?page=com.atlassian.jira.plugin... ]
Emmanuel Hugonnet updated WFLY-12085:
-------------------------------------
Labels: (was: regression)
> [GSS](7.2.z) java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12085
> URL: https://issues.jboss.org/browse/WFLY-12085
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 17.0.0.Alpha1
> Environment: Red Hat JBoss Enterprise Application Platform
> 7.2.1
> Microsoft Windows 10
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> There seems to be a regression in JBoss EAP 7.2.1 patch. After applying it the following exception can be seen in the server log file during the startup:
> {noformat}
> 2019-05-13 11:45:11,419 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ222277: Problem initializing automatic logging configuration reload for file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties: java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parse(URI.java:3058)
> at java.net.URI.<init>(URI.java:588)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:2369)
> at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:64)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:544)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:481)
> at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:376)
> at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:206)
> at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:65)
> at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:100)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {noformat}
> This issue only affects Microsoft Windows platform.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12085) java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
by Emmanuel Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-12085?page=com.atlassian.jira.plugin... ]
Emmanuel Hugonnet updated WFLY-12085:
-------------------------------------
Summary: java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties (was: [GSS](7.2.z) java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties)
> java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12085
> URL: https://issues.jboss.org/browse/WFLY-12085
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 17.0.0.Alpha1
> Environment: Red Hat JBoss Enterprise Application Platform
> 7.2.1
> Microsoft Windows 10
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> There seems to be a regression in JBoss EAP 7.2.1 patch. After applying it the following exception can be seen in the server log file during the startup:
> {noformat}
> 2019-05-13 11:45:11,419 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ222277: Problem initializing automatic logging configuration reload for file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties: java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parse(URI.java:3058)
> at java.net.URI.<init>(URI.java:588)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:2369)
> at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:64)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:544)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:481)
> at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:376)
> at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:206)
> at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:65)
> at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:100)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {noformat}
> This issue only affects Microsoft Windows platform.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12084) Allow core-size=0
by Teresa Miyar Gil (Jira)
[ https://issues.jboss.org/browse/WFLY-12084?page=com.atlassian.jira.plugin... ]
Teresa Miyar Gil moved JBEAP-16916 to WFLY-12084:
-------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-12084 (was: JBEAP-16916)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: EE
(was: EE)
Affects Version/s: 17.0.0.Alpha1
(was: 7.0.0.GA)
(was: 7.2.0.GA.CR1)
> Allow core-size=0
> -----------------
>
> Key: WFLY-12084
> URL: https://issues.jboss.org/browse/WFLY-12084
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 17.0.0.Alpha1
> Reporter: Teresa Miyar Gil
> Assignee: Teresa Miyar Gil
> Priority: Major
>
> Getting WFLYEE0112: The core-threads value must be greater than 0 when the queue-length is 0.
> queue-length="0" core-threads="0" should be allowed to enable direct hand off
> and get REJECT exceptions.
> Right now direct hand off is possible setting core-threads=1 but then no REJECT exceptions are thrown.
> Use case:queueSize=0, coreSize=0, maxSize=16 and have direct handoff. there will be no REJECT unless we try to submit more than maxSize tasks concurrently. if we submit more than maxSize concurrently, we expect to see REJECT.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3972) Evaluation of facts hasn't been affected by 'modify()' when parsing String to Double
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3972?page=com.atlassian.jira.plugi... ]
Mario Fusco edited comment on DROOLS-3972 at 5/16/19 10:14 AM:
---------------------------------------------------------------
Can you please clarify why do you have a constraints like
{{
Double.parseDouble(amount) == "20"}}
The method parseDouble returns a primitive double, so why are comparing it with a String?
was (Author: mfusco):
Can you please clarify why do you have a constraints like
{source}
Double.parseDouble(amount) == "20"
{source}
The method parseDouble returns a primitive double, so why are comparing it with a String?
> Evaluation of facts hasn't been affected by 'modify()' when parsing String to Double
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-3972
> URL: https://issues.jboss.org/browse/DROOLS-3972
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.20.0.Final
> Environment: Ubuntu
> Reporter: Almas Toimbekov
> Assignee: Mario Fusco
> Priority: Major
> Labels: double, evaluation, execution, parse
>
> When I modify amount in an example below from 5 to 20 (both are Strings) and then try to evaluate this fact parsing it to Double - the third rule doesn't fire. But it fires when use 'update()' instead of 'modify() {}'
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3972) Evaluation of facts hasn't been affected by 'modify()' when parsing String to Double
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3972?page=com.atlassian.jira.plugi... ]
Mario Fusco edited comment on DROOLS-3972 at 5/16/19 10:14 AM:
---------------------------------------------------------------
Can you please clarify why do you have a constraints like
Double.parseDouble(amount) == "20"
The method parseDouble returns a primitive double, so why are comparing it with a String?
was (Author: mfusco):
Can you please clarify why do you have a constraints like
{{
Double.parseDouble(amount) == "20"}}
The method parseDouble returns a primitive double, so why are comparing it with a String?
> Evaluation of facts hasn't been affected by 'modify()' when parsing String to Double
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-3972
> URL: https://issues.jboss.org/browse/DROOLS-3972
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.20.0.Final
> Environment: Ubuntu
> Reporter: Almas Toimbekov
> Assignee: Mario Fusco
> Priority: Major
> Labels: double, evaluation, execution, parse
>
> When I modify amount in an example below from 5 to 20 (both are Strings) and then try to evaluate this fact parsing it to Double - the third rule doesn't fire. But it fires when use 'update()' instead of 'modify() {}'
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3972) Evaluation of facts hasn't been affected by 'modify()' when parsing String to Double
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3972?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-3972:
-------------------------------------
Can you please clarify why do you have a constraints like
{source}
Double.parseDouble(amount) == "20"
{source}
The method parseDouble returns a primitive double, so why are comparing it with a String?
> Evaluation of facts hasn't been affected by 'modify()' when parsing String to Double
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-3972
> URL: https://issues.jboss.org/browse/DROOLS-3972
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.20.0.Final
> Environment: Ubuntu
> Reporter: Almas Toimbekov
> Assignee: Mario Fusco
> Priority: Major
> Labels: double, evaluation, execution, parse
>
> When I modify amount in an example below from 5 to 20 (both are Strings) and then try to evaluate this fact parsing it to Double - the third rule doesn't fire. But it fires when use 'update()' instead of 'modify() {}'
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3972) Evaluation of facts hasn't been affected by 'modify()' when parsing String to Double
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3972?page=com.atlassian.jira.plugi... ]
Mario Fusco edited comment on DROOLS-3972 at 5/16/19 10:13 AM:
---------------------------------------------------------------
Can you please clarify why do you have a constraints like
{source}
Double.parseDouble(amount) == "20"
{source}
The method parseDouble returns a primitive double, so why are comparing it with a String?
was (Author: mfusco):
Can you please clarify why do you have a constraints like
{source}
Double.parseDouble(amount) == "20"
{source}
The method parseDouble returns a primitive double, so why are comparing it with a String?
> Evaluation of facts hasn't been affected by 'modify()' when parsing String to Double
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-3972
> URL: https://issues.jboss.org/browse/DROOLS-3972
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.20.0.Final
> Environment: Ubuntu
> Reporter: Almas Toimbekov
> Assignee: Mario Fusco
> Priority: Major
> Labels: double, evaluation, execution, parse
>
> When I modify amount in an example below from 5 to 20 (both are Strings) and then try to evaluate this fact parsing it to Double - the third rule doesn't fire. But it fires when use 'update()' instead of 'modify() {}'
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months