[JBoss JIRA] (WFLY-11613) [GSS](7.1.z) Deleting JMS temporary destination with a closed session should throw an exception
by ehsavoie Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-11613?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet moved JBEAP-16241 to WFLY-11613:
--------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-11613 (was: JBEAP-16241)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: ActiveMQ)
Affects Version/s: 15.0.1.Final
(was: 7.1.5.GA)
> [GSS](7.1.z) Deleting JMS temporary destination with a closed session should throw an exception
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-11613
> URL: https://issues.jboss.org/browse/WFLY-11613
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 15.0.1.Final
> Reporter: ehsavoie Hugonnet
> Assignee: Martyn Taylor
> Priority: Major
>
> If a client closes its JMS session (intentionally or not) and then invokes javax.jms.TemporaryQueue.delete() or javax.jms.TemporaryTopic.delete() these methods will return without actually deleting the destination (because the underlying session was closed). This can be confusing and/or mask programming errors.
> The JavaDoc for{{ javax.jms.TemporaryQueue }}states that a JMSException should be thrown, "if the JMS provider fails to delete the temporary queue due to some internal error."
> Options
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11613) Deleting JMS temporary destination with a closed session should throw an exception
by ehsavoie Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-11613?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet updated WFLY-11613:
-------------------------------------
Summary: Deleting JMS temporary destination with a closed session should throw an exception (was: [GSS](7.1.z) Deleting JMS temporary destination with a closed session should throw an exception)
> Deleting JMS temporary destination with a closed session should throw an exception
> ----------------------------------------------------------------------------------
>
> Key: WFLY-11613
> URL: https://issues.jboss.org/browse/WFLY-11613
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 15.0.1.Final
> Reporter: ehsavoie Hugonnet
> Assignee: Martyn Taylor
> Priority: Major
>
> If a client closes its JMS session (intentionally or not) and then invokes javax.jms.TemporaryQueue.delete() or javax.jms.TemporaryTopic.delete() these methods will return without actually deleting the destination (because the underlying session was closed). This can be confusing and/or mask programming errors.
> The JavaDoc for{{ javax.jms.TemporaryQueue }}states that a JMSException should be thrown, "if the JMS provider fails to delete the temporary queue due to some internal error."
> Options
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11613) Deleting JMS temporary destination with a closed session should throw an exception
by ehsavoie Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-11613?page=com.atlassian.jira.plugin... ]
ehsavoie Hugonnet reassigned WFLY-11613:
----------------------------------------
Assignee: ehsavoie Hugonnet (was: Martyn Taylor)
> Deleting JMS temporary destination with a closed session should throw an exception
> ----------------------------------------------------------------------------------
>
> Key: WFLY-11613
> URL: https://issues.jboss.org/browse/WFLY-11613
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 15.0.1.Final
> Reporter: ehsavoie Hugonnet
> Assignee: ehsavoie Hugonnet
> Priority: Major
>
> If a client closes its JMS session (intentionally or not) and then invokes javax.jms.TemporaryQueue.delete() or javax.jms.TemporaryTopic.delete() these methods will return without actually deleting the destination (because the underlying session was closed). This can be confusing and/or mask programming errors.
> The JavaDoc for{{ javax.jms.TemporaryQueue }}states that a JMSException should be thrown, "if the JMS provider fails to delete the temporary queue due to some internal error."
> Options
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11612) Not possible to configure more than 1 passivation-store per deployment
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-11612?page=com.atlassian.jira.plugin... ]
Paul Ferraro moved JBEAP-16238 to WFLY-11612:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-11612 (was: JBEAP-16238)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
EJB
(was: Clustering)
(was: EJB)
Affects Version/s: 15.0.1.Final
(was: 7.2.0.GA.CR4)
Fix Version/s: (was: 7.2.1.GA)
> Not possible to configure more than 1 passivation-store per deployment
> ----------------------------------------------------------------------
>
> Key: WFLY-11612
> URL: https://issues.jboss.org/browse/WFLY-11612
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 15.0.1.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> In EAP 7.1 and 7.2 per subdeployment, in the EAR, only one passivation store can be used.
> If within one EAR-subdeployment caches "infinispanCache" and "infinispanCache2" per config below are used (referenced via @Cache annotation or <ec:cache-ref> deplyoment desriptor), it results in the error listed below:
> <caches>
> <cache name="simple"/>
> <cache name="infinispanCache" passivation-store-ref="infinispanStore" aliases="passivating"/>
> <cache name="infinispanCache2" passivation-store-ref="infinispanStore2" aliases="longLife"/>
> </caches>
> <passivation-stores>
> <passivation-store name="infinispanStore" cache-container="ejb" bean-cache="passivation" max-size="5"/>
> <passivation-store name="infinispanStore2" cache-container="ejb" bean-cache="passivation" max-size="10"/>
> </passivation-stores>
> using both caches from 1 EAR-subdeployment leads to:
> 2019-01-10 12:14:10,757 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.subunit."frameworktest.ear"."framework_ejb.jar".cache-dependencies-installer: org.jboss.msc.service.StartException in service jboss.deployment.subunit."frameworktest.ear"."framework_ejb.jar".cache-dependencies-installer: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730)
> [...]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.infinispan.cache-configuration.ejb.frameworktest.ear/framework_ejb.jar is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:111)
> It should be possible to configure more than 1 passivation-store per subdeployment, in particular when different time-outs are configured this way.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3373) [DMN Designer] Need Palette glyph/icon and Canvas shape for Decision Service
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3373?page=com.atlassian.jira.plugi... ]
Michael Anstis edited comment on DROOLS-3373 at 1/18/19 10:06 AM:
------------------------------------------------------------------
[~bdellasc] The text position has been changed recently (see attached).
The border stroke width is "4" and the divider's is "2". Other shapes use "1.5". The DMN Specification simply states "6.2.5... A Decision Service is represented in a DRD as rectangle with rounded corners, drawn with a heavy solid border". They're simple to change so happy to try 3 and 1.5 respectively?
was (Author: manstis):
[~bdellasc] The text position has been changed recently (see attached).
The border stroke width is "4" and the divider's is "2". Other shapes use "1.5". The DMN Specification simply states "6.2.5... A Decision Service is represented in a DRD as rectangle with rounded corners, drawn with a heavy solid border". They're simple to change so happy to try 3 and 1.5 repectively?
> [DMN Designer] Need Palette glyph/icon and Canvas shape for Decision Service
> ----------------------------------------------------------------------------
>
> Key: DROOLS-3373
> URL: https://issues.jboss.org/browse/DROOLS-3373
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: VisualDesign, drools-tools, ux_needed, visualdesign
> Fix For: 7.17.0.Final
>
> Attachments: DMN_palette_icons.png, DROOLS-3373-Node-Types.png, DecisionService-insitu.png, Screenshot from 2019-01-14 10-48-32.png, decision-service.svg, decision.svg, decision_palette.svg, decision_service_expanded_palette.svg, decision_service_palette.svg
>
>
> We need a new "Palette" icon and Canvas shape for "Decision Services".
> See Table 1: DRD components in the [DMN 1.2 Specification|https://www.omg.org/spec/DMN/1.2/Beta1/PDF].
> See also 6.2.5 Decision service for some narrative regarding the shape.
> {quote}
> A Decision Service is represented in a DRD as rectangle with rounded corners, drawn with a heavy solid border.... the Decision Service SHALL be divided into two parts with a straight solid line.
> {quote}
> We are currently adding support for the _expanded_ form however we will also require (at some stage) a Palette glyph/icon and Canvas shape for the _collapsed_ form too.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3373) [DMN Designer] Need Palette glyph/icon and Canvas shape for Decision Service
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3373?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3373:
-----------------------------------
Attachment: DROOLS-3373-Node-Types.png
> [DMN Designer] Need Palette glyph/icon and Canvas shape for Decision Service
> ----------------------------------------------------------------------------
>
> Key: DROOLS-3373
> URL: https://issues.jboss.org/browse/DROOLS-3373
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: VisualDesign, drools-tools, ux_needed, visualdesign
> Fix For: 7.17.0.Final
>
> Attachments: DMN_palette_icons.png, DROOLS-3373-Node-Types.png, DecisionService-insitu.png, Screenshot from 2019-01-14 10-48-32.png, decision-service.svg, decision.svg, decision_palette.svg, decision_service_expanded_palette.svg, decision_service_palette.svg
>
>
> We need a new "Palette" icon and Canvas shape for "Decision Services".
> See Table 1: DRD components in the [DMN 1.2 Specification|https://www.omg.org/spec/DMN/1.2/Beta1/PDF].
> See also 6.2.5 Decision service for some narrative regarding the shape.
> {quote}
> A Decision Service is represented in a DRD as rectangle with rounded corners, drawn with a heavy solid border.... the Decision Service SHALL be divided into two parts with a straight solid line.
> {quote}
> We are currently adding support for the _expanded_ form however we will also require (at some stage) a Palette glyph/icon and Canvas shape for the _collapsed_ form too.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3373) [DMN Designer] Need Palette glyph/icon and Canvas shape for Decision Service
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3373?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3373:
----------------------------------------
[~bdellasc] The text position has been changed recently (see attached).
The border stroke width is "4" and the divider's is "2". Other shapes use "1.5". The DMN Specification simply states "6.2.5... A Decision Service is represented in a DRD as rectangle with rounded corners, drawn with a heavy solid border". They're simple to change so happy to try 3 and 1.5 repectively?
> [DMN Designer] Need Palette glyph/icon and Canvas shape for Decision Service
> ----------------------------------------------------------------------------
>
> Key: DROOLS-3373
> URL: https://issues.jboss.org/browse/DROOLS-3373
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: VisualDesign, drools-tools, ux_needed, visualdesign
> Fix For: 7.17.0.Final
>
> Attachments: DMN_palette_icons.png, DecisionService-insitu.png, Screenshot from 2019-01-14 10-48-32.png, decision-service.svg, decision.svg, decision_palette.svg, decision_service_expanded_palette.svg, decision_service_palette.svg
>
>
> We need a new "Palette" icon and Canvas shape for "Decision Services".
> See Table 1: DRD components in the [DMN 1.2 Specification|https://www.omg.org/spec/DMN/1.2/Beta1/PDF].
> See also 6.2.5 Decision service for some narrative regarding the shape.
> {quote}
> A Decision Service is represented in a DRD as rectangle with rounded corners, drawn with a heavy solid border.... the Decision Service SHALL be divided into two parts with a straight solid line.
> {quote}
> We are currently adding support for the _expanded_ form however we will also require (at some stage) a Palette glyph/icon and Canvas shape for the _collapsed_ form too.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3373) [DMN Designer] Need Palette glyph/icon and Canvas shape for Decision Service
by Brian Dellascio (Jira)
[ https://issues.jboss.org/browse/DROOLS-3373?page=com.atlassian.jira.plugi... ]
Brian Dellascio commented on DROOLS-3373:
-----------------------------------------
[~manstis] If possible, I'd like to see the text in the upper half of the Decision service node moved a little further down away from the outer stroke. I agree, it's looking better than it did before, but the outer stroke is still looking a bit heavy-handed. What are the stroke thicknesses for the outer border and the separator line for that node?
> [DMN Designer] Need Palette glyph/icon and Canvas shape for Decision Service
> ----------------------------------------------------------------------------
>
> Key: DROOLS-3373
> URL: https://issues.jboss.org/browse/DROOLS-3373
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: VisualDesign, drools-tools, ux_needed, visualdesign
> Fix For: 7.17.0.Final
>
> Attachments: DMN_palette_icons.png, DecisionService-insitu.png, Screenshot from 2019-01-14 10-48-32.png, decision-service.svg, decision.svg, decision_palette.svg, decision_service_expanded_palette.svg, decision_service_palette.svg
>
>
> We need a new "Palette" icon and Canvas shape for "Decision Services".
> See Table 1: DRD components in the [DMN 1.2 Specification|https://www.omg.org/spec/DMN/1.2/Beta1/PDF].
> See also 6.2.5 Decision service for some narrative regarding the shape.
> {quote}
> A Decision Service is represented in a DRD as rectangle with rounded corners, drawn with a heavy solid border.... the Decision Service SHALL be divided into two parts with a straight solid line.
> {quote}
> We are currently adding support for the _expanded_ form however we will also require (at some stage) a Palette glyph/icon and Canvas shape for the _collapsed_ form too.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11611) Add ServletConfig and ServletContext as ConfigSources to wildfly-microprofile-config
by Ron Sigal (Jira)
Ron Sigal created WFLY-11611:
--------------------------------
Summary: Add ServletConfig and ServletContext as ConfigSources to wildfly-microprofile-config
Key: WFLY-11611
URL: https://issues.jboss.org/browse/WFLY-11611
Project: WildFly
Issue Type: Enhancement
Components: MP Config
Affects Versions: 15.0.1.Final
Reporter: Ron Sigal
Assignee: Jeff Mesnil
The MicroProfile Config spec, the smallrye implementation of the MicroProfile Config spec, and the wildfly-microprofile-config based on the smallrye implementation include about a half dozen ConfigSources, from system properties to the wildfly microprofile-config-smallrye subsystem configuration.
None of these, however, accesses the ServletConfig and ServletContext parameters in web.xml files. These would seem to be worth adding as ConfigSources.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months