[tallapureddy]

Hi Joy,

I tested this on ME7.5, even I got the same issue. As you said while running the while starting the WL with ant I have set the jvm argument as below. However, it didn’t help.

<!– Configure JMS for Weblogic –>
<target name=”_wls-jms-setup”>
<echo message=”Configure JMS…” />
<java classname=”weblogic.WLST” fork=”yes”>
<jvmarg value=”-XX:MaxPermSize=600m”/>
<jvmarg value=”-Xms256m”/>
<jvmarg value=”-Xmx900m”/>
<arg line=”-loadProperties ${tmp_propsFile} ./chrd_jms_creation.py” />

Let me know you suggestions to proceed on this further.

Thanks,
Naresh

[Loyal Water]

The arguments you have posted in your last post (the ant script) are the arguments used to launch WebLogic — and per your original post, it looks like Ant itself might be running out of memory:

=================
[java] WLST-WLS-1248692319957: <Jul 27, 2009 4:31:24 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID ‘1248692482208’ for task
=================

So again, you need to adjust the memory given to run the Ant script itself — not to run WebLogic.

(Screenshot inbound)

Attachments:

You must be logged in to view attached files.

[tallapureddy]

Hi Nipun,

The below error is not related to ANT OOM.

[java] WLST-WLS-1248692319957: <Jul 27, 2009 4:31:24 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID ‘1248692482208’ for task

While activating the Queues and topics in WebLogic it gives OOM. This only comes when I configure the WL with ME. I suspect something needs to be taken care in ME level.

Let me know your thoughts.

~Naresh

[Loyal Water]

Naresh,
There are only 3 memory pools to mess with:

1. MyEclipse VM Args (which you’ve’s tried)
2. Ant VM Args (which we tried to show you)
3. WebLogic VM Args (which you’ve tried)

I’m afraid I have no more suggestions for you. Maybe some other user on this forum could help you out.

[Author]

Posts