Invoking Remote EJB (not as module in Workshop)

Hi,
Help required please...
I am trying to integrate WLS 8.1 with WLS 7.0, i.e. invoking EJB running in 7.0 from 8.1.
While creating a EJB Control in Workshop, its listing only the ejbs deployed as modules. But as my EJB is running in 7.0 I have just imported my Remote and Home (in Libraries). But EJB Control doesn't look to recognise it.
Any solution!!!
Thanks in advance
Kirupa

Then I have to worry about caching home object and also should take care of stale home's in my code (which I am reluctant to do).
I am just wondering, if Workshop EJB Control supports Remote EJB lookup, then why are they not identifying clients with ejb home and remote.
-Kirupa

Similar Messages

AccessControl Exception when invoking remote ejb from portlet class

Hi,
From Portlet class, I am invoking Remote EJB which is deployed in weblogic application server.
After EJB call it not requst Dispathcer not allowed to include the request ..
Exception as follows ..
java.security.AccessControlException: access denied (java.security.SecurityPermission getHttpRequestBase)
X      at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
X      at java.security.AccessController.checkPermission(AccessController.java:427)
X      at org.apache.catalina.connector.HttpRequestFacade.getHttpRequestBase(HttpRequestFacade.java:257)
X      at org.apache.catalina.core.ApplicationDispatcher.getRequestBase(ApplicationDispatcher.java:1115)
X      at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:759)
X      at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:628)
X      at org.apache.catalina.core.ApplicationDispatcher.access$100(ApplicationDispatcher.java:123)
X      at org.apache.catalina.core.ApplicationDispatcher$PrivilegedInclude.run(ApplicationDispatcher.java:154)
X      at java.security.AccessController.doPrivileged(Native Method)
X      at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:528)
X      at com.sun.portal.portlet.impl.RequestDispatcherImpl.include(RequestDispatcherImpl.java:95)
X      at com.gm.gc.sample.SamplePortlet.doView(Unknown Source)
X      at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:235)
X      at javax.portlet.GenericPortlet.render(GenericPortlet.java:163)
X      at com.sun.portal.portletappengine.PortletAppEngineServlet.service(PortletAppEngineServlet.java:271)
X      at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
X      at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:772)
X      at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:628)
X      at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:539)
X      at com.sun.portal.container.portlet.impl.PortletContainer.invokePAE(PortletContainer.java:409)
X      at com.sun.portal.container.portlet.impl.PortletContainer.getMarkup(PortletContainer.java:180)
X      at com.sun.portal.providers.window.WindowProvider.getPortletContent(WindowProvider.java:386)
X      at com.sun.portal.providers.window.WindowProvider.getContentInternal(WindowProvider.java:239)
X      at com.sun.portal.providers.window.WindowProvider.getContent(WindowProvider.java:204)
X      at com.sun.portal.desktop.context.ReusableProviderCaller.run(ReusableProviderCaller.java:160)
Source Code
===========
SamplePortlet Class
protected void doView(RenderRequest request, RenderResponse response)
               throws PortletException, IOException {
          PortletRequestDispatcher prDispatcher = null;
          String helloString=null;
          SamplePortletHandler spHandler=null;
          response.setContentType(request.getResponseContentType());
          try {
               spHandler=new SamplePortletHandler();
               prDispatcher = pContext.getRequestDispatcher("/jsp/SampleView.jsp");
               helloString=spHandler.getHelloString();
               prDispatcher.include(request, response);
          } catch (Exception e) {
               e.printStackTrace();
               request.setAttribute("ERROR_MSG", e.getMessage());
               prDispatcher = pContext.getRequestDispatcher("/jsp/Error.jsp");
               prDispatcher.include(request, response);
Handler Class
is there any solution?
Thanks in Advance ...

Hi,
I didn't configure the JNDI stuff in WLS per se. I created a simple session bean and the meta data in the jar of this determined the JNDI setup.
Once this is deployed on either WLS it can then be seen in Weblogic Console by clicking on View JNDI Tree. The full JNDI name is present and correct on both WLS to which it is deployed.
Does that answer your questions or are you asking how I configured the SOA Suite composite? In which case I selected the EJB in the Partner Link swimlane. Viewed the properties and added
java.naming.provider.url
t3://myremotehost:7001

GlassFish, JAAS Login Module - get remote ejb clien IP address

How to get remote ejb client IP in my custom JAAS login module if I use Glassfish?
Edited by: NoName on Sep 23, 2009 4:06 AM

Hi,
Try configuring wdisp/add_xforwardedfor_header in web dispatcher as described here:
http://help.sap.com/saphelp_nw04/helpdata/en/de/89023c59698908e10000000a11402f/content.htm
And configuring ClientIpHeaderName on the java server as described here:
http://help.sap.com/saphelp_nw04/helpdata/en/52/46f6a089754e3a964a5d932eb9db8b/content.htm
Regards,
Maria

Servlet jndi lookup to remote EJB, servlet and EJB not in the same application

Hi,
I think that the subject explain my problem.
I have Oracle IAS9i 9.0.2.0.0, and JDeveloper 9.0.2.829
I have deployed and EJB in IAS9i and i want to use from the developer machines, which have JDeveloper.
how can i to do remote calls from JDeveloper?.
I have modifed the orion-application.xml, and added remote=true.
I have modifed the rmi.xml and added the hosts where the Jdeveloper placed.
Any ideas?
Thanks and cheers
P.D The app server and jdeveloper are in the same net.
if it is posible replys me to [email protected] too.

Steps to access a remote EJB from within OC4J
++++++++++++++++++++++++++++++++++++++++++++++
1) Deploy EJB application (ApplicationRemote) to remote container (REMOTE)
"java -jar admin.jar -deploy ormi://REMOTE.hostname:REMOTE.port REMOTE.username REMOTE.password -deploy -file ApplicationRemote.ear
-deploymentName ApplicationRemote"
2) Ensure that local application (ApplicationLocal) has ejb-ref tags for remote EJBs accessed (in web.xml or ejb-jar.xml)
3) Deploy to local container (LOCAL) an empty application (ApplicationEmpty) with the same name as the remote application (ApplicationRemote)
"java -jar admin.jar -deploy ormi://LOCAL.hostname:LOCAL.port LOCAL.username LOCAL.password -deploy -file ApplicationEmpty.ear -deploymentName
ApplicationRemote"
5) Deploy local application (ApplicationLocal) to local container (LOCAL)
"java -jar admin.jar -deploy ormi://LOCAL.hostname:LOCAL.port LOCAL.username LOCAL.password -deploy -file ApplicationLocal.ear -deploymentName
ApplicationLocal"
4)Restart local container
ApplicationEmpty should consist of just an application.xml file - no modules. The same file can be deployed with different application names for all the remote
applications that must be accessed.
ApplicationLocal should access the remote EJB by using the following JNDI properties
java.naming.factory.initial = "com.evermind.server.rmi.RMIInitialContextFactory"
java.naming.provider.url = "ormi://REMOTE.hostname:REMOTE.port/ApplicationRemote"
java.naming.security.principal = "REMOTE.username"
java.naming.security.credentials = "REMOTE.password"
regards
Debu Panda

Deployed EJB Not Bound

I deplyed a simple EJB on S17AS. The server.log tells me it is deployed successful.
CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1017ca1
CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@9d5793
LDR5010: All ejb(s) of [simpleEjb] loaded successfully!
The relevant simpleEjb.jar_verified.txt is as follows
     Test Name : tests.ejb.ias.ASEjbJndiName
     Test Assertion :
     Test Description : PASSED [AS-EJB ejb] : jndi-name is simpleHome
However, the server log did not indicate the EJB is bound even if I set the log level to finest.
Therefore when I tried to access it, I get the following error
Exception in thread "main" javax.naming.NameNotFoundException: No object bound f
or java:comp/env/ejb/simpleHome
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.j
ava:116)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at HelloClient.main(HelloClient.java:61)
The client code is as follows
String JNDIName = "java:comp/env/ejb/simpleHome";
myGreeterDBHome = (GreeterDBHome) javax.rmi.PortableRemoteObject.narrow(
               initContext.lookup(JNDIName), GreeterDBHome.class);
