[JBoss JIRA] (WFWIP-90) [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-90?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak commented on WFWIP-90:
-------------------------------------
This is regression against EAP 7.1 (Artemis 1.5.5.012).
> [Artemis 2.x upgrade] Undelivered messages in remote jca topology after restart
> -------------------------------------------------------------------------------
>
> Key: WFWIP-90
> URL: https://issues.jboss.org/browse/WFWIP-90
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
>
> There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test.
> Test scenario:
> * Start 2 server in Artemis cluster
> * Start 2 servers with MDB connected to Artemis cluster
> ** MDB resends messages from InQueue to OutQueue from/to remote cluster
> * Send messages to InQueue
> * Restart all server (one by one)
> * Consumes messages from OutQueue
> Results:
> After the test there are missing messages in OutQueue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-88) [Artemis 2.x upgrade] Server shutdown hangs with active MDB
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-88?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak commented on WFWIP-88:
-------------------------------------
It's regression against EAP 7.1 (Artemis 1.5.5.012). There this test is passing. I know we had number of occurrences of this issue.
> [Artemis 2.x upgrade] Server shutdown hangs with active MDB
> -----------------------------------------------------------
>
> Key: WFWIP-88
> URL: https://issues.jboss.org/browse/WFWIP-88
> Project: WildFly WIP
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: logs.zip
>
>
> There is regression in scenario where server with MDB which is connected throught remote JCA to another server cannot be cleanly shutdown (or it takes very long time) when remote server is killed. This is similar issue as JBEAP-9123.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELYWEB-8) constraint drive authentication method in undertow doesn't work with elytron
by Bartosz Spyrko-Śmietanko (JIRA)
[ https://issues.jboss.org/browse/ELYWEB-8?page=com.atlassian.jira.plugin.s... ]
Bartosz Spyrko-Śmietanko moved ELY-1609 to ELYWEB-8:
----------------------------------------------------
Project: Elytron Web (was: WildFly Elytron)
Key: ELYWEB-8 (was: ELY-1609)
Component/s: (was: HTTP)
Affects Version/s: (was: 1.4.0.Final)
Fix Version/s: (was: 1.5.2.CR1)
> constraint drive authentication method in undertow doesn't work with elytron
> ----------------------------------------------------------------------------
>
> Key: ELYWEB-8
> URL: https://issues.jboss.org/browse/ELYWEB-8
> Project: Elytron Web
> Issue Type: Bug
> Reporter: Darran Lofthouse
> Assignee: Bartosz Spyrko-Śmietanko
> Priority: Critical
>
> When elytron is enabled constraint driven authentication method (i.e. proactive-authentication=false) has no effect.
> If you try to request an unsecured page sending in an invalid user with basic authentication, you should get the page returned with constraint drive authentication and a 401 with proactive authentication. This is what happens without Elytron enabled. But if you enable Elytron it gives a 401 in both cases.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months