[JBoss JIRA] (WFCORE-3885) CLI script prints WARNING with JDK10+ if CLI connects to server
by Marek Kopecký (JIRA)
Marek Kopecký created WFCORE-3885:
-------------------------------------
Summary: CLI script prints WARNING with JDK10+ if CLI connects to server
Key: WFCORE-3885
URL: https://issues.jboss.org/browse/WFCORE-3885
Project: WildFly Core
Issue Type: Bug
Components: CLI, Scripts
Reporter: Marek Kopecký
Assignee: Jean-Francois Denise
Priority: Blocker
CLI prints WARNING with JDK10+ if CLI connects to server
{noformat}
[mkopecky@dhcp-10-40-5-52 bin]$ java -version
java version "10" 2018-03-20
Java(TM) SE Runtime Environment 18.3 (build 10+46)
Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10+46, mixed mode)
[mkopecky@dhcp-10-40-5-52 bin]$ ./jboss-cli.sh "echo test"
test
[mkopecky@dhcp-10-40-5-52 bin]$ ./jboss-cli.sh -c "echo test"
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.xnio.nio.NioXnio$2 (jar:file:/home/mkopecky/playground/eap/7.2.0.CD13.1/jboss-eap-7.2/modules/system/layers/base/org/jboss/xnio/nio/main/xnio-nio-3.6.3.Final.jar!/) to constructor sun.nio.ch.EPollSelectorProvider()
WARNING: Please consider reporting this to the maintainers of org.xnio.nio.NioXnio$2
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
test
[mkopecky@dhcp-10-40-5-52 bin]$
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-206) Investegate b21 & b12 Docker Failures
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-206?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-206:
------------------------------------------
Sprint: Kiali QE Sprint 6 (was: Kiali QE Sprint 5)
> Investegate b21 & b12 Docker Failures
> -------------------------------------
>
> Key: SWSQE-206
> URL: https://issues.jboss.org/browse/SWSQE-206
> Project: Kiali QE
> Issue Type: Task
> Reporter: Matt Mahoney
> Assignee: Michael Foley
> Priority: Minor
>
> Docker periodical needs to be restarted, which is causing pod failures. This issue appears to have started when clusters were upgraded to OS3.9.
> Investigate reason for failures. Resolve if at all possible.
> Temp work-around:
> 1) Restart docker service
> 2) Reboot instance if #1 failed
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month