Set SECURITY_PRINCIPAL,SECURITY_CREDENTIALS in sample EJB client to what?

Hi!
I'm getting an:
javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; ...
from a sample client class that JDeveloper generated from an Entity Bean that it generated from a Table.
I haven't successfully been able to the Oracle 9i IAS on a separate machine, so I'm using JDeveloper's embedded OC4J for now.
In the Database Connection is specified the DB user and passwd, in ejb.jar and orion-ejb.jar i created a role "serious-user" and specified that it can access all the Bean's methods.
I'm not sure if the DB access is refused because something is wrong or missing about those role definitions or because I'd need to instanciate some session or the like..
so far, I only have: Entity Bean, sample client generated from it, ejb-jar.xml and orion-ejb-jar.xml .
the generated sample code says this:
               Hashtable env = new Hashtable();
               env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
               env.put(Context.SECURITY_PRINCIPAL, "admin");
               env.put(Context.SECURITY_CREDENTIALS, "welcome");
               env.put(Context.PROVIDER_URL, "ormi://localhost:23895/current-workspace-app");
Is the security principal supposed to be changed to the role I've defined? What about the security credentials?
challenged,
Lukas
Btw: Something might be wrong with my Jdeveloper/OC4J setup ..
In a different project, trying to retrieve the ServletContext from a Servlet's init() method gets me a null pointer exception.

I'm having the exact same error message with my Sample Client. And I get this error even though I have made sure to run the Entity Bean, and the Session Bean. When I run these EJBs, i get no errors and it looks like the embedded OC4J is getting launched.
So there must be something else going on, at least for me. But What??
Also, where do you specify whether you want to Run the client against a standalone OC4J instance or the Embedded OC4J instance?
Thanks and whoever answers my question will receive my undying gratitude as well as a few good karma points.

Similar Messages

How do I generate the sample EJB Client

The online documentation says, by right clicking on EJB in system navigator, I should be able to see the context menu for creating a Sample EJB Client. However, I only see "New Java Client" and that too is disabled. Can somebody tell me how do I generate the Sample EJB Client.
Thanks
vimal

The right-mouse option is on each individual session bean.
"New Sample Java Client..."

How to set SSL from an Webservice EJB client

I want to invoke a web service from a stateless session EJB. How do I
configure Weblogic 9.0/8.1 so that the transport uses SSL? I have a set of
SSL related properties that I want to set e.g. Client Authentication
Enabled, Private Key file, Client Certifiicate file etc.
Note that I am NOT using weblogic native programming (i.e.e jws
files/controls and annotations) to create the web service client. It is a
simple EJB that was developed outiside weblogic and runs in the weblogic
container.
How do I set the SSL related properties in this case?
Thanks for any help.
Shantanu Sen

You configuring both the server and client side? And how exactly is you're client implemented?
A bit difficult but basic way to do this is with SSLSocket and giving that the necessary keystore which holds you're client certificate (key) and the server CA.
Then push you're soap envelope with http-headers up the socket?

Building an EJB Client

