RA and EJB Requestor Errors

The following table shows possible errors that may be encountered when running AMNU sample WARs.

Exception/Error message Possible solution
When accessing the AmnuRaSample.WAR
...\__index.java:19: package com.attachmate.cicsbridge.j2ee.outputs does not exist
probably occurred due to an error in /index.jsp line 5:
<%@page import="com.attachmate.cicsbridge.j2ee.outputs.*" %>
...\__index.java:20 package com.attachmate.cicsbridge.j2ee.resource.cci does not exist
probably occurred due to an error in /index.jsp line 6:
<%@page import="com.attachmate.cicsbridge.j2ee.resource.cci.IBridgeAPI" %>
...
The BridgeAPI-ra-client has not been added to the application servers class path.
When accessing the AmnuEjbSample.WAR
...\__index.java:19: package com.attachmate.cicsbridge.j2ee.ejb.stateful does not exist
probably occurred due to an error in /index.jsp line 5:
<%@page import="com.attachmate.cicsbridge.j2ee.ejb.stateful.BridgeAPI_EJB" %>
...\__index.java:20: package com.attachmate.cicsbridge.j2ee.ejb.stateful does not exist
probably occurred due to an error in /index.jsp line 6:
<%@page import="com.attachmate.cicsbridge.j2ee.ejb.stateful.BridgeAPI_EJBHome" %>
...\__index.java:21: package com.attachmate.cicsbridge.j2ee.outputs does not exist
probably occurred due to an error in /index.jsp line 7:
<%@page import="com.attachmate.cicsbridge.j2ee.outputs.*" %>
...
The EJB Client JAR has not been packaged inside the AmnuEjbSample.WAR file.
When clicking connectBridge in AmnuRaSample.WAR
javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'eis.BridgeAPI' didn't find subcontext 'eis' Resolved ; remaining name 'eis/BridgeAPI']; Link Remaining Name: 'eis/BridgeAPI' at ... Caused by: javax.naming.NameNotFoundException: While trying to lookup 'eis.BridgeAPI' didn't find subcontext 'eis' Resolved ; remaining name 'eis/BridgeAPI' at ... The BridgeAPI.ear has not been deployed or has been undeployed, the JNDI name of the resource adapter has been changed, or the resource reference mapping has not been setup up correctly.
When clicking connectBridge in AmnuEjbSample.WAR
javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'ejb.BridgeAPI' Resolved ejb; remaining name 'BridgeAPI']; Link Remaining Name: 'ejb/BridgeAPI' at ... Caused by: javax.naming.NameNotFoundException: Unable to resolve 'ejb.BridgeAPI' Resolved ejb; remaining name 'BridgeAPI' at ... The BridgeAPI.ear has not been deployed or has been undeployed, the JNDI name of the stateful session EJB has been changed, or the stateful session EJB mapping has not been setup up correctly.
Related Topics
Bullet RA and EJB Requestors
Bullet Packaging Enterprise Applications
Bullet J2EE Sample Code: Accessing the Stateful Session EJB in a Web Application
Bullet J2EE Sample Code: Accessing the Resource Adapter from a Web Application
  Attachmate