The sun-ejb-jar.xml is as follows
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE sun-ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 EJB 2.0//EN' 'http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_0-0.dtd'>
<sun-ejb-jar>
<enterprise-beans>
<name>simpleEjb.jar</name>
<ejb>
<ejb-name>simpleEJB</ejb-name>
<jndi-name>simpleHome</jndi-name>
<is-read-only-bean>false</is-read-only-bean>
               <bean-pool>
                    <steady-pool-size>2</steady-pool-size>
                    <resize-quantity>5</resize-quantity>
                    <max-pool-size>20</max-pool-size>
                    <pool-idle-timeout-in-seconds>3600</pool-idle-timeout-in-seconds>
               </bean-pool>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
I tried to use lookup for both "java:comp/env/ejb/simpleHome" and "java:comp/env/simpleHome". None succeed.
Does anyone know why the ejb is deployed successful but not bound?
Sha

Hi, Parsuram,
I did restart the server and the error is the same.
Here is the sample code. I did not change them. Only the names in deployment descriptors are modified.
Below is the info.
*************************Remote Interface
Copyright � 2002 Sun Microsystems, Inc. All rights reserved.
package samples.jdbc.simple.ejb;
* Remote interface for the GreeterDBEJB. The remote interface defines all possible
* business methods for the bean. These are the methods going to be invoked remotely
* by the servlets, once they have a reference to the remote interface.
* Servlets generally take the help of JNDI to lookup the bean's home interface and
* then use the home interface to obtain references to the bean's remote interface.
public interface GreeterDB extends javax.ejb.EJBObject {
* Returns the greeting String such as "Good morning, John"
     * @return the greeting String
public String getGreeting() throws java.rmi.RemoteException;
*************************Home Interface
Copyright � 2002 Sun Microsystems, Inc. All rights reserved.
package samples.jdbc.simple.ejb;
* Home interface for the GreeterDB EJB. Clients generally use home interface
* to obtain references to the bean's remote interface.
public interface GreeterDBHome extends javax.ejb.EJBHome {
* Gets a reference to the remote interface to the GreeterDBBean.
     * @exception throws CreateException and RemoteException.
public GreeterDB create() throws java.rmi.RemoteException, javax.ejb.CreateException;
*************************Bean Class
Copyright � 2002 Sun Microsystems, Inc. All rights reserved.
package samples.jdbc.simple.ejb;
import java.util.*;
import java.io.*;
* A simple stateless session bean which generates the greeting string for jdbc-simple
* application. This bean implements the business method as declared by the remote interface.
public class GreeterDBBean implements javax.ejb.SessionBean {
private javax.ejb.SessionContext m_ctx = null;
* Sets the session context. Required by EJB spec.
     * @param ctx A SessionContext object.
public void setSessionContext(javax.ejb.SessionContext ctx) {
m_ctx = ctx;
* Creates a bean. Required by EJB spec.
public void ejbCreate() {
System.out.println("ejbCreate() on obj " + this);
* Removes a bean. Required by EJB spec.
public void ejbRemove() {
System.out.println("ejbRemove() on obj " + this);
* Loads the state of the bean from secondary storage. Required by EJB spec.
public void ejbActivate() {
System.out.println("ejbActivate() on obj " + this);
* Keeps the state of the bean to secondary storage. Required by EJB spec.
public void ejbPassivate() {
System.out.println("ejbPassivate() on obj " + this);
* Required by EJB spec.
public void GreeterDBBean() {
* Returns the Greeting String based on the time
* @return the Greeting String.
public String getGreeting() throws java.rmi.RemoteException {
System.out.println("GreeterDB EJB is determining message...");
String message = null;
Calendar calendar = new GregorianCalendar();
int currentHour = calendar.get(Calendar.HOUR_OF_DAY);
if(currentHour < 12) message = "morning";
else {
if( (currentHour >= 12) &&
(calendar.get(Calendar.HOUR_OF_DAY) < 18)) message = "afternoon";
else message = "evening";
System.out.println("- Message determined successfully");
return message;
************************ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<display-name>simple</display-name>
<ejb-name>simpleEJB</ejb-name>
<home>samples.jdbc.simple.ejb.GreeterDBHome</home>
<remote>samples.jdbc.simple.ejb.GreeterDB</remote>
<ejb-class>samples.jdbc.simple.ejb.GreeterDBBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
************************sun-ejb-jar.xml
<sun-ejb-jar>
<enterprise-beans>
<name>simpleEjb.jar</name>
<ejb>
<ejb-name>simpleEJB</ejb-name>
<jndi-name>ejb/simpleHome</jndi-name>
<is-read-only-bean>false</is-read-only-bean>
               <bean-pool>
                    <steady-pool-size>2</steady-pool-size>
                    <resize-quantity>5</resize-quantity>
                    <max-pool-size>20</max-pool-size>
                    <pool-idle-timeout-in-seconds>3600</pool-idle-timeout-in-seconds>
               </bean-pool>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
************************Assemble Info
C:\Sun\AppServer7\samples\jdbc\simple\assemble\jar>jar cvf simpleEjb.jar *
added manifest
ignoring entry META-INF/
adding: META-INF/ejb-jar.xml(in = 710) (out= 350)(deflated 50%)
adding: META-INF/sun-ejb-jar.xml(in = 803) (out= 424)(deflated 47%)
adding: samples/(in = 0) (out= 0)(stored 0%)
adding: samples/jdbc/(in = 0) (out= 0)(stored 0%)
adding: samples/jdbc/simple/(in = 0) (out= 0)(stored 0%)
adding: samples/jdbc/simple/ejb/(in = 0) (out= 0)(stored 0%)
adding: samples/jdbc/simple/ejb/GreeterDB.class(in = 210) (out= 168)(deflated 20%)
adding: samples/jdbc/simple/ejb/GreeterDBBean.class(in = 1441) (out= 734)(deflated 49%)
adding: samples/jdbc/simple/ejb/GreeterDBHome.class(in = 257) (out= 177)(deflated 31%)
C:\Sun\AppServer7\samples\jdbc\simple\assemble\jar>jar tf simpleEJB.jar
META-INF/
META-INF/MANIFEST.MF
META-INF/ejb-jar.xml
META-INF/sun-ejb-jar.xml
samples/
samples/jdbc/
samples/jdbc/simple/
samples/jdbc/simple/ejb/
samples/jdbc/simple/ejb/GreeterDB.class
samples/jdbc/simple/ejb/GreeterDBBean.class
samples/jdbc/simple/ejb/GreeterDBHome.class
******************************** Deployment Info
server1: Applications: EJB Modules: simpleEjb
EJB Module Name: simpleEjb
Location: C:\Sun\AppServer7\domains\domain1\server1\applications\j2ee-modules\simpleEjb_1
******************************** simplEJB.jar_verified.txt
STATIC VERIFICATION RESULTS
     NUMBER OF FAILURES/WARNINGS/ERRORS
     # of Failures : 0
# of Warnings : 1
     # of Errors : 0
     Test Name : tests.ejb.ias.ASEjbJndiName
     Test Assertion :
     Test Description : PASSED [AS-EJB ejb] : jndi-name is ejb/simpleHome
     WARNINGS :
     Test Name : tests.ejb.businessmethod.BusinessMethodException
     Test Assertion : Enterprise bean business method throws RemoteException test
     Test Description : For [ module_simpleEjb#simpleEjb#simpleEJB ]
For EJB Class [ samples.jdbc.simple.ejb.GreeterDBBean ] business method [ getGreeting ]
Error: Compatibility Note: A public business method [ getGreeting ] was found, but EJB 1.0 allowed the business methods to throw the java.rmi.RemoteException to indicate a non-application exception. This practice is deprecated in EJB 1.1 ---an EJB 1.1 compliant enterprise bean should throw the javax.ejb.EJBException or another RuntimeException to indicate non-application exceptions to the Container.
*********************** server log (no binding info)
[05/Jan/2003:17:07:19] FINE ( 1760): [EJBClassPathUtils] EJB Class Path for [simpleEjb] is ...
[C:\Sun\AppServer7\domains\domain1\server1\applications\j2ee-modules\simpleEjb_1, C:\Sun\AppServer7\domains\domain1\server1\generated\ejb\j2ee-modules\simpleEjb]
[05/Jan/2003:17:07:20] FINE ( 1760): Loading StatelessSessionContainer...
[05/Jan/2003:17:07:20] FINE ( 1760): [BaseContainer] Registered EJB [simpleEJB] with MBeanServer under name [ias:instance-name=server1,mclass=stateless-session-bean,name=simpleEJB,root=root,standalone-ejb-module=simpleEjb,type=monitor]
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBBean_RemoteHomeImpl_Tie", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBHome_Stub", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBHome_Stub", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBBean_EJBObjectImpl_Tie", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDB_Stub", codebase = ""
[05/Jan/2003:17:07:20] FINE ( 1760): [Pool-ejb/simpleHome]: Added PoolResizeTimerTask...
[05/Jan/2003:17:07:20] FINE ( 1760): Created container with uinque id: 68275827784351744
[05/Jan/2003:17:07:20] FINE ( 1760): Application deployment successful : com.sun.ejb.containers.StatelessSessionContainer@1083717
[05/Jan/2003:17:07:20] INFO ( 1760): LDR5010: All ejb(s) of [simpleEjb] loaded successfully!
[05/Jan/2003:17:07:22] FINE ( 1760): Started 48 request processing threads
[05/Jan/2003:17:07:22] INFO ( 1760): CORE3274: successful server startup
[05/Jan/2003:17:07:22] FINE ( 1760): The server is now ready to process requests
[05/Jan/2003:17:07:22] INFO ( 1760): CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@10613aa
[05/Jan/2003:17:07:22] INFO ( 1760): CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1f52460
[05/Jan/2003:17:07:22] INFO ( 1760): CORE5053: Application onReady complete.
*********************** Client class
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import java.util.Properties;
import java.util.Hashtable;
import javax.ejb.*;
import java.sql.*;
import javax.sql.*;
import samples.jdbc.simple.ejb.*;
public class HelloClient {
     public static void main(String[] args) throws Exception {
javax.ejb.Handle beanHandle;
GreeterDBHome myGreeterDBHome;
GreeterDB myGreeterDBRemote;
InitialContext initContext = null;
Hashtable env = new java.util.Hashtable(1);
initContext = getContextInfo();
String JNDIName = "java:comp/env/ejb/simpleHome";
System.out.println("- Looking up: " + JNDIName);
myGreeterDBHome = (GreeterDBHome) javax.rmi.PortableRemoteObject.narrow(initContext.lookup(JNDIName), GreeterDBHome.class);
myGreeterDBRemote = myGreeterDBHome.create();
          String theMessage = myGreeterDBRemote.getGreeting();
myGreeterDBRemote.remove();
     public static InitialContext getContextInfo() {
     InitialContext ctx = null;
     String url = "iiop://1st:3700";
     String fac = "com.sun.enterprise.naming.SerialInitContextFactory";
try {
     Properties props = new Properties();
     props.put(Context.INITIAL_CONTEXT_FACTORY, fac);
     props.put(Context.PROVIDER_URL, url);
          ctx = new InitialContext(props);
     catch (NamingException ne){
System.out.println("We were unable to get a connection to " +
" the application server at " + url);
ne.printStackTrace();
return ctx;
*********************** Running Client from command line
C:\Sun\AppServer7\samples\jdbc\simple\assemble\jar>java HelloClient
- Looking up: java:comp/env/ejb/simpleHome
Exception in thread "main" javax.naming.NameNotFoundException: No object bound for java:comp/env/ejb/simpleHome
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:116)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at HelloClient.main(HelloClient.java:34)

Error during JNDI lookup Accessing Remote EJB (access to web service restricted using declarative security model)

Hello everyone,
I developed a Web Service prototype accessing remote EJB using the EJB
control with special syntax in the jndi-name attribute: @jws:ejb
home-jndi-name="t3://10.10.245.70:7131/AccountDelegatorEJB"
Everything works fine, but I get an error when I restrict access to my web
service with a declarative security model by implementing steps provided in
help doc:
- Define the web resource you wish to protect
- Define which security role is required to access the web resource
- Define which users are granted the required security role
- Configure WebLogic Server security for my web service(Compatibility
Security/Users)
I launch the service by entering the address in a web browser. When prompted
to accept the digital certificate, click Yes, when prompted for network
authentication information, enter username and password, navigate to the
Test Form tab of Test View, invoke the method by clicking the button and I
get the following exception:
<error>
<faultcode>JWSError</faultcode>
<faultstring>Error during JNDI lookup from
jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed for
name:t3://10.10.245.70:7131/AccountDelegatorEJB]</faultstring>
<detail>
<jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
lookup from jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed
for name:t3://10.10.245.70:7131/AccountDelegatorEJB] at
weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
8) at
weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
.java:220) at
weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64) </jwErrorDetail>
</detail>
</error>
I have a simple Hello method as well in my WebService (which is also
restricted) and it works fine, but remote EJB access doesn't. I tested my
prototype on Weblogic 7.2 and 8.1 platforms - same result.
Is that a bug or I am missing some additional configuration in order to get
that working. Has anyone seen similar behavior? Is there a known resolution?
Or a suggested way to work around the problem?
Thank you.
Andre

Andre,
It would be best if this issue is handled as an Eval Support case. Please
BEA Customer Support at http://support.beasys.com along with the required
files, and request that an Eval support case be created for this issue.
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Andre Shergin" <[email protected]> wrote in message
news:[email protected]...
Anurag,
I removed "t3", still get an error but a different one (Unable to create
InitialContext:null):
<error>
<faultcode>JWSError</faultcode>
<faultstring>Error during JNDI lookup from
jndi://secuser1:[email protected]:7131/AccountDelegatorEJB[Unable to
create InitialContext:null]</faultstring>
<detail>
<jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
lookup from
jndi://secuser1:[email protected]:7131/AccountDelegatorEJB[Unable to
create InitialContext:null] at
weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
8) at
weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
.java:220) at
weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
ibas.GetVisaHistoryTransactions.getVisaHistoryTxn(GetVisaHistoryTransactions
.jws:67) </jwErrorDetail>
</detail>
</error>
Note: inter-domain communication is configured properly. The Web Service to
remote EJB works fine without a declarative security.
Any other ideas?
Thank you for your help.
Andre
"Anurag" <[email protected]> wrote in message
news:[email protected]...
Andre,
It seems you are using the URL
jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB
whereas you should not be specifying the "t3:" protocol.
The URL should be like
jndi://secuser1:[email protected]:7131/AccountDelegatorEJB
Please do let me know if you see any issues with this.
Note that this will only allow you to access remote EJBs in the same WLS
domain. For accessing EJBs on another domain, you need to configure
inter-domain communication by
following a few simple steps as mentioned at
http://e-docs.bea.com/wls/docs81/ConsoleHelp/jta.html#1106135. This link has
been provided in the EJB Control Workshop documentation.
Regards,
Anurag
"Andre Shergin" <[email protected]> wrote in message
news:[email protected]...
Raj,
I tried that before, it didn't help. I got similar error message:
<error>
<faultcode>JWSError</faultcode>
<faultstring>Error during JNDI lookup from
jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB[Lookup
failed for
name:t3://secuser1:[email protected]:7131/AccountDelegatorEJB]</faultstr
ing>
<detail>
<jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
lookup from
jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB[Lookup
failed for
name:t3://secuser1:[email protected]:7131/AccountDelegatorEJB] at
weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
8) at
weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
.java:220) at
weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64) </jwErrorDetail>
</detail>
</error>
Anything else should I try?
P.S. AccountDelegatorEJB, the remote EJB my Web Service calls is NOTaccess
restricted.
I hope there is a solution.
Thanks,
Andre
"Raj Alagumalai" <[email protected]> wrote in message
news:[email protected]...
Andre,
Can you try using the following url with username and password
jndi://username:password@host:7001/my.resource.jndi.object ?
once you add webapp level security, the authenticated is the user who
invokes the EJB.
http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/controls/ejb/con
CreatingANewEJBControl.html?skipReload=true
has more info on using remote EJB's.
Hope this helps.
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Alla Resnik" <[email protected]> wrote in message
news:[email protected]...
Hello everyone,
I developed a Web Service prototype accessing remote EJB using the EJB
control with special syntax in the jndi-name attribute: @jws:ejb
home-jndi-name="t3://10.10.245.70:7131/AccountDelegatorEJB"
Everything works fine, but I get an error when I restrict access to my
web
service with a declarative security model by implementing steps
provided
in
help doc:
- Define the web resource you wish to protect
- Define which security role is required to access the web resource
- Define which users are granted the required security role
- Configure WebLogic Server security for my web service(Compatibility
Security/Users)
I launch the service by entering the address in a web browser. Whenprompted
to accept the digital certificate, click Yes, when prompted for
network
authentication information, enter username and password, navigate tothe
Test Form tab of Test View, invoke the method by clicking the buttonand
I
get the following exception:
<error>
<faultcode>JWSError</faultcode>
<faultstring>Error during JNDI lookup from
jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed for
name:t3://10.10.245.70:7131/AccountDelegatorEJB]</faultstring>
<detail>
<jwErrorDetail> weblogic.jws.control.ControlException: Error during
JNDI
lookup from jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookupfailed
for name:t3://10.10.245.70:7131/AccountDelegatorEJB] at
weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
8) at
weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
.java:220) at
weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260)at
ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64)</jwErrorDetail>
</detail>
</error>
I have a simple Hello method as well in my WebService (which is also
restricted) and it works fine, but remote EJB access doesn't. I testedmy
prototype on Weblogic 7.2 and 8.1 platforms - same result.
Is that a bug or I am missing some additional configuration in order
to
get
that working. Has anyone seen similar behavior? Is there a knownresolution?
Or a suggested way to work around the problem?
Thank you.
Andre

BC4J :3 tier: Can not open module

Hi
I am using Jdevloepr 10.1.3.
I have created a application module.
When I run the application I get following Exception.
java.io.NotSerializableException: oracle.jdbc.driver.T4CConnection
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1369)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1341)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)
     at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1245)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1069)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1369)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1341)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291)
     at oracle.jbo.common.PiggybackOutput.getPiggybackStream(PiggybackOutput.java:173)
     at oracle.jbo.common.JboServiceMessage.marshal(JboServiceMessage.java:248)
     at oracle.jbo.server.remote.PiggybackManager.marshalServiceMessage(PiggybackManager.java:334)
     at oracle.jbo.server.remote.PiggybackManager.marshalServiceMessage(PiggybackManager.java:316)
     at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.processMessage(AbstractRemoteApplicationModuleImpl.java:2283)
     at oracle.jbo.server.ApplicationModuleImpl.doMessage(ApplicationModuleImpl.java:7509)
     at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.sync(AbstractRemoteApplicationModuleImpl.java:2221)
     at oracle.jbo.server.remote.ejb.ServerApplicationModuleImpl.doMessage(ServerApplicationModuleImpl.java:79)
     at oracle.jbo.server.ejb.SessionBeanImpl.doMessage(SessionBeanImpl.java:474)
     at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
     at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:53)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
     at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_invokeMethod(StatefulSessionEJBObject.java:840)
     at RemoteAMDuties_StatefulSessionBeanWrapper332.doMessage(RemoteAMDuties_StatefulSessionBeanWrapper332.java:89)
     at sun.reflect.GeneratedMethodAccessor54.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Does any one know about the solution for the same.

