[jira] Updated: (GERONIMO-3243) ActiveMQ violates System Properties
[
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] Updated: (GERONIMO-3243) ActiveMQ violates System Properties
[
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] Updated: (GERONIMO-3243) ActiveMQ violates System Properties
[
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-configurationsglobal-variables
myConstantHello 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
[jira] Updated: (GERONIMO-3243) ActiveMQ violates System Properties
[
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
