ankush purwar

The other causes may your cluser configuration or network configuration.
Try to check it over there ?

Creattion and destroy of servlets absolutely depends on the web-server. You may not control this behaviour. So in my opinion you shouldn't write such code that depends on web server mechanism.

Try to use IP Address rather than name.

Try to check your URL

If it's really an error because of name .
So simply change the name

Try to check your application.xml in the EAR.
and see the resered ejb modules and web modules are properly placed into good hiererchy.

You can't catch Transactiotimeoutexception in weblogic.
It's better for you to catch Remote Exception on client side not in sesion beans .

Look at the JVM option
Xmx

Yes ,it should be that Server X and server Y will coordinate same transactions. But at least vendor must provide distributed transaction .

I am not sure but i think you copy your class files into your exploded directory. so weblogic automatically take it. There are some options for it in weblogic .
I refer you to see weblogic hot deployment

For Deploying the application don't need to restart server.

It's good for you to take a learning on weblogic rather than weblogic interview questions

Try to use weblogic.Deployer class for deploying,undeploying jars.

Whe user login in the system you should log a message for the login user
and when user logout from the system, then again you should the log the message for logout user.

Now you can easily track the login users in the system.

Why you want to access Config.xml ??