Bug 1019232 - jboss-cli.sh throws NullPointerException when using tab complete on data-source node
jboss-cli.sh throws NullPointerException when using tab complete on data-sour...
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CLI (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ER5
: EAP 6.3.0
Assigned To: Joe Wertz
Petr Kremensky
Russell Dickenson
Depends On:
  Show dependency treegraph
Reported: 2013-10-15 06:45 EDT by Petr Kremensky
Modified: 2016-01-04 00:08 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In previous versions of JBoss EAP 6, the `jboss-cli` tool would throw an exception and exit when the user attempted to use the tab completion feature in some circumstances. This was due to inadequate exception handling in the command parser for these situations and has been corrected in this release.
Story Points: ---
Clone Of:
Last Closed: 2014-08-06 10:38:26 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Petr Kremensky 2013-10-15 06:45:24 EDT
Description of problem:
 NullPointerException is thrown once using tab complete on "data-source --name=ExampleDS a"

Version-Release number of selected component (if applicable):
 EAP 6.2.0.ER5

How reproducible:

Steps to Reproduce:
 1. Start out-of-box standalone.
 2. Connect to CLI 
 3. Enter (it is important to enter some char after datasource name): 
   - [standalone@localhost:9999 /] data-source --name=ExampleDS a
 4. Press TAB

Actual results:
 [standalone@localhost:9999 /] data-source --name=ExampleDS ajava.lang.NullPointerException
	at org.jboss.as.cli.operation.OperationRequestCompleter.complete(OperationRequestCompleter.java:145)
	at org.jboss.as.cli.CommandCompleter.complete(CommandCompleter.java:95)
	at org.jboss.as.cli.impl.Console$Factory$1$1.complete(Console.java:102)
	at org.jboss.aesh.console.Console.complete(Console.java:1151)
	at org.jboss.aesh.console.Console.parseOperation(Console.java:550)
	at org.jboss.aesh.console.Console.read(Console.java:452)
	at org.jboss.aesh.console.Console.read(Console.java:346)
	at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:178)
	at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1200)
	at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:263)
	at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.modules.Module.run(Module.java:292)
	at org.jboss.modules.Main.main(Main.java:455)

Expected results:
 Nothing is displayed
Comment 1 Alexey Loubyansky 2013-11-08 05:28:51 EST
This is fixed upstream. Probably as https://issues.jboss.org/browse/WFLY-2204 runtime exceptions thrown during parsing crash cli sessions
Comment 2 sgilda 2014-05-14 15:16:54 EDT
I accidentally changed the jboss-eap-6.3.0 flag. 

Do you know who has permission to change it back to '+'?
Comment 3 Joe Wertz 2014-05-15 03:18:47 EDT
Comment 4 Petr Kremensky 2014-07-01 03:28:43 EDT
This one was left over.

Verified on EAP 6.3.0.ER8.

Note You need to log in before you can comment on or make changes to this bug.