StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POIntermittent failures accessing clustered remote EJB via Spring
primarykey
Id
10830838
data
AcceptedAnswerId
10850995
AnswerCount
1
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2012-05-31T09:26:23.950
FavoriteCount
1
LastActivityDate
2012-06-01T16:07:57.620
LastEditDate
2012-06-01T16:07:57.620
LastEditorUserId
7512
OwnerUserId
7512
ParentId
0
PostTypeId
1
Score
1
ViewCount
827
LastEditorDisplayName
text
Body
I have a Spring application which uses a remote stateless EJB hosted in WebLogic. <pre><code><jee:remote-slsb id="itemService" jndi-name="org.example.ItemService" business-interface="org.example.ItemService" cache-home="false" lookup-home-on-startup="false" home-interface="org.example.ItemServiceHome" resource-ref="false" refresh-home-on-connect-failure="true"> <jee:environment> java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory java.naming.provider.url=t3://server1:7101,server2:7101 </jee:environment> </jee:remote-slsb> </code></pre> My app gets items from the server thus: <pre><code>ItemEntry[] itemEntries = itemService.listAvailableItems(criteria); for(ItemEntry entry: itemEntries) { Item item = itemService.getItemAccessObject(entry.getKey()); // Do something with item } </code></pre> This works fine most of the time. However, when the item is very new (put in the database in the last couple of seconds), I get intermittent failures when I try to do anything with the Item: <pre><code>java.rmi.NoSuchObjectException: CORBA OBJECT_NOT_EXIST 1330446337 No; nested exception is: org.omg.CORBA.OBJECT_NOT_EXIST: vmcid: OMG minor code: 1 completed: No </code></pre> For new objects, as described, the failures seem to happen approximately 50% of attempts, and within the for() loop there will be a mixture of failures and successes. If I change the t3:// address to contain only one hostname:port, the problem goes away. So, my working theory is that the listAvailableItems() call goes to one server in the cluster -- where the items in question have arrived, and that the failing getItemAccessObject() calls are going to a different server, where the items are still syncing. If I bypass Spring and manage the EJB context myself, I can't reproduce the problem. Questions: <ol> <li>Is my working theory realistic? (note that the server cluster is a black box to me)</li> <li>How does the Spring SimpleRemoteStatelessSessionProxyBean and/or the WebLogic client divide calls between cluster members?</li> <li>Is there a way to make a sequence of calls go to the same cluster member?</li> </ol>
Tags
<spring><ejb><weblogic><cluster-computing>
Title
Intermittent failures accessing clustered remote EJB via Spring
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USslim
UserOwnerUserId
1. USslim
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POIntermittent failures accessing clustered remote EJB via Spring
 UserUserId
 USuser944849
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.