I had sent this in an email to someone asking for help. I t contains more detail than I had in my original post.
--
We have the follow setup for our environments:
Dev and SystemTest have 2 servers - one is running a WebAS 6.40 instance
and has Oracle installed. The other is a WebAS 6.40 instance with EP
6.0 installed. Any EP application are installed on the EP box
(naturally), and other applications are installed on the WebAS only
boxes.
We have 2 clustered environments - User Test (UTT) and Production
(Prod). Both of these have 2xWebAS boxes in a CI/DI cluster
arrangement, 2xWebAS+EP6 boxes in a CI/DI cluster arrangement, and
2xOracle boxes in a cluster.
All of our servers are running Windows 2003, and the clustering is
Windows clustering. Each cluster has it's own Virtual IP. Standard
stuff, really.
We have written small utility to allow users to publish KM content
easily from the UTT environment into Prod - we don't give our users
direct access to the KM on our production systems . This utility works
very well between Dev and SystemTest, where we did all of our testing.
However, we are having an issue running this between SystemTest and UTT,
and between UTT and Prod.
The error we get occur when we try to get the InitialContext.
Here is the code:
private void createHandle() throws CPUException {
String server;
String port;
try {
server = CPUDao.getInstance().getServer();
port = String.valueOf(CPUDao.getInstance().getPort());
} catch (CPUException e) {
Logger.log(e.getMessage(), e);
throw e;
}
try {
String url = server + ":" + port;
Logger.log("URL is " + url);
Properties properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sap.engine.services.jndi.InitialContextFactoryImpl");
properties.put(Context.PROVIDER_URL, url);
//properties.put(Context.SECURITY_PRINCIPAL, "Administrator");
//properties.put(Context.SECURITY_CREDENTIALS, "password_here");
properties.put("force_remote", "true");
intialcontext = new InitialContext(properties);
object = intialcontext.lookup(CPUConstants.EJB_URL);
if (object==null) {
throw new CPUException ("lookup returned null");
}
CPUKmSessionHome cpuKmSessionHome =
(CPUKmSessionHome)PortableRemoteObject.narrow(object,
CPUKmSessionHome.class);
if (cpuKmSessionHome!=null) {
cpuKmSession = cpuKmSessionHome.create();
} else {
throw new CPUException ("Received a null Home object!!");
}
} catch (NamingException e) {
Logger.log("Naming Exception: " + e.getMessage(), e);
Logger.log("Exception is : " + e.getClass().getName());
Logger.log("Cause is: " + e.getCause());
Logger.log("Explaination is: " + e.getExplanation());
Logger.log("RemainingName is: " + e.getRemainingName());
Logger.log("ResolvedName is: " + e.getResolvedName());
Logger.log("toString() return: " + e.toString());
throw new CPUException(e.getMessage(), e);
} catch (RemoteException e) {
Logger.log("Remote Exception: " + e.getMessage(), e);
throw new CPUException(e.getMessage(), e);
} catch (CreateException e) {
Logger.log("Create Exception: " + e.getMessage(), e);
throw new CPUException(e.getMessage(), e);
} catch (Exception e) {
Logger.log("Other Exception: " + e.getClass().getName() + ": " +
e.getMessage());
StringWriter sw=new StringWriter();
e.printStackTrace(new PrintWriter(sw));
Logger.log("Trace:<BR><pre><code>"+sw.toString()+"</code></pre>");
throw new CPUException(e.getMessage(), e);
}
}
I've a tonne of debug statements in there so that I can see what is
happening (Logger.log() logs to a static StringBuffer variable in,
appending a <BR>\n to each line - I can view this then using a webpage.
When an exception is passed in, it will print some of the stacktrace to
the log too)
It failed on the
intialcontext = new InitialContext(properties);
line.
At the moment it's coming back with a
priority: DEBUG - message: Naming Exception: Exception during
getInitialContext operation. No server is running.
Exception during getInitialContext operation. No server is running.
Or
priority: DEBUG - message: Exception is :
com.sap.engine.services.jndi.persistent.exceptions.NamingException
priority: DEBUG - message: Cause is:
com.sap.engine.services.rmi_p4.exception.P4BaseConnectionException:
Incorrect client ID. The stub is not connected yet.
priority: DEBUG - message: Explaination is: Exception while trying to
get InitialContext.
Strangely, if I take the above code and put it into it's own Class, and
run this from a command line, it will connect...
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.rmi.PortableRemoteObject;
import java.rmi.RemoteException;
public class JNDITest {
static String user=null;
static String pass=null;
public void createHandle() {
String server=" server_ip";
String port="50004";
try {
String url = server + ":" + port;
System.err.println("URL is " + url);
Properties properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sap.engine.services.jndi.InitialContextFactoryImpl");
properties.put(Context.PROVIDER_URL, url);
if (user!=null) {
properties.put(Context.SECURITY_PRINCIPAL, user);
properties.put(Context.SECURITY_CREDENTIALS, pass);
}
properties.put("force_remote", "true");
System.out.println("Properties are: " + properties);
System.out.println("Getting context...");
Context intialcontext = new InitialContext(properties);
System.out.println("Have context: " + intialcontext);
System.out.println("Looking up object:
diageo.com/CPUSystemApp/CPUKmSessionBean");
Object object =
intialcontext.lookup("diageo.com/CPUSystemApp/CPUKmSessionBean");
System.out.println("Have object: " + object);
} catch (NamingException e) {
System.err.println("Naming Exception: " + e.getMessage());
e.printStackTrace();
System.err.println("Exception is : " + e.getClass().getName());
System.err.println("Cause is: " + e.getCause());
System.err.println("Explaination is: " + e.getExplanation());
System.err.println("RemainingName is: " + e.getRemainingName());
System.err.println("ResolvedName is: " + e.getResolvedName());
System.err.println("toString() return: " + e.toString());
} catch (Exception e) {
System.err.println("other Exception: " + e.getMessage());
System.err.println("Exception is" + e.getClass().getName());
e.printStackTrace();
}
}
public static void main(String[] args) {
JNDITest j=new JNDITest();
if (args.length>0) {
user=args[0];
pass="";
}
if (args.length>1) {
pass=args[1];
}
j.createHandle();
}
}
The output from the above is:
URL is server_ip:50004
Properties are: {java.naming.provider.url= server_ip:50004,
java.naming.factory.initial=com.sap.engine.services.jndi.InitialContextF
actoryImpl, force_remote=true}
Getting context...
Have context: javax.naming.InitialContext@c2ff5
Looking up object: diageo.com/CPUSystemApp/CPUKmSessionBean
Have object: 248
where server_ip is the IP address of the CI instance on the WebAS+EP
box on UTT. Because this is occuring between ST/UTT and UTT/Prod, it
would appear that it could be a firewall issue. However, the
stand-alone class above connects which would negate the firewall issue.
Also, I had a firewall guy look at the issue, and he is not seeing
anything that is being blocked.
The connect from ST to UTT is to the CI instance directly. Same with
the connection from UTT to Prod. I have also tried connecting to the
Virtual IP of the cluster on UTT from ST to see if that would help - it
dodn't .
I haven't been able to find anything on the forums about this. Is it a
problem connecting remotely to an EJB in a cluster? Or another issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.