JAVA Heap Size Error in SAP Work Manager

We are getting the below error wrt Java Heap size in the SAP Work manager Application:
2014/08/08 00:48:56.142:setImportParameters::STORAGE_REF_KEY=ET_COMPLEX_TABLE
2014/08/08 00:48:56.143: + User=MAINTMGR
2014/08/08 00:48:56.143: execute::::MAINTMGR::before BAPI execute: /SMERP/MM_CTMATPLANT_GET
2014/08/08 00:55:20.905: + BackEnd=Java-1
2014/08/08 00:55:20.905: Exception while updating complex table 'ctpart': JavaBackEndError: JAVA EXCEPTION CAUGHT: java.lang.OutOfMemoryError: Java heap space in AgentryJavaComplexTableIterator::hasNext at AgentryJavaComplexTableIterator.cpp:52
2014/08/08 00:55:21.099: + Thread=6588
2014/08/08 00:55:21.099: + Thread Pool=Server
2014/08/08 00:55:21.099: + WorkFunction=00000000020DEF90
2014/08/08 00:55:21.099: + User=MAINTMGR
2014/08/08 00:55:21.099: + User=MAINTMGR
2014/08/08 00:55:21.099: Received Logout Request message 18 status changed to 'In Progress'
2014/08/08 00:55:21.105: Logged out (but not yet cleaned up)
We have tried to increase the initial and maximum heap size in the Agentry.ini file from 256 / 512 to 512 / 2048 respectively. But the
error still persists.
Can you please let us know if there are any
other changes required for
the same?
PFA the Java backend and the user
logs. Please treat this ticket with
the highest priority.
Thanks,
Boopalan

Looks like ur getting   heap size error while trying to fetch  records for ctparts complex table. From platform  point of view you have increased heap size. Next step is to analyze application settings for ctparts  complex table. As indicated by Steve from application point you need check the need for  amount of materials your trying to retrive , can you set filter for ctparts ,  does  ctparts  BAPI execute in SAP without any timeout error.
What is the version of Work Manager your using ?    With WM 6.1 you have options to  take advantage of data staging that is delievered as part of standard application.
Thanks
Manju.

