[JBoss-dev] [ jboss-Bugs-705542 ] Errorenous IllegalStateException on CMR-Collection
Bugs item #705542, was opened at 2003-03-18 13:53 Message generated for change (Comment added) made by loubyansky You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 Category: JBossCMP Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Johan Granlund (johgr814) Assigned to: Nobody/Anonymous (nobody) Summary: Errorenous IllegalStateException on CMR-Collection Initial Comment: We've been dealing with this bug since we started up our project with JBoss 3.0.0. Now we are using JBoss 3.0.2RC2 with Postgres 7.2 and we still get it. When we are using a Collection retrieved with a CMR-getter on a local interface the Collection sporadicly maybe 1 of 200 calls thinks it was created in another transaction that obviously isn't the case. We get a stacktrace like this: 12:21:38,121 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: The iterator of a CMR collection may only be used within the transction in which it was created at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.verif yIteratorIsValid(RelationSet.java:345) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.has Next(RelationSet.java:298) at se.alleato.ejb.alexandria.server.facade.PersonFacadeBe an.getNodePersonRoles(PersonFacadeBean.java:318) ... This isn't isolated to any specific bean, instead it occurs on Collection retrieved by local CMP interfaces that are called often. It is obvious an errorenous behaviour that can be worked around by catching the exception and creating the Collection again by calling the getter again which works fine but clearly is anoying. -- Comment By: Alexey Loubyansky (loubyansky) Date: 2004-06-10 10:11 Message: Logged In: YES user_id=543482 Does setting read-only=false help? -- Comment By: Don Vines (dvines) Date: 2004-06-10 02:54 Message: Logged In: YES user_id=955996 We're getting the same error with JBoss 3.2.2 under heavy load; where heavy load is stress test with 10 threads. Has this bug been fixed? Is there a patch that I can apply to 3.2.2 or should I try JBoss 3.2.3? Here's some additional information on our environment. We run JBoss 3.2.2 on Linux with the Sun JVM 1.4.1. The database is MS SQL Server 2000 with the Opta2000 driver We using CMP 2.0. The relationship uses read-ahead with on- find. Its accessor method is defined as read-only. We're also using commit option A. The transaction type is required. We call the method which traverses the 1-m relationship and returns a set. We get an iterator from that set and use it in in the same transaction. We do not store the set and use it in another transaction. Any thoughts or suggestions on a work around? Thanks, -- Don -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-04-01 11:27 Message: Logged In: YES user_id=543482 Please, try 3.2.0RC5 from CVS. It should be fixed now. Thanks, alex -- Comment By: Johan Granlund (johgr814) Date: 2003-04-01 10:48 Message: Logged In: YES user_id=509036 Yes I'm using pessimistic locking, never got any performance out of the optimistic. I pretty sure this is a duplicate bug #634910 and in that report there is test case. -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-03-28 17:17 Message: Logged In: YES user_id=543482 Are you using pessimistic locking? I tried to reproduce it but couldn't. I have a Parent and 1000 of related Child instances. There are 100 concurrent threads that getting parent's children collection and iterate over it. This does not fail for me. If could you provide a testcase that fails even time to time that would be great. alex -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 12:15 Message: Logged In: YES user_id=509036 I'm using Required transaction setting. The error occurs no matter what commit option I'm using. I don't think any special use case is required to reproduce it, just specify two entity beans A 1-n B. Create one session bean that fetches the collection a.getBs() and iterate over it. With some load the error will occur. -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 12:06 Message: Logged In: YES user_id=509036 Sorry about that, 3.2.0RC2 it was, and now 3.2.0RC4. I can also add that the easiest way to reproduce the bug is to put load on the system, then you can be sure it will happen, in our case it starts around 15 simultanous users. To work around the problem I have
[JBoss-dev] [ jboss-Bugs-705542 ] Errorenous IllegalStateException on CMR-Collection
Bugs item #705542, was opened at 2003-03-18 11:53 Message generated for change (Comment added) made by dvines You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 Category: JBossCMP Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Johan Granlund (johgr814) Assigned to: Nobody/Anonymous (nobody) Summary: Errorenous IllegalStateException on CMR-Collection Initial Comment: We've been dealing with this bug since we started up our project with JBoss 3.0.0. Now we are using JBoss 3.0.2RC2 with Postgres 7.2 and we still get it. When we are using a Collection retrieved with a CMR-getter on a local interface the Collection sporadicly maybe 1 of 200 calls thinks it was created in another transaction that obviously isn't the case. We get a stacktrace like this: 12:21:38,121 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: The iterator of a CMR collection may only be used within the transction in which it was created at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.verif yIteratorIsValid(RelationSet.java:345) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.has Next(RelationSet.java:298) at se.alleato.ejb.alexandria.server.facade.PersonFacadeBe an.getNodePersonRoles(PersonFacadeBean.java:318) ... This isn't isolated to any specific bean, instead it occurs on Collection retrieved by local CMP interfaces that are called often. It is obvious an errorenous behaviour that can be worked around by catching the exception and creating the Collection again by calling the getter again which works fine but clearly is anoying. -- Comment By: Don Vines (dvines) Date: 2004-06-10 13:55 Message: Logged In: YES user_id=955996 Alex, Thank you for your response. We haven't tried setting read-only=false for the entity yet because the data that we're dealing with is the catalog for a commerce site which is browsed. But the stress test shows good performance, ie. sub-second response time for browsing from the web client all the way to apache, jboss/tomcat, etc. One question and that is if we change the entities to read- only=false then JBoss will call ejbStore() methods (which in our case is unnecessary) so is there some way to null out those ejbStores so they don't actually make the SQL calls? Thanks, -- Don -- Comment By: Alexey Loubyansky (loubyansky) Date: 2004-06-10 07:11 Message: Logged In: YES user_id=543482 Does setting read-only=false help? -- Comment By: Don Vines (dvines) Date: 2004-06-09 23:54 Message: Logged In: YES user_id=955996 We're getting the same error with JBoss 3.2.2 under heavy load; where heavy load is stress test with 10 threads. Has this bug been fixed? Is there a patch that I can apply to 3.2.2 or should I try JBoss 3.2.3? Here's some additional information on our environment. We run JBoss 3.2.2 on Linux with the Sun JVM 1.4.1. The database is MS SQL Server 2000 with the Opta2000 driver We using CMP 2.0. The relationship uses read-ahead with on- find. Its accessor method is defined as read-only. We're also using commit option A. The transaction type is required. We call the method which traverses the 1-m relationship and returns a set. We get an iterator from that set and use it in in the same transaction. We do not store the set and use it in another transaction. Any thoughts or suggestions on a work around? Thanks, -- Don -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-04-01 08:27 Message: Logged In: YES user_id=543482 Please, try 3.2.0RC5 from CVS. It should be fixed now. Thanks, alex -- Comment By: Johan Granlund (johgr814) Date: 2003-04-01 07:48 Message: Logged In: YES user_id=509036 Yes I'm using pessimistic locking, never got any performance out of the optimistic. I pretty sure this is a duplicate bug #634910 and in that report there is test case. -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-03-28 15:17 Message: Logged In: YES user_id=543482 Are you using pessimistic locking? I tried to reproduce it but couldn't. I have a Parent and 1000 of related Child instances. There are 100 concurrent threads that getting parent's children collection and iterate over it. This does not fail for me. If could you provide a testcase that fails even time to time that would be great. alex -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 10:15 Message: Logged In: YES user_id=509036
[JBoss-dev] [ jboss-Bugs-705542 ] Errorenous IllegalStateException on CMR-Collection
Bugs item #705542, was opened at 2003-03-18 11:53 Message generated for change (Comment added) made by dvines You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 Category: JBossCMP Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Johan Granlund (johgr814) Assigned to: Nobody/Anonymous (nobody) Summary: Errorenous IllegalStateException on CMR-Collection Initial Comment: We've been dealing with this bug since we started up our project with JBoss 3.0.0. Now we are using JBoss 3.0.2RC2 with Postgres 7.2 and we still get it. When we are using a Collection retrieved with a CMR-getter on a local interface the Collection sporadicly maybe 1 of 200 calls thinks it was created in another transaction that obviously isn't the case. We get a stacktrace like this: 12:21:38,121 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: The iterator of a CMR collection may only be used within the transction in which it was created at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.verif yIteratorIsValid(RelationSet.java:345) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.has Next(RelationSet.java:298) at se.alleato.ejb.alexandria.server.facade.PersonFacadeBe an.getNodePersonRoles(PersonFacadeBean.java:318) ... This isn't isolated to any specific bean, instead it occurs on Collection retrieved by local CMP interfaces that are called often. It is obvious an errorenous behaviour that can be worked around by catching the exception and creating the Collection again by calling the getter again which works fine but clearly is anoying. -- Comment By: Don Vines (dvines) Date: 2004-06-10 14:44 Message: Logged In: YES user_id=955996 Alex, Woohoo! Its fixed. The problem was that we didn't mark all of the catalog entities as read-only. We had a couple that were marked read-write. We made sure all the catalog entities were marked as read-only=false and viola. It fixed not only the exception that we were getting that says CMR collection may only be used within the transaction in which it was created, but also the exception that we were getting that says CMR field value is already loaded. We tested it on both JBoss 3.2.2 and 3.2.3 and it worked. Thanks for your help. -- Don -- Comment By: Don Vines (dvines) Date: 2004-06-10 13:55 Message: Logged In: YES user_id=955996 Alex, Thank you for your response. We haven't tried setting read-only=false for the entity yet because the data that we're dealing with is the catalog for a commerce site which is browsed. But the stress test shows good performance, ie. sub-second response time for browsing from the web client all the way to apache, jboss/tomcat, etc. One question and that is if we change the entities to read- only=false then JBoss will call ejbStore() methods (which in our case is unnecessary) so is there some way to null out those ejbStores so they don't actually make the SQL calls? Thanks, -- Don -- Comment By: Alexey Loubyansky (loubyansky) Date: 2004-06-10 07:11 Message: Logged In: YES user_id=543482 Does setting read-only=false help? -- Comment By: Don Vines (dvines) Date: 2004-06-09 23:54 Message: Logged In: YES user_id=955996 We're getting the same error with JBoss 3.2.2 under heavy load; where heavy load is stress test with 10 threads. Has this bug been fixed? Is there a patch that I can apply to 3.2.2 or should I try JBoss 3.2.3? Here's some additional information on our environment. We run JBoss 3.2.2 on Linux with the Sun JVM 1.4.1. The database is MS SQL Server 2000 with the Opta2000 driver We using CMP 2.0. The relationship uses read-ahead with on- find. Its accessor method is defined as read-only. We're also using commit option A. The transaction type is required. We call the method which traverses the 1-m relationship and returns a set. We get an iterator from that set and use it in in the same transaction. We do not store the set and use it in another transaction. Any thoughts or suggestions on a work around? Thanks, -- Don -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-04-01 08:27 Message: Logged In: YES user_id=543482 Please, try 3.2.0RC5 from CVS. It should be fixed now. Thanks, alex -- Comment By: Johan Granlund (johgr814) Date: 2003-04-01 07:48 Message: Logged In: YES user_id=509036 Yes I'm using pessimistic locking, never got any performance out of the optimistic. I pretty sure this is a duplicate bug #634910 and
[JBoss-dev] [ jboss-Bugs-705542 ] Errorenous IllegalStateException on CMR-Collection
Bugs item #705542, was opened at 2003-03-18 11:53 Message generated for change (Comment added) made by dvines You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 Category: JBossCMP Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Johan Granlund (johgr814) Assigned to: Nobody/Anonymous (nobody) Summary: Errorenous IllegalStateException on CMR-Collection Initial Comment: We've been dealing with this bug since we started up our project with JBoss 3.0.0. Now we are using JBoss 3.0.2RC2 with Postgres 7.2 and we still get it. When we are using a Collection retrieved with a CMR-getter on a local interface the Collection sporadicly maybe 1 of 200 calls thinks it was created in another transaction that obviously isn't the case. We get a stacktrace like this: 12:21:38,121 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: The iterator of a CMR collection may only be used within the transction in which it was created at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.verif yIteratorIsValid(RelationSet.java:345) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.has Next(RelationSet.java:298) at se.alleato.ejb.alexandria.server.facade.PersonFacadeBe an.getNodePersonRoles(PersonFacadeBean.java:318) ... This isn't isolated to any specific bean, instead it occurs on Collection retrieved by local CMP interfaces that are called often. It is obvious an errorenous behaviour that can be worked around by catching the exception and creating the Collection again by calling the getter again which works fine but clearly is anoying. -- Comment By: Don Vines (dvines) Date: 2004-06-09 23:54 Message: Logged In: YES user_id=955996 We're getting the same error with JBoss 3.2.2 under heavy load; where heavy load is stress test with 10 threads. Has this bug been fixed? Is there a patch that I can apply to 3.2.2 or should I try JBoss 3.2.3? Here's some additional information on our environment. We run JBoss 3.2.2 on Linux with the Sun JVM 1.4.1. The database is MS SQL Server 2000 with the Opta2000 driver We using CMP 2.0. The relationship uses read-ahead with on- find. Its accessor method is defined as read-only. We're also using commit option A. The transaction type is required. We call the method which traverses the 1-m relationship and returns a set. We get an iterator from that set and use it in in the same transaction. We do not store the set and use it in another transaction. Any thoughts or suggestions on a work around? Thanks, -- Don -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-04-01 08:27 Message: Logged In: YES user_id=543482 Please, try 3.2.0RC5 from CVS. It should be fixed now. Thanks, alex -- Comment By: Johan Granlund (johgr814) Date: 2003-04-01 07:48 Message: Logged In: YES user_id=509036 Yes I'm using pessimistic locking, never got any performance out of the optimistic. I pretty sure this is a duplicate bug #634910 and in that report there is test case. -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-03-28 15:17 Message: Logged In: YES user_id=543482 Are you using pessimistic locking? I tried to reproduce it but couldn't. I have a Parent and 1000 of related Child instances. There are 100 concurrent threads that getting parent's children collection and iterate over it. This does not fail for me. If could you provide a testcase that fails even time to time that would be great. alex -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 10:15 Message: Logged In: YES user_id=509036 I'm using Required transaction setting. The error occurs no matter what commit option I'm using. I don't think any special use case is required to reproduce it, just specify two entity beans A 1-n B. Create one session bean that fetches the collection a.getBs() and iterate over it. With some load the error will occur. -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 10:06 Message: Logged In: YES user_id=509036 Sorry about that, 3.2.0RC2 it was, and now 3.2.0RC4. I can also add that the easiest way to reproduce the bug is to put load on the system, then you can be sure it will happen, in our case it starts around 15 simultanous users. To work around the problem I have patched the RelationSet class. In the constructor I copy the setHandle array to the member variable instead of assigning it. This makes everything work fine but clearly isn't the correct way.
[JBoss-dev] [ jboss-Bugs-705542 ] Errorenous IllegalStateException on CMR-Collection
Bugs item #705542, was opened at 2003-03-18 13:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Johan Granlund (johgr814) Assigned to: Nobody/Anonymous (nobody) Summary: Errorenous IllegalStateException on CMR-Collection Initial Comment: We've been dealing with this bug since we started up our project with JBoss 3.0.0. Now we are using JBoss 3.0.2RC2 with Postgres 7.2 and we still get it. When we are using a Collection retrieved with a CMR-getter on a local interface the Collection sporadicly maybe 1 of 200 calls thinks it was created in another transaction that obviously isn't the case. We get a stacktrace like this: 12:21:38,121 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: The iterator of a CMR collection may only be used within the transction in which it was created at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.verif yIteratorIsValid(RelationSet.java:345) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.has Next(RelationSet.java:298) at se.alleato.ejb.alexandria.server.facade.PersonFacadeBe an.getNodePersonRoles(PersonFacadeBean.java:318) ... This isn't isolated to any specific bean, instead it occurs on Collection retrieved by local CMP interfaces that are called often. It is obvious an errorenous behaviour that can be worked around by catching the exception and creating the Collection again by calling the getter again which works fine but clearly is anoying. -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-04-01 11:27 Message: Logged In: YES user_id=543482 Please, try 3.2.0RC5 from CVS. It should be fixed now. Thanks, alex -- Comment By: Johan Granlund (johgr814) Date: 2003-04-01 10:48 Message: Logged In: YES user_id=509036 Yes I'm using pessimistic locking, never got any performance out of the optimistic. I pretty sure this is a duplicate bug #634910 and in that report there is test case. -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-03-28 17:17 Message: Logged In: YES user_id=543482 Are you using pessimistic locking? I tried to reproduce it but couldn't. I have a Parent and 1000 of related Child instances. There are 100 concurrent threads that getting parent's children collection and iterate over it. This does not fail for me. If could you provide a testcase that fails even time to time that would be great. alex -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 12:15 Message: Logged In: YES user_id=509036 I'm using Required transaction setting. The error occurs no matter what commit option I'm using. I don't think any special use case is required to reproduce it, just specify two entity beans A 1-n B. Create one session bean that fetches the collection a.getBs() and iterate over it. With some load the error will occur. -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 12:06 Message: Logged In: YES user_id=509036 Sorry about that, 3.2.0RC2 it was, and now 3.2.0RC4. I can also add that the easiest way to reproduce the bug is to put load on the system, then you can be sure it will happen, in our case it starts around 15 simultanous users. To work around the problem I have patched the RelationSet class. In the constructor I copy the setHandle array to the member variable instead of assigning it. This makes everything work fine but clearly isn't the correct way. -- Comment By: Stephen Coy (scoy) Date: 2003-03-28 11:30 Message: Logged In: YES user_id=463096 Are you *really* using JBoss 3.0.2RC2? Or is it 3.2.0RC2? Either way, you need to provide more information wrt to the way you are specifying your transactions and your use cases. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-705542 ] Errorenous IllegalStateException on CMR-Collection
Bugs item #705542, was opened at 2003-03-18 12:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Johan Granlund (johgr814) Assigned to: Nobody/Anonymous (nobody) Summary: Errorenous IllegalStateException on CMR-Collection Initial Comment: We've been dealing with this bug since we started up our project with JBoss 3.0.0. Now we are using JBoss 3.0.2RC2 with Postgres 7.2 and we still get it. When we are using a Collection retrieved with a CMR-getter on a local interface the Collection sporadicly maybe 1 of 200 calls thinks it was created in another transaction that obviously isn't the case. We get a stacktrace like this: 12:21:38,121 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: The iterator of a CMR collection may only be used within the transction in which it was created at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.verif yIteratorIsValid(RelationSet.java:345) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.has Next(RelationSet.java:298) at se.alleato.ejb.alexandria.server.facade.PersonFacadeBe an.getNodePersonRoles(PersonFacadeBean.java:318) ... This isn't isolated to any specific bean, instead it occurs on Collection retrieved by local CMP interfaces that are called often. It is obvious an errorenous behaviour that can be worked around by catching the exception and creating the Collection again by calling the getter again which works fine but clearly is anoying. -- Comment By: Johan Granlund (johgr814) Date: 2003-04-01 09:48 Message: Logged In: YES user_id=509036 Yes I'm using pessimistic locking, never got any performance out of the optimistic. I pretty sure this is a duplicate bug #634910 and in that report there is test case. -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-03-28 16:17 Message: Logged In: YES user_id=543482 Are you using pessimistic locking? I tried to reproduce it but couldn't. I have a Parent and 1000 of related Child instances. There are 100 concurrent threads that getting parent's children collection and iterate over it. This does not fail for me. If could you provide a testcase that fails even time to time that would be great. alex -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 11:15 Message: Logged In: YES user_id=509036 I'm using Required transaction setting. The error occurs no matter what commit option I'm using. I don't think any special use case is required to reproduce it, just specify two entity beans A 1-n B. Create one session bean that fetches the collection a.getBs() and iterate over it. With some load the error will occur. -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 11:06 Message: Logged In: YES user_id=509036 Sorry about that, 3.2.0RC2 it was, and now 3.2.0RC4. I can also add that the easiest way to reproduce the bug is to put load on the system, then you can be sure it will happen, in our case it starts around 15 simultanous users. To work around the problem I have patched the RelationSet class. In the constructor I copy the setHandle array to the member variable instead of assigning it. This makes everything work fine but clearly isn't the correct way. -- Comment By: Stephen Coy (scoy) Date: 2003-03-28 10:30 Message: Logged In: YES user_id=463096 Are you *really* using JBoss 3.0.2RC2? Or is it 3.2.0RC2? Either way, you need to provide more information wrt to the way you are specifying your transactions and your use cases. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-705542 ] Errorenous IllegalStateException on CMR-Collection
Bugs item #705542, was opened at 2003-03-18 22:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Johan Granlund (johgr814) Assigned to: Nobody/Anonymous (nobody) Summary: Errorenous IllegalStateException on CMR-Collection Initial Comment: We've been dealing with this bug since we started up our project with JBoss 3.0.0. Now we are using JBoss 3.0.2RC2 with Postgres 7.2 and we still get it. When we are using a Collection retrieved with a CMR-getter on a local interface the Collection sporadicly maybe 1 of 200 calls thinks it was created in another transaction that obviously isn't the case. We get a stacktrace like this: 12:21:38,121 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: The iterator of a CMR collection may only be used within the transction in which it was created at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.verif yIteratorIsValid(RelationSet.java:345) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.has Next(RelationSet.java:298) at se.alleato.ejb.alexandria.server.facade.PersonFacadeBe an.getNodePersonRoles(PersonFacadeBean.java:318) ... This isn't isolated to any specific bean, instead it occurs on Collection retrieved by local CMP interfaces that are called often. It is obvious an errorenous behaviour that can be worked around by catching the exception and creating the Collection again by calling the getter again which works fine but clearly is anoying. -- Comment By: Stephen Coy (scoy) Date: 2003-03-28 20:30 Message: Logged In: YES user_id=463096 Are you *really* using JBoss 3.0.2RC2? Or is it 3.2.0RC2? Either way, you need to provide more information wrt to the way you are specifying your transactions and your use cases. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-705542 ] Errorenous IllegalStateException on CMR-Collection
Bugs item #705542, was opened at 2003-03-18 12:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Johan Granlund (johgr814) Assigned to: Nobody/Anonymous (nobody) Summary: Errorenous IllegalStateException on CMR-Collection Initial Comment: We've been dealing with this bug since we started up our project with JBoss 3.0.0. Now we are using JBoss 3.0.2RC2 with Postgres 7.2 and we still get it. When we are using a Collection retrieved with a CMR-getter on a local interface the Collection sporadicly maybe 1 of 200 calls thinks it was created in another transaction that obviously isn't the case. We get a stacktrace like this: 12:21:38,121 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: The iterator of a CMR collection may only be used within the transction in which it was created at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.verif yIteratorIsValid(RelationSet.java:345) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.has Next(RelationSet.java:298) at se.alleato.ejb.alexandria.server.facade.PersonFacadeBe an.getNodePersonRoles(PersonFacadeBean.java:318) ... This isn't isolated to any specific bean, instead it occurs on Collection retrieved by local CMP interfaces that are called often. It is obvious an errorenous behaviour that can be worked around by catching the exception and creating the Collection again by calling the getter again which works fine but clearly is anoying. -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 11:06 Message: Logged In: YES user_id=509036 Sorry about that, 3.2.0RC2 it was, and now 3.2.0RC4. I can also add that the easiest way to reproduce the bug is to put load on the system, then you can be sure it will happen, in our case it starts around 15 simultanous users. To work around the problem I have patched the RelationSet class. In the constructor I copy the setHandle array to the member variable instead of assigning it. This makes everything work fine but clearly isn't the correct way. -- Comment By: Stephen Coy (scoy) Date: 2003-03-28 10:30 Message: Logged In: YES user_id=463096 Are you *really* using JBoss 3.0.2RC2? Or is it 3.2.0RC2? Either way, you need to provide more information wrt to the way you are specifying your transactions and your use cases. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-705542 ] Errorenous IllegalStateException on CMR-Collection
Bugs item #705542, was opened at 2003-03-18 12:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Johan Granlund (johgr814) Assigned to: Nobody/Anonymous (nobody) Summary: Errorenous IllegalStateException on CMR-Collection Initial Comment: We've been dealing with this bug since we started up our project with JBoss 3.0.0. Now we are using JBoss 3.0.2RC2 with Postgres 7.2 and we still get it. When we are using a Collection retrieved with a CMR-getter on a local interface the Collection sporadicly maybe 1 of 200 calls thinks it was created in another transaction that obviously isn't the case. We get a stacktrace like this: 12:21:38,121 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: The iterator of a CMR collection may only be used within the transction in which it was created at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.verif yIteratorIsValid(RelationSet.java:345) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.has Next(RelationSet.java:298) at se.alleato.ejb.alexandria.server.facade.PersonFacadeBe an.getNodePersonRoles(PersonFacadeBean.java:318) ... This isn't isolated to any specific bean, instead it occurs on Collection retrieved by local CMP interfaces that are called often. It is obvious an errorenous behaviour that can be worked around by catching the exception and creating the Collection again by calling the getter again which works fine but clearly is anoying. -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 11:15 Message: Logged In: YES user_id=509036 I'm using Required transaction setting. The error occurs no matter what commit option I'm using. I don't think any special use case is required to reproduce it, just specify two entity beans A 1-n B. Create one session bean that fetches the collection a.getBs() and iterate over it. With some load the error will occur. -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 11:06 Message: Logged In: YES user_id=509036 Sorry about that, 3.2.0RC2 it was, and now 3.2.0RC4. I can also add that the easiest way to reproduce the bug is to put load on the system, then you can be sure it will happen, in our case it starts around 15 simultanous users. To work around the problem I have patched the RelationSet class. In the constructor I copy the setHandle array to the member variable instead of assigning it. This makes everything work fine but clearly isn't the correct way. -- Comment By: Stephen Coy (scoy) Date: 2003-03-28 10:30 Message: Logged In: YES user_id=463096 Are you *really* using JBoss 3.0.2RC2? Or is it 3.2.0RC2? Either way, you need to provide more information wrt to the way you are specifying your transactions and your use cases. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-705542 ] Errorenous IllegalStateException on CMR-Collection
Bugs item #705542, was opened at 2003-03-18 13:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Johan Granlund (johgr814) Assigned to: Nobody/Anonymous (nobody) Summary: Errorenous IllegalStateException on CMR-Collection Initial Comment: We've been dealing with this bug since we started up our project with JBoss 3.0.0. Now we are using JBoss 3.0.2RC2 with Postgres 7.2 and we still get it. When we are using a Collection retrieved with a CMR-getter on a local interface the Collection sporadicly maybe 1 of 200 calls thinks it was created in another transaction that obviously isn't the case. We get a stacktrace like this: 12:21:38,121 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: The iterator of a CMR collection may only be used within the transction in which it was created at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.verif yIteratorIsValid(RelationSet.java:345) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.has Next(RelationSet.java:298) at se.alleato.ejb.alexandria.server.facade.PersonFacadeBe an.getNodePersonRoles(PersonFacadeBean.java:318) ... This isn't isolated to any specific bean, instead it occurs on Collection retrieved by local CMP interfaces that are called often. It is obvious an errorenous behaviour that can be worked around by catching the exception and creating the Collection again by calling the getter again which works fine but clearly is anoying. -- Comment By: Alexey Loubyansky (loubyansky) Date: 2003-03-28 17:17 Message: Logged In: YES user_id=543482 Are you using pessimistic locking? I tried to reproduce it but couldn't. I have a Parent and 1000 of related Child instances. There are 100 concurrent threads that getting parent's children collection and iterate over it. This does not fail for me. If could you provide a testcase that fails even time to time that would be great. alex -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 12:15 Message: Logged In: YES user_id=509036 I'm using Required transaction setting. The error occurs no matter what commit option I'm using. I don't think any special use case is required to reproduce it, just specify two entity beans A 1-n B. Create one session bean that fetches the collection a.getBs() and iterate over it. With some load the error will occur. -- Comment By: Johan Granlund (johgr814) Date: 2003-03-28 12:06 Message: Logged In: YES user_id=509036 Sorry about that, 3.2.0RC2 it was, and now 3.2.0RC4. I can also add that the easiest way to reproduce the bug is to put load on the system, then you can be sure it will happen, in our case it starts around 15 simultanous users. To work around the problem I have patched the RelationSet class. In the constructor I copy the setHandle array to the member variable instead of assigning it. This makes everything work fine but clearly isn't the correct way. -- Comment By: Stephen Coy (scoy) Date: 2003-03-28 11:30 Message: Logged In: YES user_id=463096 Are you *really* using JBoss 3.0.2RC2? Or is it 3.2.0RC2? Either way, you need to provide more information wrt to the way you are specifying your transactions and your use cases. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-705542 ] Errorenous IllegalStateException on CMR-Collection
Bugs item #705542, was opened at 2003-03-18 12:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Johan Granlund (johgr814) Assigned to: Nobody/Anonymous (nobody) Summary: Errorenous IllegalStateException on CMR-Collection Initial Comment: We've been dealing with this bug since we started up our project with JBoss 3.0.0. Now we are using JBoss 3.0.2RC2 with Postgres 7.2 and we still get it. When we are using a Collection retrieved with a CMR-getter on a local interface the Collection sporadicly maybe 1 of 200 calls thinks it was created in another transaction that obviously isn't the case. We get a stacktrace like this: 12:21:38,121 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: The iterator of a CMR collection may only be used within the transction in which it was created at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.verif yIteratorIsValid(RelationSet.java:345) at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet$1.has Next(RelationSet.java:298) at se.alleato.ejb.alexandria.server.facade.PersonFacadeBe an.getNodePersonRoles(PersonFacadeBean.java:318) ... This isn't isolated to any specific bean, instead it occurs on Collection retrieved by local CMP interfaces that are called often. It is obvious an errorenous behaviour that can be worked around by catching the exception and creating the Collection again by calling the getter again which works fine but clearly is anoying. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=705542group_id=22866 --- This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
