Ryszard Musielak
Member
Hello,
I have an SQL that is crashing out on these errors:
This is probably just the amount of data the SQL has to return. There are some suggestions where we can increase the limit:
community.progress.com
I have these settings in the following files:
The problem is, it's not clear from the article which broker files would I have to modify for the SQL . I wouldn't want to impact all the other application brokers and cause any further performance problems.
activemqsRealm.properties
jmsProvider.properties
msngrs.properties
JavaTools.properties
international.properties
conmgr.properties
AdminServerPlugins.properties
management.properties
agent.properties
smdatabase.properties
pasmgr.properties
ubroker.properties
fathom.properties
I also have these settings in the script:
@HasFetchLimit False
@TransactionIsolation 0
Kind Regards,
Richard
I have an SQL that is crashing out on these errors:
Code:
====== Start exception logging == "/home/rmusielak/SQLExplorer.exceptions" opened == Tue Jun 27 13:2
3:24 BST 2023 ======
**** 1 ****
Exception at Tue Jun 27 13:23:24 BST 2023: java.lang.OutOfMemoryError
Message (throw): ### Throwable in SQLProcessor run(). ###
Message (excp): GC overhead limit exceeded
Stack Trace:
java.lang.OutOfMemoryError: GC overhead limit exceeded
at com.ddtek.openedgeutil.ddak.a(Unknown Source)
at com.ddtek.openedgeutil.ddj.a(Unknown Source)
at com.ddtek.jdbc.openedge.client.dde.a(Unknown Source)
at com.ddtek.jdbc.openedge.client.dde.a(Unknown Source)
at com.ddtek.jdbc.openedge.client.dde.a(Unknown Source)
at com.ddtek.jdbc.openedge.client.dde.ah(Unknown Source)
at com.ddtek.jdbc.openedge.client.dde.ag(Unknown Source)
at com.ddtek.jdbc.openedge.dde.a(Unknown Source)
at com.ddtek.jdbc.openedgebase.ddcq.aa(Unknown Source)
at com.ddtek.jdbc.openedgebase.dddm.next(Unknown Source)
at com.progress.sql.explorer.SQLStringResults.vectorizeResultSet(SQLStringResults.java:897)
at com.progress.sql.explorer.SQLStringResults.getOutput(SQLStringResults.java:526)
at com.progress.sql.explorer.SQLProcessor.postCommandResults(SQLProcessor.java:214)
at com.progress.sql.explorer.SQLProcessor.run(SQLProcessor.java:128)
at java.lang.Thread.run(Thread.java:744)This is probably just the amount of data the SQL has to return. There are some suggestions where we can increase the limit:
Progress Customer Community
I have these settings in the following files:
Code:
[xxx@accordvrush properties]$ grep -i xmx *.properties
AdminServerPlugins.properties: jvmargs=-Xmx384m -XX:MaxPermSize=128m -Djava.awt.headless=true -Dsun.lang.ClassLoader.allowArraySyntax=true
JavaTools.properties: jvmargs=-Xmx512m -Xms64m -DMode=2 -Djava.util.prefs.syncInterval=2000000
JavaTools.properties: jvmargs=-Xmx512m -Xms64m -DMode=2
JavaTools.properties: jvmargs=-Xms64m -Xmx256mThe problem is, it's not clear from the article which broker files would I have to modify for the SQL . I wouldn't want to impact all the other application brokers and cause any further performance problems.
activemqsRealm.properties
jmsProvider.properties
msngrs.properties
JavaTools.properties
international.properties
conmgr.properties
AdminServerPlugins.properties
management.properties
agent.properties
smdatabase.properties
pasmgr.properties
ubroker.properties
fathom.properties
I also have these settings in the script:
@HasFetchLimit False
@TransactionIsolation 0
Kind Regards,
Richard