Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
StevenB77 Super Contributor.
Super Contributor.
1117 views

Java Heap Space errors on web service calls on attachments...

We have developers trying to send attachments that are larger than 20MB and they keep getting the message below when this limit is exceeded. When creating attachments that are greater than 20MB through the web-tier this issue does not occur. 

I have tried localizing the traffic to a single thread/sevrlet with min and max memory settings set to 512 and 1024 respectively. This did not help in resolving the "Out of Memory" errors. 

Any assistance that you could provide would be grealty appreciated. 

10140( 9336) 01/29/2018 14:03:58

java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:3236)
at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:118)
at java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:153)
at com.sun.org.apache.xml.internal.serializer.WriterToUTF8Buffered.flushBuffer(WriterToUTF8Buffered.java:482)
at com.sun.org.apache.xml.internal.serializer.WriterToUTF8Buffered.write(WriterToUTF8Buffered.java:226)
at com.sun.org.apache.xml.internal.serializer.WriterToUTF8Buffered.write(WriterToUTF8Buffered.java:279)
at com.sun.org.apache.xml.internal.serializer.ToStream.characters(ToStream.java:1535)
at com.sun.org.apache.xml.internal.serializer.ToStream.characters(ToStream.java:1649)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:276)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:262)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:262)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:262)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:262)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:262)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:262)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:262)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java:126)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transformIdentity(TransformerImpl.java:697)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:743)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:349)
at com.hp.ov.sm.common.util.DOMSerializer.DOM2String(DOMSerializer.java:52)
at com.hp.ov.sm.server.utility.ServletUtility.writeSoapPart(ServletUtility.java:1270)
at com.hp.ov.sm.server.utility.ServletUtility.logSoapMessage(ServletUtility.java:1369)
at com.hp.ov.sm.server.utility.SoapServer.createXMLDocAndAttachment(SoapServer.java:1128)
at com.hp.ov.sm.server.utility.SoapServer.buildRequest(SoapServer.java:188)
at com.hp.ov.sm.server.utility.SoapServer.passRequestToWorkerThread(SoapServer.java:171)
at com.hp.ov.sm.server.utility.SoapServer.handleSoapRequest(SoapServer.java:768)
at com.hp.ov.sm.server.appserver.servlet.Servlet.doPost(Servlet.java:223)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)
10140( 7808) 01/29/2018 14:05:26 RTE I Idle login session has been marked for termination

 It also appears that by this knowledge document that this is not a best practice for identifying the Java Heap Space issue defined above.

SM: Development recommendations for Java heap/memory - , servicecenter - technical_documents - Micro Focus Software Support

Title :
SM: Development recommendations for Java heap/memory
Document ID :
KM995452
Product - Version:
service manager ; servicecenter ;
OS :
 
Updated :
2017-Jan-27
Summary :
Development recommendations for Java heap/memory
 
 
 
Our teams have seen a number of Service Manager (SM) server issues related to ill-advised recommendations regarding Java heap settings. This appears to be due to a number of incorrect KM articles and general lack of knowledge in this area. The over-arching theme appears to be that larger heap settings lead to enhanced performance, which is false in most scenarios.
 
This document aims to clarify this topic and set the proper policy going forward.
Solution
 
1. In general, support shouldn't automatically suggest an increase to the default Xms and Xms settings for SM without first understanding the underlying root-cause of the issue. Increasing these default settings may have a positive impact short-term, but in the long-run causes more issues. Keep in mind that the SM server is not a pure Java application and other memory considerations are required.
 
2. When troubleshooting java.lang.OutOfMemoryError messages, please ensure that the following JVM option is enabled in the sm.ini:
 
This allows the JVM running the SM servlet to generate a diagnostic Java heap dump (HPROF or PHD (on AIX)) file which can be analyzed by our teams to determine root cause. Newer versions of SM will include additional diagnostic information when a java.lang.OutOfMemoryError is thrown, so when sending in a Java heap dump for analysis, please ensure the relevant sm.log and Process*.log files have been included. This is a standard Java parameter useful in troubleshooting these errors and has no significant performance overhead associated with leaving it enabled indefinitely.
 
