Skip to content

Troubleshooting Volt MX Foundry Integration Service

This chapter explains how to troubleshoot specific properties that you may encounter while developing applications using Volt MX Foundry Integration Service ( You can access file from <middleware.home>/middleware/middleware-bootconfig and edit.

Properties in Volt MX Foundry Integration Service

Note: In license validation on WebSphere, Volt MX supports only Oracle JDK. Middleware license does not get validated on WebSphere if the server has IBM JDK. This is an expected behavior for license validation on WebSphere. This behavior is present in Middleware 5.0 and higher versions.

Property in Volt MX Foundry Integration Service Troubleshooting Tip
cacheid.transport=PARAM_ONLY The property is only for memcached. Instead of HTTP session, Volt MX Foundry Integration Service maintains session values in memcached. Memcached provides a cacheid. You can set the following values for cacheid: PARAM_ONLY: PARAM_ONLY is defined in file, by default. This represents that the cacheid is passed as param in every result sent to the device. COOKIE_ONLY: To pass the cacheid as cookie to the device or browser. You can use this property if you are running memcached in your Application Server. Set the PARAM_ONLY to COOKIE_ONLY to enable the application to set a cookie on the users’ device. EITHER: To pass the cacheid sometimes as PARAM_ONLY and sometimes as COOKIE_ONLY.
log.description.error=true The SOAP fault details are logged, by default. If you do not want to log SOAP fault details, then change it false.
p.exclude=password If you do not want to log any sensitive information in request / response parameters, specify the key name. For example, if you specify password=jack123, it masks and shows as password=****.
do.not.log If you do not want to log specific values into report database, then specify do.not.log=. For example, if you specify do.not.log=SESSIONID, then, sessionid is not inserted into database.
ssl.SocketFactory.hostname.verifierBROWSER_COMPATIBLE_HOSTNAME_VERIFIER If the application has self signed certificates, then use ssl.SocketFactory.hostname.verifier=ALLOW_ALL_HOSTNAME_VERIFIER
dontEscapeXMLSpecialChars= If you want to send the special characters; <,>,\', \", & in the xml request as is, set dontEscapeXMLSpecialChars= any of the above specified special character.For example, In, "jhonson & jhonson", if you want to send the special character, &, then specify:fault : jhonson & jhonsondontEscapeXMLSpecialChars=& thenhexpected : jhonson & jhonson If you are unable to publish an application to the server hosted on Tomcat 7.0.X: In, provide the URL as shown in the below example.http://:/manager/text In conf/tomcat-users.xml, the manager should have the following roles: admin-gui,manager-gui,manager-script,manager-jmx,manager-status.
antisamy.xml If you are unable to upload images of large size, then in antisamy.xml located at <middleware.home>/middleware/middleware_bootconfig folder, modify the below tag value to your size; .For example, if you want to upload images of maximum size, 21,000 bytes, then modify the below tag as:
SUN JSSE Security Provider While connecting Secured Socket Layer (SSL) to HTTPS based end point URLs, in middleware.log, if the following exception java.lang.ClassNotFoundException: then, in file, change the following Secured Socket Layer (SSL) Factory provider setting SSLServerSocketFactoryImpl

Other Features

  • What is the Standard way in which I can handle HTTP status codes (401, and 404) from Volt MX Foundry Integration Service?


In PostProcessor, Result object is available. In that, you can use the following code snippet to find the httpStatus code:

    Param statusCodeparam = result.findParam("httpStatusCode");
    int httpStatusCode = Integer.parseInt(statusCodeparam.getValue());

By default, Volt MX Foundry Integration Service passes the HTTP status code in the resultset json format to device. The following is the sample output string:

    resultset =  {"httpStatusCode":200,"marketIndex":[{"indName":"Dow Jones Ind.","indVal":"15618.22","symbol":"0DJIA","indValChg":"            -20.90"},{"indName":"Nasdaq Comp.","indVal":"3939.86","symbol":"0NDQC","indValChg":"3.27"},{"indName":"NYSE Composite","indVal":"          10011.65","symbol":"0NYC","indValChg":"-52.46"},{"indName":"S & P 500","indVal":"1762.97","symbol":"0S&P5","indValChg":"             -4.96"}],"opstatus":0}

You can use the following snippet in .js file to get the httpStatusCode from JSON resultset object.

int statusCode = resultset["httpStatusCode "];

  • How can I use Basic Authenticate in RESTful service with dynamic userids in request? When working with service definitions in Volt MX Iris, I need to be able to dynamically assign those values in code, that is, do I have to authenticate with Active Directory and then with REST endpoints?


Dynamically, in basic authentication, in every request, you can pass the username and password in request params with the following specified param names:

  • userid
  • pwd

If you have any domain and hostname, then use the following specified param names:

  • domain
  • hname

Volt MX Foundry Integration Service first checks in:

  • request parameters
  • if not available, it checks in session, that is, session.getAttribute(userid)
  • if not available in request and session, then it takes from the service definition file.

In JS code level:

    var inputParamTable={};                  
    inputParamTable["appID"] = "ServicesApp";                 
    inputParamTable["serviceID"] = "BasicAuthService";
                    inputParamTable["userid"] = "steve";                  
    inputParamTable["pwd"] = "apple";  
    inputParamTable["domain"] = "kits";                  
    inputParamTable["hname"] = "apple";  

If you want to store userid and password in HTTP session, write the below code in pre / post processor:

    Session session = request.getSession(false);
    session.setAttribute("userid", "steve");
    session.setAttribute("pwd", "******");

  • If end server has proxy enabled authentication, then what should I do?


You need to configure the below -D parameters:


If end server is with NTLM enabled authentication, then you need to configure the additional below -D parameter:


  • How can I add Headers?


For example, to add "Content-Type" as a header:

In the Service Definition editor -> Http Headers tab, under Id, declare Content-Type as header type and under Session, select session from the drop-down list as shown:

Write preprocessor for the service and use the following snippet in preprocessor:

    Session session = request.getSession();
    session.setAttribute("Content-Type"," application/json");

If you want to pass header values in "request" parameters,

In the Service Definition editor -> Http Headers tab, under Scope, select request from the drop-down list, then pass the header value with same key that you defined in Header section with request as scope.

For example,

    Content-Type - request scope in Volt MX Iris Header section  
    2)Use the below code in JavaScript  
    var inputParamTable={};             
    inputParamTable["Content-Type"] = "application/json";  

  • How can I add Custom Cookies in header?


  • Create cookie object using HTTP client 4.1 API, org.apache.http.cookie.Cookie
  • In pre or post processor, use the following snippet:

    Session session = request.getSession(false);

  • How can I change the url or user authentication details dynamically?


