[JBoss JIRA] (WFLY-9590) Auto-[create|delete]-jms-queues cannot be disabled
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-9590?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil moved JBEAP-13898 to WFLY-9590:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9590 (was: JBEAP-13898)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: ActiveMQ)
(was: JMS)
Affects Version/s: (was: 7.2.0.GA)
> Auto-[create|delete]-jms-queues cannot be disabled
> --------------------------------------------------
>
> Key: WFLY-9590
> URL: https://issues.jboss.org/browse/WFLY-9590
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> For more information about origin of this issue see JBEAP-13856.
> Auto-create-jms-queues and auto-delete-jms-queues enable or disable automatic creation or deletion of JMS queues when they are requested or when they are not used anymore.
> In EAP 7.1 the features are disabled by default and they are Technical previews.
> In EAP 7.2 the features cannot be disabled via mentioned management attributes and thus they are always enabled. The “cannot be” in previous sentence means that the configuration has no effect.
> *Customer impact:* Behavior of messaging broker was changed in case of automatic creation and deletion JMS destinations.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-9590) auto-[create|delete]-jms-queues are not supported in Artemis 2.4
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-9590?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil updated WFLY-9590:
------------------------------
Summary: auto-[create|delete]-jms-queues are not supported in Artemis 2.4 (was: Auto-[create|delete]-jms-queues cannot be disabled)
> auto-[create|delete]-jms-queues are not supported in Artemis 2.4
> ----------------------------------------------------------------
>
> Key: WFLY-9590
> URL: https://issues.jboss.org/browse/WFLY-9590
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> For more information about origin of this issue see JBEAP-13856.
> Auto-create-jms-queues and auto-delete-jms-queues enable or disable automatic creation or deletion of JMS queues when they are requested or when they are not used anymore.
> In EAP 7.1 the features are disabled by default and they are Technical previews.
> In EAP 7.2 the features cannot be disabled via mentioned management attributes and thus they are always enabled. The “cannot be” in previous sentence means that the configuration has no effect.
> *Customer impact:* Behavior of messaging broker was changed in case of automatic creation and deletion JMS destinations.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFCORE-2673) HTTP redirect if both http and https socket-binding is configured for http-interface
by Bartosz Spyrko-Śmietanko (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2673?page=com.atlassian.jira.plugi... ]
Bartosz Spyrko-Śmietanko reassigned WFCORE-2673:
------------------------------------------------
Assignee: (was: Bartosz Spyrko-Śmietanko)
> HTTP redirect if both http and https socket-binding is configured for http-interface
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-2673
> URL: https://issues.jboss.org/browse/WFCORE-2673
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Ondrej Lukas
>
> In case when both http and https socket-binding is configured for management http-interface and http port is accessed then server tries to redirect automatically to https port. Access http is not possible.
> It causes that it is impossible to connect to http-interface with clients which do not supports https (even if http port is provided by application server), i.e. following ModelControllerClient is not able to connect to http-interface when both http and https socket-binding is configured:
> {code}
> ModelControllerClient client = ModelControllerClient.Factory
> .create(new ModelControllerClientConfiguration.Builder()
> .setProtocol("remote+http")
> .setPort(9990)
> .setHostName("localhost")
> .setConnectionTimeout(10000).build())
> {code}
> See:
> {code}
> curl -v -H 'Upgrade: jboss-remoting' http://localhost:9990
> * Rebuilt URL to: http://localhost:9990/
> * Hostname was NOT found in DNS cache
> * Trying 127.0.0.1...
> * Connected to localhost (127.0.0.1) port 9990 (#0)
> > GET / HTTP/1.1
> > User-Agent: curl/7.38.0
> > Host: localhost:9990
> > Accept: */*
> > Upgrade: jboss-remoting
> >
> < HTTP/1.1 302 Found
> < Connection: keep-alive
> < Location: https://localhost:9993/
> < Content-Length: 0
> < Date: Thu, 13 Apr 2017 11:59:56 GMT
> <
> * Connection #0 to host localhost left intact
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2157) DMN Editor: Contexts: Add special behaviour of last row
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2157?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2157:
-----------------------------------
Tester: Jozef Marko
> DMN Editor: Contexts: Add special behaviour of last row
> -------------------------------------------------------
>
> Key: DROOLS-2157
> URL: https://issues.jboss.org/browse/DROOLS-2157
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> The last row of a {{Context}} should span all columns and populate the last {{ContextEntry}} in the {{Context}}. It should not have a variable. This is the XML for a _regular_ row and the _final_ row:
> {code}
> <semantic:context id="_f4f86e5f-e3e3-4b99-9260-8086764e598f">
> <semantic:contextEntry>
> <semantic:variable id="_779ca919-15d8-48d0-a9f0-e0203e60fac6" name="in1"/>
> <semantic:literalExpression id="_4b8b8cc1-a56c-4673-8334-96e178cd04a4">
> <semantic:text>"literal exp" </semantic:text>
> </semantic:literalExpression>
> </semantic:contextEntry>
> <semantic:contextEntry>
> <semantic:literalExpression id="_297181da-d0d5-4137-960b-34836d5570e5">
> <semantic:text>"result" </semantic:text>
> </semantic:literalExpression>
> </semantic:contextEntry>
> </semantic:context>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2157) DMN Editor: Contexts: Add special behaviour of last row
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2157?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2157:
----------------------------------------
Things to do:
* Add a new {{ContextEntry}} to the definition for the last row.
* Use a default (variable) "name" for the {{ContextEntry}}. This may become irrelevant if the grid rendering changes to ignore the "name" column.
* Prevent editing the "name" for the last {{ContextEntry}}
* Prevent dragging the last row, or other rows past the last row.
* Prevent deleting the last row (it is impossible to delete rows at the moment!)
* Insert new {{ContextEntry}} rows before the last row.
> DMN Editor: Contexts: Add special behaviour of last row
> -------------------------------------------------------
>
> Key: DROOLS-2157
> URL: https://issues.jboss.org/browse/DROOLS-2157
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> The last row of a {{Context}} should span all columns and populate the last {{ContextEntry}} in the {{Context}}. It should not have a variable. This is the XML for a _regular_ row and the _final_ row:
> {code}
> <semantic:context id="_f4f86e5f-e3e3-4b99-9260-8086764e598f">
> <semantic:contextEntry>
> <semantic:variable id="_779ca919-15d8-48d0-a9f0-e0203e60fac6" name="in1"/>
> <semantic:literalExpression id="_4b8b8cc1-a56c-4673-8334-96e178cd04a4">
> <semantic:text>"literal exp" </semantic:text>
> </semantic:literalExpression>
> </semantic:contextEntry>
> <semantic:contextEntry>
> <semantic:literalExpression id="_297181da-d0d5-4137-960b-34836d5570e5">
> <semantic:text>"result" </semantic:text>
> </semantic:literalExpression>
> </semantic:contextEntry>
> </semantic:context>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFCORE-1392) Undeploy doesn't remove Data content if server is in --admin-only mode
by Tomas Hofman (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1392?page=com.atlassian.jira.plugi... ]
Tomas Hofman commented on WFCORE-1392:
--------------------------------------
As for full replace deployment, the handler already removes the content in both modes - no changes are required and it's also not affected by modifications in DeploymentRemoveHandler.
{code}
DeploymentFullReplaceHandler:
remove old resource
contentRepository.addContent(new content) or contentRepository.syncContent(new content)
create new resource
if (ENABLED):
DeploymentHandlerUtil.replace(...) // basically just removes old services and creates new ones
else:
DeploymentHandlerUtil.undeploy(...)
complete step:
if (new and old content hashes differ, or new content is unmanaged):
contentRepository.removeContent(...)
if (is managed content):
contentRepository.addContentReference(...)
{code}
The domain controller's DeploymentFullReplaceHandler works very similarly, also removing content in the complete step of the main step (so in both modes).
> Undeploy doesn't remove Data content if server is in --admin-only mode
> -----------------------------------------------------------------------
>
> Key: WFCORE-1392
> URL: https://issues.jboss.org/browse/WFCORE-1392
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Affects Versions: 2.1.0.CR2
> Reporter: Chao Wang
> Assignee: Tomas Hofman
> Priority: Minor
>
> {noformat}
> Steps to Reproduce:
> 1. Start server instance using --admin-only flag
> 2. Deploy application using CLI command.
> ~~~
> deploy /valid/path/WebApp.war --runtime-name=WebApp.war --name=WebApp.war
> ~~~
> 3. Undeploy application using CLI command:
> ~~~
> undeploy WebApp.war
> ~~~
> 4. Application will be undeployed but content from 'data' directory are not removed.
> {noformat}
> Lines:
> https://github.com/wildfly/wildfly-core/blob/b1a4439f442f7984e681840c0f8d...
> https://github.com/wildfly/wildfly-core/blob/e737eff554ee433ca54835154fd6...
> runningMode value is ADMIN_ONLY will bypass that step in DeploymentRemoveHandler.java leads to this behavior.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years