JVMOptionN:-XX:+HeapDumpOnOutOfMemoryError
Where N = 1 or higher depending on pre-existing options.
 
 
3. As a hard and fast rule, never set Xmx values greater than 512MB. As such, even 512MB is likely too large a value. These large values take away from the native (non Java related) memory required by SM to run correctly. In addition, as a secondary rule, it is always recommended to be on the latest patch available as there are continuous server resiliency, performance, and memory improvements.
 
4. The threadsperprocess values specified in sm.ini file has a direct impact on memory usage as well. Please be aware that the default value of 50 is typically sufficient in Windows platform deployments. On Unix and Windows 64-bit platforms, the default value can be set to 70 without any cause for concern. This is because the memory management models on these platforms allows for larger values without negative impact to SM performance. Please note that threadsperprocess can also be set higher than 50 for SM servlets that are dedicated to hosting ONLY Web Services transactions. This is because WS transactions do not have the typical overhead associated with SM GUI clients.
Labels (1)
0 Likes
12 Replies
Carlos_V_SM Acclaimed Contributor.
Acclaimed Contributor.

Re: Java Heap Space errors on web service calls on attachments...

Hi Steven,

Hope you are doing fine.

Could you please share the sm.ini in order to take a look?

In addition, what kind / format files are you trying to attach?

Carlos Villalobos R
Customer Support Engineer
If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
StevenB77 Super Contributor.
Super Contributor.

Re: Java Heap Space errors on web service calls on attachments...

Hi Carlos, 

It doesn't matter what file type.  If the attachment payload is larger than 20MB the Java Heap error is displayed in the log. I have attached the contents of the sm.ini file below. 

#smmasterkey is generated by SM automatically. Don't change it manually. Otherwise SM might fail to start.
smmasterkey:534152F94805E4E4300B811D7CA77CD42F909AC2431F43A7D335FFD8ECD60D030484606A
# BOF
# ServiceManager Initialization file
# (c) Copyright 2008 Hewlett-Packard Development Company, L.P.
# Configuration Modified Date:03/06/2015 2:00 PM
# Configuration Modified By: 

#################################################################################################################
## ##
## Line 14 is the parameter that specifies the IP address when requesting a license from Autopass. ##
## The value of the "grouplicenseip" parameter should be "10.12.210.23" in the PROD environment. ##
## Line 15 is the parameter that specifies the IP address to bind to because this VM has 3 NICs. ##
#################################################################################################################

grouplicenseip:10.12.210.23
groupbindaddress:10.12.210.23
maxKeepAliveRequests:3
groupname:SM934LBGROUP
groupmcastaddress:224.0.1.53
groupsubnetaddress:255.255.255.192
groupport:13180

#################################################################################################################
## ##
## Line 32 is the parameter that specifies the value for the size of Shared Memory. ##
## The value of the "shared_memory" parameter should be "256000000" in the QA environment. ##
## ##
## Line 33 is the parameter that specifies the value for the Cache Clean Interval ##
## This parameter defines the interval the HPSM server waits before clearing the cache of infrequently used ##
## entries. ##
#################################################################################################################

shared_memory:512000000
cache_clean_interval:2400

#################################################################################################################
## ##
## Lines 44 through 46 are the parameters that specifies the following: ##
## (1). The "log" parameter stores the location path and name of the log file (Line 44) ##
## (2). The "numberoflogfiles" parameter stores the number of log files to keep before overwriting (Line 45)##
## (3). The "maxlogsize" parameter stores the size of the log file before rolling to the next file (Line 46)##
## ##
#################################################################################################################

log:D:/logs/sm.log
numberoflogfiles:7
maxlogsize:33554432

#################################################################################################################
## ##
## Lines 54 and 55 are responsible for setting the SQL and HPSM Server time zones ##
## ##
#################################################################################################################

sqltz:US/Eastern
servertz:US/Eastern

#################################################################################################################
## ##
## Lines 63 and 64 specify https port # and SQL database type ##
## ##
#################################################################################################################

httpsPort:13443
sqldictionary:sqlserver

