[JBoss JIRA] (WFLY-9967) LayeredDistributionTestCase fails without clean install
by Jan Kalina (JIRA)
Jan Kalina created WFLY-9967:
--------------------------------
Summary: LayeredDistributionTestCase fails without clean install
Key: WFLY-9967
URL: https://issues.jboss.org/browse/WFLY-9967
Project: WildFly
Issue Type: Bug
Components: Test Suite
Affects Versions: 12.0.0.Final
Reporter: Jan Kalina
LayeredDistributionTestCase fails when started twice without {{mvn clean}} - removing old working directory is done using operation supporting only blank directories:
{code}
Running org.jboss.as.test.manualmode.layered.LayeredDistributionTestCase
Tests run: 4, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.1 sec <<< FAILURE! - in org.jboss.as.test.manualmode.layered.LayeredDistributionTestCase
before(org.jboss.as.test.manualmode.layered.LayeredDistributionTestCase) Time elapsed: 0.058 sec <<< ERROR!
java.nio.file.DirectoryNotEmptyException: target/jbossas-layered/modules/system/layers/test
at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:242)
at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108)
at java.nio.file.Files.deleteIfExists(Files.java:1165)
at org.jboss.as.test.manualmode.layered.LayeredDistributionTestCase.buildLayer(LayeredDistributionTestCase.java:162)
at org.jboss.as.test.manualmode.layered.LayeredDistributionTestCase.before(LayeredDistributionTestCase.java:99)
{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 Gaétan QUENTIN (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3667?page=com.atlassian.jira.plugi... ]
Gaétan QUENTIN commented on WFCORE-3667:
----------------------------------------
FYI
doing :
script /dev/null
bash
and jboss-cli.sh
it works.
but what have changed between v11/v12?
> 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] (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 updated WFCORE-3667:
-----------------------------------
Attachment: jboss-cli.log
> 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] (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:
----------------------------------------
same results.
attached log file.
[^jboss-cli.log]
> 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, 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-9966) local-cache doesn't allow jndi-name attribute any more in wildfly 12, but it still supports in wildfly 11
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9966?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-9966.
------------------------------
Resolution: Rejected
jndi-name was intentionally removed from the subsystem schema.
By default, Infinispan caches are bound to JNDI using the name:
"java:jboss/infinispan/cache/_container-name_/_cache-name_"
You can use a resource-ref or resource-env-ref to link the global jndi name to an application specific namespace with any name that you like.
> local-cache doesn't allow jndi-name attribute any more in wildfly 12, but it still supports in wildfly 11
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9966
> URL: https://issues.jboss.org/browse/WFLY-9966
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 12.0.0.Final
> Reporter: dungtri pham
> Assignee: Paul Ferraro
>
> I use to have my local cache defined in wildfly 10, 11 like below:
> <cache-container name="mycache" default-cache="my_device_cache">
> <local-cache name="my_device_cache" jndi-name="java:/cache/device/status">
> <file-store passivation="false" preload="true" purge="false" shared="true"/>
> </local-cache>
> </cache-container>
> Now, it blows up in wildfly 12 and complains about jndi-name isnt allowed attribute for the local-cache.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9966) local-cache doesn't allow jndi-name attribute any more in wildfly 12, but it still supports in wildfly 11
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9966?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-9966:
-----------------------------------
Component/s: Clustering
(was: Server)
> local-cache doesn't allow jndi-name attribute any more in wildfly 12, but it still supports in wildfly 11
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9966
> URL: https://issues.jboss.org/browse/WFLY-9966
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 12.0.0.Final
> Reporter: dungtri pham
> Assignee: Jason Greene
>
> I use to have my local cache defined in wildfly 10, 11 like below:
> <cache-container name="mycache" default-cache="my_device_cache">
> <local-cache name="my_device_cache" jndi-name="java:/cache/device/status">
> <file-store passivation="false" preload="true" purge="false" shared="true"/>
> </local-cache>
> </cache-container>
> Now, it blows up in wildfly 12 and complains about jndi-name isnt allowed attribute for the local-cache.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9966) local-cache doesn't allow jndi-name attribute any more in wildfly 12, but it still supports in wildfly 11
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9966?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-9966:
--------------------------------------
Assignee: Paul Ferraro (was: Jason Greene)
> local-cache doesn't allow jndi-name attribute any more in wildfly 12, but it still supports in wildfly 11
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9966
> URL: https://issues.jboss.org/browse/WFLY-9966
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 12.0.0.Final
> Reporter: dungtri pham
> Assignee: Paul Ferraro
>
> I use to have my local cache defined in wildfly 10, 11 like below:
> <cache-container name="mycache" default-cache="my_device_cache">
> <local-cache name="my_device_cache" jndi-name="java:/cache/device/status">
> <file-store passivation="false" preload="true" purge="false" shared="true"/>
> </local-cache>
> </cache-container>
> Now, it blows up in wildfly 12 and complains about jndi-name isnt allowed attribute for the local-cache.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9966) local-cache doesn't allow jndi-name attribute any more in wildfly 12, but it still supports in wildfly 11
by dungtri pham (JIRA)
[ https://issues.jboss.org/browse/WFLY-9966?page=com.atlassian.jira.plugin.... ]
dungtri pham updated WFLY-9966:
-------------------------------
Description:
I use to have my local cache defined in wildfly 10, 11 like below:
<cache-container name="mycache" default-cache="my_device_cache">
<local-cache name="my_device_cache" jndi-name="java:/cache/device/status">
<file-store passivation="false" preload="true" purge="false" shared="true"/>
</local-cache>
</cache-container>
Now, it blows up in wildfly 12 and complains about jndi-name isnt allowed attribute for the local-cache.
was:
I use to have my local cache defined in wildfly 10, 11 like below:
<cache-container name="mycache" default-cache="my_device_cache">
<local-cache name="my_device_cache" jndi-name="java:/cache/device/status">
<file-store passivation="false" preload="true" purge="false" shared="true"/>
</local-cache>
</cache-container>
Now, it blows up in wildfly 12 and complains about jndi-name is invalid attribute.
> local-cache doesn't allow jndi-name attribute any more in wildfly 12, but it still supports in wildfly 11
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9966
> URL: https://issues.jboss.org/browse/WFLY-9966
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 12.0.0.Final
> Reporter: dungtri pham
> Assignee: Jason Greene
>
> I use to have my local cache defined in wildfly 10, 11 like below:
> <cache-container name="mycache" default-cache="my_device_cache">
> <local-cache name="my_device_cache" jndi-name="java:/cache/device/status">
> <file-store passivation="false" preload="true" purge="false" shared="true"/>
> </local-cache>
> </cache-container>
> Now, it blows up in wildfly 12 and complains about jndi-name isnt allowed attribute for the local-cache.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months