geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "viola.lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GERONIMO-6023) Fail to lookup EJB LoadBeanRemote in EJB Mulicast Cluster
Date Tue, 28 Jun 2011 06:48:17 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056345#comment-13056345
] 

viola.lu commented on GERONIMO-6023:
------------------------------------

By default, multicast is enabled, so other servers started but without loadbean deployment
also join this cluster group, fail over happens on these server, making lookup fail. After
code update @ #1139164, this error will disappear.

> Fail to lookup EJB LoadBeanRemote in EJB Mulicast Cluster
> ---------------------------------------------------------
>
>                 Key: GERONIMO-6023
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6023
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: OpenEJB
>    Affects Versions: 3.0
>         Environment: OS: winxp, win2003, ubuntu, winxp
> jdk: ibm 1.6
>            Reporter: viola.lu
>            Priority: Minor
>             Fix For: 3.0
>
>
> 1. Start geronimo server on win2003, ubuntu, winxp-chinese, and deploy loadbean.jar ejb
module to servers.
> 2.Start geronimo server on winxp2-english, deploy loadbean-war to server
> 3.Access web url on winxp2-english:http://localhost:8080/load/Multicast with test code:
> p.setProperty(Context.PROVIDER_URL,"multicast://239.255.3.2:6142?group=cluster1");
>             Context context3 = new InitialContext(p);
>             loadRemote =(Load) context3.lookup("LoadBeanRemote");
> but got an error:
> 2011-06-23 11:41:41,718 ERROR [[MulticastBean]] Servlet.service() for servlet [MulticastBean]
in context with path [/load] threw exception [javax.naming.NameNotFoundException: /LoadBeanRemote
does not exist in the system.  Check that the app was successfully deployed.] with root cause
> javax.naming.NameNotFoundException: /LoadBeanRemote does not exist in the system.  Check
that the app was successfully deployed.
> 	at org.apache.openejb.client.JNDIContext.lookup(JNDIContext.java:261)
> 	at org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161)
> 	at javax.naming.InitialContext.lookup(InitialContext.java:436)
> 	at org.apache.geronimo.tests.LoadBeanMulticastServlet.doGet(LoadBeanMulticastServlet.java:65)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240)
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
> 	at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:700)
> 	at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:48)
> 	at org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53)
> but this pass with url:failover:ejbd://****:4201,ejbd://***:4201,ejbd://**:4201" or ejbd:***:4201.

> 4.If i shutdown the served server 1, but it will not failover to next server, seems only
the first server is one the list.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message