##################################################################################################################################
## ##
## Lines 76 through 79 are parameters that specify the database properties for HP Service Manager. ##
## Line 76 is a section header that specifies the Microsoft SQL Server Database. ##
## Line 77 is the parameter that stores the name of the SQL Server database for HPSM. ##
## Line 78 is the parameter that stores user name and password used by the HPSM application to login to the SQL Server database.##
## Line 79 is the parameter that stores the DLL file responsible for the KM Search Engine. ##
## ##
##################################################################################################################################

[sqlserver]
sqldb:hpServiceManager
*sqllogin:FGFGF518C62FCAF40F9562FFA8690DBD93F89D02C206033A1EBD98F8E06324232617A37C99548067A2B86DEF492F315EF148GFGF
plugin0:kmplugin.dll

##################################################################################################################################
## ##
## Lines 91 through 93 are parameters that specify Information Retrieval (IR) Expert Parameters ##
## Line 91, ir_max_relevant_answers, sets the maximum number of relevant records an IR search can return. ##
## Line 92, ir_term_drop_off, sets the maximum percentage frequency that search terms and have in the IR index for SM to ##
## include them in search results. ##
## Line 93, ir_sql_limit, sets the maximum number of records to fetch from the RDBMS in a combined IR and SQL query. ##
## ##
##################################################################################################################################

ir_max_relevant_answers:200
ir_term_drop_off:75
ir_sql_limit:65534
ir_asynchronous:1

#########################################################################################################################################
## ##
## Lines 106 through 108 are parameters that specify specific startup parameters ##
## Line 106, threadsperprocess, sets the maximum number of threads that you want the HPSM server to start when it starts a new process.##
## Line 107, sessiontimeout, sets the number of minutes that the server waits for a client heartbeat signal before the server assumes ##
## that the client session has timed out and closes the connection. ##
## Line 108, heartbeatinterval, controls the CLIENT heartbeat frequency. If the server does not receive a heartbeat from the client ##
## within the time-out limit as defined by the sessiontimeout parameter, the server terminates the client. All unsaved data ##
## is lost and the client must establish a new connection. ##
#########################################################################################################################################

threadsperprocess:42
sessiontimeout:180
heartbeatinterval:30

 

########################################################################################################################################
## ##
## Lines 128 through 140 are parameters that specify LDAP information related to HPSM. ##
## Line 128, ldapbinddn, sets the name the HPSM server uses to bind to the LDAP server. ##
## Line 129, ldapbindpass, sets the password the HPSM server uses to bind to the LDAP server. ##
## Line 130, ldapauthenticateonly, boolean value that requires the HPSM server to use LDAP for login authentication only. ##
## Line 131, ldapnostrictlogin, boolean value that allows users with valid operator records to log into HPSM without also ##
## having a valid LDAP record. ##
## Line 132, ldapmaxrecords, specifies the maximum number of records to return from an LDAP query. ##
## Line 133, ldapdisable, boolean value that disables the LDAP login authentication procedure. ##
## Line 134, ldapserver1, sets the backup LDAP servers that the HPSM server can connect to if the primary LDAP server is unavailable. ##
## Line 135, ldapserver2, sets the backup LDAP servers that the HPSM server can connect to if the primary LDAP server is unavailable. ##
## Line 136, ldapserver3, sets the backup LDAP servers that the HPSM server can connect to if the primary LDAP server is unavailable. ##
## Line 137, ldapserver4, sets the backup LDAP servers that the HPSM server can connect to if the primary LDAP server is unavailable. ##
## Line 138, ldapserver5, sets the backup LDAP servers that the HPSM server can connect to if the primary LDAP server is unavailable. ##
## Line 139, ldapserver6, sets the backup LDAP servers that the HPSM server can connect to if the primary LDAP server is unavailable. ##
## Line 140, ldapserver7, sets the backup LDAP servers that the HPSM server can connect to if the primary LDAP server is unavailable. ##
########################################################################################################################################
ldapbinddn:cn=sysvcmgr,ou=service accounts,dc=nscorp,dc=ad,dc=nscorp,dc=com
*ldapbindpass:FGFG262D0D3D322848629AA48D451014417BB1B032E5CD57026E09B32DE8C84C856FGFGF
ldapauthenticateonly:1
ldapnostrictlogin:1
ldapmaxrecords:1000
ldapdisable:0
ldapserver1:nscorp.ad.nscorp.com%3269%cn=sysvcmgr,dc=ad,dc=nscorp,dc=com%C:\LDAPPEM\trusted.certs.pem
ldapserver2:nscorp.ad.nscorp.com%3269%cn=sysvcmgr,dc=ad,dc=nscorp,dc=com%C:\LDAPPEM\trusted.certs.pem
#ldapserver3:gatucitadns06s.nscorp.ad.nscorp.com,3269,"cn=sysvcmgr,dc=ad,dc=nscorp,dc=com",C:\LDAPPEM\trusted.certs.pem
ldapserver3:gatucitadns09s.nscorp.ad.nscorp.com%3269%cn=sysvcmgr,dc=ad,dc=nscorp,dc=com%C:\LDAPPEM\trusted.certs.pem
ldapserver4:gaatlitadns09s.nscorp.ad.nscorp.com%3269%cn=sysvcmgr,dc=ad,dc=nscorp,dc=com%C:\LDAPPEM\trusted.certs.pem
ldapserver5:gatucitadns08s.nscorp.ad.nscorp.com%3269%cn=sysvcmgr,dc=ad,dc=nscorp,dc=com%C:\LDAPPEM\trusted.certs.pem
ldapserver6:gaatlitadns08s.nscorp.ad.nscorp.com%3269%cn=sysvcmgr,dc=ad,dc=nscorp,dc=com%C:\LDAPPEM\trusted.certs.pem

