[JBoss JIRA] (AS7-6334) Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/AS7-6334?page=com.atlassian.jira.plugin.s... ]
Kabir Khan updated AS7-6334:
----------------------------
Description:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups [OK]
clustering/infinispan
cmp [OK]
configadmin [OK]
connector/datasource
connector/jca [OK]
connector/resource-adapter
deployment-scanner - https://github.com/jbossas/jboss-as/pull/3970 this cannot be used in domain mode and gives an error when initializing the extension. I created a nicer error message.
ee - PR https://github.com/jbossas/jboss-as/pull/3969
ejb3 [OK]
jacorb - Just a note: the 'security' attribute transformation is not tested
jaxr [OK]
jaxrs [OK] empty subsystem
jdr - [OK] empty subsystem
jmx [OK]
jpa [OK]
jsf [OK]
jsr77 [OK] empty subsystem
logging - PR sent https://github.com/jbossas/jboss-as/pull/3930
mail
messaging [OK]
modcluster [OK]
naming [OK]
osgi [OK]
pojo [OK] empty subsystem
remoting - [OK]
sar [OK] empty subsystem
security [PR sent - https://github.com/jbossas/jboss-as/pull/3941 - needs more work as mentioned in https://issues.jboss.org/browse/AS7-6407]
threads - WIP Brian
transactions [OK]
web [OK]
webservices - WIP Kabir
weld [OK] empty subsystem
xts - [OK] susbystem model has not changed since 7.1.2 & 7.1.3
was:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups [OK]
clustering/infinispan
cmp [OK]
configadmin [OK]
connector/datasource
connector/jca [OK]
connector/resource-adapter
deployment-scanner - WIP Kabir
ee - PR https://github.com/jbossas/jboss-as/pull/3969
ejb3 [OK]
jacorb - Just a note: the 'security' attribute transformation is not tested
jaxr [OK]
jaxrs [OK] empty subsystem
jdr - [OK] empty subsystem
jmx [OK]
jpa [OK]
jsf [OK]
jsr77 [OK] empty subsystem
logging - PR sent https://github.com/jbossas/jboss-as/pull/3930
mail
messaging [OK]
modcluster [OK]
naming [OK]
osgi [OK]
pojo [OK] empty subsystem
remoting - [OK]
sar [OK] empty subsystem
security [PR sent - https://github.com/jbossas/jboss-as/pull/3941 - needs more work as mentioned in https://issues.jboss.org/browse/AS7-6407]
threads - WIP Brian
transactions [OK]
web [OK]
webservices - WIP Kabir
weld [OK] empty subsystem
xts - [OK] susbystem model has not changed since 7.1.2 & 7.1.3
> Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6334
> URL: https://issues.jboss.org/browse/AS7-6334
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> Task to track the work we've all been doing on expressions/transformers.
> See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
> 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
> 2) Basic transformation testing against 7.1.2 and 7.1.3
> 3) Reject-expression testing against 7.1.2 and 7.1.3
> Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
> Please edit this description and put an OK after the subsystem name to indicate it's good to go.
> clustering/jgroups [OK]
> clustering/infinispan
> cmp [OK]
> configadmin [OK]
> connector/datasource
> connector/jca [OK]
> connector/resource-adapter
> deployment-scanner - https://github.com/jbossas/jboss-as/pull/3970 this cannot be used in domain mode and gives an error when initializing the extension. I created a nicer error message.
> ee - PR https://github.com/jbossas/jboss-as/pull/3969
> ejb3 [OK]
> jacorb - Just a note: the 'security' attribute transformation is not tested
> jaxr [OK]
> jaxrs [OK] empty subsystem
> jdr - [OK] empty subsystem
> jmx [OK]
> jpa [OK]
> jsf [OK]
> jsr77 [OK] empty subsystem
> logging - PR sent https://github.com/jbossas/jboss-as/pull/3930
> mail
> messaging [OK]
> modcluster [OK]
> naming [OK]
> osgi [OK]
> pojo [OK] empty subsystem
> remoting - [OK]
> sar [OK] empty subsystem
> security [PR sent - https://github.com/jbossas/jboss-as/pull/3941 - needs more work as mentioned in https://issues.jboss.org/browse/AS7-6407]
> threads - WIP Brian
> transactions [OK]
> web [OK]
> webservices - WIP Kabir
> weld [OK] empty subsystem
> xts - [OK] susbystem model has not changed since 7.1.2 & 7.1.3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (AS7-6426) Jboss-cli crashes on Windows on backslash in history
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6426?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori updated AS7-6426:
-----------------------------------
Steps to Reproduce:
> bin\jboss-cli
[] connect localhost
[] deploy C:\APPS\JBoss\jboss-as-7.x.nightly.30-01-2013.manageclinic\custom_osgi_packages\org.springframework.jdbc-3.1.3.RELEASE.jar [or any other valid path to deployment package]
[] [press up button]
was:
> bin\jboss-cli
> connect localhost
> deploy C:\APPS\JBoss\jboss-as-7.x.nightly.30-01-2013.manageclinic\cust
om_osgi_packages\org.springframework.jdbc-3.1.3.RELEASE.jar [or any other valid path to deployment package]
> [press up button]
> Jboss-cli crashes on Windows on backslash in history
> ----------------------------------------------------
>
> Key: AS7-6426
> URL: https://issues.jboss.org/browse/AS7-6426
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: jarkko rantavuori
> Assignee: Alexey Loubyansky
>
> Note: seems to apply to latest snapshot only, not to 7.1.1.
> If you use a backslash in commands (like you need to use on absolute path deployments on windows) and then press up button to go back to that command, jboss-cli crashes with
> java.lang.NumberFormatException: For input string: "1B"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:492)
> at java.lang.Integer.<init>(Integer.java:677)
> at org.fusesource.jansi.AnsiOutputStream.write(AnsiOutputStream.java:120)
> at java.io.FilterOutputStream.write(FilterOutputStream.java:125)
> at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
> at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.PrintWriter.flush(PrintWriter.java:320)
> at org.jboss.aesh.terminal.WindowsTerminal.writeToStdOut(WindowsTerminal.java:89)
> at org.jboss.aesh.console.Console.drawLine(Console.java:923)
> at org.jboss.aesh.console.Console.redrawLine(Console.java:902)
> at org.jboss.aesh.console.Console.getHistoryElement(Console.java:673)
> at org.jboss.aesh.console.Console.parseOperation(Console.java:476)
> at org.jboss.aesh.console.Console.read(Console.java:377)
> at org.jboss.aesh.console.Console.read(Console.java:331)
> at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:171)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1181)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:259)
> 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:601)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> Press any key to continue . . .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (DROOLS-11) ArrayIndexOutOfBoundsException when calling a method with more than two varargs parameters
by Vikram Duggal (JIRA)
[ https://issues.jboss.org/browse/DROOLS-11?page=com.atlassian.jira.plugin.... ]
Vikram Duggal commented on DROOLS-11:
-------------------------------------
Is there a workaround to this issue for 5.5.0.Final?
> ArrayIndexOutOfBoundsException when calling a method with more than two varargs parameters
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-11
> URL: https://issues.jboss.org/browse/DROOLS-11
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Andreas Bentele
> Assignee: Mario Fusco
> Fix For: 6.0.0.Alpha1
>
>
> I have a rule which uses a Java Interface ILogService with Varargs Parameter. When the rule is evaluated, an ArrayIndexOutOfBoundsException is thrown within MVEL2 code which evaluates the varargs parameters. The MVEL2 code works with two varargs parameters, but not with more than two varargs parameters.
> Drools Version: 5.5.0.Final
> {code}
> // Java Interface ILogService with varargs
> public interface ILogService {
> public void debug(String logMessage, Object... arg);
> ...
> }
> // Global definition ILogService
> global ILogService log;
> rule "..."
> ruleflow-group " ... "
> no-loop true
> salience 2
> when
> ...
> then
> log.debug("{} {} {}", operation.getOrderNumber(), operation.getOperationNumber(), Long.valueOf($operationId));
> end
> {code}
> * Breakpoint in org.mvel2.optimizers.impl.refl.nodes.MethodAccessor.executeAll(Object, VariableResolverFactory, Method), Line 149:
> {code}
> for (int i = 0; i < vararg.length; i++) vararg[i] = parms[parms.length - length + i].getValue(ctx, vars);
> {code}
> * Debugging of this context:
> {code}
> vararg.length = 3
> parms.length = 4
> length = 2
> i = 0 => vararg[0] = parms[4-2+0].getValue(ctx, vars);
> i = 1 => vararg[1] = parms[4-2+1].getValue(ctx, vars);
> i = 2 => vararg[2] = parms[4-2+2].getValue(ctx, vars); => vararg[2] = parms[4].getValue(ctx, vars); => java.lang.ArrayIndexOutOfBoundsException: 4 (because params is an array of length 4 and maximum index 3.
> {code}
> Complete Stacktrace:
> {code}
> MethodAccessor.executeAll(Object, VariableResolverFactory, Method) line: 149
> MethodAccessor.getValue(Object, Object, VariableResolverFactory) line: 48
> VariableAccessor.getValue(Object, Object, VariableResolverFactory) line: 37
> ASTNode.getReducedValueAccelerated(Object, Object, VariableResolverFactory) line: 108
> MVELRuntime.execute(boolean, CompiledExpression, Object, VariableResolverFactory) line: 85
> CompiledExpression.getDirectValue(Object, VariableResolverFactory) line: 123
> CompiledExpression.getValue(Object, VariableResolverFactory) line: 119
> MVEL.executeExpression(Object, Object, VariableResolverFactory) line: 930
> MVELConsequence.evaluate(KnowledgeHelper, WorkingMemory) line: 104
> DefaultAgenda.fireActivation(Activation) line: 1287
> DefaultAgenda.fireNextItem(AgendaFilter) line: 1221
> DefaultAgenda.fireAllRules(AgendaFilter, int) line: 1456
> ReteooStatefulSession(AbstractWorkingMemory).fireAllRules(AgendaFilter, int) line: 710
> ReteooStatefulSession(AbstractWorkingMemory).fireAllRules() line: 674
> StatefulKnowledgeSessionImpl.fireAllRules() line: 230
> ...
> {code}
> I tried to create a simple test case to reproduce it, but the test case always worked - no Exception. but there was also another Stacktrace when stopping at a breakpoint in the LogService:
> {code}
> LogService.info(String, Object...) line: 60
> Rule_Hello_World_4df945f15bc043ef85d8e1317cd461f1.defaultConsequence(KnowledgeHelper, ILogService) line: 7
> Rule_Hello_World_4df945f15bc043ef85d8e1317cd461f1DefaultConsequenceInvokerGenerated.evaluate(KnowledgeHelper, WorkingMemory) line: not available
> Rule_Hello_World_4df945f15bc043ef85d8e1317cd461f1DefaultConsequenceInvoker.evaluate(KnowledgeHelper, WorkingMemory) line: not available
> DefaultAgenda.fireActivation(Activation) line: 1287
> DefaultAgenda.fireNextItem(AgendaFilter) line: 1221
> DefaultAgenda.fireAllRules(AgendaFilter, int) line: 1456
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (AS7-6424) Web administration console does not handle values set with expressions
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-6424?page=com.atlassian.jira.plugin.s... ]
Heiko Braun commented on AS7-6424:
----------------------------------
https://github.com/jbossas/console/tree/1.5.x
> Web administration console does not handle values set with expressions
> ----------------------------------------------------------------------
>
> Key: AS7-6424
> URL: https://issues.jboss.org/browse/AS7-6424
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Heiko Braun
> Labels: console_1.5.1
> Fix For: 7.2.0.Alpha1
>
>
> In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
> As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
> This was hit on ejb subsystem.
> You can try to set following tag like this
> {code}
> <strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
> {code}
> In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (AS7-6424) Web administration console does not handle values set with expressions
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-6424?page=com.atlassian.jira.plugin.s... ]
Heiko Braun resolved AS7-6424.
------------------------------
Resolution: Done
Fixed in 1.5.1
> Web administration console does not handle values set with expressions
> ----------------------------------------------------------------------
>
> Key: AS7-6424
> URL: https://issues.jboss.org/browse/AS7-6424
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Heiko Braun
> Labels: console_1.5.1
> Fix For: 7.2.0.Alpha1
>
>
> In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
> As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
> This was hit on ejb subsystem.
> You can try to set following tag like this
> {code}
> <strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
> {code}
> In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (AS7-6425) Imposible to define attribute via web administration console as system property expression
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-6425?page=com.atlassian.jira.plugin.s... ]
Heiko Braun updated AS7-6425:
-----------------------------
Labels: console_1.5.1 (was: )
> Imposible to define attribute via web administration console as system property expression
> ------------------------------------------------------------------------------------------
>
> Key: AS7-6425
> URL: https://issues.jboss.org/browse/AS7-6425
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Heiko Braun
> Labels: console_1.5.1
> Fix For: 7.2.0.Alpha1
>
>
> What my tests show is that it's not possible to use system property expressions for defining attributes in web administration console.
> When I tried to set attribute (e.g. "Stateful Access Timeout" - Profile/Containter/EJB3) like
> {code}
> ${some.variable:5000}
> {code}
> the console does not show any error message but it does not show the information about successful update. After "Save" it just takes the expression value and says nothing.
> The change is not propagated (not saved) to xml config file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (AS7-6424) Web administration console does not handle values set with expressions
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-6424?page=com.atlassian.jira.plugin.s... ]
Heiko Braun updated AS7-6424:
-----------------------------
Labels: console_1.5.1 (was: )
> Web administration console does not handle values set with expressions
> ----------------------------------------------------------------------
>
> Key: AS7-6424
> URL: https://issues.jboss.org/browse/AS7-6424
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Heiko Braun
> Labels: console_1.5.1
> Fix For: 7.2.0.Alpha1
>
>
> In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
> As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
> This was hit on ejb subsystem.
> You can try to set following tag like this
> {code}
> <strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
> {code}
> In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (AS7-6425) Imposible to define attribute via web administration console as system property expression
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-6425?page=com.atlassian.jira.plugin.s... ]
Heiko Braun edited comment on AS7-6425 at 1/31/13 3:45 AM:
-----------------------------------------------------------
AS7-6424 is the same root cause
was (Author: heiko.braun):
AS7-6424 i0s the same root problem
> Imposible to define attribute via web administration console as system property expression
> ------------------------------------------------------------------------------------------
>
> Key: AS7-6425
> URL: https://issues.jboss.org/browse/AS7-6425
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Heiko Braun
> Fix For: 7.2.0.Alpha1
>
>
> What my tests show is that it's not possible to use system property expressions for defining attributes in web administration console.
> When I tried to set attribute (e.g. "Stateful Access Timeout" - Profile/Containter/EJB3) like
> {code}
> ${some.variable:5000}
> {code}
> the console does not show any error message but it does not show the information about successful update. After "Save" it just takes the expression value and says nothing.
> The change is not propagated (not saved) to xml config file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (AS7-6425) Imposible to define attribute via web administration console as system property expression
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-6425?page=com.atlassian.jira.plugin.s... ]
Heiko Braun resolved AS7-6425.
------------------------------
Resolution: Done
> Imposible to define attribute via web administration console as system property expression
> ------------------------------------------------------------------------------------------
>
> Key: AS7-6425
> URL: https://issues.jboss.org/browse/AS7-6425
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Heiko Braun
> Fix For: 7.2.0.Alpha1
>
>
> What my tests show is that it's not possible to use system property expressions for defining attributes in web administration console.
> When I tried to set attribute (e.g. "Stateful Access Timeout" - Profile/Containter/EJB3) like
> {code}
> ${some.variable:5000}
> {code}
> the console does not show any error message but it does not show the information about successful update. After "Save" it just takes the expression value and says nothing.
> The change is not propagated (not saved) to xml config file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (AS7-6426) Jboss-cli crashes on Windows on backslash in history
by jarkko rantavuori (JIRA)
jarkko rantavuori created AS7-6426:
--------------------------------------
Summary: Jboss-cli crashes on Windows on backslash in history
Key: AS7-6426
URL: https://issues.jboss.org/browse/AS7-6426
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.2.0.Alpha1
Environment: Windows 7, 64-bit
Reporter: jarkko rantavuori
Assignee: Alexey Loubyansky
Note: seems to apply to latest snapshot only, not to 7.1.1.
If you use a backslash in commands (like you need to use on absolute path deployments on windows) and then press up button to go back to that command, jboss-cli crashes with
java.lang.NumberFormatException: For input string: "1B"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:492)
at java.lang.Integer.<init>(Integer.java:677)
at org.fusesource.jansi.AnsiOutputStream.write(AnsiOutputStream.java:120)
at java.io.FilterOutputStream.write(FilterOutputStream.java:125)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
at java.io.PrintWriter.flush(PrintWriter.java:320)
at org.jboss.aesh.terminal.WindowsTerminal.writeToStdOut(WindowsTerminal.java:89)
at org.jboss.aesh.console.Console.drawLine(Console.java:923)
at org.jboss.aesh.console.Console.redrawLine(Console.java:902)
at org.jboss.aesh.console.Console.getHistoryElement(Console.java:673)
at org.jboss.aesh.console.Console.parseOperation(Console.java:476)
at org.jboss.aesh.console.Console.read(Console.java:377)
at org.jboss.aesh.console.Console.read(Console.java:331)
at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:171)
at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1181)
at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:259)
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:601)
at org.jboss.modules.Module.run(Module.java:270)
at org.jboss.modules.Main.main(Main.java:294)
Press any key to continue . . .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months