Well, if you have concurrency at all you will get dirty reads. You will have inconsistent behavior and may corrupt your data.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Janardhan > Burugupalli > Sent: Tuesday, July 22, 2003 12:10 PM > To: [EMAIL PROTECTED] > Subject: AW: [JBoss-user] Tx lock detection not possible even as i > enabled EntityLockMonitor > > > Thanks Bill, > > But if i set the threshold to INFO or WARN i will surely miss the other > important debug statements. > > I only meant to say that can i turn off the debug stmts only > related to the > Table updates or inserts done when we modify any EJB. > > And coming to the TX problem i tried the QuedPessimistciTXlock > mechanism and > the client hanged as i expalined before > and i changed the policy to > <locking-policy>org.jboss.ejb.plugins.lock.NoLock</locking-policy> > in the Standard CMP EntityBean configuration against the doc > specification > that i shuld use this NoLock only incase of IPT. And i am also > using Commit > option A. The settings looks as follows.. for me the work is done > .. but is > it right thing or what i really dont know. Beacause inspite of > using NoLock > every TX executes correctly and all the data is also saved in the > tables. By > the way i am using ejb-jar_1_1 setting all method TX attributes in the > ejb-jar.xml > > > <container-configuration> > <container-name>Standard CMP EntityBean</container-name> > <call-logging>false</call-logging> > > <invoker-proxy-binding-name>entity-rmi-invoker</invoker-proxy-bind > ing-name> > <sync-on-commit-only>false</sync-on-commit-only> > <container-interceptors> > > <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</ > intercepto > r> > > <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor> > > <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor> > > <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor> > <interceptor > metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</in > terceptor> > > <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor> > > <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor> > > <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor> > > <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</in > terceptor> > > <interceptor>org.jboss.resource.connectionmanager.CachedConnection > Intercepto > r</interceptor> > > <interceptor>org.jboss.ejb.plugins.EntitySynchronizationIntercepto > r</interce > ptor> > </container-interceptors> > > <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool> > > <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache> > > <persistence-manager>org.jboss.ejb.plugins.jaws.JAWSPersistenceMan > ager</pers > istence-manager> > <locking-policy>org.jboss.ejb.plugins.lock.NoLock</locking-policy> > <container-cache-conf> > > <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolic > y</cache-p > olicy> > <cache-policy-conf> > <min-capacity>50</min-capacity> > <max-capacity>1000000</max-capacity> > <overager-period>300</overager-period> > <max-bean-age>600</max-bean-age> > <resizer-period>400</resizer-period> > <max-cache-miss-period>60</max-cache-miss-period> > <min-cache-miss-period>1</min-cache-miss-period> > <cache-load-factor>0.75</cache-load-factor> > </cache-policy-conf> > </container-cache-conf> > <container-pool-conf> > <MaximumSize>100</MaximumSize> > <MinimumSize>10</MinimumSize> > </container-pool-conf> > <commit-option>A</commit-option> > </container-configuration> > > > -----Ursprungliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Auftrag von Bill Burke > Gesendet: Dienstag, 22. Juli 2003 16:14 > An: [EMAIL PROTECTED] > Betreff: RE: [JBoss-user] Tx lock detection not possible even as i > enabled EntityLockMonitor > > > Does the TX eventually time out and give you a stack trace? There is one > deadlock scenario that we don't detect > All this is in the same thread. > > 1. begin tx1 > 2. access entity bean A (does lock for tx1 > 3. suspend tx1 (a RequiresNew or something similar) > 4. begin tx2 > 5. access entity bean A > > How to turn off debugging? Go to server/default/conf/log4j.xml > > In the "FILE" appender add a threshhold of WARN or INFO: > > <param name="Threshold" value="INFO"/> > > Bill > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Janardhan > > Burugupalli > > Sent: Tuesday, July 22, 2003 10:20 AM > > To: [EMAIL PROTECTED] > > Subject: AW: [JBoss-user] Tx lock detection not possible even as i > > enabled EntityLockMonitor > > > > > > Hi All, > > > > I have problems regarding the Tx lock. My client hangs when performing a > > specific command like loading data of a form the server. Its > always in the > > same place . So in dont get any error message , but to think that > > there is a > > TX lock i dont get any information in the server.log. > > > > I activated the metricsinterceptor and also the EntityLockMonitor as > > specified in the documentation. But in any case i cant see the > message or > > info regarding some TX locks or some thing like that happened. > > > > And one more thing is that i see a lot of debug output in the server.log > > file specifying all the SQL commands with rrespective values > inserted into > > the table a sample i pasted down here. I want to turn this > debug off. Can > > any one please tell me were i can do this. I tried all means of > > metricsenabled=false and also in the standardjaws.xml i turned debug to > > false . > > > > 2003-07-22 14:57:11,824 DEBUG > > [org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand] > > Set parameter: idx=5, jdbcType=VARCHAR, value= > > > > > > thanks > > and regards > > jani > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: VM Ware > > With VMware you can run multiple operating systems on a single machine. > > WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the > > same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 > > _______________________________________________ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: VM Ware > With VMware you can run multiple operating systems on a single machine. > WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the > same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > ------------------------------------------------------- > This SF.net email is sponsored by: VM Ware > With VMware you can run multiple operating systems on a single machine. > WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the > same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
