geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "solprovider (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3243) ActiveMQ violates System Properties
Date Tue, 04 Dec 2007 23:25:43 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548463
] 

solprovider commented on GERONIMO-3243:
---------------------------------------

ActiveMQ-4.1.1 is broken. The fix was committed to ActiveMQ in July.  ActiveMQ-5.0 is fixed
and available as snapshots.  

Geronimo-2.0.1 and 2.0.2 have been released with ActiveMQ-4.1.1; this issue was unresolved.
 Does the Geronimo project believe releasing broken code is more important than not releasing
snapshots of library dependencies?

Kevan Miller removed that this issue affects Geronimo-1.2 so administrators of the older Geronimo
will be unaware the issue affects their servers.  Kevan reassigned this issue to Geronimo-2.1.
 (Is 2.0.3 or 2.1 the next release?)

> ActiveMQ violates System Properties
> -----------------------------------
>
>                 Key: GERONIMO-3243
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3243
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ
>    Affects Versions: 2.0.1, 2.0.2
>            Reporter: solprovider
>            Priority: Blocker
>             Fix For: 2.1
>
>
> The latest Geronimo 1.2 and 2.0 use ActiveMQ.  (Would someone familiar with Geronimo
development please add all affected versions?)
> ActiveMQ adds a HashMap as a global Property named "org.apache.activeio.journal.active.lockMap".
> Properties must use Strings for keys and values per http://java.sun.com/j2se/1.4.2/docs/api/java/util/Properties.html
> This causes any code reading all the Properties and expecting Strings to error.
> {code:title=Test Code|borderStyle=solid}
>    boolean test(){  //true = passes, false = failed.
>       boolean test = true;
>       java.util.Properties properties = System.getProperties();
>       java.util.Enumeration enumeration = properties.elements();
>       while(test & enumeration.hasMoreElements()) test= String.class.equals(enumeration.nextElement().getClass());
>       enumeration = properties.keys();
>       while(test & enumeration.hasMoreElements()) test= String.class.equals(enumeration.nextElement().getClass());
>       return test;
>    }
> {code}
> The permanent fix is for Geronimo to update to a better version of ActiveMQ, either downgrading
to before the bug was programmed or wait for the ActiveMQ team to follow the standards.  That
is unlikely to be tested and released quickly.
> The quick fix  is to disable the offensive code.  For Geronimo 1.2 on Windows, add this
line at the beginning of STARTUP.BAT:
> SET GERONIMO_OPTS=-Dorg.apache.activeio.journal.active.DisableLocking=true %GERONIMO_OPTS%
> David Jencks suggested that Geronimo can set the org.apache.activeio.journal.active.DisableLocking
property in a Geronimo SystemProperties gbean, there's one called ServerSystemProperties in
j2ee-server.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message