I'm completely confused on how to build an EJB client automagically using Ant.
I have a simple EJB, which I compile using the wlwBuild Ant task. If I set the "ejbgen.jar-settings.ejb-client-jar" property in the project's build.properties, the client jar gets built, but it then ends up in the application EAR file. Worse yet, the generated application.xml descriptor includes the client module. Deploying the ear file fails since WebLogic tries to deploy both modules, and it blows up on NamingExceptions.
I've kludged the process by using wlwBuild and then 'fixing' the resulting EAR file, but that's far from ideal. It works for simple projects, but not Integration projects with the auto-generated very ugly EJB names.
I've looked at wlappc, but the documentation is so scarce I can't tell if this is the tool to use, or how to make it work. Trial and error has gotten me nowhere...:(
So the question is: how can I build the EJB client through Ant without having it end up in the application EAR?
thanks
mike

I'm looking for too and there isn't any.
Here is an example. I hope it could be helpful.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<%@ page import="javax.naming.*" %>
<%@ page import="javax.rmi.*" %>
<%@ page import="java.rmi.*" %>
<%@ page import="javax.ejb.*" %>
<%@ page import="modelo.ejb.*" %>
<%@ page
language="java"
contentType="text/html; charset=ISO-8859-1"
pageEncoding="ISO-8859-1"
%>
<%!
Fachada sbFachada = null;
public void jspInit() {
     String sJNDI = "ejb/modelo/ejb/FachadaHome";
     try{
          Context ejbCtx = (Context) new InitialContext();
          System.out.println("Obteniendo la referencia JNDI: " + sJNDI);
          Object oRef = ejbCtx.lookup(sJNDI);
          FachadaHome home = (FachadaHome) PortableRemoteObject.narrow(oRef, FachadaHome.class);
          try {
               sbFachada = home.create();
          } catch (CreateException ce){
               System.out.println("Error en la creaci�n");
          } catch (RemoteException re) {
               System.out.println("Error remoto en creaci�n");
     } catch (NamingException ne){
          System.out.println("NamingException " + ne.toString());
%>
<TITLE>InvocarEJB2.jsp</TITLE>
</HEAD>
<BODY>
<%
     out.println(sbFachada.contador());
%>
</BODY>
</HTML>
Salu2.
V�ctor.

Sample java client not running--showing a strange error-- help urgently

Hi,
I have followed all the steps, given in JDevloper help, to create and deploy an EJB onto a 9ias server and I have been successful in creating the EJB and deploying it from the JDevloper machine to 9ias machine.My JDevloper is on one machine and 9ias is on another. After deploying when I am creating a sample java client, as given in the JDevloper help file, it gives a very strange error
java.lang.NullPointerException
void Samplemypackage1.MySessionEJB1Client.main(java.lang.String[])
Process exited with exit code 0.
I have tried a lot but it's not happening. Is it becuase
1. 9ias and JDevloper should be on the same machine
2. some configurational changes need to be done in the settings
3. jdk1.3.1 is not compatible with JDevloper.
I am enclosing the code snippet for your quick reference.
package Samplemypackage1;
import java.util.Hashtable;
//import javax.rmi.PortableRemoteObject;
import javax.naming.Context;
import javax.naming.InitialContext;
import mypackage1.MySessionEJB1;
import mypackage1.MySessionEJB1Home;
public class MySessionEJB1Client
public static void main(String [] args)
MySessionEJB1Client mySessionEJB1Client = new MySessionEJB1Client();
try
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "admin");
env.put(Context.SECURITY_CREDENTIALS, "admin");
env.put(Context.PROVIDER_URL, "ormi://9ias:23791/MySessionEJB1");
Context ctx = new InitialContext(env);
MySessionEJB1Home mySessionEJB1Home = (MySessionEJB1Home)ctx.lookup("MySessionEJB1");
MySessionEJB1 mySessionEJB1;
// Use one of the create() methods below to create a new instance
mySessionEJB1 = mySessionEJB1Home.create();
// Call any of the Remote methods below to access the EJB
System.out.println(mySessionEJB1.calc("om sri"));
catch(NullPointerException ne)
ne.printStackTrace();
catch(Throwable ex)
ex.printStackTrace();
When I tried to debug the program I found that the line " mySessionEJB1 = mySessionEJB1Home.create()" returns a null. I really fail to understand as to why it is happening.
Please help me.
Thankx

That's strange. home.create() should never return a null.
Do you see any exception trace on the server side?
Do you have the same version of oc4j.jar on client and server machine? Which version of Jdeveloper and 9iAs are you using?
Try copying oc4j.jar from the server machine to client machine and use that to connect to the bean.
HTH
Dhiraj

EJB Client Access From JDeveloper9iR2

I seem to be running into a lot of problems when trying to get a simple EJB client to talk to an EJB on our 9IAS platform. I have developed a simple session bean (just to test) which simply returns a string. When I create the default client code this works fine using the embedded OC4J server in Jdeveloper but I can't run a similar client against 9IAS when I deploy the code. When I go through the client wizard it seems to produce the same code as the standalone EJB OC4J client. I simply changed the name of the server (Context.PROVIDER_URL, "ormi://pe2500/). This is the parameter code I use:
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "admin");
env.put(Context.SECURITY_CREDENTIALS, "welcome");
env.put(Context.PROVIDER_URL, "ormi://pe2500:23891/MyEJBs");
This is the output I receive:
D:\jdeveloper9ir2\jdk\bin\javaw.exe -ojvm -classpath D:\javadev\ejbservlet\ejbservlet\WEB-INF\classes;D:\jdeveloper9ir2\jdev\lib\jdev-rt.jar;D:\jdeveloper9ir2\j2ee\home\lib\ojsp.jar;D:\jdeveloper9ir2\j2ee\home\jsp\lib\taglib\ojsputil.jar;D:\jdeveloper9ir2\j2ee\home\oc4j.jar;D:\jdeveloper9ir2\j2ee\home\lib\servlet.jar;D:\jdeveloper9ir2\jdev\lib\ojc.jar;D:\jdeveloper9ir2\j2ee\home\lib\activation.jar;D:\jdeveloper9ir2\j2ee\home\lib\ejb.jar;D:\jdeveloper9ir2\j2ee\home\lib\jaas.jar;D:\jdeveloper9ir2\j2ee\home\lib\jaxp.jar;D:\jdeveloper9ir2\j2ee\home\lib\jcert.jar;D:\jdeveloper9ir2\j2ee\home\lib\jdbc.jar;D:\jdeveloper9ir2\j2ee\home\lib\jms.jar;D:\jdeveloper9ir2\j2ee\home\lib\jndi.jar;D:\jdeveloper9ir2\j2ee\home\lib\jnet.jar;D:\jdeveloper9ir2\j2ee\home\lib\jsse.jar;D:\jdeveloper9ir2\j2ee\home\lib\jta.jar;D:\jdeveloper9ir2\j2ee\home\lib\mail.jar;D:\jdeveloper9ir2\j2ee\home\oc4j.jar;D:\jdeveloper9ir2\lib\xmlparserv2.jar;D:\jdeveloper9ir2\lib\xmlcomp.jar;D:\jdeveloper9ir2\j2ee\home\oc4j.jar;D:\jdeveloper9ir2\j2ee\home\lib\servlet.jar Samplemypackage6.ctejb1Client3
javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
     java.net.ConnectException: Connection refused: connect
     java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
          RMIContext.java:134
     java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
          InitialContext.java:350
     void Samplemypackage6.ctejb1Client3.main(java.lang.String[])
          ctejb1Client3.java:18
Process exited with exit code 0.
Can anyone tell me if this is the correct communication method for client EJB's talking to the 9IAS server?
Any help really appreciated.
Chris Taylor

hi Chris Taylor, did you find the solution for this error. i too get this error and i am looking for the answer. if you find any answer please share with me too. if i get any answer for this i will reply you too.

How to hide password in EJB client

I have created an EJB client and it's initial context code is as below.
Hashtable env = new Hashtable();
env.put( Context.INITIAL_CONTEXT_FACTORY, "oracle.j2ee.naming.ApplicationClientInitialContextFactory" );
env.put( Context.SECURITY_PRINCIPAL, "scott" );
env.put( Context.SECURITY_CREDENTIALS, "welcome1" );
env.put(Context.PROVIDER_URL, "ormi://132.100.5.248:23791/ejbhr");
The password is shown within the code. Please advise how I can hide this password, thanks.
SK

Hi Mike,
Thanks for your information. From the documentation, password indirection applies to data-sources.xml, ra.xml, rmi.xml, jms.xml. My case is that the password is contained inside a Java program. Would you please provide me an example on how to apply password indirection for EJB client Java program? Much thanks.
SK

Java EJB client "Can't connect to ORB" errors...

I'm writing an application that is a Java EJB client application (no web
stuff at all). Needless to say there are no examples of such an app in
the samples dir, they are all web-based.
My problem is that when I try to run my application (client calls a
stateless session bean on the server and gets a "hello world" string
back) I get a "Could not create the TestService bean:
javax.naming.CommunicationException: Cannot connect to ORB [Root
exception is org.omg.CORBA.COMM_FAILURE: minor code: 1 completed:
Maybe]" error.
This is a very simple test, and I'm getting quite frustrated in trying
to figure out what's actually wrong.
Here's the client code (the bean on the server has been deployed into a
module called achptestEjb, the bean name is TestService)
TestService service = null;
TestServiceHome home=null;
String host = "localhost";
String port = "12345";
try {
Properties env = new Properties();
Context context=null;
String jndiName="ejb/achptestEjb/TestService";
System.out.println("JNDI name is "+jndiName);
env.put
("java.naming.factory.initial","com.sun.jndi.cosnaming.CNCtxFactory");
env.put("java.naming.provider.url", "iiop://"+host+":"+port);
context = new InitialContext(env);
The error comes when the new InitialContext is set with the properties
in the env object.
Any ideas what I'm doing wrong?
It would be a BIG help if iPlanet included one simple pure EJB client
example. There are some of us out here who feel HTML is too limiting
for complicated applications.
Douglas Bullard

I finally found the answer to my problem.... in the Ant script I had
copied from another example, the "-iiop" was lacking in the ejbc
arguments - almost all of the examples assume you'll be calling EJBs
from within the container, instead of a stand-alone client, so they
don't use that flag.
Putting that "-iiop" flag into the ejbc arguments fixed everything.
Thanks, Shivani, for pointing out what is now obvious but was
mysterious.
Douglas Bullard
In article <[email protected]>,
[email protected] says...
I'm writing an application that is a Java EJB client application (no web
stuff at all). Needless to say there are no examples of such an app in
the samples dir, they are all web-based.
My problem is that when I try to run my application (client calls a
stateless session bean on the server and gets a "hello world" string
back) I get a "Could not create the TestService bean:
javax.naming.CommunicationException: Cannot connect to ORB [Root
exception is org.omg.CORBA.COMM_FAILURE: minor code: 1 completed:
Maybe]" error.
This is a very simple test, and I'm getting quite frustrated in trying
to figure out what's actually wrong.
Here's the client code (the bean on the server has been deployed into a
module called achptestEjb, the bean name is TestService)
TestService service = null;
TestServiceHome home=null;
String host = "localhost";
String port = "12345";
try {
Properties env = new Properties();
Context context=null;
String jndiName="ejb/achptestEjb/TestService";
System.out.println("JNDI name is "+jndiName);
env.put
("java.naming.factory.initial","com.sun.jndi.cosnaming.CNCtxFactory");
env.put("java.naming.provider.url", "iiop://"+host+":"+port);
context = new InitialContext(env);
The error comes when the new InitialContext is set with the properties
in the env object.
Any ideas what I'm doing wrong?
It would be a BIG help if iPlanet included one simple pure EJB client
example. There are some of us out here who feel HTML is too limiting
for complicated applications.
Douglas Bullard

How can I run EJB Client in other computer ?

Hello,
I'm trying to run converter examples.
if ejb client pgm resides on a same machine with j2ee server , it works fine.
But when I put client pgm on a different maching
below message show.
No application client descriptors defined for: ConverterClinet
I put ConverterApp.ear, ConverterAppClient.jar and ConverterClient.class on the machine and
set APPCPATH=ConverterAppClient.jar
set VMARGS=-Dorg.omg.CORBA.ORBInitialHost=xxx.xxx.xx.xx
What should I do to run ejb client on different machine?

Hi SangHPark,
I had the same problem but have solved it and it works.
I ran the client remotely from a win98 box.
Keep two things in mind
1> Deploy the applications to an ip address and not to the local host using the deploy too. Use the deploy tool Gui to add a new server and then deploy the application to this ip address.
2> I am running j2ee version 1.3 and jsdk 1.3
Use the following code but instead of using "java:comp/env/ejb/SimpleConverter" use the jndi name of the object: "MyConverter" as specified in the tutorial.
Properties prop = new Properties();
prop.setProperty(Context.INITIAL_CONTEXT_FACTORY,"com.sun.enterprise.naming.SerialInitContextFactory");
prop.setProperty(Context.PROVIDER_URL,"IIOP://xxx.xx.x.xxx:1050");
System.out.println("Attempting to create context...");
Context initial = new InitialContext(prop);
// Instead of this use the below line of code
//Object objref = initial.lookup("java:comp/env/ejb/SimpleConverter");
Object objref = initial.lookup("MyConverter");
// MyConverter is the Jndi name of the ConverterBean as per the tutorial
You need to do the following things.
1> After making changes to the code recompile using Ant and redeploy it.
2> Copy the j2ee.jar, ConverterAppClient.jar and ConverterClient.class file to the machine that u want to run the client from.
3> create a directory called "config" on the remote machine where you copied the files in step two.
4> Copy to this directory the files ejb.properties and security.properties from your j2ee_home\config\ directory.
For example you copied the files in step 2 on the remote machine in the c:\test directory. Create c:\test\config directory and copy the files from step 4 into this directory.
5> Run the following command from the directory where u copied the client files
java -Dorg.omg.CORBA.ORBInitialHost="host name" -classpath .\j2ee.jar;.;.\ConverterAppClient.jar ConverterClient
Monal

Error in running EJB Client on a remote machine

I delploy my beans and can run the EJB Client locally. However when I try to run the Client on another machine, there are errors.
Here is the errors
Syntax error
Out of environment space
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/enterprise/appclient/Main
I have follow the step in the j2ee tutorial and set the env variables according. Here is the bat file I write
set APPCPATH=CBSAppClient.jar
set VMARGS=-Dj2eelogin.name=guest -Dj2eelogin.password=guest123 -Dorg.omg.CORBA.ORBInitialHost=192.168.0.2
runclient -client CBSApp.ear -name CBSClient -textauth
Do anyone facing the same problem with me?
And how can I solve the problems?
This is really URGENT, please help

You are running on Windows 9x or Me, right? The darn OS has 300 or so bytes allocated for environment by default.
Try setting the Initial environment to 4096 in the Properties|Memory tab for the batch file. That will get rid of "Out of environment space". The syntax error is another matter; Windows (except NT and derivatives) shells do not allow '=' in an environment variables value. You cannot overcome that. Some software (Sybase for instance) interprets # as = just because of that. Unfortunately, the JVM doesn't take such an approach.
Better, grab copies of Unix utilities for Windows (www.gnu.org) including the wonderful shell 'bash' and write .sh scripts, which are inherently more powerful.

How to run a sample Jolt client

Can any one explain me how to run a sample jolt client.
Iam trying to run the following jolt client code ToUpper.java at the command prompt but I am getting the following error.I am getting the same error when i run the Jrepository Applet RE.html.
D:\ToUpper>javac ToUpper.java
D:\ToUpper>java ToUpper
bea.jolt.SessionException: Cannot connect to any //localhost:3050.
Reason:NwHdlr: Network Error: chkauth: J_CHECKAUTH FAILED
at bea.jolt.JoltSessionAttributes.getDomainInfoJoltSessionAttributes.java:584)
at bea.jolt.JoltSessionAttributes.checkAuthenticationLevel(JoltSessionAttributes.java:507)
at ToUpper.main(ToUpper.java:20).
I have the tlistener running and provided apppassword and userpassword as my System login password where I have the complete Tuxedo Installation(server and client). Please see the attached sample jolt client program I am trying to run. I am not sure what configuration Settings I need to do.
ToUpper.java
/* Copyright 1996 BEA Systems, Inc. All Rights Reserved */
import bea.jolt.*;
public class ToUpper
public static void main (String[] args)
JoltSession session;
JoltSessionAttributes sattr;
JoltRemoteService toupper;
JoltTransaction trans;
String userName=null;
String userPassword=null;
String appPassword=null;
String userRole="myapp";
String outstr;
          try{
sattr = new JoltSessionAttributes();
sattr.setString(sattr.APPADDRESS, "//GVC3ZA03TESTING:3050");
switch (sattr.checkAuthenticationLevel())
case JoltSessionAttributes.NOAUTH:
break;
case JoltSessionAttributes.APPASSWORD:
appPassword = "123456"//"appPassword";
break;
case JoltSessionAttributes.USRPASSWORD:
userName = "myname";
userPassword = "123456";
appPassword = "123456";
break;
sattr.setInt(sattr.IDLETIMEOUT, 300);
session = new JoltSession(sattr, userName, userRole,
userPassword, appPassword);
toupper = new JoltRemoteService ("TOUPPER", session);
toupper.setString("STRING", "hello world");
toupper.call(null);
outstr = toupper.getStringDef("STRING", null);
if (outstr != null)
System.out.println(outstr);
session.endSession();
System.exit(0);
          }catch(Exception e){
          e.printStackTrace();
} // end main
} // end ToUpper

