JMS issues when migration from weblogic 9.2 to 10.3.5

Question

We are facing some issues when migration from weblogic 9.2 to 10.3.5
In  weblogic 9.2 :_
BMP Entity EJBs used in our project are read-only in nature using entity cache, below is the configuration details
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN" "http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>
Company
</ejb-name>
<entity-descriptor>
<pool>
<max-beans-in-free-pool>300</max-beans-in-free-pool>
<initial-beans-in-free-pool>150</initial-beans-in-free-pool>
</pool>
<entity-cache>
<max-beans-in-cache>3500</max-beans-in-cache>
<idle-timeout-seconds>100000</idle-timeout-seconds>
<read-timeout-seconds>0</read-timeout-seconds>
<concurrency-strategy>ReadOnly</concurrency-strategy>
</entity-cache>
Entity beans will get refreshed using the JMS messges. with in the MDB descriptor files(weblogic-ejb-jar.xml) we are using the provider URL directly and XA enabled connection factory is set to false.
migration to Weblogic 10.3.5_
With the same configurations MDB are not not getting deployed in weblogic 10 with some exception, so we removed the provider URL from weblogic-ejb-jar.xml and changed the JMS configuration to use foreign JMS and XA enable connection factory is set to true. Now when ever the JMS message is triggered Entity bean is not getting refreshed with the updated values. i.e values are stale.
Can some one look into this and provide your inputs to resolve this issue.

Answer 1

I think the Entity bean refresh problem appears to be unrelated to MDBs. The MDB is only responsible for getting the message to your application (which in turn interacts with Entity beans). You might want to try posting your question to an EJB newsgroup.
Tom