Is the ftp daemon that you use provided by the Solaris media ? If this is not the case, then would recommend to contact the software maintainer for more help.
And regarding chroot, please check this URL to know what it is : Sandbox (computer security) - Wikipedia, the free encyclopedia
Depending how this environment is configured, the library is maybe not present in this one.

@EJB not working when used in Cactus ServletTestCase

Hi All,
I am running my tests using Cactus ServletTestCase servlet and testing my EJB from there. I deploy my EAR application (my test servlet is in WAR, EJB in EAR modul)
When I run the test, I got NPE as the @EJB is not working and EJB ref is not initialized. Strange thing is, the @EJB is working fine from any other servlet or POJO in WAR.
Test result:
<webresult>
−
<exception classname="java.lang.NullPointerException">
<message>null</message>
−
<stacktrace>
java.lang.NullPointerException
     at test.fenix.legalsubject.TestLegalSubjectController.testConvert(TestLegalSubjectController.java:56)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at junit.framework.TestCase.runTest(TestCase.java:164)
     at junit.framework.TestCase.runBare(TestCase.java:130)
     at org.apache.cactus.internal.AbstractCactusTestCase.runBareServer(AbstractCactusTestCase.java:155)
     at org.apache.cactus.internal.server.AbstractWebTestCaller.doTest(AbstractWebTestCaller.java:120)
     at org.apache.cactus.internal.server.AbstractWebTestController.handleRequest_aroundBody0(AbstractWebTestController.java:94)
     at org.apache.cactus.internal.server.AbstractWebTestController.handleRequest_aroundBody1$advice(AbstractWebTestController.java:218)
     at org.apache.cactus.internal.server.AbstractWebTestController.handleRequest(AbstractWebTestController.java:1)
     at org.apache.cactus.server.ServletTestRedirector.doPost_aroundBody2(ServletTestRedirector.java:102)
     at org.apache.cactus.server.ServletTestRedirector.doPost_aroundBody3$advice(ServletTestRedirector.java:218)
     at org.apache.cactus.server.ServletTestRedirector.doPost(ServletTestRedirector.java:1)
     at org.apache.cactus.server.ServletTestRedirector.doGet_aroundBody0(ServletTestRedirector.java:73)
     at org.apache.cactus.server.ServletTestRedirector.doGet_aroundBody1$advice(ServletTestRedirector.java:218)
     at org.apache.cactus.server.ServletTestRedirector.doGet(ServletTestRedirector.java:1)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:718)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
     at com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:380)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
     at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