Hi Todd,
I am not getting the jcheckauthentication error now as i changed the port no. to the port where JSL is running.Now I am getting this error.Also find the ULOG contents pasted below.
D:\bea\tuxedo9.1\samples\jolt\ToUpper>java ToUpper
Authentication Level set To :0
Exception caught error no is:6
bea.jolt.ServiceException: TPENOENT - no entry found
at bea.jolt.JoltRemoteService.decodeCALL(JoltRemoteService.java:460)
at bea.jolt.JoltRemoteService.call(JoltRemoteService.java:345)
at bea.jolt.JoltRemoteService.call(JoltRemoteService.java:267)
at ToUpper.main(ToUpper.java:39)
I have checked the jrepository file and also the Applet window for the service defination(TOUPPER)but still its not recognizing the service.Is there some configuration thing I have missed out before running JOLT client.
ULOG File Contents
132947.GVC3ZA03TESTING!JSH.4000.2464.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
132956.GVC3ZA03TESTING!WSL.432.5308.0: WSNAT_CAT:1196: INFO: Terminating handlers in preparation for shutdown
132956.GVC3ZA03TESTING!WSL.432.5308.0: WSNAT_CAT:1197: INFO: Exiting system
132956.GVC3ZA03TESTING!JSL.2644.2356.0: JOLT_CAT:1506: "INFO: Terminating Jolt administration services in preparation for shutdown"
132956.GVC3ZA03TESTING!JSL.2644.2356.0: JOLT_CAT:1196: "INFO: Terminating handlers in preparation for shutdown"
132956.GVC3ZA03TESTING!JSH.4000.2464.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name 'jolt'; client name 'joltadmin'"
132956.GVC3ZA03TESTING!JSL.2644.2356.0: JOLT_CAT:1197: "INFO: Exiting system"
132956.GVC3ZA03TESTING!DMADM.5844.5348.0: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
132959.GVC3ZA03TESTING!BBL.3216.4372.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
133021.GVC3ZA03TESTING!tmloadcf.6104.3164.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
133021.GVC3ZA03TESTING!tmloadcf.6104.3164.-2: CMDTUX_CAT:872: INFO: TUXCONFIG file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig has been updated
133028.GVC3ZA03TESTING!BBL.6140.5124.0: 02-01-2007: Tuxedo Version 9.1, 32-bit, Patch Level (none)
133028.GVC3ZA03TESTING!BBL.6140.5124.0: LIBTUX_CAT:262: INFO: Standard main starting
133028.GVC3ZA03TESTING!DMADM.4928.1868.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133028.GVC3ZA03TESTING!DMADM.4928.1868.0: LIBTUX_CAT:262: INFO: Standard main starting
133028.GVC3ZA03TESTING!DMADM.4928.1868.0: CMDGW_CAT:3149: INFO: BDMCONFIG environment variable not set. Using $APPDIR/BDMCONFIG
133028.GVC3ZA03TESTING!DMADM.4928.1868.0: CMDGW_CAT:3761: INFO: Using version 2 BDMCONFIG, 3DES is enabled.
133028.GVC3ZA03TESTING!JSL.5608.6088.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133028.GVC3ZA03TESTING!JSL.5608.6088.0: LIBTUX_CAT:262: INFO: Standard main starting
133028.GVC3ZA03TESTING!JSL.5608.6088.0: INFO: JOLT Listener version-BEA Jolt 9.1
133028.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1563: "INFO: Serial Number : <454493271161-2140437240256>, Expiration Date : <2007-02-15>"
133028.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1564: "INFO: Licensee : <BEA Evaluation Customer>"
133029.GVC3ZA03TESTING!JSH.6028.5748.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1030: "INFO: Jolt Handler joining application"
133029.GVC3ZA03TESTING!JSH.6028.5748.-2: INFO: JOLT Handler version-BEA Jolt 9.1
133029.GVC3ZA03TESTING!JREPSVR.3476.4980.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!JREPSVR.3476.4980.0: LIBTUX_CAT:262: INFO: Standard main starting
133029.GVC3ZA03TESTING!JREPSVR.3476.4980.0: Current version: BEA Jolt 9.1
133029.GVC3ZA03TESTING!JREPSVR.3476.4980.0: Repository "D:\bea\tuxedo9.1\udataobj\jolt\repository\jrepository" (16 records) is writable.
133029.GVC3ZA03TESTING!WSL.3292.4892.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!WSL.3292.4892.0: LIBTUX_CAT:262: INFO: Standard main starting
133029.GVC3ZA03TESTING!WSH.2568.3772.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!WSH.2568.3772.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
133029.GVC3ZA03TESTING!WSH.5764.3836.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!WSH.5764.3836.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
133242.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
133300.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
133300.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
133359.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
133456.GVC3ZA03TESTING!JSH.6028.5748.-2: Fldid32(ACCOUNT_ID) failed for INQUIRY: LIBFML_CAT:8: ERROR: Unknown field name. Maybe FIELDTBLS32 is not set properly.
133612.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
143325.GVC3ZA03TESTING!JSH.6028.5748.-2: Fldid(SAMOUNT) failed for DEPOSIT: LIBFML_CAT:11: ERROR: Cannot find or open field table. Maybe FIELDTBLS is not set properly.
144116.GVC3ZA03TESTING!WSL.3292.4892.0: WSNAT_CAT:1196: INFO: Terminating handlers in preparation for shutdown
144116.GVC3ZA03TESTING!WSL.3292.4892.0: WSNAT_CAT:1197: INFO: Exiting system
144116.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1506: "INFO: Terminating Jolt administration services in preparation for shutdown"
144116.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1196: "INFO: Terminating handlers in preparation for shutdown"
144116.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name 'jolt'; client name 'joltadmin'"
144116.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1197: "INFO: Exiting system"
144116.GVC3ZA03TESTING!DMADM.4928.1868.0: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
144119.GVC3ZA03TESTING!BBL.6140.5124.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
144142.GVC3ZA03TESTING!tmloadcf.2668.3316.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
144142.GVC3ZA03TESTING!tmloadcf.2668.3316.-2: CMDTUX_CAT:872: INFO: TUXCONFIG file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig has been updated
144148.GVC3ZA03TESTING!BBL.4144.4376.0: 02-01-2007: Tuxedo Version 9.1, 32-bit, Patch Level (none)
144148.GVC3ZA03TESTING!BBL.4144.4376.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!DMADM.4436.5968.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!DMADM.4436.5968.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!DMADM.4436.5968.0: CMDGW_CAT:3149: INFO: BDMCONFIG environment variable not set. Using $APPDIR/BDMCONFIG
144148.GVC3ZA03TESTING!DMADM.4436.5968.0: CMDGW_CAT:3761: INFO: Using version 2 BDMCONFIG, 3DES is enabled.
144148.GVC3ZA03TESTING!JSL.5072.2444.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!JSL.5072.2444.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!JSL.5072.2444.0: INFO: JOLT Listener version-BEA Jolt 9.1
144148.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1563: "INFO: Serial Number : <454493271161-2140437240256>, Expiration Date : <2007-02-15>"
144148.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1564: "INFO: Licensee : <BEA Evaluation Customer>"
144148.GVC3ZA03TESTING!JSH.5856.5268.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1030: "INFO: Jolt Handler joining application"
144148.GVC3ZA03TESTING!JSH.5856.5268.-2: INFO: JOLT Handler version-BEA Jolt 9.1
144148.GVC3ZA03TESTING!JREPSVR.2952.1248.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!JREPSVR.2952.1248.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!JREPSVR.2952.1248.0: Current version: BEA Jolt 9.1
144148.GVC3ZA03TESTING!JREPSVR.2952.1248.0: Repository "D:\bea\tuxedo9.1\udataobj\jolt\repository\jrepository" (16 records) is writable.
144148.GVC3ZA03TESTING!WSL.3040.5488.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!WSL.3040.5488.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!WSH.5740.2764.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!WSH.5740.2764.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
144148.GVC3ZA03TESTING!WSH.1784.5448.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!WSH.1784.5448.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
144157.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
144207.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
144226.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
144229.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
144518.GVC3ZA03TESTING!WSL.3040.5488.0: WSNAT_CAT:1196: INFO: Terminating handlers in preparation for shutdown
144518.GVC3ZA03TESTING!WSL.3040.5488.0: WSNAT_CAT:1197: INFO: Exiting system
144518.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1506: "INFO: Terminating Jolt administration services in preparation for shutdown"
144518.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1196: "INFO: Terminating handlers in preparation for shutdown"
144518.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name 'jolt'; client name 'joltadmin'"
144518.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1197: "INFO: Exiting system"
144519.GVC3ZA03TESTING!DMADM.4436.5968.0: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
144522.GVC3ZA03TESTING!BBL.4144.4376.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
144537.GVC3ZA03TESTING!tmloadcf.4892.4980.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
144537.GVC3ZA03TESTING!tmloadcf.4892.4980.-2: CMDTUX_CAT:872: INFO: TUXCONFIG file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig has been updated
144543.GVC3ZA03TESTING!BBL.5440.4548.0: 02-01-2007: Tuxedo Version 9.1, 32-bit, Patch Level (none)
144543.GVC3ZA03TESTING!BBL.5440.4548.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!DMADM.1016.6128.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!DMADM.1016.6128.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!DMADM.1016.6128.0: CMDGW_CAT:3149: INFO: BDMCONFIG environment variable not set. Using $APPDIR/BDMCONFIG
144543.GVC3ZA03TESTING!DMADM.1016.6128.0: CMDGW_CAT:3761: INFO: Using version 2 BDMCONFIG, 3DES is enabled.
144543.GVC3ZA03TESTING!JSL.1796.5232.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!JSL.1796.5232.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!JSL.1796.5232.0: INFO: JOLT Listener version-BEA Jolt 9.1
144543.GVC3ZA03TESTING!JSL.1796.5232.0: JOLT_CAT:1563: "INFO: Serial Number : <454493271161-2140437240256>, Expiration Date : <2007-02-15>"
144543.GVC3ZA03TESTING!JSL.1796.5232.0: JOLT_CAT:1564: "INFO: Licensee : <BEA Evaluation Customer>"
144543.GVC3ZA03TESTING!JSH.3164.4076.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!JSH.3164.4076.-2: JOLT_CAT:1030: "INFO: Jolt Handler joining application"
144543.GVC3ZA03TESTING!JSH.3164.4076.-2: INFO: JOLT Handler version-BEA Jolt 9.1
144543.GVC3ZA03TESTING!JREPSVR.860.2916.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!JREPSVR.860.2916.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!JREPSVR.860.2916.0: Current version: BEA Jolt 9.1
144543.GVC3ZA03TESTING!JREPSVR.860.2916.0: Repository "D:\bea\tuxedo9.1\udataobj\jolt\repository\jrepository" (16 records) is writable.
144543.GVC3ZA03TESTING!WSL.2596.4404.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!WSL.2596.4404.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!WSH.3508.5136.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!WSH.3508.5136.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
144543.GVC3ZA03TESTING!WSH.4288.5676.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!WSH.4288.5676.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
144548.GVC3ZA03TESTING!JSH.3164.4076.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
144634.GVC3ZA03TESTING!JSH.3164.4076.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
144734.GVC3ZA03TESTING!JSH.3164.4076.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"

