Also, please take a look at the following blog entry (it also has an
example) on using GMS APIs that provides an abstraction over the
ClusterManager which is a Jxta based service provider implementation in
Shoal.
http://blogs.sun.com/shreedhar/entry/shoal_clustering_101
Let us know if you have any suggestions and issues.
regards
Shreedhar
Shreedhar Ganapathy wrote:
> Hi D.J
> Could you share with us what you were trying to do when you
> encountered the NPE ? Steps to reproduce would greatly help.
> The version of Shoal and Jxta jars that went into GF FCS b58g is not
> yet promoted in Shoal site. It has been tagged but 1.0ea bits are
> slightly older. I will get that done tomorrow.
>
> Mo should be able to answer the question on jxta sources corresponding
> to the GFv2_FCS_FINAL tagged jxta.jar
> It would be good to hear from you though about your experiment with
> shoal which ran into this issue.
>
> regards
> Shreedhar
>
> D. J. Hagberg (Sun) wrote:
>> Hi all --
>>
>> I'm trying to debug what looks like a configuration issue with Shoal
>> and am having trouble matching up the error messages in this stack
>> trace with the source code in Shoal's CVS and in the source I could
>> download from the JXTA project.
>>
>> Here's what I'm working with -- jars from FCS Glassfish v2, build 58g:
>>
>> Length Name md5
>> -------- ------------- --------------------------------
>> 1677853 jxta.jar cfe206f9f92d7d9f7f9de6943485c2d0
>> 199724 shoal-gms.jar 011247a88a8b44b06bf04258daa9d5bf
>>
>> For Shoal CVS, I've checked out and updated to
>> -r GFv2_FCS_FINAL
>>
>> For JXTA, I downloaded jxta-src-2.4.1.tar.gz but it seems that Shoal
>> might possibly be using a different version? When I download
>> jxta-lib-2.4.1.tar.gz, the jar is a different size and MD5:
>>
>> Length Name md5
>> -------- ------------- --------------------------------
>> 1617004 jxta.jar 60b9a365e3302808402e7708c0bd4082
>>
>> And nowhere in the jxta 2.4.1 source can I find the string for this
>> exception:
>>
>> ---------------------------------------------------------------------
>> 2007-09-14 13:40:17.443 SEVERE [T10 ClusterManager.<init>] Could not
>> locate World PeerGroup Module Implementation.
>> 2007-09-14 13:40:17.449 SEVERE [T10 ClusterAdapter.main] Error in
>> ClusterAdapter: java.lang.NullPointerException
>> :
>> java.lang.NullPointerException
>> at
>> com.sun.enterprise.jxtamgmt.ClusterManager.createSystemAdv(ClusterManager.java:574)
>>
>> at
>> com.sun.enterprise.jxtamgmt.ClusterManager.<init>(ClusterManager.java:152)
>>
>> at
>> com.sun.enterprise.ee.cms.impl.jxta.GroupCommunicationProviderImpl.initializeGroupCommunicationProvider(GroupCommunicationProviderImpl.java:129)
>>
>> at
>> com.sun.enterprise.ee.cms.impl.jxta.GMSContext.join(GMSContext.java:122)
>> at
>> com.sun.enterprise.ee.cms.impl.common.GroupManagementServiceImpl.join(GroupManagementServiceImpl.java:309)
>>
>> at
>> com.sun.xxxxxxxxxxxxxxxxx.nio.ClusterAdapter.startCluster(ClusterAdapter.java:178)
>>
>> ---------------------------------------------------------------------
>>
>> From looking at the jxta-2.4.1 source, it seems that there is a
>> missing entry in net/jxta/impl/config.properties for
>> PlatformPeerGroupClassName that could potentially cause this error.
>> But the messages don't look like the "Could not locate World
>> PeerGroup Module Implementation" message. Nor is the underlying
>> PeerGroupException logged or passed up the chain to help determine
>> the underlying cause.
>>
>> Here's what I've been able to trace so far:
>>
>> - When ClusterManager(String,String,Map,Map,List,List) is called, in
>> constructs a NetworkManager and then calls NetworkManager.start().
>> This is producing the first "Could not locate..." message but not
>> logging the underlying exception.
>>
>> - The later call to ClusterManager.createSystemAdv gets a NPE because
>> NetworkManager was never able to instantiate its PeerGroup.
>>
>> - NetworkManager's start method called into
>> NetPeerGroupFactory(ConfigParams,URI) which in turn tried to call
>> into WorldPeerGroupFactory(ConfigParams,URI). This called
>> WorldPeerGroupFactory.getDefaultPeerGroupClass() which was missing
>> the PlatformPeerGroupClassName property in config.properties I
>> mentioned earlier.
>>
>> Suggestions? How do I get my hands on the same jxta source code that
>> Shoal-1.0ea and Glassfish-v2b58g were built against?
>>
>> -=- D. J.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_shoal.dev.java.net
>> For additional commands, e-mail: dev-help_at_shoal.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_shoal.dev.java.net
> For additional commands, e-mail: dev-help_at_shoal.dev.java.net
>