tag:blogger.com,1999:blog-5215551487816981140.post4115657741448285766..comments2024-01-23T06:10:31.184-08:00Comments on ORA-00001: Unique constraint violated: ORDS Java heap space OutOfMemoryErrorMorten Bratenhttp://www.blogger.com/profile/12300886042835631690noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-5215551487816981140.post-16614913172041537102016-05-31T07:14:12.017-07:002016-05-31T07:14:12.017-07:00Hi Morton,
thanks for your Tip.
You suggest the -...Hi Morton,<br />thanks for your Tip.<br /><br />You suggest the -Xms128m and -Xmx512m values per ORDS or per connectet database?<br />We use one ORDS for conntecd with two PDBs.<br />And we run 3 different ORDS on one tomcat<br /><br />Regards,<br />ManuManuelhttp://www.knuspermedia.denoreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-87786812430187041912015-10-09T06:38:51.547-07:002015-10-09T06:38:51.547-07:00Hi Morten,
we use BIRT as report engine for our Ap...Hi Morten,<br />we use BIRT as report engine for our Apex application and we had many problems with "Java heap space".<br />It seems that today we finally found the solution: the 12c version of Oracle JDBC.<br />With Java JDK 7 must be used ojdbc7.jar not ojdbc6.jar.<br />No more problems with BIRT Designer, next week will test Tomcat 7 and 8.<br /><br />Regards,<br />GianluigiGianluigi Trentohttp://blog.betasoftware.itnoreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-35103614345186675172015-10-09T05:09:46.376-07:002015-10-09T05:09:46.376-07:00I can also advise that I have run into the problem...I can also advise that I have run into the problem too, in my case it would fail on page where I would post base64 encoded files via f0x arrays. I came across the following post at the time which may have suggested it was a memory deallocation issue with associative arrays with the flavour of jdk in use: https://community.oracle.com/thread/1776427?start=0<br /><br />MattAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-63326155188983084762015-10-06T16:41:43.093-07:002015-10-06T16:41:43.093-07:00Hi Morten
I had the same issue with ORDS 2.x abou...Hi Morten<br /><br />I had the same issue with ORDS 2.x about 18 months ago, at a clients site.<br /><br />Similar issue, with a tabular form with a large number of editable fields.<br />Like you we increased the memory, but even that wasn't enough.<br /><br />Tested reducing the number of editable fields (rows), which made the issue go away, but wasn't an viable solution for the particular page.<br />Logged a SR with Oracle Support, who said the issue was with Java memory allocation and no solution was available at the time.<br /><br />Ended up having to switch back to Oracle HTTP server with mod_plsql, which resolved the issue.<br /><br />We did limited testing due to time constraints, I would have liked to see if making the max length for input items smaller affected memory allocation or not.<br /><br />I had hoped the issue was resolved in ORDS 3.x, but your blog indicates it's still an issue.<br /><br />Regards<br /><br />MarkMark Lancasterhttps://www.blogger.com/profile/06316329564169609358noreply@blogger.com