</stacktrace>
</exception>
</webresult>
my test class:
public class TestLegalSubjectController extends ServletTestCase {
     * Class under test
     static final Logger log = Logger
               .getLogger(TestLegalSubjectController.class);
     * TODO nemuzu to rozchodit
     @EJB
     public LegalSubjectController legalSubject;
local interface:
@Local
public interface LegalSubjectController extends ControllerFilter {
public LegalSubjectWizardData getByID(Long ID);
public void createLegalSubject(LegalSubjectWizardData legalSubjectWizardData);
public LegalSubject findByName(String name);
EJB implementation
@Stateless
public class LegalSubjectControllerBean implements LegalSubjectController, LegalSubjectControllerRemote {
private static final Logger log = Logger.getLogger(LegalSubjectControllerBean.class);
I am stucked with this one, dont want to use the EJB2 way with JNDI look up. Any suggestions much appreciated!

Was anyone ever able to figure out a solution for this issue? I'm having the exact same problem right now and this is the only reference to it I've been able to find online.
Thanks!
-Blake

Unable to invoke a EJB from a BPEL process

I am unable to invoke a EJB from a BPEL process. Whenever I try to test it from the oracle EM, I get the below exception. I am using WebLogic 10.3.3, SOA suite 11.1.1.3 and JDev 11.1.1.3 .
This is what I see from the EM....
Non Recoverable System Fault :
javaInterface attribute for the binding is missing or the inteface class is not available.
Below is a part of the stack trace from the soa server log…
Caused By: oracle.classloader.util.AnnotatedClassNotFoundException:
Missing class: com.abc.GreetingEJBBean
Dependent class: oracle.integration.platform.blocks.ejb.SDOEjbReferenceD
elegateImpl
Loader: sun.misc.Launcher$AppClassLoader@20929799
Code-Source: /C:/Oracle_latest/Middleware/home_11gR1/Oracle_SOA1/soa
/modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
Configuration: /C:/Oracle_latest/Middleware/home_11gR1/Oracle_SOA1/soa
/modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
Piece of xml from the composite.xml
<reference name="GreetingService"
ui:wsdlLocation="http://123.45.218.140:7001/GreetingEJBBean/GreetingEJBBeanService?wsdl">
<interface.wsdl interface="http://abc.com/#wsdl.interface(GreetingEJBBean)" />
<binding.ejb uri="GreetingEJB-GreetingEJB-GreetingEJB"
javaInterface="com.abc.GreetingEJB"/>
</reference>
Looks like its not able to find the javaInterface mentioned above.
I have a simple EJB with one business method and a very simple BPEL process.
@Stateless(name = "GreetingEJB", mappedName = "GreetingEJB-GreetingEJB-GreetingEJB")
@WebService
public class GreetingEJBBean implements GreetingEJB {
public GreetingEJBBean() {
public String greetUser(String name){
return ("Hello " + name);
Any help would be greatly appreciated.

I haven't tried from a BPEL process, but I have had success (as in Lucas's blogs) of using services and references as EJB Java Interface. This is with EJB java interfaces solely of base types (i.e. String foo(String s)).
At high level here's what I have noted so far:
1. Per Lucas's blog, @javaInterface is not being added to the ejb.binding automatically but it's not clear to me when this is and is not required given that interface.java is specified for the reference or service. Would interface.java and @javaInterface ever be different? I've been adding @javaInterface manually anyways since Lucas is a smart guy and I'd rather avoid errors. :-)
2. Dropping an EJB interface jar in SCA-INF/lib works, but I've had the problem that the JDeveloper SOA Plugin doesn't see those classes until I stop and restart JDeveloper. Until then, I'm confronted with the java->wsdl mapping error. I was sort of primed to figure this one out since I ran into similar issues with SOA SpringBean components.
3. Dropping EJB interface source in SCA-INF/src is more reliable, because then I can build the project (i.e. create SCA-INF/classes) and the JDeveloper SOA Plugin seems to resolve these brand new classes immediately.
4. I've tried to invoke an EJB java-interface reference with a slightly complicated java interface (a class parameter with some fields, one of which is an array of another class). The auto-generated WSDL doesn't look exactly right to me (but I'm new to JAXB). Mediator maps to it just fine and the project compiles and deploys normally but fails at runtime. I have not researched in depth. It's not clear to me from the documentation and release notes whether I should expect for it to work, or whether I should expect to have to create my own JAXB mapping. If the latter, I really need a good example!

Error during lookup of remote ejb CaseService - Oracle ACM 12C Standalone

StandAlone Setup:
CD %ORACLE_HOME%\soa\common\bin
set QS_TEMPLATES=%ORACLE_HOME%\soa\common\templates\wls\oracle.soa_template_12.1.3.jar, %ORACLE_HOME%\osb\common\templates\wls\oracle.osb_template_12.1.3.jar
qs_config.cmd
Then ran config.cmd from WLS and extended BPM domain, then was able to see composer app in deployment.
AdminServer Args:
set USER_MEM_ARGS=-Xms512m -Xmx3096m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=1024m
Error
====
Error during ejb lookup from bpm services client.
Error during lookup of remote ejb CaseService .
Contact Oracle support if exception can not be fixed.
        at oracle.bpm.client.impl.casemgmt.CaseManagementServiceRemoteClient.get
CaseService(CaseManagementServiceRemoteClient.java:86)
        at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.getCaseService(NotificationCallbackUtil.java:158)
        at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.isActivityRegistered(NotificationCallbackUtil.java:167)
        at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.registerEmailActivity(NotificationCallbackUtil.java:83)
        at oracle.bpm.casemgmt.fabric.CaseManagementServiceEngine.stateChanged(C
aseManagementServiceEngine.java:1340)
        at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListene
rs(FabricLifecycle.java:54)
        at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(Fabr
icLifecycle.java:41)
        at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshI
mpl.java:204)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
on(AopUtils.java:318)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
inpoint(ReflectiveMethodInvocation.java:183)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:150)
        at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEven
tAspect.java:71)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:172)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
cAopProxy.java:202)
        at com.sun.proxy.$Proxy324.postDeployInit(Unknown Source)
        at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.r
