April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2464) [DMN Editor] Decision Navigator dock: Nodes's arrows should be clickable

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2464?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2464: -------------------------------- Description: Only the node's icons are clickable, and the arrows should be clickable too. See more [here|https://github.com/kiegroup/kie-wb-common/pull/1542#issuecomment-379...]. h2. Acceptance test Check all DMN node types that can contain some expression can be expanded / collapsed by arrow in navigator dock. was: Only the node's icons are clickable, and the arrows should be clickable too. See more [here|https://github.com/kiegroup/kie-wb-common/pull/1542#issuecomment-379...]. > [DMN Editor] Decision Navigator dock: Nodes's arrows should be clickable > ------------------------------------------------------------------------ > > Key: DROOLS-2464 > URL: https://issues.jboss.org/browse/DROOLS-2464 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Minor > > Only the node's icons are clickable, and the arrows should be clickable too. > See more [here|https://github.com/kiegroup/kie-wb-common/pull/1542#issuecomment-379...]. > h2. Acceptance test > Check all DMN node types that can contain some expression can be expanded / collapsed by arrow in navigator dock. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2464) [DMN Editor] Decision Navigator dock: Nodes's arrows should be clickable

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2464?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2464: -------------------------------- Tester: Jozef Marko Affects Version/s: 7.8.0.Final > [DMN Editor] Decision Navigator dock: Nodes's arrows should be clickable > ------------------------------------------------------------------------ > > Key: DROOLS-2464 > URL: https://issues.jboss.org/browse/DROOLS-2464 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Minor > > Only the node's icons are clickable, and the arrows should be clickable too. > See more [here|https://github.com/kiegroup/kie-wb-common/pull/1542#issuecomment-379...]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10200) WARN on presence of -jmx.xml file if embedded broker is not present, instead of doing invalid wiring

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10200?page=com.atlassian.jira.plugin... ] Jeff Mesnil commented on WFLY-10200: ------------------------------------ I'm leaving it open as I think that there might be room for improvement on that topic. First, the -jms.xml files are considered legacy (we added them in the messaging-activemq subsystem as it was a feature provided by the legacy messaging subsystems) but there is no reason to use them instead of the Java EE specified XML deployment file. However, the Java EE XML file is itself very limited, it requires that the JMS broker is available as a resource adapter that supports Admin objects to create the JMS resources. As this support is optional for JMS (e.g. Artemis RA does not support them), we have a hack where we try to match a messaging-activemq pooled-connection-factory (that is backed by Artemis) to create the resources before we delegate to IronJacamar do do that with JCA. The original intent of this RFE (an application that requires JMS resources should be able to work with either an embedded broker or a remote one) is valid. It is difficult to achieve currently as the resource tree of the messaging-activemq subsystem was not considered for such a use case. The main flaw is that the pooled-connection-factory (that represents to a connection to a broker) is under the server resource *even though a pooled-connection-factory can be configured to connect to another unrelated broker*. With the current structure, we must have an embedded broker that is running to be able to connect to a remote one... I am preparing a roadmap for the messaging features related to cloud enablement and this RFE is taken into consideration. We need to have a better separation of concerns between messaging client and broker that is reflected in our management model. Once this roadmap has been discussed and approved, I'll open JIRA issues corresponding to the different RFEs (and update this one) to cover all these new use cases. > WARN on presence of -jmx.xml file if embedded broker is not present, instead of doing invalid wiring > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-10200 > URL: https://issues.jboss.org/browse/WFLY-10200 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Priority: Minor > > This is largely a topic for discussion. > If the messaging subsystem is present but no 'server' child resource is installed, there's a DUP that will try and create services for destinations in any discovered xxx-jmx.xml. These will fail due to missing dependencies on broker services. > Perhaps the DUP could just log a WARN in this case. Of course if the app depends on the destinations configured in the -jmx.xml and they are not provided otherwise (i.e. separately configured on an external broker) then the app will fail anyway, and the WARN would just help explain why. But if the destinations are available, then the -jms.xml could be regarded as just ignorable cruft left in the deployment. > For example, the app at https://github.com/jboss-openshift/openshift-quickstarts/tree/master/jta-... could benefit from this, by being able to work when deployed 1) with an embedded broker or 2) with an external broker and just an empty subsystem-messaging-activemq. > An assumption I'm making here is a subsystem=messaging-activemq is or will be useful even without a child 'server' resource. That's what our current openshift images configure when we configure for an external broker. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10211) Upgrade Ironjacamar from 1.4.8 to 1.4.9

by Lin Gao (JIRA)

Lin Gao created WFLY-10211: ------------------------------ Summary: Upgrade Ironjacamar from 1.4.8 to 1.4.9 Key: WFLY-10211 URL: https://issues.jboss.org/browse/WFLY-10211 Project: WildFly Issue Type: Component Upgrade Components: JCA Reporter: Lin Gao Assignee: Stefano Maestri -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2458) [DMN Designer] Error while removing connected decision

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2458?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2458: -------------------------------- Labels: Stunner (was: ) > [DMN Designer] Error while removing connected decision > ------------------------------------------------------ > > Key: DROOLS-2458 > URL: https://issues.jboss.org/browse/DROOLS-2458 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Roger Martínez > Priority: Critical > Labels: Stunner > Fix For: 7.8.0.Final > > Attachments: Screenshot from 2018-04-06 14-41-28.png, Screenshot from 2018-04-06 14-42-45.png > > > If there are connected decisions, user is unable to delete them. Issue was found during JBPM-6777 review, however probably there is no relation. > h2. Acceptance test > Prepare DRG diagram with all combinations of connections, be sure all node types used, try to delete each node type in situation it is either source or target of connection. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5549) org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory

by Lap Tran (JIRA)

[ https://issues.jboss.org/browse/WFLY-5549?page=com.atlassian.jira.plugin.... ] Lap Tran commented on WFLY-5549: -------------------------------- Thor Lange, it saved a lot of time for me. Thank you. > org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory > --------------------------------------------------------------------- > > Key: WFLY-5549 > URL: https://issues.jboss.org/browse/WFLY-5549 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Carlos E. Feria Vila > Assignee: Scott Marlow > > 10:06:35,545 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 61) MSC000001: Failed to start service jboss.persistenceunit."********": org.jboss.msc.service.StartException in service jboss.persistenceunit."*******": java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:172) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:117) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:667) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:182) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory > at org.dom4j.DocumentFactory.getInstance(DocumentFactory.java:97) > at org.hibernate.internal.util.xml.XMLHelper$1.doWork(XMLHelper.java:33) > at org.hibernate.internal.util.xml.XMLHelper$1.doWork(XMLHelper.java:27) > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.workWithClassLoader(ClassLoaderServiceImpl.java:342) > at org.hibernate.internal.util.xml.XMLHelper.<init>(XMLHelper.java:26) > at org.hibernate.envers.boot.internal.EnversServiceImpl.initialize(EnversServiceImpl.java:115) > at org.hibernate.envers.boot.internal.AdditionalJaxbMappingProducerImpl.produceAdditionalMappings(AdditionalJaxbMappingProducerImpl.java:99) > at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:288) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:770) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:797) > at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:154) > ... 7 more > 10:06:35,552 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "cooperativa-1.0.0.Final.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.persistenceunit.\"cooperativa-1.0.0.Final.war#CooperativaPU\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"cooperativa-1.0.0.Final.war#CooperativaPU\": java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory > Caused by: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory"}} > 10:06:35,732 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "cooperativa-1.0.0.Final.war" (runtime-name : "cooperativa-1.0.0.Final.war") > 10:06:35,733 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.persistenceunit."cooperativa-1.0.0.Final.war#CooperativaPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."cooperativa-1.0.0.Final.war#CooperativaPU": java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-777) Picketbox uses non-synchronized static maps

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-777?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-777: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1565186, https://bugzilla.redhat.com/show_bug.cgi?id=1565325 Bugzilla Update: Perform > Picketbox uses non-synchronized static maps > ------------------------------------------- > > Key: SECURITY-777 > URL: https://issues.jboss.org/browse/SECURITY-777 > Project: PicketBox > Issue Type: Bug > Affects Versions: PicketBox_4_0_20.Beta2 > Reporter: Stuart Douglas > Assignee: Stefan Guilhen > Fix For: PicketBox_4_0_20.Final > > Attachments: picketlink.diff > > > Picketbox uses quite a few static maps as global registries (yuck), and unfortunately they are not all thread safe, which can result in races as Wildfly starts security domains asynchronously. > Please see attached patch. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3733) Picketbox should be loaded lazily by the vault reader

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-3733: -------------------------------------- Summary: Picketbox should be loaded lazily by the vault reader Key: WFCORE-3733 URL: https://issues.jboss.org/browse/WFCORE-3733 Project: WildFly Core Issue Type: Bug Reporter: Stuart Douglas This will allow the ee8.preview.mode property to work correctly, otherwise EE8 API's get loaded too early. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2458) [DMN Designer] Error while removing connected decision

by Roger Martínez (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2458?page=com.atlassian.jira.plugi... ] Roger Martínez commented on DROOLS-2458: ---------------------------------------- Oh thanks for tracking this guys! So from the feedback you provide I guess there is one or two issues here: # _DeleteCanvasConnectorCommand_ - it should NOT notify element updated if the element has been deleted yeah, well in fact I think threre is a notification for element removed, this one is the one taht should be firing... # _FormPropertiesWidget_ - Probably once fixing the 1) this fix issue not happen, as this widget should be calling the _show_ only when it receives an element created or updated notification (event), so if the wrong notification event is not fired, probably the issue is not present. Anyway we should check it after fixing 1) Does that makes sense? Thx! > [DMN Designer] Error while removing connected decision > ------------------------------------------------------ > > Key: DROOLS-2458 > URL: https://issues.jboss.org/browse/DROOLS-2458 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Roger Martínez > Priority: Critical > Fix For: 7.8.0.Final > > Attachments: Screenshot from 2018-04-06 14-41-28.png, Screenshot from 2018-04-06 14-42-45.png > > > If there are connected decisions, user is unable to delete them. Issue was found during JBPM-6777 review, however probably there is no relation. > h2. Acceptance test > Prepare DRG diagram with all combinations of connections, be sure all node types used, try to delete each node type in situation it is either source or target of connection. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-118) ElasticSearch deployment fails on B11 cluster with out of memory errors

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-118?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-118: ------------------------------------------ Team: Infrastructure > ElasticSearch deployment fails on B11 cluster with out of memory errors > ----------------------------------------------------------------------- > > Key: SWSQE-118 > URL: https://issues.jboss.org/browse/SWSQE-118 > Project: Kiali QE > Issue Type: QE Task > Reporter: Kevin Earls > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > Attachments: screenshot-1.png > > > As part of KIALI-336 I'm trying to run Jaeger with ElasticSearch as its storage, using this Jenkinsfile: https://github.com/jaegertracing/jaeger-performance/blob/master/standalon... > The test is setup on B11 in the jaeger-test project https://jenkins-jaeger-test.openshift4.jonqe.lab.eng.bos.redhat.com/job/J... > I'm running into a few problems here, which may or may not be related. > 1. Even though I've run this test twice, Jenkins does not have any logs. > 2. ElasticSearch will not start up. I don't have the exact log of the problem yet, as it keeps trying to redeploy, but I have seen "Oom" errors messages, which I assume means out of memory. I will attach logs if I can catch it in this exact state. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2018