You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "solprovider (JIRA)" <ji...@apache.org> on 2007/06/13 19:36:26 UTC
[jira] Created: (GERONIMO-3243) ActiveMQ violates System Properties
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-M3, 1.2, 2.0-M4
Reporter: solprovider
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.
The error can be produced with Cocoon's SitemapVariableHolder for XMAP constants:
<map:component-configurations><global-variables>
<myConstant>Hello World</myConstant>
</global-variables></map:component-configurations>
"{global:myConstant}" errors
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.
[jira] Commented: (GERONIMO-3243) ActiveMQ violates System
Properties
Posted by "solprovider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562785#action_12562785 ]
solprovider commented on GERONIMO-3243:
---------------------------------------
If you are worried about disabling the locking, just fix ActiveMQ. If you can compile Java-1.5, easy instructions are in the fourth comment:
https://issues.apache.org/activemq/browse/AMQ-1254
2007-04-01: ActiveMQ-4.1.1 released broken. This bug was in previous releases.
2007-05-28: Bug is reported.
2007-07-07: Fix submitted.
2007-07-23: Fix added to ActiveMQ-Trunk.
2007-10-18: Geronimo's most recent release did not include the fix..
2007-12-17: ActiveMQ-5.0.0 release includes the fix. .
An ActiveMQ or Geronimo Committer should apply the fix to the ActiveMQ-4.1.1 release (and rename to ActiveMQ-4.1.1a?) Code violating basic Java should not remain unpatched.
> 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.
[jira] Commented: (GERONIMO-3243) ActiveMQ violates System
Properties
Posted by "solprovider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554313 ]
solprovider commented on GERONIMO-3243:
---------------------------------------
ActiveMQ-5.0 0 was released 20071213. Should Geronimo immediately upgrade ActiveMQ?
> 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.
[jira] Updated: (GERONIMO-3243) ActiveMQ violates System Properties
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Miller updated GERONIMO-3243:
-----------------------------------
Priority: Blocker (was: Major)
Affects Version/s: (was: 2.0-M3)
(was: 1.2)
(was: 2.0-M4)
2.0.1
2.0.2
Fix Version/s: 2.1
> 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.
[jira] Commented: (GERONIMO-3243) ActiveMQ violates System
Properties
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581751#action_12581751 ]
David Jencks commented on GERONIMO-3243:
----------------------------------------
Kaha fixed in amq 4.1 branch amq rev 640659. I expect to get a amq 4.1.2 out soon. Not sure if I can get a newer activeio out with a fix for that.
BTW the fix applied to amq trunk was quite wrong and avoided 80% of the usefulness of the lock.
> 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, 2.0.x, 2.1, 2.1.1, 2.2
> Reporter: solprovider
> Assignee: David Jencks
> Fix For: 2.2
>
>
> 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.
[jira] Updated: (GERONIMO-3243) ActiveMQ violates System Properties
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated GERONIMO-3243:
-----------------------------------
Priority: Major (was: Blocker)
Affects Version/s: 2.2
Fix Version/s: (was: 2.1.1)
(was: 2.0.x)
2.2
Assigning to 2.2, given the move to AMQ 5.0 will require some integration rework, which shouldn't go into a maintenance release like 2.1.1.
> 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, 2.0.x, 2.1, 2.1.1, 2.2
> Reporter: solprovider
> Fix For: 2.2
>
>
> 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.
[jira] Updated: (GERONIMO-3243) ActiveMQ violates System Properties
Posted by "solprovider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
solprovider updated GERONIMO-3243:
----------------------------------
Description:
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.
was:
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.
Here is a test:
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;
}
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.
> 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: 1.2, 2.0-M3, 2.0-M4
> Reporter: solprovider
>
> 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.
[jira] Updated: (GERONIMO-3243) ActiveMQ violates System Properties
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevan Miller updated GERONIMO-3243:
-----------------------------------
Affects Version/s: 2.1.1
2.1
2.0.x
Fix Version/s: (was: 2.1)
2.1.1
2.0.x
Don't have a AMQ 4.1.x fix for this, yet. We'll be looking at a move to AMQ 5 in the future.
> 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, 2.0.x, 2.1, 2.1.1
> Reporter: solprovider
> Priority: Blocker
> Fix For: 2.0.x, 2.1.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.
[jira] Commented: (GERONIMO-3243) ActiveMQ violates System
Properties
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506322 ]
David Jencks commented on GERONIMO-3243:
----------------------------------------
https://issues.apache.org/activemq/browse/AMQ-1254 contains a fix in activemq for a similar problem in the kaha store, although I don't really know how to check that it works.
> 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: 1.2, 2.0-M3, 2.0-M4
> Reporter: solprovider
>
> 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.
[jira] Closed: (GERONIMO-3243) ActiveMQ violates System Properties
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed GERONIMO-3243.
----------------------------------
Resolution: Fixed
Fixed in latest activeio and activemq 4.x and 5.x releases.
> 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, 2.0.x, 2.1, 2.1.1, 2.2
> Reporter: solprovider
> Assignee: David Jencks
> Fix For: 2.2
>
>
> 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.
[jira] Updated: (GERONIMO-3243) ActiveMQ violates System Properties
Posted by "solprovider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
solprovider updated GERONIMO-3243:
----------------------------------
Description:
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.
Here is a test:
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;
}
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.
was:
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.
The error can be produced with Cocoon's SitemapVariableHolder for XMAP constants:
<map:component-configurations><global-variables>
<myConstant>Hello World</myConstant>
</global-variables></map:component-configurations>
"{global:myConstant}" errors
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.
> 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: 1.2, 2.0-M3, 2.0-M4
> Reporter: solprovider
>
> 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.
> Here is a test:
> 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;
> }
> 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.
[jira] Commented: (GERONIMO-3243) ActiveMQ violates System
Properties
Posted by "Aman Nanner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562673#action_12562673 ]
Aman Nanner commented on GERONIMO-3243:
---------------------------------------
We are experiencing this problem as well. I'm not sure what the effect is of disabling ActiveMQ journal locking though, so I'm not sure how practical the workaround is.
> 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.
[jira] Commented: (GERONIMO-3243) ActiveMQ violates System
Properties
Posted by "solprovider (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (GERONIMO-3243) ActiveMQ violates System
Properties
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks reassigned GERONIMO-3243:
--------------------------------------
Assignee: David Jencks
> 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, 2.0.x, 2.1, 2.1.1, 2.2
> Reporter: solprovider
> Assignee: David Jencks
> Fix For: 2.2
>
>
> 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.