[JBoss JIRA] (WFLY-9969) JDK9 + FIPS BC, unable to configure
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-9969?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-9969:
-----------------------------------
The {{-cp}} option is ignored because we launch WildFly with {{-jar}}.
> JDK9 + FIPS BC, unable to configure
> -----------------------------------
>
> Key: WFLY-9969
> URL: https://issues.jboss.org/browse/WFLY-9969
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 12.0.0.Final
> Reporter: Martin Choma
>
> * Configure BouncyCastleFipsProvider in java
> {code:title=$\{jdk9_home\}/conf/security/java.security}
> security.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
> security.provider.2=SUN
> security.provider.3=SunRsaSign
> security.provider.4=SunEC
> security.provider.5=SunJSSE BCFIPS
> security.provider.6=SunJCE
> security.provider.7=SunJGSS
> security.provider.8=SunSASL
> security.provider.9=XMLDSig
> security.provider.10=SunPCSC
> security.provider.11=JdkLDAP
> security.provider.12=JdkSASL
> security.provider.13=SunPKCS11
> {code}
> * configure -cp of java process based on https://docs.oracle.com/javase/9/security/howtoimplaprovider.htm#JSSEC-GU.... It means in $\{jboss_home\}/bin/standalone.conf put -cp option with bcfips jar
> {{JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -cp /home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.0/bc-fips-1.0.0.jar"}}
> * Configure additional logging
> {code}
> /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level, value=ALL)
> /subsystem=logging/logger=org.wildfly.extension.elytron:add(level=ALL)
> {code}
> * Run CLI command usink BCFKS key store type
> {{/subsystem=elytron/key-store=bcfks_keystore:add(path=keystore.bcfks,relative-to=jboss.server.config.dir, type="BCFKS", credential-reference=\{clear-text=password\})}}
> * For some reason BouncyCastleFipsProvider is not listed among providers returned by Security.getProviders() and therefore BCFKS can't be resolved
> {code}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/mchoma/eap/7.2.0.EL12.CR1/jboss-eap-7.2
> JAVA: /opt/java/jdk-9.0.1_bcfips/bin/java
> JAVA_OPTS: -server -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -cp /home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.0/bc-fips-1.0.0.jar -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n
> =========================================================================
> ...
> 09:20:16,630 TRACE [org.wildfly.extension.elytron] (MSC service thread 1-3) No provider identified for name [null] and algorithm [BCFKS] between [SUN version 9, ApacheXMLDSig version 2.11, SunRsaSign version 9, SunEC version 9, SunJSSE version 9, SunJCE version 9, SunJGSS version 9, SunSASL version 9, XMLDSig version 9, SunPCSC version 9, JdkLDAP version 9, JdkSASL version 9, SunPKCS11 version 9, SunDeploy-MozillaJSS version 1.5, WildFlyElytron version 1.0, TLSP version 1.0, openssl version 1.0]
> 09:20:16,632 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.security.key-store.bcfks_keystore: org.jboss.msc.service.StartException in service org.wildfly.security.key-store.bcfks_keystore: WFLYELY00004: Unable to start the service.
> at org.wildfly.extension.elytron@4.0.0.CR1-redhat-1-20180228//org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:148)
> at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.base/java.lang.Thread.run(Thread.java:844)
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYELY00012: No suitable provider found for type 'BCFKS'
> at org.wildfly.extension.elytron@4.0.0.CR1-redhat-1-20180228//org.wildfly.extension.elytron.KeyStoreService.resolveProvider(KeyStoreService.java:156)
> at org.wildfly.extension.elytron@4.0.0.CR1-redhat-1-20180228//org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:110)
> ... 8 more
> {code}
> * With same java I can run succesfully this java code
> {code:java|title=TestBCLoaded.java}
> import java.security.*;
> public class TestBCLoaded {
> public static void main(String[] args) {
> Provider p = Security.getProvider("org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider");
> if (p==null){
> System.out.println("Not Loaded: org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider");
> }
> p = Security.getProvider("BouncyCastleFipsProvider");
> if (p==null){
> System.out.println("Not Loaded: BouncyCastleFipsProvider");
> }
> p = Security.getProvider("BCFIPS");
> if (p==null){
> System.out.println("Not Loaded: BCFIPS");
> } else {
> System.out.println("Provider name is " + p.getName());
> System.out.println("Provider version # is " + p.getVersion());
> System.out.println("Provider info is " + p.getInfo());
> }
> }
> }
> {code}
> {code}
> [mchoma@localhost jdk9Test]$ java -cp .:/home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.0/bc-fips-1.0.0.jar TestBCLoaded
> Not Loaded: org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
> Not Loaded: BouncyCastleFipsProvider
> Provider name is BCFIPS
> Provider version # is 0.9
> Provider info is BouncyCastle Security Provider (FIPS edition) v0.90
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3667) Wildfly 12 : jboss-cli.sh in infinite loop
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3667?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise updated WFCORE-3667:
-----------------------------------------
Attachment: (was: aesh-readline-1.5.jar)
> Wildfly 12 : jboss-cli.sh in infinite loop
> -------------------------------------------
>
> Key: WFCORE-3667
> URL: https://issues.jboss.org/browse/WFCORE-3667
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Environment: ubuntu 16.06 lxd container
> java version "1.8.0_161" oracle
> v12 migrated from v11
> Reporter: Gaétan QUENTIN
> Assignee: Jean-Francois Denise
> Priority: Critical
> Labels: regression
> Attachments: aesh-readline-1.5.jar, jboss-cli-logging.properties, jboss-cli.25300, jboss-cli.log, term.txt
>
>
> i cannot use anymore the jboss-cli.sh to connect to the contoller since i migrated from v11 to with wildfly 12:
>
> wildfly@java2:/opt/Wildfly$ ls -la
> drwxr-xr-x 1 root root 156 Mar 3 20:36 jboss-server-migration
> drwxr-xr-x 1 root root 454 Mar 4 00:09 overlays
> drwxr-xr-x 1 root root 166 Mar 4 11:43 scripts
> drwxr-xr-x 1 root root 236 Oct 24 05:30 wildfly-11.0.0.Final
> drwxr-xr-x 1 root root 236 Mar 1 07:29 wildfly-12.0.0.Final
> lrwxrwxrwx 1 root root 20 Mar 4 12:49 wildfly-current -> wildfly-12.0.0.Final
>
>
> my wildfly management console is on 172.20.12.192.
> v12 has been migrated from v11 with the jboss-server-migration tool. Applications and app manager works fine and the wildfly instance controller is well binded on the requested ip.
>
>
> with wildfly-current link on -> wildfly-11.0.0.Final:
>
> this works perfectly:
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
>
> with wildfly-current -> wildfly-12.0.0.Final:
> this go in infinite loop until crash :
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
> output:
>
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '[standalone@172.20.12.192:9990' is not a valid operation name.
> ''[standalone@172.20.12.192:9990'' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid operation name.
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '''[standalone@172.20.12.192:9990''' is not a valid operation name.
> ''''[standalone@172.20.12.192:9990'''' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid oper is not a valid operation name.
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '''''[standalone@172.20.12.192:9990''''' is not a valid operation name.
> ''''''[standalone@172.20.12.192:9990'''''' is not a valid operation name.
> attached is a strace capture file (one of thousands) of jboss-cli .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9969) JDK9 + FIPS BC, unable to configure
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-9969?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFLY-9969:
------------------------------------
Found external discussions:
* https://www.bouncycastle.org/devmailarchive/msg15581.html
* http://mail.openjdk.java.net/pipermail/security-dev/2018-March/016858.html
??Note when changing the list of Providers in Java.security file, that this requires the signed Provider JAR to be present on the class- or module path of the JVM. When the Provider class cannot be loaded, it will be skipped.??
>From that it appears there is no recommended way how to register BC on JDK9 globally so far. It should be possible registering dynamically using Security.addProvider() [1]
[1] https://www.bouncycastle.org/devmailarchive/msg15579.html
> JDK9 + FIPS BC, unable to configure
> -----------------------------------
>
> Key: WFLY-9969
> URL: https://issues.jboss.org/browse/WFLY-9969
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 12.0.0.Final
> Reporter: Martin Choma
>
> * Configure BouncyCastleFipsProvider in java
> {code:title=$\{jdk9_home\}/conf/security/java.security}
> security.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
> security.provider.2=SUN
> security.provider.3=SunRsaSign
> security.provider.4=SunEC
> security.provider.5=SunJSSE BCFIPS
> security.provider.6=SunJCE
> security.provider.7=SunJGSS
> security.provider.8=SunSASL
> security.provider.9=XMLDSig
> security.provider.10=SunPCSC
> security.provider.11=JdkLDAP
> security.provider.12=JdkSASL
> security.provider.13=SunPKCS11
> {code}
> * configure -cp of java process based on https://docs.oracle.com/javase/9/security/howtoimplaprovider.htm#JSSEC-GU.... It means in $\{jboss_home\}/bin/standalone.conf put -cp option with bcfips jar
> {{JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -cp /home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.0/bc-fips-1.0.0.jar"}}
> * Configure additional logging
> {code}
> /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level, value=ALL)
> /subsystem=logging/logger=org.wildfly.extension.elytron:add(level=ALL)
> {code}
> * Run CLI command usink BCFKS key store type
> {{/subsystem=elytron/key-store=bcfks_keystore:add(path=keystore.bcfks,relative-to=jboss.server.config.dir, type="BCFKS", credential-reference=\{clear-text=password\})}}
> * For some reason BouncyCastleFipsProvider is not listed among providers returned by Security.getProviders() and therefore BCFKS can't be resolved
> {code}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/mchoma/eap/7.2.0.EL12.CR1/jboss-eap-7.2
> JAVA: /opt/java/jdk-9.0.1_bcfips/bin/java
> JAVA_OPTS: -server -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -cp /home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.0/bc-fips-1.0.0.jar -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n
> =========================================================================
> ...
> 09:20:16,630 TRACE [org.wildfly.extension.elytron] (MSC service thread 1-3) No provider identified for name [null] and algorithm [BCFKS] between [SUN version 9, ApacheXMLDSig version 2.11, SunRsaSign version 9, SunEC version 9, SunJSSE version 9, SunJCE version 9, SunJGSS version 9, SunSASL version 9, XMLDSig version 9, SunPCSC version 9, JdkLDAP version 9, JdkSASL version 9, SunPKCS11 version 9, SunDeploy-MozillaJSS version 1.5, WildFlyElytron version 1.0, TLSP version 1.0, openssl version 1.0]
> 09:20:16,632 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.security.key-store.bcfks_keystore: org.jboss.msc.service.StartException in service org.wildfly.security.key-store.bcfks_keystore: WFLYELY00004: Unable to start the service.
> at org.wildfly.extension.elytron@4.0.0.CR1-redhat-1-20180228//org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:148)
> at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc@1.3.2.Final-redhat-1//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads@2.3.1.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.base/java.lang.Thread.run(Thread.java:844)
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYELY00012: No suitable provider found for type 'BCFKS'
> at org.wildfly.extension.elytron@4.0.0.CR1-redhat-1-20180228//org.wildfly.extension.elytron.KeyStoreService.resolveProvider(KeyStoreService.java:156)
> at org.wildfly.extension.elytron@4.0.0.CR1-redhat-1-20180228//org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:110)
> ... 8 more
> {code}
> * With same java I can run succesfully this java code
> {code:java|title=TestBCLoaded.java}
> import java.security.*;
> public class TestBCLoaded {
> public static void main(String[] args) {
> Provider p = Security.getProvider("org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider");
> if (p==null){
> System.out.println("Not Loaded: org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider");
> }
> p = Security.getProvider("BouncyCastleFipsProvider");
> if (p==null){
> System.out.println("Not Loaded: BouncyCastleFipsProvider");
> }
> p = Security.getProvider("BCFIPS");
> if (p==null){
> System.out.println("Not Loaded: BCFIPS");
> } else {
> System.out.println("Provider name is " + p.getName());
> System.out.println("Provider version # is " + p.getVersion());
> System.out.println("Provider info is " + p.getInfo());
> }
> }
> }
> {code}
> {code}
> [mchoma@localhost jdk9Test]$ java -cp .:/home/mchoma/.m2/repository/org/bouncycastle/fips/bc-fips/1.0.0/bc-fips-1.0.0.jar TestBCLoaded
> Not Loaded: org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
> Not Loaded: BouncyCastleFipsProvider
> Provider name is BCFIPS
> Provider version # is 0.9
> Provider info is BouncyCastle Security Provider (FIPS edition) v0.90
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2369) Refactor use of class ListSelector to use interface ListSelectorView.Presenter
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2369?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2369:
-----------------------------------
Description: I noticed we inject {{ListSelector}} quite a lot rather than the interface {{ListSelectorView.Presenter}}. Also check {{CellEditorControls}} vs {{CellEditorControlsView.Presenter}}. (was: I noticed we inject {{ListSeletor}} quite a lot rather than the interface {{ListSelectorView.Presenter}}. Also check {{CellEditorControls}} vs {{CellEditorControlsView.Presenter}}.)
> Refactor use of class ListSelector to use interface ListSelectorView.Presenter
> ------------------------------------------------------------------------------
>
> Key: DROOLS-2369
> URL: https://issues.jboss.org/browse/DROOLS-2369
> Project: Drools
> Issue Type: Sub-task
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> I noticed we inject {{ListSelector}} quite a lot rather than the interface {{ListSelectorView.Presenter}}. Also check {{CellEditorControls}} vs {{CellEditorControlsView.Presenter}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9970) WildFly 12.0.0.Final + Java 9 ignores @WebServlet
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-9970?page=com.atlassian.jira.plugin.... ]
jaikiran pai resolved WFLY-9970.
--------------------------------
Resolution: Duplicate Issue
This is a genuine issue which got reported a day back and is being addressed. Marking this as duplicate of WFLY-9961
> WildFly 12.0.0.Final + Java 9 ignores @WebServlet
> -------------------------------------------------
>
> Key: WFLY-9970
> URL: https://issues.jboss.org/browse/WFLY-9970
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 12.0.0.Final
> Environment: os: Windows Proffessional 7 64 bit
> jdk: Oracle JDK 9.0.4, Oracle JDK 1.8.0_162
> mvn: Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T10:58:13+03:00)
> Reporter: Анатолий Широков
>
> I have WildFly 12.0.0.Final server running on JDK 9. I have simple maven based annotated servlet project: https://github.com/anatoly-spb/simple-annotated-servlet .
> If I build my project with Java 9, WildFly does not see @WebServlet annotation. If I build my project with Java 1.8, WildFly uses @WebServlet annotation and works as expected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9970) WildFly 12.0.0.Final + Java 9 ignores @WebServlet
by Анатолий Широков (JIRA)
[ https://issues.jboss.org/browse/WFLY-9970?page=com.atlassian.jira.plugin.... ]
Анатолий Широков updated WFLY-9970:
-----------------------------------
Description:
I have WildFly 12.0.0.Final server running on JDK 9. I have simple maven based annotated servlet project: https://github.com/anatoly-spb/simple-annotated-servlet .
If I build my project with Java 9, WildFly does not see @WebServlet annotation. If I build my project with Java 1.8, WildFly uses @WebServlet annotation and works as expected.
was:
I have WildFly 12.0.0.Final server running on JDK 9. I have simple maven based annotated servlet project: https://github.com/anatoly-spb/simple-annotated-servlet .
If I build my project with Java 9, WildFly does see @WebServlet annotation. If I build my project with Java 1.8, WildFly uses @WebServlet annotation and works as expected.
> WildFly 12.0.0.Final + Java 9 ignores @WebServlet
> -------------------------------------------------
>
> Key: WFLY-9970
> URL: https://issues.jboss.org/browse/WFLY-9970
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 12.0.0.Final
> Environment: os: Windows Proffessional 7 64 bit
> jdk: Oracle JDK 9.0.4, Oracle JDK 1.8.0_162
> mvn: Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T10:58:13+03:00)
> Reporter: Анатолий Широков
>
> I have WildFly 12.0.0.Final server running on JDK 9. I have simple maven based annotated servlet project: https://github.com/anatoly-spb/simple-annotated-servlet .
> If I build my project with Java 9, WildFly does not see @WebServlet annotation. If I build my project with Java 1.8, WildFly uses @WebServlet annotation and works as expected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3667) Wildfly 12 : jboss-cli.sh in infinite loop
by Gaétan QUENTIN (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3667?page=com.atlassian.jira.plugi... ]
Gaétan QUENTIN commented on WFCORE-3667:
----------------------------------------
[~jdenise]
root@java2:~# set | grep lxc
container=lxc
root@java2:~#
your last patch works fine!
thanks
> Wildfly 12 : jboss-cli.sh in infinite loop
> -------------------------------------------
>
> Key: WFCORE-3667
> URL: https://issues.jboss.org/browse/WFCORE-3667
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Environment: ubuntu 16.06 lxd container
> java version "1.8.0_161" oracle
> v12 migrated from v11
> Reporter: Gaétan QUENTIN
> Assignee: Jean-Francois Denise
> Priority: Critical
> Labels: regression
> Attachments: aesh-readline-1.5.jar, aesh-readline-1.5.jar, jboss-cli-logging.properties, jboss-cli.25300, jboss-cli.log, term.txt
>
>
> i cannot use anymore the jboss-cli.sh to connect to the contoller since i migrated from v11 to with wildfly 12:
>
> wildfly@java2:/opt/Wildfly$ ls -la
> drwxr-xr-x 1 root root 156 Mar 3 20:36 jboss-server-migration
> drwxr-xr-x 1 root root 454 Mar 4 00:09 overlays
> drwxr-xr-x 1 root root 166 Mar 4 11:43 scripts
> drwxr-xr-x 1 root root 236 Oct 24 05:30 wildfly-11.0.0.Final
> drwxr-xr-x 1 root root 236 Mar 1 07:29 wildfly-12.0.0.Final
> lrwxrwxrwx 1 root root 20 Mar 4 12:49 wildfly-current -> wildfly-12.0.0.Final
>
>
> my wildfly management console is on 172.20.12.192.
> v12 has been migrated from v11 with the jboss-server-migration tool. Applications and app manager works fine and the wildfly instance controller is well binded on the requested ip.
>
>
> with wildfly-current link on -> wildfly-11.0.0.Final:
>
> this works perfectly:
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
>
> with wildfly-current -> wildfly-12.0.0.Final:
> this go in infinite loop until crash :
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
> output:
>
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '[standalone@172.20.12.192:9990' is not a valid operation name.
> ''[standalone@172.20.12.192:9990'' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid operation name.
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '''[standalone@172.20.12.192:9990''' is not a valid operation name.
> ''''[standalone@172.20.12.192:9990'''' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid oper is not a valid operation name.
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '''''[standalone@172.20.12.192:9990''''' is not a valid operation name.
> ''''''[standalone@172.20.12.192:9990'''''' is not a valid operation name.
> attached is a strace capture file (one of thousands) of jboss-cli .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9970) WildFly 12.0.0.Final + Java 9 ignores @WebServlet
by Анатолий Широков (JIRA)
[ https://issues.jboss.org/browse/WFLY-9970?page=com.atlassian.jira.plugin.... ]
Анатолий Широков updated WFLY-9970:
-----------------------------------
Steps to Reproduce:
1. Download simple project from github
```
git clone https://github.com/anatoly-spb/simple-annotated-servlet
```
2. Enter into project directory
```
cd simple-annotated-servlet
```
3. Build project with Java 9:
```
set JAVA_HOME=%JAVA9_HOME%
set PATH=%JAVA_HOME%\bin;%PATH%
mvn clean install
copy /Y target\*.war F:\wildfly-12.0.0.Final\standalone\deployments\
```
4. Check that servlet is not initialized, because there is not `initinig` message from our servlet in the log:
```
13:15:07,995 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: Content added at location F:\tools\wildfly-12.0.0.Final\standalone\data\content\ca\7aa2a316c34941ab2dc1230d64523b4eba4c49\content
13:15:08,004 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 19) WFLYUT0022: Unregistered web context: '/myservlet-1.0-SNAPSHOT' from server 'default-server'
13:15:08,136 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment myservlet-1.0-SNAPSHOT.war (runtime-name: myservlet-1.0-SNAPSHOT.war) in 135ms
13:15:08,138 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "myservlet-1.0-SNAPSHOT.war" (runtime-name: "myservlet-1.0-SNAPSHOT.war")
13:15:08,316 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0021: Registered web context: '/myservlet-1.0-SNAPSHOT' for server 'default-server'
13:15:08,402 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "myservlet-1.0-SNAPSHOT.war" with deployment "myservlet-1.0-SNAPSHOT.war"
13:15:08,405 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0002: Content removed from location F:\tools\wildfly-12.0.0.Final\standalone\data\content\e5\61ef7d0c4b695ba0e71aeb1e5ab2a3e69f58a4\content
```
5. Build project with Java 8:
```
set JAVA_HOME=%JAVA8_HOME%
set PATH=%JAVA_HOME%\bin;%PATH%
mvn clean install
copy /Y target\*.war F:\wildfly-12.0.0.Final\standalone\deployments\
```
6. Check that our servlet is initialized because there is `[my.ScriptServlet] (ServerService Thread Pool -- 74) initinig` in the log:
```
13:17:08,512 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: Content added at location F:\tools\wildfly-12.0.0.Final\standalone\data\content\d9\ba6f286c582b522f90ea51b956b0b27f899623\content
13:17:08,526 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0022: Unregistered web context: '/myservlet-1.0-SNAPSHOT' from server 'default-server'
13:17:08,563 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment myservlet-1.0-SNAPSHOT.war (runtime-name: myservlet-1.0-SNAPSHOT.war) in 48ms
13:17:08,580 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "myservlet-1.0-SNAPSHOT.war" (runtime-name: "myservlet-1.0-SNAPSHOT.war")
13:17:08,779 INFO [my.ScriptServlet] (ServerService Thread Pool -- 74) initinig
13:17:08,780 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0021: Registered web context: '/myservlet-1.0-SNAPSHOT' for server 'default-server'
13:17:08,814 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "myservlet-1.0-SNAPSHOT.war" with deployment "myservlet-1.0-SNAPSHOT.war"
13:17:08,816 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0002: Content removed from location F:\tools\wildfly-12.0.0.Final\standalone\data\content\ca\7aa2a316c34941ab2dc1230d64523b4eba4c49\content
```
was:
1. Download simple project from github
```
git clone https://github.com/anatoly-spb/simple-annotated-servlet
```
2. Enter into project directory
```
cd simple-annotated-servlet
```
3. Build project with Java 9:
```
set JAVA_HOME=%JAVA9_HOME%
set PATH=%JAVA_HOME%\bin;%PATH%
mvn clean install
copy /Y target\*.war F:\wildfly-12.0.0.Final\standalone\deployments\
```
4. Check that servlet is not initialized, because there is not `initinig` message from our servlet in the log:
```
13:15:07,995 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: Content added at location F:\tools\wildfly-12.0.0.Final\standalone\data\content\ca\7aa2a316c34941ab2dc1230d64523b4eba4c49\content
13:15:08,004 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 19) WFLYUT0022: Unregistered web context: '/myservlet-1.0-SNAPSHOT' from server 'default-server'
13:15:08,136 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment myservlet-1.0-SNAPSHOT.war (runtime-name: myservlet-1.0-SNAPSHOT.war) in 135ms
13:15:08,138 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "myservlet-1.0-SNAPSHOT.war" (runtime-name: "myservlet-1.0-SNAPSHOT.war")
13:15:08,316 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0021: Registered web context: '/myservlet-1.0-SNAPSHOT' for server 'default-server'
13:15:08,402 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "myservlet-1.0-SNAPSHOT.war" with deployment "myservlet-1.0-SNAPSHOT.war"
13:15:08,405 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0002: Content removed from location F:\tools\wildfly-12.0.0.Final\standalone\data\content\e5\61ef7d0c4b695ba0e71aeb1e5ab2a3e69f58a4\content
```
4. Build project with Java 8:
```
set JAVA_HOME=%JAVA8_HOME%
set PATH=%JAVA_HOME%\bin;%PATH%
mvn clean install
copy /Y target\*.war F:\wildfly-12.0.0.Final\standalone\deployments\
```
6. Check that our servlet is initialized because there is `[my.ScriptServlet] (ServerService Thread Pool -- 74) initinig` in the log:
```
13:17:08,512 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: Content added at location F:\tools\wildfly-12.0.0.Final\standalone\data\content\d9\ba6f286c582b522f90ea51b956b0b27f899623\content
13:17:08,526 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0022: Unregistered web context: '/myservlet-1.0-SNAPSHOT' from server 'default-server'
13:17:08,563 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment myservlet-1.0-SNAPSHOT.war (runtime-name: myservlet-1.0-SNAPSHOT.war) in 48ms
13:17:08,580 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "myservlet-1.0-SNAPSHOT.war" (runtime-name: "myservlet-1.0-SNAPSHOT.war")
13:17:08,779 INFO [my.ScriptServlet] (ServerService Thread Pool -- 74) initinig
13:17:08,780 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0021: Registered web context: '/myservlet-1.0-SNAPSHOT' for server 'default-server'
13:17:08,814 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "myservlet-1.0-SNAPSHOT.war" with deployment "myservlet-1.0-SNAPSHOT.war"
13:17:08,816 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0002: Content removed from location F:\tools\wildfly-12.0.0.Final\standalone\data\content\ca\7aa2a316c34941ab2dc1230d64523b4eba4c49\content
```
> WildFly 12.0.0.Final + Java 9 ignores @WebServlet
> -------------------------------------------------
>
> Key: WFLY-9970
> URL: https://issues.jboss.org/browse/WFLY-9970
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 12.0.0.Final
> Environment: os: Windows Proffessional 7 64 bit
> jdk: Oracle JDK 9.0.4, Oracle JDK 1.8.0_162
> mvn: Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T10:58:13+03:00)
> Reporter: Анатолий Широков
>
> I have WildFly 12.0.0.Final server running on JDK 9. I have simple maven based annotated servlet project: https://github.com/anatoly-spb/simple-annotated-servlet .
> If I build my project with Java 9, WildFly does see @WebServlet annotation. If I build my project with Java 1.8, WildFly uses @WebServlet annotation and works as expected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months