Axis2 clustering with tomcat

2012-04-29 Thread Kishanthan Thangarajah 
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
this was causing the NPE in DefaultStateManager.
This was because, by default, the parameter "AvoidInitiation" is set as
"true" under the clustering section in axis2.xml. So when running axis2 on
tomcat, this skips the initiation of the cluster when the
ConfigurationContext is being build. This issue can be overcome by setting
the parameter as "false". The other place where the
cluster initialization is called, is in AxisServer. This will not be called
when running axis2 as a webapp.

Thanks,
Kishanthan.
[1] https://issues.apache.org/jira/browse/AXIS2-5178

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

2012-04-29 Thread Kishanthan Thangarajah (JIRA) 

[ 
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 ClusteringAgent was not initialized when updateContexts 
method was called. Can you try changing the true to false in axis2.xml under clustering 
section and then try again to see whether it works? 

Thanks,
Kishanthan.

> Axis2 Clustering on Tomcat
> --
>
> Key: AXIS2-5178
> URL: https://issues.apache.org/jira/browse/AXIS2-5178
> Project: Axis2
>  Issue Type: Bug
>  Components: deployment
>Affects Versions: 1.6.1
> Environment: Tomcat 7.0.22, Axis2 1.6.1
>Reporter: Dzmitry Hancharou
>Assignee: Afkham Azeez
>  Labels: clustering, tomcat,
> Fix For: 1.6.1
>
> Attachments: bug.zip
>
>
> I've extracted Axis2 distribution in two different tomcat directories and 
> changed http ports in axis2 xml.
> After that I've enabled clustering support by changing Clustering section.
> Also I created simple ClusterableService with getName/setName methods in 
> application scope.
> But after running I've got NullPointerException:
> at 
> org.apache.axis2.clustering.state.DefaultStateManager.updateContexts(DefaultStateManager.java:80)
> at org.apache.axis2.clustering.state.Replicator.replicate(Replicator.java:81)
> If I run simple axis2servers everything works.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Re: [Vote] Release Rampart 1.6.2 and Sandesha 1.6.2

2012-04-29 Thread Andreas Veithen 
+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.
>
>
> == Rampart 1.6.2 
>
> List of issues fixed in this release can be found here.
>
> http://s.apache.org/rampart1.6.2
>
> The staging repository is here:
>
> https://repository.apache.org/content/repositories/orgapacheaxis2-110/
>
>
> The distributions are here:
>
> https://repository.apache.org/content/repositories/orgapacheaxis2-110/org/apache/rampart/rampart-dist/1.6.2/
>
> The Maven site preview is here:
>
> http://people.apache.org/~sagara/dist/rampart/1.6.2/site/
>
>
>
> == Sandesha2 1.6.2 
>
> The staging repository is here:
>
> https://repository.apache.org/content/repositories/orgapacheaxis2-111/
>
> The distributions are here:
>
> http://people.apache.org/~sagara/dist/sandesha2/1.6.2/
>
> The Maven site preview is here:
>
> http://people.apache.org/~sagara/dist/sandesha2/1.6.2/site/
>
>
>
> The vote will be open for 72 hours.
>
> Here is my +1.for both releases.
>
> Thanks !
>
>
>
> --
> Sagara Gunathunga
>
> Blog      - http://ssagara.blogspot.com
> Web      - http://people.apache.org/~sagara/
> LinkedIn - http://www.linkedin.com/in/ssagara

-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

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

2012-04-29 Thread Andreas Veithen (JIRA) 
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: Axis2
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.6.2
Reporter: Andreas Veithen
Priority: Minor


The message builders for MTOM and SwA both initialize the message context with 
an Attachments object that contains all MIME parts, including the root part. On 
the other hand, the corresponding message formatters have different 
expectations. The message formatter for MTOM doesn't look at the Attachments 
object in the message context because attachments are referenced by special 
OMText instances in the SOAP envelope. Finally, the message formatter for SwA 
assumes that the Attachments object in the message context only contains the 
attachment parts.

This means that for MTOM and SwA messages, the message context is set up 
differently for incoming and outgoing messages. Such inconsistencies in the API 
are not only annoying, but they also cause subtile issues in Synapse which 
needs to be able to forward messages, i.e. transform incoming into outgoing 
messages. One such issue is described in SYNAPSE-867.

The proposal is to change the semantics for incoming messages, such that they 
match the current semantics for outgoing messages. In practice this means:

1. The Attachments object in the message context would no longer be set for 
MTOM messages. In fact, code that attempts to directly access the MIME parts of 
an MTOM message is broken by definition, because the sender is free to choose 
which base64Binary elements are sent as attachments and which ones are inlined.
2. The message builder for SwA would remove the root part from the Attachments 
object before adding it to the message context, so that application code only 
sees attachments parts. In fact, there is no valid use case where application 
code would want to retrieve the SOAP part directly from the Attachments object.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Re: [Vote] Release Rampart 1.6.2 and Sandesha 1.6.2

2012-04-29 Thread Sagara Gunathunga 
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-plugin:2.2-beta-5:single
(distribution-package) on project distribution: Failed to create assembly:
Error adding file to archive:
/home/sagara/Downloads/sandesha2-1.6.1-src/modules/distribution/../../src/site/xdoc/architectureGuide.xml
isn't a file.

Maven try to generate site but we haven't include site sources within the
source distribution hence result in to failure this is not happen when we
test with sources check out from SVN. I tested 1.6.1 release and it's also
failed with same exception may be some other old releases as well. Let's
block current Sandesh2 release and fix this issue.

Thanks !


>
> 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.
> >
> >
> > == Rampart 1.6.2 
> >
> > List of issues fixed in this release can be found here.
> >
> > http://s.apache.org/rampart1.6.2
> >
> > The staging repository is here:
> >
> > https://repository.apache.org/content/repositories/orgapacheaxis2-110/
> >
> >
> > The distributions are here:
> >
> >
> https://repository.apache.org/content/repositories/orgapacheaxis2-110/org/apache/rampart/rampart-dist/1.6.2/
> >
> > The Maven site preview is here:
> >
> > http://people.apache.org/~sagara/dist/rampart/1.6.2/site/
> >
> >
> >
> > == Sandesha2 1.6.2 
> >
> > The staging repository is here:
> >
> > https://repository.apache.org/content/repositories/orgapacheaxis2-111/
> >
> > The distributions are here:
> >
> > http://people.apache.org/~sagara/dist/sandesha2/1.6.2/
> >
> > The Maven site preview is here:
> >
> > http://people.apache.org/~sagara/dist/sandesha2/1.6.2/site/
> >
> >
> >
> > The vote will be open for 72 hours.
> >
> > Here is my +1.for both releases.
> >
> > Thanks !
> >
> >
> >
> > --
> > Sagara Gunathunga
> >
> > Blog  - http://ssagara.blogspot.com
> > Web  - http://people.apache.org/~sagara/
> > LinkedIn - http://www.linkedin.com/in/ssagara
>
> -
> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-dev-h...@axis.apache.org
>
>


-- 
Sagara Gunathunga

Blog  - http://ssagara.blogspot.com
Web  - http://people.apache.org/~sagara/
LinkedIn - http://www.linkedin.com/in/ssagara

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

2012-04-29 Thread Sagara Gunathunga (JIRA) 

[ 
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 clear API.
 Going further is there any possibility to use generic semantics for both MTOM 
and SwA ?

> Attachments semantics are different for incoming and outgoing messages
> --
>
> Key: AXIS2-5308
> URL: https://issues.apache.org/jira/browse/AXIS2-5308
> Project: Axis2
>  Issue Type: Bug
>  Components: kernel
>Affects Versions: 1.6.2
>Reporter: Andreas Veithen
>Priority: Minor
>
> The message builders for MTOM and SwA both initialize the message context 
> with an Attachments object that contains all MIME parts, including the root 
> part. On the other hand, the corresponding message formatters have different 
> expectations. The message formatter for MTOM doesn't look at the Attachments 
> object in the message context because attachments are referenced by special 
> OMText instances in the SOAP envelope. Finally, the message formatter for SwA 
> assumes that the Attachments object in the message context only contains the 
> attachment parts.
> This means that for MTOM and SwA messages, the message context is set up 
> differently for incoming and outgoing messages. Such inconsistencies in the 
> API are not only annoying, but they also cause subtile issues in Synapse 
> which needs to be able to forward messages, i.e. transform incoming into 
> outgoing messages. One such issue is described in SYNAPSE-867.
> The proposal is to change the semantics for incoming messages, such that they 
> match the current semantics for outgoing messages. In practice this means:
> 1. The Attachments object in the message context would no longer be set for 
> MTOM messages. In fact, code that attempts to directly access the MIME parts 
> of an MTOM message is broken by definition, because the sender is free to 
> choose which base64Binary elements are sent as attachments and which ones are 
> inlined.
> 2. The message builder for SwA would remove the root part from the 
> Attachments object before adding it to the message context, so that 
> application code only sees attachments parts. In fact, there is no valid use 
> case where application code would want to retrieve the SOAP part directly 
> from the Attachments object.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

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

2012-04-29 Thread Hendy Irawan (JIRA) 
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: kernel
Affects Versions: 1.6.2
Reporter: Hendy Irawan


I recently had a conflict in my project where Axis2 wanted jsr311-api version 
1.0 where the other component (specifically neo4j-rest-graph 1.6) wanted 
jsr311-api version 1.1.1.

Manually overriding axis2 and using the jsr311-api 1.1.1 makes the whole app 
work fine.

Since axis2 works fine with 1.1.1 and it is the latest version of jsr311-api, 
this should be the jsr311-api version Axis2 depends on.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

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

2012-04-29 Thread Sagara Gunathunga (JIRA) 
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
 Project: Rampart
  Issue Type: Improvement
  Components: distribution
Affects Versions: 1.6.1
Reporter: Sagara Gunathunga 
Assignee: Sagara Gunathunga 
Priority: Minor
 Fix For: 1.7.0, 1.6.3




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Re: [Vote] Release Rampart 1.6.2 and Sandesha 1.6.2

2012-04-29 Thread Sagara Gunathunga 
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 issue [1] and will start it again.


2. Apache Rampart  1.6.2
=

There are three +1 binding votes ( Ruchith, Andreas and myself) and there
is one -1 vote (Ruwan). According to following given explanation I don't
think it required to block the current release due the miner issue pointed
out by Ruwan. Based on Apache package release process [2] we have three +1
binding votes and  +1 votes have majority approval[3] hence I will proceed
with the release.


 According to Ruwan's quote from ALv2 , NOTICE and LICENSE file *must*
be included
in the same directory but it says  *try* to add the LICENSE file first in
order to place it at the top of the archive" here it is not a must thing
instead recommendation hence I don't think it's requited to block current
release due to this issue. Further, I have noticed same issue within most
of the older Rampart releases as well. Any how since we have identified
this issue I will fix this for next release. I already created JIRA issue
for this [4] and thanks Ruwan for pointing out this issue.


[1] - https://issues.apache.org/jira/browse/SANDESHA2-212
[2] - http://www.apache.org/foundation/voting.html
[3] - http://www.apache.org/foundation/glossary.html#MajorityApproval
[4] - https://issues.apache.org/jira/browse/RAMPART-367

Thanks !



On Sun, Apr 29, 2012 at 7:47 PM, Sagara Gunathunga <
sagara.gunathu...@gmail.com> wrote:

>
>
> On Sun, Apr 29, 2012 at 5:49 PM, Andreas Veithen <
> andreas.veit...@gmail.com> 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-plugin:2.2-beta-5:single
> (distribution-package) on project distribution: Failed to create assembly:
> Error adding file to archive:
> /home/sagara/Downloads/sandesha2-1.6.1-src/modules/distribution/../../src/site/xdoc/architectureGuide.xml
> isn't a file.
>
> Maven try to generate site but we haven't include site sources within the
> source distribution hence result in to failure this is not happen when we
> test with sources check out from SVN. I tested 1.6.1 release and it's also
> failed with same exception may be some other old releases as well. Let's
> block current Sandesh2 release and fix this issue.
>
> Thanks !
>
>
>>
>> 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.
>> >
>> >
>> > == Rampart 1.6.2 
>> >
>> > List of issues fixed in this release can be found here.
>> >
>> > http://s.apache.org/rampart1.6.2
>> >
>> > The staging repository is here:
>> >
>> > https://repository.apache.org/content/repositories/orgapacheaxis2-110/
>> >
>> >
>> > The distributions are here:
>> >
>> >
>> https://repository.apache.org/content/repositories/orgapacheaxis2-110/org/apache/rampart/rampart-dist/1.6.2/
>> >
>> > The Maven site preview is here:
>> >
>> > http://people.apache.org/~sagara/dist/rampart/1.6.2/site/
>> >
>> >
>> >
>> > == Sandesha2 1.6.2 
>> >
>> > The staging repository is here:
>> >
>> > https://repository.apache.org/content/repositories/orgapacheaxis2-111/
>> >
>> > The distributions are here:
>> >
>> > http://people.apache.org/~sagara/dist/sandesha2/1.6.2/
>> >
>> > The Maven site preview is here:
>> >
>> > http://people.apache.org/~sagara/dist/sandesha2/1.6.2/site/
>> >
>> >
>> >
>> > The vote will be open for 72 hours.
>> >
>> > Here is my +1.for both releases.
>> >
>> > Thanks !
>> >
>> >
>> >
>> > --
>> > Sagara Gunathunga
>> >
>> > Blog  - http://ssagara.blogspot.com
>> > Web  - http://people.apache.org/~sagara/
>> > LinkedIn - http://www.linkedin.com/in/ssagara
>>
>> -
>> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
>> For additional commands, e-mail: java-dev-h...@axis.apache.org
>>
>>
>
>
> --
> Sagara Gunathunga
>
> Blog  - http://ssagara.blogspot.com
> Web  - http://people.apache.org/~sagara/
> LinkedIn - http://www.linkedin.com/in/ssagara
>



-- 
Sagara Gunathunga

Blog  - http://ssagara.blogspot.com
Web  - http://people.apache.org/~sagara/
LinkedIn - http://www.linkedin.com/in/ssagara

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

2012-04-29 Thread Sagara Gunathunga (JIRA) 

[ 
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 fully by changing the jsr311-api version in 
modules/parent/pom.xml file and let us know your results please ? 

> 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: kernel
>Affects Versions: 1.6.2
>Reporter: Hendy Irawan
>
> I recently had a conflict in my project where Axis2 wanted jsr311-api version 
> 1.0 where the other component (specifically neo4j-rest-graph 1.6) wanted 
> jsr311-api version 1.1.1.
> Manually overriding axis2 and using the jsr311-api 1.1.1 makes the whole app 
> work fine.
> Since axis2 works fine with 1.1.1 and it is the latest version of jsr311-api, 
> this should be the jsr311-api version Axis2 depends on.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Fwd: Nexus: Promotion Completed.

2012-04-29 Thread Sagara Gunathunga 
-- 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
Releasesrepository.

archetype-catalog.xml
rampart-policy-1.6.2-sources.jar
rampart-policy-1.6.2.pom.asc
rampart-policy-1.6.2-sources.jar.asc
rampart-policy-1.6.2.pom
rampart-policy-1.6.2.jar
rampart-policy-1.6.2-javadoc.jar.asc
rampart-policy-1.6.2.jar.asc
rampart-policy-1.6.2-javadoc.jar
rampart-tests-1.6.2-sources.jar
rampart-tests-1.6.2.pom
rampart-tests-1.6.2.jar
rampart-tests-1.6.2-sources.jar.asc
rampart-tests-1.6.2.pom.asc
rampart-tests-1.6.2.jar.asc
rampart-trust-1.6.2.pom
rampart-trust-1.6.2.jar.asc
rampart-trust-1.6.2-javadoc.jar.asc
rampart-trust-1.6.2-sources.jar
rampart-trust-1.6.2-sources.jar.asc
rampart-trust-1.6.2.pom.asc
rampart-trust-1.6.2.jar
rampart-trust-1.6.2-javadoc.jar
rahas-1.6.2.mar
rahas-1.6.2.mar.asc
rahas-1.6.2-sources.jar.asc
rahas-1.6.2.pom.asc
rahas-1.6.2.pom
rahas-1.6.2-sources.jar
rampart-sample-1.6.2-sources.jar.asc
rampart-sample-1.6.2.pom.

Fwd: Nexus: Staging Repository Dropped.

2012-04-29 Thread Sagara Gunathunga 
-- 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) staging repository has
been dropped.



-- 
Sagara Gunathunga

Blog  - http://ssagara.blogspot.com
Web  - http://people.apache.org/~sagara/
LinkedIn - http://www.linkedin.com/in/ssagara

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

2012-04-29 Thread Santhosh (JIRA) 
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: databinding, transports
Affects Versions: 1.6.2
 Environment: Axis2.0 version used : 1.6.2
NSJSP7.0 and ITP webserver 7.2 for HP Nonstop Tandem
Reporter: Santhosh
Priority: Blocker


I'm facing below error message after deploying a webservice using Axis2.0 in 
webserver.

Mon, Apr 30, 16:08:27;$Z0QF;INFO;StandardService#stopInternal;Stopping service 
NSJSP
Mon, Apr 30, 16:08:29;$Z0QF;SEVERE;WebappClassLoader#clearReferencesThreads;The 
web application [/PSAPI-V1-0/axis2] is still processing a request that has yet 
to finish. This is very likely to create a memory leak. You can control the 
time allowed for requests to finish by using the unloadDelay attribute of the 
standard Context implementation.
Mon, Apr 30, 
16:08:29;$Z0QF;SEVERE;WebappClassLoader#checkThreadLocalMapForLeaks;The web 
application [/PSAPI-V1-0/axis2] created a ThreadLocal with key of type 
[java.lang.ThreadLocal] (value [java.lang.ThreadLocal@2465e5]) and a value of 
type [org.apache.axis2.context.MessageContext] (value [[MessageContext: 
logID=3fecb85757bee1e6fd9cdc8eb6a0e146d5c1eaa7dd28d0e7]]) but failed to remove 
it when the web application was stopped. Threads are going to be renewed over 
time to try and avoid a probable memory leak.
Mon, Apr 30, 
16:08:29;$Z0QF;SEVERE;WebappClassLoader#checkThreadLocalMapForLeaks;The web 
application [/PSAPI-V1-0/axis2] created a ThreadLocal with key of type 
[org.apache.axiom.util.UIDGenerator$1] (value 
[org.apache.axiom.util.UIDGenerator$1@b103dd]) and a value of type [long[]] 
(value [[J@174d4c9]) but failed to remove it when the web application was 
stopped. Threads are going to be renewed over time to try and avoid a probable 
memory leak.
Mon, Apr 30, 16:08:29;$Z0QF;INFO;AbstractProtocolHandler#stop;Stopping 
ProtocolHandler ["http-bio-0"]


As per error logs i understand that "Axis2.0 - framework" is not able to 
delete/failed to cleanup a thread. Please provide me with resolution if any.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org