un(FabricKernelInitializerServlet.java:1008)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run
(WorkManagerExecutor.java:184)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManag
er.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'ejb.bpm.c
ase.CaseService' didn't find subcontext 'bpm'. Resolved 'ejb'; remaining name 'b
pm/case/CaseService'
        at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Basic
NamingNode.java:1180)
        at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.jav
a:265)
        at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.j
ava:187)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:21
0)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:22
4)
        at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.j
ava:253)
        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
        at javax.naming.InitialContext.lookup(InitialContext.java:411)
        at oracle.bpm.client.impl.casemgmt.CaseManagementServiceRemoteClient.get
CaseService(CaseManagementServiceRemoteClient.java:80)
        at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.getCaseService(NotificationCallbackUtil.java:158)
        at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.isActivityRegistered(NotificationCallbackUtil.java:167)
        at oracle.bpm.casemgmt.customactivity.notification.NotificationCallbackU
til.registerEmailActivity(NotificationCallbackUtil.java:83)
        at oracle.bpm.casemgmt.fabric.CaseManagementServiceEngine.stateChanged(C
aseManagementServiceEngine.java:1340)
        at oracle.integration.platform.blocks.mesh.FabricLifecycle.notifyListene
rs(FabricLifecycle.java:54)
        at oracle.integration.platform.blocks.mesh.FabricLifecycle.setState(Fabr
icLifecycle.java:41)
        at oracle.integration.platform.blocks.mesh.MeshImpl.postDeployInit(MeshI
mpl.java:204)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
on(AopUtils.java:318)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
inpoint(ReflectiveMethodInvocation.java:183)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:150)
        at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEven
tAspect.java:71)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:172)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
cAopProxy.java:202)
        at com.sun.proxy.$Proxy324.postDeployInit(Unknown Source)
        at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.r
un(FabricKernelInitializerServlet.java:1008)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run
(WorkManagerExecutor.java:184)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManag
er.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
>
Please help. The problem does not occur with Integrated WLS. I think the config scripts are correctly running from JDev.

Hi,
It's not easy to tell what's wrong with your example.
Maybe you could send me a zip and I'll check when I have some time.
By the way, you're asking a question about the lookup of an EJB3, I wrote an article that covers that topic.
It should give you some interesting input.
http://m-button.blogspot.com/2008/07/reminder-on-how-to-use-ejb3-with.html
Regards.

Stand alone client for remote EJB corba error

Regarding problem below, I've checked System env variables
that weblogic server is using for CORBA classes:
javax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
org.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
org.omg.CORBA.ORBClass weblogic.corba.orb.ORB
javax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
But these are server classes and not found in wlclient.jar and wljmsclient.jar. What classes should be used for client? What needs to be set in order to get successful remote RMI/EJB call to weblogic server?
Original post:
I have a stand alone spring client for simple stateless session EJB deployed on weblogic 9.2. I'm using spring (jdk 1.5) to call this remote EJB and the only way I can succeed is to have full weblogic.jar in my bootstrap classpath. Otherwise I get corba error:
CORBA BAD_PARAM 0 No; nested exception is:
org.omg.CORBA.BAD_PARAM: vmcid: 0x0 minor code: 0 completed: No
Interestingly, within same client I have JMS call to weblogic JMS and that fails if weblogic.jar is in boot classpath. Getting rid of weblogic.jar from boot classpath works if I have wlclient.jar and wljmsclient.jar in regular classpath (as per weblogic docs). I would think that for stand alone client all I would need is to weblogic client jars, why should I need to have full weblogic.jar?
I can't get those work together with same classpath. I wonder if anybody has some pointers and/or advice. I was looking to set system parameters for corba for weblogic client that maybe could help:
org.omg.CORBA.ORBClass
org.omg.CORBA.ORBSingletonClass
javax.rmi.CORBA.UtilClass
javax.rmi.CORBA.StubClass
javax.rmi.CORBA.PortableRemoteObjectClass
But I can't find definitive answer.
Regards,
-pp
Edited by mr.papini at 06/28/2007 9:05 AM

I'm stuck exactly with the same issue while trying to port my application from weblogic to jboss.
I tried to specify different ORB implementations (JacORB, OpenORB) for jvm option org.omg.CORBA.ORBClass, but JBoss couldn't get them instantiated. Native Sun implementation which is used in JBoss by default and can be instantiated, apparently is not fully compatible with weblogic security module.
So did you manage to find out the solution?
Edited by DigitalDude at 04/09/2008 11:47 PM

ClassCastException when I access an EJB from a remote EJB in WL 8.1