#######################################################################################################################################
## ##
## Line 154, msg_buffer_size, sets the size (in bytes) of the MSG Buffer that is used to store the current notification message ##
## inside the SM server, which will be displayed in the Messages view of the client. ##
## Line 155, soap12binding, SM generates WSDLs that conform to SOAP 1.1 binding. However, some Web Service clients accept ##
## both SOAP 1.1 and SOAP 1.2. In such cases, you can enable soap12binding by providing the parameter soapbinding:1. ##
## Line 156, vj_record_limit, sets the maximum number of records a virtual join may return on a subform. ##
## Line 157, logqueuesize, sets the number of log messages the server caches when writing a log file. ##
## Line 158, memorypollinterval, sets the frequency at which the memory heap is monitored. If you specify 0, monitoring is disabled. ##
## ##
#######################################################################################################################################

msg_buffer_size:75000
soap12binding:0
vj_record_limit:2000
logqueuesize:1000
memorypollinterval:1

##################################################################################################################################
## ##
## Lines 170 through 172 are parameters that specify the Java heap usage for HP Service Manager. ##
## Line 170, JVMOption0, sets the Java heap memory to 128MB. ##
## Line 171, JVMOption1, sets the Java heap memory to 512MB. ##
## Line 172, JVMOption2, creates a JVM with default option -Xrs, which reduces the number of signals to be handled by the JVM. ##
## ##
##################################################################################################################################


JVMOption0:-Xms128m
JVMOption1:-Xmx512m
JVMOption2:-Xrs

##################################################################################################################################
## ##
## Line 180 is used to invoke the health check file on the HP Service Manager application server. ##
## ##
##################################################################################################################################

#JVMOption999:C:/Program Files (x86)/HP/Service Manager 9.40/Server/RUN/lib/mbeanclient-9.41.war

queryhashcode:hostname:13080
restaccessviabrowser:1


querysecurity:1
clean:1
smtphost:xxxxxx.xxxxxx.com
smtpport:25
mailFrom:ServiceManager@XXXXXX.com
dashboard_export_path:D:/temp

 

##keystoreFile:servercert.keystore
##keystorePass:password1
##ssl:0
##ssl_reqClientAuth:2
##ssl_trustedClientsJKS:trustedclients.keystore
##ssl_trustedClientsPwd:tpassword
##trustedsignon:0
##truststoreFile:cacerts
##truststorePass:changeit

#truststoreFile:cacerts
#*truststorePass:0E45D6FC3E026B20D0C21E51926DE3A5
truststoreFile:hpsmTrust.jks
*truststorePass:FGFGF604396DB886D773ADA3353E7F7FEE83GFGF
sslConnector:0

 

