Sorry, i sort of ignored your last post about the new exception. But you did
the right thing by opening a new thread to discuss it
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=161403. Let's continue
it there.
View the original post :
http://www.jboss.org/index.html?module=bb&op=vi
Yes that is definitely the issue at hand. I removed the classloader isolation
by removing the jboss-app.xml in my EAR file. I now run into another issue
which looks to be the same as mentioned in this post:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212804#4212804
If I launch a s
Looks like this issue https://jira.jboss.org/jira/browse/EJBTHREE-1876
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255540#4255540
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4255540
Seems if I remove the classloader isolation from the jboss-app.xml file in the
ear files META-INF directory things seem to work properly. This doesn't seem
right though I should be able to isolate the classloader... Any ideas???
View the original post :
http://www.jboss.org/index.html?module=bb
Hosted the file on GigaSize so please forgive me for having to wait for the
download. If anyone has a better way for me to share these files I am all ears.
http://www.gigasize.com/get.php?d=ys0m5d1g9jd - classloader.log file
http://www.gigasize.com/get.php?d=yxqgyx4d72c - server.log file
Hope t
This post seems to be the same issue I am running into
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212804#4212804
Was anything ever resolved regarding this issue? I am going to provide the
classloader trace log file for you and hopefully it will shed some light on
this issue.
V