I am using WebLogic 8.1 and am trying to lookup the home interface for an EJB (_ejbRemote_)
from another EJB (_ejbCurrent_). They are deployed in seperate EARs. When I bundle
the home and remote interfaces for ejbRemote in the EAR file that ejbCurrent
is deployed in, everything works fine. But I need to be able to configure ejbRemote
at run time and my customers don't want to have to bundle their classes in my
EAR. So I invoke a custom classloader (of type java.net.URLClassLoader) that will
load the home and remote interface classes for ejbRemote from a configurable
location at runtime. This finds the classes no problem, and the InitialContext.lookup()
returns a stub, but I get a 'java.lang.ClassCastException: Cannot narrow remote
object' error when I call PortableRemoteObject.narrow(home, homeClass);
The code looks like:
// Assume EJBHomeStr = "com.foo.TestHome" in this case
// Load the home interface class. This works.
Class homeClass = urlClassLoader.loadClass(EJBHomeStr);
// Lookup the home interface. This works.
Object lookedUpHomeObject = initialContext.lookup(JNDIName);
// This fails.
Object homeObject = PortableRemoteObject.narrow(lookedUpHomeObject, homeClass);
And the weblogic error looks like
... ; nested exception is:
java.lang.ClassCastException: Cannot narrow remote object to com.foo.TestHome
at weblogic.iiop.PortableRemoteObjectDelegateImpl.narrow(PortableRemoteO
bjectDelegateImpl.java:219)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
at ...[the rest is just my application code stack...]
When I log the ClassLoaders for the affected objects, using getClass().getClassLoader(),
I get:
<snippet from log follows>
getClass().getClassLoader(): weblogic.utils.classloaders.GenericClassLoader@667da1
finder:
weblogic.utils.classloaders.MultiClassFinder@db9199 annotation: myEJBApp@
homeClass.getName(): com.foo.TestHome classloader = java.net.URLClassLoader@4f1707
lookedUpHomeObject.getClass().getName(): com.foo.Test_EJB_kx82zy_HomeImpl_810_WLStub
classloader = weblogic.utils.classloaders.GenericClassLoader@667da1
finder: weblogic.utils.classloaders.MultiClassFinder@db9199 annotation: myEJBApp@
<end snippet from log>
So it appears that since the looked up Stub was loaded by the WebLogic classloader
and the actual Home class was loaded by my URLClassLoader, the narrow() can't
reconcile the two. I have tried both rmic and the Weblogic appc command to pre-generate
the stubs, which I put in the same JAR as my home and remote interface classes
and load with my custom classloader. But the standard stub (generated by either
rmic or appc) is named TestHomeStub.class and Weblogic is ignoring those and
making a class with the name Test_EJB_kx82zy_HomeImpl_810_WLStub, as shown above.
I have also tried to put the remote interface classes and stubs in the System
classpath using the -classpath option when I start WebLogic, but same result.
The question is, Is there a way in WebLogic to communicate with a remote EJB in
a seperate EAR without bundling anything about that remote EAR in my EAR? Or is
there something I've missed? I need to keep my application J2EE compliant, meaning
I can't hardcode any AppServer-specific code in my application.
Thanks.

Hi Jon,
Glad to hear that.
Regards,
Slava Imeshev
"Jon Sutula" <[email protected]> wrote in message news:[email protected]...
>
I fixed the problem. It turns out I didn't need to use a custom classloader at
all, I just use Reflection directly on the classes ruturned from my JNDI lookup.
So when I lookup the home class, I don't need to narrow or cast it, I just use
Reflection to invoke the "create" method. Then I use the object that I get from
create and directly invoke whatever method on it I need, again using Reflection.
And that works.
"Slava Imeshev" <[email protected]> wrote:
Hi Jon,
The problem is, this class is not available for the classloader
running your "main code".
You can try to hack the into the thread context class loader:
Thread thread = Thread.currentThread();
ContextClassLoader originalClassLoader = thread.getContextClassLoader();
try {
YourURLClassloader yourClassLoader = new
YourURLClassloader(originalClassLoader);
thread.setContextClassLoader(yourClassLoader );
// your code goes here
} finally {
// Don't forget to restore it !!!
thread.setContextClassLoader(originalClassLoader);
Be very cautious. If you fail to restore the original context class loader,
you will likely have to restart the server.
Hope this helps.
Regards,
Slava Imeshev
"Jon Sutula" <[email protected]> wrote in message news:[email protected]...
I am using WebLogic 8.1 and am trying to lookup the home interfacefor an EJB (_ejbRemote_)
from another EJB (_ejbCurrent_). They are deployed in seperate EARs.When I bundle
the home and remote interfaces for ejbRemote in the EAR file that
ejbCurrent
is deployed in, everything works fine. But I need to be able to configure
ejbRemote
at run time and my customers don't want to have to bundle their classesin my
EAR. So I invoke a custom classloader (of type java.net.URLClassLoader)that will
load the home and remote interface classes for ejbRemote from a configurable
location at runtime. This finds the classes no problem, and the InitialContext.lookup()
returns a stub, but I get a 'java.lang.ClassCastException: Cannot narrowremote
object' error when I call PortableRemoteObject.narrow(home, homeClass);
The code looks like:
// Assume EJBHomeStr = "com.foo.TestHome" in this case
// Load the home interface class. This works.
Class homeClass = urlClassLoader.loadClass(EJBHomeStr);
// Lookup the home interface. This works.
Object lookedUpHomeObject = initialContext.lookup(JNDIName);
// This fails.
Object homeObject = PortableRemoteObject.narrow(lookedUpHomeObject,homeClass);
And the weblogic error looks like
... ; nested exception is:
java.lang.ClassCastException: Cannot narrow remote object tocom.foo.TestHome
at weblogic.iiop.PortableRemoteObjectDelegateImpl.narrow(PortableRemoteO
bjectDelegateImpl.java:219)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
at ...[the rest is just my application code stack...]
When I log the ClassLoaders for the affected objects, using getClass().getClassLoader(),
I get:
<snippet from log follows>
getClass().getClassLoader(): weblogic.utils.classloaders.GenericClassLoader@667da1
finder:
weblogic.utils.classloaders.MultiClassFinder@db9199 annotation: myEJBApp@
homeClass.getName(): com.foo.TestHome classloader = java.net.URLClassLoader@4f1707
lookedUpHomeObject.getClass().getName(): com.foo.Test_EJB_kx82zy_HomeImpl_810_WLStub
classloader = weblogic.utils.classloaders.GenericClassLoader@667da1
finder: weblogic.utils.classloaders.MultiClassFinder@db9199 annotation:myEJBApp@
<end snippet from log>
So it appears that since the looked up Stub was loaded by the WebLogicclassloader
and the actual Home class was loaded by my URLClassLoader, the narrow()can't
reconcile the two. I have tried both rmic and the Weblogic appc commandto pre-generate
the stubs, which I put in the same JAR as my home and remote interfaceclasses
and load with my custom classloader. But the standard stub (generatedby either
rmic or appc) is named TestHomeStub.class and Weblogic is ignoringthose and
making a class with the name Test_EJB_kx82zy_HomeImpl_810_WLStub, asshown above.
I have also tried to put the remote interface classes and stubs inthe System
classpath using the -classpath option when I start WebLogic, but sameresult.
The question is, Is there a way in WebLogic to communicate with a remoteEJB in
a seperate EAR without bundling anything about that remote EAR in myEAR? Or is
there something I've missed? I need to keep my application J2EE compliant,meaning
I can't hardcode any AppServer-specific code in my application.
Thanks.

Error when calling remote EJB from my application

hi
I am getting the following error when i am trying to call a remote EJB from my application.
Can any help me out regarding this issue
javax.naming.ConfigurationException: COS Name Service not registered with ORB under the name 'NameService'. Root exception is org.omg.CORBA.ORBPackage.InvalidName: NameService:org.omg.CORBA.COMM_FAILURE: purge_calls:1500 reason=1 state=5 vmcid: IBM minor code: 306 completed: Maybe
     at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:218)
     at com.ibm.rmi.corba.ORB.resolve_initial_references(ORB.java:4428)
     at com.ibm.rmi.iiop.ORB.resolve_initial_references(ORB.java:654)
     at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:3363)
     at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:387)
     at com.sun.jndi.cosnaming.CNCtx.initUsingIiopUrl(CNCtx.java:330)
     at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:285)
     at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:236)
     at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:84)
     at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:50)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:675)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:257)
     at javax.naming.InitialContext.init(InitialContext.java:233)
     at javax.naming.InitialContext.<init>(InitialContext.java:209)
     at com.ibm._jsp._invoke._jspService(_invoke.java:89)
     at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:91)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:762)
     at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
     at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:204)
     at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3071)
     at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:236)
     at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:210)
     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1958)
     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:109)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:411)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:288)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:207)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:109)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)
