[JBoss JIRA] (REMJMX-4) Allow for long method calls within the protocol.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/REMJMX-4?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated REMJMX-4:
----------------------------------
Fix Version/s: 1.0.1.GA
(was: 1.0.0.CR1)
> Allow for long method calls within the protocol.
> ------------------------------------------------
>
> Key: REMJMX-4
> URL: https://issues.jboss.org/browse/REMJMX-4
> Project: Remoting JMX
> Issue Type: Task
> Components: Connection, RPC
> Reporter: Darran Lofthouse
> Fix For: 1.0.1.GA
>
>
> Methods such as invoke could take a long time to return depending on what the MBean is actually doing.
> This task is to build support for this into the protocol, 2 initial ideas are: -
> 1 - Allow the client to 'ping' the server after a request has timed out and ask the server is this request still running, server side the we can track the correlation IDs of current requests an check it is still in-progress.
> 2 - The server could periodically send a message to the client to say the message is still in progress, the client could cache these and on timing out check if one has been received recently and wait again if one has.
> 3 - Any other suggestions?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (AS7-3572) Changing a DS JNDI name leads to DS that cannot be enabled
by Heiko Braun (JIRA)
Heiko Braun created AS7-3572:
--------------------------------
Summary: Changing a DS JNDI name leads to DS that cannot be enabled
Key: AS7-3572
URL: https://issues.jboss.org/browse/AS7-3572
Project: Application Server 7
Issue Type: Bug
Components: JCA
Reporter: Heiko Braun
Assignee: Stefano Maestri
Fix For: 7.1.0.Final
This requires some clarification: I can change the jndi name of a datasource when it's disabled. However I cannot re-enable it afterwards:
{noformat}
{
"outcome" => "failed",
"result" => {"server-groups" => {"main-server-group" => {
"7" => {
"host" => "master",
"response" => {
"outcome" => "failed",
"failure-description" => "JBAS010454: Data-source service [MyDS] is not available",
"rolled-back" => true
}
},
"server-one" => {
"host" => "master",
"response" => {
"outcome" => "failed",
"failure-description" => "JBAS010454: Data-source service [MyDS] is not available",
"rolled-back" => true
}
}
}}},
"failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
"rolled-back" => true
}
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months