please note you jndi in your web application. is it really a clustering jndi?
For jndi lookup in my web application, I use t3://myserver1.mydomain.net:7001, myserver2.mydomain.net:7001 for the PROVIDER_URL. (Actual server names are different)
Contacted BEA support and got a patch CR369556 for 10.0 MP1. This resolved the issue.
Wait a minute! I thought EJB's deployed to a cluster were automagically clusterable. Is that not so?
If not, then where do you specify the "clusterable" annotation?
Have you find out what was the cause you get the BasicRemoteRef as a reference?
I'm having the same problem: I have two references to different EJB's, one is resolved as ClusterableRemoteRef which never fails, and the one resolved as BasicRemoteRef is the one that fails when for example, invoke both services when my Weblogic 11 is shutting down.