Skipping the RMI if ejb client is in the same box as WLS.

does weblogic skip RMI if the ejb client is on the same machine as WLS?
if it does, is that automatic or do we need to set anything?
thanks,
ali.

If the ejb client is (for example) a servlet hosted by WLS and the ejb is in
the same instance of WLS then it skips the RMI. Otherwise it uses RMI.
Cameron Purdy
http://www.tangosol.com
"Ali Ozgun" <[email protected]> wrote in message
news:[email protected]..
does weblogic skip RMI if the ejb client is on the same machine as WLS?
if it does, is that automatic or do we need to set anything?
thanks,
ali.

I am getting this problem when running ejb client

Hi,
Any one help me , i am getting this error when i run my ejb Client
D:\sample\Client>
java -Djava.naming.factory.initial=com.sun.jndi.cosnamin
g.CNCtxFactory -Djava.naming.provider.url=iiop://localhost:1050 com.net.ejbexamples.slsb.EJBClient
Exception in thread "main" org.omg.CORBA.COMM_FAILURE: minor code: 1398079490
completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnectio
n.java:956)
at com.sun.corba.se.internal.iiop.IIOPConnection.send(IIOPConnection.jav
a:1017)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStre
am.java:71)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequest
Impl.java:82)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.
java:153)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNa
mingClient.java:195)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialRefe
rences(InitialNamingClient.java:260)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_r
eferences(InitialNamingClient.java:183)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.ja
va:1465)
at weblogic.iiop.IORManager.createInitialReference(IORManager.java:113)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContex
t(InitialContextFactoryImpl.java:96)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContex
t(InitialContextFactoryImpl.java:86)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
60)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
at com.net.ejbexamples.slsb.EJBClient.main(EJBClient.java:15)
Thanks

