Websphere 8.5 with JRebel 7 and IBM JVM – Not Working

Forum on this website is being phased out. New threads or replies cannot be posted. Existing content remains available for now in read only mode. You can contact technical support at support@zeroturnaround.com.

ZeroTurnaround Homepage Forums JRebel Support Websphere 8.5 with JRebel 7 and IBM JVM – Not Working

This topic contains 0 replies, has 1 voice, and was last updated by  mfotiou 1 month, 3 weeks ago.

Viewing 1 post (of 1 total)
  • Author
  • #67068



    I’m testing the JRebel trial with our Java stack. We use Eclipse Mars with Websphere traditional profile (not Liberty) on a 64-bit IBM JVM (Java 1.6).

    Whenever I enable JRebel on the server, the server takes a very long time to start up, and the “publishing” status panel in Eclipse never dissappears. Futhermore, web applications are not accessible. When I try to access the WAS console locally, I often get blank pages, extremely slow responses, or no response at all. It seems that the entire server environment is in an inconsistent or corrupt state. The WAS console in Eclipse shows many OutOfMemoryErrors in Java heap space.

    Removing JRebel integration and cleaning/restarting the server twice seems to bring me back to a normal state.

    Do I have to integrate with Websphere 8.5 differently than simple IDE integration? The documentation online is not clear at all on this. Websphere 8.5 is supposed to be supported, but clicking that link takes me to “standalone” server integration, which is not what I want.

    So, my questions are:
    1. Is Websphere 8.5.x Traditional 64 bit supported by JRebel 7.x Eclipse Plugin?
    2. If (1) is “Yes”, then what is the proper way to install it?



Viewing 1 post (of 1 total)

The forum ‘JRebel Support’ is closed to new topics and replies.