Thursday, July 18, 2013
Why do we get "Failed Sending Email org.apache.axis2.AxisFault: The system cannot infer the transport information from the mailto" issue?
Most of the time in WSO2 Carbon products, users may encounter exceptions as follow when subscribing for a particular mail response:
[2013-07-17 09:49:45,781] ERROR {org.apache.axis2.description.ClientUtils} - The system cannot infer the transport information from the mailto:<email> URL.
Failed Sending Email
org.apache.axis2.AxisFault: The system cannot infer the transport information from the mailto : <email>
at org.apache.axis2.description.ClientUtils.inferOutTransport(ClientUtils.java:81)
at org.apache.axis2.client.OperationClient.prepareMessageContext(OperationClient.java:288)
at org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:249)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:511)
at org.apache.axis2.client.ServiceClient.fireAndForget(ServiceClient.java:488)
at org.wso2.carbon.email.verification.util.EmailSender.run(EmailSender.java:115)
[2013-07-17 09:49:46,079] DEBUG {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} - Authorization cache entry is not found for username
The reason can be :
The reason for this issue is the AxisConfiguration which uses to send this message does not have the mail transport. In axis2.xml you have to define the transportSender as below.
<transportSender name="mailto" class="org.apache.axis2.transport.mail.MailTransportSender">
<parameter name="mail.smtp.from">user@gmail.com</parameter>
<parameter name="mail.smtp.user">user</parameter>
<parameter name="mail.smtp.password">mailpassword</parameter>
<parameter name="mail.smtp.host">smtp.gmail.com</parameter>
<parameter name="mail.smtp.port">587</parameter>
<parameter name="mail.smtp.starttls.enable">true</parameter>
<parameter name="mail.smtp.auth">true</parameter>
</transportSender>
Sometimes having an unnecessary space in between these values might also be a reason for this issue.
Labels:
Carbon,
email,
Mail transport,
transportSender,
WSO2
Friday, July 12, 2013
How to test the disable HTTP chunking for outgoing messaging via WSO2 ESB and a REST request
There are few HTTP transport-specific
properties in ESB.
Properties use in ESB access various
types of information regarding a message that passes through the ESB.
Also properties can be used to control the behavior of the ESB on a
given message.
WSO2 ESB support transfer-encoding –
chunked by default. To make it disabled, there is a property that
would help to perform it.
<property name="DISABLE_CHUNKING" value="true" scope="axis2"/>
Transfer-encoding - chunked is a feature came along with HTTP 1.1. Therefore no matter what HTTP 1.0 will support only content type. Therefore if the message is forced to send as HTTP1.0 you will be able to see only the content type. Refer the previous blog post for more reference. Outgoing message can be seen in here.
By the following steps I will be
explaining how to test this behavior if WSO2 ESB.
Download WSO2 ESB,
http://wso2.com/products/enterprise-service-bus
To Setup :
----------------
- Go to <ESB_Home>/samples/axis2Server/src/SimpleStockQuoteService and build it, ant
- Start the Go to <ESB_Home>/samples/axis2Server and start the axis2Server by the following command, sh axis2server.sh.
- Start the ESB Server, <ESB_Home>/bin by providing, sh wso2server.sh.
- Run a tcpMon to view the outgoing messages.
- Start the tcpmon in the <ESB_Home>/bin - sh tcpmon.shCreate 2 listeners as below.1. Listen Port 8281, Target host – localhost, Target port – 8280 – Before hits the ESB2. Listen Port 9001, Target host – localhost, target port – 9000 – After passing through ESB and Before hits the backend
- Log in to the ESB and provide the following synapse configuration.
<?xml version="1.0" encoding="UTF-8"?> <definitions xmlns="http://ws.apache.org/ns/synapse"> <sequence name="fault"> <log level="full"> <property name="MESSAGE" value="Executing default "fault" sequence"/> <property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/> <property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/> </log> <drop/> </sequence> <sequence name="main"> <header name="Action" value="urn:getQuote"/> <filter source="get-property('To')" regex=".*/StockQuote.*"> <property name="DISABLE_CHUNKING" value="true" scope="axis2"/> <send> <endpoint> <address uri="http://localhost:9001/services/SimpleStockQuoteService" format="soap11"/> </endpoint> </send> <drop/> </filter> <send/> </sequence> </definitions>
To Send the Rest request :
---------------------------------------------
- Go to axis2Client, <ESB_Home>/samples/axis2Client and send the following REST request.
ant stockquote -Dtrpurl=http://localhost:8281/services/StockQuote -Drest=true
Labels:
chunking,
Enterprise Service Bus,
ESB,
HTTP 1.1,
HTTP transport properties,
transfer encoding,
WSO2
How to test the Force HTTP 1.0 outgoing messages via WSO2 ESB and a REST request
There are few HTTP transport-specific
properties in ESB.
Properties use in ESB access various
types of information regarding a message that passes through the ESB.
Also properties can be used to control the behavior of the ESB on a
given message.
WSO2 ESB support HTTP 1.1 outgoing
messages by default. To make it HTTP 1.0, there is a property that
would help to perform it.
<property name="FORCE_HTTP_1.0" value="true" scope="axis2"/>
By the following steps I will be
explaining how to test this behavior if WSO2 ESB.
Download WSO2 ESB,
http://wso2.com/products/enterprise-service-bus
To Setup :
----------------
- Go to <ESB_Home>/samples/axis2Server/src/SimpleStockQuoteService and build it, ant
- Start the Go to <ESB_Home>/samples/axis2Server and start the axis2Server by the following command, sh axis2server.sh.
- Start the ESB Server, <ESB_Home>/bin by providing, sh wso2server.sh.
- Run a tcpMon to view the outgoing messages.
- Start the tcpmon in the <ESB_Home>/bin - sh tcpmon.shCreate 2 listeners as below.1. Listen Port 8281, Target host – localhost, Target port – 8280 – Before hits the ESB2. Listen Port 9001, Target host – localhost, target port – 9000 – After passing through ESB and Before hits the backend
- Log in to the ESB and provide the following synapse configuration.
<?xml version="1.0" encoding="UTF-8"?> <definitions xmlns="http://ws.apache.org/ns/synapse"> <sequence name="fault"> <log level="full"> <property name="MESSAGE" value="Executing default "fault" sequence"/> <property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/> <property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/> </log> <drop/> </sequence> <sequence name="main"> <header name="Action" value="urn:getQuote"/> <filter source="get-property('To')" regex=".*/StockQuote.*"> <property name="FORCE_HTTP_1.0" value="true" scope="axis2"/> <send> <endpoint> <address uri="http://localhost:9001/services/SimpleStockQuoteService" format="soap11"/> </endpoint> </send> <drop/> </filter> <send/> </sequence> </definitions>
To Send the Rest request :
---------------------------------------------
- Go to axis2Client, <ESB_Home>/samples/axis2Client and send the following REST request.
ant stockquote -Dtrpurl=http://localhost:8281/services/StockQuote -Drest=true
Observations :
-------------------------
- On the server side, Standard :: Stock price = $157.06490695255485 will be generated.
- Observe the tcpMon.
Rest request sent to ESB can be
seen in port 8281,
POST /services/StockQuote HTTP/1.1
Outgoing message from ESB can be
seen in port 9001,
Wednesday, July 10, 2013
Saturday, June 29, 2013
How to test Multipart/form-data with attachments and json content type pass-through support for WSO2 ESB.
I hope the reader of this blog has got an
idea about WSO2 ESB and the pass-through transport and the different
type of content types support for the product.
For more information read on,
http://wso2.com/products/enterprise-service-bus/
To test Multipart/form data, we need
the below things ready.
- A backend service.
- tcpmon to view the pass through
- A form to submit data
- Attachments – text files, json file, an image
- WSO2 ESB with the correct synapse configuration of the proxy
Backend Service
- As the backend service, I will be setting the offset to 2 and run a WSO2 App Server, which can also be downloaded from http://wso2.com/products/application-server/. I am using 5.1.0.
- I will be using the HelloService in unsecured mode.
- I assume now that I have the HelloService up and runninn in, http://localhost:9765/services/HelloService
Set up tcp mon
1. Start the tcpmon in the
<ESB_Home>/bin - sh tcpmon.sh
2. Create 2 listeners as below.
1. Listen Port 8281, Target host –
localhost, Target port – 8280 – Before hits the ESB/
HelloProxyService proxy
2. Listen Port 9766, target host –
localhost, target port – 9765 – After passing through ESB and
Before hits the backend
A form to submit data
form action="http://localhost:8281/services/HelloProxyService/greet"
<html>
<head><title>multipart/form-data - Client</title></head>
<body>
<form action="http://localhost:8281/services/HelloProxyService/greet" method="POST" enctype="multipart/form-data">
User Name: <input type="text" name="name">
User id: <input type="text" name="id">
User Address: <input type="text" name="add">
AGE: <input type="text" name="age">
<br>
Upload :
<input type="file" name="datafile" size="40" multiple>
</p>
<input type="submit" value="Submit">
</form>
</body>
</html>
Attachments
- As attachments, I have just a text file with some texts in it
- A jpeg image
- A Json file with a json object.
{
"name":"John Johnson",
"street":"Oslo West 555",
"age":33,
"phone":"555 1234567"
}
Synapse configurations
- The below proxy will allow the user to view the data that has been sent.
<Port> = 9766 or a different port you provide
<proxy name="HelloProxyService"
transports="https http"
startOnLoad="true"
trace="disable">
<description/>
<target>
<endpoint>
<address uri="http://localhost:<port>/services/HelloService"/>
</endpoint>
<outSequence>
<property name="OUT_ONLY" value="true"/>
<send/>
</outSequence>
</target>
</proxy>
2. If you want to test whether this form data saved in to a file correctly, you can enable VFS transport in axis2.xml and use the following synapse accordingly. We will be saving it in to a file in the given location.
<proxy name="HelloProxyService"
transports="https http"
startOnLoad="true"
trace="disable">
<description/>
<target>
<endpoint>
<address uri="vfs:file:///home/ushani/Downloads/out"/>
</endpoint>
<inSequence>
<property name="OUT_ONLY" value="true"/>
</inSequence>
<outSequence>
<send/>
</outSequence>
</target>
</proxy>
To Test :
(Listen Port 8281, Target host – localhost, Target port – 8280 – Before hits the ESB/ HelloProxyService proxy)
(Listen Port 9766 or a different port, target host – localhost, target port – 9765 or different port which the backend service is run – After passing through ESB and Before hits the backend)
Labels:
Content Type,
Enterprise Service Bus,
ESB,
Multipart/Data form,
Pass Through,
VFS,
WSO2
Sunday, June 23, 2013
How to create a MySQL database and a datasource using WSO2 Appfactory
To access : https://appfactorypreview.wso2.com
With the beta release of WSO2 App factory, it enables you to create a
database and datasource for the applications you create using App
Factory.
Current latest version supports MySQL.
This blog post explains you steps to create a database and a
datasource and how to point them in a Web application (WAR) created
using WSO2 App Factory.
For more information on WSO2 App Factory :
To
create a WAR/ Web app supports the datasource
- Registered user can successfully login to WSO2 app factory and create a web application. As an example I will be creating a web application named ColourFindApp.
Application Creation - Once I created the application, I will be assigning user roles for the application using the Team page.
- Then a developer or the app owner which has developer rights will be checking out the source code using GIT and do the necessary code level changes via Developer studio and then commit the code.
http://ushanib.blogspot.com/2013/02/steps-to-checkout-and-commit-wso2.html - As an example assume in my source code, I refer my datasource as colour. So the sample code in my application source code will be something like below.
E.g.,…............
Hashtable hashtable = new Hashtable();
hashtable.put("java.naming.factory.initial","org.wso2.carbon.tomcat.jndi.CarbonJavaURLContextFactory");
Context initContext = new InitialContext(hashtable);
ds = (DataSource) initContext.lookup("jdbc/colour");
Connection conn = ds.getConnection();
Statement statement = conn.createStatement();
…............
- So the datasource I will be creating should be named as colour.
Databases Permission level
| User Role | Permission |
|---|---|
| App Owner | Can create and configure databases in Development, Testing and Staging |
| Developer | Can create and configure databases in Development and Testing environments |
| QA/Tester | Can create and configure databases in Testing and Staging environments |
| Dev-Ops | Can create and configure databases in Staging and Production environments |
- A user can login to the system and select the resource section to create a database.
- User can create the database as per the above permission. Visibility of Database environment will be as above user role permission. User will be able to select the environment from the drop down. DB User and template can be created inline or separately and select it form the drop down.
- Created users and the templates for each environment will be loaded depends on the selected database environment.Datasource Permission Level
| User Role | Permission |
|---|---|
| App Owner | Can create and edit datsources in Development, Testing and Staging |
| Developer | Can create and edit datasources in Development and Testing environments |
| QA/Tester | Can configure created datasources in Testing and Staging environments |
| Dev-Ops | Can configure created datadources in Staging and Production environments |
- App owner can create a datasource and provide the database url created initially. E.g., I create a database named COL_DB and Datasource as colour.
- Then a datasource will be copied in to testing and staging as well along with the provided database URL. E.g., If I provide the database URL of the development stage it will copy the database URL of development stage in testing and staging as well.
E.g., jdbc:mysql://rss.dev.appfactorypreview.wso2.com:3306/COL_DB - If a developer logs in to the system, he or she will see the datasources created in Dveloement and testing stages.
- A Developer or a testing user can create another database in testing environment and select the datasource created and the stage as Testing and provide the newly created database URL of the testing stage. E.g., Database created in testing : COL_DB in testing storage server and select the colour as the datasource and the stage as testing and the testing DB URL and update it.
E.g., jdbc:mysql://rss.test.appfactorypreview.wso2.com:3306/COL_DB - This will enable the different users to easily update their datasource with their desired database location and test the application.
- Depends on the stage selected, existing database URL and attached users will be loaded.
- If not a developer or a tester can test their application with the datasource created initially which points to the database in the development without editing and configuring it to the different environment.
- When promoting the application in to proceeding stage it will refer the database pointed to the promoted environment.
- Only Dev Ops have permission to configure the production environment. Therefore DevOps will have to select the stage as Production and provide the database URL accordingly.
Labels:
app factory,
appfactory,
Configure Resource,
Databases,
Datasources,
MySQL,
Resources,
WSO2
Wednesday, April 24, 2013
How to test SOAP Fault Data in WSO2 ESB and JMS message store, a message processor with a reply sequence and a fault sequence
In this post I am not going to explain
about message store or message processor and their behavior. I will
exactly explain how to test SOAP Fault Data in WSO2 ESB and JMS
message store, a message processor with a reply sequence and a fault
sequence.
Before you try out
this sample, it is better to read the following articles and blog
posts to get more information.
- To read more on WSO ESB : http://wso2.com/products/enterprise-service-bus/
- Product Documentation : http://docs.wso2.org/wiki/display/ESB460/Enterprise+Service+Bus+Documentation
- Message Store : http://docs.wso2.org/wiki/display/ESB460/Message+Stores
- JMS Message Stores : http://docs.wso2.org/wiki/display/ESB460/JMS+Message+Store
- Message processor : http://docs.wso2.org/wiki/display/ESB460/Message+Processors
- Mediators : http://docs.wso2.org/wiki/display/ESB460/Mediators
- Samples on Forward Mesaging patterns with Message Stores and processors : http://docs.wso2.org/wiki/display/ESB460/Store+and+Forward+Messaging+Patterns+with+Message+Stores+and+Processors
- Error Codes : http://docs.wso2.org/wiki/display/ESB460/Error+Handling+and+Error+Codes
- Blogs : http://techfeast-hiranya.blogspot.com/2012/01/wso2-esb-tips-tricks-08-message-stores.html and http://maharachchi.blogspot.com/2012/09/now-you-can-send-soapfaults-to-fault.html
- Behaviour : https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbxKydMUlsUcTyFfMyUqeMps2pWqBhVnt-NP6Tn7zWYsQGOv1Wc0kl5-7Ha64B5iaqtYGXP92t1yLGFFTCJrplWNesVJCEkBgxDShrSjd84XwC6eW1HEYu6ptgMzPMFLGcC82Y2C-nisTI/s1600/dlc.png
- Applications and networks can be full of errors, Applications crash. Network routers and links get into states where they cannot pass messages through with the expected efficiency. These error conditions are very likely to cause a fault or trigger a runtime exception in the ESB.
- When applications and networks can be full of errors. Applications crash. Network routers and links get into states where they cannot pass messages through with the expected efficiency. These error conditions are very likely to cause a fault or trigger a runtime exception in the ESB.
- It is not mandatory to associate each sequence and proxy service with a fault sequence. In situations where a fault sequence is not specified explicitly, a default fault sequence will be used to handle errors.
Whenever
an error occurs in WSO2 ESB, the mediation engine attempts to provide
as much information as possible on the error to the user by
initializing the following properties on the erroneous message:
- ERROR_CODE
- ERROR_MESSAGE
- ERROR_DETAIL
- ERROR_EXCEPTION etc
We can configure a message broker to
save the failed requests in a message store for later delivery. When
the client
sends requests to a proxy service , the proxy service stores the
messages to a JMS message store if it cannot be delivered and then
the back-end service is invoked by a message forwarding processor,
which picks stored messages in the JMS message store.
To
test this scenario we need the following:
- Message Broker – I will be using WSO2 Message Broker (MB)
- WSO2 ESB
- WSO2 Application Server to invoke a service – Axis2Service (You can use any other service which will generate an exception)
To configure WSO2 ESB, AS and MB, follow the steps below:
- Follow the steps in the following location. http://docs.wso2.org/wiki/display/ESB460/Configure+with+WSO2+Message+Broker
- Or 1 and 2 steps in http://sandapa.blogspot.com/2013/02/jms-messaging-with-wso2-esb-460-and.html
- Now the ESB and Message broker should be ready.
Configurations :
---------------------------
- Set the offset as 2 in carbon.xml (<AS_HOME/repository/conf>) and start the Application server deploying the Axis2service. Refer the following document. http://docs.wso2.org/wiki/display/AS510/Installation+Guide
- Create a proxy. Provide the following synapse configuration.
<proxy name="FaultTestProxy"
transports="https http"
startOnLoad="true"
trace="disable">
<description/>
<target>
<inSequence>
<log level="full"/>
<property name="target.endpoint" value="AxisEp"/>
<property name="FORCE_SC_ACCEPTED" value="true" scope="axis2"/>
<property name="FORCE_ERROR_ON_SOAP_FAULT" value="true"/>
<store messageStore="Queue1"/>
</inSequence>
<outSequence>
<send/>
</outSequence>
<faultSequence>
<log level="full" category="ERROR"/>
</faultSequence>
</target>
</proxy>
6. Set the endpoint as following to invoke Axis2Service. This can be any service which will help to produce an error.
<endpoint name="AxisEp">
<address uri="http://localhost:9765/services/Axis2Service">
<suspendOnFailure>
<errorCodes>-1</errorCodes>
<progressionFactor>1.0</progressionFactor>
</suspendOnFailure>
</address>
</endpoint>
7.
Create
a message store as following.
<messageStore class="org.wso2.carbon.message.store.persistence.jms.JMSMessageStore"
name="Queue1">
<parameter name="java.naming.factory.initial">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter>
<parameter name="store.jms.cache.connection">false</parameter>
<parameter name="java.naming.provider.url">repository/conf/jndi.properties</parameter>
<parameter name="store.jms.JMSSpecVersion">1.1</parameter>
<parameter name="store.jms.destination">Queue1</parameter>
</messageStore>
8.
Create
a Scheduled Message Forwarding Processor as following.
<messageProcessor class="org.apache.synapse.message.processors.forward.ScheduledMessageForwardingProcessor"
name="MyMsgProc"
messageStore="Queue1">
<parameter name="message.processor.reply.sequence">Axis_Ok</parameter>
<parameter name="max.delivery.attempts">4</parameter>
<parameter name="interval">5000</parameter>
<parameter name="message.processor.fault.sequence">Axis_Fault</parameter>
</messageProcessor>
9.
Following fault
sequence should be configured
<sequence name="Axis_Fault">
<log level="custom" category="ERROR">
<property name="text" value="An error occured"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="ERROR_MESSAGE"
expression="get-property('ERROR_MESSAGE')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="ERROR_CODE"
expression="get-property('ERROR_CODE')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="ERROR_DETAIL"
expression="get-property('ERROR_DETAIL')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="ERROR_EXCEPTION"
expression="get-property('ERROR_EXCEPTION')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="FaultTo"
expression="get-property('FaultTo')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="FAULT"
expression="get-property('FAULT')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="SENDING_FAULT"
expression="get-property('SENDING_FAULT')"/>
<property xmlns:ns="http://org.apache.synapse/xsd" name="REPLY" expression="/"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="RESPONSE"
expression="get-property('RESPONSE ')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="HTTP_SC"
expression="get-property('HTTP_SC')"/>
</log>
<log level="full" category="ERROR"/>
</sequence>
The whole Synapse Configuration would be as follows :
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://ws.apache.org/ns/synapse">
<registry provider="org.wso2.carbon.mediation.registry.WSO2Registry">
<parameter name="cachableDuration">15000</parameter>
</registry>
#######################
# Proxy
#######################
<proxy name="FaultTestProxy"
transports="https http"
startOnLoad="true"
trace="disable">
<description/>
<target>
<inSequence>
<log level="full"/>
<property name="target.endpoint" value="AxisEp"/>
<property name="FORCE_SC_ACCEPTED" value="true" scope="axis2"/>
<property name="FORCE_ERROR_ON_SOAP_FAULT" value="true"/>
<store messageStore="Queue1"/>
</inSequence>
<outSequence>
<send/>
</outSequence>
<faultSequence>
<log level="full" category="ERROR"/>
</faultSequence>
</target>
</proxy>
#######################
# Endpoint
#######################
<endpoint name="AxisEp">
<address uri="http://localhost:9765/services/Axis2Service">
<suspendOnFailure>
<errorCodes>-1</errorCodes>
<progressionFactor>1.0</progressionFactor>
</suspendOnFailure>
</address>
</endpoint>
#######################
# Fault Sequence
#######################
<sequence name="Axis_Fault">
<log level="custom" category="ERROR">
<property name="text" value="An error occured"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="ERROR_MESSAGE"
expression="get-property('ERROR_MESSAGE')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="ERROR_CODE"
expression="get-property('ERROR_CODE')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="ERROR_DETAIL"
expression="get-property('ERROR_DETAIL')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="ERROR_EXCEPTION"
expression="get-property('ERROR_EXCEPTION')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="FaultTo"
expression="get-property('FaultTo')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="FAULT"
expression="get-property('FAULT')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="SENDING_FAULT"
expression="get-property('SENDING_FAULT')"/>
<property xmlns:ns="http://org.apache.synapse/xsd" name="REPLY" expression="/"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="RESPONSE"
expression="get-property('RESPONSE ')"/>
<property xmlns:ns="http://org.apache.synapse/xsd"
name="HTTP_SC"
expression="get-property('HTTP_SC')"/>
</log>
<log level="full" category="ERROR"/>
</sequence>
<sequence name="main">
<in>
<log level="full"/>
<filter source="get-property('To')" regex="http://localhost:9000.*">
<send/>
</filter>
</in>
<out>
<send/>
</out>
<description>The main sequence for the message mediation</description>
</sequence>
#######################
# Message Store
#######################
<messageStore class="org.wso2.carbon.message.store.persistence.jms.JMSMessageStore"
name="Queue1">
<parameter name="java.naming.factory.initial">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter>
<parameter name="store.jms.cache.connection">false</parameter>
<parameter name="java.naming.provider.url">repository/conf/jndi.properties</parameter>
<parameter name="store.jms.JMSSpecVersion">1.1</parameter>
<parameter name="store.jms.destination">Queue1</parameter>
</messageStore>
#######################
# Message Processor
#######################
<messageProcessor class="org.apache.synapse.message.processors.forward.ScheduledMessageForwardingProcessor"
name="MyMsgProc"
messageStore="Queue1">
<parameter name="message.processor.reply.sequence">Axis_Ok</parameter>
<parameter name="max.delivery.attempts">4</parameter>
<parameter name="interval">5000</parameter>
<parameter name="message.processor.fault.sequence">Axis_Fault</parameter>
</messageProcessor>
</definitions>
To Test:
------------
1. Via SOAP create a new SOAP project and provide the following wsdl URL,
http://localhost:8281/services/FaultTestProxy?wsdl
2. Then stop the Axis2Service and send the following request in echoInt method. (We are sending a String value except an int value)
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://service.carbon.wso2.org">
<soapenv:Header/>
<soapenv:Body>
<ser:echoInt>
<!--Optional:-->
<ser:x>String</ser:x>
</ser:echoInt>
</soapenv:Body>
</soapenv:Envelope>
3. Then the message store will store the message. Then start the Axis2Service. Then the Message Processor will pick the message and try to forward it. Due to the string value, following Error codes will be printed in the ESB Server console.
ERROR - LogMediator text = An error occured, ERROR_MESSAGE = Invalid value "String" for element x, ERROR_CODE = Client, ERROR_DETAIL = , ERROR_EXCEPTION = , FaultTo = , FAULT = TRUE, SENDING_FAULT = null, REPLY = <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header><ns:BAMEvent xmlns:ns="http://wso2.org/ns/2010/10/bam" activityID="13320046414250_138"/></soapenv:Header><soapenv:Body><soapenv:Fault xmlns:axis2ns26="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>axis2ns26:Client</faultcode><faultstring>Invalid value "String" for element x</faultstring><detail/></soapenv:Fault></soapenv:Body></soapenv:Envelope>, RESPONSE = null, HTTP_SC = 500
This was done with the great help provided by Charitha Kankanamge. :)
Labels:
Enterprise Service Bus,
ESB,
Fault Sequence,
Message Processor,
Message Store,
SOAP Fault Data,
WSO2
Subscribe to:
Posts (Atom)








