[JBossCache] - Re: Could this be deadlock when modifying TreeCache
by ramdas
Manik,
Thanks for the response. The TreeCache is set up for "REPL_ASYNC". I am not very familiar with the JBoss cache tuning params. Was wondering if u had any comments on the configuration shown below. Since this happens on our production system and is hard to reproduce, do you have any recommendations on how to tune this? Do you still recommend removing FC?
The JBoss cache is hosted on a 8 node Linux cluster running Debian Linux based on the 2.4 kernel.
-Ramdas
| <mbean code="org.jboss.cache.TreeCache"
| name="jboss.cache:service=TreeCache">
| <depends>jboss:service=Naming</depends>
| <depends>jboss:service=TransactionManager</depends>
| <attribute name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup</attribute>
| <attribute name="IsolationLevel">READ_UNCOMMITTED</attribute>
| <attribute name="CacheMode">REPL_ASYNC</attribute>
| <attribute name="UseReplQueue">false</attribute>
| <attribute name="ClusterName">TreeCache-Cluster</attribute>
| <attribute name="ClusterConfig">
| <config>
| <UDP mcast_addr="227.1.2.3" mcast_port="45566"
| ip_ttl="32" ip_mcast="true"
| mcast_send_buf_size="10000000" mcast_recv_buf_size="10000000"
| ucast_send_buf_size="10000000" ucast_recv_buf_size="10000000"
| max_bundle_size="64000"
| max_bundle_timeout="30"
| use_incoming_packet_handler="false"
| use_outgoing_packet_handler="true"
| loopback="false"
| />
| <PING timeout="2000" down_thread="false" num_initial_members="3"/>
| <MERGE2 max_interval="10000" down_thread="false" min_interval="5000"/>
| <FD_SOCK down_thread="false"/>
| <VERIFY_SUSPECT timeout="1500" down_thread="false"/>
| <pbcast.NAKACK max_xmit_size="60000" down_thread="false" use_mcast_xmit="true" gc_lag="50" retransmit_timeout="300,600,1200,2400,4800"/>
| <UNICAST timeout="300,600,1200,2400,3600" down_thread="false"/>
| <pbcast.STABLE stability_delay="1000" desired_avg_gossip="5000" down_thread="false" max_bytes="250000"/>
| <pbcast.GMS print_local_addr="true" join_timeout="3000" down_thread="false" join_retry_timeout="2000" shun="true"/>
| <FC max_credits="1000000" down_thread="false" min_threshold="0.10"/>
| <FRAG frag_size="60000" down_thread="false" up_thread="true"/>
| <pbcast.STATE_TRANSFER down_thread="false" up_thread="false"/>
| </config>
| </attribute>
| <attribute name="FetchStateOnStartup">true</attribute>
| <attribute name="InitialStateRetrievalTimeout">5000</attribute>
| <attribute name="SyncReplTimeout">10000</attribute>
| <attribute name="LockAcquisitionTimeout">15000</attribute>
| <attribute name="EvictionPolicyClass"></attribute>
| </mbean>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063152#4063152
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063152
18Â years, 11Â months
[JBoss Seam] - EntityHome and optimistic transaction
by azalea
Hi,
Now I struggle with EntityHome :)
my environments:
JBoss AS 4.2.0.GA
Seam 2.0.0.BETA1(CVS)
Seam gen-generated project(ear)
I have a simple CRUD app using EntityHome.
The app needs the optimistic transaction.
Scenario:
1. In browser tab#1, display the person list.
2. In tab#1, select a person from the person list for editing.
(1)the selected person id is bound to EntityHome.setId().
(2)long-running conversation begins.
(3)the view for editing the person information is rendered.
3. In tab#2, display the person list.
4. In tab#2, select the same person from the person list for deleting.
(1)the selected person id is bound to EntityHome.setId().
(2)long-running conversation begins.
(3)the view for deleting is rendered.
5. In tab#2, click "delete" button.
(1)EntityHome.remove() is called.
(2)long-running conversation ends.
(3)now the person record doesn't exist in database table.
Now If I click "edit" button after editing any entity attributes in tab#1,
OptimisticLockException is thrown.
Because the person record was deleted by tab#2, this is OK.
But if I click "edit" button "without" editing any entity attributes in tab#1,
OptimisticLockException is not thrown.
And the following occur:
-Any update SQLs don't seem to be executed.
-However JSF message "successfully updated" added by EntityHome is displayed.
How can I detect this situation in my app?
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063146#4063146
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063146
18Â years, 11Â months