Axis2 clustering with tomcat

Hi All, I was recently working with the $subject. I used two different tomcat instances to create the cluster. But i was facing the same problem as mentioned in here [1]. I digged in to see the root cause for this and found that the ClusteringAgent (TribesClusteringAgent) was never initialized and

[jira] [Commented] (AXIS2-5178) Axis2 Clustering on Tomcat

[ https://issues.apache.org/jira/browse/AXIS2-5178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264483#comment-13264483 ] Kishanthan Thangarajah commented on AXIS2-5178: --- Hi, This is because the Clu

Re: [Vote] Release Rampart 1.6.2 and Sandesha 1.6.2

+1 for the Rampart release. For Sandesha2, there seems to be a problem because the source distribution is not buildable. Andreas On Thu, Apr 26, 2012 at 15:06, Sagara Gunathunga wrote: > Hi Devs, > > Here is the vote for the  Rampart 1.6.2 and  Sandesha 1.6.2 maintenance > releases. > > > =

[jira] [Created] (AXIS2-5308) Attachments semantics are different for incoming and outgoing messages

Andreas Veithen created AXIS2-5308: -- Summary: Attachments semantics are different for incoming and outgoing messages Key: AXIS2-5308 URL: https://issues.apache.org/jira/browse/AXIS2-5308 Project: Axi

Re: [Vote] Release Rampart 1.6.2 and Sandesha 1.6.2

On Sun, Apr 29, 2012 at 5:49 PM, Andreas Veithen wrote: > +1 for the Rampart release. > > For Sandesha2, there seems to be a problem because the source > distribution is not buildable. > I think you faced to following issue. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly

[jira] [Commented] (AXIS2-5308) Attachments semantics are different for incoming and outgoing messages

[ https://issues.apache.org/jira/browse/AXIS2-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264561#comment-13264561 ] Sagara Gunathunga commented on AXIS2-5308: --- +1 for your proposal and make it a

[jira] [Created] (AXIS2-5309) Usr jsr311-api version 1.1.1

Hendy Irawan created AXIS2-5309: --- Summary: Usr jsr311-api version 1.1.1 Key: AXIS2-5309 URL: https://issues.apache.org/jira/browse/AXIS2-5309 Project: Axis2 Issue Type: Bug Components

[jira] [Created] (RAMPART-367) It is better to move LICENSE and NOTICE file into top level of source distribution.

Sagara Gunathunga created RAMPART-367: -- Summary: It is better to move LICENSE and NOTICE file into top level of source distribution. Key: RAMPART-367 URL: https://issues.apache.org/jira/browse/RAMPART-367

Re: [Vote] Release Rampart 1.6.2 and Sandesha 1.6.2

This vote has been open for more than 72 hours and results are as follows. 1. Apache Sandesha2 1.6.2 = Andreas found a build issue on source distribution and it seems this issue exists on previous releases also. I will drop the current Sandesha2 release, will fix the

[jira] [Commented] (AXIS2-5309) Usr jsr311-api version 1.1.1

[ https://issues.apache.org/jira/browse/AXIS2-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264682#comment-13264682 ] Sagara Gunathunga commented on AXIS2-5309: --- Can you try to build Axis2 trunk fu

Fwd: Nexus: Promotion Completed.

-- Forwarded message -- From: Nexus Repository Manager Date: Mon, Apr 30, 2012 at 11:17 AM Subject: Nexus: Promotion Completed. To: Sagara Gunathunga *Description:* Rampart 1.6.2 vote was successful. *Details:* The following artifacts have been promoted to the Releases

Fwd: Nexus: Staging Repository Dropped.

-- Forwarded message -- From: Nexus Repository Manager Date: Mon, Apr 30, 2012 at 11:18 AM Subject: Nexus: Staging Repository Dropped. To: Sagara Gunathunga *Description:* found a issue and canceled the release. *Details:* The org.apache.axis2-111 (u:sagara, a:203.143.31.75)

[jira] [Created] (AXIS2-5310) Axis2.0 : 1.6.2 : Memory Leak Issue

Santhosh created AXIS2-5310: --- Summary: Axis2.0 : 1.6.2 : Memory Leak Issue Key: AXIS2-5310 URL: https://issues.apache.org/jira/browse/AXIS2-5310 Project: Axis2 Issue Type: Bug Components