[JBoss JIRA] (WFCORE-670) Node type is not complete at index 0 after tab completion on an empty resource
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-670?page=com.atlassian.jira.plugin... ]
James Perkins updated WFCORE-670:
---------------------------------
Fix Version/s: 1.0.0.CR1
> Node type is not complete at index 0 after tab completion on an empty resource
> ------------------------------------------------------------------------------
>
> Key: WFCORE-670
> URL: https://issues.jboss.org/browse/WFCORE-670
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: James Perkins
> Assignee: Alexey Loubyansky
> Priority: Blocker
> Fix For: 1.0.0.CR1
>
>
> Using something like {{/system-property=<TAB>}} with no system properties set results in future commands no longer working.
> {code:title=Example Output}
> [standalone@localhost:9990 /] /system-property=
> The operation name is missing or the format of the operation request is wrong.
> [standalone@localhost:9990 /]
> [standalone@localhost:9990 /] exit
> Node type is not complete at index 0
> [standalone@localhost:9990 /]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
- 1
- 0
[JBoss JIRA] (WFCORE-670) Node type is not complete at index 0 after tab completion on an empty resource
by James Perkins (JIRA)
James Perkins created WFCORE-670:
------------------------------------
Summary: Node type is not complete at index 0 after tab completion on an empty resource
Key: WFCORE-670
URL: https://issues.jboss.org/browse/WFCORE-670
Project: WildFly Core
Issue Type: Bug
Components: CLI
Reporter: James Perkins
Assignee: Alexey Loubyansky
Using something like {{/system-property=<TAB>}} with no system properties set results in future commands no longer working.
{code:title=Example Output}
[standalone@localhost:9990 /] /system-property=
The operation name is missing or the format of the operation request is wrong.
[standalone@localhost:9990 /]
[standalone@localhost:9990 /] exit
Node type is not complete at index 0
[standalone@localhost:9990 /]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
- 1
- 0
[JBoss JIRA] (WFLY-156) Unable to start jboss AS on windows if installed on path containig non-ascii characters
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-156?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar closed WFLY-156.
----------------------------
Resolution: Deferred
Once https://bugs.openjdk.java.net/browse/JDK-4488646 is fixed this should work with new powershell scripts that are part of WildFly 9.
> Unable to start jboss AS on windows if installed on path containig non-ascii characters
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-156
> URL: https://issues.jboss.org/browse/WFLY-156
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Environment: windows 2008 x64
> Reporter: Ales Kolenc
> Assignee: Tomaz Cerar
> Priority: Critical
> Fix For: Awaiting Volunteers
>
>
> 1.) Install jboss into a folder containing non-ascii characters. (i.e. "C:\Testチ").
> 2.) run standalone.bat
> C:\Test?\jboss-as-7.1.1.Final\bin>set JAVA_HOME=C:\Program Files\Java\jre7
> C:\Test?\jboss-as-7.1.1.Final\bin>standalone.bat
> Calling "C:\Test?\jboss-as-7.1.1.Final\bin\standalone.conf.bat"
> ===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: C:\Test?\jboss-as-7.1.1.Final
> JAVA: C:\Program Files\Java\jre7\bin\java
> JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djb
> oss.server.default.config=standalone.xml
> ===============================================================================
> Error: Unable to access jarfile C:\Test?\jboss-as-7.1.1.Final\jboss-modules.jar
> Press any key to continue . . .
> C:\Test?\jboss-as-7.1.1.Final\bin>
> 3.) pleas note that: "Testチ" used in path -> 'チ' does not bellong to system locale code page. E.g.: char 'チ' is in CP 932, system locale code page used 437/1252,..
> 4.) i would also like to add that jboss does not start if it installed in "normal" folder, but JBOSS_CONFIG_DIR && JBOSS_LOG_DIR are set to folder with non-ascii characters:
> c:\test\jboss-as-7.1.1.Final\bin>set JBOSS_LOG_DIR=c:\Test?
> c:\test\jboss-as-7.1.1.Final\bin>set JBOSS_CONFIG_DIR=c:\Test?\configuration
> c:\test\jboss-as-7.1.1.Final\bin>dir %JBOSS_CONFIG_DIR%
> Volume in drive C has no label.
> Volume Serial Number is 2C2F-FA6F
> Directory of c:\Test?\configuration
> 01/04/2013 02:34 AM <DIR> .
> 01/04/2013 02:34 AM <DIR> ..
> 01/04/2013 01:42 AM 634 application-roles.properties
> 01/04/2013 01:42 AM 812 application-users.properties
> 01/04/2013 01:42 AM 2,042 logging.properties
> 01/04/2013 01:42 AM 836 mgmt-users.properties
> 01/04/2013 01:42 AM 27,024 standalone-full-ha.xml
> 01/04/2013 01:42 AM 20,794 standalone-full.xml
> 01/04/2013 01:42 AM 20,358 standalone-ha.xml
> 01/04/2013 01:42 AM 15,372 standalone.xml
> 01/04/2013 02:34 AM <DIR> standalone_xml_history
> 8 File(s) 87,872 bytes
> 3 Dir(s) 20,185,866,240 bytes free
> c:\test\jboss-as-7.1.1.Final\bin>standalone.bat -Djboss.server.config.dir=%JBOSS_CONFIG_DIR%
> Calling "c:\test\jboss-as-7.1.1.Final\bin\standalone.conf.bat"
> ===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: c:\test\jboss-as-7.1.1.Final
> JAVA: C:\Program Files\Java\jre7\bin\java
> JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djb
> oss.server.default.config=standalone.xml
> ===============================================================================
> Unable to read the logging configuration from 'file:c:\Test?\configuration/logging.properties' (java.io.FileNotFoundException: c:\Test?\configuration\logging.properties (The filename, directory name, or volume label syntax is incorrect))
> java.lang.IllegalStateException: JBAS018701: Configuration directory does not exist: c:\Test?\configuration
> at org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:371)
> at org.jboss.as.server.Main.determineEnvironment(Main.java:242)
> at org.jboss.as.server.Main.main(Main.java:83)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.modules.Module.run(Module.java:260)
> at org.jboss.modules.Main.main(Main.java:291)
> Press any key to continue . . .
> c:\test\jboss-as-7.1.1.Final\bin>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
- 1
- 0