Similar Messages

  • Java heap size error Work manager

    Hi,
      We are working with Work Manager 6.0 running on SMP 2.3 SP03.
    The application was working fine, but after the data load that has happened in the UAT
    System, we are getting the below error:
    2014/08/08 00:48:56.142:
    setImportParameters::STORAGE_REF_KEY=ET_COMPLEX_TABLE
    2014/08/08 00:48:56.143:               + User=TS_MAINTMGR
    2014/08/08 00:48:56.143:                 execute::::TS_MAINTMGR::before
    BAPI execute: /SMERP/MM_CTMATPLANT_GET
    2014/08/08 00:55:20.905:             + BackEnd=Java-1
    2014/08/08 00:55:20.905:               Exception while updating complex
    table 'ctpart': JavaBackEndError: JAVA EXCEPTION CAUGHT:
    java.lang.OutOfMemoryError: Java heap space in
    AgentryJavaComplexTableIterator::hasNext at
    AgentryJavaComplexTableIterator.cpp:52
    2014/08/08 00:55:21.099: + Thread=6588
    2014/08/08 00:55:21.099:   + Thread Pool=Server
    2014/08/08 00:55:21.099:     + WorkFunction=00000000020DEF90
    2014/08/08 00:55:21.099:       + User=TS_MAINTMGR
    2014/08/08 00:55:21.099:         + User=TS_MAINTMGR
    2014/08/08 00:55:21.099:           Received Logout Request message 18
    status changed to 'In Progress'
    2014/08/08 00:55:21.105:         Logged out (but not yet cleaned up)
    We tried to increase the min and max heap size from 256 / 512 to 512 /
    2048 respectively in Agentry.ini, but are still getting the same error.
    Please let us know if there is any other parameter which can be used to
    fine tune this and get this up and running,
    Thanks for the help.

    Raviraj,
    Are you working with Boopaln?  The reason why I as He posted the same error (in the same complex table) With the same changes but just a different user shown.
    If yes. please see that thread at:  JAVA Heap Size Error in SAP Work Manager

  • Java Heap Space error while reading from Excel

    Hello,
    I have a data flow which reads from excel and updates records in an oracle table.
    When the data flow tries to read the excel I get a java Heap space Error.
    Error preparing to read <SUPP_STG3_FILE1>: <Java heap space>.
    Data flow <DF_SUPP_STG3_UPD> is terminated due to error <58105>.
    I have configured Excel Adapter since the server is on UNIX. BOExcelAdapter shows status as red once the execution fails. Before that BOExcel adapter status is green.
    BOExcelAdapter Trace:
    1/13/12 10:57:38 PM Thread[Thread-6,5,main]      Received an error message from the message broker. [Communication failure. Read timed out]. Will exit adapter immediately.
    1/13/12 10:57:47 PM Thread[main,5,main]      Create broker client for life-cycle management. Host:port = hikalxboes01:4001
    1/13/12 10:57:47 PM Thread[main,5,main]      Create broker client for data exchange with ASP. Host:port = hikalxboes01:4001. Client ID = com.acta.adapter.msexceladapter.MSExcelAdapter.data_18
    1/13/12 10:57:47 PM Thread[Thread-11,5,main]      Create broker client for real-time services with ASP. Host:port = 'hikalxboes01:4000''.
    1/13/12 10:57:47 PM Thread[Thread-11,5,main]      Start instance [BOExcelAdapter] of adapter [com.acta.adapter.msexceladapter.MSExcelAdapter].
    1/13/12 10:57:47 PM Thread[Thread-11,5,main]      Register the client ID [com.acta.adapter.msexceladapter.MSExcelAdapter.data_18] and adapter destination [hikalxboes01:4001] with the adapter manager.
    1/13/12 10:57:47 PM Thread[Thread-11,5,main]      Registration complete.
    1/13/12 10:58:10 PM Thread[Thread-10,5,main]      java.lang.OutOfMemoryError: Java heap space
         at org.apache.poi.hssf.usermodel.HSSFRow.addCell(HSSFRow.java:273)
         at org.apache.poi.hssf.usermodel.HSSFRow.createCellFromRecord(HSSFRow.java:196)
         at org.apache.poi.hssf.usermodel.HSSFSheet.setPropertiesFromSheet(HSSFSheet.java:183)
         at org.apache.poi.hssf.usermodel.HSSFSheet.<init>(HSSFSheet.java:128)
         at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:283)
         at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:196)
         at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:178)
         at com.acta.adapter.msexceladapter.MSExcelAdapterReadTable.begin(MSExcelAdapterReadTable.java:537)
         at com.acta.adapter.sdk.StreamOperationWrapper.beginStream(StreamOperationWrapper.java:88)
         at com.acta.adapter.sdk.AdapterRunnerImpl.processBeginOperation(AdapterRunnerImpl.java:1762)
         at com.acta.adapter.sdk.AdapterServiceDataListener.handleBrokerMessage(AdapterServiceDataListener.java:90)
         at com.acta.brokerclient.BrokerClient.handleMessage(BrokerClient.java:439)
         at com.acta.brokerclient.BrokerClient.access$100(BrokerClient.java:53)
         at com.acta.brokerclient.BrokerClient$MessageHandler.run(BrokerClient.java:1621)
         at com.acta.brokerclient.ThreadPool$PoolThread.run(ThreadPool.java:100)
    BOExcelAdapter Error Log:
    1/13/12 10:58:10 PM      java.lang.OutOfMemoryError: Java heap space
         at org.apache.poi.hssf.usermodel.HSSFRow.addCell(HSSFRow.java:273)
         at org.apache.poi.hssf.usermodel.HSSFRow.createCellFromRecord(HSSFRow.java:196)
         at org.apache.poi.hssf.usermodel.HSSFSheet.setPropertiesFromSheet(HSSFSheet.java:183)
         at org.apache.poi.hssf.usermodel.HSSFSheet.<init>(HSSFSheet.java:128)
         at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:283)
         at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:196)
         at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:178)
         at com.acta.adapter.msexceladapter.MSExcelAdapterReadTable.begin(MSExcelAdapterReadTable.java:537)
         at com.acta.adapter.sdk.StreamOperationWrapper.beginStream(StreamOperationWrapper.java:88)
         at com.acta.adapter.sdk.AdapterRunnerImpl.processBeginOperation(AdapterRunnerImpl.java:1762)
         at com.acta.adapter.sdk.AdapterServiceDataListener.handleBrokerMessage(AdapterServiceDataListener.java:90)
         at com.acta.brokerclient.BrokerClient.handleMessage(BrokerClient.java:439)
         at com.acta.brokerclient.BrokerClient.access$100(BrokerClient.java:53)
         at com.acta.brokerclient.BrokerClient$MessageHandler.run(BrokerClient.java:1621)
         at com.acta.brokerclient.ThreadPool$PoolThread.run(ThreadPool.java:100)

    As Jay mentioned above it might be due to the size of the Excel spreadsheet as you might be hitting the limitation in Apache POI library used for adapter.
    What is the size of the Excel file?
    What is the value of -Xmx parameter - see DS Management Console > Adapter configuration page.
    Thank you,
    Viacheslav.

  • SAP Work Manager status STOPPED in SCC

    Hi All,
    We have installed and deployed SAP Work Manager 6.0 on SMP 2.3. In the SCC it shows the app was registered or started successfully, however the Agentry instance server status is STOPPED. The Task Manager shows the Agentry Server is running, and can actually accessed from ATE.
    The problem is we can't see anything in any of the other tabs. The tab Configurations is blank and we are not able to see or maintain any settings and/or parameters. The other tabs are also blank, for example Logs is not pulling in the data from the log files. See screenshots below.
    The startup.log is also noit giving me any indications or errors. See also below.
    Any suggestions as to what might be wrong? And how this can be resolved?
    Kind regards,
    Edwin
    STARTUP.LOG
    09:16:47 03/27/2014: Starting server (64-bit Windows)
    09:16:48 03/27/2014: Administration client command port is 60880, status port is 60881
    09:16:48 03/27/2014: Looking for initial status connection...
    09:16:58 03/27/2014: Event: 0, 2, Status connection not detected.  Continuing startup
    09:16:58 03/27/2014: Reading system ini file.
    09:16:58 03/27/2014: ID: SAP Work Manager Server v6.0.0.0, Name: ???, Location: ???
    09:16:58 03/27/2014: Starting log file.
    09:16:58 03/27/2014: Loading message groups.
    09:16:58 03/27/2014: Starting threads.
    09:16:58 03/27/2014:    1 initial threads.  Threads will auto-scale.
    09:16:58 03/27/2014: Starting Server: Agentry v6.1.3.10212
    09:16:58 03/27/2014: Event: 0, 2, System Startup
    09:16:58 03/27/2014: Loading 1 front ends
    09:16:58 03/27/2014: Loading front end from angelvine.dll
    09:16:58 03/27/2014: ANGEL Front End: reading init files.
    09:16:58 03/27/2014: Event: 17, 14, ANGEL Front End v6.1.3.10212
    09:16:58 03/27/2014: Event: 0, 2, Loading the Agentry Server's public/private key for password exchanges.
    09:16:58 03/27/2014: Event: 0, 2, Key pair loaded successfully.
    09:16:58 03/27/2014: Starting Server Agent.
    09:16:58 03/27/2014: Agentry: Starting threads.
    09:16:58 03/27/2014:    1 initial threads.  Threads will auto-scale.
    09:16:58 03/27/2014: Agentry: Adding messages.
    09:16:58 03/27/2014: Event: 1, 4, Agentry v6.1.3.10212
    09:16:58 03/27/2014: Loading 1 agents
    09:16:58 03/27/2014: Loading agent from ag3.dll
    09:16:59 03/27/2014: Starting Server
    09:16:59 03/27/2014: Server: reading ini file
    09:17:00 03/27/2014: Initializing 2-HTTPXML from ag3httpxmlbe.dll
    09:17:00 03/27/2014: SystemConnection-2: Reading configuration information.
    09:17:00 03/27/2014: SystemConnection-2: Setting name to 'HTTP-XML Back End'.
    09:17:00 03/27/2014: HTTP-XML Back End: Initialized.
    09:17:00 03/27/2014: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v6.1.3.10212) from ag3httpxmlbe.dll
    09:17:00 03/27/2014: Initializing 1-Java from ag3javabe.dll
    09:17:00 03/27/2014: SystemConnection-1: Reading configuration information.
    09:17:00 03/27/2014: SystemConnection-1: Setting name to 'Java Back End'.
    09:17:00 03/27/2014: Java Back End: Initialized.
    09:17:02 03/27/2014: Java Back End: Java Virtual Machine loaded.
    09:17:07 03/27/2014: Java Back End: Java Back End AJAPI version 5.0, release 6.1.3.10200
    09:17:07 03/27/2014: Event: 23, 101, Java Back End: AJAPI JAR version 6.1.3.10200 does not match the version of the Agentry Server
    09:17:07 03/27/2014: Java Back End: Initialized.
    09:17:07 03/27/2014: Event: 23, 4, Loaded Java Back End (Java v6.1.3.10212 (JVM version 1.6.0_35, AJAPI version 5.0 build 6.1.3.10200)) from ag3javabe.dll
    09:17:07 03/27/2014: Event: 20, 150, Loading Production application definitions using file "SAPWM-v1-0-0-app"
    09:17:07 03/27/2014: Event: 20, 152, Loading Production application definitions for default localization
    09:17:18 03/27/2014: Event: 20, 153, Finished loading Production application definitions for default localization
    09:17:18 03/27/2014: Event: 20, 151, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
    09:17:18 03/27/2014: HTTP-XML Back End Back End: Started
    09:17:18 03/27/2014: Server: Starting threads.
    09:17:18 03/27/2014:    1 initial threads.  Threads will auto-scale.
    09:17:19 03/27/2014: Event: 20, 4, Server v6.1.3.10212
    09:17:19 03/27/2014: Starting front ends
    09:17:19 03/27/2014: ANGEL Front End: Starting threads.
    09:17:19 03/27/2014:    3 initial threads.  Threads will auto-scale.
    09:17:19 03/27/2014: ANGEL Front End: opening listen socket on port 7003
    09:17:19 03/27/2014: Event: 17, 10, 0.0.0.0:7003 open
    09:17:19 03/27/2014: Event: 17, 10, ANGEL Front End v6.1.3.10212
    09:17:19 03/27/2014: Event: 0, 0, Old log files moved into E:\SAP\MobilePlatform\Servers\UnwiredServer\logs\com.sap.wm\Rolled\2014-03-27-091647
    09:17:19 03/27/2014: Event: 0, 23, SAP Mobile Platform
    09:17:19 03/27/2014: Event: 0, 2, Server startup is complete.
    09:17:19 03/27/2014: Agentry Application startup complete

    Hi Stephen,
    We installed SP04, but we are still experiencing the same issue. We even went as far as deleting and re-deploying the app.
    Again it shows the app registered successfully:
    On the General tab it still shows status STOPPED:
    The other tabs don't show anything, e.g. Configurations or Logs:
    After restarting SMP the node completely disappears:
    The Region & Language settings on the SMP server:
    Any further suggestions are much appreciated.
    Regards,
    Edwin

  • Java.lang.OutOfMemoryError:class Your Java heap size might be set too high.

    I am getting the below error while deploying some soa applications in WLS 10.3 on solaris platform.As a workaround,
    the server instance has to be restarted everytime i make the deployments when i face this OOM situations.
    usually i face this issue after first deployment onwards.
    So, everytime i make the next deployment the server instance has to be restarted before that.
    The server is configured with 1Gb JVM and runs on JRockit jrrt-4.0.0-1.6.0.
    MEM_ARGS="-Xms1g -Xmx1g -Xgcprio:throughput -Xverbose:gc -XX:+HeapDumpOnOutO
    fMemoryError -XXcompressedRefs:enable=true"
    Can anybody please provide any pointers to track/solve this issue?
    Log extract:
    ####<Oct 10, 2010 4:27:31 PM PST> <Error> <Deployer> <BOX1> <SERVER2> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1256893524756> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1256893524756' for task '3'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:118)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:205)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.lang.OutOfMemoryError: class allocation, 21977184 loaded, 20M footprint in check_alloc (classalloc.c:213) 1412 bytes requested.
    Java heap 1G reserved, 1G committed
    Paged memory=18014398507524232K/16781304K.
    Your Java heap size might be set too high.
    Try to reduce the Java heap
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:335)
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:288)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176)
    at java.lang.Class.getDeclaredConstructors0(Native Method)
    at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
    at java.lang.Class.getConstructor0(Class.java:2699)
    at java.lang.Class.newInstance0(Class.java:326)
    at java.lang.Class.newInstance(Class.java:308)
    at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:1058)
    at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:1129)
    at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:542)
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:435)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    Its running on Solaris 10 platform.The server is configured with 1Gb JVM and JRockit jrrt-4.0.0-1.6.0.
    MEM_ARGS="-Xms1g -Xmx1g -Xgcprio:throughput -Xverbose:gc -XX:+HeapDumpOnOutO
    fMemoryError -XXcompressedRefs:enable=true"
    Let me know if you need any more information to track this issue.

  • Extending java heap size

    hi,
    In message mapping  iam importing the ED for target field at that time it tells java heap size is extended. so using repository.jnlp
    i extended the memory.
    But still i can't upload the ED.
    could u plz suggest wht to do in that..
    it is urgent plz do needful...
    regards
    sasi

    Hi Sk
    follow these link to understand java heaap and its solution for extending size
    Java heap: Java objects belonging to a VM are stored on the Java heap. Each VM has its own Java heap, and other VMs cannot access them.
    Memory Management in the VM Container
    http://help.sap.com/saphelp_nw04s/helpdata/en/3b/88d863ff72456aa61e993831a76614/frameset.htm
    Note 667841 - J2EE Engine 6.20 on AIX: how to increase the heap size
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=667841
    Note 667711 - Max. JVM Heap Size for AIX JDK 1.3.1
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=667711
    Regards
    sandeep
    if helpful reward points

  • Java Heap Space Error in BI Publisher

    Hi,
    I have an issue with BIP reports.
    My report is working fine in development instance as it has very less data.
    But the same report is throwing "Java Heap Space" error in another instance which is having huge amount of data.
    I tried to modify the oc4j.cmd file by increasing the values -XX:MaxPermSize=128m -Xmx1024m.
    After restarting the oc4j serivices,my OBIEE and BIP URL's becomes dead slow.
    Is there any solution to improve the performance (or) is there any other way to resolve this issue.
    I am running on
    OBIEE 10.1.3.4.2.
    oc4j Server
    Windows box.
    Thanks in advance.
    Pramod.

    Changing os's may help, or it may not. Java requires contiguous memory addresses for the heap, and that varies with the os, os parameters, what has previously been loaded into memory, and how much physical memory is available. The heap can't be assigned to the os's swap space; the os handles paging in and out of memory. All modern os's provide paging to disk.

  • While generating the huge report getting Java Heap Space Error

    Hi All,
    We are using XML Publisher 5.6.2. we have to generate the huge report which contains more than 300 sql statements. Since our schema structure we can not reduce the queries. Now we are facing issue while generating the report. It takes lot of time and gives 'java heap space error'. We are using data template and RTF template for generating excel report.
    Can anybody help me to resolve the issue? or is there any other way to generate the huge reports?
    Thanks,

    Hi,
    I had seen the forum, but we had already adjusted the parameters in the oc4j "-XX:MaxPermSize=128m -Xmx512m" values to 4096. but still we are getting the java heap space error. since we increased the size of xmx value, XML Publisher occupies 61% of memory of the server. B'coz of this our other applications are getting affected.
    and also, since we are using XML Publisher 5.6.2, can you please assist us how to set the scalable property to 'true'.
    Thanks,
    Ramya.
    Edited by: user753355 on Aug 12, 2009 3:35 AM

  • On Demand attachment download issue in SAP Work Manager 6.0

    We are using SAP Work Manager 6.0 app with SMP 2.3. System is configured to download attachments for external DMS using this document http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90087094-ddad-3110-cdab-e6dbc1a12e45?QuickLink=index&overridelayout=true&59236188953046
    While we tried to download the attachment, the download request was sent to SAP
    We checked through Push Instance monitor in Syclo Admin panel, a push request was there for scenario ID SM60_DMS_DOCUMENT_PUSH with status PROCESS. Status was set to NEW under Subscriber view tab of this push request.
    We checked following things:
    1. Push was enabled for Agentry Server in JavaBE.ini
    2.  Port 8282 was maintained in outbound trigger settings & in Agentry.ini configurations. This port is only used by Agentry Server.
    3. SCC displays the error for the WorkManager application as XFailedToSendResponse: 9,1,16, smp_mobile
    Regards,
    Sahil Dudeja
    Tags edited by: Michael Appleby

    We are still facing this issue.

  • Java Heap Space Error

    Hi,
    We are running SAP MII 12.0 on windows server 2003 SP1 installed on a virtual machine with 4GB RAM, Intel Xenon CPU E5504 @ 2.00 GHz.
    We started getting the Java Heap Space Error while executing a transaction which fetches about 200 rows. But now the error is quiet frequent and appears while trying to open or close the transactions or save trying to save data.
    I have edited the heap space in the config tool to 2048 but this has not helped. Not sure if this is of significance but the SAP R3 server being used is quiet slow and takes about 3 mins to return data when I run the BAPI on it. This resulted in the transaction timing out a few times before we started getting the error. Increasing the connection timeout and read timeout for the transaction has not helped.
    Please help me resolve this
    Thanks
    Maaz Ahmed

    The BAPI being used is BAPI_GOODSMVT_GETITEMS I am specifying the Material, Plant, Goods Mvt ranges, and a date range.
    I was informed that the QA R3 system is not among the best servers and the speeds would be better in production (under 3s).
    Also I have been looking at the sapmmc. Each time I restart the cluster or the server I get a series of messages or alerts. In these alerts I see a series (Content, Navigation, PRT, etc..) of health checks failing. And the last two errors are as below
    Object - Common Information
    Attribute - Failed to Start Application
    Description - 2 appl > 1 appl last reported value above threshold.
    and
    Object - Common Information
    Attribute - Failed to Start Application
    Description - 1 appl > 0 appl last reported value above threshold.
    I am able to launch the menu page after this and when i run the above mantioned BAPI I get the error
    Object - Memory Info
    Attribute - Usage Rate
    Description - 81% > 80% last reported value above threshold

  • Flash Builder 4.5 Java Heap Space Error

    Hello everyone,
    I've downloaded Flash Builder 4.5 trial a few days ago. Let me first tell that I like the new features a lot and they help to speed up the development process noticably. I thank Adobe for that very much.
    However I did not notice any performance boost over the Flash Buidler 4. Even worse, the 4.5 version seems to run much slower and use more memory than Flash Builder 4. I constantly keep getting Java Heap Space errors and needles to say, the tool just crashes and I have to restart it.
    Here how my experience working with the new version looks like. I start the Flash Builder 4.5 which has my current project open (for the record, I still use Flex 4.1, and the project includes roughly 300+ classes and 30000+ lines of code (AS and MXML)). At the beggining everything works fine and pretty fast. UI, code completion, snippets and all other good stuff works pretty fast. However, after each build, FlashBuilder.exe process eats up from 50 to 100 megabytes of memory and does not seem to release it or reuse it. So after a 5 or 10 builds it already appears to be using over 1 GB of RAM. At that point the editor becomes sloppy - it can't keep up with my typing, code completion popups takes a few seconds to show up. And a few more builds - the Flash Builder freezes and after a minute or two I get Java Heap Space error.
    I've tried increased the JRE heap space used by the Flash Builder (flashbuilder.ini, flashbuilderc.ini, eclipse.ini) to -Xms512m -Xmx1024m as well as permanent generation heap space to -XX:MaxPermSize=512m -XX:PermSize=256m and the mxml compiler (jvm.config) to -Xms384m -Xmx768m. However this did not solve the problem. Maybe just postponed it a bit.
    Am I the only one observing such behaviour of Flash Builder 4.5? Does any one have any other ideas how to fix this? (by the way, I work on 64bit machine with Widnows Server 2008R2, 4GB of RAM and 2.66 GHz Intel Core 2 Duo).
    Thanks in advance.
    Michael

    I'm seeing nearly the same thing.  I also have a very large set of projects similar to what you are describing and I do have Java Heap Space errors (The details show an error of "java.lang.OutOfMemoryError: unable to create new native thread" occurring for me)
    I had similar issues, although they are more frequent in the 4.5 builder, in the 4.1 builder.  In 4.1 builder, I didn't get the exact same detailed error regarding threads.
    I did install my flash builder into a clean instance of eclipse 3.6.2 vs using the standalone install.  That shouldn't make a difference though.  In 4.1, I tried he standalone install and saw the same issues I saw in the plugin version.
    I'm also using the 4.1 SDK in Flash Builder 4.5 (It appears that is what you are doing).  I've been attributing the crashes to the following bug in the 4.1 SDK, although I have applied the files in the bug report and still have the problem.  I'm hoping when I'm able to switch to the 4.5 SDK it may help.  (I can't switch yet because from what I can tell, it requires 10.2 Flash Player and my company is currently only on 10.0)
    The Bug Report I'm referring to is: https://bugs.adobe.com/jira/browse/SDK-26366
    I've bumped up all of the memory settings you've referred to and it helps the environment run longer, but it still eventually crashes.  One thing I definately do is make sure that the "Build Automatically" is unchecked.
    The machine I'm running on is an Intel 2600K with 16GB of memory running Windows 7 64-bit, so I don't think hardware is the issue.
    No real answer, but your not alone in having similar issues.
    Jon

  • SMP SAP Work Manager 6.1 multi language

    Hi all,
    we have installed SMP 3.0 SP5 with SAP Work Manager 6.1. We would like to use multi-language functionality but field labels do not translate after our configuration changes.
    We have created "localization" folder under "server\configuration\com.sap.mobile.platform.server.agentry.application\Application\Development" path and copy new ini files from language pack.
    We modify the configuration property as follows:
    Localization Path = Application\Development\localization
    Localizations= it
    In the startup server log seems no error occurs and translation file are loaded successfully.
    Thank you.
    Regards,
    Paolo
    Tags edited by: Jitendra Kansal (Moderator)

    Hi Stephen,
    our SMP system returned available so I copy dei multi language file of "it" country under the path that you have suggested.
    When I synchronize from the agentry client seems that connection does not end successfully. In particular in the log file I found the new italian label but the synch is very slow about 2 hours.
    What do you think about it?
    Thanks,
    Paolo

  • Java.lang.OutOfMemoryError: Java heap space error

    Hello All,
    We are on SOA 10g (10.1.3.5) and are facing java heap memory error intermittently. We have already beefed up the memory to 1024MB and have implemented separate module-wise domain on the SOA server ex: PTP,DTD etc.
    The error is thrown ecen when data volume is very low << 7MB in size.
    Following is the excerpt from the opmn.xml file.
    <process-type id="oc4j_soa" module-id="OC4J" status="enabled">
    <module-data>
    <category id="start-parameters">
    <data id="java-options" value="-server *-Xms1024m -Xmx1024m* -Djava.security.policy=$ORACLE_HOME/j2ee/oc4j_soa/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false *-XX:MaxPermSize=256M* -Doraesb.home=/u01/app/oracle/soaprd2/product/app/integration/esb -Dhttp.proxySet=false -Doc4j.userThreads=true -Doracle.mdb.fastUndeploy=60 -Doc4j.formauth.redirect=true -Djava.net.preferIPv4Stack=true -Dorabpel.home=/u01/app/oracle/soaprd2/product/app/bpel -Xbootclasspath^/p:/u01/app/oracle/soaprd2/product/app/bpel/lib/orabpel-boot.jar -Dhttp.proxySet=false"/>
    </category>
    <category id="stop-parameters">
    <data id="java-options" value="-Djava.security.policy=$ORACLE_HOME/j2ee/oc4j_soa/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false"/>
    </category>
    </module-data>
    Can anyone please point out what could go wrong here..
    Thanks,
    Rahul.

    Thanks All..We were able to resolve this issue by tuning the query that SOA used via the DB adapter to poll and select the data set from the custom staging tables. Still, we are thinking of increasing the memory to 2 Gigs.
    Can anyone point out what is the ideal settings for a high transaction environment on SOA 10g (10.1.3.5) for the following..
    -Xms1024m
    -Xmx2048m
    - XX:MaxPermSize=512M
    Thanks,
    Rahul

  • How to increase Memory and Java Heap Size for Content Server

    Hi,
    My content server is processing requests very slowly. Over performance is not good. I have 2 GB of RAM any idea what files I can modify to increase the Java Heap Size for the Content Server. If I increase the RAM to 4 or 6 GB where do I need to make changes for the Java Heap Size and what are the recommended values. I just have Content Server Running on the linux box. Or how do I assign more memory to the user that owns the content server install.
    Thanks

    You might find these interesting:
    http://blogs.oracle.com/fusionecm/2008/10/how_to_-javatuning.html
    http://download.oracle.com/docs/cd/E10316_01/cs/cs_doc_10/documentation/admin/performance_tuning_10en.pdf
    Do you have access to metalink? This has about everything you could want:
    https://metalink2.oracle.com/metalink/plsql/f?p=130:14:9940589543422282072::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,788210.1,1,1,1,helvetica
    Or search for "788210.1" in metalink knowledgebase if that link doesn't work and look for the FAQ on configuring Java for Content Servers

  • How to increase the Java Heap size ?

    Hi
    I am new to java. I have created a java application and i configured in Eclipse. While running my application it throws an error that
    "Exception in thread "Thread-21" java.lang.OutOfMemoryError: Java heap space"
    i have used threads in my application. Then i searched some forums regarding this. The answer i got is "Increase the java heap size" using
    "java -Xms64m -Xmx256m prog" in command prompt. while running.
    But i am not running my application in command prompt. I used Eclipse to run my application. Here my ultimate question is how to set the heap size while running the application in Eclipse and where to set in Eclipse.
    Kindly help me.
    Regards
    Ramesh E

    i have used 20 threads to extract the datas
    Then parallel i am starting one more thread to process the data. Means that i am starting 21st thread. In thread is throwing the error.
    20 threads:
    for (int i = 0; i < 20; i++) {
    try{
    extrThreads[i] = new Thread(this);
    extrThreads.start();
    }catch (Exception e) {
    System.out.println(e);
    21st Thread:
    public void processdata()throws Exception{
    Thread t = new Thread(this);
    t.start();
    if(t!= null)
    t.join();
    funtion();
    This thread is throwing the error

Maybe you are looking for

  • Problem running Java GUI apps in Linux

    When launching GUI Java apps a blank window with only a title appears and nothing more happens. Have no idea of how to deal with it.. pvs@pvs-laptop:~$ uname -a Linux pvs-laptop 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux pvs

  • Apple Remote Desktop Setup for Exernal Networks

    Hi there , i would like to setup apple remote desktop 3 in the office to control 6 Macs ( external Networks ) in 6 different places via Internet . Do i need to buy a server or would it be enough to buy a Mac Pro - which setup would i need . stefan

  • Send Message Process prompting for "Process Chain to Check"

    Hi, When I insert a "Send Message" Process into my chain I do get prompted to select the message.  1. When I do a pull down I am getting prompted for "Process Chain to Check".  If I select my current process chain I get an abend. 2. When I click crea

  • Interface confusion

    Hi. I posted this topic yesterday, but somehow it didn't appear on the forum. So, here it is again... I'm confused about some interface issues. If I understood correctlty, interfaces are classes whose methods have no implementation, so it's up on a u

  • Archiving old data from a partitioned table

    Hi, While sifting through all the options for archiving the old data from a table which is also indexed, i came across a few methods which could be used: 1. Use a CTAS to create new tables on a different tablespace from the partitions on the exisitng