Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!

Ashutosh kaur

Greenhorn
+ Follow
since Jan 03, 2003
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Ashutosh kaur

Hi,
We require JMS and EJB transactions together as one automic transaction such that we send a JMS message and try persisting the EJB (or do any database operation etc). If this proceeds without error then commit the JMS transaction Else rollback.

Similarly if the above commit of JMS fails then rolback the EJB transaction.

The session beans have no transaction tag so it will use the default which is supported.

Can we do this by using container Managed transactions OR do we have to do it manually using user transactions?

Please advise,
Regards,
Ashutosh
15 years ago
Hi,
Cybage is one of the best companies as regards to work culture. Cybage has excellent J2EE projects with latest technologies. Cybage has short term onsite appointments. How ever It has also sent 6 guys this year on H1B. Short term assignments are many. Cybage now has 4 US offices.

Hope this helps.
Ashutosh
p.s.: I am associated with Cybage for over 4 years. Went abroad 4 times till now..
15 years ago
Justin/Scott,
Thanks for replying.

Load balanging: My this application is runing at the back ground. Users are not aware of such an application. So the users wont have to wait if the service is too busy.

Fail over: Yes I need to handle this. I am using an RMI object. I have gone through the link sent by Justing already. It says that if we use RMI objects, weblogic handles the fail over:

from the link..
--------------------------------------------------
To make J2EE services available to a client, WebLogic binds an RMI stub for a particular service into its JNDI tree under a particular name. The RMI stub is updated with the location of other instances of the RMI object as the instances are deployed to other servers in the cluster. If a server within the cluster fails, the RMI stubs in the other server's JNDI tree are updated to reflect the server failure.
--------------------------------------------------

I have multiple servers running in a cluster and a single database. There are threads running and I want to process the rows from one table. I have to read the entries in this table and do some java prosessing which includes making JMS calls, using EJB and updating some more tables. My problem is that even after using exclusive locking mechanism through EJB, threads from multiple managed servers are able to read the same record. I want to avoid this. Thats why I need to have only single object through out the application.


by using narrowing now, I do not get class case exception. But fail over is still important to me. The link says that i can bind an rmi object on one of the managed servers and the fail over wil be handled automatically.

Please share your thoughts.
15 years ago
Hi,
My application requires only one object through out several managed servers in a weblogic cluster. WE tried putting RMI object in weblogic JNDI. We are facing several issues.

1) If we select the clusterable option then we find that different instance is created on each managed server.
2) if we do not give the clusterable option then we can retrive the object on theserver which initially bound the object into weblogic jndi. But we get ClassCastException on all the other managed servers.

I have read many threads which also suggest that singleton i J2EE cluster is not possible.
Please suggest/help.

Thanks,
Ashutosh Kaur
15 years ago