[JBoss JIRA] (WFWIP-73) IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x
by Miroslav Novak (JIRA)
Miroslav Novak created WFWIP-73:
-----------------------------------
Summary: IndexOutOfBoundsException during receiving messages in remote JCA scenario between Artemis 1.5 and 2.x
Key: WFWIP-73
URL: https://issues.jboss.org/browse/WFWIP-73
Project: WildFly WIP
Issue Type: Bug
Components: Artemis
Reporter: Miroslav Novak
Assignee: Martyn Taylor
Priority: Blocker
*Scenario:*
Nodes A and B are in cluster. Destinations InQueue and OutQueue are deployed on them.
MDBs are deployed on node C and D. These MDBs read messages from InQueue of nodes A, B and sends them to OutQueue on A and B.
Nodes A,B are running Artemis 1.5. Nodes C,D are using Artemis 2.6.
# Client sends messages to InQueue on node A
# MDBs on nodes C,D read messages from remote InQueue and send them to remote OutQueue on nodes A,B
# During processing of messages nodes A and C are killed
# Client reads messages from OutQueue on node B.
*Issue*
At the end of the test, client is not able to read message
{code}
java.lang.IndexOutOfBoundsException: readerIndex(9) + length(128) exceeds writerIndex(133): UnpooledDuplicatedByteBuf(ridx: 9, widx: 133, cap: 606, unwrapped: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 0, widx: 606, cap: 606))
at io.netty.buffer.AbstractByteBuf.checkReadableBytes0(AbstractByteBuf.java:1405)
at io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1392)
at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:872)
at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:880)
at io.netty.buffer.WrappedByteBuf.readBytes(WrappedByteBuf.java:649)
at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:183)
at org.apache.activemq.artemis.api.core.SimpleString.readSimpleString(SimpleString.java:171)
at org.apache.activemq.artemis.api.core.SimpleString.readNullableSimpleString(SimpleString.java:158)
at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:69)
at org.apache.activemq.artemis.reader.TextMessageUtil.readBodyText(TextMessageUtil.java:37)
at org.apache.activemq.artemis.jms.client.ActiveMQTextMessage.doBeforeReceive(ActiveMQTextMessage.java:112)
at org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.getMessage(ActiveMQMessageConsumer.java:224)
at org.apache.activemq.artemis.jms.client.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:132)
at org.jboss.qa.hornetq.apps.clients.Receiver11.receiveMessage(Receiver11.java:151)
at org.jboss.qa.hornetq.apps.clients.ReceiverTransAck.run(ReceiverTransAck.java:89)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (WFLY-10735) Unable to disable iiop port (non-ssl)
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-10735?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski reassigned WFLY-10735:
-----------------------------------------
Assignee: Bartosz Baranowski
> Unable to disable iiop port (non-ssl)
> -------------------------------------
>
> Key: WFLY-10735
> URL: https://issues.jboss.org/browse/WFLY-10735
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Reporter: Derek Horton
> Assignee: Bartosz Baranowski
>
> Wildfly 13.0.0.Final
> Removing the "iiop" socket-binding from the orb configuration:
> <subsystem xmlns="urn:jboss:domain:iiop-openjdk:2.0">
> <orb ssl-socket-binding="iiop-ssl"/>
> <initializers security="identity" transactions="spec"/>
> <security server-requires-ssl="true" client-requires-ssl="true" support-ssl="true" security-domain="jsse"/>
> </subsystem>
> and commenting out the iiop socket-binding leads to the following error:
> 2018-07-24 14:47:29,315 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.binding.iiop"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.iiop-openjdk.orb-service is missing [jboss.binding.iiop]"]
> }
> 2018-07-24 14:47:29,351 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.binding.iiop (missing) dependents: [service jboss.iiop-openjdk.orb-service]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2787:
--------------------------------
Description:
*Background*
Persona: Business analyst or Rules practitioner
Use Cases:
As a user I want to:
* *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
* *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.)
* *Remove* Data Types from the list of available selections.
* be prevented from making selections that are not valid or would cause an error.
* know that when I edit a data type the changes will be updated in the DMN model.
Functional considerations/ pre conditions:
* Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
* Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
Verification conditions:
* Scrum team and PO review.
was:
*Background*
Persona: Business analyst or Rules practitioner
Use Cases:
As a user I want to:
* *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
* *Add* a new data type, which might be a nested object as defined by the (ItemDefinition.)
* *Remove* Data Types from the list of available selections.
* be prevented from making selections that are not valid or would cause an error.
* know that when I edit a data type the changes will be updated in the DMN model.
Functional considerations/ pre conditions:
* Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
* Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
Verification conditions:
* Scrum team and PO review.
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2738.bmpr, Screen Shot 2018-07-24 at 3.51.03 PM.png, treegrid.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.)
> * *Remove* Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (WFLY-10735) Unable to disable iiop port (non-ssl)
by Derek Horton (JIRA)
[ https://issues.jboss.org/browse/WFLY-10735?page=com.atlassian.jira.plugin... ]
Derek Horton updated WFLY-10735:
--------------------------------
Description:
Wildfly 13.0.0.Final
Removing the "iiop" socket-binding from the orb configuration:
<subsystem xmlns="urn:jboss:domain:iiop-openjdk:2.0">
<orb ssl-socket-binding="iiop-ssl"/>
<initializers security="identity" transactions="spec"/>
<security server-requires-ssl="true" client-requires-ssl="true" support-ssl="true" security-domain="jsse"/>
</subsystem>
and commenting out the iiop socket-binding leads to the following error:
2018-07-24 14:47:29,315 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.binding.iiop"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.iiop-openjdk.orb-service is missing [jboss.binding.iiop]"]
}
2018-07-24 14:47:29,351 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.binding.iiop (missing) dependents: [service jboss.iiop-openjdk.orb-service]
was:
EAP 7.1.3
Removing the "iiop" socket-binding from the orb configuration:
<subsystem xmlns="urn:jboss:domain:iiop-openjdk:2.0">
<orb ssl-socket-binding="iiop-ssl"/>
<initializers security="identity" transactions="spec"/>
<security server-requires-ssl="true" client-requires-ssl="true" support-ssl="true" security-domain="jsse"/>
</subsystem>
and commenting out the iiop socket-binding leads to the following error:
14:29:44,937 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.binding.iiop"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.iiop-openjdk.orb-service is missing [jboss.binding.iiop]"],
"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> Unable to disable iiop port (non-ssl)
> -------------------------------------
>
> Key: WFLY-10735
> URL: https://issues.jboss.org/browse/WFLY-10735
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Reporter: Derek Horton
>
> Wildfly 13.0.0.Final
> Removing the "iiop" socket-binding from the orb configuration:
> <subsystem xmlns="urn:jboss:domain:iiop-openjdk:2.0">
> <orb ssl-socket-binding="iiop-ssl"/>
> <initializers security="identity" transactions="spec"/>
> <security server-requires-ssl="true" client-requires-ssl="true" support-ssl="true" security-domain="jsse"/>
> </subsystem>
> and commenting out the iiop socket-binding leads to the following error:
> 2018-07-24 14:47:29,315 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.binding.iiop"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.iiop-openjdk.orb-service is missing [jboss.binding.iiop]"]
> }
> 2018-07-24 14:47:29,351 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.binding.iiop (missing) dependents: [service jboss.iiop-openjdk.orb-service]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (WFLY-10735) Unable to disable iiop port (non-ssl)
by Derek Horton (JIRA)
[ https://issues.jboss.org/browse/WFLY-10735?page=com.atlassian.jira.plugin... ]
Derek Horton moved JBEAP-15119 to WFLY-10735:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-10735 (was: JBEAP-15119)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Affects Version/s: 13.0.0.Final
(was: 7.1.3.GA)
> Unable to disable iiop port (non-ssl)
> -------------------------------------
>
> Key: WFLY-10735
> URL: https://issues.jboss.org/browse/WFLY-10735
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Reporter: Derek Horton
>
> EAP 7.1.3
> Removing the "iiop" socket-binding from the orb configuration:
> <subsystem xmlns="urn:jboss:domain:iiop-openjdk:2.0">
> <orb ssl-socket-binding="iiop-ssl"/>
> <initializers security="identity" transactions="spec"/>
> <security server-requires-ssl="true" client-requires-ssl="true" support-ssl="true" security-domain="jsse"/>
> </subsystem>
> and commenting out the iiop socket-binding leads to the following error:
> 14:29:44,937 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.binding.iiop"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.iiop-openjdk.orb-service is missing [jboss.binding.iiop]"],
> "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2787:
--------------------------------
Attachment: Screen Shot 2018-07-24 at 3.51.03 PM.png
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2738.bmpr, Screen Shot 2018-07-24 at 3.51.03 PM.png, treegrid.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * *Add* a new data type, which might be a nested object as defined by the (ItemDefinition.)
> * *Remove* Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2787:
-------------------------------------
added [~manstis]'s mockup, for reference.
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2738.bmpr, treegrid.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * *Add* a new data type, which might be a nested object as defined by the (ItemDefinition.)
> * *Remove* Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2787:
--------------------------------
Attachment: DROOLS-2738.bmpr
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2738.bmpr, treegrid.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * *Add* a new data type, which might be a nested object as defined by the (ItemDefinition.)
> * *Remove* Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months