This week's book giveaway is in the Server-Side JavaScript and NodeJS forum.
We're giving away four copies of Micro Frontends in Action and have Michael Geers on-line!
See this thread for details.
Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!

Premkumar Rangarajan

Greenhorn
+ Follow
since Jul 29, 2001
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 Premkumar Rangarajan

Hi,
We are getting the can't serialize access exception when trying to create multiple rows in a table, by different threaded clients running simaltaneously contacting our Bean Managed entity bean, each threaded client trying to create one row.
Any ideas???
PPL,
Yesterday i discovered one awful thing about Finders and getters for CMP. We are using Weblogic 4.5.1. I ran a finder on a table which returned 10 rows in an enumeration. There were around 10 fields in the table. When i actually used the getters for getting the field values, I found out to my dismay that each get involved in the bean updating the table for that row ( God knows why this should happen. I was doing a simple select on the table only). In oracle i added a trigger to that table to insert into a log table, everytime an update happens to this table. After find and get, I found out that log table had 318 rows inserted, meaning 318 updates had happened to this table. No wonder entity beans are so slow. Anyone, any idea as to why this should happen? Iam seriously thinking now, to scrap all entity beans and to go for session beans with Connection Con. So all you entity bean buffs out there, Think again.
Hi,
We have a bean in our weblogic server, that contacts a bean in a sybase app server running Financial Fusion to send FIX messages. Now, if we have to restart the Sybase app server, we are forced to restart the Weblogic as well. Seems the weblogic maintains the bean handles of sybase app server, when communication between the two happens. So if sybase app server is restarted and i run my application, the bean in my weblogic fails saying 'CORBA COMM ERROR'. This seems to be bcos the weblogic retains the old handle of the bean in Sybase app server. How do i automatically refresh the handle, without having to restart my weblogic server?
19 years ago
Hi,
We have a bean in our weblogic server, that contacts a bean in a sybase app server running Financial Fusion to send FIX messages. Now, if we have to restart the Sybase app server, we are forced to restart the Weblogic as well. Seems the weblogic maintains the bean handles of sybase app server, when communication between the two happens. So if sybase app server is restarted and i run my application, the bean in my weblogic fails saying 'CORBA COMM ERROR'. This seems to be bcos the weblogic retains the old handle of the bean in Sybase app server. How do i automatically refresh the handle, without having to restart my weblogic server?