Hi,
I too am experiencing this very same problem on 3.0.6 but I do need to make a remote
call so its not an option for me to comment out the jndi url line.
Does anyone know why this is occurring and whether or not there is a workaround?
Regards
Lea.
View the original post :
http://www.jboss.o
turn on classloader debugging (insert the following into your log4j.xml file)
|
|
|
|
|
|
|
|
|
|
|
|
if you have the jboss admin book, this is talked about in chapter 2 and it explains
how to use the jmx console to provide some additional information (not su
Thanks for your time to help on this issue.
"DummyService" MBEAN implements schedulable interface and calls the "Worker" session
bean. As I said in my original post, this works fine if you restart the jboss
appserver.
Here is the jboss log and you can see that "dummyService" MBEAN actually get
hrm - i'm not really sure. you shouldn't be getting casting exceptions if both
archives are being deployed as one unit. the classloader that deploys the ear should
be the same one that is being used to look up class references.
i haven't experienced this problem when deploying everything in one
It looks that my "enemy" is class-loader so I've added into jboss-app.xml following:
dummy:loader=dummy.ear
However it does not solving the redeployment issue at all...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831921#3831921
Reply to the post :
http
Yes the scheduler.sar & ejb.jar are in the same ear. Also I tried to separate
scheduler into single deployed file -- but same result...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831863#3831863
Reply to the post :
http://www.jboss.org/index.html?module
