Unable to find Listener Port MyListener for binding MDB MyMDB in RAD 6, JDK 1,4

[Sam Gehouse]

I created Message Driven Bean using RAD 6 (JDK 1,4, WAS 5.1) wizard. I went to ejb-jar.xml to add listener port as: MyListener and saved ejb-jar.xml. As a result, ibm-ejb-jar.bnd.xmi got created with an entry as:

<?xml version="1.0" encoding="UTF-8"?>
<ejbbnd:EJBJarBinding xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:ejb="ejb.xmi" xmlns:ejbbnd="ejbbnd.xmi" xmi:id="EJBJarBinding_1215548791893">
<ejbJar href="META-INF/ejb-jar.xml#ejb-jar_ID"/>
<ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding" xmi:id="MessageDrivenBeanBinding_1215548791893" listenerInputPortName="My1Listener">
<enterpriseBean xmi:type="ejb:MessageDriven" href="META-INF/ejb-jar.xml#My1"/>
</ejbBindings>
</ejbbnd:EJBJarBinding>

I added this EJB project in RAD 6 Test sever. However, I get exception as Listener port cannot be found.

In WSAD 5, I could specify Listener port name; while creating Message Driven Bean using the wizard. In RAD 6, I do not see name of Listener Port in the wizard any more. I added it using ejb-jar.xml.

However, I get following exception:

Unable to
find Listener Port MyListener for binding MDB MyMDB
[7/8/08 15:27:47:858 EDT] 35421a44 EJBContainerI E WSVR0062E: Unable to
start EJB, My#MyEJB.jar#MyMDB: com.ibm.ejs.jms.listener.MDBException:
Creation of MDB MyMDB unable to find ListenerPort 'MyListener'
at
com.ibm.ejs.jms.listener.MDBListenerManagerImpl.create(MDBListenerManagerImpl.ja
va:314)
at
com.ibm.ejs.container.EJSContainer.loadBeanMetaData(EJSContainer.java:1395)
at
com.ibm.ejs.container.EJSContainer.getHomeWrapperCommon(EJSContainer.java:1012)
at
com.ibm.ejs.container.EJSContainer.getHomeInstance(EJSContainer.java:934)
at com.ibm.ejs.container.EJSContainer.startBean(EJSContainer.java:913)

[Marcelo Sousa Ancelmo]

Hi Sam,

Did you created the Listener Port in WAS?

Looks like there is no listener port created, so you got the exception.

Also, in WAS 6.1 the listener port is deprecated, it is present just for backward compatibility with WAS 5.1 deployments, try to use the Service Integration Bus.

Regards,

[Dinesh Ramakrishnan]

I presume there's a Websphere V5 compatible Listener port available in 6.1. We are trying to do the same (installing an application running in 5.1 and porting it to 6.1), and encountering the same exception.

[Marcelo Sousa Ancelmo]

Sam and Dinesh,

In this link you can find all the information about administering and configuring listener ports in WAS 6.1

Regards,