Bugs item #935196, was opened at 2004-04-14 13:46 Message generated for change (Comment added) made by dgreen99 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=935196&group_id=22866
Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: eugene (eugene75) Assigned to: Nobody/Anonymous (nobody) Summary: NullPointerException in SimpleReadWriteEJBLock Initial Comment: When setting a CMR field (either one-to-one or one-to- many), a null pointer occurs in SimpleReadWriteEJBLock.schedule. The cause is a null method attribute in the Invocation object. When the invocation, in this case a CMRInvocation, is created in the JDBCRelationSetBridge object, no method is set. ---------------------------------------------------------------------- Comment By: David Green (dgreen99) Date: 2004-11-03 15:24 Message: Logged In: YES user_id=733416 All that is needed to fix this problem (against 3.2.5 codebase) is to change line 71 to the following: boolean reading = mi.getMethod() == null ? false : container.getBeanMetaData().isMethodReadOnly (mi.getMethod().getName()); It would be great to get this one fixed. ---------------------------------------------------------------------- Comment By: Kurt A. Seiffert (seiffert) Date: 2004-07-12 07:19 Message: Logged In: YES user_id=269007 Is there any change on this bug? This one is biting us and it would be nice if it was fixed. ---------------------------------------------------------------------- Comment By: Rajagopal Venkataraman (raja05) Date: 2004-04-20 02:33 Message: Logged In: YES user_id=206536 Or we could just get out of the schedule method on finding out that mi.getMethod is null. Anyway, the calling Tx is in effect and this method call is only to get the object corresponding to the foreign key. We probably need to change releaseReadLock and releaseWriteLock if we are going about in this manner ---------------------------------------------------------------------- Comment By: Rajagopal Venkataraman (raja05) Date: 2004-04-20 02:27 Message: Logged In: YES user_id=206536 Yes, so one way to circumvent this is to loop around the method-name argument. We could just check for a null value and substitute "no-method" instead. This would make boolean reading return false, so it would create a write lock and use the same Tx as it was called with. I can fill in a patch if that sounds ok ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=935196&group_id=22866 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
