cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wing Lian (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-1778) Change classloader strategy to load version from non system classloader
Date Thu, 16 Dec 2010 11:36:04 GMT


Wing Lian updated CASSANDRA-1778:

    Comment: was deleted

(was: I am still getting the warning below in the log when starting rc2. (this issues is listed
as fixed in rc2 changelog)

 WARN [main] 2010-12-16 02:48:19,677 (line 527) Unable to load
  at java.util.Properties$LineReader.readLine(
  at java.util.Properties.load0(
  at java.util.Properties.load(
  at org.apache.cassandra.utils.FBUtilities.getReleaseVersionString(
  at org.apache.cassandra.service.StorageService.initServer(
  at org.apache.cassandra.service.AbstractCassandraDaemon.setup(
  at org.apache.cassandra.thrift.CassandraDaemon.setup(
  at org.apache.cassandra.service.AbstractCassandraDaemon.activate(
  at org.apache.cassandra.thrift.CassandraDaemon.main(
 INFO [main] 2010-12-16 02:48:19,678 (line 348) Cassandra version: debug
 INFO [main] 2010-12-16 02:48:19,678 (line 349) Thrift API version: 19.4.0

> Change classloader strategy to load version from non system classloader
> -----------------------------------------------------------------------
>                 Key: CASSANDRA-1778
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7 beta 3
>            Reporter: Bram de Kruijff
>            Assignee: Bram de Kruijff
> At present when initializing the StorageService, FBUtilities.getReleaseVersionString()
 tries to load the resource from the ClassLoader.getSystemClassLoader(). This
typically fails in an embedded scenario (such as an OSGi container) resulting in a dummy version
at INFO and a stacktrace at WARN
>             logger_.warn("Unable to load", e);
>             return "debug version";
> My guess is that changing the implementation to using the FBUtilities.class.getClassLoader()
for loading resources would solve it and will work in almost any case I can think off. However,
as discussed on the Apache Felix mailing list, the only "right"way to do it is to allow an
optional ClassLoader to be specified (@see
> This issue was initially reported at the Amdatu jira:

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

View raw message