Win a copy of Securing DevOps this week in the Security forum!

Vivek Punekar

Greenhorn
+ Follow
since Aug 25, 2009
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 Vivek Punekar

Hi All,

Interesting and very relevant thread for the issue I am looking into.
In my case - there are two threads which are hogging CPU - The VM Thread and ConcurrentMarkSweep thread.
I can understand that ConcurrentMarkSweep thread is busy as less space is remaining in tenured gen. But, Jayesh Lalwani has commented that VM thread does GC.
I don't quite agree as in my case the GC thread is clearly labeled with name ConcurrentMarkSweep.

Now the query is - what could this VM thread be doing and how to find it?
5 years ago
Hello,

We are using java 1.6 on Linux CentOS 64 bit for JBOSS application.

Which one is recommended UseParNewGC or UseParallelGC? What is the criteria to decide?

We have alloted 1.8GB heap on 6 GB RAM.
JVM is 32 bit.

Thanks.
6 years ago
Thanks for the reply.

About the comment: [Transaction management should not be occuring in the UI regardless. If you code transaction management in the UI then you will need to figure out how it could be accomplished. This is not a good thing. ]
The transaction management in our case is really in the persistence layer by means of @version column.
In UI case:
1. User A clicks on List employee records: A table with employee records is displayed. User A selects first record, goes to its Edit page.
2. User B clicks on List employee records: A table with employee records is displayed. User B selects first record, goes to its Edit page.
3. User A commits his changes
4. User B commits his changes.
In my view, the action in step 4 should fail as User B was working with older version of entity (which was modified by user A in the meantime)

Please correct me or suggest.
7 years ago
Hello,
We are using optimistic locking using version column (JBoss + Hibernate).
Now we are planning to implement Web Services interface. My basic query is: How can we maintain data integrity?
E.g. step 1: user 1 fetches a record by sending a web service request.
step 2: user 2 in mean time modifies this record from UI.
step 3: Then user 1 modifies the record and sends it over web services to persist it.
If both these were carried from UI, user 1 would have got optimistic lock exception flow in step 3

How will the flow using web services behave? In step 3, Will user1 overwrite the changes of user 2?

Any help would be appreciated.
7 years ago
Hello,

We have a complex logic getting executed in the background (triggered by quartz). It uses a lot of stateless beans in the processing. Is it possible to start Seam Conversation explicitly for such non UI background methods.

Thanks!
Hello,

So does it mean we need both @Remove and @Destroy for a Seam component which is EJB also?

Thanks,
Vivek

I have following scenario:
At JBoss startup, I want to update all rows in a Table where the status is 'Running' to 'Failed'. I feel this is a pretty common problem and looking for a commonly used solution for this.

Thanks in advance,
Vivek
8 years ago

My mistake. I had not deployed the changes correctly. Calling the method with @Remove does remove the EJB and its fundamentally correct.

Whats the difference between @Destroy and @Remove? Are both of them needed for Seam component which is an EJB as well?

Thanks.
In fact I tried creating so many instances of the EJBs and everytime calling the @Remove method. Hundreds of instances were created and the server went OutOfMemory finally. But still the EJBs were hanging around.

Any clues?

Thanks in advance.
Thanks for the reply.

I did use the force GC option on Profiler but it still doesnt cleanup the bean.

Thanks,
Vivek

BTW, I have also tried nullifying the EJB reference. Still it doesn't work.

Thanks.
I am doing exactly this. Calling the @Remove and @Destroy annotated method from client but still I can see the SFSB hanging around in JProfiler.

I will highly appreciate any help, suggestion.

Thanks.