Skip to main content

Error "Header message of length [...] received but the packetSize is only [8,192]" when creating default information model in TIBCO Spotfire

Rich Talbot
  • Created
Date Posted:
Product: TIBCO Spotfire®

Problem:

Error "Header message of length [...] received but the packetSize is only [8,192]" when creating default information model in TIBCO Spotfire


Solution:

When creating a default information model in the Information Designer, the client returns the following error (where "..." is a number greater than 8,192): 

Error message: An issue occurred while creating the default model. It may be partially constructed.

InformationModelException at Spotfire.Dxp.Data:
Header message of length [...] received but the packetSize is only [8,192] (HRESULT: 80131500)

Stack Trace:
at Spotfire.Dxp.Data.InformationModel.InternalInformationModelManager.AddElement(InformationModelElement element, Boolean ignoreWarnings)
at Spotfire.Dxp.Data.InformationModel.InternalInformationModelManager.TryAddElementWithNameResolution(String suggestedName, ElementProducer elementProducer, Boolean ignoreWarnings, NameConflictStrategy conflictStrategy, InformationModelElement& createdElement)
....
InformationModelServiceException at Spotfire.Dxp.Services:
Header message of length [...] received but the packetSize is only [8,192] (HRESULT: 80131509)

Stack Trace:
at Spotfire.Dxp.Services.WebServiceBase`1.InvokeService[T](ServiceMethod`1 serviceMethod, ExceptionFactoryMethod exceptionFactoryMethod)
at Spotfire.Dxp.Data.InformationModel.InternalInformationModelManager.AddElement(InformationModelElement element, Boolean ignoreWarnings)

SoapHeaderException at System.Web.Services:
Header message of length [...] received but the packetSize is only [8,192] (HRESULT: 80131501)

Stack Trace:
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Spotfire.Dxp.WebServices.ElementManagerService.addElement(IMElement element, Boolean ignoreWarnings)
at Spotfire.Dxp.Services.WebServiceBase`1.InvokeService[T](ServiceMethod`1 serviceMethod, ExceptionFactoryMethod exceptionFactoryMethod)


  Note: We have removed the AJP connector configuration template and it is commented out in <tss>/tomcat/server.xml. Use of the AJP protocol requires additional security considerations because it allows greater direct manipulation of Tomcat's internal data structures than the HTTP connectors. If you do enable the AJP connector, for security reasons the following attributes must be configured appropriately: address, secret, secretRequired and allowedRequestAttributesPattern. For more details please refer to the Tomcat Documentation. 


If the packetSize attribute is not specified in the AJP connector configuration in the TIBCO Spotfire Server server.xml file, then the default value 8192 is used for the packetSize. In some cases when the header message length exceeds this size then the above error may be thrown. To resolve the issue, set the packetSize to 65536 in the server.xml following the steps below:
  1. Stop the TIBCO Spotfire Server service and back up the current server.xml file (This file is stored in the <installation dir>/tomcat/conf/ directory)
  2. In the server.xml, for the APJ Connector, set the packetSize to "65536". If the packetSize parameter does not exist then add it. Since the AJP connector is disabled by default, you will have to enable (uncomment) it first by removing <!-- & --> for the Connector section shown below.

    Example server.xml:

    <!-- Enable this connector if you want to use a load balancer that supports the Apache JServ Protocol -->     
<!--     <Connector port="8009"                
           protocol="AJP/1.3"                
           packetSize="65536"                
           URIEncoding="UTF-8"
         />    
 -->
  3. Save the file and then restart your TIBCO Spotfire Server. 
Doc: Server.xml file

Comments

0 comments

Article is closed for comments.