[JBoss JIRA] (WFLY-10031) Scripts throws "illegal reflective access" warning on JDK9
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-10031?page=com.atlassian.jira.plugin... ]
Marek Kopecký updated WFLY-10031:
---------------------------------
Description:
*Description of the issue:*
Scripts throws "illegal reflective access" warning on JDK9.
*How reproducible:*
Always with JDK9
*Steps to Reproduce:*
* ./jboss-cli.sh "echo test"
* ./add-user.sh -u test4 -p Test123* -s
* ./appclient.sh -v
*Actual results:*
{noformat}
[hudson@rhel7-large-9887 bin]$ java --version
java 9.0.4
Java(TM) SE Runtime Environment (build 9.0.4+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
[hudson@rhel7-large-9887 bin]$
{noformat}
{noformat}
[hudson@rhel7-large-9887 bin]$ ./jboss-cli.sh "echo test"
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$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
[hudson@rhel7-large-9887 bin]$
{noformat}
{noformat}
[hudson@rhel7-large-9887 bin]$ ./add-user.sh -u test4 -p Test123* -s
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$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
[hudson@rhel7-large-9887 bin]$ cat ../standalone/configuration/mgmt-users.properties | tail -n 1
test4=a95aa9d159b7afe0cc9d3795061551ad
[hudson@rhel7-large-9887 bin]$
{noformat}
{noformat}
[hudson@rhel7-large-9887 bin]$ ./appclient.sh -v
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$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
06:11:52,205 INFO [org.jboss.modules] (main) JBoss Modules version 1.7.0.Final
WildFly Full 13.0.0.Alpha1-SNAPSHOT (WildFly Core 4.0.0.Final)
[hudson@rhel7-large-9887 bin]$
{noformat}
*Expected results:*
No warnings
was:
*Description of the issue:*
AddUser tool throws "illegal reflective access" warning on JDK9.
*How reproducible:*
Always with JDK9
*Steps to Reproduce:*
# ./add-user.sh -u test4 -p Test123* -s
*Actual results:*
{noformat}
[hudson@rhel7-large-9887 bin]$ java --version
java 9.0.4
Java(TM) SE Runtime Environment (build 9.0.4+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
[hudson@rhel7-large-9887 bin]$ ./add-user.sh -u test4 -p Test123* -s
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$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
[hudson@rhel7-large-9887 bin]$ cat ../standalone/configuration/mgmt-users.properties | tail -n 1
test4=a95aa9d159b7afe0cc9d3795061551ad
[hudson@rhel7-large-9887 bin]$
{noformat}
*Expected results:*
No warnings
> Scripts throws "illegal reflective access" warning on JDK9
> ----------------------------------------------------------
>
> Key: WFLY-10031
> URL: https://issues.jboss.org/browse/WFLY-10031
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Security
> Reporter: Marek Kopecký
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> *Description of the issue:*
> Scripts throws "illegal reflective access" warning on JDK9.
> *How reproducible:*
> Always with JDK9
> *Steps to Reproduce:*
> * ./jboss-cli.sh "echo test"
> * ./add-user.sh -u test4 -p Test123* -s
> * ./appclient.sh -v
> *Actual results:*
> {noformat}
> [hudson@rhel7-large-9887 bin]$ java --version
> java 9.0.4
> Java(TM) SE Runtime Environment (build 9.0.4+11)
> Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> {noformat}
> [hudson@rhel7-large-9887 bin]$ ./jboss-cli.sh "echo test"
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$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
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> {noformat}
> [hudson@rhel7-large-9887 bin]$ ./add-user.sh -u test4 -p Test123* -s
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$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
> [hudson@rhel7-large-9887 bin]$ cat ../standalone/configuration/mgmt-users.properties | tail -n 1
> test4=a95aa9d159b7afe0cc9d3795061551ad
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> {noformat}
> [hudson@rhel7-large-9887 bin]$ ./appclient.sh -v
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$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
> 06:11:52,205 INFO [org.jboss.modules] (main) JBoss Modules version 1.7.0.Final
> WildFly Full 13.0.0.Alpha1-SNAPSHOT (WildFly Core 4.0.0.Final)
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> *Expected results:*
> No warnings
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10029) bean-discovery-mode="annotated" is not working like described in the spec
by Ralph Soika (JIRA)
[ https://issues.jboss.org/browse/WFLY-10029?page=com.atlassian.jira.plugin... ]
Ralph Soika commented on WFLY-10029:
------------------------------------
This is an example plugin:
https://github.com/imixs/imixs-jsf-example/blob/master/src/main/java/org/...
But you can turn around the szenario to simplify it. Just try to inject the 'SomeClass' into a EJB.
{code:java}
@Stateless
@LocalBean
public class SomeService {
@inject
SomeClass someClass; // will be null on Glassfish when beans.xml uses bean-discovery-mode=annotated
...
}
{code}
This will work in Wildfly out of the box independent if the beans.xml attribute bean-discovery-mode is set to "_annotated_" or "_all_". So there is no problem for wildfly. It works and this is great on the first look :-).
But if you use "_annotated_", which is the recommended setting, it does not work in Glassfish/Payara. There it will be always null because "SomeClass" is not recognized as a CDI bean.
To be clear: you can not reproduce an error in WIldfly. I only think it should not work in WIldfly too. And maybe a warning in the log during the deployment would be sufficient. Something like:
_.... Bean "SomeClass" has no scope annotation but will be treated as an CDI bean. You should use bean-discovery-mode "all" instead of "annotated"._
> bean-discovery-mode="annotated" is not working like described in the spec
> -------------------------------------------------------------------------
>
> Key: WFLY-10029
> URL: https://issues.jboss.org/browse/WFLY-10029
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 10.1.0.Final
> Reporter: Ralph Soika
> Assignee: Martin Kouba
> Priority: Minor
> Labels: beans.xml
>
> I think we have a problem in Wildfly 10 concerning scanning of CDI Beans. Take a look at the following example:
> {code:java}
> @Stateless
> @LocalBean
> public class SomeService {
> ...
> }
> public class SomeClass {
> @EJB
> SomeService someService;
> ....
> }
> {code}
> We have a stateless session ejb an a bean which is not annotated with a scope but is injecting the service EJB. If you use a beans.xml with the tag:
> {noformat}
> bean-discovery-mode="annotated"
> {noformat}
> this works in wildfly 10 - the _someService_ is injected into the _someClass_ which is treated as a CDI bean. But this is not a correct behavior as stated in the specification. It says, that in this case only beans with a scope annotation should be treated as CDI which is not the case for SomeClass. Normally, as a developer, you would not complain much about this. So this is only a minor issue.
> I recognized this after I tried to run my application on Glassfish/Payara4 which did no longer work until I changed the beans.xml tag to:
> {noformat}
> bean-discovery-mode="all"
> {noformat}
> Now it works in both application servers. I think in wildfly we are misinterpreting the attribute "bean-discovery-mode". I think this should be changed in the next versions for EE8. I don't know if this behavior is a known issue and maybe it is still under development.
> I know also that with such a change some projects (also my own ones) will break. So maybe a new configuration switch like "strict-cdi-scanning" is helpful. What do you think?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10031) Scripts throws "illegal reflective access" warning on JDK9
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-10031?page=com.atlassian.jira.plugin... ]
Marek Kopecký updated WFLY-10031:
---------------------------------
Summary: Scripts throws "illegal reflective access" warning on JDK9 (was: AddUser tool throws "illegal reflective access" warning on JDK9)
> Scripts throws "illegal reflective access" warning on JDK9
> ----------------------------------------------------------
>
> Key: WFLY-10031
> URL: https://issues.jboss.org/browse/WFLY-10031
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Security
> Reporter: Marek Kopecký
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> *Description of the issue:*
> AddUser tool throws "illegal reflective access" warning on JDK9.
> *How reproducible:*
> Always with JDK9
> *Steps to Reproduce:*
> # ./add-user.sh -u test4 -p Test123* -s
> *Actual results:*
> {noformat}
> [hudson@rhel7-large-9887 bin]$ java --version
> java 9.0.4
> Java(TM) SE Runtime Environment (build 9.0.4+11)
> Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
> [hudson@rhel7-large-9887 bin]$ ./add-user.sh -u test4 -p Test123* -s
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$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
> [hudson@rhel7-large-9887 bin]$ cat ../standalone/configuration/mgmt-users.properties | tail -n 1
> test4=a95aa9d159b7afe0cc9d3795061551ad
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> *Expected results:*
> No warnings
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10029) bean-discovery-mode="annotated" is not working like described in the spec
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-10029?page=com.atlassian.jira.plugin... ]
Martin Kouba commented on WFLY-10029:
-------------------------------------
Ok. And how does the questionable plugin implementation look like? Also a simple reproducer/minimal test would be useful.
> bean-discovery-mode="annotated" is not working like described in the spec
> -------------------------------------------------------------------------
>
> Key: WFLY-10029
> URL: https://issues.jboss.org/browse/WFLY-10029
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 10.1.0.Final
> Reporter: Ralph Soika
> Assignee: Martin Kouba
> Priority: Minor
> Labels: beans.xml
>
> I think we have a problem in Wildfly 10 concerning scanning of CDI Beans. Take a look at the following example:
> {code:java}
> @Stateless
> @LocalBean
> public class SomeService {
> ...
> }
> public class SomeClass {
> @EJB
> SomeService someService;
> ....
> }
> {code}
> We have a stateless session ejb an a bean which is not annotated with a scope but is injecting the service EJB. If you use a beans.xml with the tag:
> {noformat}
> bean-discovery-mode="annotated"
> {noformat}
> this works in wildfly 10 - the _someService_ is injected into the _someClass_ which is treated as a CDI bean. But this is not a correct behavior as stated in the specification. It says, that in this case only beans with a scope annotation should be treated as CDI which is not the case for SomeClass. Normally, as a developer, you would not complain much about this. So this is only a minor issue.
> I recognized this after I tried to run my application on Glassfish/Payara4 which did no longer work until I changed the beans.xml tag to:
> {noformat}
> bean-discovery-mode="all"
> {noformat}
> Now it works in both application servers. I think in wildfly we are misinterpreting the attribute "bean-discovery-mode". I think this should be changed in the next versions for EE8. I don't know if this behavior is a known issue and maybe it is still under development.
> I know also that with such a change some projects (also my own ones) will break. So maybe a new configuration switch like "strict-cdi-scanning" is helpful. What do you think?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10031) AddUser tool throws "illegal reflective access" warning on JDK9
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-10031?page=com.atlassian.jira.plugin... ]
Marek Kopecký commented on WFLY-10031:
--------------------------------------
cc: [~ctomc]
> AddUser tool throws "illegal reflective access" warning on JDK9
> ---------------------------------------------------------------
>
> Key: WFLY-10031
> URL: https://issues.jboss.org/browse/WFLY-10031
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Security
> Reporter: Marek Kopecký
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> *Description of the issue:*
> AddUser tool throws "illegal reflective access" warning on JDK9.
> *How reproducible:*
> Always with JDK9
> *Steps to Reproduce:*
> # ./add-user.sh -u test4 -p Test123* -s
> *Actual results:*
> {noformat}
> [hudson@rhel7-large-9887 bin]$ java --version
> java 9.0.4
> Java(TM) SE Runtime Environment (build 9.0.4+11)
> Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
> [hudson@rhel7-large-9887 bin]$ ./add-user.sh -u test4 -p Test123* -s
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$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
> [hudson@rhel7-large-9887 bin]$ cat ../standalone/configuration/mgmt-users.properties | tail -n 1
> test4=a95aa9d159b7afe0cc9d3795061551ad
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> *Expected results:*
> No warnings
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10032) Wildfly 12 Final (RestEASy 3.5 Final) can't discover JsonBindingProvider for Jax-RS
by Alessandro Moscatelli (JIRA)
Alessandro Moscatelli created WFLY-10032:
--------------------------------------------
Summary: Wildfly 12 Final (RestEASy 3.5 Final) can't discover JsonBindingProvider for Jax-RS
Key: WFLY-10032
URL: https://issues.jboss.org/browse/WFLY-10032
Project: WildFly
Issue Type: Bug
Components: REST
Affects Versions: 12.0.0.Final
Reporter: Alessandro Moscatelli
Assignee: Alessio Soldano
Even if started in JavaEE8 Preview Mode :
<property name="ee8.preview.mode" value="true"/>
Wildfly 12 + RestEasy 3.5 Final can't find this MessageBodyWriter (or Reader) :
org.jboss.resteasy.plugins.providers.jsonb.JsonBindingProvider
Such is provided inside this dependecy :
<dependency>
<groupId>org.jboss.resteasy</groupId>
<artifactId>resteasy-json-binding-provider</artifactId>
<version>3.5.0.Final</version>
</dependency>
resteasy-json-binding-provider.jar is already provided inside WIldfly 12.
RestEASY 3.5 Final documentation stats that JsonBindingProvider should be automatically loaded :
RESTEasy JAX-RS
If you forcefully exclude Jackson with NoJackson annotation an error will appear stating no MessageWrite is found for json media type when serializing objects for Jax-RS.
I debugged a little to try and find out what was happening and I can confirm that in
org.jboss.resteasy.spi.ResteasyProviderFactory at row 2592
JsonBindingProvider won't be discovered
Can you reproduce/fix this issue ?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10031) AddUser tool throws "illegal reflective access" warning on JDK9
by Marek Kopecký (JIRA)
Marek Kopecký created WFLY-10031:
------------------------------------
Summary: AddUser tool throws "illegal reflective access" warning on JDK9
Key: WFLY-10031
URL: https://issues.jboss.org/browse/WFLY-10031
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Marek Kopecký
Assignee: Darran Lofthouse
Priority: Blocker
*Description of the issue:*
AddUser tool throws "illegal reflective access" warning on JDK9.
*How reproducible:*
Always with JDK9
*Steps to Reproduce:*
# ./add-user.sh -u test4 -p Test123* -s
*Actual results:*
{noformat}
[hudson@rhel7-large-9887 bin]$ java --version
java 9.0.4
Java(TM) SE Runtime Environment (build 9.0.4+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
[hudson@rhel7-large-9887 bin]$ ./add-user.sh -u test4 -p Test123* -s
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$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
[hudson@rhel7-large-9887 bin]$ cat ../standalone/configuration/mgmt-users.properties | tail -n 1
test4=a95aa9d159b7afe0cc9d3795061551ad
[hudson@rhel7-large-9887 bin]$
{noformat}
*Expected results:*
No warnings
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10030) Add test for selection of ClusterNodeSelector into clustering testsuite
by Michal Jurc (JIRA)
[ https://issues.jboss.org/browse/WFLY-10030?page=com.atlassian.jira.plugin... ]
Michal Jurc updated WFLY-10030:
-------------------------------
Description: A test validating that the provided implementation of {{ClusterNodeSelector}} is being used by the EJB client to select the node of the cluster to route the request to should be added to WildFly testsuite. (was: A test validating that the provided implementation of {{ClusterNodeSelecto}r} is being used by the EJB client to select the node of the cluster to route the request to should be added to WildFly testsuite.)
> Add test for selection of ClusterNodeSelector into clustering testsuite
> -----------------------------------------------------------------------
>
> Key: WFLY-10030
> URL: https://issues.jboss.org/browse/WFLY-10030
> Project: WildFly
> Issue Type: Enhancement
> Components: Test Suite
> Affects Versions: 13.0.0.Beta1
> Reporter: Michal Jurc
> Assignee: tommaso borgato
> Priority: Minor
>
> A test validating that the provided implementation of {{ClusterNodeSelector}} is being used by the EJB client to select the node of the cluster to route the request to should be added to WildFly testsuite.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10031) AddUser tool throws "illegal reflective access" warning on JDK9
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-10031?page=com.atlassian.jira.plugin... ]
Marek Kopecký updated WFLY-10031:
---------------------------------
Component/s: Scripts
> AddUser tool throws "illegal reflective access" warning on JDK9
> ---------------------------------------------------------------
>
> Key: WFLY-10031
> URL: https://issues.jboss.org/browse/WFLY-10031
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Security
> Reporter: Marek Kopecký
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> *Description of the issue:*
> AddUser tool throws "illegal reflective access" warning on JDK9.
> *How reproducible:*
> Always with JDK9
> *Steps to Reproduce:*
> # ./add-user.sh -u test4 -p Test123* -s
> *Actual results:*
> {noformat}
> [hudson@rhel7-large-9887 bin]$ java --version
> java 9.0.4
> Java(TM) SE Runtime Environment (build 9.0.4+11)
> Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
> [hudson@rhel7-large-9887 bin]$ ./add-user.sh -u test4 -p Test123* -s
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$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
> [hudson@rhel7-large-9887 bin]$ cat ../standalone/configuration/mgmt-users.properties | tail -n 1
> test4=a95aa9d159b7afe0cc9d3795061551ad
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> *Expected results:*
> No warnings
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months