Caused by: org.omg.CORBA.COMM_FAILURE: purge_calls:1500 reason=1 state=5 vmcid: IBM minor code: 306 completed: Maybe
     at com.ibm.rmi.iiop.Connection.purge_calls(Connection.java:1499)
     at com.ibm.rmi.iiop.Connection.doReaderWorkOnce(Connection.java:2702)
     at com.ibm.rmi.transport.ReaderThread.run(ReaderPoolImpl.java:137)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:218)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.rmi.corba.ORB.resolve_initial_references(ORB.java:4428)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.rmi.iiop.ORB.resolve_initial_references(ORB.java:654)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:3363)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:387)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.initUsingIiopUrl(CNCtx.java:330)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:285)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:236)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:84)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:50)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:675)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:257)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at javax.naming.InitialContext.init(InitialContext.java:233)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at javax.naming.InitialContext.<init>(InitialContext.java:209)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm._jsp._invoke._jspService(_invoke.java:89)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:91)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:762)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:204)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3071)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:236)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:210)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1958)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:109)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:411)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:288)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:207)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:109)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R Caused by: org.omg.CORBA.COMM_FAILURE: purge_calls:1500 reason=1 state=5 vmcid: IBM minor code: 306 completed: Maybe
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.rmi.iiop.Connection.purge_calls(Connection.java:1499)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.rmi.iiop.Connection.doReaderWorkOnce(Connection.java:2702)
[4/26/07 19:35:11:727 IST] 00000053 SystemErr R      at com.ibm.rmi.transport.ReaderThread.run(ReaderPoolImpl.java:137)
[4/26/07 19:35:11:727 IST] 00000054 SystemErr R javax.naming.ConfigurationException: COS Name Service not registered with ORB under the name 'NameService'. Root exception is org.omg.CORBA.ORBPackage.InvalidName: NameService:org.omg.CORBA.COMM_FAILURE: purge_calls:1500 reason=1 state=5 vmcid: IBM minor code: 306 completed: Maybe
     at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:218)
     at com.ibm.rmi.corba.ORB.resolve_initial_references(ORB.java:4428)
     at com.ibm.rmi.iiop.ORB.resolve_initial_references(ORB.java:654)
     at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:3363)
     at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:387)
     at com.sun.jndi.cosnaming.CNCtx.initUsingIiopUrl(CNCtx.java:330)
     at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:285)
     at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:236)
     at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:84)
     at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:50)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:675)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:257)
     at javax.naming.InitialContext.init(InitialContext.java:233)
     at javax.naming.InitialContext.<init>(InitialContext.java:209)
     at com.ibm._jsp._invoke._jspService(_invoke.java:89)
     at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:91)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:762)
     at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
     at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:204)
     at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3071)
     at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:236)
     at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:210)
     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1958)
     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:109)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:411)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:288)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:207)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:109)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)
Caused by: org.omg.CORBA.COMM_FAILURE: purge_calls:1500 reason=1 state=5 vmcid: IBM minor code: 306 completed: Maybe
     at com.ibm.rmi.iiop.Connection.purge_calls(Connection.java:1499)
     at com.ibm.rmi.iiop.Connection.doReaderWorkOnce(Connection.java:2702)
     at com.ibm.rmi.transport.ReaderThread.run(ReaderPoolImpl.java:137)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:218)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.rmi.corba.ORB.resolve_initial_references(ORB.java:4428)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.rmi.iiop.ORB.resolve_initial_references(ORB.java:654)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:3363)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:387)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.initUsingIiopUrl(CNCtx.java:330)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:285)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:236)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:84)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:50)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:675)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:257)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at javax.naming.InitialContext.init(InitialContext.java:233)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at javax.naming.InitialContext.<init>(InitialContext.java:209)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm._jsp._invoke._jspService(_invoke.java:89)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:91)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:762)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:204)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3071)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:236)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:210)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1958)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:109)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:411)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:288)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:207)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:109)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R Caused by: org.omg.CORBA.COMM_FAILURE: purge_calls:1500 reason=1 state=5 vmcid: IBM minor code: 306 completed: Maybe
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.rmi.iiop.Connection.purge_calls(Connection.java:1499)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.rmi.iiop.Connection.doReaderWorkOnce(Connection.java:2702)
[4/26/07 19:35:11:742 IST] 00000054 SystemErr R      at com.ibm.rmi.transport.ReaderThread.run(ReaderPoolImpl.java:137)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R javax.naming.ConfigurationException: COS Name Service not registered with ORB under the name 'NameService'. Root exception is org.omg.CORBA.ORBPackage.InvalidName: NameService:org.omg.CORBA.COMM_FAILURE: purge_calls:1500 reason=1 state=5 vmcid: IBM minor code: 306 completed: Maybe
     at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:218)
     at com.ibm.rmi.corba.ORB.resolve_initial_references(ORB.java:4428)
     at com.ibm.rmi.iiop.ORB.resolve_initial_references(ORB.java:654)
     at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:3363)
     at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:387)
     at com.sun.jndi.cosnaming.CNCtx.initUsingIiopUrl(CNCtx.java:330)
     at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:285)
     at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:236)
     at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:84)
     at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:50)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:675)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:257)
     at javax.naming.InitialContext.init(InitialContext.java:233)
     at javax.naming.InitialContext.<init>(InitialContext.java:209)
     at com.ibm._jsp._invoke._jspService(_invoke.java:89)
     at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:91)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:762)
     at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
     at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:204)
     at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3071)
     at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:236)
     at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:210)
     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1958)
     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:109)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:411)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:288)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:207)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:109)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)
Caused by: org.omg.CORBA.COMM_FAILURE: purge_calls:1500 reason=1 state=5 vmcid: IBM minor code: 306 completed: Maybe
     at com.ibm.rmi.iiop.Connection.purge_calls(Connection.java:1499)
     at com.ibm.rmi.iiop.Connection.doReaderWorkOnce(Connection.java:2702)
     at com.ibm.rmi.transport.ReaderThread.run(ReaderPoolImpl.java:137)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:218)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.rmi.corba.ORB.resolve_initial_references(ORB.java:4428)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.rmi.iiop.ORB.resolve_initial_references(ORB.java:654)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:3363)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:387)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.initUsingIiopUrl(CNCtx.java:330)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:285)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:236)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:84)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:50)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:675)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:257)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at javax.naming.InitialContext.init(InitialContext.java:233)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at javax.naming.InitialContext.<init>(InitialContext.java:209)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm._jsp._invoke._jspService(_invoke.java:89)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:91)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:762)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:204)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3071)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:236)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:210)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1958)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:109)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:411)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:288)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:207)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:109)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R Caused by: org.omg.CORBA.COMM_FAILURE: purge_calls:1500 reason=1 state=5 vmcid: IBM minor code: 306 completed: Maybe
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.rmi.iiop.Connection.purge_calls(Connection.java:1499)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.rmi.iiop.Connection.doReaderWorkOnce(Connection.java:2702)
[4/26/07 19:37:22:758 IST] 00000052 SystemErr R      at com.ibm.rmi.transport.ReaderThread.run(ReaderPoolImpl.java:137)
[4/26/07 19:37:36:117 IST] 00000056 SystemErr R javax.naming.ConfigurationException: COS Name Service not registered with ORB under the name 'NameService'. Root exception is org.omg.CORBA.ORBPackage.InvalidName: NameService:org.omg.CORBA.COMM_FAILURE: purge_calls:1500 reason=1 state=5 vmcid: IBM minor code: 306 completed: Maybe
     at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:218)
     at com.ibm.rmi.corba.ORB.resolve_initial_references(ORB.java:4428)
     at com.ibm.rmi.iiop.ORB.resolve_initial_references(ORB.java:654)
     at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:3363)
     at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:387)
     at com.sun.jndi.cosnaming.CNCtx.initUsingIiopUrl(CNCtx.java:330)
     at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:285)
     at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:236)
     at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:84)
     at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:50)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:675)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:257)
     at javax.naming.InitialContext.init(InitialContext.java:233)
     at javax.naming.InitialContext.<init>(InitialContext.java:209)
     at com.ibm._jsp._invoke._jspService(_invoke.java:89)
     at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:91)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:762)
     at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
     at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:204)
     at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3071)
     at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:236)
     at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:210)
     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1958)
     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:109)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:411)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:288)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:207)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:109)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952)
     at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039)
     at com.ibm.ws.util.Th

