Previous Topic

Next Topic

Book Contents

Book Index

Hessian requests

In This Section


Record a Hessian request

Post-recording wizard

See Also


HTTP requests

SOAP requests

WebSocket requests

Oracle Forms requests

Adobe Flex/AMF requests

Adobe RTMP requests

Data Format Extension requests

Google Web Toolkit requests

Java serialization requests

Siebel requests

Silverlight requests

Media requests

Polling requests

Streaming requests

Push messages


Edit a request in text mode

Edit an xml request in advanced mode

Variable extractors

Advanced parameters

Variable correlation


Compare requests and responses


Hessian is a binary web service protocol developed by Caucho Technology, Inc. It allows remote procedure calls to be executed between the client and server, using the standard Hessian RPC (Remote Procedure Call) communication or specific Frameworks such as Spring Remoting (Spring HTTP Invoker). The data exchange is carried out in binary and encapsulated in the HTTP protocol.

The Hessian module allows load testing web applications programmed in Java and using the standard Hessian RPC communication or specific Frameworks such as Spring Remoting (Hessian).

NeoLoad 6.7 supports Hessian 1.0 and 2.0 protocol.

Dependent libraries

When recording Hessian requests, you will need to load the Java classes for the objects exchanged, as well as the client interfaces for the called services. For more information, see Hessian.


The following diagram shows how the Hessian module works during recording:

The binary data exchanged between the client and server passes through the recording proxy. The Hessian module comes into play as the data travels through the proxy, analyzing and decoding the requests. Once translated into XML, the requests are inserted in the project.


The following diagram shows how the Hessian module works during a test run:

The XML request variables are evaluated and the module engine translates the XML to binary data. This data is then sent to the server. The binary response received is translated into XML, after which the validity checks and Variable Extractors in the played request are executed.