| Author |
Message
|
| sloaneuys |
 Posted: Wed Jul 12, 2006 2:09 am Post subject: java.lang.outofMemoryError while using JText on AIX |
 |
|
Newbie
Joined: 12 Jul 2006
Posts: 9
|
Hi all!
I'm receiving this error on a AIX machine running the queue manager.
The max message length are set to 104587600on all the channels, local queues and the transmission queues on the sending and receiving side.
The adapter falls over with the error when handling a bigger than normal file(9meg) when it needs to send it off to the Broker on a remote machine (Windows)
Time: 2006/07/12 08:12:43.948] [System: ConnectorAgent] [SS: JTextConnector] [T
hread: appPolling (#1965969531)] [Type: Trace] [Mesg: Caught java.lang.OutOfMemoryError: exiting...]
Any suggestions?
Could Java Heaps be a resulting problem??
Thanks!
Sloane |
|
| Back to top |
|
 |
| gibiman |
| Posted: Mon Jul 17, 2006 1:25 am Post subject: Post all the logs |
|
|
Novice
Joined: 14 Apr 2006
Posts: 10
|
What does the other connector log say ? ( the $var_output_log )
Had the same pb with the ICS Server .. Definetly Java Heap is the problem but still your connector might not be writing the whole error message .
Your system memory might also be the problem ( As it was in my case ) . |
|
| Back to top |
|
|
| cejones |
| Posted: Tue Jul 18, 2006 11:09 am Post subject: |
|
|
Newbie
Joined: 18 Jul 2006
Posts: 2
|
That error is coming from the JText agent process, not your MQ system. How big of a file are you trying to read/write? The biggest I've been able to handle is a 20MB xml file with a 2GB heap.
You'll need to increase the max heap size allowed for your connector. Open the start_JText.sh and near the end you'll find a comment that says "start the Java connector under the Java Application End" followed by a line that starts with
| Code: |
| exec ${CWJAVA} ${JVM_FLAGS} -Xms64m |
Right after the Xms64m, add "-Xmx2048m" or whatever value you need to increase the heap to.
I believe you can go up to 2.5GB with the 1.4 JVM. Though keep in mind that if your heap size gets bigger than the physical memory on the machine, it will page to the disk and performance will suffer (all Java processes have their own heap). Also, you don't want to make the heap too big otherwise garbage collection will not be as fast so your app will slow down too. |
|
| Back to top |
|
|
| djeripo |
| Posted: Tue Aug 01, 2006 8:25 pm Post subject: |
|
|
Master
Joined: 25 Jan 2004
Posts: 225
|
You not kidding right .Your JText is able to process 20MB file?
We are facing hell lot of problems with JText when its trying to process 11mb EDI file. |
|
| Back to top |
|
|
| cejones |
| Posted: Wed Aug 02, 2006 5:19 am Post subject: |
|
|
Newbie
Joined: 18 Jul 2006
Posts: 2
|
No kidding, I've done 20.8MB and the heap size of our JText is set to 1200MB (I misstated in my previous post), so we could go higher. Granted that was 20MB of xml so there is a lot more "filler" in there from the tags compared to your EDI file.
Are you running out of memory in JText or ICS? What's your heap size set to? |
|
| Back to top |
|
|
|
|
