ESB configuration Of .Net Service on WSO2
I have downloaded WSO2 Enterprise Service Bus (ESB) v1.6. we have a POC, I which all the web services is written in .NET Freamework2.0. now I want to integrate deploy my .net services on Fuse ESB and so that my client will see the ESB implementation. Can you help in this regards.
• Is .NET services will be configured on WSO2 Enterprise Service Bus (ESB) v1.6.
• If yes any supporting document/reference, so that I will implement WSO2 Enterprise Service Bus (ESB) v1.6 in my POC.
please help me in this regards
:Kapil Muni Gupta
- Login or register to post comments
- Printer friendly version
- 453 reads











Kapil Please use the WSO2
Kapil
Please use the WSO2 ESB 1.7 release instead of the 1.6 version. I do not understand what you want with the Fuse ESB?
Yes, you can use the WSO2 ESB v1.7 with .Net services. Refer to the standard product documentation and samples from wso2.org/esb
There is nothing different to do to integrate with a SOAP service on .net.. that is the whole idea about SOAP after all :)!
asankha
Hi Asankha, As you have
Hi Asankha,
As you have suggested, I am downloading the 1.7 version of this.
here is what i want to do-
To develop a new web service we have write a simple code like
using System;
using System.Web;
using System.Web.Services;
using System.Web.Services.Protocols;
[WebService(Namespace = "http://tempuri.org/hellowebserver/")]
[WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]
// To allow this Web Service to be called from script, using ASP.NET AJAX, uncomment the following line.
// [System.Web.Script.Services.ScriptService]
public class Service : System.Web.Services.WebService
{
public Service () {
//Uncomment the following line if using designed components
//InitializeComponent();
}
[WebMethod]
public string Hello(string mesg) {
return "Welcome ........ " + mesg + "!!";
}
}
Now we are able to browse the wsdl as http:///helloworld/service.asmx?wsdl
No to consume in .net we need to add webreference of that wsdl in that project and need to write simple code like.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
namespace HelloWebClient
{
class Program
{
static void Main(string[] args)
{
Console.Write("Enter your name: ");
string str = Console.ReadLine();
HelloProxy.HelloProxy hp = new HelloProxy.HelloProxy();
string respStr = hp.Hello(str);
Console.WriteLine("Got this response from server: {0}", respStr);
}
}
}
Now can you tell me step to how I will create a proxy/endpoint in wso2esb and then how i will be able to consume that end point in .net client. please explain or provide and reference document.
:Kapil muni Gupta
Kapil Refer
Kapil
Refer http://wso2.org/project/esb/java/1.7/docs/ESB_Samples.html#Sample150
And http://wso2.org/library/3333
Basically create a proxy service that exposes your .Net service
Then, direct your .Net client at the Proxy service EPR to consume it via the ESB
Note: The ASMX services does NOT property adhere to HTTP semantics when run in the IDE mode. You will need to deploy the .Net service into IIS or use WCF services with the WSO2 ESB
asankha
while creating new proxy from v1.7, i m getting following consol
while creating new proxy from v1.7, i m getting following console error(further if you provide me your contact no then i will plan a disscussion with you)
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\gk47072>d:
D:\>cd D:\wso2esb-1.7\bin
D:\wso2esb-1.7\bin>wso2-esb.bat
"Starting WSO2 Enterprise Service Bus ..."
Using ESB_HOME: D:\wso2esb-1.7\bin\..
Using JAVA_HOME: C:\Program Files\Java\jdk1.6.0
Using SYNAPSE_XML:
--> Wrapper Started as Console
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
2008-08-14 17:58:55,297 [-] [WrapperSimpleAppMain] INFO ServiceBus [ESB] Starti
ng the WSO2 ESB ...
2008-08-14 17:58:55,329 [-] [WrapperSimpleAppMain] INFO TomcatServer Starting t
he embedded Tomcat server..
2008-08-14 17:58:56,297 [-] [WrapperSimpleAppMain] INFO ServiceBusManager Start
ing the JMX Connector
2008-08-14 17:58:56,297 [-] [WrapperSimpleAppMain] INFO ServiceBusConfiguration
Configuration loading from : D:\wso2esb-1.7\.\webapp\WEB-INF\classes\conf\serve
r.xml
2008-08-14 17:58:56,532 [-] [WrapperSimpleAppMain] INFO ServiceBusManager JMX c
onsoles can connect to : service:jmx:rmi:///jndi/rmi://172.17.13.26:1099/esb
2008-08-14 17:58:56,532 [-] [WrapperSimpleAppMain] INFO ServiceBusManager Start
ing the WSO2 Enterprise Service Bus..
2008-08-14 17:58:57,954 [-] [WrapperSimpleAppMain] INFO ServiceBusManager Datab
ase server started on 127.0.0.1 over port 1528
2008-08-14 17:58:57,954 [-] [WrapperSimpleAppMain] INFO ServerManager Using Syn
apse home as : D:\wso2esb-1.7\.
2008-08-14 17:58:57,954 [-] [WrapperSimpleAppMain] INFO ServerManager Using the
Axis2 Repository : D:\wso2esb-1.7\.\repository
2008-08-14 17:58:57,954 [-] [WrapperSimpleAppMain] INFO ServerManager Using the
axis2.xml : D:\wso2esb-1.7\.\webapp\WEB-INF\classes\conf\axis2.xml
2008-08-14 17:58:57,954 [-] [WrapperSimpleAppMain] INFO ServerManager The serve
r name was not specified, defaulting to : pth-pc388314
2008-08-14 17:58:57,954 [-] [WrapperSimpleAppMain] INFO ServerManager The timeo
ut handler will run every : 15s
2008-08-14 17:58:58,438 [-] [WrapperSimpleAppMain] INFO SynapseInitializationMo
dule Initializing Synapse at : Thu Aug 14 17:58:58 GMT+05:30 2008
2008-08-14 17:58:58,438 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Loading mediator extensions...
2008-08-14 17:58:58,891 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Initializing the Synapse configuration ...
2008-08-14 17:58:58,891 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
XMLConfigurationBuilder Generating the Synapse configuration model by parsing t
he XML configuration
2008-08-14 17:59:11,250 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
SynapseConfigurationBuilder Loaded Synapse configuration from : D:\wso2esb-1.7\
.\webapp/WEB-INF/classes/conf/synapse.xml
2008-08-14 17:59:11,250 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Deploying the Synapse service..
2008-08-14 17:59:11,266 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Synapse server name : pth-pc388314
2008-08-14 17:59:11,266 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Deploying Proxy services...
2008-08-14 17:59:11,266 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Synapse initialized successfully...!
2008-08-14 17:59:11,266 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
HttpCoreNIOSSLSender Loading Identity Keystore from : webapp/WEB-INF/classes/co
nf/identity.jks
2008-08-14 17:59:11,266 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
HttpCoreNIOSSLSender Loading Trust Keystore from : webapp/WEB-INF/classes/conf/
trust.jks
2008-08-14 17:59:11,281 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
HttpCoreNIOSender HTTPS Sender starting
2008-08-14 17:59:11,281 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
HttpCoreNIOSender HTTP Sender starting
2008-08-14 17:59:11,281 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
JMSSender JMS Sender started
2008-08-14 17:59:11,281 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
VFSTransportSender VFS Sender started
2008-08-14 17:59:12,078 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
ServerManager Starting transport mailto
2008-08-14 17:59:12,078 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
MailTransportListener MAILTO Listener started
2008-08-14 17:59:12,078 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
ServerManager Starting transport https on port 8243
2008-08-14 17:59:12,078 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
HttpCoreNIOSSLListener Loading Identity Keystore from : webapp/WEB-INF/classes/
conf/identity.jks
2008-08-14 17:59:12,078 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
HttpCoreNIOSSLListener Loading Trust Keystore from : webapp/WEB-INF/classes/con
f/trust.jks
2008-08-14 17:59:12,078 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
HttpCoreNIOListener HTTPS Listener starting on port : 8243
2008-08-14 17:59:12,078 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
ServerManager Starting transport admin/https
2008-08-14 17:59:12,078 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
ServerManager Starting transport http on port 8280
2008-08-14 17:59:12,078 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
HttpCoreNIOListener HTTP Listener starting on port : 8280
2008-08-14 17:59:12,078 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
ServerManager Starting transport vfs
2008-08-14 17:59:12,094 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
VFSTransportListener VFS Listener started
2008-08-14 17:59:12,094 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
ServerManager Ready for processing
2008-08-14 17:59:17,828 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
ServiceBusManager [ESB] Start request completed
2008-08-14 17:59:18,312 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
TomcatServer Tomcat Server started at https://pth-pc388314:9444/esb
2008-08-14 17:59:18,312 [172.17.13.26-pth-pc388314] [WrapperSimpleAppMain] INFO
ServiceBus [ESB] WSO2 ESB started in 23015 ms
2008-08-14 18:00:31,013 [172.17.13.26-pth-pc388314] [http-9444-Processor4] INFO
LoginAdmin User : admin logged into the system
2008-08-14 18:01:09,652 [172.17.13.26-pth-pc388314] [http-9444-Processor1] ERROR
PoolTcpEndpoint Socket error caused by remote host /127.0.0.1
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.readFully(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.waitForClose(Unknown Sourc
e)
at com.sun.net.ssl.internal.ssl.HandshakeOutStream.flush(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.sendChangeCipherSpec(Unknown
Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.sendChangeCipherAndFini
sh(Unknown Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.clientFinished(Unknown
Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.processMessage(Unknown
Source)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source
)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Un
known Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Sou
rce)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Sou
rce)
at org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocke
tFactory.java:119)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:520)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
at java.lang.Thread.run(Unknown Source)
2008-08-14 18:01:09,668 [172.17.13.26-pth-pc388314] [http-9444-Processor2] ERROR
PoolTcpEndpoint Socket error caused by remote host /127.0.0.1
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.readFully(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.waitForClose(Unknown Sourc
e)
at com.sun.net.ssl.internal.ssl.HandshakeOutStream.flush(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.sendChangeCipherSpec(Unknown
Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.sendChangeCipherAndFini
sh(Unknown Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.clientFinished(Unknown
Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.processMessage(Unknown
Source)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source
)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Un
known Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Sou
rce)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Sou
rce)
at org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocke
tFactory.java:119)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:520)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
at java.lang.Thread.run(Unknown Source)
2008-08-14 18:01:09,668 [172.17.13.26-pth-pc388314] [http-9444-Processor3] ERROR
PoolTcpEndpoint Socket error caused by remote host /127.0.0.1
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.readFully(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.waitForClose(Unknown Sourc
e)
at com.sun.net.ssl.internal.ssl.HandshakeOutStream.flush(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.sendChangeCipherSpec(Unknown
Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.sendChangeCipherAndFini
sh(Unknown Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.clientFinished(Unknown
Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.processMessage(Unknown
Source)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source
)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Un
known Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Sou
rce)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Sou
rce)
at org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocke
tFactory.java:119)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:520)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
at java.lang.Thread.run(Unknown Source)
2008-08-14 18:01:11,855 [172.17.13.26-pth-pc388314] [http-9444-Processor8] ERROR
PoolTcpEndpoint Socket error caused by remote host /127.0.0.1
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.readFully(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Un
known Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Sou
rce)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Sou
rce)
at org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocke
tFactory.java:119)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:520)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
at java.lang.Thread.run(Unknown Source)
2008-08-14 18:01:11,855 [172.17.13.26-pth-pc388314] [http-9444-Processor3] ERROR
PoolTcpEndpoint Socket error caused by remote host /127.0.0.1
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.readFully(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Un
known Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Sou
rce)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Sou
rce)
at org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocke
tFactory.java:119)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:520)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
at java.lang.Thread.run(Unknown Source)
Regards
Kapil
020-30922817
919921383362
Hi Kapil Could you try using
Hi Kapil
Could you try using a JDK 1.5.x version instead? We deploy the WSO2 ESB Admin console on an embedded Tomcat server, and the problem seems to be a SSL connection issue with it..
asankha
Hi Asankha, while tryng
Hi Asankha,
while tryng with jdk1.5.0_04, i got following error at login time. please help in this regards.
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\gk47072>d:
D:\>cd D:\wso2esb-1.7\bin
D:\wso2esb-1.7\bin>wso2-esb
JAVA_HOME variable not defined or incorrect. Please set JAVA_HOME.
"Starting WSO2 Enterprise Service Bus ..."
Using ESB_HOME: D:\wso2esb-1.7\bin\..
Using JAVA_HOME:
Using SYNAPSE_XML:
--> Wrapper Started as Console
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
2008-08-18 11:12:36,877 [-] [WrapperSimpleAppMain] INFO ServiceBus [ESB] Starti
ng the WSO2 ESB ...
2008-08-18 11:12:36,924 [-] [WrapperSimpleAppMain] INFO TomcatServer Starting t
he embedded Tomcat server..
2008-08-18 11:12:37,717 [-] [WrapperSimpleAppMain] INFO ServiceBusManager Start
ing the JMX Connector
2008-08-18 11:12:37,717 [-] [WrapperSimpleAppMain] INFO ServiceBusConfiguration
Configuration loading from : D:\wso2esb-1.7\.\webapp\WEB-INF\classes\conf\serve
r.xml
2008-08-18 11:12:37,934 [-] [WrapperSimpleAppMain] INFO ServiceBusManager JMX c
onsoles can connect to : service:jmx:rmi:///jndi/rmi://172.17.8.116:1099/esb
2008-08-18 11:12:37,934 [-] [WrapperSimpleAppMain] INFO ServiceBusManager Start
ing the WSO2 Enterprise Service Bus..
2008-08-18 11:12:39,334 [-] [WrapperSimpleAppMain] INFO ServiceBusManager Datab
ase server started on 127.0.0.1 over port 1528
2008-08-18 11:12:39,334 [-] [WrapperSimpleAppMain] INFO ServerManager Using Syn
apse home as : D:\wso2esb-1.7\.
2008-08-18 11:12:39,334 [-] [WrapperSimpleAppMain] INFO ServerManager Using the
Axis2 Repository : D:\wso2esb-1.7\.\repository
2008-08-18 11:12:39,334 [-] [WrapperSimpleAppMain] INFO ServerManager Using the
axis2.xml : D:\wso2esb-1.7\.\webapp\WEB-INF\classes\conf\axis2.xml
2008-08-18 11:12:39,334 [-] [WrapperSimpleAppMain] INFO ServerManager The serve
r name was not specified, defaulting to : pth-pc388319
2008-08-18 11:12:39,334 [-] [WrapperSimpleAppMain] INFO ServerManager The timeo
ut handler will run every : 15s
2008-08-18 11:12:39,847 [-] [WrapperSimpleAppMain] INFO SynapseInitializationMo
dule Initializing Synapse at : Mon Aug 18 11:12:39 GMT+05:30 2008
2008-08-18 11:12:39,847 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Loading mediator extensions...
2008-08-18 11:12:40,282 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Initializing the Synapse configuration ...
2008-08-18 11:12:40,282 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
XMLConfigurationBuilder Generating the Synapse configuration model by parsing t
he XML configuration
2008-08-18 11:12:42,910 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
SynapseConfigurationBuilder Loaded Synapse configuration from : D:\wso2esb-1.7\
.\webapp/WEB-INF/classes/conf/synapse.xml
2008-08-18 11:12:42,910 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Deploying the Synapse service..
2008-08-18 11:12:42,910 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Synapse server name : pth-pc388319
2008-08-18 11:12:42,910 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Deploying Proxy services...
2008-08-18 11:12:42,910 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Synapse initialized successfully...!
2008-08-18 11:12:42,942 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
HttpCoreNIOSSLSender Loading Identity Keystore from : webapp/WEB-INF/classes/co
nf/identity.jks
2008-08-18 11:12:42,957 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
HttpCoreNIOSSLSender Loading Trust Keystore from : webapp/WEB-INF/classes/conf/
trust.jks
2008-08-18 11:12:42,957 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
HttpCoreNIOSender HTTPS Sender starting
2008-08-18 11:12:42,957 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
HttpCoreNIOSender HTTP Sender starting
2008-08-18 11:12:42,957 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
VFSTransportSender VFS Sender started
2008-08-18 11:12:43,237 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
JMSSender JMS Sender started
2008-08-18 11:12:43,595 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
ServerManager Starting transport https on port 8243
2008-08-18 11:12:43,595 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
HttpCoreNIOSSLListener Loading Identity Keystore from : webapp/WEB-INF/classes/
conf/identity.jks
2008-08-18 11:12:43,595 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
HttpCoreNIOSSLListener Loading Trust Keystore from : webapp/WEB-INF/classes/con
f/trust.jks
2008-08-18 11:12:43,595 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
HttpCoreNIOListener HTTPS Listener starting on port : 8243
2008-08-18 11:12:43,595 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
ServerManager Starting transport http on port 8280
2008-08-18 11:12:43,610 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
HttpCoreNIOListener HTTP Listener starting on port : 8280
2008-08-18 11:12:43,610 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
ServerManager Starting transport vfs
2008-08-18 11:12:43,626 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
VFSTransportListener VFS Listener started
2008-08-18 11:12:43,626 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
ServerManager Starting transport mailto
2008-08-18 11:12:43,626 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
MailTransportListener MAILTO Listener started
2008-08-18 11:12:43,626 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
ServerManager Starting transport admin/https
2008-08-18 11:12:43,626 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
ServerManager Ready for processing
2008-08-18 11:12:45,212 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
ServiceBusManager [ESB] Start request completed
2008-08-18 11:12:45,601 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
TomcatServer Tomcat Server started at https://pth-pc388319:9444/esb
2008-08-18 11:12:45,601 [172.17.8.116-pth-pc388319] [WrapperSimpleAppMain] INFO
ServiceBus [ESB] WSO2 ESB started in 8708 ms
2008-08-18 11:12:56,626 [172.17.8.116-pth-pc388319] [http-9444-Processor4] INFO
LoginAdmin User : admin logged into the system
2008-08-18 11:12:56,859 [172.17.8.116-pth-pc388319] [http-9444-Processor2] ERROR
PoolTcpEndpoint Socket error caused by remote host /127.0.0.1
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.readFully(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.waitForClose(Unknown Sourc
e)
at com.sun.net.ssl.internal.ssl.HandshakeOutStream.flush(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.sendChangeCipherSpec(Unknown
Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.sendChangeCipherAndFini
sh(Unknown Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.clientFinished(Unknown
Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.processMessage(Unknown
Source)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source
)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Un
known Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Sou
rce)
at org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocke
tFactory.java:119)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:520)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
at java.lang.Thread.run(Unknown Source)
2008-08-18 11:12:56,890 [172.17.8.116-pth-pc388319] [http-9444-Processor4] ERROR
PoolTcpEndpoint Socket error caused by remote host /127.0.0.1
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.readFully(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.waitForClose(Unknown Sourc
e)
at com.sun.net.ssl.internal.ssl.HandshakeOutStream.flush(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.sendChangeCipherSpec(Unknown
Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.sendChangeCipherAndFini
sh(Unknown Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.clientFinished(Unknown
Source)
at com.sun.net.ssl.internal.ssl.ServerHandshaker.processMessage(Unknown
Source)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source
)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Un
known Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Sou
rce)
at org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocke
tFactory.java:119)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:520)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
at java.lang.Thread.run(Unknown Source)
Kapil I think I nailed the
Kapil
I think I nailed the problem to something related to a wrong image link and IE 6.. can you try with FF 2.x or IE 7 instead for now?
asankha
Hi Asankha, thanks for
Hi Asankha,
thanks for reply, now i am able to create proxy service using firfox 2.x., while accessing proxy service from asp.net it give following error.
please help me.
Server Error in '/testesb' Application.
--------------------------------------------------------------------------------
The remote certificate is invalid according to the validation procedure.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
Source Error:
Line 44: [System.Web.Services.Protocols.SoapDocumentMethodAttribute("http://tempuri.org/HelloWorld", RequestNamespace="http://tempuri.org/", ResponseNamespace="http://tempuri.org/", Use=System.Web.Services.Description.SoapBindingUse.Literal, ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Wrapped)]
Line 45: public string HelloWorld() {
Line 46: object[] results = this.Invoke("HelloWorld", new object[0]);
Line 47: return ((string)(results[0]));
Line 48: }
Source File: c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\testesb\bd45701c\81b9a037\App_WebReferences.2xsud3zo.0.cs Line: 46
Stack Trace:
[AuthenticationException: The remote certificate is invalid according to the validation procedure.]
System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception) +1101034
System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) +1101081
System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) +248
System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) +53
System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) +208
System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) +178
System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) +107
System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) +248
System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) +53
System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) +208
System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) +178
System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) +107
System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) +248
System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) +53
System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) +208
System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) +178
System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) +107
System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) +248
System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) +130
System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) +85
System.Net.TlsStream.CallProcessAuthentication(Object state) +47
System.Threading.ExecutionContext.runTryCode(Object userData) +66
System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) +0
System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) +166
System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) +145
System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) +728
System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) +44
System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) +25
System.Net.ConnectStream.WriteHeaders(Boolean async) +122
[WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.]
System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) +314
System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request) +4
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) +172
ABCD.esbTesting.HelloWorld() in c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\testesb\bd45701c\81b9a037\App_WebReferences.2xsud3zo.0.cs:46
_Default.Page_Load(Object sender, EventArgs e) in c:\Inetpub\wwwroot\testesb\Default.aspx.cs:18
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +33
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436
Asankha and Kapil, This is
Asankha and Kapil,
This is due to the image links that are there from YUI JavaScript library. We are not shipping all the images relevant to the YUI scripts. But all these will be fixed on the ESB 2.0 release.
Thanks,
Ruwan Linton
Hi Ruwan,thanks for prompt
Hi Ruwan,
thanks for prompt reply, is any other way to consume this proxy service in .net?
Please reply
Thanks
Kapil
Kapil This error you
Kapil
This error you reported is due to the browser you use and would be harmless for actual messages processed via the ESB.
You can consume .Net services via the ESB, or ESB services via .net or other languages. There is no difference whether the service was developed using .net or php or java etc.. after all this is the idea of SOA!
asankha
Hi Asankha, i have updated
Hi Asankha,
i have updated my browser version to ie7.0. now i getting following error.
Server Error in '/test' Application.
--------------------------------------------------------------------------------
The underlying connection was closed: An unexpected error occurred on a receive.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive.
Source Error:
Line 35: [System.Web.Services.Protocols.SoapDocumentMethodAttribute("http://tempuri.org/HelloWorld", RequestNamespace="http://tempuri.org/", ResponseNamespace="http://tempuri.org/", Use=System.Web.Services.Description.SoapBindingUse.Literal, ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Wrapped)]
Line 36: public string HelloWorld() {
Line 37: object[] results = this.Invoke("HelloWorld", new object[0]);
Line 38: return ((string)(results[0]));
Line 39: }
Source File: c:\inetpub\wwwroot\test\Web References\aaaa\Reference.cs Line: 37
Stack Trace:
[WebException: The underlying connection was closed: An unexpected error occurred on a receive.]
System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) +58
System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request) +5
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) +183
test.aaaa.testing.HelloWorld() in c:\inetpub\wwwroot\test\Web References\aaaa\Reference.cs:37
test.WebForm1.Page_Load(Object sender, EventArgs e) in c:\inetpub\wwwroot\test\webform1.aspx.cs:24
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032
the console message is:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\gk47072>d:
D:\>c:
C:\Documents and Settings\gk47072>c:
C:\Documents and Settings\gk47072>cd\
C:\>cd C:\wso2esb-1.7\bin
C:\wso2esb-1.7\bin>ws02-esb
'ws02-esb' is not recognized as an internal or external command,
operable program or batch file.
C:\wso2esb-1.7\bin>wso2-esb
"Starting WSO2 Enterprise Service Bus ..."
Using ESB_HOME: C:\wso2esb-1.7\bin\..
Using JAVA_HOME: C:\Sun\SDK\jdk
Using SYNAPSE_XML:
--> Wrapper Started as Console
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
2008-08-22 12:36:26,267 [-] [WrapperSimpleAppMain] INFO ServiceBus [ESB] Starti
ng the WSO2 ESB ...
2008-08-22 12:36:26,299 [-] [WrapperSimpleAppMain] INFO TomcatServer Starting t
he embedded Tomcat server..
2008-08-22 12:36:27,408 [-] [WrapperSimpleAppMain] INFO ServiceBusManager Start
ing the JMX Connector
2008-08-22 12:36:27,408 [-] [WrapperSimpleAppMain] INFO ServiceBusConfiguration
Configuration loading from : C:\wso2esb-1.7\.\webapp\WEB-INF\classes\conf\serve
r.xml
2008-08-22 12:36:27,720 [-] [WrapperSimpleAppMain] INFO ServiceBusManager JMX c
onsoles can connect to : service:jmx:rmi:///jndi/rmi://172.17.8.134:1099/esb
2008-08-22 12:36:27,720 [-] [WrapperSimpleAppMain] INFO ServiceBusManager Start
ing the WSO2 Enterprise Service Bus..
2008-08-22 12:36:29,299 [-] [WrapperSimpleAppMain] INFO ServiceBusManager Datab
ase server started on 127.0.0.1 over port 1528
2008-08-22 12:36:29,299 [-] [WrapperSimpleAppMain] INFO ServerManager Using Syn
apse home as : C:\wso2esb-1.7\.
2008-08-22 12:36:29,299 [-] [WrapperSimpleAppMain] INFO ServerManager Using the
Axis2 Repository : C:\wso2esb-1.7\.\repository
2008-08-22 12:36:29,299 [-] [WrapperSimpleAppMain] INFO ServerManager Using the
axis2.xml : C:\wso2esb-1.7\.\webapp\WEB-INF\classes\conf\axis2.xml
2008-08-22 12:36:29,299 [-] [WrapperSimpleAppMain] INFO ServerManager The serve
r name was not specified, defaulting to : pth-pc388336
2008-08-22 12:36:29,299 [-] [WrapperSimpleAppMain] INFO ServerManager The timeo
ut handler will run every : 15s
2008-08-22 12:36:29,814 [-] [WrapperSimpleAppMain] INFO SynapseInitializationMo
dule Initializing Synapse at : Fri Aug 22 12:36:29 IST 2008
2008-08-22 12:36:29,814 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Loading mediator extensions...
2008-08-22 12:36:30,299 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Initializing the Synapse configuration ...
2008-08-22 12:36:30,299 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
XMLConfigurationBuilder Generating the Synapse configuration model by parsing t
he XML configuration
2008-08-22 12:36:32,908 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
SynapseConfigurationBuilder Loaded Synapse configuration from : C:\wso2esb-1.7\
.\webapp/WEB-INF/classes/conf/synapse.xml
2008-08-22 12:36:32,924 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Deploying the Synapse service..
2008-08-22 12:36:32,924 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Synapse server name : pth-pc388336
2008-08-22 12:36:32,924 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Deploying Proxy services...
2008-08-22 12:36:32,924 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
SynapseInitializationModule Synapse initialized successfully...!
2008-08-22 12:36:33,064 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
HttpCoreNIOSSLSender Loading Identity Keystore from : webapp/WEB-INF/classes/co
nf/identity.jks
2008-08-22 12:36:33,095 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
HttpCoreNIOSSLSender Loading Trust Keystore from : webapp/WEB-INF/classes/conf/
trust.jks
2008-08-22 12:36:33,127 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
HttpCoreNIOSender HTTPS Sender starting
2008-08-22 12:36:33,127 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
HttpCoreNIOSender HTTP Sender starting
2008-08-22 12:36:33,127 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
VFSTransportSender VFS Sender started
2008-08-22 12:36:33,236 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
JMSSender JMS Sender started
2008-08-22 12:36:33,611 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
ServerManager Starting transport https on port 8243
2008-08-22 12:36:33,611 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
HttpCoreNIOSSLListener Loading Identity Keystore from : webapp/WEB-INF/classes/
conf/identity.jks
2008-08-22 12:36:33,611 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
HttpCoreNIOSSLListener Loading Trust Keystore from : webapp/WEB-INF/classes/con
f/trust.jks
2008-08-22 12:36:33,611 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
HttpCoreNIOListener HTTPS Listener starting on port : 8243
2008-08-22 12:36:33,611 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
ServerManager Starting transport http on port 8280
2008-08-22 12:36:33,627 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
HttpCoreNIOListener HTTP Listener starting on port : 8280
2008-08-22 12:36:33,627 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
ServerManager Starting transport vfs
2008-08-22 12:36:33,642 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
VFSTransportListener VFS Listener started
2008-08-22 12:36:33,642 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
ServerManager Starting transport mailto
2008-08-22 12:36:33,642 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
MailTransportListener MAILTO Listener started
2008-08-22 12:36:33,642 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
ServerManager Starting transport admin/https
2008-08-22 12:36:33,642 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
ServerManager Ready for processing
2008-08-22 12:36:35,142 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
ServiceBusManager [ESB] Start request completed
2008-08-22 12:36:36,080 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
TomcatServer Tomcat Server started at https://pth-pc388336:9444/esb
2008-08-22 12:36:36,080 [172.17.8.134-pth-pc388336] [WrapperSimpleAppMain] INFO
ServiceBus [ESB] WSO2 ESB started in 9813 ms
2008-08-22 12:37:29,501 [172.17.8.134-pth-pc388336] [http-9444-Processor4] INFO
LoginAdmin User : admin logged into the system
2008-08-22 12:42:57,963 [172.17.8.134-pth-pc388336] [http-9444-Processor2] INFO
LoginAdmin User : admin logged into the system
2008-08-22 12:43:55,696 [172.17.8.134-pth-pc388336] [http-9444-Processor3] INFO
ProxyService Building Axis service for Proxy service : testing
2008-08-22 12:43:55,806 [172.17.8.134-pth-pc388336] [http-9444-Processor3] INFO
ProxyService Adding service testing to the Axis2 configuration
2008-08-22 12:43:55,806 [172.17.8.134-pth-pc388336] [http-9444-Processor3] INFO
ProxyService Successfully created the Axis2 service for Proxy service : testing
2008-08-22 12:43:55,806 [172.17.8.134-pth-pc388336] [http-9444-Processor3] INFO
ProxyServiceAdmin Added proxy service : testing
2008-08-22 12:44:26,274 [172.17.8.134-pth-pc388336] [HttpServerWorker-1] ERROR S
erverWorker Invalid service : testing.testingHttpSoap11Endpoint
2008-08-22 12:46:42,584 [172.17.8.134-pth-pc388336] [HttpServerWorker-7] INFO L
ogMediator To: /soap/testing.testingHttpSoap11Endpoint,WSAction: http://tempuri.
org/HelloWorld,SOAPAction: http://tempuri.org/HelloWorld,MessageID: urn:uuid:D92
EB98FB3B9DB4A221219389402666,Direction: request,Envelope: <?xml version='1.0' en
coding='utf-8'?>
2008-08-22 12:46:42,599 [172.17.8.134-pth-pc388336] [HttpServerWorker-7] INFO T
imeoutHandler This engine will expire all callbacks after : 86400 seconds, irres
pective of the timeout action, after the specified or optional timeout
2008-08-22 12:46:52,599 [172.17.8.134-pth-pc388336] [HttpServerWorker-8] INFO L
ogMediator To: /soap/testing.testingHttpSoap11Endpoint,WSAction: http://tempuri.
org/HelloWorld,SOAPAction: http://tempuri.org/HelloWorld,MessageID: urn:uuid:D92
EB98FB3B9DB4A221219389412686,Direction: request,Envelope: <?xml version='1.0' en
coding='utf-8'?>
2008-08-22 12:49:32,721 [172.17.8.134-pth-pc388336] [http-9444-Processor2] INFO
LoginAdmin User : admin logged into the system
2008-08-22 12:49:44,424 [172.17.8.134-pth-pc388336] [http-9444-Processor2] INFO
LoginAdmin User : admin logged into the system
2008-08-22 12:50:04,861 [172.17.8.134-pth-pc388336] [http-9444-Processor2] INFO
LoginAdmin User : admin logged into the system
2008-08-22 12:50:32,439 [172.17.8.134-pth-pc388336] [http-9444-Processor4] INFO
LogAdmin Get Log4J configuration
2008-08-22 12:50:36,673 [172.17.8.134-pth-pc388336] [http-9444-Processor2] INFO
ProxyServiceAdmin Enabled statistics on proxy service : testing
2008-08-22 12:50:41,360 [172.17.8.134-pth-pc388336] [http-9444-Processor4] INFO
ProxyServiceAdmin Enabled tracing on proxy service : testing
2008-08-22 12:51:16,141 [172.17.8.134-pth-pc388336] [HttpServerWorker-9] INFO L
ogMediator To: /soap/testing.testingHttpSoap11Endpoint,WSAction: http://tempuri.
org/HelloWorld,SOAPAction: http://tempuri.org/HelloWorld,MessageID: urn:uuid:D92
EB98FB3B9DB4A221219389676238,Direction: request,Envelope: <?xml version='1.0' en
coding='utf-8'?>
2008-08-25 10:59:28,098 [172.17.8.134-pth-pc388336] [HttpServerWorker-12] INFO
LogMediator To: /soap/testing.testingHttpSoap11Endpoint,WSAction: http://tempuri
.org/HelloWorld,SOAPAction: http://tempuri.org/HelloWorld,MessageID: urn:uuid:D9
2EB98FB3B9DB4A221219642171814,Direction: request,Envelope: <?xml version='1.0' e
ncoding='utf-8'?><
/soap:Body>
please help in this regards
Kapil
Hi Kapil, Looking at your
Hi Kapil,
Looking at your error i see that this could possibly be a client side error which has resulted this error. Could you check out the following thread which might help you solve your probelm.
But looking at the log of the wso2 esb there is something wrong with the soap message that is comming into the esb. If you look at the following excerpt of your log;
2008-08-25 10:59:28,098 [172.17.8.134-pth-pc388336] [HttpServerWorker-12] INFO
LogMediator To: /soap/testing.testingHttpSoap11Endpoint,WSAction: http://tempuri
.org/HelloWorld,SOAPAction: http://tempuri.org/HelloWorld,MessageID: urn:uuid:D9
2EB98FB3B9DB4A221219642171814,Direction: request,Envelope: <?xml version='1.0' e
ncoding='utf-8'?><
/soap:Body>
The soap body is basically empty which cannot be. There is a tool called TCP Monitor which can track the incoming and outgoing soap messages. Could you kindly use TCP Monitor and direct your soap message to th TCP Monitor which in turn will forward the soap message to the wso2 ESB and post the output displayed in the TCP Monitor console here please?
Thank you
Dinuka