This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.
Axis2 Properties
Given below is a list of the Axis2 properties.
Axis 2 and module properties
Given below are some Axis2 and module properties set at scope "axis2".
CacheLevel
Name | CacheLevel |
---|---|
Possible Values | none, connection, session, consumer, producer, auto
|
Default Behavior |
|
Scope |
|
Description | This property determines which JMS objects should be cached. JMS objects are cached so that they can be reused in the subsequent invocations. Each caching level can be described as follows:
auto : An appropriate caching level will be used depending on the transaction strategy. |
Example | <parameter name="transport.jms.CacheLevel">consumer</parameter> |
ConcurrentConsumers
Name | ConcurrentConsumers |
---|---|
Possible Values | integer
|
Default Behavior |
|
Scope |
|
Description | The minimum number of threads for message consuming. The value specified for this property is the initial number of threads started. As the number of messages to be consumed increases, number of threads are also increased to match the load until the total number of threads equals the value specified for the |
Example | <parameter name="transport.jms.ConcurrentConsumers"locked="false">50</parameter> |
MaxConcurrentConsumers
Name | MaxConcurrentConsumers |
---|---|
Possible Values | integer
|
Default Behavior |
|
Scope |
|
Description | The maximum number of threads that can be added for message consuming. See ConcurrentConsumers. |
Example | <parameter name="transport.jms.MaxConcurrentConsumers"locked="false">50</parameter> |
JMS_COORELATION_ID
Name | JMS_COORELATION_ID |
---|---|
Possible Values | String |
Default Behavior |
|
Scope | axis2 |
Description | The JMS coorelation ID is used to match responses with specific requests. This property can be used to set the JMS coorrelation ID as a dynamic or a hard coded value in a request. As a result, responses with the matching JMS correlation IDs will be matched with the request. |
Example | <property name="JMS_COORELATION_ID" action="set" scope="axis2" expression="$header/wsa:MessageID" xmlns:sam="http://sample.esb.org/> |
MercurySequenceKey
Name | MercurySequenceKey |
---|---|
Possible Values | integer |
Default Behavior |
|
Scope |
|
Description | Can be an identifier specifying a Mercury internal sequence key. |
Example |
|
MercuryLastMessage
Name | MercuryLastMessage |
---|---|
Possible Values | true/false |
Default Behavior |
|
Scope |
|
Description | When set to "true", it will make this the last message and terminate the sequence. |
Example |
|
Axis2 client-side properties
Given below are some Axis2 client-side properties set at scope "axis2-client".
FORCE_HTTP_1.0
Name | FORCE_HTTP_1.0 |
---|---|
Possible Values | true/false |
Default Behavior |
|
Scope |
|
Description | Forces outgoing http/s messages to use HTTP 1.0 (instead of the default 1.1). |
Example |
|