<![CDATA[Latest posts for the topic "Classloader woes"]]> http://forums.terracotta.org/forums/posts/list/5.page JForum - http://www.jforum.net Classloader woes eh. We use LBQ:s for the communication. We have 3 different (the default webapp, ws & bnet) webapps deployed in jboss. In production there is only one app running on each node (the other disabled in application.xml) but in testing we want allt three to be enabled on the same node. We've got it working with the default sending messages to eh but when we try to enable bnet we get a ClassNotFoundException on the class we use as a LBQ wrapper (which is shared and accessible from a root). To alleviate the problem we found the tag and added this: Code:
        <dso>
            <app-groups>
                <app-group name="eventHorizon">
                    <web-application>ROOT</web-application>
                    <web-application>bnet</web-application>
                    <web-application>ws</web-application>
                    <named-classloader>Standard.system</named-classloader>
                </app-group>
            </app-groups>
And suddenly nothing works. Now we can't send from ws either and I'm a bit lost here. I'm pretty certain it is a class-loader thing, the debug printouts and exceptions point to it. Any pointers to a solution would be greatly appreciated. Full tc-config here: ]]> http://forums.terracotta.org/forums/posts/list/2628.page#15603 http://forums.terracotta.org/forums/posts/list/2628.page#15603 GMT Re:Classloader woes Code:
<app-groups>
   <app-group name="myGroup">
      <web-application>A</web-application>
      <named-classloader>Standard.system</named-classloader>
   </app-group>
</app-groups>
On host running B: Code:
<app-groups>
   <app-group name="myGroup">
      <web-application>B</web-application>
      <named-classloader>Standard.system</named-classloader>
   </app-group>
</app-groups>
Another alternative, on both hosts: Code:
<app-groups>
   <app-group name="myGroup">
      <web-application>A</web-application>
      <web-application>B</web-application>
      <named-classloader>Standard.system</named-classloader>
   </app-group>
</app-groups>
All applications communicate objects declared in a jar library shared between all applications, e.g. in WEB-INF/lib of the web apps, and in the classpath of the POJO app. The app-group documentation isn't clear beyond the two basic cases covered there - multiple web-apps, and web-app+pojo, so any help appreciated! Regards Anders ]]> http://forums.terracotta.org/forums/posts/list/2628.page#15613 http://forums.terracotta.org/forums/posts/list/2628.page#15613 GMT Re:Classloader woes Code:
<app-groups>
    <app-group name="myGroup1">
       <named-classloader>Standard.system</named-classloader>
   </app-group>
    <app-group name="myGroup2">
       <web-application>ROOT</web-application>
       <named-classloader>Standard.system</named-classloader>
    </app-group>
 </app-groups>
This one is deployed on all 3 nodes. This seems to work so far. This is not ideal, however. We would like to change the context of the webb-apps. As before, any hints greatly appreciated. Btw, the app-group named myGroup1, is it meaningful in any way? cheer Erik Svensson, Memnon]]> http://forums.terracotta.org/forums/posts/list/2628.page#15618 http://forums.terracotta.org/forums/posts/list/2628.page#15618 GMT Re:Classloader woes http://forums.terracotta.org/forums/posts/list/2628.page#15680 http://forums.terracotta.org/forums/posts/list/2628.page#15680 GMT Re:Classloader woes http://forums.terracotta.org/forums/posts/list/2628.page#15685 http://forums.terracotta.org/forums/posts/list/2628.page#15685 GMT Re:Classloader woes http://forums.terracotta.org/forums/posts/list/2628.page#21367 http://forums.terracotta.org/forums/posts/list/2628.page#21367 GMT Re:Classloader woes

apaliwal wrote:
Is this still an issue? 
Very much so. cheers Erik Svensson, Memnon Networks AB]]> http://forums.terracotta.org/forums/posts/list/2628.page#21428 http://forums.terracotta.org/forums/posts/list/2628.page#21428 GMT