Implement URLProvider2 class and write your own logic to override the service definition values.

  • If request data is more than 1024 MB, then Linux default values do not allow to forward the request. What do I need to do so that Linux values allow to forward the request?


Login to Linux shell with root privileges.

Set the following in Linux Operating System:

Note: Below changes apply on QNBDEV server to resolve the BRE service issue.

# vi /etc/sysctl.conf ( Add the below values)

increase TCP max buffer size settable using setsockopt()net.core.rmem_max = 16777216 net.core.wmem_max = 16777216

recommended for hosts with jumbo frames enabled net.ipv4.tcp_mtu_probing=1

  • If a SOAP response has an embedded xml, then what do I need to do?


Select the Escape embedded xml in response check box in the SOAP service definition editor in Volt MX Iris to enable it.

Sample HTTP Response from end server:

<soapenv:Envelope xmlns:Soapenv="" xmlns:xsd="" xmlns:xsi="">     
    <lmsSOAPResponse xmlns="HYPERLINK """>
         <lmsPReturn>&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;&lt;LMS&gt;&lt;record id="0"&gt;&lt;CO_APP2_GMI&gt;![CDATA[Google check]&lt;/CO_APP2_GMI&gt;&lt;NMI_ELG_CAL&gt;&lt;/record&gt;&lt;/LMS&gt;</lmsReturn>

The sample embedded xml in SOAP response is converted into valid SOAP response for parsing as shown:

<soapenv:Envelope xmlns:Soapenv="" xmlns:xsd="" xmlns:xsi="">
      <lmsSOAPResponse xmlns="HYPERLINK ""http://l">
         <lmsPReturn>&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;&lt;LMS&gt;&lt;record id="0"&gt;&lt;CO_APP2_GMI&gt;![CDATA[Google check]&lt;/CO_APP2_GMI&gt;&lt;NMI_ELG_CAL&gt;&lt;/record&gt;&lt;/LMS&gt;</lmsReturn>

  • What should I do when I get a message as "Maximum offline sessions exceeded?"


This message displays when you have upgraded the Volt MX Iris to a version 2 service pack releases higher than the server. To overcome this message, you need to contact Volt MX Support team. If you are a cloud user, you have to contact the Volt MX Customer Representative and plan for the server upgrade.

  • What is the solution when middleware logs are not rolling consistently in windows environment?


Check whether you have User and Administrator permissions for the folders where middleware logs are logged. If you do not have permissions, get the permissions for the folders.

  • What should I do when I get "null" as the value for $ and if the entry is deleted from the request template when I send the request to the endpoint service?


If the run-time value for $ appears as "null", replace $ with $! to get an empty string in place of "null" to avoid the entry getting deleted.

While you replace with $! in the request body template, follow these guidelines:

  • Use $! in only the request template body. Do not use $! while you define the URL parameters in the endpoint URL.
  • If you use "foreach" in the request template body, you should not mention $! for "foreach" parameters.

    For example: #foreach ($rec in $ZashpayAccount.records)

  • What is the process of Secured Socket Layer (SSL) setup in Volt MX Foundry Integration Service?


The process of SSL setup is as follows:

Pre-requisities: Volt MX Foundry Integration Service Installation

Steps for setting up SSL:

  • Configure https port in for the property https_port in the path \tomcat\instance1\conf (Ex: D:\Workspaces\VoltMXServer\tomcat\instance1\conf,https_port = 8443 ).
  • Add the tag to middleware web.xml

  • Copy the below connector configuration for SSL enabling in server.xml:

    <Connector address="${TOMCAT.BIND.IP}" port="${https_port}" 
        maxHttpHeaderSize="8192" maxThreads="150" enableLookups="false" 
        acceptCount="25" disableUploadTimeout="true" server="VoltMX" 
        tcpNoDelay="true" compression="on" 
        SSLEnabled="true" scheme="https" secure="true" 
        clientAuth="false" sslProtocol="TLS" 
        keystoreFile="D:/ssl/tomcat.jks" keystorePass="password" 
        truststoreFile="D:/ssl/tomcat.jks" truststorePass="password"/>

Note: D:/ssl/tomcat.jks is the keystore and truststore location. You can point this to java cacerts also.
TOMCAT.BIND.IP is the IP configured in file.

Important: The above mentioned steps are for one-way SSL. If you want to enable two-way SSL on Volt MX Foundry Integration Service, please make clientAuth = true.

Java Messaging Service (JMS) Issue

  • If you are unable to start JBoss 5.1.0 with JDK 1.7.X and in Server.log and if you come across the below error:

    3:53:10,693 ERROR [AbstractKernelController] Error installing to Instantiated: name=AttachmentStore state=Described
    java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[] actual=[]
    at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(
    at org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(
    at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.newInstance (
    at org.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch  
    at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.createTarget( at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(
    at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(
    at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(
    at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(


In /jboss_jms/server/default/conf/bootstrap/profile.xml file, change the following:

<constructor><parameter><inject bean="BootstrapProfileFactory" property="attachmentStoreRoot" /></parameter></constructor>


<constructor><parameter class=""><inject bean="BootstrapProfileFactory" property="attachmentStoreRoot" /></parameter></constructor>

Open topic with navigation