Found in negative cache.... very strange.
RFC found in negative cache
What is the negative cache?

Can an EJB client application access to EJBs on two domains concurrently?

It is well-known that there can be multiple domains in a SUN application server. If two domains are started up, can the same EJB client application call different EJB methods from the two domains? If can, how to implement? Please kindly give a snippet of sample codes.
Another question: can EJBs among multiple domains communicate with each other? If can, tell me how to implement and had better provide some sample codes as well.

I have my client working now!
I was looking around on other forums and found a guy who said that javax.comm has problems with security. here is the address
http://lists.dalsemi.com/maillists/java-powered-ibutton/2002-February/002168.html
He said,
"This is an error generated by the javax.comm packages when initializing
the
serial ports. It's basically a security related bug. Officially, all
packages stored in your lib/ext folder should be considered trusted
code,
running with the same permissions as your trusted main application. But
it
seems that isn't the case with comm.jar.
I've heard that signing the comm.jar file might fix it, but I wasn't
able to
verify that myself (but I didn't test with Netscape's java plugin). I
found
a workaround that should take care of it (as long as your main
application
has "all-permissions"). Try adding this line to the top of your main
method:
System.setSecurityManager(null);
So I did that and it worked except for one thing. at the end of my program the client tells me
The system cannot find the path specified.
Do you think this is a major problem? What is it trying to find??
Michael B

