[JBoss JIRA] Updated: (JBAS-2870) Separate the HA aspect from the invoker proxy
by Brian Stansberry (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-2870?page=com.atlassian.jira.plug... ]
Brian Stansberry updated JBAS-2870:
-----------------------------------
Fix Version/s: Backlog
(was: JBossAS-5.0.0.CR2)
Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)])
Unscheduling this for AS 5.0.0. It's a major rework of legacy code.
> Separate the HA aspect from the invoker proxy
> ---------------------------------------------
>
> Key: JBAS-2870
> URL: https://jira.jboss.org/jira/browse/JBAS-2870
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Clustering
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: Backlog
>
> Original Estimate: 2 weeks
> Remaining Estimate: 2 weeks
>
> Comment from Scott Stark (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926369#3926369)
> HA proxy invokers like JRMPInvokerProxyHA should not exist. The only difference between an ha proxy and regular proxy would be an interceptor that selected from the available targets and set the invocation proxy such that the common Invoker proxy was told the transport proxy to use. Even an unclustered proxy could have a recover/ha sematic like blocking until the server is availble with this configuration. HA is an aspect that should not be embedded in the transport specific proxy.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 2 months
[JBoss JIRA] Created: (JBCOMMON-60) file URI and URLs not properly handled in property editors
by Adrian Brock (JIRA)
file URI and URLs not properly handled in property editors
----------------------------------------------------------
Key: JBCOMMON-60
URL: https://jira.jboss.org/jira/browse/JBCOMMON-60
Project: JBoss Common
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: common-core (2.x)
Affects Versions: 2.2.7.GA
Reporter: Adrian Brock
Assignee: Adrian Brock
Fix For: 2.2.8.GA
If you use property editors to inject file urls they are not properly handled in terms of encoding.
e.g.
file:/some/path%20withspaces
gets translated into
file:/some/path%25%20withspaces
by the Strings.toURI/URL methods
when it is trying to turn them into absolute paths.
The String passed into makeURL/URIFromFileSpec
needs to be decoded before it is turned into a file and later converted back to a URL/URI
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 2 months
[JBoss JIRA] Created: (JBAS-5791) JBossMQ ReadTask in UIL2 could block until socket timeout
by Takayoshi Kimura (JIRA)
JBossMQ ReadTask in UIL2 could block until socket timeout
---------------------------------------------------------
Key: JBAS-5791
URL: https://jira.jboss.org/jira/browse/JBAS-5791
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMS (JBossMQ)
Affects Versions: JBossAS-4.2.3.GA
Reporter: Takayoshi Kimura
Assignee: Adrian Brock
This is similar to JBPAPP-685, but in ReadTask. The in.readByte() call in ReadTask won't be interrupted when the thread is interrupted. When this happened the connection.close() call in client won't return until socket timeout, 2 min by default.
Since it's blocking socket, we can't use short timeout approach applied for WriteTask.
The only way to interrupt ReadTask is to call Socket.close() or close() on InputStream underlying socket.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 2 months
[JBoss JIRA] Created: (JBCACHE-1392) Use the correct MBeanServer if multiple MBeanServers are present.
by Robert Buck (JIRA)
Use the correct MBeanServer if multiple MBeanServers are present.
-----------------------------------------------------------------
Key: JBCACHE-1392
URL: https://jira.jboss.org/jira/browse/JBCACHE-1392
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX
Reporter: Robert Buck
Assignee: Manik Surtani
The prior bug did not fix the issue of running the cache under jboss when the following options are present:
set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote
The code is presently as follows (which is incorrect, by the way):
{code}
157 List servers=MBeanServerFactory.findMBeanServer(null);
158 if(servers == null || servers.size() == 0)
159 throw new Exception("TreeCacheView.init(): no MBeanServers found");
{code}
TreeCacheView fails to deploy because it is using the wrong MBeanServer. Rather than doing the above, you should either do something like:
{code}
import org.jboss.mx.util.MBeanServerLocator;
...
// find the local MBeanServer
MBeanServer server = MBeanServerLocator.locateJBoss();
{code}
, or you should do something like this:
{code}
public static MBeanServer getDefaultMBeanServer() {
return findMBeanServer("jboss");
}
private static MBeanServer findMBeanServer(String agentId) {
List servers = MBeanServerFactory.findMBeanServer(null);
if (servers != null && servers.size() > 0) {
for (Object object : servers) {
MBeanServer server = (MBeanServer) object;
if (server.getDefaultDomain().equals(agentId)) {
return server;
}
}
}
return null;
}
{code}
The reason is because with Java 5, when the "-Dcom.sun.management.jmxremote" switch is turned on, the default platform MBeanServer is the zeroth instance rather than "jboss".
See:
http://fisheye.jboss.com/browse/JBossCache/core/support-branches/1.4.1.SP...
To test, deploy the tree cache view, and start JBoss with the JAVA_OPTS mentioned above.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 2 months