Re: Axis Clustering in OC4J Cluster

[Afkham Azeez]

If you are deploying totally stateless Axis2 Web services, meaning,
you do not rely on stuff that you store in the Axis2 context
hierarchy, and you do not require Axis2 cluster management, then you
do not have to enable Axis2 clustering.

When nodes go down, if you require the requests to be redirected to
other nodes, you must front your cluster with an appropriately
configured load balancer which supports failover. Simply deploying
Axis2 in a cluster does not mean this will happen.

Axis2 supports URL repositories. Hence all your nodes in the cluster
can point to that URL repository. Again, this does not require you to
enable Axis2 clustering.

State replication is one part of clustering. What we mean by 'state'
is stuff saved in the Axis2 COnfigurationCOntext, ServiceGroupContext
& ServiceContext. This can be useful for stateful Web services and
even other Axis2 configuration items such as modules, deployers and so
on. For example, the WSO2 Caching module supports caching of requests
to improve performance. It maintains the cache as a map in the
ConfigContext. As you can see, this map has to be replicated across
all Axis2 nodes in the cluster. In such a scenario, clustering state
replication comes in handy.

HTH
Azeez

On Fri, Jan 8, 2010 at 10:53 PM, Shailesh Potnis  wrote:
> Hi Azeez:
>
> Thank you for valuable input and links.  I think I went through the first
> link during my research and the axis2.xml clustering guide includes info
> from the second link.  I am still not clear about the end user use cases for
> stateless services.
>
> What I am trying to determine is:  Under what specific scenarios Axis2
> cluster deployed within OC4J cluster would provide additional value,  In
> other words what would be use cases for using Axis2 cluster within OC4J
> cluster that is fronted by OHS (Apache Web server) and a hardware load
> balancer?  I am trying to find this only for stateless services.
>
> During my discussion with some of my coworkers some possible use cases were
> discussed though I do not know if they would be provided by Axis2 Cluster.
> I would like to list them below:
>
> 1) In case a service is down in one Axis2 container, would Axis2 container
> redirect the request to another container -- I think the you provided
> (clustering at the servlet container level (HTTP session & request
> replication) is out of the scope of Axis2) indicates that this is not
> possible or out of scope. Correct me if this assumption is incorrect.
> 2) The second scenario is to be able to redeploy a single service (deployed
> with other services in a single J2EE war) using a central remote  repository
> -- this may not be related to cluster itself but would Axis clustering
> assist accomplishing this when OC4J standard deployment requires entire
> Axis2 war (potentially containing multiple services) to be redeployed.
> Would like to know whether this can be done using a central repository and
> Axis2 Admin console (with or without Axis2 cluster).
> 3) What are specific advantages of replicating ConfigurationContext,
> ServiceGroupContext & ServiceContext (For someone who has limited
> understanding of those objects) in Axis2 cluster for stateless services?
>
> Thank You and Best Regards
>
> Sincerely
>
> Shailesh
>
> 
> From: Afkham Azeez 
> To: axis-user@ws.apache.org
> Sent: Fri, January 8, 2010 12:30:00 AM
> Subject: Re: Axis Clustering in OC4J Cluster
>
> We have not tested Axis2 clustering on OC4J AFAIK.
> With respect to state replication, at the Axis2 level, we are only
> concerned about replicating the values stored in the Axis2
> ConfigurationContext, ServiceGroupContext & ServiceContext. We use
> default Java serialization, hence the entire object tree should be
> serializable for the replication to be successful. Please note that
> clustering at the servlet container level (HTTP session & request
> replication) is out of the scope of Axis2 and has to be handled by the
> respective servlet containers.
>
> For more details; refer to my articles;
> 1. Introduction to WSO2 Carbon Clustering
> http://wso2.org/library/articles/introduction-wso2-carbon-clustering
> 2. WSO2 Carbon Cluster Configuration Language
> http://wso2.org/library/articles/wso2-carbon-cluster-configuration-language
>
>
> Azeez
>
> On Fri, Jan 8, 2010 at 1:29 AM, Shailesh Potnis 
> wrote:
>>
>> Hi:
>>
>> I am going through a good deal of Axis2 documents and links.  I am trying
>> to determine if anyone has deployed Axis2 Cluster within OC4J cluster and
>> what is the experience.  I am planning to use it exclusively for stateless
>> web services.  Here are some specific questions:
>>
>> 1) What would be specific benefits of deploying the stateless web services
>> in Axis2 cluster when scalability would be provided by OC4J cluster?
>> 2) Are the Axis2 clustering benefits limited to deploying in Tomcat or are
>> useful in other app servers?
>> 3) In case a service is hung due to application or infrastructure is

Re: Axis2 1.5.1 service handling is very slow

[Amila Suriarachchi]

On Wed, Jan 13, 2010 at 5:21 PM, Martin Gerner <
martin.ger...@postgrad.manchester.ac.uk> wrote:

