Using work managers to process WorkItems in a message driven bean

Question

Hi, I'm trying to get to grips with using a work manager (in 10.3) to process WorkItems concurrently, with the whole process being triggered by a JMS message. I've got everything working using the default work manager but I'm having problems switching over to using a work manager that I've created myself, using annotations to provide the resource ref.
My current setup, using the default work manager, is (roughly) this:
@MessageDriven(mappedName = "jms/tsrd.DependencyWorker", activationConfig = {
        @ActivationConfigProperty(propertyName = "connectionFactoryJndiName", propertyValue = "jms/connectionFactory"),
        @ActivationConfigProperty(propertyName = "ejbName", propertyValue = "tsrd.DependencyWorker"),
        @ActivationConfigProperty(propertyName = "destinationJndiName", propertyValue = "jms/tsrd.DependencyWorker"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") })
@Interceptors(SpringBeanAutowiringInterceptor.class)
public class DependencyWorker implements MessageListener {
    private WorkManager workManager;
    @Required
    @Resource(name = "taskExecutor")
    public void setWorkManager(final WorkManager workManager) {
        this.workManager = workManager;
    public void doOperation(final WorkflowControlMessage msg) throws Exception {
         Work myWork = new ...
         workManager.schedule(myWork, listener);
}With my spring config including this bean:
<bean id="taskExecutor" class="org.springframework.scheduling.commonj.WorkManagerTaskExecutor">
    <property name="workManagerName" value="wm/default"/>
    <property name="resourceRef" value="true"/>
</bean>And this works fine: when the JMS message is received I send a load of WorkItems to the default work manager and they get processed.
Now what I'd like to do is change the spring config to this:
<bean id="taskExecutor" class="org.springframework.scheduling.commonj.WorkManagerTaskExecutor">
    <property name="workManagerName" value="wm/MyWorkManager"/>
    <property name="resourceRef" value="true"/>
</bean>Where I've already created MyWorkManager as a global work manager for the server, and it's visible on the admin server for the deployment.
From the examples I've seen I know I need to add a resource ref for the MDB so that it can lookup the work manager using JNDI. We mainly use annotations, so I'd like to just be able to add this line to the MDB:
@Resource(name = "MyWorkManager", type = commonj.work.WorkManager.class, authenticationType = Resource.AuthenticationType.CONTAINER, shareable = true)But when I try that my server refuses to start:
Unable to deploy EJB: DependencyWorker from tsrd-mdb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'MyWorkManager' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation.So is there a way to fully configure my work manager just using the @Resource annotation, or do I need to add a weblogic-ejb.jar.xml file and put some specific config in there? Presumably if I do need to add an xml file then I'd need to put something like this in it?
<wls:weblogic-enterprise-bean>
    <wls:ejb-name>DependencyWorker</wls:ejb-name>
    <wls:resource-description>
        <wls:res-ref-name>MyWorkManager</wls:res-ref-name>
        <wls:jndi-name>wm/MyWorkManager</wls:jndi-name>
    </wls:resource-description>
</wls:weblogic-enterprise-bean>Am I also right in thinking that I don't need to add a dispatch policy to the MDB specifying MyWorkManager, because I don't actually want to dispatch the MDB to that manager, I just want the manager to be available to the MDB.
Thanks.

Answer 1

Hi, so I've added a weblogic-ejb.jar.xml file with a reference to the JNDI name of the work manager:
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-ejb-jar xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-ejb-jar" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd http://xmlns.oracle.com/weblogic/weblogic-ejb-jar http://xmlns.oracle.com/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd">
    <wls:weblogic-enterprise-bean>
        <wls:ejb-name>DependencyWorker</wls:ejb-name>
        <wls:resource-description>
            <wls:res-ref-name>MyWorkManager</wls:res-ref-name>
            <wls:jndi-name>wm/MyWorkManager</wls:jndi-name>
        </wls:resource-description>
    </wls:weblogic-enterprise-bean>
</wls:weblogic-ejb-jar>But I still get exactly the same error when I try to start my server. The example you referred to kind of cryptically suggests that adding a plan.xml suddenly fixed everything, but what am I missing here that actually hooks the work manager up to JNDI? am I getting these problems because I'm using annotations, or are people not supposed to access work managers in this way?
Thanks,
Edited by: 806682 on 05-Nov-2010 08:57