java.lang.OutOfMemoryError

Requested array size exceeds VM limit at org.eclipse.wst.server.core.internal.ModulePublishInfo.loadR esource(ModulePublishInfo.java:189) at org.eclipse.wst.server.core.internal.ModulePublishInfo.load( ModulePublishInfo.java:184) at org.eclipse.wst.server.core.internal.ModulePublishInfo.<init >(ModulePublishInfo.java:84) at org.eclipse.wst.server.core.internal.ServerPublishInfo.load( ServerPublishInfo.java:274) at org.eclipse.wst.server.core.internal.ServerPublishInfo.<init >(ServerPublishInfo.java:56) at org.eclipse.wst.server.core.internal.PublishInfo.getServerPu blishInfo(PublishInfo.java:75) at org.eclipse.wst.server.core.internal.Server.getServerPublish Info(Server.java:843) at org.eclipse.wst.server.core.internal.Server.doPublish(Server .java:886) at org.eclipse.wst.server.core.internal.Server.publish(Server.j ava:874) at org.eclipse.wst.server.core.internal.PublishServerJob.run(Pu blishServerJob.java:72)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web7618

  • Requested array size exceeds VM limit at org.eclipse.wst.server.core.internal.ModulePublishInfo.loadR esource(ModulePublishInfo.java:189) at org.eclipse.wst.server.core.internal.ModulePublishInfo.load( ModulePublishInfo.java:184) at
  • Requested array size exceeds VM limit at java.util.ArrayList.&lt;init&gt;(Unknown Source)
  • via nabble.com by Unknown author, 1 year ago
    Requested array size exceeds VM limit at org.postgresql.jdbc2.AbstractJdbc2Statement.setCharacterStream(AbstractJdbc2Statement.java:2881) at org.apache.ojb.broker.platforms.PlatformDefaultImpl.defaultSetClob(PlatformDefaultImpl.java:464) at
  • Stack trace

    • java.lang.OutOfMemoryError: Requested array size exceeds VM limit at org.eclipse.wst.server.core.internal.ModulePublishInfo.loadR esource(ModulePublishInfo.java:189) at org.eclipse.wst.server.core.internal.ModulePublishInfo.load( ModulePublishInfo.java:184) at org.eclipse.wst.server.core.internal.ModulePublishInfo.<init >(ModulePublishInfo.java:84) at org.eclipse.wst.server.core.internal.ServerPublishInfo.load( ServerPublishInfo.java:274) at org.eclipse.wst.server.core.internal.ServerPublishInfo.<init >(ServerPublishInfo.java:56) at org.eclipse.wst.server.core.internal.PublishInfo.getServerPu blishInfo(PublishInfo.java:75) at org.eclipse.wst.server.core.internal.Server.getServerPublish Info(Server.java:843) at org.eclipse.wst.server.core.internal.Server.doPublish(Server .java:886) at org.eclipse.wst.server.core.internal.Server.publish(Server.j ava:874) at org.eclipse.wst.server.core.internal.PublishServerJob.run(Pu blishServerJob.java:72) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.