> Hi all,
>
> I'm running a simple web service which receives a string from the
> client, processes it and returns an array of custom objects (nothing
> complicated, they're just data holders containing a few ints, strings
> and booleans). While the actual serverside processing performed by my
> server code is performed very fast, the response times from the server
> are very large and seem to be linear in the number of returned objects.
>
> A short example: if I send a string to the server which results in 0
> objects being returned, the response from the server is received just a
> few milliseconds after the request is made. If the string is modified
> such that it returns one object, that increases to 8 seconds, and if it
> returns two objects it increases to 16 seconds. In all cases, I can see
> that the actual processing takes less than a second, so the web service
> java code that I've deployed is handling the requests quickly.
>
> All responses are small in size - the largest is ~900 bytes (so I can't
> imagine that it's an XML transformation issue). Using packet sniffers, I
> can see that the delay definitely is occurring on the server side (for
> the last example, I could see the POST packet going to the server, and
> then the response packet coming back 16 seconds later). Going by client
> and server log timings, I can see that the delay occurs after processing
> rather than before.
>
> I'm running axis2 1.5.1 with default settings, have tested it running on
> both the bundled SimpleAxisServer and Tomcat (both on a Debian server)
> and am using a very simple client based on code auto-generated by axis
> from the WSDL (running in Windows).
>
> Does anybody here have any clue as to what's causing the delays? It
> seems clear enough that it's something in the internal axis2 system, but
> as I'm quite new to axis2 I'm having difficulties locating the issue.
>

As a alternative you can use the contract first approach.
you can get the wsdl which is generated from the POJO and generate the
server side code for that.
then use the generated Skelton class to call your pojo.

thanks,
Amila.

>
> Best wishes,
> Martin Gerner
>



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: MTOM causes ADBException: Unexpected subelement

[Mike Borozdin]

I believe I have 1.5.1

Here are my libraries:
XmlSchema-1.4.3.jar bcprov-jdk16-144.jar
mail-1.4.jar
activation-1.1.jar  catalina-ant-5.0.28.jar 
mex-1.5.1.jar
axiom-api-1.2.8.jar commons-codec-1.3.jar   
neethi-2.0.4.jar
axiom-dom-1.2.8.jar commons-fileupload-1.2.jar  
rampart-core-1.4.jar
axiom-impl-1.2.8.jarcommons-httpclient-3.1.jar  
rampart-policy-1.4.jar
axis2-adb-1.5.1.jar commons-io-1.4.jar  
rampart-trust-1.4.jar
axis2-adb-codegen-1.5.1.jar commons-lang-2.3.jar
smack-3.0.4.jar
axis2-ant-plugin-1.5.1.jar  commons-logging-1.1.1.jar   
smackx-3.0.4.jar
axis2-clustering-1.5.1.jar  geronimo-annotation_1.0_spec-1.1.jar
soapmonitor-1.5.1.jar
axis2-codegen-1.5.1.jar geronimo-jaxws_2.1_spec-1.0.jar 
spring-2.5.1.jar
axis2-corba-1.5.1.jar   geronimo-saaj_1.3_spec-1.0.1.jar
spring-webmvc-2.5.1.jar
axis2-fastinfoset-1.5.1.jar geronimo-stax-api_1.0_spec-1.0.1.jar
standard-1.1.2.jar
axis2-java2wsdl-1.5.1.jar   geronimo-ws-metadata_2.0_spec-1.1.2.jar 
woden-api-1.0M8.jar
axis2-jaxbri-1.5.1.jar  httpcore-4.0.jar
woden-impl-dom-1.0M8.jar
axis2-jaxws-1.5.1.jar   jalopy-1.5rc3.jar   
wsdl4j-1.6.2.jar
axis2-jibx-1.5.1.jarjaxb-api-2.1.jar
wss4j-1.5.8.jar
axis2-json-1.5.1.jarjaxb-impl-2.1.7.jar 
wstx-asl-3.2.4.jar
axis2-kernel-1.5.1.jar  jaxb-xjc-2.1.7.jar  
xalan-2.7.0.jar
axis2-metadata-1.5.1.jarjaxen-1.1.1.jar 
xalan-2.7.1.jar
axis2-mtompolicy-1.5.1.jar  jettison-1.0-RC2.jar
xercesImpl-2.6.2.jar
axis2-saaj-1.5.1.jarjibx-bind-1.2.1.jar 
xml-apis-1.3.02.jar
axis2-spring-1.5.1.jar  jibx-run-1.2.1.jar  
xml-resolver-1.2.jar
axis2-transport-http-1.5.1.jar  jsr173_api.jar  
xmlbeans-2.3.0.jar
axis2-transport-local-1.5.1.jar jstl-1.1.2.jar  
xmlsec-1.4.1.jar
axis2-xmlbeans-1.5.1.jarjunit.jar
bcel-5.1.jarlog4j-1.2.15.jar

Were there some MTOM fixes after?

I will also try to regenerate the code without ADB.


On Jan 13, 2010, at 10:44 AM, Andreas Veithen wrote:

> I fixed multiple issues with MTOM and ADB after the 1.5 branch was
> created. Can you test this service with an Axis2 snapshot?
>
> Andreas
>
> On Tue, Jan 12, 2010 at 03:48, Mike Borozdin  wrote:
>> Hi!
>>
>> I have a Java Axis2 client that seems to encounter an error on the same 
>> exact XML structure if part of it is moved into an MTOM attachment.  The 
>> more complete stack is cited at the end.
>>
>> I have checked the WSDL and the response complies with the response XML for 
>> more info on the WSDL you can get it here. 
>> https://demo.docusign.net/api/3.0/api.asmx?WSDL
>>
>> The way the web service is configured is that it will only generate an MTOM 
>> attachment if the subelement exceeds a certain size.  I am attaching 
>> Example1 and Example2 which show working vs. not working.
>>
>> Axis Libraries used are 1.5.1.
>>
>> Does anyone have any idea what could be causing this?  The element that's 
>> triggering an exception is ...
>>
>> Thank you!
>>
>>
>> WORKING RESPONSE
>>
>> http://www.w3.org/2004/08/xop/include"; 
>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; 
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
>> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; 
>> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
>>  
>> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>
>> 
>>  
>> http://www.docusign.net/API/3.0/RequestStatusResponse
>>  urn:uuid:48cbb69a-9357-4745-bc1f-83c736ba1d90
>>  urn:uuid:04ade417-d078-4e64-a047-0bf7876b43fd
>>  
>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>>  
>>
>>  2010-01-11T20:41:51Z
>>  2010-01-11T20:46:51Z
>>
>>  
>> 
>> 
>>  http://www.docusign.net/API/3.0";>
>>
>>  
>>
>>  Signer
>>  nolongema...@gmail.com
>>  Mike Borozdin
>>  1
>>  2010-01-11T12:41:14.62
>>  2010-01-11T12:41:21.013
>>  2010-01-11T12:41:50.12
>>  
>>  Completed
>>  97.65.97.246
>>  unknown-web-user
>>  
>>
>>  93 S Jackson St
>>  #8329
>>  Seattle
>>  WA
>>  

Axis2: Class at University of South Florida (USF)

[Ayers, Sam]

Axis2 Users,

 

Dr. Chari at the University of South Florida (USF) has scheduled an
Apache Axis2 class (see link below).

 

I hope this isn't too "spammy" an announcement (as I am the instructor),
but upon reflection my thoughts were that this class is of direct
interest to folks on the Axis2 user list, and I believe is a good
promotion of this important technology.

 

I do hope you can come join us!

 

**

 

The Information Systems & Decision Sciences department at the University
of South Florida is organizing two continuing education classes in March
2010. These classes will be taught by experienced industry
professionals. I would appreciate if you could publicize this is in your
organization and let me know if there is any interest for these classes.
The two classes are listed below:

1. SOA Web Services Development with Apache Axis 2 and Eclipse
 

   Schedule: March 8 through March 12, 2010 
   8:15AM - 5:15PM
   Location: BSN 2406, University of South Florida, 4202 E. Fowler
Avenue, CIS 1040, Tampa, FL 33620-7800
   ... more information 
... 

2.  Leading Technology Projects with Scrum
 

 Schedule: March 10 through March 12, 2010 
 8:15AM - 5:15PM
 Location: BSN 120, University of South Florida, 4202 E. Fowler
Avenue, CIS 1040, Tampa, FL 33620-7800
 ... more information ...
 

 

Sam Ayers

Java Architect

Chase Paymentech

4200 West Cypress Street, Suite 500

Tampa, Florida  33607

Phone:  813-351-2274

 

 

--
Learn more about Chase Paymentech Solutions,LLC payment processing services at 
www.chasepaymentech.com.

THIS MESSAGE IS CONFIDENTIAL.  This e-mail message and any attachments are 
proprietary and confidential information intended only for the use of the 
recipient(s) named above.  If you are not the intended recipient, you may not 
print, distribute, or copy this message or any attachments.  If you have 
received this communication in error, please notify the sender by return e-mail 
and delete this message and any attachments from your computer.

Axis2: Replacing Services in the access URL

[Rahul Rulz]

Hi Everyone,
I have a query reg the URL to access the service..

Is there anyways to replace the 'services' as in 
http://localhost:8080/axis2/services/Myservice to 
"http://localhost:8080/axis2/serviceGrp1/Myservice"; ?
If am just renaming the services inside the deployment file to serviceGrp1 it 
is not able to locate the Myservice inside that..Is there a way to achieve 
this..?
Thanks,Raghav.

 


  

fastinfoset integration

[Victor]

Hello,

How can I integrate fastinfoset ( binary serialization) into the existing
web service?

Thank you,

-vl

Re: Axis2 1.5.1 service handling is very slow

[Andreas Veithen]

The issue seems to be as follows:

* For POJO services, Axis2 uses the JRE's bean introspector to detect
the properties of the POJOs.
* Following the Java Beans standard, the introspector attempts to find
BeanInfo classes corresponding to these POJOs. BeanInfo classes are
optional and rarely used in this context.
* Axis2 uses the service class loader to introspect the beans. This is
not a standard class loader, but a component specific to Axis2
(DeploymentClassLoader) which uses a different strategy to load the
classes. I had a quick look at the code, and it appears that in order
to load a class, it needs to scan all the JARs used by the service
archive.

Conclusion: in this case, Axis2 repeatedly attempts to load non
existing classes from a class loader that uses a suboptimal strategy
to load resources from JARs.

Unfortunately, I'm not very familiar with the POJO and class loading
parts of Axis2. Maybe some of the other developers can shed some light
on the following questions:

* Shouldn't the POJO code cache the results returned by the bean introspector?
* Why is the DeploymentClassLoader implemented in this way? My guess
is that it is to avoid file locking issues. Thus, it is only used when
hot deployment is enabled?

Andreas

On Wed, Jan 13, 2010 at 15:24, Martin Gerner
 wrote:
> I've attached a full thread dump. I'd greatly appreciate any help in
> determining the cause, as I'm quite a novice when it comes to Axis2 and its
> internal workings. CPU usage for the java process goes up to 100% when it's
> blocking.
>
> The top parts of a few dumps (taken at different times to get an idea about
> whether it's the same thing blocking):
>
> "HttpConnection-8080-1" prio=10 tid=0x08c06c00 nid=0x1c77 runnable
> [0x2e9fe000]
>  java.lang.Thread.State: RUNNABLE
>       at java.util.zip.Inflater.inflateBytes(Native Method)
>       at java.util.zip.Inflater.inflate(Inflater.java:223)
>       - locked <0xa65b86e0> (a java.util.zip.Inflater)
>       at
> java.util.zip.InflaterInputStream.read(InflaterInputStream.java:135)
>       at java.util.zip.ZipInputStream.read(ZipInputStream.java:146)
>       at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:92)
>       at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:70)
>       at
> org.apache.axis2.deployment.DeploymentClassLoader.getBytes(DeploymentClassLoader.java:198)
>       at
> org.apache.axis2.deployment.DeploymentClassLoader.getBytes(DeploymentClassLoader.java:178)
>       at
> org.apache.axis2.deployment.DeploymentClassLoader.findClass(DeploymentClassLoader.java:81)
>       at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
>       - locked <0x34220a70> (a
> org.apache.axis2.deployment.DeploymentClassLoader)
>       at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>       at java.beans.Introspector.instantiate(Introspector.java:1453)
>      [...]
>
>
> 
>
> "HttpConnection-8080-2" prio=10 tid=0x08a4fc00 nid=0x1cf6 runnable
> [0x2e9ad000]
>  java.lang.Thread.State: RUNNABLE
>       at java.util.zip.ZipInputStream.readFully(ZipInputStream.java:403)
>       at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:361)
>       at java.util.zip.ZipInputStream.read(ZipInputStream.java:148)
>       at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:92)
>       at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:70)
>       at
> org.apache.axis2.deployment.DeploymentClassLoader.getBytes(DeploymentClassLoader.java:198)
>       at
> org.apache.axis2.deployment.DeploymentClassLoader.getBytes(DeploymentClassLoader.java:178)
>       at
> org.apache.axis2.deployment.DeploymentClassLoader.findClass(DeploymentClassLoader.java:81)
>       at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
>       - locked <0x342afa70> (a
> org.apache.axis2.deployment.DeploymentClassLoader)
>       at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>       at java.beans.Introspector.instantiate(Introspector.java:1453)
>
> 
>
> Best wishes,
> Martin Gerner
>
> On 13/01/2010 12:30, Andreas Veithen wrote:
>>
>> The type of databinding cannot account for this delay. I would suggest
>> to take a thread dump and try to understand where Axis2 is blocking.
>>
>> Andreas
>>
>> On Wed, Jan 13, 2010 at 13:04, Bruno Simioni 
>> wrote:
>>
>>>
>>> Maybe using JAXB annotations on Java return objects, you can speed up the
>>> process.
>>>
>>> Bruno.
>>>
>>> On Wed, Jan 13, 2010 at 9:51 AM, Martin Gerner
>>>  wrote:
>>>

 Hi all,

 I'm running a simple web service which receives a string from the
 client, processes it and returns an array of custom objects (nothing
 complicated, they're just data holders containing a few ints, strings
 and booleans). While the actual serverside processing performed by my
 server code is performed very fast, the response times from the server
 are very large and seem to be linear in the number of returned objects.

 A short example: if I send a strin

