William Evans wrote:
> I have an application that uses Commons Configuration.
>
> It runs on an AMD64 SunFire (dual processor) box under Solaris 10.
>
> When I run with the JVM in 32 bit it runs fine but as soon as I try it
> in 64 bit mode it takes a JVM crash.
>
>
>
> I isolated the problem to calls into the Configuration package and wrote
> a test class that does only the following:
>
>
>
> try {
>
> Configuration config = new
> PropertiesConfiguration(args[0]);
>
> System.out.println("Properties:");
>
> for (Iterator iter = config.getKeys(); iter.hasNext();)
> {
>
> String key = (String) iter.next();
>
> System.out.println("\n" + key + " = " +
> config.getString(key));
>
> }
>
> }
>
> catch (Exception e) {
>
> System.out.println("Error reading file " + args[0] +
> "\n" + e.toString());
>
> }
>
>
>
> Almost every time I run it crashes the JVM but only when running in 64
> bit mode.
>
>
>
> Has anyone else seen this?
>
> Bill
>
I haven't seen this before. What makes me wonder is that
PropertiesConfiguration by inheriting from BaseConfiguration is (at
least for the methods you use in your test) only a thin wrapper for a
map object (in fact it's a org.apache.commons.collections.map.LinkedMap).
Any chance that you can find out the concrete line where the crash
happens (maybe by adding further trace statements and flushing the
output stream after each write)?
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
|