#EOF

 

 

0 Likes
StevenB77 Super Contributor.
Super Contributor.

Re: Java Heap Space errors on web service calls on attachments...

Hi Carlos,

Any updates on this one?  I am still unable to find any settings that will resolve the Java Heap Space issue when sending attachments via web services.  Let me know what infomation I need to attach to a support case if that is necessary.

Thanks in Advance,

StevenB

0 Likes
Carlos_V_SM Acclaimed Contributor.
Acclaimed Contributor.

Re: Java Heap Space errors on web service calls on attachments...

Hi Steven,

Hope you are doing fine.

Setting file attachment limits Setting attachment size limits

You can set the following two file attachment size limits:

  • Maximum single attachment size

    This value limits the maximum size of a single attachment.

     * Total attachment size

    This value limits the total size of all attachments in an attachment container, such as an incident record.

You can set these attachment size limits in the following ways:

  • Specify the attachment size limit for the entire system in the system information record
  • Specify the attachment size limit for a particular operator in their operator record
  • Specify the attachment size limit for the attachment container on a form by using Forms Designer
  • Specify the attachment size limit for individual attachments by using the MaxAttachUploadSize and MaxTotalAttachUploadSize parameters.

     

    Note

    These parameters are located in the web.xml file. The default value of the MaxAttachUploadSize parameter is 10 MB, and the default value of the MaxTotalAttachUploadSize parameter is 50 MB.

     

If you do not specify a value in one of these places, there is no limit on the size of attachments, and users can add attachments as large as the database record will hold. If you specify the attachment size limits in more than one place, then the order of precedence is:

  1. The value from the attachment container
  2. The value from the operator record
  3. The value from the company record
  4. The values of the MaxAttachUploadSize and MaxTotalAttachUploadSize parameters

As an example, for the maximum size of a single attachment, if the company record limit is set to 1,000,000 bytes, the operator has a limit set to 2,000,000 bytes, and the container has a limit of 3,000,000 bytes, the person will be able to store a 3,000,000 byte attachment in the container (the attachment container property overrides the other two limits). A different operator without a limit, storing attachments in a different container with no limit set, would only be able to save a 1,000,000 byte attachment.

Note

File size validation is not performed at the widget level on the web service. Therefore, it is possible to attach a file that exceeds the configured size limits by using the web service.

 

Setting attachment count limits

You can limit the number of individual files that can be attached to each record in Service Manager. To do this, configure the maxattachmentcount parameter. By default, the value of this parameter is 100 files.

Carlos Villalobos R
Customer Support Engineer
If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
Highlighted
StevenB77 Super Contributor.
Super Contributor.

Re: Java Heap Space errors on web service calls on attachments...

Carlos, thanks for the update.  I have tried the suggestions below with no success.  Do you have any other suggestions on how this OutOfMemory error could occur? I have referenced the JVM whitepaper found on Oracle's website and have been unable to determine anything significant from this resource as well. 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Java Heap Space errors on web service calls on attachments...

If many users are dealing with attachments or large data sets, consider increasing the java heap size available to the servlet containers handling the web service integrations by adding these lines to your dedicated SM web services servlet definitions in the sm.cfg configuration file:

JVMOption0:-Xms512M
JVMOption1:-Xmx512M

0 Likes
StevenB77 Super Contributor.
Super Contributor.

Re: Java Heap Space errors on web service calls on attachments...

Yes, did this on a single port/thread that was dedicated to the programmer's request to add an attachment larger than 20MB.  Anytime this limit is reached the Out of Heap Space error message is written to the log. 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Java Heap Space errors on web service calls on attachments...

Can you upload a copy of the sm.cfg being used?

0 Likes
Carlos_V_SM Acclaimed Contributor.
Acclaimed Contributor.

Re: Java Heap Space errors on web service calls on attachments...

Hello Steven,

hope you are doing fine.

can you please load the sm.cfg requested?

Carlos Villalobos R
Customer Support Engineer
If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
StevenB77 Super Contributor.
Super Contributor.

Re: Java Heap Space errors on web service calls on attachments...

Apologies for taking so long to respond.  Here are the contents of the sm.cfg file.