The procedure apex_cdc.enable_table_capture i created myself with no authid mentioned explicitly, so it uses definer rights, by default.
BUt this procedure is simply a wrapper for sys.dbms_cdc_publish.create_change_table.
When I look on the security model for this sys.dbms_cdc_publish, i see it runs under invoker rights. (http://www.psoug.org/reference/dbms_cdc_publish.html).
The code is like this:
CREATE OR REPLACE PROCEDURE enable_table_capture
          i_owner               IN VARCHAR2,
          i_change_table_name     IN VARCHAR2,
          i_change_set_name     IN VARCHAR2,
          i_change_source          IN VARCHAR2,
          i_source_schema          IN VARCHAR2,
          i_source_table          IN VARCHAR2,
          i_column_type_list     IN VARCHAR2
     IS
     BEGIN
          EXECUTE IMMEDIATE 'alter session set REMOTE_DEPENDENCIES_MODE=SIGNATURE';
          EXECUTE IMMEDIATE 'begin add_log@orcl01(i_tableName => ''G''); end;';
sys.DBMS_CDC_PUBLISH.CREATE_CHANGE_TABLE(
owner => i_owner,
change_table_name => i_change_table_name,
change_set_name => i_change_set_name,
source_schema => i_source_schema,
source_table => i_source_table,
column_type_list => i_column_type_list,
capture_values => 'both',
rs_id => 'y',
row_id => 'n',
user_id => 'n',
timestamp => 'y',
object_id => 'n',
source_colmap => 'n',
target_colmap => 'y',
options_string => NULL);
END enable_table_capture;

Why can't I invoke a ejb in Tomcat?

Hi everyone:
I invoke a ejb in Tomcat(the ejb is in the weblogic in the same computer with tomcat).The jsp code is:
/////////////////first method//////////////////////
Context ctx=new InitialContext();
Object obj=ctx.lookup("ejb/Hello");
Hellohome home=(Hellohome)PortableRemoteObject.narrow(obj,Hellohome.class);
Hello hello=home.create();
out.println(hello.getHello());
///////////////second method//////////////////
Hashtable ht=new Hashtable();
Context ctx=null;
ht.put(ctx.PROVIDER_URL, "t3://127.0.0.1:7001" ); // t3://127.0.0.1:7001
ht.put(ctx.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
ctx = new InitialContext();
Hellohome home= (Hellohome) javax.rmi.PortableRemoteObject.narrow (ctx.lookup ("HelloEJB"),Hellohome.class);
Hello hello=home.create();
out.println(hello.getHello());
Is there any different?If I want to invoke the EJB which is in the weblogic.The Tomcat says:
Name HelloEJB is not bound in this Context
But I bound it in the weblogic and I add the "
<ejb-ref>
<ejb-ref-name>HelloEJB</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>lyoejb.Hellohome</home>
<remote>lyoejb.Hello</remote>
<ejb-link>Hello.jar#HelloEJB</ejb-link>
</ejb-ref>"
in the ejb-jar.xml. And I copy the j2ee.jar,wlclient.jar,Hello.jar to Tomcat/....web-inf/lib
How to setting the web.xml in the Tomcat?

Hi duffymo:
I install weblogic in windowsXP and weblogic run property in it.Any wrong?I install JVM in IE6 so the IE can display Applet.
I can invoke the EJB in Tomcat.Let me say it carefully.
The weblogic's port is 7001 and the Tomcat's port is 8080.I deploy a EJB in weblogic and I can see the JNDI name in weblogic console(The JNDI name is HelloEJB). I test the EJB in Tomcat.The dir is C:\tomcat\webapps\ROOT\ejb\invokeEJB.jsp and I write the code:
///////////////////////////invokeEJB.jsp///////////////////////////////////////
Hashtable ht=new Hashtable();
Context ctx=null;
ht.put(ctx.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
ht.put(ctx.PROVIDER_URL, "t3://127.0.0.1:7001" );
ctx = new InitialContext(ht);
Hellohome home= (Hellohome)ctx.lookup ("ejb.HelloEJB");
Hello hello=home.create();
out.println(hello.getHello());
/////////////////////////End code////////////////////////////////
I test it using the URL:"http://localhost:8080/ejb/invokeEJB.jsp"
It can display the content of the EJB property.I means that the Tomcat can invoke EJB.I copy the "j2ee.jar , wlclient.jar , HelloEJB.jar(My EJB Home and Remote interface)" to "Tomcat/.../share/lib" directory.
I hope you will reply if you have any advice. :)

EJB not getting bound to JNDI name using Sun App Server upon deployment

Hello,
I've created a very simple "HelloWorld" EJB (2.1-style) and have successfully deployed it to my local application server (Sun Java System App Server Platform Edition 9.0). I now want to invoke the EJB (I have single stateless session bean that returns a string) using a simple remote client app (the client app is executing outside of the app server within its own JVM).
From my client app I am able to create the InitialContext object, but I get error when trying to lookup my EJB's home object. My client looks as follows:
               jndiProperties = new Properties();
               jndiProperties.put("java.naming.factory.initial",
                    "com.sun.jndi.cosnaming.CNCtxFactory");
               jndiProperties.put("java.naming.provider.url",
                    "iiop://localhost:3700"); // ORB listener is listening on port 3700...
               context = new InitialContext(jndiProperties);
               home = context.lookup("ejb/HelloWorldEJB"); // this line throws an exception (line 54)
               ...The exception I receive is:
               [java] 234 ERROR [main] net.blueslate.sample.ejb.helloworld.HelloWorldClient     - javax.namin
g.NameNotFoundException [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.
org/CosNaming/NamingContext/NotFound:1.0]
     [java]     at com.sun.jndi.cosnaming.ExceptionMapper.mapException(ExceptionMapper.java:44)
     [java]     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:453)
     [java]     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:492)
     [java]     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:470)
     [java]     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     [java]     at net.blueslate.sample.ejb.helloworld.HelloWorldClient.main(HelloWorldClient.java:5
4)
     [java] Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/Naming
Context/NotFound:1.0
     [java]     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:72
     [java]     at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:406)
     [java]     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:440)
     [java]     ... 4 moreHere is my ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar
     xmlns="http://java.sun.com/xml/ns/j2ee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
     version="2.1">
     <enterprise-beans>
          <session>
               <ejb-name>HelloWorldEJB</ejb-name>
               <home>net.blueslate.sample.ejb.helloworld.HelloWorldRemoteHome</home>
               <remote>net.blueslate.sample.ejb.helloworld.HelloWorldRemote</remote>
               <local-home>net.blueslate.sample.ejb.helloworld.HelloWorldLocalHome</local-home>
               <local>net.blueslate.sample.ejb.helloworld.HelloWorldLocal</local>
               <ejb-class>net.blueslate.sample.ejb.helloworld.impl.HelloWorldImpl</ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Container</transaction-type>
          </session>
     </enterprise-beans>
</ejb-jar>Here is my sun-ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 EJB 3.0//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_3_0-0.dtd">
<sun-ejb-jar>
     <enterprise-beans>
          <ejb>
               <ejb-name>HelloWorldEJB</ejb-name>
               <jndi-name>HelloWorldEJB</jndi-name>
          </ejb>
     </enterprise-beans>
</sun-ejb-jar>I believe the root cause is that my EJB is not bound to a name within the app server. If I browse the "JNDI tree" from the app server admin console, I can see there is a root element "ejb," but there is nothing underneath. I guess I just expected to find the name of my EJB, "HelloWorldEJB." I swear I could have read somewhere in the documentation for the app server that when you deploy an EJB, the name of the EJB as specified by the "<ejb-name>" element of the ejb-jar.xml deployment descriptor gets automatically bound within the naming server to its home object.
At this point I would appreciate any insight anyone might have regarding this problem. I suspect there is something extra I need to do when deploying my EJB so that its name gets binded to its home object; I just don't have a clue at this point what that is.
I should also mention that I have played with the parameter passed to 'context.lookup()' - I tried passing: "ejb/HelloWorldEJB", "HelloWorldEJB", etc - nothing seems to work. FWIW, if I just pass in "ejb", I don't receive an exception (I was glad to see this work since the JNDI tree-view from the app server admin console shows "ejb" as one of the root-elements within the naming-tree - this indicated to me I was on the right track in my diagnosis of the problem; i.e., it's probably not a connectivity or protocol issue)
Thank you very much for your time and help.

Nevermind folks - I got it to work. All my configuration was correct; I had other issues with the ejb-jar file that the verifier informed me of (my previous deployments were with the verifier turned-off).

Invoking Remote EJB (not as module in Workshop)

Similar Messages

Maybe you are looking for