Re: MTOM causes ADBException: Unexpected subelement

[Andreas Veithen]

I fixed multiple issues with MTOM and ADB after the 1.5 branch was
created. Can you test this service with an Axis2 snapshot?

Andreas

On Tue, Jan 12, 2010 at 03:48, Mike Borozdin  wrote:
> Hi!
>
> I have a Java Axis2 client that seems to encounter an error on the same exact 
> XML structure if part of it is moved into an MTOM attachment.  The more 
> complete stack is cited at the end.
>
> I have checked the WSDL and the response complies with the response XML for 
> more info on the WSDL you can get it here. 
> https://demo.docusign.net/api/3.0/api.asmx?WSDL
>
> The way the web service is configured is that it will only generate an MTOM 
> attachment if the subelement exceeds a certain size.  I am attaching Example1 
> and Example2 which show working vs. not working.
>
> Axis Libraries used are 1.5.1.
>
> Does anyone have any idea what could be causing this?  The element that's 
> triggering an exception is ...
>
> Thank you!
>
>
> WORKING RESPONSE
>
> http://www.w3.org/2004/08/xop/include"; 
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; 
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
>  
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>
>  
>   
> http://www.docusign.net/API/3.0/RequestStatusResponse
>   urn:uuid:48cbb69a-9357-4745-bc1f-83c736ba1d90
>   urn:uuid:04ade417-d078-4e64-a047-0bf7876b43fd
>   
> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>   
>     
>       2010-01-11T20:41:51Z
>       2010-01-11T20:46:51Z
>     
>   
>  
>  
>   http://www.docusign.net/API/3.0";>
>     
>       
>         
>           Signer
>           nolongema...@gmail.com
>           Mike Borozdin
>           1
>           2010-01-11T12:41:14.62
>           2010-01-11T12:41:21.013
>           2010-01-11T12:41:50.12
>           
>           Completed
>           97.65.97.246
>           unknown-web-user
>           
>             
>               93 S Jackson St
>               #8329
>               Seattle
>               WA
>               98102
>             
>             
>               X0LT+NRxPAvOz0U6NcLadg==
>             
>           
>           
>           
>             
>               SignHere
>               Signed
>               135
>               283
>               
>               
>               
>             
>             
>               DateSigned
>               Signed
>               683
>               333
>               
>               
>               1/11/2010
>             
>             
>               FullName
>               Signed
>               141
>               420
>               
>               
>               Mike Borozdin
>             
>             
>               Title
>               Signed
>               689
>               422
>               Job Title
>               
>               test
>             
>             
>               Company
>               Signed
>               664
>               616
>               
>               
>               test
>             
>             
>               Custom
>               Active
>               906
>               693
>               Business Type
>               Radio Button
>               
>             
>             
>               Custom
>               Active
>               1045
>               693
>               Business Type
>               Radio Button
>               
>             
>             
>               Custom
>               Signed
>               722
>               716
>               Business Type
>               Radio Button
>               X
>             
>             
>               Custom
>               Active
>               1045
>               718
>               Business Type
>               Radio Button
>               
>             
>             
>               FullName
>               Signed
>               658
>               752
>               
>               
>               Mike Borozdin
>             
>             
>               Title
>               Signed
>               1033
>               758
>               Job Title
>               
>               test
>             
>             
>               Custom
>               Signed
>               2010-01-11 12:41:51,841 DEBUG [httpclient.wire.content] - <<< ">
>               662
>               820
>               Full Address
>               Full Address
>               test
>             
>             
>               Custom
>               Signed
>               991
>               893
>               State
>               
> ;AK;AL;AR;AZ;CA;CO;CT;DE;DC;FL;GA;HI;IA;ID;IL;IN;KS;KY;LA;MA;MD;ME;MI;MN;MO;MS;MT;NC;NE;NV;NH;NJ;NM;NY;ND;OH;OK;OR;PA;PR;RI;SC;SD;TN;TX;UT;VA;VT;WA;WI;WV;WY
>            

Re: Static WSDL problems

[Vinicius Carvalho]

We are using Axis2 bundled with our server, using AxisServlet. Where
should this classes go? Do I still need a services.xml?

Regards

On Mon, Jan 11, 2010 at 12:49 PM, Yashvant chauhan  wrote:
> Hi Vinicius,
>
> As per my understanding you have to do folowing things,
> 1) create a WSDL first with proper schema...
> 2) generarte server side code using the Axis2 utility wsdl2Java and update
> the *Impl java file your business logic
> 3) create a war file with whole stuff and deploy it in a webserver
>
> once you completed above three steps your service should work.
>
> Regards,
> Yashvant
>
>
> On Mon, Jan 11, 2010 at 7:19 PM, Vinicius Carvalho 
> wrote:
>>
>> Hello there! We have an legacy WS built with Pojo based deployment
>> with Axis2. I was told that in order to override a few defaults from
>> axis (soap address, and some nillable properties on elements) one
>> should get the generated WSDL and copy it to the same folder that the
>> services.xml resides.
>>
>> Problem is: When we do that, Axis simply stop working. When I get the
>> exact WSDL that is generated through:
>> www.myserver.com/services/MyService?WSDL copy it to the folder of
>> services.xml, restart tomcat. Well things get messy, and very very
>> messy: One is that the marshalling stop working, parameters do not get
>> converted I get lots of \n on string parameters for instance.
>>
>> As I said, I was told that just putting the WSDL at the services.xml
>> folder should work, but it does not seems so.
>>
>> Any ideas please?
>>
>> Regards
>
>
>
> --
> 
> Yashvant Singh Chauhan
> Mobile- 09845277271
> Bangalore
>
> *
>

