[jira] [Updated] (TOMEE-2234) BMP finder returning more than 256 entities

2019-09-16 Thread Jonathan Gallimore (Jira)


 [ 
https://issues.apache.org/jira/browse/TOMEE-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Gallimore updated TOMEE-2234:
--
Fix Version/s: (was: 8.0.0-Final)
   8.0.1

> BMP finder returning more than 256 entities
> ---
>
> Key: TOMEE-2234
> URL: https://issues.apache.org/jira/browse/TOMEE-2234
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 1.7.3, 7.0.5, 7.1.0, 8.0.0-M1
>Reporter: Thomas Lien
>Assignee: Jonathan Gallimore
>Priority: Major
>  Labels: pull-request-available
> Fix For: 8.0.1
>
> Attachments: bmp.zip, sourcecode.zip, ztest.ear.zip, zztest.war
>
>
> Running into a situation where calling an EJB2 BMP finder method that returns 
> more than 256 entities causes subsequent finder calls in the same sessionbean 
> transaction to fail.
>  
> {code:java}
> BigFinderHome bigFinderHome = (BigFinderHome)lookup("BigFinderHome");
> LittleFinderHome littleFinderHome = 
> (LittleFinderHome)lookup("LittleFinderHome");
> for (int i = 1; i < 300; ++i) {
>   // this is a test finder that returns "i" number of entities
>   // once this returns more than 256 it causes the littleFinderHome.findAll
>   // to return BigFinder entities instead of the LittleFinder entities!
>   bigFinderHome.findN(i);
>   Collection littleList = littleFinderHome.findAll();
>   for (Object obj: littleList) {
> if (!(obj instanceof LittleFinder)) {
>   StringBuilder msg = new StringBuilder();
>   msg.append("Failed with " + i + " records. LittleFinder Remote is 
> actually " + obj.getClass().getName() + " Implemented interfaces " + 
> Arrays.toString(obj.getClass().getInterfaces()));
>   if (obj instanceof EJBObject) {
> Object pk = ((EJBObject)obj).getPrimaryKey();
> msg.append(" Primary key value is " + pk);
>   }
>   throw new EJBException(msg.toString());
> }
>   }
> }{code}
>  
> I can replicate this 100% of the time by deploying the attached ztest.ear 
> application and running the FinderTestBean.main function (same as the above 
> code). I have tried this on TomEE versions 1.7.3 and 7.0.5 and they both have 
> the error.
> The error output of my test is as follows
> 09-07 12:25:13 [SEVERE] EjbTransactionUtil.handleSystemException: Failed with 
> 257 records. LittleFinder Remote is actually com.sun.proxy.$Proxy142 
> Implemented interfaces [interface ztest.BigFinder, interface 
> java.io.Serializable, interface org.apache.openejb.core.ivm.IntraVmProxy] 
> Primary key value is 1
>  
> Note that in my test I am configured to use simple jndi lookup names in the 
> system.properties
> openejb.jndiname.format=\\{interfaceClass.simpleName}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (TOMEE-2234) BMP finder returning more than 256 entities

2019-09-09 Thread Jean-Louis MONTEIRO (Jira)


 [ 
https://issues.apache.org/jira/browse/TOMEE-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Louis MONTEIRO updated TOMEE-2234:
---
Fix Version/s: (was: 8.0.0-M4)
   8.0.0-Final

> BMP finder returning more than 256 entities
> ---
>
> Key: TOMEE-2234
> URL: https://issues.apache.org/jira/browse/TOMEE-2234
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 1.7.3, 7.0.5, 7.1.0, 8.0.0-M1
>Reporter: Thomas Lien
>Assignee: Jonathan Gallimore
>Priority: Major
>  Labels: pull-request-available
> Fix For: 8.0.0-Final
>
> Attachments: bmp.zip, sourcecode.zip, ztest.ear.zip, zztest.war
>
>
> Running into a situation where calling an EJB2 BMP finder method that returns 
> more than 256 entities causes subsequent finder calls in the same sessionbean 
> transaction to fail.
>  
> {code:java}
> BigFinderHome bigFinderHome = (BigFinderHome)lookup("BigFinderHome");
> LittleFinderHome littleFinderHome = 
> (LittleFinderHome)lookup("LittleFinderHome");
> for (int i = 1; i < 300; ++i) {
>   // this is a test finder that returns "i" number of entities
>   // once this returns more than 256 it causes the littleFinderHome.findAll
>   // to return BigFinder entities instead of the LittleFinder entities!
>   bigFinderHome.findN(i);
>   Collection littleList = littleFinderHome.findAll();
>   for (Object obj: littleList) {
> if (!(obj instanceof LittleFinder)) {
>   StringBuilder msg = new StringBuilder();
>   msg.append("Failed with " + i + " records. LittleFinder Remote is 
> actually " + obj.getClass().getName() + " Implemented interfaces " + 
> Arrays.toString(obj.getClass().getInterfaces()));
>   if (obj instanceof EJBObject) {
> Object pk = ((EJBObject)obj).getPrimaryKey();
> msg.append(" Primary key value is " + pk);
>   }
>   throw new EJBException(msg.toString());
> }
>   }
> }{code}
>  
> I can replicate this 100% of the time by deploying the attached ztest.ear 
> application and running the FinderTestBean.main function (same as the above 
> code). I have tried this on TomEE versions 1.7.3 and 7.0.5 and they both have 
> the error.
> The error output of my test is as follows
> 09-07 12:25:13 [SEVERE] EjbTransactionUtil.handleSystemException: Failed with 
> 257 records. LittleFinder Remote is actually com.sun.proxy.$Proxy142 
> Implemented interfaces [interface ztest.BigFinder, interface 
> java.io.Serializable, interface org.apache.openejb.core.ivm.IntraVmProxy] 
> Primary key value is 1
>  
> Note that in my test I am configured to use simple jndi lookup names in the 
> system.properties
> openejb.jndiname.format=\\{interfaceClass.simpleName}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (TOMEE-2234) BMP finder returning more than 256 entities

2019-01-25 Thread Roberto Cortez (JIRA)


 [ 
https://issues.apache.org/jira/browse/TOMEE-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roberto Cortez updated TOMEE-2234:
--
Fix Version/s: (was: 8.0.0-M2)
   8.0.0-M3

> BMP finder returning more than 256 entities
> ---
>
> Key: TOMEE-2234
> URL: https://issues.apache.org/jira/browse/TOMEE-2234
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 1.7.3, 7.0.5, 7.1.0, 8.0.0-M1
>Reporter: Thomas Lien
>Assignee: Jonathan Gallimore
>Priority: Major
>  Labels: pull-request-available
> Fix For: 8.0.0-M3
>
> Attachments: bmp.zip, sourcecode.zip, ztest.ear.zip, zztest.war
>
>
> Running into a situation where calling an EJB2 BMP finder method that returns 
> more than 256 entities causes subsequent finder calls in the same sessionbean 
> transaction to fail.
>  
> {code:java}
> BigFinderHome bigFinderHome = (BigFinderHome)lookup("BigFinderHome");
> LittleFinderHome littleFinderHome = 
> (LittleFinderHome)lookup("LittleFinderHome");
> for (int i = 1; i < 300; ++i) {
>   // this is a test finder that returns "i" number of entities
>   // once this returns more than 256 it causes the littleFinderHome.findAll
>   // to return BigFinder entities instead of the LittleFinder entities!
>   bigFinderHome.findN(i);
>   Collection littleList = littleFinderHome.findAll();
>   for (Object obj: littleList) {
> if (!(obj instanceof LittleFinder)) {
>   StringBuilder msg = new StringBuilder();
>   msg.append("Failed with " + i + " records. LittleFinder Remote is 
> actually " + obj.getClass().getName() + " Implemented interfaces " + 
> Arrays.toString(obj.getClass().getInterfaces()));
>   if (obj instanceof EJBObject) {
> Object pk = ((EJBObject)obj).getPrimaryKey();
> msg.append(" Primary key value is " + pk);
>   }
>   throw new EJBException(msg.toString());
> }
>   }
> }{code}
>  
> I can replicate this 100% of the time by deploying the attached ztest.ear 
> application and running the FinderTestBean.main function (same as the above 
> code). I have tried this on TomEE versions 1.7.3 and 7.0.5 and they both have 
> the error.
> The error output of my test is as follows
> 09-07 12:25:13 [SEVERE] EjbTransactionUtil.handleSystemException: Failed with 
> 257 records. LittleFinder Remote is actually com.sun.proxy.$Proxy142 
> Implemented interfaces [interface ztest.BigFinder, interface 
> java.io.Serializable, interface org.apache.openejb.core.ivm.IntraVmProxy] 
> Primary key value is 1
>  
> Note that in my test I am configured to use simple jndi lookup names in the 
> system.properties
> openejb.jndiname.format=\\{interfaceClass.simpleName}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (TOMEE-2234) BMP finder returning more than 256 entities

2018-12-20 Thread Martin Wiesner (JIRA)


 [ 
https://issues.apache.org/jira/browse/TOMEE-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martin Wiesner updated TOMEE-2234:
--
Affects Version/s: 7.1.0
   8.0.0-M1

> BMP finder returning more than 256 entities
> ---
>
> Key: TOMEE-2234
> URL: https://issues.apache.org/jira/browse/TOMEE-2234
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 1.7.3, 7.0.5, 7.1.0, 8.0.0-M1
>Reporter: Thomas Lien
>Assignee: Jonathan Gallimore
>Priority: Major
>  Labels: pull-request-available
> Fix For: 8.0.0-M2
>
> Attachments: bmp.zip, sourcecode.zip, ztest.ear.zip, zztest.war
>
>
> Running into a situation where calling an EJB2 BMP finder method that returns 
> more than 256 entities causes subsequent finder calls in the same sessionbean 
> transaction to fail.
>  
> {code:java}
> BigFinderHome bigFinderHome = (BigFinderHome)lookup("BigFinderHome");
> LittleFinderHome littleFinderHome = 
> (LittleFinderHome)lookup("LittleFinderHome");
> for (int i = 1; i < 300; ++i) {
>   // this is a test finder that returns "i" number of entities
>   // once this returns more than 256 it causes the littleFinderHome.findAll
>   // to return BigFinder entities instead of the LittleFinder entities!
>   bigFinderHome.findN(i);
>   Collection littleList = littleFinderHome.findAll();
>   for (Object obj: littleList) {
> if (!(obj instanceof LittleFinder)) {
>   StringBuilder msg = new StringBuilder();
>   msg.append("Failed with " + i + " records. LittleFinder Remote is 
> actually " + obj.getClass().getName() + " Implemented interfaces " + 
> Arrays.toString(obj.getClass().getInterfaces()));
>   if (obj instanceof EJBObject) {
> Object pk = ((EJBObject)obj).getPrimaryKey();
> msg.append(" Primary key value is " + pk);
>   }
>   throw new EJBException(msg.toString());
> }
>   }
> }{code}
>  
> I can replicate this 100% of the time by deploying the attached ztest.ear 
> application and running the FinderTestBean.main function (same as the above 
> code). I have tried this on TomEE versions 1.7.3 and 7.0.5 and they both have 
> the error.
> The error output of my test is as follows
> 09-07 12:25:13 [SEVERE] EjbTransactionUtil.handleSystemException: Failed with 
> 257 records. LittleFinder Remote is actually com.sun.proxy.$Proxy142 
> Implemented interfaces [interface ztest.BigFinder, interface 
> java.io.Serializable, interface org.apache.openejb.core.ivm.IntraVmProxy] 
> Primary key value is 1
>  
> Note that in my test I am configured to use simple jndi lookup names in the 
> system.properties
> openejb.jndiname.format=\\{interfaceClass.simpleName}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (TOMEE-2234) BMP finder returning more than 256 entities

2018-12-13 Thread Martin Wiesner (JIRA)


 [ 
https://issues.apache.org/jira/browse/TOMEE-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martin Wiesner updated TOMEE-2234:
--
Fix Version/s: 8.0.0-Final

> BMP finder returning more than 256 entities
> ---
>
> Key: TOMEE-2234
> URL: https://issues.apache.org/jira/browse/TOMEE-2234
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 1.7.3, 7.0.5
>Reporter: Thomas Lien
>Assignee: Jonathan Gallimore
>Priority: Major
>  Labels: pull-request-available
> Fix For: 8.0.0-Final
>
> Attachments: bmp.zip, sourcecode.zip, ztest.ear.zip, zztest.war
>
>
> Running into a situation where calling an EJB2 BMP finder method that returns 
> more than 256 entities causes subsequent finder calls in the same sessionbean 
> transaction to fail.
>  
> {code:java}
> BigFinderHome bigFinderHome = (BigFinderHome)lookup("BigFinderHome");
> LittleFinderHome littleFinderHome = 
> (LittleFinderHome)lookup("LittleFinderHome");
> for (int i = 1; i < 300; ++i) {
>   // this is a test finder that returns "i" number of entities
>   // once this returns more than 256 it causes the littleFinderHome.findAll
>   // to return BigFinder entities instead of the LittleFinder entities!
>   bigFinderHome.findN(i);
>   Collection littleList = littleFinderHome.findAll();
>   for (Object obj: littleList) {
> if (!(obj instanceof LittleFinder)) {
>   StringBuilder msg = new StringBuilder();
>   msg.append("Failed with " + i + " records. LittleFinder Remote is 
> actually " + obj.getClass().getName() + " Implemented interfaces " + 
> Arrays.toString(obj.getClass().getInterfaces()));
>   if (obj instanceof EJBObject) {
> Object pk = ((EJBObject)obj).getPrimaryKey();
> msg.append(" Primary key value is " + pk);
>   }
>   throw new EJBException(msg.toString());
> }
>   }
> }{code}
>  
> I can replicate this 100% of the time by deploying the attached ztest.ear 
> application and running the FinderTestBean.main function (same as the above 
> code). I have tried this on TomEE versions 1.7.3 and 7.0.5 and they both have 
> the error.
> The error output of my test is as follows
> 09-07 12:25:13 [SEVERE] EjbTransactionUtil.handleSystemException: Failed with 
> 257 records. LittleFinder Remote is actually com.sun.proxy.$Proxy142 
> Implemented interfaces [interface ztest.BigFinder, interface 
> java.io.Serializable, interface org.apache.openejb.core.ivm.IntraVmProxy] 
> Primary key value is 1
>  
> Note that in my test I am configured to use simple jndi lookup names in the 
> system.properties
> openejb.jndiname.format=\\{interfaceClass.simpleName}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (TOMEE-2234) BMP finder returning more than 256 entities

2018-12-12 Thread ASF GitHub Bot (JIRA)


 [ 
https://issues.apache.org/jira/browse/TOMEE-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated TOMEE-2234:
--
Labels: pull-request-available  (was: )

> BMP finder returning more than 256 entities
> ---
>
> Key: TOMEE-2234
> URL: https://issues.apache.org/jira/browse/TOMEE-2234
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 1.7.3, 7.0.5
>Reporter: Thomas Lien
>Assignee: Jonathan Gallimore
>Priority: Major
>  Labels: pull-request-available
> Attachments: bmp.zip, sourcecode.zip, ztest.ear.zip, zztest.war
>
>
> Running into a situation where calling an EJB2 BMP finder method that returns 
> more than 256 entities causes subsequent finder calls in the same sessionbean 
> transaction to fail.
>  
> {code:java}
> BigFinderHome bigFinderHome = (BigFinderHome)lookup("BigFinderHome");
> LittleFinderHome littleFinderHome = 
> (LittleFinderHome)lookup("LittleFinderHome");
> for (int i = 1; i < 300; ++i) {
>   // this is a test finder that returns "i" number of entities
>   // once this returns more than 256 it causes the littleFinderHome.findAll
>   // to return BigFinder entities instead of the LittleFinder entities!
>   bigFinderHome.findN(i);
>   Collection littleList = littleFinderHome.findAll();
>   for (Object obj: littleList) {
> if (!(obj instanceof LittleFinder)) {
>   StringBuilder msg = new StringBuilder();
>   msg.append("Failed with " + i + " records. LittleFinder Remote is 
> actually " + obj.getClass().getName() + " Implemented interfaces " + 
> Arrays.toString(obj.getClass().getInterfaces()));
>   if (obj instanceof EJBObject) {
> Object pk = ((EJBObject)obj).getPrimaryKey();
> msg.append(" Primary key value is " + pk);
>   }
>   throw new EJBException(msg.toString());
> }
>   }
> }{code}
>  
> I can replicate this 100% of the time by deploying the attached ztest.ear 
> application and running the FinderTestBean.main function (same as the above 
> code). I have tried this on TomEE versions 1.7.3 and 7.0.5 and they both have 
> the error.
> The error output of my test is as follows
> 09-07 12:25:13 [SEVERE] EjbTransactionUtil.handleSystemException: Failed with 
> 257 records. LittleFinder Remote is actually com.sun.proxy.$Proxy142 
> Implemented interfaces [interface ztest.BigFinder, interface 
> java.io.Serializable, interface org.apache.openejb.core.ivm.IntraVmProxy] 
> Primary key value is 1
>  
> Note that in my test I am configured to use simple jndi lookup names in the 
> system.properties
> openejb.jndiname.format=\\{interfaceClass.simpleName}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (TOMEE-2234) BMP finder returning more than 256 entities

2018-12-11 Thread Jonathan Gallimore (JIRA)


 [ 
https://issues.apache.org/jira/browse/TOMEE-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Gallimore updated TOMEE-2234:
--
Attachment: bmp.zip

> BMP finder returning more than 256 entities
> ---
>
> Key: TOMEE-2234
> URL: https://issues.apache.org/jira/browse/TOMEE-2234
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 1.7.3, 7.0.5
>Reporter: Thomas Lien
>Assignee: Jonathan Gallimore
>Priority: Major
> Attachments: bmp.zip, sourcecode.zip, ztest.ear.zip, zztest.war
>
>
> Running into a situation where calling an EJB2 BMP finder method that returns 
> more than 256 entities causes subsequent finder calls in the same sessionbean 
> transaction to fail.
>  
> {code:java}
> BigFinderHome bigFinderHome = (BigFinderHome)lookup("BigFinderHome");
> LittleFinderHome littleFinderHome = 
> (LittleFinderHome)lookup("LittleFinderHome");
> for (int i = 1; i < 300; ++i) {
>   // this is a test finder that returns "i" number of entities
>   // once this returns more than 256 it causes the littleFinderHome.findAll
>   // to return BigFinder entities instead of the LittleFinder entities!
>   bigFinderHome.findN(i);
>   Collection littleList = littleFinderHome.findAll();
>   for (Object obj: littleList) {
> if (!(obj instanceof LittleFinder)) {
>   StringBuilder msg = new StringBuilder();
>   msg.append("Failed with " + i + " records. LittleFinder Remote is 
> actually " + obj.getClass().getName() + " Implemented interfaces " + 
> Arrays.toString(obj.getClass().getInterfaces()));
>   if (obj instanceof EJBObject) {
> Object pk = ((EJBObject)obj).getPrimaryKey();
> msg.append(" Primary key value is " + pk);
>   }
>   throw new EJBException(msg.toString());
> }
>   }
> }{code}
>  
> I can replicate this 100% of the time by deploying the attached ztest.ear 
> application and running the FinderTestBean.main function (same as the above 
> code). I have tried this on TomEE versions 1.7.3 and 7.0.5 and they both have 
> the error.
> The error output of my test is as follows
> 09-07 12:25:13 [SEVERE] EjbTransactionUtil.handleSystemException: Failed with 
> 257 records. LittleFinder Remote is actually com.sun.proxy.$Proxy142 
> Implemented interfaces [interface ztest.BigFinder, interface 
> java.io.Serializable, interface org.apache.openejb.core.ivm.IntraVmProxy] 
> Primary key value is 1
>  
> Note that in my test I am configured to use simple jndi lookup names in the 
> system.properties
> openejb.jndiname.format=\\{interfaceClass.simpleName}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (TOMEE-2234) BMP finder returning more than 256 entities

2018-12-10 Thread Thomas Lien (JIRA)


 [ 
https://issues.apache.org/jira/browse/TOMEE-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Lien updated TOMEE-2234:
---
Description: 
Running into a situation where calling an EJB2 BMP finder method that returns 
more than 256 entities causes subsequent finder calls in the same sessionbean 
transaction to fail.

 
{code:java}
BigFinderHome bigFinderHome = (BigFinderHome)lookup("BigFinderHome");
LittleFinderHome littleFinderHome = 
(LittleFinderHome)lookup("LittleFinderHome");
for (int i = 1; i < 300; ++i) {
  // this is a test finder that returns "i" number of entities
  // once this returns more than 256 it causes the littleFinderHome.findAll
  // to return BigFinder entities instead of the LittleFinder entities!
  bigFinderHome.findN(i);
  Collection littleList = littleFinderHome.findAll();
  for (Object obj: littleList) {
if (!(obj instanceof LittleFinder)) {
  StringBuilder msg = new StringBuilder();
  msg.append("Failed with " + i + " records. LittleFinder Remote is 
actually " + obj.getClass().getName() + " Implemented interfaces " + 
Arrays.toString(obj.getClass().getInterfaces()));
  if (obj instanceof EJBObject) {
Object pk = ((EJBObject)obj).getPrimaryKey();
msg.append(" Primary key value is " + pk);
  }
  throw new EJBException(msg.toString());
}
  }
}{code}
 

I can replicate this 100% of the time by deploying the attached ztest.ear 
application and running the FinderTestBean.main function (same as the above 
code). I have tried this on TomEE versions 1.7.3 and 7.0.5 and they both have 
the error.

The error output of my test is as follows

09-07 12:25:13 [SEVERE] EjbTransactionUtil.handleSystemException: Failed with 
257 records. LittleFinder Remote is actually com.sun.proxy.$Proxy142 
Implemented interfaces [interface ztest.BigFinder, interface 
java.io.Serializable, interface org.apache.openejb.core.ivm.IntraVmProxy] 
Primary key value is 1

 

Note that in my test I am configured to use simple jndi lookup names in the 
system.properties

openejb.jndiname.format=\\{interfaceClass.simpleName}

  was:
Running into a situation where calling an EJB2 BMP finder method that returns 
more than 256 entities causes subsequent finder calls in the same sessionbean 
transaction to fail.

 
{code:java}
BigFinderHome bigFinderHome = (BigFinderHome)lookup("BigFinderHome");
LittleFinderHome littleFinderHome = 
(LittleFinderHome)lookup("LittleFinderHome");
for (int i = 1; i < 300; ++i) {
  // this is a test finder that returns "i" number of entities
  // once this returns more than 256 it causes the littleFinderHome.findAll
  // to return BigFinder entities instead of the LittleFinder entities!
  bigFinderHome.findN(i);
  Collection littleList = littleFinderHome.findAll();
  for (Object obj: littleList) {
StringBuilder msg = new StringBuilder();
if (!(obj instanceof LittleFinder)) {
  msg.append("Failed with " + i + " records. LittleFinder Remote is 
actually " + obj.getClass().getName() + " Implemented interfaces " + 
Arrays.toString(obj.getClass().getInterfaces()));
if (obj instanceof EJBObject) {
  Object pk = ((EJBObject)obj).getPrimaryKey();
  msg.append(" Primary key value is " + pk);
}
throw new EJBException(msg.toString());
  }
}
{code}
 

I can replicate this 100% of the time by deploying the attached ztest.ear 
application and running the FinderTestBean.main function (same as the above 
code). I have tried this on TomEE versions 1.7.3 and 7.0.5 and they both have 
the error.

The error output of my test is as follows

09-07 12:25:13 [SEVERE] EjbTransactionUtil.handleSystemException: Failed with 
257 records. LittleFinder Remote is actually com.sun.proxy.$Proxy142 
Implemented interfaces [interface ztest.BigFinder, interface 
java.io.Serializable, interface org.apache.openejb.core.ivm.IntraVmProxy] 
Primary key value is 1


> BMP finder returning more than 256 entities
> ---
>
> Key: TOMEE-2234
> URL: https://issues.apache.org/jira/browse/TOMEE-2234
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 1.7.3, 7.0.5
>Reporter: Thomas Lien
>Priority: Major
> Attachments: sourcecode.zip, ztest.ear.zip
>
>
> Running into a situation where calling an EJB2 BMP finder method that returns 
> more than 256 entities causes subsequent finder calls in the same sessionbean 
> transaction to fail.
>  
> {code:java}
> BigFinderHome bigFinderHome = (BigFinderHome)lookup("BigFinderHome");
> LittleFinderHome littleFinderHome = 
> (LittleFinderHome)lookup("LittleFinderHome");
> for (int i = 1; i < 300; ++i) {
>   // this is a test finder that returns "i" number of entities
>   // once this returns more than 256 it causes the littleFinderHome.findAll
>   // to return BigFinder entities instead of the 

[jira] [Updated] (TOMEE-2234) BMP finder returning more than 256 entities

2018-09-11 Thread Thomas Lien (JIRA)


 [ 
https://issues.apache.org/jira/browse/TOMEE-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Lien updated TOMEE-2234:
---
Attachment: ztest.ear.zip

> BMP finder returning more than 256 entities
> ---
>
> Key: TOMEE-2234
> URL: https://issues.apache.org/jira/browse/TOMEE-2234
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 1.7.3, 7.0.5
>Reporter: Thomas Lien
>Priority: Major
> Attachments: sourcecode.zip, ztest.ear.zip
>
>
> Running into a situation where calling an EJB2 BMP finder method that returns 
> more than 256 entities causes subsequent finder calls in the same sessionbean 
> transaction to fail.
>  
> {code:java}
> BigFinderHome bigFinderHome = (BigFinderHome)lookup("BigFinderHome");
> LittleFinderHome littleFinderHome = 
> (LittleFinderHome)lookup("LittleFinderHome");
> for (int i = 1; i < 300; ++i) {
>   // this is a test finder that returns "i" number of entities
>   // once this returns more than 256 it causes the littleFinderHome.findAll
>   // to return BigFinder entities instead of the LittleFinder entities!
>   bigFinderHome.findN(i);
>   Collection littleList = littleFinderHome.findAll();
>   for (Object obj: littleList) {
> StringBuilder msg = new StringBuilder();
> if (!(obj instanceof LittleFinder)) {
>   msg.append("Failed with " + i + " records. LittleFinder Remote is 
> actually " + obj.getClass().getName() + " Implemented interfaces " + 
> Arrays.toString(obj.getClass().getInterfaces()));
> if (obj instanceof EJBObject) {
>   Object pk = ((EJBObject)obj).getPrimaryKey();
>   msg.append(" Primary key value is " + pk);
> }
> throw new EJBException(msg.toString());
>   }
> }
> {code}
>  
> I can replicate this 100% of the time by deploying the attached ztest.ear 
> application and running the FinderTestBean.main function (same as the above 
> code). I have tried this on TomEE versions 1.7.3 and 7.0.5 and they both have 
> the error.
> The error output of my test is as follows
> 09-07 12:25:13 [SEVERE] EjbTransactionUtil.handleSystemException: Failed with 
> 257 records. LittleFinder Remote is actually com.sun.proxy.$Proxy142 
> Implemented interfaces [interface ztest.BigFinder, interface 
> java.io.Serializable, interface org.apache.openejb.core.ivm.IntraVmProxy] 
> Primary key value is 1



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (TOMEE-2234) BMP finder returning more than 256 entities

2018-09-11 Thread Thomas Lien (JIRA)


 [ 
https://issues.apache.org/jira/browse/TOMEE-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Lien updated TOMEE-2234:
---
Attachment: sourcecode.zip

> BMP finder returning more than 256 entities
> ---
>
> Key: TOMEE-2234
> URL: https://issues.apache.org/jira/browse/TOMEE-2234
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 1.7.3, 7.0.5
>Reporter: Thomas Lien
>Priority: Major
> Attachments: sourcecode.zip
>
>
> Running into a situation where calling an EJB2 BMP finder method that returns 
> more than 256 entities causes subsequent finder calls in the same sessionbean 
> transaction to fail.
>  
> {code:java}
> BigFinderHome bigFinderHome = (BigFinderHome)lookup("BigFinderHome");
> LittleFinderHome littleFinderHome = 
> (LittleFinderHome)lookup("LittleFinderHome");
> for (int i = 1; i < 300; ++i) {
>   // this is a test finder that returns "i" number of entities
>   // once this returns more than 256 it causes the littleFinderHome.findAll
>   // to return BigFinder entities instead of the LittleFinder entities!
>   bigFinderHome.findN(i);
>   Collection littleList = littleFinderHome.findAll();
>   for (Object obj: littleList) {
> StringBuilder msg = new StringBuilder();
> if (!(obj instanceof LittleFinder)) {
>   msg.append("Failed with " + i + " records. LittleFinder Remote is 
> actually " + obj.getClass().getName() + " Implemented interfaces " + 
> Arrays.toString(obj.getClass().getInterfaces()));
> if (obj instanceof EJBObject) {
>   Object pk = ((EJBObject)obj).getPrimaryKey();
>   msg.append(" Primary key value is " + pk);
> }
> throw new EJBException(msg.toString());
>   }
> }
> {code}
>  
> I can replicate this 100% of the time by deploying the attached ztest.ear 
> application and running the FinderTestBean.main function (same as the above 
> code). I have tried this on TomEE versions 1.7.3 and 7.0.5 and they both have 
> the error.
> The error output of my test is as follows
> 09-07 12:25:13 [SEVERE] EjbTransactionUtil.handleSystemException: Failed with 
> 257 records. LittleFinder Remote is actually com.sun.proxy.$Proxy142 
> Implemented interfaces [interface ztest.BigFinder, interface 
> java.io.Serializable, interface org.apache.openejb.core.ivm.IntraVmProxy] 
> Primary key value is 1



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)