vintu79

hi ,
I am using 3 tier architecture where my servlets and htmls are placed in the iplanet webserver4.1 and my EJB in
are in weblogic server 4.5.1 and the Weblogic server uses oci driver to connect to oracle 8.1.6 .
when I am trying to access the EJB which is deployed in weblogic4.5.1 from servlets which are on iplanet webserver 4.1
.I am facing a problem where the servlet in iplanet is not able able to lookup the bean which are deployed on weblogic server using their JNDI lookup name .I am using t3 connectivity to comunicate with the EJB from the servlets.My request hangs for a long time and then displays a insecure item dialog box in the browser.when i checked up the weblogic logs i found no exception or errors while the iplanet log showed me this error [Root exception is java.net.ConnectException: Connection refused]javax.naming.CommunicationException
.The servlet is unable to lookup the bean and I found the connectivity between the iplanet webserver machine and the weblogic server machine is lost and i was not able to invoke a telnet session from iplanet webserver machine to weblogic server machine it is giving connection refused.however if i shut and start iplanet webserver the connectivity is restablished and i am able to invoked the bean from the servlets.This problem is happening once in a while but still i am not able to find a permanent solution for it can anybody give the reason why this is happening the only solution that i have now is to restart iplanet webserver.
I suspect it is due to ports getting locked any one help me
please
thanks for your ideas in advance
vinodh

hi ,
I am using 3 tier architecture where my servlets and htmls are placed in the iplanet webserver4.1 and my EJB in
are in weblogic server 4.5.1 and the Weblogic server uses oci driver to connect to oracle 8.1.6 .
when I am trying to access the EJB which is deployed in weblogic4.5.1 from servlets which are on iplanet webserver 4.1
.I am facing a problem , the servlet in iplanet is not able able to lookup the bean which are deployed on weblogic server using their JNDI lookup name .I am using t3 connectivity to comunicate with the EJB from the servlets.My request hangs for a long time and then displays a insecure item dialog box in the browser.when i checked up the weblogic logs i found no exception or errors while the iplanet log showed me this error [Root exception is java.net.ConnectException: Connection refused]javax.naming.CommunicationException
.The servlet is unable to lookup the bean and I found the connectivity between the iplanet webserver machine and the weblogic server machine is lost and i was not able to invoke a telnet session from iplanet webserver machine to weblogic server machine it is giving connection refused.however if i shut and start iplanet webserver the connectivity is restablished and i am able to invoked the bean from the servlets.This problem is happening once in a while but still i am not able to find a permanent solution for it can anybody give the reason why this is happening the only solution that i have now is to restart iplanet webserver.

thanks for your ideas in advance
vinodh

[This message has been edited by vintu79 (edited October 30, 2001).]

hi,
muthu i think u a bit confused by looking into RMI and EJB
on RMI our implemetation class as to implement the remote interface that we are using.in the case of EJB we are not doing so because the Implementation class are written are by the container automatically. ie during the time of deployment the container will generate you the implementaion class you can open the implementation class code and see you will find your remote interface implemented there.In weblogic during deployment you will get bean class with Impl you can check that for clarifications.while deploying EJB in weblogic you select keep code generated option this will give you the java file for the class that are created.

Originally posted by muthukumaran mohan:
Dear All,
I have a simple doubt. Why we implement session bean or entity bean in Enterprice bean class. Actually we have to implement remote interface know, so that the method present in remote interface will be given definition. please clear my doubt.
with regards
thanx in advance
muthukumaran

hi ,
I am trying to access the EJB which is deployed in weblogic4.5.1 using servlets which are on iplanet webserver 4.1
.I am facing a problem where the servlet in iplanet is not able to communicate with the EJB in weblogic.I am using t3 connectivity to comunicate with the EJB from the servlets.My request hangs for a long time and then displays a insecure item dialog box in the browser.when i checked up the iplanet and weblogic logs i found no exception or errors but the connectivity with the iplanet and the weblogic is lost and i was not able to invoke a telnet session from iplanet webserver machine to weblogic machine it is giving connection refused.however if i shut and start iplanet the connectivity is restablished and i am able to invoked the bean from the servlets.This problem is happening once in a while
but still i am not able to find a permanent solution for it
or the reason why this is happening the only solution that i have now is restart of iplanet
can anyone through a light into this issue

hi ,
I am trying to access the EJB which is deployed in weblogic4.5.1 using servlets which are on iplanet webserver 4.1
.I am facing a problem where the servlet in iplanet is not able to communicate with the EJB in weblogic.I am using t3 connectivity to comunicate with the EJB from the servlets.My request hangs for a long time and then displays a insecure item dialog box in the browser.when i checked up the iplanet and weblogic logs i found no exception or errors but the connectivity with the iplanet and the weblogic is lost and i was not able to invoke a telnet session from iplanet webserver machine to weblogic machine it is giving connection refused.however if i shut and start iplanet the connectivity is restablished and i am able to invoked the bean from the servlets.This problem is happening once in a while
but still i am not able to find a permanent solution for it
or the reason why this is happening the only solution that i have now is restart of iplanet
can anyone through a light into this issue