Re: MTOM causes ADBException: Unexpected subelement

[Mike Borozdin]

Maybe this will help also.  Here is a list of jars used by this servlet:

DocusignWS.jar  geronimo-stax-api_1.0_spec-1.0.1.jar
XmlSchema-1.4.3.jar geronimo-ws-metadata_2.0_spec-1.1.2.jar
activation-1.1.jar  httpcore-4.0.jar
axiom-api-1.2.8.jar jalopy-1.5rc3.jar
axiom-dom-1.2.8.jar jaxb-api-2.1.jar
axiom-impl-1.2.8.jarjaxb-impl-2.1.7.jar
axis2-adb-1.5.1.jar jaxb-xjc-2.1.7.jar
axis2-adb-codegen-1.5.1.jar jaxen-1.1.1.jar
axis2-ant-plugin-1.5.1.jar  jettison-1.0-RC2.jar
axis2-clustering-1.5.1.jar  jibx-bind-1.2.1.jar
axis2-codegen-1.5.1.jar jibx-run-1.2.1.jar
axis2-corba-1.5.1.jar   jsr173_api.jar
axis2-fastinfoset-1.5.1.jar jstl-1.1.2.jar
axis2-java2wsdl-1.5.1.jar   junit.jar
axis2-jaxbri-1.5.1.jar  log4j-1.2.15.jar
axis2-jaxws-1.5.1.jar   mail-1.4.jar
axis2-jibx-1.5.1.jarmex-1.5.1.jar
axis2-json-1.5.1.jarneethi-2.0.4.jar
axis2-kernel-1.5.1.jar  rampart-core-1.4.jar
axis2-metadata-1.5.1.jarrampart-policy-1.4.jar
axis2-mtompolicy-1.5.1.jar  rampart-trust-1.4.jar
axis2-saaj-1.5.1.jarsmack-3.0.4.jar
axis2-spring-1.5.1.jar  smackx-3.0.4.jar
axis2-transport-http-1.5.1.jar  soapmonitor-1.5.1.jar
axis2-transport-local-1.5.1.jar spring-2.5.1.jar
axis2-xmlbeans-1.5.1.jarspring-webmvc-2.5.1.jar
bcel-5.1.jarstandard-1.1.2.jar
bcprov-jdk16-144.jarwoden-api-1.0M8.jar
catalina-ant-5.0.28.jar woden-impl-dom-1.0M8.jar
commons-codec-1.3.jar   wsdl4j-1.6.2.jar
commons-fileupload-1.2.jar  wss4j-1.5.8.jar
commons-httpclient-3.1.jar  wstx-asl-3.2.4.jar
commons-io-1.4.jar  xalan-2.7.1.jar
commons-lang-2.3.jarxercesImpl-2.6.2.jar
commons-logging-1.1.1.jar   xml-apis-1.3.02.jar
geronimo-annotation_1.0_spec-1.1.jarxml-resolver-1.2.jar
geronimo-jaxws_2.1_spec-1.0.jar xmlbeans-2.3.0.jar
geronimo-saaj_1.3_spec-1.0.1.jarxmlsec-1.4.1.jar

Thanks!

On Jan 11, 2010, at 6:48 PM, Mike Borozdin wrote:

> Hi!
>
> I have a Java Axis2 client that seems to encounter an error on the same exact 
> XML structure if part of it is moved into an MTOM attachment.  The more 
> complete stack is cited at the end.
>
> I have checked the WSDL and the response complies with the response XML for 
> more info on the WSDL you can get it here. 
> https://demo.docusign.net/api/3.0/api.asmx?WSDL
>
> The way the web service is configured is that it will only generate an MTOM 
> attachment if the subelement exceeds a certain size.  I am attaching Example1 
> and Example2 which show working vs. not working.
>
> Axis Libraries used are 1.5.1.
>
> Does anyone have any idea what could be causing this?  The element that's 
> triggering an exception is ...
>
> Thank you!
>
>
> WORKING RESPONSE
>
> http://www.w3.org/2004/08/xop/include"; 
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; 
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
>  
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>
> 
>   
> http://www.docusign.net/API/3.0/RequestStatusResponse
>   urn:uuid:48cbb69a-9357-4745-bc1f-83c736ba1d90
>   urn:uuid:04ade417-d078-4e64-a047-0bf7876b43fd
>   
> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>   
> 
>   2010-01-11T20:41:51Z
>   2010-01-11T20:46:51Z
> 
>   
> 
> 
>   http://www.docusign.net/API/3.0";>
> 
>   
> 
>   Signer
>   nolongema...@gmail.com
>   Mike Borozdin
>   1
>   2010-01-11T12:41:14.62
>   2010-01-11T12:41:21.013
>   2010-01-11T12:41:50.12
>   
>   Completed
>   97.65.97.246
>   unknown-web-user
>   
> 
>   93 S Jackson St
>   #8329
>   Seattle
>   WA
>   98102
> 
> 
>   X0LT+NRxPAvOz0U6NcLadg==
> 
>   
>   
>   
> 
>   SignHere
>   Signed
>   135
>   283
>   
>   
>   
> 
> 
>   DateSigned
>   Signed
>   683
>   333
>   
>   
>   1/11/2010
> 
> 
>   FullName
> 

Re: [Axis2] Invoking Interdependent Web Services in a distributed system.

[Deepal jayasinghe]

There should be some issues with your service (or the server). Are you
invoking in-out operation or in-only operation ?. Because read time out
indicates client can connect to the server but server does not reply,
probably your service.

Thanks,
Deepal
> Hi ,
>
> Sorry for the late reply.
>
> As I stated earlier, I invoke two dependent WSs. First has the second
> one's business delegate (proxies ) to invoke the second.I have used
> axiom clients here.At remote debugging I get the following error
>
> org.apache.axis2.AxisFault: Read timed out
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:389)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:222)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:435)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
> at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:539)
> at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:520)
> at samples.test.service.axiom
> .WS1AXIOMClient.invoke(WS1AXIOMClient.java:68)
>
> In the Second WS invoke client I have set the following .
> options.setTimeOutInMilliSeconds(60).
>
> Your feed back highly appreciated.
>
> /BR
> Kanchana
>
> On Fri, Jan 8, 2010 at 2:13 PM, Afkham Azeez  > wrote:
>
> On Fri, Jan 8, 2010 at 1:44 PM, Kanchana Welagedara
> mailto:kancha...@gmail.com>> wrote:
> > Hi Deepal
> >
> > Sorry for not being very clear in previous mail.Here it is clearly.
> >
> > 1. Is there is a away of grouping couple of WS  which serve each
> other in a
> > sever.xml which are deployed in two deterrent containers ? If
> that is a
> > single container you have the option of service group for this
> correct?How
> > do we do it for a remote invoke ?
> >
> >
> Service groups cannot span across multiple Axis2 instances. I think if
> you tell us more about the problem you are trying to solve rather than
> explaining the solution you have in mind, we could propose a proper
> solution.
>
> >
> >>If you can please try to explain the question bit more clearly,
> so do
> >>you want to invoke a service (service2) from another service
> (service1)
> >>and send the final reply to the client ?
> >
> > 2. The above  I have done. Also How wanted to know about the session
> > management in across web servers too in such a scenario.
> >
> HTTP session replication should be handled at the HTTP server level
> and is out of the scope of Axis2. You will need to deploy Axis2 on an
> HTTP server which supports clustering.
>
>


-- 
Thank you!


http://blogs.deepal.org
http://deepal.org

Re: Building axis2-1.5.1 with maven2 fails, due to wrong [SOLVED]

[Patrick Kirsch]

Andreas Veithen schrieb:
> Now I remember. The problem occurs because java.net messed up their
> repository. On the trunk we fixed that [1]. You will have to do the
> same change to the 1.5.1 sources (or set up something in your Maven
> settings.xml to override the settings in Axis2).
> 
> Andreas
Thanks, that fixed it!

Patrick

RE: JAXB (2.1) and AXIS2 (1.5.1)

[Oded Onn]

Andreas,

