[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 Jaikiran Pai (Jira)
[ https://issues.jboss.org/browse/WFLY-12085?page=com.atlassian.jira.plugin... ]
Jaikiran Pai updated WFLY-12085:
--------------------------------
Affects Version/s: 17.0.0.Final
> 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, 17.0.0.Final
> 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, 1 month
[JBoss JIRA] (DROOLS-3755) [DMN Designer] Data Types - Constraints (Range/Enumeration) - Add "Date/Time" component when the type is "Date/Time"
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3755?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3755:
--------------------------------
Description:
When the type of the Data Type is "Date/Time", add the "Date/Time" component to the input, as the following mockup shows:
Enum/Range:
!datetime-enum.png|thumbnail!
!datetime-range.png|thumbnail!
Components:
!datetime-dropdown.png|thumbnail!
!datetime-time.png|thumbnail!
⚠️ Notice:
This component has some elements from the time component (https://issues.jboss.org/browse/DROOLS-3665):
- An input with the timepicker;
- A toggle button (to toggle between offset and timezone)
- An input which is filled accordingly to the toggle button
h2. Acceptance test
Both on Firefox and Chrome
- Enumeration, Save and reopen
- Range, Save and reopen
- Expression, Save and reopen
- Change constraint
- Build and deploy project where date/time constraint in use
was:
When the type of the Data Type is "Date/Time", add the "Date/Time" component to the input, as the following mockup shows:
Enum/Range:
!datetime-enum.png|thumbnail!
!datetime-range.png|thumbnail!
Components:
!datetime-dropdown.png|thumbnail!
!datetime-time.png|thumbnail!
⚠️ Notice:
This component has some elements from the time component (https://issues.jboss.org/browse/DROOLS-3665):
- An input with the timepicker;
- A toggle button (to toggle between offset and timezone)
- An input which is filled accordingly to the toggle button
> [DMN Designer] Data Types - Constraints (Range/Enumeration) - Add "Date/Time" component when the type is "Date/Time"
> --------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3755
> URL: https://issues.jboss.org/browse/DROOLS-3755
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: datetime-dropdown.png, datetime-enum.png, datetime-range.png, datetime-time.png
>
>
> When the type of the Data Type is "Date/Time", add the "Date/Time" component to the input, as the following mockup shows:
> Enum/Range:
> !datetime-enum.png|thumbnail!
> !datetime-range.png|thumbnail!
> Components:
> !datetime-dropdown.png|thumbnail!
> !datetime-time.png|thumbnail!
> ⚠️ Notice:
> This component has some elements from the time component (https://issues.jboss.org/browse/DROOLS-3665):
> - An input with the timepicker;
> - A toggle button (to toggle between offset and timezone)
> - An input which is filled accordingly to the toggle button
> h2. Acceptance test
> Both on Firefox and Chrome
> - Enumeration, Save and reopen
> - Range, Save and reopen
> - Expression, Save and reopen
> - Change constraint
> - Build and deploy project where date/time constraint in use
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4519) Slave Host Controller deployment repository is cleaned after a full deployment replacement
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFCORE-4519?page=com.atlassian.jira.plugi... ]
Yeray Borges updated WFCORE-4519:
---------------------------------
Workaround Description:
As a workaround to avoid the possibility to hit the issue, we can use the server-group:replace-deployment operation instead of deploy --force to update content in the server groups. For example:
{noformat}
[domain@localhost:9990 /] deploy /applications/test-application.war --name=test-application-v2.war --disabled
[domain@localhost:9990 /] /server-group=main-server-group:replace-deployment(name=test-application-v2.war, runtime-name=test-application.war, to-replace=test-application.war)
{noformat}
Workaround: Workaround Exists
> Slave Host Controller deployment repository is cleaned after a full deployment replacement
> ------------------------------------------------------------------------------------------
>
> Key: WFCORE-4519
> URL: https://issues.jboss.org/browse/WFCORE-4519
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 9.0.1.Final
> Environment: Domain mode, slave HC with deployments in its server groups
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Major
>
> In domain mode, there is a cleanup task that removes obsolete content from the deployment repository of each process (DC, slave HC, and servers). By default, this task is executed every five minutes.
> The task checks if there is any content to be marked as obsolete, if there is, it is marked and deleted on the next task execution.
> Deployment content is considerate obsolete in a slave HC if there are no references to it, that means if there is no server group that has this deployment configured.
> The issue here is the deployment handler that replaces the deployment content in a slave is not adding a reference to the new content if there are affected server groups.
> The consequence is the cleanup task could delete the slave HC content. If this occurs when the servers are starting, the servers could fail to start with the following error:
> {noformat}
> 019-06-12 08:51:32,813 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "test-application.war")]) - failure description: "WFLYSRV0137: No deployment content with hash b1fb3b872b3490bbdbd152bd082791b1f170397d is available in the deployment content repository for deployment 'test-application.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart."
> 2019-06-12 08:51:32,817 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 2019-06-12 08:51:32,833 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: WildFly Full 17.0.0.Final-SNAPSHOT (WildFly Core 9.0.1.Final-SNAPSHOT) stopped in 5ms
> {noformat}
> The issue is difficult to hit because it is the server who requests the required files to the slave HC. In order to reproduce it, there must be a coincidence when the server has requested a deployment file to its HC, the HC already has this file in its deployment repository marked as obsolete and, before send it to the server, the cleanup task removes it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (SWSQE-789) UI Automations - Fix random failures in Routing Wizard.
by Hayk Hovsepyan (Jira)
Hayk Hovsepyan created SWSQE-789:
------------------------------------
Summary: UI Automations - Fix random failures in Routing Wizard.
Key: SWSQE-789
URL: https://issues.jboss.org/browse/SWSQE-789
Project: Kiali QE
Issue Type: QE Task
Reporter: Hayk Hovsepyan
Routing CRUD tests fails randomly when checking Actions menu items enable/disable states.
Probably we need to add waits after each action which will cause menu items state change and checking is done very fast.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month