Skip to content

Exception in thread “Email Daemon” java.lang.OutOfMemoryError: Java heap space

We recently launched BMC Remedy 7.1. It’s been a great project learning the characteristics of a very powerful application platform. One of the issues we ran into, shortly after we launched our production server was the error “Exception in thread “Email Daemon” java.lang.OutOfMemoryError: Java heap space” in the stderr.log When looking through the Email Messages form, a large number of messages were also queued for delivery. Clearly, something was wrong as the server had 8 GBs of RAM, so any out of memory error message could only mean a configuration issue or worst case scenario, bad memory. If anyone else is in the same boat, here’s a solution that worked for us:

  1. Click on Start
  2. Click on Run
  3. Type regedit and press Enter
  4. Navigate to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > BMC Remedy Email Engine > Parameters
  5. Double click the JVM Option Count : REG_DWORD : 0x2
  6. Change the value from 2 to 4 and click OK
  7. Click Edi t> New > String Value
  8. Enter JVM Option Number 2 as the Value name then enter –Xms128m as the Value data and click OK
  9. Click Edit > New > String Value
  10. Enter JVM Option Number 3 as the Value name then enter –Xmx512m as the Value data and click OK
  11. Restart BMC Remedy Email Engine
Tags:

7 thoughts on “Exception in thread “Email Daemon” java.lang.OutOfMemoryError: Java heap space”

  1. jobray

    I am having the exact same problem… I did the same as you, on our develpment and UAT servers and it worked fine. When doing that on our production servers, I get a registry error (file not found) when restarting the email engine.

  2. Leo

    We experienced something similar, and of course the standard, works on my machine disclaimer 🙂

    But, on our production server, there’s an EmailStart.bat file in the \Program Files\AR System\AREmail\ folder. When we ran this file the queued messages were sent without any issues.

    To get some debug logs we added the line “%JavaPath%\java” -Dmail.debug=true -cp to this file. However, this ended up causing a similar issue that you’re describing.

    Our event viewer kept referencing an invalid Win32 application and others like “Error 193: 0xc1 when starting Remedy services”.

    The solution was to ensure that the debug file did not create a file called ‘Program’ in the root folder.

  3. kavaaaaaaaaaa

    Rus.
    Пессимист учит китайский, оптимист английский, а реалист автомат Калашникова! 🙁
    Как ни грустно, но история человеческой цивилизации обязывает к наращиванию военной мощи.
    Я бы хотел тут увидеть споры не о том “да” или “нет”, а когда, кого и с кем.

    Eng.
    The pessimist learns Chinese, the optimist English, and the realist the automatic machine ak47!: (
    As it is sad, but the history of a human civilisation obliges to escalating of military power.
    I would like to see here disputes not about that “yes” or “was not present”, and when, whom and with whom.

  6. MutrisguibDug

    Hi.
    My PC worked slowly, too much mistakes and buggs. Please, help me to fix buggs on my PC.
    I used Windows XP.
    With best regards,
    MutrisguibDug

  7. MaizosMecrera

    Hi guys,
    My PC worked not correctly, too much errors. Help me, please to fix errors on my computer.
    My operation system is Windows XP.
    Thx,
    MaizosMecrera

Comments are closed.