Indeed, the problem was with the class loader and your suggestion solved the 
problem (I now create the JAXBContext with the service class loader. No need 
for the jaxb.index file btw).

Many thanks,
Oded 

-Original Message-
From: Andreas Veithen [mailto:andreas.veit...@gmail.com] 
Sent: Wednesday, January 13, 2010 14:35
To: axis-user@ws.apache.org
Subject: Re: JAXB (2.1) and AXIS2 (1.5.1)

This probably means that JAXB is trying to look up ObjectFactory and
jaxb.index from the wrong class loader. This may happen if the JAXB
JARs are loaded by the application class loader, while the generated
code is loaded from the service class loader. One solution would be to
use the variant of the JAXBContext.newInstance method that takes a
class loader as parameter.

Andreas

On Wed, Jan 13, 2010 at 13:28, Oded Onn  wrote:
> Hi,
>
>
>
> I am deploying a WS under tomcat 5.5 and Java JDK is 1.5.0_08. I use some
> external jars that include code which was generated with JAXB 2.1 (using Ant
> XJC Task). The code is built from the xml schema without any error using the
> same JAXB libs as used in Axis2:
>
> jaxb-xjc-2.1.7.jar
>
> activation-1.1.jar
>
> jaxb-api-2.1.jar
>
> jaxb-impl-2.1.7.jar
>
> jsr173_api.jar
>
>
>
> When calls (client requests) to the server are made, the code try to get a
> marshaller for a class that is derived from the schema
>
>
>
> myMarshaller =
> JAXBContext.newInstance(fromShema.class.getPackage().getName()).createMarshaller();
>
>
>
> Upon creation of the JAXBContext, the server throws the exception:
>
>
>
> java.lang.ExceptionInInitializerError
>
> . . .
>
> Caused by: java.lang.IllegalStateException: javax.xml.bind.JAXBException:
> "com.mobixell.mwc.acquisitionconfiguration.schema" doesnt contain
> ObjectFactory.class or jaxb.index
>
> . . .
>
> Caused by: javax.xml.bind.JAXBException:
> "com.mobixell.mwc.acquisitionconfiguration.schema" doesnt contain
> ObjectFactory.class or jaxb.index
>
>     at
> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:183)
>
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
>     at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
>     at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
>     at java.lang.reflect.Method.invoke(Method.java:585)
>
>     at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:133)
>
>     at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
>
>     at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372)
>
>     at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337)
>
>     at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:244)
>
>     at
> com.mobixell.mwc.psm.AcquisitionDatabase.(AcquisitionDatabase.java:69)
>
>     ... 14 more
>
>
>
> Originally, the auto-generated jars were not created with the jaxb.index
> file. I understand that it is not a must to have a jaxb.index if you have an
> ObjectFactory class. However, I tried adding the appropriate jaxb.index
> files anyway, and it still doesn't work.
>
>
>
> Any ideas why Axis2 has problems with the JAXB generated classes? I am
> really lost on that one and would appreciate any help.
>
>
>
>
>
> Thanks!
>
> Oded
>
>

Re: Axis2 1.5.1 service handling is very slow

[Martin Gerner]

I've attached a full thread dump. I'd greatly appreciate any help in 
determining the cause, as I'm quite a novice when it comes to Axis2 and 
its internal workings. CPU usage for the java process goes up to 100% 
when it's blocking.


The top parts of a few dumps (taken at different times to get an idea 
about whether it's the same thing blocking):


"HttpConnection-8080-1" prio=10 tid=0x08c06c00 nid=0x1c77 runnable 
[0x2e9fe000]

  java.lang.Thread.State: RUNNABLE
   at java.util.zip.Inflater.inflateBytes(Native Method)
   at java.util.zip.Inflater.inflate(Inflater.java:223)
   - locked <0xa65b86e0> (a java.util.zip.Inflater)
   at 
java.util.zip.InflaterInputStream.read(InflaterInputStream.java:135)

   at java.util.zip.ZipInputStream.read(ZipInputStream.java:146)
   at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:92)
   at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:70)
   at 
org.apache.axis2.deployment.DeploymentClassLoader.getBytes(DeploymentClassLoader.java:198)
   at 
org.apache.axis2.deployment.DeploymentClassLoader.getBytes(DeploymentClassLoader.java:178)
   at 
org.apache.axis2.deployment.DeploymentClassLoader.findClass(DeploymentClassLoader.java:81)

   at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
   - locked <0x34220a70> (a 
org.apache.axis2.deployment.DeploymentClassLoader)

   at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
   at java.beans.Introspector.instantiate(Introspector.java:1453)
  [...]




"HttpConnection-8080-2" prio=10 tid=0x08a4fc00 nid=0x1cf6 runnable 
[0x2e9ad000]

  java.lang.Thread.State: RUNNABLE
   at java.util.zip.ZipInputStream.readFully(ZipInputStream.java:403)
   at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:361)
   at java.util.zip.ZipInputStream.read(ZipInputStream.java:148)
   at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:92)
   at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:70)
   at 
org.apache.axis2.deployment.DeploymentClassLoader.getBytes(DeploymentClassLoader.java:198)
   at 
org.apache.axis2.deployment.DeploymentClassLoader.getBytes(DeploymentClassLoader.java:178)
   at 
org.apache.axis2.deployment.DeploymentClassLoader.findClass(DeploymentClassLoader.java:81)

   at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
   - locked <0x342afa70> (a 
org.apache.axis2.deployment.DeploymentClassLoader)

   at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
   at java.beans.Introspector.instantiate(Introspector.java:1453)



Best wishes,
Martin Gerner

On 13/01/2010 12:30, Andreas Veithen wrote:

The type of databinding cannot account for this delay. I would suggest
to take a thread dump and try to understand where Axis2 is blocking.

Andreas

On Wed, Jan 13, 2010 at 13:04, Bruno Simioni  wrote:
  

Maybe using JAXB annotations on Java return objects, you can speed up the
process.

Bruno.

On Wed, Jan 13, 2010 at 9:51 AM, Martin Gerner
 wrote:


Hi all,

I'm running a simple web service which receives a string from the
client, processes it and returns an array of custom objects (nothing
complicated, they're just data holders containing a few ints, strings
and booleans). While the actual serverside processing performed by my
server code is performed very fast, the response times from the server
are very large and seem to be linear in the number of returned objects.

A short example: if I send a string to the server which results in 0
objects being returned, the response from the server is received just a
few milliseconds after the request is made. If the string is modified
such that it returns one object, that increases to 8 seconds, and if it
returns two objects it increases to 16 seconds. In all cases, I can see
that the actual processing takes less than a second, so the web service
java code that I've deployed is handling the requests quickly.

All responses are small in size - the largest is ~900 bytes (so I can't
imagine that it's an XML transformation issue). Using packet sniffers, I
can see that the delay definitely is occurring on the server side (for
the last example, I could see the POST packet going to the server, and
then the response packet coming back 16 seconds later). Going by client
and server log timings, I can see that the delay occurs after processing
rather than before.

I'm running axis2 1.5.1 with default settings, have tested it running on
both the bundled SimpleAxisServer and Tomcat (both on a Debian server)
and am using a very simple client based on code auto-generated by axis
from the WSDL (running in Windows).

Does anybody here have any clue as to what's causing the delays? It
seems clear enough that it's something in the internal axis2 system, but
as I'm quite new to axis2 I'm having difficulties locating the issue.

Best wishes,
Martin Gerner
  




--
Martin Gerner
Faculty of Life Sciences
Michael S

Re: Building axis2-1.5.1 with maven2 fails, due to wrong repos?

[Andreas Veithen]

Now I remember. The problem occurs because java.net messed up their
repository. On the trunk we fixed that [1]. You will have to do the
same change to the 1.5.1 sources (or set up something in your Maven
settings.xml to override the settings in Axis2).

Andreas

[1] 
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/parent/pom.xml?r1=835405&r2=835404&pathrev=835405

On Wed, Jan 13, 2010 at 14:01, Patrick Kirsch  wrote:
> Andreas Veithen schrieb:
>> Maybe it helps to empty the
>> /home/kadmin/.m2/repository/org/apache/ws/commons/axiom folder to
>> force Maven to download the corrupted artifacts again.
> Well it turns out that:
> /home/kadmin/.m2/repository/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar
> contains:
> 301 Moved Permanently
> 
> Moved Permanently
> The document has moved  href="http://download.java.net/maven/1/org.apache.ws.commons.axiom/jars/axiom-api-1.2.8.jar";>here.
> 
> Apache Server at maven-repository.dev.java.net Port 443
>
> BUT, the given redirect results on the host download.java.net in 404:
>
> Not Found
> The requested object does not exist on this server. The link you
> followed is either outdated, inaccurate, or the server has been
> instructed not to let you have it.
>
> Now, I see none of the requested mirrors does provide the axiom package
> in this version 1.2.8.
> requested are: http://ws.zones.apache.org/repository2,
> http://tomcat.apache.org/dev/dist/m2-repository,
> http://repo1.maven.org/eclipse.
>
> See:
> http://ws.zones.apache.org/repository2/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar
> [INFO] Unable to find resource
> 'org.apache.ws.commons.axiom:axiom-api:jar:1.2.8' in repository ws-zones
> (http://ws.zones.apache.org/repository2)
> Downloading:
> http://ws.zones.apache.org/repository2/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar
> [INFO] Unable to find resource
> 'org.apache.ws.commons.axiom:axiom-api:jar:1.2.8' in repository
> apache-ws-snapshots2 (http://ws.zones.apache.org/repository2)
> Downloading:
> http://tomcat.apache.org/dev/dist/m2-repository/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar
> [INFO] Unable to find resource
> 'org.apache.ws.commons.axiom:axiom-api:jar:1.2.8' in repository
> tomcat-repository (http://tomcat.apache.org/dev/dist/m2-repository)
> Downloading:
> http://repo1.maven.org/eclipse/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar
> [INFO] Unable to find resource
> 'org.apache.ws.commons.axiom:axiom-api:jar:1.2.8' in repository
> eclipse-repo (http://repo1.maven.org/eclipse)
> Downloading:
> https://maven-repository.dev.java.net/nonav/repository//org.apache.ws.commons.axiom/jars/axiom-api-1.2.8.jar
> 373b downloaded  (axiom-api-1.2.8.jar)
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '047b09bdb4cff4f03d94f2390bc3fa79c659ec99'; remote = ' Downloading:
> https://maven-repository.dev.java.net/nonav/repository//org.apache.ws.commons.axiom/jars/axiom-api-1.2.8.jar
> 373b downloaded  (axiom-api-1.2.8.jar)
>
> Does anyone catches this problem?
>>
>> Andreas
> Regards,
>  Patrick
>

Re: Building axis2-1.5.1 with maven2 fails, due to wrong repos?

[Patrick Kirsch]

Andreas Veithen schrieb:
> Maybe it helps to empty the
> /home/kadmin/.m2/repository/org/apache/ws/commons/axiom folder to
> force Maven to download the corrupted artifacts again.
Well it turns out that:
/home/kadmin/.m2/repository/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar
contains:
301 Moved Permanently

Moved Permanently
The document has moved http://download.java.net/maven/1/org.apache.ws.commons.axiom/jars/axiom-api-1.2.8.jar";>here.

Apache Server at maven-repository.dev.java.net Port 443

BUT, the given redirect results on the host download.java.net in 404:

Not Found
The requested object does not exist on this server. The link you
followed is either outdated, inaccurate, or the server has been
instructed not to let you have it.

Now, I see none of the requested mirrors does provide the axiom package
in this version 1.2.8.
requested are: http://ws.zones.apache.org/repository2,
http://tomcat.apache.org/dev/dist/m2-repository,
http://repo1.maven.org/eclipse.

See:
http://ws.zones.apache.org/repository2/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar
[INFO] Unable to find resource
'org.apache.ws.commons.axiom:axiom-api:jar:1.2.8' in repository ws-zones
(http://ws.zones.apache.org/repository2)
Downloading:
http://ws.zones.apache.org/repository2/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar
[INFO] Unable to find resource
'org.apache.ws.commons.axiom:axiom-api:jar:1.2.8' in repository
apache-ws-snapshots2 (http://ws.zones.apache.org/repository2)
Downloading:
http://tomcat.apache.org/dev/dist/m2-repository/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar
[INFO] Unable to find resource
'org.apache.ws.commons.axiom:axiom-api:jar:1.2.8' in repository
tomcat-repository (http://tomcat.apache.org/dev/dist/m2-repository)
Downloading:
http://repo1.maven.org/eclipse/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar
[INFO] Unable to find resource
'org.apache.ws.commons.axiom:axiom-api:jar:1.2.8' in repository
eclipse-repo (http://repo1.maven.org/eclipse)
Downloading:
https://maven-repository.dev.java.net/nonav/repository//org.apache.ws.commons.axiom/jars/axiom-api-1.2.8.jar
373b downloaded  (axiom-api-1.2.8.jar)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'047b09bdb4cff4f03d94f2390bc3fa79c659ec99'; remote = 'https://maven-repository.dev.java.net/nonav/repository//org.apache.ws.commons.axiom/jars/axiom-api-1.2.8.jar
373b downloaded  (axiom-api-1.2.8.jar)

Does anyone catches this problem?
> 
> Andreas
Regards,
 Patrick

Re: Building axis2-1.5.1 with maven2 fails, due to wrong repos?

[Andreas Veithen]

Maybe it helps to empty the
/home/kadmin/.m2/repository/org/apache/ws/commons/axiom folder to
force Maven to download the corrupted artifacts again.

Andreas

On Wed, Jan 13, 2010 at 12:14, Patrick Kirsch  wrote:
> Hey,
>  I know it is a silly question but I'm facing the following problem:
> when I'm trying to build axis-1.5.1 from the source with maven2 (mvn
> install as in /1/) it fails due to it could not download the dependencies.
>
>  - See:
>
> http://ws.zones.apache.org/repository2/org/apache/maven/shared/file-management/1.2/file-management-1.2.pom
> [INFO] Unable to find resource
> 'org.apache.maven.shared:file-management:pom:1.2' in repository ws-zones
> (http://ws.zones.apache.org/repository2)
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/shared/file-management/1.2/file-management-1.2.pom
> Downloading:
> http://ws.zones.apache.org/repository2/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom
> [INFO] Unable to find resource
> 'org.apache.maven.shared:maven-shared-io:pom:1.1' in repository ws-zones
> (http://ws.zones.apache.org/repository2)
> Downloading:
> http://ws.zones.apache.org/repository2/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom
> [INFO] Unable to find resource
> 'org.apache.maven.shared:maven-shared-io:pom:1.1' in repository
> apache-ws-snapshots2 (http://ws.zones.apache.org/repository2)
> Downloading:
> http://tomcat.apache.org/dev/dist/m2-repository/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom
> [INFO] Unable to find resource
> 'org.apache.maven.shared:maven-shared-io:pom:1.1' in repository
> tomcat-repository (http://tomcat.apache.org/dev/dist/m2-repository)
> Downloading:
> http://repo1.maven.org/eclipse/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom
> [INFO] Unable to find resource
> 'org.apache.maven.shared:maven-shared-io:pom:1.1' in repository
> eclipse-repo (http://repo1.maven.org/eclipse)
> etc. ...
>
>  - afterwards it stops with:
>
>
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] Compilation failure
>
> error: error reading
> /home/kadmin/.m2/repository/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar;
> error in opening zip file
> error: error reading
> /home/kadmin/.m2/repository/org/apache/ws/commons/axiom/axiom-impl/1.2.8/axiom-impl-1.2.8.jar;
> error in opening zip file
> error: error reading
>
> I guess I'm using a wrong repository although I did not change anything
> of the defaults coming along with axis2-1.5.1-src.zip.
>
> This leads me to another question,
>  how did you set up your axis2 build environment?
>
>
> (I'm aware of Maven HowTos, eg.
> http://maven.apache.org/run-maven/index.html and
> http://ws.apache.org/axis2/maven-help.html /1/, but they didn't helped
> me further)
>
> Thanks and Regards,
>  Patrick
>

Re: JAXB (2.1) and AXIS2 (1.5.1)

[Andreas Veithen]

This probably means that JAXB is trying to look up ObjectFactory and
jaxb.index from the wrong class loader. This may happen if the JAXB
JARs are loaded by the application class loader, while the generated
code is loaded from the service class loader. One solution would be to
use the variant of the JAXBContext.newInstance method that takes a
class loader as parameter.

Andreas

On Wed, Jan 13, 2010 at 13:28, Oded Onn  wrote:
> Hi,
>
>
>
> I am deploying a WS under tomcat 5.5 and Java JDK is 1.5.0_08. I use some
> external jars that include code which was generated with JAXB 2.1 (using Ant
> XJC Task). The code is built from the xml schema without any error using the
> same JAXB libs as used in Axis2:
>
> jaxb-xjc-2.1.7.jar
>
> activation-1.1.jar
>
> jaxb-api-2.1.jar
>
> jaxb-impl-2.1.7.jar
>
> jsr173_api.jar
>
>
>
> When calls (client requests) to the server are made, the code try to get a
> marshaller for a class that is derived from the schema
>
>
>
> myMarshaller =
> JAXBContext.newInstance(fromShema.class.getPackage().getName()).createMarshaller();
>
>
>
> Upon creation of the JAXBContext, the server throws the exception:
>
>
>
> java.lang.ExceptionInInitializerError
>
> . . .
>
> Caused by: java.lang.IllegalStateException: javax.xml.bind.JAXBException:
> "com.mobixell.mwc.acquisitionconfiguration.schema" doesnt contain
> ObjectFactory.class or jaxb.index
>
> . . .
>
> Caused by: javax.xml.bind.JAXBException:
> "com.mobixell.mwc.acquisitionconfiguration.schema" doesnt contain
> ObjectFactory.class or jaxb.index
>
>     at
> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:183)
>
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
>     at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
>     at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
>     at java.lang.reflect.Method.invoke(Method.java:585)
>
>     at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:133)
>
>     at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
>
>     at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372)
>
>     at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337)
>
>     at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:244)
>
>     at
> com.mobixell.mwc.psm.AcquisitionDatabase.(AcquisitionDatabase.java:69)
>
>     ... 14 more
>
>
>
> Originally, the auto-generated jars were not created with the jaxb.index
> file. I understand that it is not a must to have a jaxb.index if you have an
> ObjectFactory class. However, I tried adding the appropriate jaxb.index
> files anyway, and it still doesn’t work.
>
>
>
> Any ideas why Axis2 has problems with the JAXB generated classes? I am
> really lost on that one and would appreciate any help.
>
>
>
>
>
> Thanks!
>
> Oded
>
>

Re: Axis2 1.5.1 service handling is very slow

[Andreas Veithen]

The type of databinding cannot account for this delay. I would suggest
to take a thread dump and try to understand where Axis2 is blocking.

Andreas

On Wed, Jan 13, 2010 at 13:04, Bruno Simioni  wrote:
> Maybe using JAXB annotations on Java return objects, you can speed up the
> process.
>
> Bruno.
>
> On Wed, Jan 13, 2010 at 9:51 AM, Martin Gerner
>  wrote:
>>
>> Hi all,
>>
>> I'm running a simple web service which receives a string from the
>> client, processes it and returns an array of custom objects (nothing
>> complicated, they're just data holders containing a few ints, strings
>> and booleans). While the actual serverside processing performed by my
>> server code is performed very fast, the response times from the server
>> are very large and seem to be linear in the number of returned objects.
>>
>> A short example: if I send a string to the server which results in 0
>> objects being returned, the response from the server is received just a
>> few milliseconds after the request is made. If the string is modified
>> such that it returns one object, that increases to 8 seconds, and if it
>> returns two objects it increases to 16 seconds. In all cases, I can see
>> that the actual processing takes less than a second, so the web service
>> java code that I've deployed is handling the requests quickly.
>>
>> All responses are small in size - the largest is ~900 bytes (so I can't
>> imagine that it's an XML transformation issue). Using packet sniffers, I
>> can see that the delay definitely is occurring on the server side (for
>> the last example, I could see the POST packet going to the server, and
>> then the response packet coming back 16 seconds later). Going by client
>> and server log timings, I can see that the delay occurs after processing
>> rather than before.
>>
>> I'm running axis2 1.5.1 with default settings, have tested it running on
>> both the bundled SimpleAxisServer and Tomcat (both on a Debian server)
>> and am using a very simple client based on code auto-generated by axis
>> from the WSDL (running in Windows).
>>
>> Does anybody here have any clue as to what's causing the delays? It
>> seems clear enough that it's something in the internal axis2 system, but
>> as I'm quite new to axis2 I'm having difficulties locating the issue.
>>
>> Best wishes,
>> Martin Gerner
>
>

JAXB (2.1) and AXIS2 (1.5.1)

[Oded Onn]

Hi,

 

I am deploying a WS under tomcat 5.5 and Java JDK is 1.5.0_08. I use
some external jars that include code which was generated with JAXB 2.1
(using Ant XJC Task). The code is built from the xml schema without any
error using the same JAXB libs as used in Axis2:

jaxb-xjc-2.1.7.jar

activation-1.1.jar

jaxb-api-2.1.jar

jaxb-impl-2.1.7.jar

jsr173_api.jar

 

When calls (client requests) to the server are made, the code try to get
a marshaller for a class that is derived from the schema

 

myMarshaller =
JAXBContext.newInstance(fromShema.class.getPackage().getName()).createMa
rshaller();

 

Upon creation of the JAXBContext, the server throws the exception:

 

java.lang.ExceptionInInitializerError

. . .

Caused by: java.lang.IllegalStateException:
javax.xml.bind.JAXBException:
"com.mobixell.mwc.acquisitionconfiguration.schema" doesnt contain
ObjectFactory.class or jaxb.index

. . .

Caused by: javax.xml.bind.JAXBException:
"com.mobixell.mwc.acquisitionconfiguration.schema" doesnt contain
ObjectFactory.class or jaxb.index

at
com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:183
)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at
javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:133)

at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)

at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372)

at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337)

at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:244)

at
com.mobixell.mwc.psm.AcquisitionDatabase.(AcquisitionDatabase.java
:69)

... 14 more

 

Originally, the auto-generated jars were not created with the jaxb.index
file. I understand that it is not a must to have a jaxb.index if you
have an ObjectFactory class. However, I tried adding the appropriate
jaxb.index files anyway, and it still doesn't work.

 

Any ideas why Axis2 has problems with the JAXB generated classes? I am
really lost on that one and would appreciate any help.

 

 

Thanks!

Oded

 

Re: Axis2 1.5.1 service handling is very slow

[Bruno Simioni]

Maybe using JAXB annotations on Java return objects, you can speed up the
process.

Bruno.

On Wed, Jan 13, 2010 at 9:51 AM, Martin Gerner <
martin.ger...@postgrad.manchester.ac.uk> wrote:

> Hi all,
>
> I'm running a simple web service which receives a string from the
> client, processes it and returns an array of custom objects (nothing
> complicated, they're just data holders containing a few ints, strings
> and booleans). While the actual serverside processing performed by my
> server code is performed very fast, the response times from the server
> are very large and seem to be linear in the number of returned objects.
>
> A short example: if I send a string to the server which results in 0
> objects being returned, the response from the server is received just a
> few milliseconds after the request is made. If the string is modified
> such that it returns one object, that increases to 8 seconds, and if it
> returns two objects it increases to 16 seconds. In all cases, I can see
> that the actual processing takes less than a second, so the web service
> java code that I've deployed is handling the requests quickly.
>
> All responses are small in size - the largest is ~900 bytes (so I can't
> imagine that it's an XML transformation issue). Using packet sniffers, I
> can see that the delay definitely is occurring on the server side (for
> the last example, I could see the POST packet going to the server, and
> then the response packet coming back 16 seconds later). Going by client
> and server log timings, I can see that the delay occurs after processing
> rather than before.
>
> I'm running axis2 1.5.1 with default settings, have tested it running on
> both the bundled SimpleAxisServer and Tomcat (both on a Debian server)
> and am using a very simple client based on code auto-generated by axis
> from the WSDL (running in Windows).
>
> Does anybody here have any clue as to what's causing the delays? It
> seems clear enough that it's something in the internal axis2 system, but
> as I'm quite new to axis2 I'm having difficulties locating the issue.
>
> Best wishes,
> Martin Gerner
>

Axis2 1.5.1 service handling is very slow

[Martin Gerner]

Hi all,

I'm running a simple web service which receives a string from the
client, processes it and returns an array of custom objects (nothing
complicated, they're just data holders containing a few ints, strings
and booleans). While the actual serverside processing performed by my
server code is performed very fast, the response times from the server
are very large and seem to be linear in the number of returned objects.

A short example: if I send a string to the server which results in 0
objects being returned, the response from the server is received just a
few milliseconds after the request is made. If the string is modified
such that it returns one object, that increases to 8 seconds, and if it
returns two objects it increases to 16 seconds. In all cases, I can see
that the actual processing takes less than a second, so the web service
java code that I've deployed is handling the requests quickly.

All responses are small in size - the largest is ~900 bytes (so I can't
imagine that it's an XML transformation issue). Using packet sniffers, I
can see that the delay definitely is occurring on the server side (for
the last example, I could see the POST packet going to the server, and
then the response packet coming back 16 seconds later). Going by client
and server log timings, I can see that the delay occurs after processing
rather than before.

I'm running axis2 1.5.1 with default settings, have tested it running on
both the bundled SimpleAxisServer and Tomcat (both on a Debian server)
and am using a very simple client based on code auto-generated by axis
from the WSDL (running in Windows).

Does anybody here have any clue as to what's causing the delays? It
seems clear enough that it's something in the internal axis2 system, but
as I'm quite new to axis2 I'm having difficulties locating the issue.

Best wishes,
Martin Gerner

Building axis2-1.5.1 with maven2 fails, due to wrong repos?

[Patrick Kirsch]

Hey,
 I know it is a silly question but I'm facing the following problem:
when I'm trying to build axis-1.5.1 from the source with maven2 (mvn
install as in /1/) it fails due to it could not download the dependencies.

 - See:

http://ws.zones.apache.org/repository2/org/apache/maven/shared/file-management/1.2/file-management-1.2.pom
[INFO] Unable to find resource
'org.apache.maven.shared:file-management:pom:1.2' in repository ws-zones
(http://ws.zones.apache.org/repository2)
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/shared/file-management/1.2/file-management-1.2.pom
Downloading:
http://ws.zones.apache.org/repository2/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom
[INFO] Unable to find resource
'org.apache.maven.shared:maven-shared-io:pom:1.1' in repository ws-zones
(http://ws.zones.apache.org/repository2)
Downloading:
http://ws.zones.apache.org/repository2/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom
[INFO] Unable to find resource
'org.apache.maven.shared:maven-shared-io:pom:1.1' in repository
apache-ws-snapshots2 (http://ws.zones.apache.org/repository2)
Downloading:
http://tomcat.apache.org/dev/dist/m2-repository/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom
[INFO] Unable to find resource
'org.apache.maven.shared:maven-shared-io:pom:1.1' in repository
tomcat-repository (http://tomcat.apache.org/dev/dist/m2-repository)
Downloading:
http://repo1.maven.org/eclipse/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom
[INFO] Unable to find resource
'org.apache.maven.shared:maven-shared-io:pom:1.1' in repository
eclipse-repo (http://repo1.maven.org/eclipse)
etc. ...

 - afterwards it stops with:


[ERROR] BUILD FAILURE
[INFO]

[INFO] Compilation failure

error: error reading
/home/kadmin/.m2/repository/org/apache/ws/commons/axiom/axiom-api/1.2.8/axiom-api-1.2.8.jar;
error in opening zip file
error: error reading
/home/kadmin/.m2/repository/org/apache/ws/commons/axiom/axiom-impl/1.2.8/axiom-impl-1.2.8.jar;
error in opening zip file
error: error reading

I guess I'm using a wrong repository although I did not change anything
of the defaults coming along with axis2-1.5.1-src.zip.

This leads me to another question,
 how did you set up your axis2 build environment?


(I'm aware of Maven HowTos, eg.
http://maven.apache.org/run-maven/index.html and
http://ws.apache.org/axis2/maven-help.html /1/, but they didn't helped
me further)

Thanks and Regards,
 Patrick

axis2 1.4 -> 1.5.1 problem (EPR not found)

[Marc Noma]

Hi everybody

We recently updated our project from axis2 1.4 to 1.5.1 and do now experience a 
strange problem.

With version 1.4 when requesting (e.g. for a test service "echows")
http://127.0.0.1:8080/axis2/services/echows
the answer is a web page that provides a service description, a list with all 
service operations and a link to the wsdl. After migrating to 1.5.1 the answer 
now is an error:



The endpoint reference (EPR) for the Operation not found is 
/axis2/services/echows and the WSA Action = null



The service still works, e.g. when called with SoapUI, and the following link 
still provides the wsdl file successfully.
http://127.0.0.1:8080/axis2/services/echows?wsdl
The webservice code base is untouched and the configurations we did in 
axis2.xml for 1.4 have been migrated to 1.5.1 and should be the same. 

When searching for "EPR not found" problems I was not able to find information 
that seemed related to our problem with the webservice description page no 
longer showing up.

Any ideas what's going wrong here? Thanks in advance for any help!

Marc



  

Custom SOAP fault

[lad alex]

Hello
I'm using Axis client  1.2 and trying to catch custom soap fault
defined in wsdl. SOAP service is not Axis-driven one but i can control it .
It seems WSDL2Java  properly creates an exception class and
inherit it from org.apache.axis.AxisFault. But caught exception object
is AxisFault and property 'detail' is null instead of MyException   
object.  AxisFault.getFaultDetails() contains DOM tree of
 tag but custom exception object is not 
   
mapped to  tag.
Here is relevant part of wsdl

 
http://schemas.xmlsoap.org/wsdl/soap/";
   name="myservice"  
   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
   xmlns:tns="MyModule"  
   xmlns:xsd="http://www.w3.org/2001/XMLSchema";
   targetNamespace="MyModule">
...
...






..
...
  

   

  

  
  
  


...
  
http://schemas.xmlsoap.org/soap/http"/>
   

  
  

  
  

  
  
  
  
 

Here is what Axis client gets from server:

http://www.w3.org/2001/XMLSchema-instance";
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>


soap:MyModule
Login test error



1
Login or password are 
invalid


   





Adding MyModule.MyExceptionto 
soap fault  causes myException to throw on client side 
but it is not mapped anyway.
Please answer: Is it something wrong in wsdl or envelop or both?

Re: [Axis2] Invoking Interdependent Web Services in a distributed system.

[Kanchana Welagedara]

Hi ,

Sorry for the late reply.

As I stated earlier, I invoke two dependent WSs. First has the second one's
business delegate (proxies ) to invoke the second.I have used axiom clients
here.At remote debugging I get the following error

org.apache.axis2.AxisFault: Read timed out
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:389)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:222)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:435)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:539)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:520)
at samples.test.service.axiom
.WS1AXIOMClient.invoke(WS1AXIOMClient.java:68)

In the Second WS invoke client I have set the following .
options.setTimeOutInMilliSeconds(60).

Your feed back highly appreciated.

/BR
Kanchana

On Fri, Jan 8, 2010 at 2:13 PM, Afkham Azeez  wrote:

> On Fri, Jan 8, 2010 at 1:44 PM, Kanchana Welagedara 
> wrote:
> > Hi Deepal
> >
> > Sorry for not being very clear in previous mail.Here it is clearly.
> >
> > 1. Is there is a away of grouping couple of WS  which serve each other in
> a
> > sever.xml which are deployed in two deterrent containers ? If that is a
> > single container you have the option of service group for this
> correct?How
> > do we do it for a remote invoke ?
> >
> >
> Service groups cannot span across multiple Axis2 instances. I think if
> you tell us more about the problem you are trying to solve rather than
> explaining the solution you have in mind, we could propose a proper
> solution.
>
> >
> >>If you can please try to explain the question bit more clearly, so do
> >>you want to invoke a service (service2) from another service (service1)
> >>and send the final reply to the client ?
> >
> > 2. The above  I have done. Also How wanted to know about the session
> > management in across web servers too in such a scenario.
> >
> HTTP session replication should be handled at the HTTP server level
> and is out of the scope of Axis2. You will need to deploy Axis2 on an
> HTTP server which supports clustering.
>