You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Ioannis Canellos (JIRA)" <ji...@apache.org> on 2011/08/30 12:11:37 UTC

[jira] [Created] (KARAF-842) Cellar's hazelcast instance cannot be reused outside cellar

Cellar's hazelcast instance cannot be reused outside cellar
-----------------------------------------------------------

                 Key: KARAF-842
                 URL: https://issues.apache.org/jira/browse/KARAF-842
             Project: Karaf
          Issue Type: Bug
          Components: cellar-hazelcast
    Affects Versions: cellar-2.2.1, cellar-2.2.2
            Reporter: Ioannis Canellos
            Assignee: Ioannis Canellos


It seems that the hazelcast instance that is created by cellar, cannot be reused outside cellar. The root cause is that the cellar-hazelcast bundle is trying to deserialize each object that is added to the grid, in order to pass it to the registered listeners resulting in a ClassNotFoundException.

I am currently not sure of how to deal with it. Some possible solutions are:
a) Have bundles that want to reuse the Hazelcast instance be fragments of cellar-hazelcast bundle (don't like that much).
b) Have bundles that want to reuse the Hazelcast instance create an instance of their own (this is also not very elegant).
c) Implement inside cellar a combined class loader as described here http://www.osgi.org/blog/2008/08/classy-solutions-to-tricky-proxies.html and have a listenerhook that will add the bundle class loader of each bundle that imports the service.
d) Some other solution.

What do you think?

Here is the discussion on the mailing lists:
http://karaf.922171.n3.nabble.com/Cellar-And-Hazelcast-Questions-td3184320.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (KARAF-842) Cellar's hazelcast instance cannot be reused outside cellar

Posted by "Ioannis Canellos (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ioannis Canellos resolved KARAF-842.
------------------------------------

       Resolution: Fixed
    Fix Version/s: cellar-2.2.3
                   cellar-3.0.0

Committed on trunk and branch 2.2.x. 

> Cellar's hazelcast instance cannot be reused outside cellar
> -----------------------------------------------------------
>
>                 Key: KARAF-842
>                 URL: https://issues.apache.org/jira/browse/KARAF-842
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-hazelcast
>    Affects Versions: cellar-2.2.2, cellar-2.2.1
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>             Fix For: cellar-3.0.0, cellar-2.2.3
>
>
> It seems that the hazelcast instance that is created by cellar, cannot be reused outside cellar. The root cause is that the cellar-hazelcast bundle is trying to deserialize each object that is added to the grid, in order to pass it to the registered listeners resulting in a ClassNotFoundException.
> I am currently not sure of how to deal with it. Some possible solutions are:
> a) Have bundles that want to reuse the Hazelcast instance be fragments of cellar-hazelcast bundle (don't like that much).
> b) Have bundles that want to reuse the Hazelcast instance create an instance of their own (this is also not very elegant).
> c) Implement inside cellar a combined class loader as described here http://www.osgi.org/blog/2008/08/classy-solutions-to-tricky-proxies.html and have a listenerhook that will add the bundle class loader of each bundle that imports the service.
> d) Some other solution.
> What do you think?
> Here is the discussion on the mailing lists:
> http://karaf.922171.n3.nabble.com/Cellar-And-Hazelcast-Questions-td3184320.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (KARAF-842) Cellar's hazelcast instance cannot be reused outside cellar

Posted by "Achim Nierbeck (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093651#comment-13093651 ] 

Achim Nierbeck commented on KARAF-842:
--------------------------------------

I favor c) also. 
Though I haven't looked into this problem deep enough, just something that crossed my mind, is it possible to get a grip on those classes which are in need for Hazlecast with a extender pattern which would make it easier for a "Classloader" sharing? (just my little 2 cents here ;) )