#BOF
# HP Service Manager Server Configuration File
#
# Used by HP Service Manager service on Windows and smstart script on Unix
# to start the Service Manager server processes.
#
######################################################################################
#
# Copyright 1994-2010 Hewlett-Packard Development Company, L.P.
# All Rights Reserved
#
######################################################################################
#
# When unable to start the server as a service
# uncomment the following line to produce an output
# file which may contain some information from the
# Java JVM.
#cmd /c "sm" > C:\\process_stdout 2>&1

####################################################################################
##                                                                                ##
## Start the SC Auto Listener by using the sm -scautolistener:12690 parameter.    ##
## This parameter can be found on line 27.                                        ##
##                                                                                ##
####################################################################################

#sm -scautolistener:12690

sm -emailout -log:D:/logs/email.log

###################################################################################
##                                                                               ##
## Lines 53 through 61 have to do with starting the HPSM user threads/servlets.  ##
## The servlets start a sm.exe thread on the specified HTTP and HTTPS ports.     ##
## The first line (52) below is defined as the load balancer and no users can    ##
## access this thread.                                                           ##
##                                                                               ##
###################################################################################

 

sm -loadBalancer -httpPort:13080
#sm -httpPort:13082 -httpsPort:13083
#sm -httpPort:13084 -httpsPort:13085
#sm -httpPort:13086 -httpsPort:13087
#sm -httpPort:13088 -httpsPort:13089
#sm -httpPort:13090 -httpsPort:13091


###################################################################################
##                                                                               ##
## Lines 70 through 75 are responsible for starting the WSDL threads/servlets.   ##
## Lines 70 through 75 are also responsible for starting the sm.exe file related ##
## to the specified HTTP/S ports.                                                ##
##                                                                               ##
###################################################################################

sm -httpPort:13201 -httpsPort:13202 -debugnode:1 -webservices_sessiontimeout:30
sm -httpPort:13203 -httpsPort:13204 -debugnode:1 -webservices_sessiontimeout:30
sm -httpPort:13205 -httpsPort:13206 -debugnode:1 -webservices_sessiontimeout:30
sm -httpPort:13207 -httpsPort:13208 -debugnode:1 -webservices_sessiontimeout:30
sm -httpPort:13211 -httpsPort:13212 -debugnode:1 -webservices_sessiontimeout:30
sm -httpPort:13213 -httpsPort:13214 -debugnode:1 -webservices_sessiontimeout:30

###################################################################################
##                                                                               ##
##     Add Debugging Parameters starting at Line 86 .                         ##
## (1) If debugging needs to occur, please add the debugging parameters in this  ##
##     section of the SM.CFG file.                                               ##
##.##
##                                                                               ##
###################################################################################

 

 

 

#########################################################################
##                                                                     ##
## Start Service Manager Listener using the sm parameter i.e. (sm.exe) ##
##                                                                     ##
#########################################################################

sm

#########################################################################
##                                                                     ##
## Start Background Schedulers using parameter sm system.start         ##
##                                                                     ##
#########################################################################

sm system.start

############################################################################################################
##                                                                                                        ##
## Line 114 starts the sync process that's related to the inactivity timer and handles orphaned processes ##
##                                                                                                        ##
############################################################################################################

sm -sync

#################################################################################################################
##                                                                                                             ##
## Line 122 starts the HPSM "background" process for processing scheduled IR records running in Async IR mode. ##
##                                                                                                            ##
#################################################################################################################

sm -que:ir

#Report Scheduler
sm report.export -log:D:/Temp


#EOF

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Java Heap Space errors on web service calls on attachments...

Where are the JVMOptions? Add them to be debugnode ports of the sm.cfg and test the attachments.

0 Likes
Carlos_V_SM Acclaimed Contributor.
Acclaimed Contributor.

Re: Java Heap Space errors on web service calls on attachments...

Hi ,
hope you are doing fine.
I would like to know if you still require assistance or if your question was resolved. If so, could you please mark it as a correct answer so that other members can benefit from this answer and close this question. If it didn’t resolve then please let me know so that we can address your question again.


best regards.

Carlos Villalobos R
Customer Support Engineer
If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.