[JBoss JIRA] (JGRP-1605) API breakage
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1605?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1605:
---------------------------
Description:
API changes to be done in 4.0, which break code:
* MessageDispatcher: remove MessageListener
* Merge AsyncRequestHandler and RequestHandler, OR make them 2 separate interfaces, ie. AsyncRH doesn't extend RH
was:
API changes to be done in 4.0, which break code:
* MessageDispatcher: remove MessageListener
> API breakage
> ------------
>
> Key: JGRP-1605
> URL: https://issues.jboss.org/browse/JGRP-1605
> Project: JGroups
> Issue Type: Task
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0
>
>
> API changes to be done in 4.0, which break code:
> * MessageDispatcher: remove MessageListener
> * Merge AsyncRequestHandler and RequestHandler, OR make them 2 separate interfaces, ie. AsyncRH doesn't extend RH
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JGRP-1605) API breakage
by Bela Ban (JIRA)
Bela Ban created JGRP-1605:
------------------------------
Summary: API breakage
Key: JGRP-1605
URL: https://issues.jboss.org/browse/JGRP-1605
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.0
API changes to be done in 4.0, which break code:
* MessageDispatcher: remove MessageListener
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JGRP-1603) DISCARD doesn't loopback unicast messages when inserted dynamically
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1603?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1603:
--------------------------------
OK, I fixed DISCARD: now the local address is fetched just-in-time from JChannel if null. However, this doesn't make the test pass; only if RSVP.throw_exception_on_timeout is set to false, does it pass.
The reason is that RSVP waits for acks from both A and B, but doesn't get one from B, and throws an exception, so we never even get to the point where we can check the response list.
I added DynamicDiscardTest to JGroups (thanks !), the code is in master.
> DISCARD doesn't loopback unicast messages when inserted dynamically
> -------------------------------------------------------------------
>
> Key: JGRP-1603
> URL: https://issues.jboss.org/browse/JGRP-1603
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.3
> Reporter: Dan Berindei
> Assignee: Bela Ban
> Fix For: 3.3
>
> Attachments: DynamicDiscardTest.java
>
>
> If DISCARD isn't present in the stack on startup, it doesn't receive the {{SET_LOCAL_ADDRESS}} and it doesn't populate its {{localAddress}}. Because of this, it will discard all unicast messages, even if they're addressed to the local node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6648) pooled-connection-factory's inbound-config is not persisted
by Jeff Mesnil (JIRA)
Jeff Mesnil created AS7-6648:
--------------------------------
Summary: pooled-connection-factory's inbound-config is not persisted
Key: AS7-6648
URL: https://issues.jboss.org/browse/AS7-6648
Project: Application Server 7
Issue Type: Feature Request
Components: JMS
Affects Versions: 7.1.2.Final (EAP)
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 8.0.0.Alpha1
The code to persist pooled-connection-factory's inbound-config is not correct in MessagingXMLWriter (the pooled-connection-factory ModelNode layout does not have an intermediate inbound-config node): any changes to AS7 configuration will discard the <inbound-config> element from the persisted XML files
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-4331) Management operations for accessing transaction logs should be exposed in the web console
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-4331?page=com.atlassian.jira.plugin.s... ]
Heiko Braun resolved AS7-4331.
------------------------------
Resolution: Done
> Management operations for accessing transaction logs should be exposed in the web console
> -----------------------------------------------------------------------------------------
>
> Key: AS7-4331
> URL: https://issues.jboss.org/browse/AS7-4331
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.1.1.Final
> Reporter: Michael Musgrove
> Assignee: Heiko Braun
> Labels: console_1.5.2, merged
> Fix For: 7.3.0.Alpha1
>
> Attachments: tx-log-view.png, tx-log.txt, tx-participants.png
>
>
> Task AS7-925 provides CLI management operations for accessing transaction logs.
> We need the same information to be made available in the web console.
> The operations are part of the log store sub model:
> org.jboss.as.txn.subsystem.LogStoreAddHandler
> We also need to expose the attribute for switching our log store implementation:
> TransactionSubsystemRootResourceDefinition.USEHORNETQSTORE
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-4331) Management operations for accessing transaction logs should be exposed in the web console
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-4331?page=com.atlassian.jira.plugin.s... ]
Heiko Braun updated AS7-4331:
-----------------------------
Labels: console_1.5.2 merged (was: console_1.5.2)
> Management operations for accessing transaction logs should be exposed in the web console
> -----------------------------------------------------------------------------------------
>
> Key: AS7-4331
> URL: https://issues.jboss.org/browse/AS7-4331
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.1.1.Final
> Reporter: Michael Musgrove
> Assignee: Heiko Braun
> Labels: console_1.5.2, merged
> Fix For: 7.3.0.Alpha1
>
> Attachments: tx-log-view.png, tx-log.txt, tx-participants.png
>
>
> Task AS7-925 provides CLI management operations for accessing transaction logs.
> We need the same information to be made available in the web console.
> The operations are part of the log store sub model:
> org.jboss.as.txn.subsystem.LogStoreAddHandler
> We also need to expose the attribute for switching our log store implementation:
> TransactionSubsystemRootResourceDefinition.USEHORNETQSTORE
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-4331) Management operations for accessing transaction logs should be exposed in the web console
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-4331?page=com.atlassian.jira.plugin.s... ]
Heiko Braun updated AS7-4331:
-----------------------------
Labels: console_1.5.2 (was: )
Fix Version/s: 7.3.0.Alpha1
> Management operations for accessing transaction logs should be exposed in the web console
> -----------------------------------------------------------------------------------------
>
> Key: AS7-4331
> URL: https://issues.jboss.org/browse/AS7-4331
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.1.1.Final
> Reporter: Michael Musgrove
> Assignee: Heiko Braun
> Labels: console_1.5.2
> Fix For: 7.3.0.Alpha1
>
> Attachments: tx-log-view.png, tx-log.txt, tx-participants.png
>
>
> Task AS7-925 provides CLI management operations for accessing transaction logs.
> We need the same information to be made available in the web console.
> The operations are part of the log store sub model:
> org.jboss.as.txn.subsystem.LogStoreAddHandler
> We also need to expose the attribute for switching our log store implementation:
> TransactionSubsystemRootResourceDefinition.USEHORNETQSTORE
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months