> Cellar's hazelcast instance cannot be reused outside cellar
> -----------------------------------------------------------
>
>                 Key: KARAF-842
>                 URL: https://issues.apache.org/jira/browse/KARAF-842
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-hazelcast
>    Affects Versions: cellar-2.2.2, cellar-2.2.1
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>
> It seems that the hazelcast instance that is created by cellar, cannot be reused outside cellar. The root cause is that the cellar-hazelcast bundle is trying to deserialize each object that is added to the grid, in order to pass it to the registered listeners resulting in a ClassNotFoundException.
> I am currently not sure of how to deal with it. Some possible solutions are:
> a) Have bundles that want to reuse the Hazelcast instance be fragments of cellar-hazelcast bundle (don't like that much).
> b) Have bundles that want to reuse the Hazelcast instance create an instance of their own (this is also not very elegant).
> c) Implement inside cellar a combined class loader as described here http://www.osgi.org/blog/2008/08/classy-solutions-to-tricky-proxies.html and have a listenerhook that will add the bundle class loader of each bundle that imports the service.
> d) Some other solution.
> What do you think?
> Here is the discussion on the mailing lists:
> http://karaf.922171.n3.nabble.com/Cellar-And-Hazelcast-Questions-td3184320.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (KARAF-842) Cellar's hazelcast instance cannot be reused outside cellar

Posted by "Gareth Collins (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094767#comment-13094767 ] 

Gareth Collins commented on KARAF-842:
--------------------------------------

(c) looks like the best solution.

thanks,
Gareth

> Cellar's hazelcast instance cannot be reused outside cellar
> -----------------------------------------------------------
>
>                 Key: KARAF-842
>                 URL: https://issues.apache.org/jira/browse/KARAF-842
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-hazelcast
>    Affects Versions: cellar-2.2.2, cellar-2.2.1
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>
> It seems that the hazelcast instance that is created by cellar, cannot be reused outside cellar. The root cause is that the cellar-hazelcast bundle is trying to deserialize each object that is added to the grid, in order to pass it to the registered listeners resulting in a ClassNotFoundException.
> I am currently not sure of how to deal with it. Some possible solutions are:
> a) Have bundles that want to reuse the Hazelcast instance be fragments of cellar-hazelcast bundle (don't like that much).
> b) Have bundles that want to reuse the Hazelcast instance create an instance of their own (this is also not very elegant).
> c) Implement inside cellar a combined class loader as described here http://www.osgi.org/blog/2008/08/classy-solutions-to-tricky-proxies.html and have a listenerhook that will add the bundle class loader of each bundle that imports the service.
> d) Some other solution.
> What do you think?
> Here is the discussion on the mailing lists:
> http://karaf.922171.n3.nabble.com/Cellar-And-Hazelcast-Questions-td3184320.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (KARAF-842) Cellar's hazelcast instance cannot be reused outside cellar

Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093681#comment-13093681 ] 

Jean-Baptiste Onofré commented on KARAF-842:
--------------------------------------------

c) looks better for me.

> Cellar's hazelcast instance cannot be reused outside cellar
> -----------------------------------------------------------
>
>                 Key: KARAF-842
>                 URL: https://issues.apache.org/jira/browse/KARAF-842
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-hazelcast
>    Affects Versions: cellar-2.2.2, cellar-2.2.1
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>
> It seems that the hazelcast instance that is created by cellar, cannot be reused outside cellar. The root cause is that the cellar-hazelcast bundle is trying to deserialize each object that is added to the grid, in order to pass it to the registered listeners resulting in a ClassNotFoundException.
> I am currently not sure of how to deal with it. Some possible solutions are:
> a) Have bundles that want to reuse the Hazelcast instance be fragments of cellar-hazelcast bundle (don't like that much).
> b) Have bundles that want to reuse the Hazelcast instance create an instance of their own (this is also not very elegant).
> c) Implement inside cellar a combined class loader as described here http://www.osgi.org/blog/2008/08/classy-solutions-to-tricky-proxies.html and have a listenerhook that will add the bundle class loader of each bundle that imports the service.
> d) Some other solution.
> What do you think?
> Here is the discussion on the mailing lists:
> http://karaf.922171.n3.nabble.com/Cellar-And-Hazelcast-Questions-td3184320.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira