[JBoss JIRA] (WFLY-11549) Wildfly-14 : ClassCastException while marshalling/unmarshalling
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11549?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11549:
---------------------------------
Component/s: EE
> Wildfly-14 : ClassCastException while marshalling/unmarshalling
> ---------------------------------------------------------------
>
> Key: WFLY-11549
> URL: https://issues.jboss.org/browse/WFLY-11549
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 14.0.0.Final
> Reporter: Bhavesh Kharwa
> Assignee: Jason Greene
> Priority: Critical
> Attachments: hprofsnapshot.jpg
>
>
> I have configured wildfly-14 in domain mode and configured one profile "*full-ha-socket*" in domain.xml. Now I have deployed ear in wildfly.The application having functionality of marshalling/unmarshalling of content. Also I have provided jaxb dependency in maven as scope provided.
> So the issue is when I process the file the it throws classcastexception. Please refer below stackstrace.
> *Note: Sometimes it is working but sometimes giving exception*
> {code}
> Unhandled exception while procesing file 'testing.xml': java.lang.ClassCastException: com.commons.impl.NewsMessageImpl cannot be cast to com.commons.NewsMessage
> at com.common.transform.MessageTransformationService.transform(MessageTransformationService.java:521)
> at org.springframework.transaction.aspectj.AbstractTransactionAspect.ajc$around$org_springframework_transaction_aspectj_AbstractTransactionAspect$1$2a73e96cproceed(AbstractTransactionAspect.aj:59)
> at org.springframework.transaction.aspectj.AbstractTransactionAspect$AbstractTransactionAspect$1.proceedWithInvocation(AbstractTransactionAspect.aj:65)
> at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:260)
> at org.springframework.transaction.aspectj.AbstractTransactionAspect.ajc$around$org_springframework_transaction_aspectj_AbstractTransactionAspect$1$2a73e96c(AbstractTransactionAspect.aj:63)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.springframework.expression.spel.support.ReflectiveMethodExecutor.execute(ReflectiveMethodExecutor.java:69)
> at org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:122)
> at org.springframework.expression.spel.ast.MethodReference.access$000(MethodReference.java:44)
> at org.springframework.expression.spel.ast.MethodReference$MethodValueRef.getValue(MethodReference.java:258)
> at org.springframework.expression.spel.ast.CompoundExpression.getValueInternal(CompoundExpression.java:82)
> at org.springframework.expression.spel.ast.SpelNodeImpl.getTypedValue(SpelNodeImpl.java:102)
> at org.springframework.expression.spel.standard.SpelExpression.getValue(SpelExpression.java:103)
> at org.springframework.integration.util.AbstractExpressionEvaluator.evaluateExpression(AbstractExpressionEvaluator.java:126)
> at org.springframework.integration.util.MessagingMethodInvokerHelper.processInternal(MessagingMethodInvokerHelper.java:227)
> at org.springframework.integration.util.MessagingMethodInvokerHelper.process(MessagingMethodInvokerHelper.java:127)
> at org.springframework.integration.handler.MethodInvokingMessageProcessor.processMessage(MethodInvokingMessageProcessor.java:73)
> at org.springframework.integration.handler.ServiceActivatingHandler.handleRequestMessage(ServiceActivatingHandler.java:67)
> at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:134)
> at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:73)
> at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:115)
> at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:102)
> at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:77)
> at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:157)
> at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:128)
> at org.springframework.integration.core.MessagingTemplate.doSend(MessagingTemplate.java:288)
> at org.springframework.integration.core.MessagingTemplate.send(MessagingTemplate.java:149)
> at org.springframework.integration.router.AbstractMessageRouter.handleMessageInternal(AbstractMessageRouter.java:134)
> at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:73)
> at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:115)
> at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:102)
> at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:77)
> at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:157)
> at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:128)
> at org.springframework.integration.core.MessagingTemplate.doSend(MessagingTemplate.java:288)
> at org.springframework.integration.core.MessagingTemplate.send(MessagingTemplate.java:149)
> at org.springframework.integration.router.AbstractMessageRouter.handleMessageInternal(AbstractMessageRouter.java:134)
> at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:73)
> at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:115)
> at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:102)
> at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:77)
> at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:157)
> at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:128)
> at org.springframework.integration.core.MessagingTemplate.doSend(MessagingTemplate.java:288)
> at org.springframework.integration.core.MessagingTemplate.send(MessagingTemplate.java:149)
> at org.springframework.integration.router.AbstractMessageRouter.handleMessageInternal(AbstractMessageRouter.java:134)
> at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:73)
> at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:115)
> at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:102)
> at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:77)
> at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:157)
> at org.springframework.integration.channel.AbstractMessageChannel.send(AbstractMessageChannel.java:128)
> at org.springframework.integration.core.MessagingTemplate.doSend(MessagingTemplate.java:288)
> at org.springframework.integration.core.MessagingTemplate.send(MessagingTemplate.java:149)
> at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.sendMessage(AbstractReplyProducingMessageHandler.java:216)
> at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.sendReplyMessage(AbstractReplyProducingMessageHandler.java:200)
> at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.produceReply(AbstractReplyProducingMessageHandler.java:165)
> at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleResult(AbstractReplyProducingMessageHandler.java:159)
> at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:141)
> at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:73)
> at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:115)
> at org.springframework.integration.dispatcher.UnicastingDispatcher.access$000(UnicastingDispatcher.java:52)
> at org.springframework.integration.dispatcher.UnicastingDispatcher$1.run(UnicastingDispatcher.java:97)
> at org.springframework.integration.util.ErrorHandlingTaskExecutor$1.run(ErrorHandlingTaskExecutor.java:52)
> at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledRunnable.run(ControlPointUtils.java:105)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
> at org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$ElytronManagedThread.run(ElytronManagedThreadFactory.java:78)
> {code}
> Also i have added following dependencies in jboss-deployment-structure.xml
> - javax.mail.api
> - org.hibernate (slot=main)
> - javax.validation.api
> - com.sun.xml.bind (slot=main)
> - org.wildfly.clustering.singleton(slot=main)
> No duplicate classes/jars in application ear/lib...
> One thing I have noticed that if I undeploy & deploy the application then this issue start reproducing.
> One question: When I undeploy application, How can i verify application undeployed successfully (Removed all the application classes/lib from class loader while undeploy application)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2008) Test Scenarios: Ability to fail a Guvnor Test Scenario if any unexpected rules are fired when the test scenario is executed
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-2008?page=com.atlassian.jira.plugi... ]
Daniele Zonca commented on DROOLS-2008:
---------------------------------------
[~kkufova]
We cannot add assertion on rule fired or not. You can check the consequences of a rule but not just the fact that has been executed.
So yes it is still valid in new Test Scenario too.
[~ibek] [~tirelli] What do you think about that? Is it something to be planned? If yes, I think we should do it after the "coverage" page ( https://issues.jboss.org/browse/DROOLS-3516 ) as evolution of it. We can think about add there conditions/assertions on rule execution like "I expect the rule XYZ will be fired", "I expect the rule XYZ will be fired once", "Rule XYZ once and ABC never" etc.
> Test Scenarios: Ability to fail a Guvnor Test Scenario if any unexpected rules are fired when the test scenario is executed
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2008
> URL: https://issues.jboss.org/browse/DROOLS-2008
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing, Test Scenarios Editor
> Reporter: Andrea Lee
> Assignee: Toni Rikkola
> Priority: Minor
>
> Example scenario:
> Existing Rules: Rule A, Rule B, Rule C.
> Test Scenario expectation: Expect Rule A to fire once.
> I would like to have the ability to specify that this Test Scenario should fail if any other rule in addition to Rule A is fired WITHOUT having to specify the following additional expectations: Expect Rule B to not fire, Expect Rule C to not fire.
> I have posted this in the user mailing list as well: http://n3.nabble.com/Guvnor-Test-Scenario-Expectations-td722429.html#a722429
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFCORE-323) Validate composite operation steps just before executing them
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFCORE-323?page=com.atlassian.jira.plugin... ]
Yeray Borges reassigned WFCORE-323:
-----------------------------------
Assignee: Yeray Borges (was: Brian Stansberry)
> Validate composite operation steps just before executing them
> -------------------------------------------------------------
>
> Key: WFCORE-323
> URL: https://issues.jboss.org/browse/WFCORE-323
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Management
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Priority: Major
> Labels: EAP
>
> Say we have a composite operation with 2 steps:
> 1) /extension=org.jboss.as.messaging:add
> 2) /subsystem=messaging:add
> This will fail:
> Failed to execute batch: JBAS014739: No handler for add at address
> [("subsystem" => "messaging")]
> This fails because at the time of validation the /subsystem=messaging:add is not valid.
> To illustrate, the execution order is
> Validate 1-2
> 1
> 2
> A possible solution is to convert this to the following:
> V1
> 1
> V2 (works now because 1 has registered the subsystem API)
> 2
> I think that should work but it's a very complex area, particularly in a managed domain, so it's not at all certain this would prove feasible.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2010) Add queries w/assign variables in "Expect" section of Test Scenario editor
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-2010?page=com.atlassian.jira.plugi... ]
Daniele Zonca commented on DROOLS-2010:
---------------------------------------
[~kkufova]
I think that we already supporting it using nested fields: the same condition can be specified with `FactAttributeValue.fieldValidation.fieldCode = "countryCode"`
You cannot really match an object and then refer to it in another column but I'm not sure it is needed if you can just navigate through the object.
[~Rikkola] Am I missing anything? Is the use case different?
> Add queries w/assign variables in "Expect" section of Test Scenario editor
> --------------------------------------------------------------------------
>
> Key: DROOLS-2010
> URL: https://issues.jboss.org/browse/DROOLS-2010
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing, Test Scenarios Editor
> Affects Versions: 6.5.0.Final
> Environment: Tomcat 9 (CLI), Win7 x64, Google Chrome
> Reporter: Russell Morrisey
> Assignee: Toni Rikkola
> Priority: Major
>
> In the Test Scenario editor, I want to be able to set up "Expect" clauses that chain together, like this:
> {code:java}
> $r1: A fact of type FieldValidation has values:
> - fieldCode = "countryCode"
> A fact of type FactAttributeValue has values:
> - fieldValidation = $r1
> - type = "allowedValue"
> - value = "US"
> {code}
> In this case, I want to query for the 1st object, store it in a variable, and use the variable value to verify the 2nd clause of the test. This is necessary to verify relationships between objects, such as master-detail relationships. It seems like the current Test Scenario editor interface does not support this.
> The following rule snippet produces facts like those above, which seem untestable in the current Test Scenario editor:
> {code:java}
> when
> ...
> then
> FieldValidation $r1 = new FieldValidation("countryCode")
> insertLogical( $r1 )
> insertLogical( new FactAttributeValue($r1, "allowedValue", "US") )
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFCORE-4228) Add methods to the management API to get Capability Runtime API as an Optional object
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFCORE-4228?page=com.atlassian.jira.plugi... ]
Yeray Borges updated WFCORE-4228:
---------------------------------
Summary: Add methods to the management API to get Capability Runtime API as an Optional object (was: Weld subsystem should declare a capability)
> Add methods to the management API to get Capability Runtime API as an Optional object
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-4228
> URL: https://issues.jboss.org/browse/WFCORE-4228
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Major
>
> This issue is filed to to track the required changes in wildfly-core to complete the work on WFLY-11186
> Specifically it was identified the following minor changes:
> * -Make WeldDeploymentMarker available on wildfly-server, where other there are other clases that serve a similar purposes (JPADeploymentMarker, EjbDeploymentMarker)-
> * Add a method signature that allow retrieve an optional capability API from CapabilityServiceSupport without throwing a checked exception. That can be useful when we need a capability API that it is optional for the demanding subsystem
> WeldDeploymentMarker is consideated as part of Weld subsystem, so, we are not going to move it to wfcore
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ]
Liz Clayton edited comment on DROOLS-3452 at 1/15/19 11:12 AM:
---------------------------------------------------------------
Note, per [~tirelli]: We must support timezones, but they are optional for date times and explicitly defined. The editor must persist the date/time, if using timezone, exactly as it was typed in/selected by the user. No conversions allowed.
was (Author: uxdlc):
Note: We must support timezones, but they are optional for date times and explicitly defined. The editor must persist the date/time, if using timezone, exactly as it was typed in/selected by the user. No conversions allowed.
> Data type constraints: Date/Time
> --------------------------------
>
> Key: DROOLS-3452
> URL: https://issues.jboss.org/browse/DROOLS-3452
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3452:
-------------------------------------
Note: We must support timezones, but they are optional for date times and explicitly defined. The editor must persist the date/time, if using timezone, exactly as it was typed in/selected by the user. No conversions allowed.
> Data type constraints: Date/Time
> --------------------------------
>
> Key: DROOLS-3452
> URL: https://issues.jboss.org/browse/DROOLS-3452
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3452:
--------------------------------
Sprint: 2019 Week 02-04
> Data type constraints: Date/Time
> --------------------------------
>
> Key: DROOLS-3452
> URL: https://issues.jboss.org/browse/DROOLS-3452
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFCORE-4278) jboss-cli "java.lang.ArithmeticException: / by zero" when executed from /usr/bin/expect without tty
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-4278?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise moved JBEAP-16186 to WFCORE-4278:
------------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-4278 (was: JBEAP-16186)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
Affects Version/s: (was: 7.2.0.GA.CR2)
> jboss-cli "java.lang.ArithmeticException: / by zero" when executed from /usr/bin/expect without tty
> ---------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4278
> URL: https://issues.jboss.org/browse/WFCORE-4278
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Environment: Fedora 29, RHEL7.5
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Priority: Major
>
> Running the jboss-cli.sh from expect without tty (e.g. a cron or a jenkins job), causes a division by zero. (you can simulate non-availability of the real tty with "-nottycopy" :
> {code}
> $ /usr/bin/expect
> expect1.1> spawn -nottycopy ./jboss-cli.sh
> spawn -nottycopy ./jboss-cli.sh
> 25901
> expect1.2> interact
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.ArithmeticException: / by zero
> at org.aesh.readline.Buffer.printInsertedData(Buffer.java:582)
> at org.aesh.readline.Buffer.insert(Buffer.java:231)
> at org.aesh.readline.AeshConsoleBuffer.writeChar(AeshConsoleBuffer.java:130)
> at org.aesh.readline.Readline$AeshInputProcessor.parse(Readline.java:262)
> at org.aesh.readline.Readline$AeshInputProcessor.access$100(Readline.java:174)
> at org.aesh.readline.Readline.readInput(Readline.java:95)
> at org.aesh.readline.Readline.access$1000(Readline.java:57)
> at org.aesh.readline.Readline$AeshInputProcessor.lambda$start$1(Readline.java:333)
> at org.aesh.terminal.EventDecoder.accept(EventDecoder.java:118)
> at org.aesh.terminal.EventDecoder.accept(EventDecoder.java:31)
> at org.aesh.io.Decoder.write(Decoder.java:133)
> at org.aesh.readline.tty.terminal.TerminalConnection.openBlocking(TerminalConnection.java:216)
> at org.aesh.readline.tty.terminal.TerminalConnection.openBlocking(TerminalConnection.java:203)
> at org.jboss.as.cli.impl.ReadlineConsole$CLITerminalConnection.lambda$null$1(ReadlineConsole.java:176)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> The same works fine on EAP 7.1
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months