[ 
https://issues.apache.org/jira/browse/CASSANDRA-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195011#comment-13195011
 ] 

Peter Schuller commented on CASSANDRA-3797:
-------------------------------------------

Really? That's strange. I just re-tried again to double-check (ant clean and 
everything) and the patch seems to make a difference here.

In the case of Class.forName() I cannot believe that is not supposed to be 
guaranteed. Are you *sure* it's not working? I would have to assume static 
initialization must by definition happen for Class.forName() to fullfil its 
contract (even if I could possibly buy slightly more easily that the 
staticallyInitialize() NOOP didn't, but even that seems like a stretch).

I am just building and {{./bin/cassandra -f}} and immediately attaching with 
visualvm.
                
> StorageProxy static initialization not triggered until thrift requests come in
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-3797
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3797
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Peter Schuller
>            Assignee: Peter Schuller
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: 3797-forname.txt, CASSANDRA-3797-trunk-v1.txt
>
>
> While plugging in the metrics library for CASSANDRA-3671 I realized (because 
> the metrics library was trying to add a shutdown hook on metric creation) 
> that starting cassandra and simply shutting it down, causes StorageProxy to 
> not be initialized until the drain shutdown hook.
> Effects:
> * StorageProxy mbean missing in visualvm/jconsole after initial startup 
> (seriously, I thought I was going nuts ;))
> * And in general anything that makes assumptions about running early, or at 
> least not during JVM shutdown, such as the metrics library, will be 
> problematic

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to