[jira] Updated: (OPENJPA-1898) TestQueryMultiThreaded fails with OOME unable to create new native thread
[ https://issues.apache.org/jira/browse/OPENJPA-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-1898: --- Attachment: OPENJPA-1898.patch reduce parallel threads from 1000 to 800. Now it's not very likely that any user hits the default 1024 threads limit, but we still have enough parallel loops running TestQueryMultiThreaded fails with OOME unable to create new native thread --- Key: OPENJPA-1898 URL: https://issues.apache.org/jira/browse/OPENJPA-1898 Project: OpenJPA Issue Type: Bug Affects Versions: 2.0.1 Reporter: Mark Struberg Attachments: OPENJPA-1898.patch here comes the stacktrace: error message=unable to create new native thread type=java.lang.OutOfMemoryErrorjava.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:597) at org.apache.openjpa.slice.TestQueryMultiThreaded.testHeavyLoad(TestQueryMultiThreaded.java:236) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:154) reducing the thread count to 800 should help to prevent this problem. This might be caused to the 1024 processes ulimit on most linux installations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OPENJPA-1900) ClassCastException when serializing an entity if DetachedStateField=true
ClassCastException when serializing an entity if DetachedStateField=true Key: OPENJPA-1900 URL: https://issues.apache.org/jira/browse/OPENJPA-1900 Project: OpenJPA Issue Type: Bug Components: kernel Affects Versions: 2.0.1, 2.1.0 Reporter: Mark Struberg Fix For: 2.1.0 When using property name=openjpa.DetachState value=fetch-groups(DetachedStateField=true)/ serializing an entity leads to the following Exception: java.lang.ClassCastException: org.apache.openjpa.kernel.StateManagerImpl cannot be cast to org.apache.openjpa.kernel.DetachedStateManager at org.apache.openjpa.util.Proxies.writeReplace(Proxies.java:147) at org.apache.openjpa.util.java$util$Date$proxy.writeReplace(Unknown Source) at sun.reflect.GeneratedMethodAccessor176.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1032) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1107) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) at org.apache.openjpa.kernel.SingleFieldManager.serialize(SingleFieldManager.java:545) at org.apache.openjpa.kernel.StateManagerImpl.writeDetached(StateManagerImpl.java:1478) at at.ac.tuwien.tiss.curriculum.be.entities.CurriculumVersion.writeExternal(CurriculumVersion.java) at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1421) This seems related to OPENJPA-1597 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OPENJPA-1901) QueryCacheStoreQuery$CachedObjectId that is not Serializable
QueryCacheStoreQuery$CachedObjectId that is not Serializable Key: OPENJPA-1901 URL: https://issues.apache.org/jira/browse/OPENJPA-1901 Project: OpenJPA Issue Type: Bug Components: datacache Affects Versions: 2.0.1, 2.0.0 Reporter: Kevin Sutter In OpenJPA 2.0, OpenJPA tries to put the query result from JOIN query into query cache, in addition to put entities into data cache. However, the QueryResult containes Object[] of org.apache.openjpa.datacache.QueryCacheStoreQuery$CachedObjectId that is not Serializable and cause this issue. OpenJPA need to be fixed to make org.apache.openjpa.datacache.QueryCacheStoreQuery$CachedObjectId serializable. Currently, manually adding Serializable to the code works for measuring the performance, but we need a more permanent fix. I also have a concern whether this type of fix has a ripple effect. The CachedObjectId can easily be fixed to be Serializable, but it looks like other inner classes of QueryCacheStoreQuery are not Serializable either. Do these (and potentially other attributes) need to be Serializable as well? Do we need a Unit Test to verify this Serializable capability? Final portion of call stack when the Exception happens: Caused by: java.io.NotSerializableException: org.apache.openjpa.datacache.QueryCacheStoreQuery$CachedObjectId at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1113) at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1343) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1107) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:325) at java.util.ArrayList.writeObject(ArrayList.java:595) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:972) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1431) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1382) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:325) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Branch created for 2.1.0
Hi all, In preparation for a formal 2.1.0 release I've gone ahead and created a 2.1.x branch and moved trunk to version 2.2.0-SNAPSHOT - this was mentioned in a separate thread yesterday. Updates to the continuous build servers and downloads page will follow. Best Regards, -mike
[jira] Resolved: (OPENJPA-1863) update HSQL dictionary for HSQLDB 2.0
[ https://issues.apache.org/jira/browse/OPENJPA-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milosz Tylenda resolved OPENJPA-1863. - Resolution: Fixed Resolving so that it goes into 2.1.0 release notes. setMaxResults behaviour has been fixed. More fixes and doc update will be done in 2.2.0. update HSQL dictionary for HSQLDB 2.0 - Key: OPENJPA-1863 URL: https://issues.apache.org/jira/browse/OPENJPA-1863 Project: OpenJPA Issue Type: Improvement Reporter: Georgi Naplatanov Assignee: Milosz Tylenda Fix For: 2.1.0 Attachments: OPENJPA-1863-trunk.patch useGetObjectForBlobs should be set to false for HSQLDB 2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OPENJPA-1902) SQLServer reserved words may not be used as identifiers
SQLServer reserved words may not be used as identifiers --- Key: OPENJPA-1902 URL: https://issues.apache.org/jira/browse/OPENJPA-1902 Project: OpenJPA Issue Type: Bug Reporter: Michael Dick Assignee: Michael Dick Fix For: 2.1.0, 2.2.0 Per MSDN docs : http://msdn.microsoft.com/en-us/library/ms189822.aspx, reserved words must be delimited in order to be used as column identifiers. This is causing problems with some unit tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OPENJPA-1902) SQLServer reserved words may not be used as identifiers
[ https://issues.apache.org/jira/browse/OPENJPA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dick closed OPENJPA-1902. - Resolution: Fixed SQLServer reserved words may not be used as identifiers --- Key: OPENJPA-1902 URL: https://issues.apache.org/jira/browse/OPENJPA-1902 Project: OpenJPA Issue Type: Bug Reporter: Michael Dick Assignee: Michael Dick Fix For: 2.1.0, 2.2.0 Per MSDN docs : http://msdn.microsoft.com/en-us/library/ms189822.aspx, reserved words must be delimited in order to be used as column identifiers. This is causing problems with some unit tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1890) NPE is thrown when an Embeddable object is set more than once to a managed entity
[
https://issues.apache.org/jira/browse/OPENJPA-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-1890:
--
Affects Version/s: 2.0.1
Fix Version/s: 2.0.2
NPE is thrown when an Embeddable object is set more than once to a managed
entity
-
Key: OPENJPA-1890
URL: https://issues.apache.org/jira/browse/OPENJPA-1890
Project: OpenJPA
Issue Type: Bug
Affects Versions: 2.0.1
Reporter: Fay Wang
Assignee: Fay Wang
Fix For: 2.0.2, 2.1.0
java.lang.NullPointerException
at
org.apache.openjpa.kernel.SingleFieldManager.dereferenceEmbedDependent(SingleFieldManager.java:432)
at
org.apache.openjpa.kernel.SingleFieldManager.delete(SingleFieldManager.java:317)
at
org.apache.openjpa.kernel.SingleFieldManager.dereferenceDependent(SingleFieldManager.java:294)
at
org.apache.openjpa.kernel.StateManagerImpl.settingObjectField(StateManagerImpl.java:2031)
at embeddable.Department.pcSetdepartmentEmbeddable(Department.java)
at embeddable.Department.setDepartmentEmbeddable(Department.java:62)
at embeddable.TestEmbeddable.testFind(TestEmbeddable.java:52)
where:
private DepartmentEmbeddable makeEmbeddable() {
DepartmentEmbeddable d1 = new DepartmentEmbeddable();
d1.setDeptname(name);
d1.setMgrno(qw);
return d1;
}
@Override
public void test() {
Department d = em.find(Department.class, 1);
DepartmentEmbeddable d2 = new DepartmentEmbeddable();
d.setDepartmentEmbeddable(makeEmbeddable());
d.setDepartmentEmbeddable(makeEmbeddable()); == NPE is thrown
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (OPENJPA-1890) NPE is thrown when an Embeddable object is set more than once to a managed entity
[
https://issues.apache.org/jira/browse/OPENJPA-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick reopened OPENJPA-1890:
---
reopening to target for 2.0.2
NPE is thrown when an Embeddable object is set more than once to a managed
entity
-
Key: OPENJPA-1890
URL: https://issues.apache.org/jira/browse/OPENJPA-1890
Project: OpenJPA
Issue Type: Bug
Affects Versions: 2.0.1
Reporter: Fay Wang
Assignee: Fay Wang
Fix For: 2.0.2, 2.1.0
java.lang.NullPointerException
at
org.apache.openjpa.kernel.SingleFieldManager.dereferenceEmbedDependent(SingleFieldManager.java:432)
at
org.apache.openjpa.kernel.SingleFieldManager.delete(SingleFieldManager.java:317)
at
org.apache.openjpa.kernel.SingleFieldManager.dereferenceDependent(SingleFieldManager.java:294)
at
org.apache.openjpa.kernel.StateManagerImpl.settingObjectField(StateManagerImpl.java:2031)
at embeddable.Department.pcSetdepartmentEmbeddable(Department.java)
at embeddable.Department.setDepartmentEmbeddable(Department.java:62)
at embeddable.TestEmbeddable.testFind(TestEmbeddable.java:52)
where:
private DepartmentEmbeddable makeEmbeddable() {
DepartmentEmbeddable d1 = new DepartmentEmbeddable();
d1.setDeptname(name);
d1.setMgrno(qw);
return d1;
}
@Override
public void test() {
Department d = em.find(Department.class, 1);
DepartmentEmbeddable d2 = new DepartmentEmbeddable();
d.setDepartmentEmbeddable(makeEmbeddable());
d.setDepartmentEmbeddable(makeEmbeddable()); == NPE is thrown
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-1898) TestQueryMultiThreaded fails with OOME unable to create new native thread
[ https://issues.apache.org/jira/browse/OPENJPA-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dick resolved OPENJPA-1898. --- Resolution: Fixed Fix Version/s: 2.2.0 2.1.0 Assignee: Michael Dick Thanks for the patch Mark, I've committed it to trunk and 2.1.x. TestQueryMultiThreaded fails with OOME unable to create new native thread --- Key: OPENJPA-1898 URL: https://issues.apache.org/jira/browse/OPENJPA-1898 Project: OpenJPA Issue Type: Bug Affects Versions: 2.0.1 Reporter: Mark Struberg Assignee: Michael Dick Fix For: 2.1.0, 2.2.0 Attachments: OPENJPA-1898.patch here comes the stacktrace: error message=unable to create new native thread type=java.lang.OutOfMemoryErrorjava.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:597) at org.apache.openjpa.slice.TestQueryMultiThreaded.testHeavyLoad(TestQueryMultiThreaded.java:236) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:154) reducing the thread count to 800 should help to prevent this problem. This might be caused to the 1024 processes ulimit on most linux installations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1863) update HSQL dictionary for HSQLDB 2.0
[ https://issues.apache.org/jira/browse/OPENJPA-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milosz Tylenda updated OPENJPA-1863: Component/s: sql jdbc update HSQL dictionary for HSQLDB 2.0 - Key: OPENJPA-1863 URL: https://issues.apache.org/jira/browse/OPENJPA-1863 Project: OpenJPA Issue Type: Improvement Components: jdbc, sql Reporter: Georgi Naplatanov Assignee: Milosz Tylenda Fix For: 2.1.0 Attachments: OPENJPA-1863-trunk.patch useGetObjectForBlobs should be set to false for HSQLDB 2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
