[JBoss JIRA] (WFLY-12304) Upgrade Apache Artemis from 2.9.0 to 2.10.0
by Flavia Rainone (Jira)
[ https://issues.jboss.org/browse/WFLY-12304?page=com.atlassian.jira.plugin... ]
Flavia Rainone commented on WFLY-12304:
---------------------------------------
Fixing that caused a new code to be reached that wasn't reached before (because the channel already handles FileRegion, but this code was unreachable because of the CCE). That code seems to contain another bug:
{code}04:43:32,284 ERROR [org.apache.activemq.artemis.core.client] (Thread-1 (ActiveMQ-client-netty-threads)) AMQ214031: Failed to decode buffer, disconnect immediately.: java.lang.IllegalStateException: java.lang.IndexOutOfBoundsException: readerIndex(4) + length(1) exceeds writerIndex(4): PooledUnsafeDirectByteBuf(ridx: 4, widx: 4, cap: 4)
at org.apache.activemq.artemis@2.10.0//org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:390)
at org.apache.activemq.artemis@2.10.0//org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$DelegatingBufferHandler.bufferReceived(ClientSessionFactoryImpl.java:1191)
at org.apache.activemq.artemis@2.10.0//org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73)
at io.netty@4.1.34.Final//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359)
at io.netty@4.1.34.Final//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:345)
at io.netty@4.1.34.Final//io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:337)
at io.netty@4.1.34.Final//io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:323)
at io.netty@4.1.34.Final//io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
at io.netty@4.1.34.Final//io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:426)
at io.netty@4.1.34.Final//io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:278)
at io.netty@4.1.34.Final//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359)
at io.netty@4.1.34.Final//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:345)
at io.netty@4.1.34.Final//io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:337)
at io.netty@4.1.34.Final//io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1408)
at io.netty@4.1.34.Final//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:359)
at io.netty@4.1.34.Final//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:345)
at io.netty@4.1.34.Final//io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:930)
at io.netty@4.1.34.Final//io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:796)
at io.netty@4.1.34.Final//io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:427)
at io.netty@4.1.34.Final//io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:328)
at io.netty@4.1.34.Final//io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:905)
at org.apache.activemq.artemis.journal//org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
Caused by: java.lang.IndexOutOfBoundsException: readerIndex(4) + length(1) exceeds writerIndex(4): PooledUnsafeDirectByteBuf(ridx: 4, widx: 4, cap: 4)
at io.netty@4.1.34.Final//io.netty.buffer.AbstractByteBuf.checkReadableBytes0(AbstractByteBuf.java:1428)
at io.netty@4.1.34.Final//io.netty.buffer.AbstractByteBuf.readByte(AbstractByteBuf.java:723)
at io.netty@4.1.34.Final//io.netty.buffer.WrappedByteBuf.readByte(WrappedByteBuf.java:521)
at org.apache.activemq.artemis.journal//org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readByte(ChannelBufferWrapper.java:280)
at org.apache.activemq.artemis@2.10.0//org.apache.activemq.artemis.core.protocol.ServerPacketDecoder.decode(ServerPacketDecoder.java:124)
at org.apache.activemq.artemis@2.10.0//org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:377)
... 21 more{code}
I'm still working on this.
> Upgrade Apache Artemis from 2.9.0 to 2.10.0
> -------------------------------------------
>
> Key: WFLY-12304
> URL: https://issues.jboss.org/browse/WFLY-12304
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JMS
> Reporter: Martin Stefanko
> Assignee: Emmanuel Hugonnet
> Priority: Blocker
> Labels: blocker-WF18, downstream_dependency
>
> Upgrade Apache Artemis from 2.9.0.Final to 2.10.0.Final.
> Due to HA issue with Apache Artemis 2.10.0 this may not be the final version upgrade
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4517) Contextual Menus after scrolling
by Jozef Marko (Jira)
Jozef Marko created DROOLS-4517:
-----------------------------------
Summary: Contextual Menus after scrolling
Key: DROOLS-4517
URL: https://issues.jboss.org/browse/DROOLS-4517
Project: Drools
Issue Type: Bug
Components: DMN Editor, Scenario Simulation and Testing
Affects Versions: 7.27.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Attachments: Screenshot from 2019-09-10 09-48-27.png, Screenshot from 2019-09-10 09-53-24.png
There is an issue with contextual menus in ScenarioSimalation and DMN designers. When user wants to show the contextual menu after scrolling was done:
h3. ScenarioSimulation
Menu is shown at inappropriate place
!Screenshot from 2019-09-10 09-48-27.png|thumbnail!
h3. DMN
Menu is not shown at all
!Screenshot from 2019-09-10 09-53-24.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFLY-12490) Upgrade BOMs and QS due to spec artifacts which groupId/artifactId changed
by Marek Kopecky (Jira)
[ https://issues.jboss.org/browse/WFLY-12490?page=com.atlassian.jira.plugin... ]
Marek Kopecky edited comment on WFLY-12490 at 9/10/19 2:58 AM:
---------------------------------------------------------------
[~emmartins]: AFAICS, this jira also needs to update javaee bom to jakartaee8 bom files from WFLY-12468 in quickstarts (pom.xml && template/pom.xml), so this jira is blocked by WFLY-12468, right?
Edit: the answer is in WFLY-12468 description:
bq. Reference to renamed BOMs in Quickstarts project should also be updated.
was (Author: mkopecky):
[~emmartins]: AFAICS, this jira also needs to update javaee bom to jakartaee8 bom files from WFLY-12468 in quickstarts (pom.xml && template/pom.xml), so this jira is blocked by WFLY-12468, right?
> Upgrade BOMs and QS due to spec artifacts which groupId/artifactId changed
> ----------------------------------------------------------------------------
>
> Key: WFLY-12490
> URL: https://issues.jboss.org/browse/WFLY-12490
> Project: WildFly
> Issue Type: Sub-task
> Components: BOM, Quickstarts
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Major
> Fix For: 18.0.0.Final
>
>
> The Jakarta related component upgrades which changed groupId and/or artifactId of spec artifacts should be propagated to BOMs and Quickstarts projects.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFLY-12490) Upgrade BOMs and QS due to spec artifacts which groupId/artifactId changed
by Marek Kopecky (Jira)
[ https://issues.jboss.org/browse/WFLY-12490?page=com.atlassian.jira.plugin... ]
Marek Kopecky commented on WFLY-12490:
--------------------------------------
[~emmartins]: AFAICS, this jira also needs to update javaee bom to jakartaee8 bom files from WFLY-12468 in quickstarts (pom.xml && template/pom.xml), so this jira is blocked by WFLY-12468, right?
> Upgrade BOMs and QS due to spec artifacts which groupId/artifactId changed
> ----------------------------------------------------------------------------
>
> Key: WFLY-12490
> URL: https://issues.jboss.org/browse/WFLY-12490
> Project: WildFly
> Issue Type: Sub-task
> Components: BOM, Quickstarts
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Major
> Fix For: 18.0.0.Final
>
>
> The Jakarta related component upgrades which changed groupId and/or artifactId of spec artifacts should be propagated to BOMs and Quickstarts projects.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFWIP-184) Can't specify arbitrary Persistent Volume Claim Name
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-184?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFWIP-184:
------------------------------------
I admit there is not strong UseCase for this. I can think just artificiall as reusing existing PVC, complying to company naming convention. I could want to reuse PVC because of migrating from legacy applications to operator approach. And reattach operator pods to the data saved by the previous instances.
I just hit this because I was expecting name is required.
If not we should inform somehow (in documentation, CRD?) user he doesn't have to (must not) specify name. Best would be to validate somehow in time of saving WildFly CR and return to user meaningful exception.
Based on current exception I wouldn't find out what is going on without assistance of my coleague, who hit this before me.
Is validation of user input possible in Operator? Does Operator framework provide any support? Is it possible to define some basic validations in CRD?
> Can't specify arbitrary Persistent Volume Claim Name
> ----------------------------------------------------
>
> Key: WFWIP-184
> URL: https://issues.jboss.org/browse/WFWIP-184
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Major
>
> I cant create PVC with arbitrary name. It must be empty [3] or "<CR name>-volume" [2]
> When I specify PVC name I get error like
> {code}
> create Pod simple-jaxrs-eap72-0 in StatefulSet simple-jaxrs-eap72 failed error: Pod "simple-jaxrs-eap72-0" is invalid: spec.containers[0].volumeMounts[0].name: Not found: "simple-jaxrs-eap72-volume"
> {code}
> Is there any reason to not permit arbitrary PVC name?
> [1] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi...
> [2] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi...
> [3] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi...
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4513) s2i build fails at KieServerContainerVerifier if multiple listeners are set
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-4513?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-4513:
---------------------------------
Labels: support (was: )
> s2i build fails at KieServerContainerVerifier if multiple listeners are set
> ----------------------------------------------------------------------------
>
> Key: DROOLS-4513
> URL: https://issues.jboss.org/browse/DROOLS-4513
> Project: Drools
> Issue Type: Bug
> Components: build, kie server
> Affects Versions: 7.14.0.Final, 7.18.0.Final, 7.24.0.Final
> Environment: OpenShift 3.11 with rhdm72-prod-immutable-kieserver.yaml/rhdm73-prod-immutable-kieserver.yaml
> Reporter: Hiroko Miura
> Assignee: Ant Stephenson
> Priority: Major
> Labels: support
> Attachments: ruleTest.zip
>
>
> If multiple ksession are defined in kmodule.xml and Event Lister is set more than one ksession, s2i build fails at KieServerContainerVerifier with the following error.
> {noformat}
> [main] ERROR org.kie.server.services.impl.KieServerContainerVerifier - Cannot find KieModule: com.redhat.gss:ruleTest:1.0.0-SNAPSHOT
> java.lang.RuntimeException: Cannot find KieModule: com.redhat.gss:ruleTest:1.0.0-SNAPSHOT
> at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:186)
> at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:172)
> at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:65)
> at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:53)
> at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:40)
> at org.kie.server.services.impl.KieServerContainerVerifier.main(KieServerContainerVerifier.java:119)
> at org.kie.server.services.impl.KieServerContainerVerifier.main(KieServerContainerVerifier.java:101)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> [main] ERROR org.kie.server.services.impl.KieServerContainerVerifier - com.redhat.gss:ruleTest:1.0.0-SNAPSHOT not verified.
> ERROR Aborting due to error code 1 from kie server container verification
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4516) s2i build fails at KieServerContainerVerifier if multiple listeners are set
by Hiroko Miura (Jira)
Hiroko Miura created DROOLS-4516:
------------------------------------
Summary: s2i build fails at KieServerContainerVerifier if multiple listeners are set
Key: DROOLS-4516
URL: https://issues.jboss.org/browse/DROOLS-4516
Project: Drools
Issue Type: Bug
Components: build, kie server
Affects Versions: 7.14.0.Final, 7.18.0.Final, 7.24.0.Final
Environment: OpenShift 3.11 with rhdm72-prod-immutable-kieserver.yaml/rhdm73-prod-immutable-kieserver.yaml
Reporter: Hiroko Miura
Assignee: Ant Stephenson
If multiple ksession are defined in kmodule.xml and Event Lister is set more than one ksession, s2i build fails at KieServerContainerVerifier with the following error.
{noformat}
[main] ERROR org.kie.server.services.impl.KieServerContainerVerifier - Cannot find KieModule: com.redhat.gss:ruleTest:1.0.0-SNAPSHOT
java.lang.RuntimeException: Cannot find KieModule: com.redhat.gss:ruleTest:1.0.0-SNAPSHOT
at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:186)
at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:172)
at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:65)
at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:53)
at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:40)
at org.kie.server.services.impl.KieServerContainerVerifier.main(KieServerContainerVerifier.java:119)
at org.kie.server.services.impl.KieServerContainerVerifier.main(KieServerContainerVerifier.java:101)
at org.jboss.modules.Module.run(Module.java:352)
at org.jboss.modules.Module.run(Module.java:320)
at org.jboss.modules.Main.main(Main.java:593)
[main] ERROR org.kie.server.services.impl.KieServerContainerVerifier - com.redhat.gss:ruleTest:1.0.0-SNAPSHOT not verified.
ERROR Aborting due to error code 1 from kie server container verification
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4513) s2i build fails at KieServerContainerVerifier if multiple listeners are set
by Hiroko Miura (Jira)
[ https://issues.jboss.org/browse/DROOLS-4513?page=com.atlassian.jira.plugi... ]
Hiroko Miura updated DROOLS-4513:
---------------------------------
Affects Version/s: 7.14.0.Final
> s2i build fails at KieServerContainerVerifier if multiple listeners are set
> ----------------------------------------------------------------------------
>
> Key: DROOLS-4513
> URL: https://issues.jboss.org/browse/DROOLS-4513
> Project: Drools
> Issue Type: Bug
> Components: build, kie server
> Affects Versions: 7.14.0.Final, 7.18.0.Final, 7.24.0.Final
> Environment: OpenShift 3.11 with rhdm72-prod-immutable-kieserver.yaml/rhdm73-prod-immutable-kieserver.yaml
> Reporter: Hiroko Miura
> Assignee: Ant Stephenson
> Priority: Major
> Attachments: ruleTest.zip
>
>
> If multiple ksession are defined in kmodule.xml and Event Lister is set more than one ksession, s2i build fails at KieServerContainerVerifier with the following error.
> {noformat}
> [main] ERROR org.kie.server.services.impl.KieServerContainerVerifier - Cannot find KieModule: com.redhat.gss:ruleTest:1.0.0-SNAPSHOT
> java.lang.RuntimeException: Cannot find KieModule: com.redhat.gss:ruleTest:1.0.0-SNAPSHOT
> at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:186)
> at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:172)
> at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:65)
> at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:53)
> at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:40)
> at org.kie.server.services.impl.KieServerContainerVerifier.main(KieServerContainerVerifier.java:119)
> at org.kie.server.services.impl.KieServerContainerVerifier.main(KieServerContainerVerifier.java:101)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> [main] ERROR org.kie.server.services.impl.KieServerContainerVerifier - com.redhat.gss:ruleTest:1.0.0-SNAPSHOT not verified.
> ERROR Aborting due to error code 1 from kie server container verification
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFWIP-185) PVC not deleted by deleting WildFlyServer CR
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-185?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFWIP-185:
------------------------------------
I think if it is Kubernetes which is missing this feature, we shouldnt implement it by ourself. We should wait for Kubernetes to provide this feature.
> PVC not deleted by deleting WildFlyServer CR
> --------------------------------------------
>
> Key: WFWIP-185
> URL: https://issues.jboss.org/browse/WFWIP-185
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> When I delete WildFlyServer CR PVC created by this CR is not deleted as StatefullSet and Pods are .
> I see Statefull Set and Pod has ownerReferences attribute referencing to parent.
> ownerReferences
> List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.
> I dont see such attribute specified in PVC
> {code}
> # Please edit the object below. Lines beginning with a '#' will be ignored,
> # and an empty file will abort the edit. If an error occurs while saving this file will be
> # reopened with the relevant failures.
> #
> apiVersion: v1
> kind: PersistentVolumeClaim
> metadata:
> annotations:
> pv.kubernetes.io/bind-completed: "yes"
> pv.kubernetes.io/bound-by-controller: "yes"
> creationTimestamp: 2019-08-30T13:12:27Z
> finalizers:
> - kubernetes.io/pvc-protection
> labels:
> app.kubernetes.io/managed-by: wildfly-operator
> app.kubernetes.io/name: simple-jaxrs-eap72
> app.openshift.io/runtime: wildfly
> name: simple-jaxrs-eap72-volume-simple-jaxrs-eap72-0
> namespace: mchoma
> resourceVersion: "3633284"
> selfLink: /api/v1/namespaces/mchoma/persistentvolumeclaims/simple-jaxrs-eap72-volume-simple-jaxrs-eap72-0
> uid: d0aac389-cb27-11e9-b93c-fa163e9a0fb6
> spec:
> accessModes:
> - ReadWriteOnce
> resources:
> requests:
> storage: 1Mi
> volumeName: vol57
> status:
> accessModes:
> - ReadWriteMany
> - ReadWriteOnce
> capacity:
> storage: 1Gi
> phase: Bound
> {code}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months