Missing " Create Sample Java Client" from the context menu when debugging

Jdev 11.1.1.3 on Windows 7 x64
I have created an EJB - Session Bean from the ADF components and have put some logic into it with one public method.
I have exposed the method in the local interface.
I start the integrated server in the debug mode
When I right-click there is no option to do the sample client.
Am I missing a plug-in - like JUnit or something?
From the manual:
The integrated Oracle WebLogic Server runs within JDeveloper. You can run and test EJBs quickly and easily using this server, and then deploy your EJBs with no changes to them. You do not need to create a deployment profile to use this server, nor do you have to initialize it.
To run a sample client on the integrated Oracle WebLogic Server: In the Application Navigator, right-click on an EJB and choose Run.
Notice in the Message pane that Oracle WebLogic Server has been launched. Right-click on an EJB and choose Create Sample Java Client from the context menu. The default choice is to create a client for the integrated Oracle WebLogic Server, so click OK.
The client is created and opens in the code editor. If your session bean serves as a facade over JPA entities, code is generated to instantiate the query methods. If you exposed methods on your bean, the generated client contains methods that can be uncommented to call them.
After your EJB has been successfully started from the Application Navigator, right-click on the sample client and choose Run.

Shay,
Pretty much what I did exactly - except - since my apps are all using the local interface - I did not create the remote.
This may be an old habit - but generally it is not a good practice to do both - though this may have changed lately.
I have this app working and the EJBs are executing fine.
I used a testview and drug the method onto it - and was able to debug it that way - but still no create java client in the menu.
Is there any other place to find this other than the context menu? Then I can check to see if it is available.
I am using WLS 10.3 that ships with Jdev 11.1.1.3 (forgot that little bit) without any changes.

Set SECURITY_PRINCIPAL,SECURITY_CREDENTIALS in sample EJB client to what?

Similar Messages

Maybe you are looking for