JNDI / EJB deployment and clustering

Question

I'm aware that replication isn't supported for stateful EJBs. But the
          "serialization of the handle isn't supported" statement has me concerned.
          So I'm looking for a little clarification on this scenario:
          Let's say I've got a stateful session bean, which is accessed from a
          servlet. For performance reasons, you want to find the colocated instance -
          the smart stub should do this, right? To have it colocated in all
          instances, then I need to deploy it into each server of the cluster. This
          essentially bind()/rebind()'s (whichever call the container does during a
          deploy operation) the EJB n times. Does each of those JNDI bind/rebind
          calls "overwrite" the previous one, or does the replicated JNDI tree somehow
          "keep" all the entries?
          What happens if I bind/rebind "non-cluster enabled" objects into the JNDI
          tree in each server to the same name (like a reference data table - doesn't
          really need to be an RMI object, one per server is fine)? Will they get
          "overwritten"? Should I need to take into account the server name when
          binding into the tree, and then also use that for subsequent lookups?
          Thanks for any input!
          --Jason
          

Answer 1

Guys,
Thanks for the information.
The problem was that classpath, some other packages required for the Bean
were not in the weblogic\classes directory.
so that was it.
Thanks
/selvan
Murali Krishna Devarakonda wrote in message
<7qjkr1$7dl$[email protected]>...
Are you using the HOT DEPLOY feature(startweblogic.bat does it)?
Then you could go to the WebLogic Console, select the Bean, and Redploy.
You could also do it from a command line utility "weblogic.deploy".
If you didn't start the server with the hot deploy, you need to restartyour
server after any changes.
You should read the weblogic docs on the Hot Deploy feature. A different
classloader is used for it. Also, the standard weblogic classpath cannot
coexist with it.
Hot Deploy uses: (assuming your weblogic installation is in D:/WebLogic
D:\WebLogic\classes/boot
It will throw an exception if you have D:\weblogic\classes or
D:\WebLogic\lib\weblogicaux.jar in the system classpath. You need to use
the weblogic.classpath instead.
Regards,
Murali Krishna Devarakonda
Tamilselvan Ramasamy <[email protected]> wrote in message
news:7qi0ln$kpc$[email protected]..
Hello,
I have created bunch of EJB Components and deployed for WLS4.0 using the
following way. It works fine under WLS4.0
To compile java code -> javac *.java
Create SER file -> java weblogic.ejb.utils.DDCreator -d .
DeploymentDescriptor.txt
Create JAR file -> jar cmf manifest Bean.jar /directory
EJBC and deployment -> java weblogic.ejbc -d /targetDirectory Bean.jar
and also add an entry in the welogic.properties file
weblogic.ejb.deploy= ...
When I do the samething in the WLS4.5, it doesn't work, first of all,
JNDI
is not finding the home interface. It throws a naming Exception
please give me an idea hw do I deploy my Beans in the WLS4.5 using the
command line option. I don't have Visual Cafe to do that automatically.So
I
have to do that manually.
Thanks
/selvan
Captura Software Inc
[email protected]