Re: [Dev] [ESB] Some special characters are not preserved as encoded in ESB

[Ishara Premadasa]

Hi Miyuru,

Is there any configuration available for keep the encodings?
Thanks!
Ishara

On Fri, Sep 19, 2014 at 12:16 AM, Miyuru Wanninayaka 
wrote:

> This behavior comes from axiom.
>
> OMElement omElement = AXIOMUtil.stringToOM("This is &
> < > ' " Test ");
> System.out.println(omElement.toString());
>
> generates
>
> This is & < > ' " Test 
>
> @Do you know a way to turn this off in axiom level.
>
>
>
> On Fri, Sep 19, 2014 at 9:01 AM, Ishara Premadasa  wrote:
>
>> Hi all,
>>
>> I observed that when we send encoded special characters in msg context to
>> ESB some of these characters are decoded inside ESB. Please see the example
>> used below.
>>
>> My input message is like this,
>>
>> 
>> This is & < > ' " Test 
>> 
>>
>> When sending this into a proxy service and logged in the ESB, result
>> looks as this.
>>
>> http://www.w3.org/2003/05/soap-envelope
>> ">*This is & < > ' " test *
>> 
>>
>> You can see that ampersand and less than encodings are preserved but
>> greater than, single and double quotes are decoded. On a side this [1]
>> explains that only the & and < characters are strictly illegal to have in
>> XML. I was wondering whether ESB also follows this reason.
>>
>> Is there any specific reason why this happens?  In addition if it is
>> required to keep these characters encoded inside ESB what should be the way
>> to do that?
>>
>> Thanks!
>> Ishara
>>
>> [1]
>> http://stackoverflow.com/questions/14228463/why-is-ok-to-be-in-value-of-xml-file-but-is-not
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>>
>>
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> <http://isharapremadasa.blogspot.com/>Twitter   :
>> https://twitter.com/ishadil <https://twitter.com/ishadil>Mobile   : +94
>> 714445832 <%2B94%20714445832>*
>>
>>
>>
>
>
> --
> Miyuru Wanninayaka
> Senior Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile : +94 77 209 9788
>



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
<http://isharapremadasa.blogspot.com/>Twitter   :
https://twitter.com/ishadil <https://twitter.com/ishadil>Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Some special characters are not preserved as encoded in ESB

[Ishara Premadasa]

Hi all,

I observed that when we send encoded special characters in msg context to
ESB some of these characters are decoded inside ESB. Please see the example
used below.

My input message is like this,


This is & < > ' " Test 


When sending this into a proxy service and logged in the ESB, result looks
as this.

http://www.w3.org/2003/05/soap-envelope
">*This is & < > ' " test *


You can see that ampersand and less than encodings are preserved but
greater than, single and double quotes are decoded. On a side this [1]
explains that only the & and < characters are strictly illegal to have in
XML. I was wondering whether ESB also follows this reason.

Is there any specific reason why this happens?  In addition if it is
required to keep these characters encoded inside ESB what should be the way
to do that?

Thanks!
Ishara

[1]
http://stackoverflow.com/questions/14228463/why-is-ok-to-be-in-value-of-xml-file-but-is-not

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Misleading error message from spring mediator as "No bean name is defined"

[Ishara Premadasa]

Hi all,

Observed this with ESB 4.8.1. As per my scenario the spring mediator loads
the bean successful and afterwards there was an error occurred in the java
class file which is loaded by the spring mediator. (for e.g.
ClassCastException)

However as per this code from SpringMediator.java below, ESB still catches
that error by logging 'no bean name defined' where the actual error happens
in in 'return m.mediate(synCtx);' line.

try{
Object o = appContext.getBean(beanName);
if (o != null && Mediator.class.isAssignableFrom(o.getClass())) {
Mediator m = (Mediator) o;
if (synLog.isTraceOrDebugEnabled())
{ synLog.traceOrDebug("Loaded mediator from bean : " + beanName + "
executing..."); }

*return m.mediate(synCtx);*

} else {
if (synLog.isTraceOrDebugEnabled())
{ synLog.traceOrDebug("Unable to load mediator from bean : " + beanName); }

handleException("Could not load bean named : " + beanName +
" from the Spring configuration with key : " + configKey, synCtx);
   }
}* catch (Exception e) *

* { handleException("No bean named '"+beanName+"' is defined", synCtx); } *
Hence if  there is no proper error handling done in the java class file it
is possible that actual error will be getting hidden due to this code.
I created [1] for this. Please fix this for an upcoming release.

Thanks!
Ishara

[1] https://wso2.org/jira/browse/ESBJAVA-3291

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] [DOC] 'FORCE_ERROR_ON_SOAP_FAULT' Property not mentioned in 'Properties Reference' page

[Ishara Premadasa]

Hi all,

The property 'FORCE_ERROR_ON_SOAP_FAULT' is a useful entry when it comes to
re-direct a SOAPFault thrown by a back end service into a Fault sequence.
[1] If this is not set the SOAPFault will be received by the OutSequence as
a usual response message.



Currently ESB 4.8.1 docs doesn't explain the use of this property anywhere.
I think this should be properly documented in the 'Generic Properties' [2]
section of the docs.

Adding the Dev list here, as this information will be useful for someone.

Thanks!
Ishara

[1]
http://vvratha.blogspot.com/2014/05/executing-faultsequence-for-soapfaults.html
[2] https://docs.wso2.com/display/ESB481/Generic+Properties

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?

[Ishara Premadasa]

Hi Shameera,

I tried with the synapse-core dependency only at first. However there is
this TestUtils class which is required to Junit test class for custom
mediator that is not coming from synapse-core.

@Chamara,
Can you please clarify here on this TestUtils class?

Thanks!
Ishara


On Thu, Aug 7, 2014 at 1:44 PM, Shameera Rathnayaka 
wrote:

> Even though jar name is synapse-core-test its artifactId is synapse-core ,
> try with
>
> 
> org.apache.synapse
> synapse-core
> 2.1.2-wso2v4
>  
>
> ~Shameera.
>
>
> On Thu, Aug 7, 2014 at 9:58 PM, Ishara Premadasa  wrote:
>
>> Hi all,
>>
>> I get the following build error when trying to check out remote ESB
>> mediator project and trying to build it online. Since there are test cases
>> created for the class mediators, it is required to add synapse-core-tests
>> dependency into the pom.xml and use that in the test cases. Below is the
>> dependency and my maven repository entry.
>>
>> 
>> org.apache.synapse
>> synapse-core-tests
>> 2.1.2-wso2v4
>>  
>> 
>> 
>> true
>> daily
>> ignore
>> 
>> wso2-nexus
>> http://maven.wso2.org/nexus/content/groups/wso2-public/
>> 
>> 
>>
>> Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure
>> to find org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 in
>> http://maven.wso2.org/nexus/content/groups/ws
>> o2-public/ was cached in the local repository, resolution will not be
>> reattempted until the update interval of wso2-nexus has elapsed or updates
>> are forced
>> at
>> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:232)
>> at
>> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
>> at
>> org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:599)
>> at
>> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:518)
>> at
>> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:436)
>> ... 26 more
>> [ERROR]
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>>
>> This says unable to find
>> org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 jar but if you
>> traverse this can be located in neus-repo [1].
>> Any help is appreciated.
>>
>> [1]
>> http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/synapse/synapse-core/2.1.2-wso2v4/
>>
>> Thanks!
>> Ishara
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>>
>>
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> <http://isharapremadasa.blogspot.com/>Twitter   :
>> https://twitter.com/ishadil <https://twitter.com/ishadil> Mobile   :
>> +94 714445832 <%2B94%20714445832>*
>>
>>
>>
>
>
> --
> *Software Engineer - WSO2 Inc.*
> *email: shameera AT wso2.com  , shameera AT apache.org
> *
> *phone:  +9471 922 1454 <%2B9471%20922%201454>*
>
> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
> *Twitter : *https://twitter.com/Shameera_R
>



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
<http://isharapremadasa.blogspot.com/>Twitter   :
https://twitter.com/ishadil <https://twitter.com/ishadil>Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?

[Ishara Premadasa]

Hi all,

I get the following build error when trying to check out remote ESB
mediator project and trying to build it online. Since there are test cases
created for the class mediators, it is required to add synapse-core-tests
dependency into the pom.xml and use that in the test cases. Below is the
dependency and my maven repository entry.


org.apache.synapse
synapse-core-tests
2.1.2-wso2v4
 


true
daily
ignore

wso2-nexus
http://maven.wso2.org/nexus/content/groups/wso2-public/



Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure
to find org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 in
http://maven.wso2.org/nexus/content/groups/ws
o2-public/ was cached in the local repository, resolution will not be
reattempted until the update interval of wso2-nexus has elapsed or updates
are forced
at
org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:232)
at
org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:599)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:518)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:436)
... 26 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]

This says unable to find
org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 jar but if you
traverse this can be located in neus-repo [1].
Any help is appreciated.

[1]
http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/synapse/synapse-core/2.1.2-wso2v4/

Thanks!
Ishara
-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Dev Studio] Adding mediators within a sequence doesn't get saved

[Ishara Premadasa]

Hi,

When i add the below config inside a sequence.xml file in Developer Studio
3.7.0, once the file is saved and open the source view back, all the
configs are wiped out.

http://ws.apache.org/ns/synapse"; name="TestSequence">
   
  
 
  
  
 
http://localhost:9764/jaxrs_starbucks_service/services/Starbucks_Outlet_Service/orders/
">
 
  
   
   
  
 
  
   


However when use ESB UI editor to create this config it is supported there.


​

May i please know how to create In,Out mediators from Dev studio, as i have
several sequences which invokes external API endpoints at the  and need
to get the response into .

Thanks!
Ishara

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Fault mediator doesn't display full error details when used with POX format

[Ishara Premadasa]

Thanks Dushan for the clarification.


On Wed, Jul 2, 2014 at 10:39 PM, Dushan Abeyruwan  wrote:

> For soap 1.1 vs soap 1.2 fault there is a clear specification so what ever
> web service engine whose executing soap 1.2 or soap 1.1 fault know how to
> deal with when it receives faults according.
>
>  SOAP 1.1SOAP 1.2
>
> e:Fault
>
> e:Fault
>
> faultcode
>
> e:Code, e:Subcode, e:Value
>
> faultstring
>
> e:Reason
>
> faultactor
>
> e:Node, e:Role
>
> detail
>
> e:Detail
>
>
>
> SOAP 1.1SOAP 1.2
>
> 
>   e:Server.Memory
>   Out of memory
> 
>
> 
>   
> e:Receiver
> 
>   p:Memory
> 
>   
>   Out of memory
> 
>
> *Table 2*
>
>   for *POX* fault no specification so we just wrapping around with
>  tag with relevant fault
>
>
> On Thu, Jul 3, 2014 at 7:45 AM, Ishara Premadasa  wrote:
>
>> Hi all,
>>
>> Any idea on this. Would be great if i can know the reason for the
>> difference here.
>> Thanks!
>>
>>
>> On Wed, Jul 2, 2014 at 3:15 AM, Ishara Premadasa  wrote:
>>
>>> Hi,
>>>
>>> I used fault mediator with both soap 1.1 and pox format where the format
>>> of the generated fault response appeared to be different. With the pox
>>> format some elements of the fault message was missing.
>>>
>>> For e.g: This is the response getting for Soap 1.1 format
>>> http://schemas.xmlsoap.org/soap/envelope/";>
>>>
>>>   
>>>  http://schemas.xmlsoap.org/soap/envelope/
>>> ">soap11Env:VersionMismatch
>>>  Version Mismatch!!
>>>  There is a version mismatch in the input
>>> message
>>>   
>>>
>>> 
>>>
>>> This is how it looks like for POX format.
>>> http://schemas.xmlsoap.org/soap/envelope/";>
>>>
>>>
>>>   There is a version mismatch in the input
>>> message
>>>
>>> 
>>>
>>> I have two concerns on this.
>>>
>>> 1. The fault reason, code entries we set in the mediator are ommitted
>>> when creating POX fault.
>>> 2. For the Pox format it generates an empty  element but in Soap
>>> 1.1 that is missing.
>>>
>>> When debugging the fault mediator i could see the below reasons for this
>>> output.
>>>
>>> 1. When we create POX fault there is an if-else block where it first
>>> checks 'faultDetail' and else if goes to 'faultDetailExpr' etc. Therefore
>>> when the fault  is there, the other values are ommitted for the
>>> fault payload. However when we create SOAP fault all the details are taken
>>> and set into SOAPFault  object as below.
>>>
>>> setFaultCode(synCtx, factory, fault, soapVersion);
>>> setFaultReason(synCtx, factory, fault, soapVersion);
>>> setFaultDetail(synCtx, factory, fault);
>>>
>>> I would like to know whether there is any specific reason for doing
>>> that. IMO there is no harm if we provide all data with the POX fault as
>>> well rather than skipping them, since the data are already in the message
>>> context.
>>>
>>> 2. In the POX fault we add the fault payload as a child and replace the
>>> . But in SOAP fault the whole envelope is getting replaced with new
>>> fault envelope. May be this is why the  is missing there ?
>>>
>>> Thanks!
>>> Ishara
>>> --
>>> Ishara Premasada
>>> Software Engineer,
>>> WSO2 Inc. http://wso2.com/
>>>
>>>
>>> *Blog   :  http://isharapremadasa.blogspot.com/
>>> <http://isharapremadasa.blogspot.com/>Twitter   :
>>> https://twitter.com/ishadil <https://twitter.com/ishadil> Mobile   :
>>> +94 714445832 <%2B94%20714445832>*
>>>
>>>
>>>
>>
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>>
>>
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> <http://isharapremadasa.blogspot.com/>Twitter   :
>> https://twitter.com/ishadil <https://twitter.com/ishadil> Mobile   :
>> +94 714445832 <%2B94%20714445832>*
>>
>>
>>
>
>
> --
> Dushan Abeyruwan | Associate Tech Lead
> Integration Technologies Team
> PMC Member Apache Synpase
> WSO2 Inc. http://wso2.com/
> Blog:http://dushansview.blogspot.com/
> Mobile:(0094)713942042
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
<http://isharapremadasa.blogspot.com/>Twitter   :
https://twitter.com/ishadil <https://twitter.com/ishadil>Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Fault mediator doesn't display full error details when used with POX format

[Ishara Premadasa]

Hi all,

Any idea on this. Would be great if i can know the reason for the
difference here.
Thanks!


On Wed, Jul 2, 2014 at 3:15 AM, Ishara Premadasa  wrote:

> Hi,
>
> I used fault mediator with both soap 1.1 and pox format where the format
> of the generated fault response appeared to be different. With the pox
> format some elements of the fault message was missing.
>
> For e.g: This is the response getting for Soap 1.1 format
> http://schemas.xmlsoap.org/soap/envelope/
> ">
>
>   
>  http://schemas.xmlsoap.org/soap/envelope/
> ">soap11Env:VersionMismatch
>  Version Mismatch!!
>  There is a version mismatch in the input message
>   
>
> 
>
> This is how it looks like for POX format.
> http://schemas.xmlsoap.org/soap/envelope/
> ">
>
>
>   There is a version mismatch in the input
> message
>
> 
>
> I have two concerns on this.
>
> 1. The fault reason, code entries we set in the mediator are ommitted when
> creating POX fault.
> 2. For the Pox format it generates an empty  element but in Soap
> 1.1 that is missing.
>
> When debugging the fault mediator i could see the below reasons for this
> output.
>
> 1. When we create POX fault there is an if-else block where it first
> checks 'faultDetail' and else if goes to 'faultDetailExpr' etc. Therefore
> when the fault  is there, the other values are ommitted for the
> fault payload. However when we create SOAP fault all the details are taken
> and set into SOAPFault  object as below.
>
> setFaultCode(synCtx, factory, fault, soapVersion);
> setFaultReason(synCtx, factory, fault, soapVersion);
> setFaultDetail(synCtx, factory, fault);
>
> I would like to know whether there is any specific reason for doing that.
> IMO there is no harm if we provide all data with the POX fault as well
> rather than skipping them, since the data are already in the message
> context.
>
> 2. In the POX fault we add the fault payload as a child and replace the
> . But in SOAP fault the whole envelope is getting replaced with new
> fault envelope. May be this is why the  is missing there ?
>
> Thanks!
> Ishara
> --
> Ishara Premasada
> Software Engineer,
> WSO2 Inc. http://wso2.com/
>
>
> *Blog   :  http://isharapremadasa.blogspot.com/
> <http://isharapremadasa.blogspot.com/>Twitter   :
> https://twitter.com/ishadil <https://twitter.com/ishadil> Mobile   :
> +94 714445832 <%2B94%20714445832>*
>
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
<http://isharapremadasa.blogspot.com/>Twitter   :
https://twitter.com/ishadil <https://twitter.com/ishadil>Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Fault mediator doesn't display full error details when used with POX format

[Ishara Premadasa]

Hi,

I used fault mediator with both soap 1.1 and pox format where the format of
the generated fault response appeared to be different. With the pox format
some elements of the fault message was missing.

For e.g: This is the response getting for Soap 1.1 format
http://schemas.xmlsoap.org/soap/envelope/";>
   
  
 http://schemas.xmlsoap.org/soap/envelope/
">soap11Env:VersionMismatch
 Version Mismatch!!
 There is a version mismatch in the input message
  
   


This is how it looks like for POX format.
http://schemas.xmlsoap.org/soap/envelope/";>
   
   
  There is a version mismatch in the input
message
   


I have two concerns on this.

1. The fault reason, code entries we set in the mediator are ommitted when
creating POX fault.
2. For the Pox format it generates an empty  element but in Soap
1.1 that is missing.

When debugging the fault mediator i could see the below reasons for this
output.

1. When we create POX fault there is an if-else block where it first checks
'faultDetail' and else if goes to 'faultDetailExpr' etc. Therefore when the
fault  is there, the other values are ommitted for the fault
payload. However when we create SOAP fault all the details are taken and
set into SOAPFault  object as below.

setFaultCode(synCtx, factory, fault, soapVersion);
setFaultReason(synCtx, factory, fault, soapVersion);
setFaultDetail(synCtx, factory, fault);

I would like to know whether there is any specific reason for doing that.
IMO there is no harm if we provide all data with the POX fault as well
rather than skipping them, since the data are already in the message
context.

2. In the POX fault we add the fault payload as a child and replace the
. But in SOAP fault the whole envelope is getting replaced with new
fault envelope. May be this is why the  is missing there ?

Thanks!
Ishara
-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Unable to use apostrophe in fn:concat() Xpath function

[Ishara Premadasa]

Hi Ishan,

Thank you very much. This works fine :)

Also using the (') symbol straightly inside quot;  worked as well, like
below.
expression="fn:concat(*"*This is*'"*, *"*my function*"*
)"

- Ishara


On Wed, Jun 25, 2014 at 1:10 AM, Ishan Jayawardena  wrote:

> Hi Ishara,
> This worked for me,
>
> expression="fn:concat(*"*This is*'"*, *"*my function
> *"*)"
>
> First, we are surrounding the strings with double quotes and then insert
> the apostrophe (not sure if this is same as the single quote mark).
>
> Thanks,
> Ishan.
>
>
> On Wed, Jun 25, 2014 at 9:35 AM, Ishara Premadasa  wrote:
>
>> Hi all,
>>
>> I need to use a string which contains apostrophe character ( ' )  with
>> fn:concat function. Tried with the below ways and none seems to be working.
>>
>> 1. >expression="fn:concat(' This is'', ' my
>> function')"
>>scope="default"
>>type="STRING"/>
>>
>> This got saved and changed to fn:concat(' This is'', ' my
>> function') internally however when the output is logged it is like ' this
>> is &apos my function'.
>>
>> 2. I then enabled XPath 2.0 in synapse.properties and tried with below as
>> per 2.0 spec [1].
>> >expression="fn:concat('this is''', ' name')"
>>scope="default"
>>type="STRING"/>
>>
>> This didn't get saved and throws invalid xpath expression error. Tried in
>> both admin console and Dev studio but any method was not able to get the
>> apostrophe character appear. I am using ESB 4.8.1 in Windows 7, JDK 1.7_60.
>>
>> Thanks!
>> Ishara
>>
>> [1] http://www.w3.org/TR/xpath20/#doc-xpath-EscapeApos
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>>
>>
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> <http://isharapremadasa.blogspot.com/> Twitter   :
>> https://twitter.com/ishadil <https://twitter.com/ishadil>Mobile   : +94
>> 714445832 <%2B94%20714445832>*
>>
>>
>>
>
>
> --
> Ishan Jayawardena
> Senior Software Engineer
> Mobile: +94 (77) 408 2330
>



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
<http://isharapremadasa.blogspot.com/>Twitter   :
https://twitter.com/ishadil <https://twitter.com/ishadil>Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Unable to use apostrophe in fn:concat() Xpath function

[Ishara Premadasa]

Hi all,

I need to use a string which contains apostrophe character ( ' )  with
fn:concat function. Tried with the below ways and none seems to be working.

1. 

This got saved and changed to fn:concat(' This is'', ' my
function') internally however when the output is logged it is like ' this
is &apos my function'.

2. I then enabled XPath 2.0 in synapse.properties and tried with below as
per 2.0 spec [1].


This didn't get saved and throws invalid xpath expression error. Tried in
both admin console and Dev studio but any method was not able to get the
apostrophe character appear. I am using ESB 4.8.1 in Windows 7, JDK 1.7_60.

Thanks!
Ishara

[1] http://www.w3.org/TR/xpath20/#doc-xpath-EscapeApos

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Shazni Nazir

[Ishara Premadasa]

Congratulations !!


On Wed, Jun 4, 2014 at 12:39 PM, Shani Ranasinghe  wrote:

> Congrats
>
>
> On Wed, Jun 4, 2014 at 6:26 AM, Isuruwan Herath  wrote:
>
>> Congratz Shazni !!!
>>
>>
>> On Wed, Jun 4, 2014 at 3:28 AM, Amal Gunatilake  wrote:
>>
>>> Congratz Shazni ! :)
>>>
>>> Thank you  & Best regards,
>>>
>>> *Amal Gunatilake*
>>>  Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>>
>>> On Wed, Jun 4, 2014 at 11:13 AM, Gayan Yalpathwala 
>>> wrote:
>>>
 Congratulations Shazni!!


 On Wed, Jun 4, 2014 at 11:06 AM, Tishan Dahanayakage 
 wrote:

> Congratz Shazni!
>
>
> On Wed, Jun 4, 2014 at 11:04 AM, Nufail Mohamed 
> wrote:
>
>> Congrats Shazni
>>
>>
>> On Wed, Jun 4, 2014 at 10:56 AM, Lali Devamanthri 
>> wrote:
>>
>>> Congrats Shazni
>>>
>>>
>>> On Tue, Jun 3, 2014 at 7:51 PM, Pulasthi Supun 
>>> wrote:
>>>
 Congrats Shazni!!




 On Tue, Jun 3, 2014 at 7:49 PM, Subash Chaturanga 
 wrote:

> Hi all,
> It's my pleasure to announce Shazni as a WSO2 Committer. Shazni
> has done great contributions to G-Reg product and showed very good
> enthusiasm in his work. And in recognition of his contribution he has 
> been
> voted as a wso2 commiter.
>
> Shazni, welcome aboard and keep up the good work!.
>
> --
> Thanks
> /subash
>
> *Subash Chaturanga*
> Senior Software Engineer :Platform TG; WSO2 Inc. http://wso2.com
>
> email: sub...@wso2.com
> blog:  http://subashsdm.blogspot.com/
> twitter: @subash89
> phone: +9477 2225922
> Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 --
 Pulasthi Supun
 Software Engineer; WSO2 Inc.; http://wso2.com,
 Email: pulas...@wso2.com
 Mobile: +94 (71) 9258281
 Blog : http://pulasthisupun.blogspot.com/
 Git hub profile: https://github.com/pulasthi

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> *Lali Sudaththa Devamanthri*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 71 895 4922
>>>  
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Tishan Dahanayakage
> Software Engineer
>  WSO2, Inc.
> Mobile:+94 716481328
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender 
> indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, re-transmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Gayan Kaushalya Yalpathwala*
  Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 71 8682704 

  

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Isuruwan Herath
>> Technical Lead
>>
>> Contact: +94 776 273 296
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards
> *,Shani Ranasinghe*
>
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 7

Re: [Dev] WSO2 Committers += Sohani Weerasinghe

[Ishara Premadasa]

Congrats Sohani .


On Fri, May 30, 2014 at 4:59 PM, Lali Devamanthri  wrote:

> Congratulations 
>
>
> On Fri, May 30, 2014 at 11:06 AM, Jasintha Dasanayake 
> wrote:
>
>> Hi All,
>>
>> It's my distinct pleasure to welcome Sohani as a WSO2 Committer.
>>
>> Sohani has  been a valuable contributor for WSO2 Developer Studio since
>> she joined WSO2. In recognition of her contributions to WSO2, she has been
>> voted as a WSO2 Committer.
>>
>> Sohani, Congratulations and Keep up the good work!
>>
>> Thanks and Regards,
>> /Jasintha
>>
>>
>> --
>>
>> *Jasintha Dasanayake *
>>
>> *Senior Software EngineerWSO2 Inc. | http://wso2.com 
>> lean . enterprise . middleware*
>>
>>
>> *mobile :- 0711368118 <0711368118>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Lali Sudaththa Devamanthri*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 71 895 4922
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Is it recommended to have two log4j properties files in one MB pack?

[Ishara Premadasa]

Hi Kishanthan,


On Thu, May 22, 2014 at 10:41 PM, Kishanthan Thangarajah <
kishant...@wso2.com> wrote:

>
>
>
> On Thu, May 22, 2014 at 5:06 PM, Sewwandi Perera wrote:
>
>> Hi,
>>
>> Currently, WSO2 MB supports both Cassandra and Zookeeper profiles. The
>> "log4j.properties" file is configured to write all Cassandra related logs
>> to "cassandra_system.log" and all zookeeper related logs to "zookeeper.log".
>>
>
> So these separate log files are used only when those profiles started?
>
>
>>
>> We came up to a requirement where, we need to append all Cassandra logs
>> also to "wso2carbon.log" only when, the MB is started in Cassandra profile.
>>  Refer [1]
>>
>
> I'm sorry, I did not get this requirement. You want to have cassandra
> related logs on a separate log file. I believe this is to make the
> cassandra log analyzing easy. So what is the purpose of again using carbon
> log file for that?
>

The exact requirement is, since now we start Cassandra with mb profiles it
starts as an MB instance where in general users tends to monitor the
wso2carbon log and terminal log. However since the Cassandra related logs
get appended to a separate file, in case of Cassandra failure, the user
doesn't see any error logs etc. in wso2carbon log or in terminal logs where
Cassandra profile is running.

Hence from users' perspective i think it is required to append the
cassandra (or zookeeper) logs into wso2carbon.log file only when MB
instance is started as a Cassandra or a Zookeeper server. If we append
these to root logger of default log4j.properties file the logs will be
displayed in non-profiled MB servers as well. That is why it is required to
keep two log4j.properties files.

Thanks!
Ishara

>
>
>> As I see, this can be get done only by maintaining two log4j properties
>> files with different configurations to be used in different profiles.
>>
>> Is it recommended to have two log4j properties files in one MB pack? Else
>> do you have any other solution for this?
>>
>> [1] https://wso2.org/jira/browse/MB-671
>>
>> Thanks
>> --
>> Sewwandi Perera
>> Software Engineer
>>
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Senior Software Engineer,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2MB topics where messages are automatically cleared

[Ishara Premadasa]

Hi Udara,

Can you please tell us what is your exact requirement? In general if you
use normal topics the messages will be discarded anyway if there is no
consumer currently available. However if you use queues/durable topics WSO2
MB do not delete the messages regardless of they have consumers or not.
They will be persisted in the broker till a consumer comes sometime and
receives them.

There is a JMS message header called 'JMSExpiration' where JMS providers (
the broker) set this field when a message is sent. When a message's
expiration time is reached, the provider should discard it [1]. However we
currently do not support this feature yet.

Thanks!
Ishara
[1]
http://docs.oracle.com/javaee/5/api/javax/jms/Message.html#getJMSExpiration%28%29



On Tue, May 20, 2014 at 8:38 PM, Udara Liyanage  wrote:

> Hi,
>
> Is there any type of queue/topic in MB where messages are deleted
> automatically after sometime if they are not consumed.
> Please point me to a doc if available.
>
>
>
> Touched, not typed. Erroneous words are a feature, not a typo.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Enabling Cassandra system logs with MB Cassandra profile

[Ishara Premadasa]

Hi,

As from WSO2 MB 2.2.0 onwards, we will be supporting a Cassandra profile
with MB where it will be used as the external Cassandra server. Therefore
it is required to enable Cassandra specific system logs with this profile
as these logs are heavily needed when analyzing any cassandra node issue
specially in a cluster.

To address this we have added a new log4jappender for cassandra profile as
below from MB 2.2.0 onwards.  By default this log file will be located in
/repository/logs/cassandra_system.log file.

#cassandra specific

log4j.logger.org.apache.cassandra=INFO, CASSANDRA_PROFILE
log4j.additivity.org.apache.cassandra=false

log4j.appender.CASSANDRA_PROFILE=org.apache.log4j.RollingFileAppender
log4j.appender.CASSANDRA_PROFILE.maxFileSize=20MB
log4j.appender.CASSANDRA_PROFILE.Threshold=INFO
log4j.appender.CASSANDRA_PROFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.CASSANDRA_PROFILE.layout.ConversionPattern=%c %5p [%t]
%d{ISO8601} %F (line %L) %m%n
# Edit the next line to point to your cassandra system logs directory
log4j.appender.CASSANDRA_PROFILE.File=${carbon.home}/repository/logs/cassandra_system.log

Thanks!
Ishara

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fixing Shutdown Errors WSO2 MB.

[Ishara Premadasa]

Hi Hasitha,

The cassandra service related shut down errors are fixed now by Prabath.
However i noticed few more shut down errors occurring from andes side when
gracefully shutting down cluster nodes, as below.

[2014-05-12 12:58:04,856]  INFO
{org.wso2.andes.server.cluster.ClusterManager} -  Handling cluster gossip:
Node with ID 0 left the cluster
[2014-05-12 12:58:04,856] ERROR
{org.wso2.andes.server.cluster.ClusterManager} -  Error while removing node
details
java.lang.RuntimeException: Error accessing Node details to cassandra
database
at
org.wso2.andes.server.store.CassandraMessageStore.deleteNodeData(CassandraMessageStore.java:4817)
at
org.wso2.andes.server.cluster.ClusterManager$NodeExistenceListener.process(ClusterManager.java:609)
at
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:519)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:495)

[2014-05-12 14:42:27,481] ERROR
{org.wso2.andes.server.cluster.ClusterManager} -  Error in getting
destination queues from store
org.wso2.andes.AMQStoreException: Error in loading queues [error code 541:
internal error]
at
org.wso2.andes.server.store.CassandraMessageStore.getDestinationQueues(CassandraMessageStore.java:4024)
at
org.wso2.andes.server.cluster.ClusterManager.getDestinationQueuesInCluster(ClusterManager.java:805)
at
org.wso2.andes.server.cluster.GlobalQueueWorker.isThisWorkerShouldWork(GlobalQueueWorker.java:216)
at
org.wso2.andes.server.cluster.GlobalQueueWorker.run(GlobalQueueWorker.java:75)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.wso2.andes.server.store.util.CassandraDataAccessException:
Error while getting data from : QueueDetails
at
org.wso2.andes.server.store.util.CassandraDataAccessHelper.getStringTypeColumnsInARow(CassandraDataAccessHelper.java:700)
at
org.wso2.andes.server.store.CassandraMessageStore.getDestinationQueues(CassandraMessageStore.java:4013)
... 6 more


The reason seems to be that, when we close the CassandraMessageStore we are
disconnecting the hector client connection with the cluster.
  cluster.getConnectionManager().shutdown();

However after that, there are node existence listeners etc. still get
triggered for the shutdown node and this cause the error logs.

IMO we have to shutdown the connection to cluster after we process all
these operations. Or is there any requirement that we close the hector
client pool in here?

Thanks!



On Thu, May 8, 2014 at 3:38 PM, Ishara Premadasa  wrote:

> Hi PrabathA et all,
>
> We are still experiencing this issue  as reported in [1] when shutting
> down. As stated by Hasitha it seems Cassandra message service thread is
> shutdown before we perform all data cleaning tasks in MB, as per below
> logs.
>
>
> *[2014-05-08 14:51:15,299]  INFO
> {org.apache.cassandra.net.MessagingService} -  Waiting for messaging
> service to quiesce[2014-05-08 14:51:15,303]  INFO
> {org.apache.cassandra.net.MessagingService} -  MessagingService shutting
> down server thread.*
> [2014-05-08 14:51:15,722]  INFO
> {org.wso2.andes.server.store.CassandraMessageStore} -  Clearing up
> Subscription Information
> [2014-05-08 14:51:15,722]  INFO
> {org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
> -  Clearing the Persisted State of Node with ID 0
> [2014-05-08 14:51:15,733] ERROR
> {org.apache.cassandra.thrift.CustomTThreadPoolServer} -  Error occurred
> during processing of message.
> java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has
> shut down
> at
> org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:61)
>
> Can we please know the progress of fixing this issue, or else can you
> please suggest us what might be the reason for cassandra service getting
> closed before deactivation of andes tasks are completed?
>
> Thanks!
> Ishara
>
> [1] https://wso2.org/jira/browse/MB-301
>
>
> On Mon, May 5, 2014 at 9:11 PM, Hasitha Hiranya  wrote:
>
>> Hi,
>>
>> Following is prabath's explanation
>>
>> There's no any impact on Cassandra from the Transport Listener Framework.
>> Carbon transport listener framework opens up the ports used by the
>> transports configured upon the Carbon Server. However, here in this
>> particular scenario, Cassandra daemon is responsible for opening up all the
>> ports used by a given Cassandra Server. Therefore, Cassandra related ports
>> are opened up much later after the transport listener framework is
>> initialised. Similarly, when it comes to shutting down the server, the
>> Cassandra daemon

[Dev] [Architecture] WSO2 Message Broker - 2.2.0 Beta Released!

[Ishara Premadasa]

WSO2 Message Broker 2.2.0 Beta Released!

WSO2 Message Broker  team is pleased to announce the release of 2.2.0 Beta
version of WSO2 Message Broker. This release is now available at [1],  and is
built upon r202634.

*How to Run*


The only prerequisite required to try this release out is an installation
of JDK 1.6 (Sun/Oracle JDK 1.6.0_23 or higher recommended)

   - Download the WSO2 MB 2.2.0- beta release from [1].
   - Extract the downloaded archive.
   - Go to the 'bin' directory and execute wso2server.sh (Unix/Linux) or
   wso2server.bat (Windows) as appropriate.
   - Point your web browser to http://localhost:9443/carbon to get started.
   - Use 'admin/admin' as the default username/password to be logged in.

 *New Features In this version*

   - Dead letter channel
   - Publisher flow control support
   - Improved queue/topic permission model
   - Carbon profiles support for Zookeeper and Cassandra profiles
   - JMS message selectors support
   - Improved UI with queue/topic subscriptions viewer

*Bug Fixes and Improvements*

Following bug fixes and improvements are available in the current release[2].

We highly appreciate your feedback on this beta release. Please report any
issues at https://wso2.org/jira/browse/MB. If you want to see a particular
feature changed or improved, drop us a mail at dev@wso2.org
orarchitect...@wso2.org

[1] https://svn.wso2.org/repos/wso2/scratch/MB-2.2.0/beta/
[2] https://wso2.org/jira/issues/?filter=11812

Thanks and Regards,
~ WSO2 MB Team ~

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
 Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832 <%2B94%20714445832>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fixing Shutdown Errors WSO2 MB.

[Ishara Premadasa]

Hi PrabathA et all,

We are still experiencing this issue  as reported in [1] when shutting
down. As stated by Hasitha it seems Cassandra message service thread is
shutdown before we perform all data cleaning tasks in MB, as per below
logs.


*[2014-05-08 14:51:15,299]  INFO
{org.apache.cassandra.net.MessagingService} -  Waiting for messaging
service to quiesce[2014-05-08 14:51:15,303]  INFO
{org.apache.cassandra.net.MessagingService} -  MessagingService shutting
down server thread.*
[2014-05-08 14:51:15,722]  INFO
{org.wso2.andes.server.store.CassandraMessageStore} -  Clearing up
Subscription Information
[2014-05-08 14:51:15,722]  INFO
{org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
-  Clearing the Persisted State of Node with ID 0
[2014-05-08 14:51:15,733] ERROR
{org.apache.cassandra.thrift.CustomTThreadPoolServer} -  Error occurred
during processing of message.
java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has
shut down
at
org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:61)

Can we please know the progress of fixing this issue, or else can you
please suggest us what might be the reason for cassandra service getting
closed before deactivation of andes tasks are completed?

Thanks!
Ishara

[1] https://wso2.org/jira/browse/MB-301


On Mon, May 5, 2014 at 9:11 PM, Hasitha Hiranya  wrote:

> Hi,
>
> Following is prabath's explanation
>
> There's no any impact on Cassandra from the Transport Listener Framework.
> Carbon transport listener framework opens up the ports used by the
> transports configured upon the Carbon Server. However, here in this
> particular scenario, Cassandra daemon is responsible for opening up all the
> ports used by a given Cassandra Server. Therefore, Cassandra related ports
> are opened up much later after the transport listener framework is
> initialised. Similarly, when it comes to shutting down the server, the
> Cassandra daemon is stopped before we shut down the listener framework.
>
> So Prabath, how does this affect the OSGI integration of services? How are
> we going to hold Cassandra until Andes is closed gracefully?
>
> Thanks
>
>
> On Sat, May 3, 2014 at 12:59 PM, Hasitha Hiranya wrote:
>
>> Hi,
>>
>> Prabath is looking into the issue. Prabath, were you able to find out the
>> reason why client transports are closed for Cassandra? Can you shed some
>> light on this?
>>
>> Thanks
>>
>>
>> On Fri, May 2, 2014 at 11:19 AM, Hasitha Hiranya wrote:
>>
>>> Looping in PrabathA.
>>>
>>>
>>> On Fri, May 2, 2014 at 11:18 AM, Hasitha Hiranya wrote:
>>>
 Hi Shameera,

 Good catch.

 [2014-05-02 10:12:19,015]  INFO {org.wso2.carbon.core.ServerManagement}
 -  Stopped all transport listeners
 [2014-05-02 10:12:19,015]  INFO {org.wso2.carbon.core.ServerManagement}
 -  Waiting for request service completion...
 [2014-05-02 10:12:19,019]  INFO {org.wso2.carbon.core.ServerManagement}
 -  All requests have been served.
 [2014-05-02 10:12:19,019]  INFO {org.wso2.carbon.core.ServerManagement}
 -  Waiting for deployment completion...
  [2014-05-02 10:12:19,021]  INFO
 {org.apache.cassandra.transport.Server} -  Stop listening for CQL clients

 What happens when all transport listeners are stopped?
 Stop listening for CQL clients means cassandra will no longer will
 accept requests from a cql client. Most probably same goes with Hector
 (Thrift) also. That might cause these issues.

 Thanks


 On Fri, May 2, 2014 at 11:12 AM, Shameera Rathnayaka >>> > wrote:

> Hi HasithaH,
>
> In the  shutdown logs i could see following line, before start andes
> deactivation,  what does actually mean? does it stop cassandra transport
> listener?
>
> [2014-05-02 10:12:19,021]  INFO
> {org.apache.cassandra.transport.Server} -  Stop listening for CQL clients
>
>
>
>
>
> On Fri, May 2, 2014 at 10:26 AM, Hasitha Hiranya wrote:
>
>> Hi Shameera,
>>
>> I have added logs and tested. Full Log is attached at (
>> https://drive.google.com/a/wso2.com/file/d/0B57HoxWKqqNnN2FPRE9FeC0yYXM/edit?usp=sharing).
>> Deactivate of andes service is like follows.
>>
>> protected void deactivate(ComponentContext ctx) {
>> // Unregister QpidService
>> System.out.println("+++Started deactivating
>> andes");
>> System.out.println("Unregistering qpid service");
>> try {
>> if (null != qpidService) {
>> qpidService.unregister();
>> }
>> } catch (Exception e) {}
>> System.out.println("+Unregistered
>> qpidService");
>> // Shutdown the Qpid broker
>> System.out.println("+Shutting down andes");
>> ApplicationRegis

Re: [Dev] [Coordination] Embedded zookeeper in coordination component doesn't start ZooKeeperSaslServer

[Ishara Premadasa]

Hi Indika,

When further debugged i could find that in the coordination component,
jaas.conf  and java.env files are not read when SASL is enabled, therefore
Zookeeper ServerCnxnFactory skips the creation of ZooKeeperSaslServer
instance as jaas.conf entries not found. This is currently fixed in
r201478.

We need to add this into 2.2.0 documentation as well. I have created [1]
for that.
@Tania,
Please note.

Thanks!
Ishara

[1] https://wso2.org/jira/browse/DOCUMENTATION-777


On Wed, Apr 30, 2014 at 11:59 AM, Indika Sampath  wrote:

> Hi Ishara,
>
> Herewith I have attached jaas.conf and java.env files. You need to add
> these two files to /repository/conf/etc/ where MB instance start
> as zookeeper profile. After that change the path of jaas.conf  in the
> java.env. Also check the /repository/conf/security/jaas.conf file
> exist. If it is not exist copy the jaas.conf. The issue seems to be MB
> server start as zookeeper won't get the SASL configuration properly. Anyway
> you can further debug and see with these configuration settings.
>
> Cheers!
>
>
>
>
> On Tue, Apr 29, 2014 at 11:46 PM, Ishara Premadasa wrote:
>
>> Hi,
>>
>> From WSO2 MB 2.2.0 onwards we will be supporting zookeeper profiles with
>> MB where a message broker instance can be started as a zookeeper server as
>> well by using carbon profiles. For this we use embedded zookeeper server
>> that getting shipped with Coordination component. However as stated in [1]
>> when enabled SASL security for zookeeper server, the coordination server (
>> which is zk server here) doesn't seem to initiate a ZooKeeperSaslServer
>> object, but still it starts a non-SASL Zookeeper server only.
>>
>> I enabled the debug logs for zookeeper server and once the client tries
>> to connect to server with providing client login data the following error
>> logs can be seen at zk server side and client side.
>>
>> *server side ( MB with zookeeper profile enabled)*
>> [2014-04-29 22:06:31,316] DEBUG
>> {org.apache.zookeeper.server.ZooKeeperServer} -  Responding to client SASL
>> token.
>> [2014-04-29 22:06:31,316] DEBUG
>> {org.apache.zookeeper.server.ZooKeeperServer} -  Size of client SASL token:
>> 0
>> [2014-04-29 22:06:31,317] ERROR
>> {org.apache.zookeeper.server.ZooKeeperServer} -  cnxn.saslServer is null:
>> cnxn object did not initialize its saslServer properly.
>>
>> *client side ( MB server which connects to zookeeper)*
>> [2014-04-29 22:06:31,313] DEBUG
>> {org.apache.zookeeper.client.ZooKeeperSaslClient} -
>> ClientCnxn:sendSaslPacket:length=0
>> [2014-04-29 22:06:31,319] ERROR
>> {org.apache.zookeeper.client.ZooKeeperSaslClient} -  SASL authentication
>> failed using login context 'Client'.
>>
>> To get this verified, i tested the same scenario by pointing to an
>> external Apache zookeeper server where client was able to successfully
>> authenticate through same credentials as below logs.
>>
>> [2014-04-29 22:12:10,873] DEBUG
>> {org.apache.zookeeper.client.ZooKeeperSaslClient} -
>> ClientCnxn:sendSaslPacket:length=0
>> [2014-04-29 22:12:10,873] DEBUG
>> {org.apache.zookeeper.client.ZooKeeperSaslClient} -
>> saslClient.evaluateChallenge(len=101)
>> [2014-04-29 22:12:10,874] DEBUG
>> {org.apache.zookeeper.client.ZooKeeperSaslClient} -
>> ClientCnxn:sendSaslPacket:length=276
>> [2014-04-29 22:12:10,876] DEBUG
>> {org.apache.zookeeper.client.ZooKeeperSaslClient} -
>> saslClient.evaluateChallenge(len=40)
>> [2014-04-29 22:12:10,877] DEBUG {org.apache.zookeeper.ClientCnxn} -
>> Reading reply sessionid:0x145ae5b1d2e0002, packet:: clientPath:null
>> serverPath:null finished:false header:: 3,3  replyHeader:: 3,5,-101
>> request:: '/queue_workers_parent,F  response::
>>
>> Therefore it seems coordination server doesn't start zookeeper instance
>> by verifying whether security enabled or not. We need to get this fixed for
>> MB 2.2.0 and i am currently working on it. If there is any configuration
>> available for coordination server to handle this without changing the
>> source please mention it here.
>>
>> Thanks!
>> Ishara
>>
>> [1] https://wso2.org/jira/browse/MB-601
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>>
>>
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> <http://isharapremadasa.blogspot.com/> Twitter   :
>> https://twitter.com/ishadil <https://twitter.com/ishadil>Mobile   : +94
>> 714445832 <%2B94%20714445832>*
>>
>>
>>
>
>
> --
> Indika Sampath
> Software Engineer
> WSO2 Inc.
> http://wso2.com
>
> Phone: +94 716 424 744
> Blog: http://indikasampath.blogspot.com/
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
<http://isharapremadasa.blogspot.com/>Twitter   :
https://twitter.com/ishadil <https://twitter.com/ishadil>Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Coordination] Embedded zookeeper in coordination component doesn't start ZooKeeperSaslServer

[Ishara Premadasa]

Hi,

>From WSO2 MB 2.2.0 onwards we will be supporting zookeeper profiles with MB
where a message broker instance can be started as a zookeeper server as
well by using carbon profiles. For this we use embedded zookeeper server
that getting shipped with Coordination component. However as stated in [1]
when enabled SASL security for zookeeper server, the coordination server (
which is zk server here) doesn't seem to initiate a ZooKeeperSaslServer
object, but still it starts a non-SASL Zookeeper server only.

I enabled the debug logs for zookeeper server and once the client tries to
connect to server with providing client login data the following error logs
can be seen at zk server side and client side.

*server side ( MB with zookeeper profile enabled)*
[2014-04-29 22:06:31,316] DEBUG
{org.apache.zookeeper.server.ZooKeeperServer} -  Responding to client SASL
token.
[2014-04-29 22:06:31,316] DEBUG
{org.apache.zookeeper.server.ZooKeeperServer} -  Size of client SASL token:
0
[2014-04-29 22:06:31,317] ERROR
{org.apache.zookeeper.server.ZooKeeperServer} -  cnxn.saslServer is null:
cnxn object did not initialize its saslServer properly.

*client side ( MB server which connects to zookeeper)*
[2014-04-29 22:06:31,313] DEBUG
{org.apache.zookeeper.client.ZooKeeperSaslClient} -
ClientCnxn:sendSaslPacket:length=0
[2014-04-29 22:06:31,319] ERROR
{org.apache.zookeeper.client.ZooKeeperSaslClient} -  SASL authentication
failed using login context 'Client'.

To get this verified, i tested the same scenario by pointing to an external
Apache zookeeper server where client was able to successfully authenticate
through same credentials as below logs.

[2014-04-29 22:12:10,873] DEBUG
{org.apache.zookeeper.client.ZooKeeperSaslClient} -
ClientCnxn:sendSaslPacket:length=0
[2014-04-29 22:12:10,873] DEBUG
{org.apache.zookeeper.client.ZooKeeperSaslClient} -
saslClient.evaluateChallenge(len=101)
[2014-04-29 22:12:10,874] DEBUG
{org.apache.zookeeper.client.ZooKeeperSaslClient} -
ClientCnxn:sendSaslPacket:length=276
[2014-04-29 22:12:10,876] DEBUG
{org.apache.zookeeper.client.ZooKeeperSaslClient} -
saslClient.evaluateChallenge(len=40)
[2014-04-29 22:12:10,877] DEBUG {org.apache.zookeeper.ClientCnxn} -
Reading reply sessionid:0x145ae5b1d2e0002, packet:: clientPath:null
serverPath:null finished:false header:: 3,3  replyHeader:: 3,5,-101
request:: '/queue_workers_parent,F  response::

Therefore it seems coordination server doesn't start zookeeper instance by
verifying whether security enabled or not. We need to get this fixed for MB
2.2.0 and i am currently working on it. If there is any configuration
available for coordination server to handle this without changing the
source please mention it here.

Thanks!
Ishara

[1] https://wso2.org/jira/browse/MB-601

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] Moving FE operations to BE

[Ishara Premadasa]

Hi Indika,

Your observation is correct that getAccessKey() method is not exposed to
all the users, however few clarifications to made is this method is not
configured to admin role only. According to the current permission model in
carbon we can create new roles and assign permissions to that accordingly.
However if you look at the permission tree there is only two MB related
permission options named,


MB




   -


  Add Queue







  -  Queue Details

Therefore for a user to perform other queue operations than this, we need
to provide admin--> configure permission as shown in image [1] which is the
reason getAccessKey() is bound to /permission/admin/configure level. (This
is more like for any user to work with MB it needs some admin priviledges
)Therefore IMO it would be better if we can add more options to above MB
level permissions like Browse Queue etc. so user can be authorized to
getAccessKey()
by selecting that permission rather than moving the operations into BE.


On Wed, Apr 9, 2014 at 11:48 AM, Indika Sampath  wrote:

> Hi All,
>
> There is an issue with browsing the queue for users which haven't admin
> role. The reason is following two methods restricted to the admin role in
> Axis2 level.
>
>- getCurrentUser()
>- getAccessKey()
>
> There is a way to get the current logged user from the session but there
> is no way to get the access key.
> org.wso2.carbon.andes.ui.client.QueueBrowserClient creating a queue
> connection and access the queue from the FE. We need user name and access
> key to creating queue connection. There might be some security issue with
> QueueBrowserClient as I and Hasitha had discussion with Suresh on
> yesterday. Some operations in org.wso2.carbon.andes.ui module needs to move
> to the BE. I have come up with the following implementation design.
>
> Move following methods in the QueueBrowserClient to
> org.wso2.carbon.andes.core.QueueManagerService and expose as web service
> via org.wso2.carbon.andes.admin.AndesAdminService.
>
>
>- browseQueue()
>- closeBrowser()
>- getMsgContentType()
>- getMessageContentAsString()
>
> When we change like this we need to call the BE four times for each Browse
operation and this would be same for publish sample msg, purge queue etc.
which we don't necessarily have to go for BE. Wouldn't it be an overhead
that we make several FE <--> BE calls for a single UI operation each time?

Thanks!
Ishara

[1]
https://svn.wso2.org/repos/wso2/people/isharap/permissions_non_admin_user.png


> But there are another two classes
> org.wso2.carbon.andes.ui.client.QueueReceiverClient and
> org.wso2.carbon.andes.ui.client.QueueSenderClient needs do the same thing
> as I think.
>
> Cheers!
>
> --
> Indika Sampath
> Software Engineer
> WSO2 Inc.
> http://wso2.com
>
> Phone: +94 716 424 744
> Blog: http://indikasampath.blogspot.com/
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][MB] Providing JMS Message Selectors Support for WSO2 MB

[Ishara Premadasa]

Hi all,

I have committed the initial implementation in revision r199114 where it
does provide selector support for Queues and Durable Topics. When looking
at the source i could find that we were already having message selectors
for Topics and there was no need to re-implement it.

Since there are a whole list of different patterns that can be used in
selector strings we need to test them extensively against both
topics/queues and identify which literals,logics etc. are supported by
selectors and which are not. As the first phase we are going to test
against the selectors in [1] as well as testing against all the JMS headers
and properties.

As per the JMS Headers the following headers are supported with selectors,
where a client can set and send to broker.

*JMSCorrelationID  JMSReplyTo  JMSType *

The below header properties will not be filtered by broker since they are
handled by the JMS provider and set into the default values at broker side
as describer here. [2]

*JMSPriority  JMSExpiration  JMSDeliveryMode*

Once these are tested we can update the MB 2.2.0 docs with supported
syntaxes and headers for Message Selectors.

Thanks!
Ishara

[1]
http://www.novell.com/documentation/extend5/Docs/help/Composer/books/JMSAppendixB.html
[2] http://docs.oracle.com/cd/E19798-01/821-1841/bnces/index.html



On Thu, Mar 27, 2014 at 10:34 AM, Pamod Sylvester  wrote:

> +1 to handle it from the server side, also considering the fact of sending
> irrelevant messages to client will be an additional network overhead.
>
>
> On Thu, Mar 27, 2014 at 10:18 AM, Ishara Premadasa wrote:
>
>> Hi all,
>>
>> We are going to implement message selectors support [1] into WSO2 Message
>> Broker where a message consumer is allowed to specify the messages it is
>> interested by using a selector string and the broker (JMS provider) does
>> the filtering of messages according to that query. The syntax of the JMS
>> selector expression is based on a subset of SQL92, mentioned here [2].
>>
>> Message selectors can be implemented either using the client-side or
>> server-side. As the first try i have tried with filtering the messages in
>> the client-side where the filtering happens after the message is dispatched
>> into client side.
>>
>> However we had some considerable issues with this method since the
>> messages which were rejected by the consumer's selector cannot be
>> re-delivered to other consumers who do not have filters, and those messages
>> were stuck in queue. Therefore since this was not possible to be handled in
>> the client-side we moved the implementation server-side.
>>
>> Therefore with the current implementation at server side when the
>> messages are sending out to subscribers we check whether the message
>> matches the filters and if so that will be given out to the subscriber. If
>> not that message will be removed from already read messages, hence it can
>> be given to another matching subscriber in the next round.
>>
>> I will be updating this thread with the progress of the implementation.
>> The plan is to send this out with 2.2.0 version, however if takes more time
>> this will be definitely available with MB 3.0.0 version.  Any
>> feedback/suggestions are welcome.
>>
>> Thanks!
>> Ishara
>>
>> [1] http://docs.oracle.com/cd/E19798-01/821-1841/bncer/index.html
>> [2]
>> http://www.novell.com/documentation/extend5/Docs/help/Composer/books/JMSAppendixB.html
>>
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>>
>>
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> <http://isharapremadasa.blogspot.com/>Twitter   :
>> https://twitter.com/ishadil <https://twitter.com/ishadil> Mobile   :
>> +94 714445832 <%2B94%20714445832>*
>>
>>
>>
>
>
> --
> *Pamod Sylvester *
>  * Software Engineer *
> Integration Technologies Team, WSO2 Inc.; http://wso2.com
> email: pa...@wso2.com cell: +94 77 7779495
>



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
<http://isharapremadasa.blogspot.com/>Twitter   :
https://twitter.com/ishadil <https://twitter.com/ishadil>Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Remove entries from default carbon.xml file in products

[Ishara Premadasa]

Hi Carbon team,

We no longer ships an embedded qpid broker with any product where this is
replaced by WSO2 MB. Therefore currently it is not supported to use these
entries to change Message Broker's ports and hence keeping these might
mislead the users.

Therefore can we please get the following entries under the 
elelment, removed from carbon.xml file file. Created [1] for this.




5672

8672


 Thanks!
Ishara

[1] https://wso2.org/jira/browse/CARBON-14745

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][MB] Providing JMS Message Selectors Support for WSO2 MB

[Ishara Premadasa]

Hi all,

We are going to implement message selectors support [1] into WSO2 Message
Broker where a message consumer is allowed to specify the messages it is
interested by using a selector string and the broker (JMS provider) does
the filtering of messages according to that query. The syntax of the JMS
selector expression is based on a subset of SQL92, mentioned here [2].

Message selectors can be implemented either using the client-side or
server-side. As the first try i have tried with filtering the messages in
the client-side where the filtering happens after the message is dispatched
into client side.

However we had some considerable issues with this method since the messages
which were rejected by the consumer's selector cannot be re-delivered to
other consumers who do not have filters, and those messages were stuck in
queue. Therefore since this was not possible to be handled in the
client-side we moved the implementation server-side.

Therefore with the current implementation at server side when the messages
are sending out to subscribers we check whether the message matches the
filters and if so that will be given out to the subscriber. If not that
message will be removed from already read messages, hence it can be given
to another matching subscriber in the next round.

I will be updating this thread with the progress of the implementation. The
plan is to send this out with 2.2.0 version, however if takes more time
this will be definitely available with MB 3.0.0 version.  Any
feedback/suggestions are welcome.

Thanks!
Ishara

[1] http://docs.oracle.com/cd/E19798-01/821-1841/bncer/index.html
[2]
http://www.novell.com/documentation/extend5/Docs/help/Composer/books/JMSAppendixB.html


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] WSO2 MB DLC Implementation Status

[Ishara Premadasa]

Hi Asanka/Shani,


On Mon, Mar 24, 2014 at 12:11 PM, Shani Ranasinghe  wrote:

> Hi,
>
> +1, yes we could use the same way the queue's are handled. Have the list
> of queues in DLC with the destination queue name, and number of messages,
> and through the browse button you can browse the message.
>

yes, we can do this categorization as a future improvement.

>
>
> On Sun, Mar 23, 2014 at 11:36 PM, Pamod Sylvester  wrote:
>
>> +1 for the approach to add further filtering per queue. Currently from
>> the server the destination queue information is sent to the UI. We might
>> need to add some filtering per queue basis and re categorize them.
>>
>> @Ishara/Shani : WDYT about the approach ?
>>
>>
>> On Mon, Mar 24, 2014 at 11:55 AM, Asanka Vithanage wrote:
>>
>>> Hi All,
>>>
>>> While going through the current DLC implementation, I felt there is a
>>> room to improve the UI side of the DLC further.
>>>
>>> Currently we are storing all the dead letters in an single queue, and
>>> only the interface [1] available to access DLC queue.
>>> There can be thousand no of messages from different queues stored on DLC
>>> queue So it wont be easy to sort out messages belong to a single queue and
>>> do a required operation like restore, purge with the current implementation.
>>>
>>> As a solution while keeping the dead letter channel UI, we can filter
>>> out all the dead letters according to the queues and keep a link on the
>>> available queue details UI [2] with the dead letter message count. So users
>>> can get a full view of queue status in an one place and do the all queue
>>> related operations.
>>>
>>
+1, As i have stated above, we will enable per queue viewing of message
count and browse the content in future so users will find it easy monitor
the DLC. If so there won't be no need to get the DLC message count from
original queue.

Thanks!

>
>>> WDYT?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Mar 22, 2014 at 2:42 PM, Pamod Sylvester  wrote:
>>>
 The latest code of the DLC implementation is committed with r198710.
 Currently we're progressing in implementing the feature to be tenant aware,

 for the tenant aware model a DLC queue will be created per tenant, the
 queue signature will be *{tenantdomain}/DeadLetterChannel*.

 The above model should be adopted in the UI as well, where the DLC
 queue should be filtered and pointed based on the above signature.

 @Shani/Ishara : will it be possible to reflect the changes in the UI as
 well ?


 On Fri, Feb 28, 2014 at 2:39 PM, Pamod Sylvester wrote:

> Attached diff contains the Dead Letter Channel (DLC) server
> side implementation. Shani will be able to provide input on the UI
> component.
>
> The following is the nature of the DLC feature implementation,
>
> ~ External parties will not be allowed to publish/subscribe to the DLC
> queue.
> ~ Messages in the DLC could be restored back to its origin queue or
> could be deleted (When deleting it was ensured that data from the 
> NodeQueue
> CF, GlobalQueueCF and MessageContentCF was deleted)
>
> In addition to the above, an enhancement was Incorporated which will
> allow a user to specify a different destination queue other than its 
> origin
> queue for the message to be restored. The admin service signature for
> the functionality is as follows,
>
> restoreMessagesFromDeadLetterQueueToDifferentDestination(String[]
> messageIDs, String destination)
>
> @Shani : will it be possible for you to add the capability in the UI
> to allow users to specify a destination queue of their choice and invoke
> the above service ?
>
> Please do let know if there're any amendments to be done in the
> existing flows.
>
> Thanks,
> Pamod
>
>
>
>
> On Sat, Feb 15, 2014 at 11:14 AM, Pamod Sylvester wrote:
>
>> Hi All,
>>
>> The current status of the DLC implementation is described from the
>> following,
>>
>> ~ During the time where the messages are intended to be dropped after
>> the re-trying count has exceeded, it will first be stored in the Dead
>> Letter Channel queue which is an entry of the NodeQueues CF and the
>> messages will be purged.
>> ~ Implemented the functionality to delete a specific message from the
>> DLC through providing it an id of the message, and also restore a message
>> back
>> ~ The re storing process will basically cut-past the message content
>> stored in the DLC entry in the NodeQueues CF back to the Global Queue.
>>
>> TO-DOs
>>
>> ~ Currently the dead-letter queue is created and listed as a general
>> queue, which will also be listed along with the other queues. Need to
>> discuss and figure out to list it as a separate entity. Need to modify 
>> the
>> permissions of that queue which will prevent the external users f

Re: [Dev] [DEV] WSO2 MB DLC Implementation Status

[Ishara Premadasa]

We (Pamod,Hasitha,Shammi and myself ) had a meeting on the current state of
the DLC implementation. Following is the concerns raised and the agreed
solutions.

*1. What if user deletes original queue when there are messages addressed
to that queue remains in DLC ?*

When user decides to delete queue since that means he is no longer
interested in that queue of messages came under that. Therefore when user
deletes queue we delete the DLC messages which are address to the original
queue.

*2. Users should not be able to publish, subscribe to DLC but only to
browse queue. ?*

Currently this is done by comparing queue name against DLC queue nameand
restricting access if that matches. Indika is currently working on
implementing queue permission model for MB, and once this is complete we
can simply enable on 'Browse' option for DLC and disable other permissions.
Created [1] for this.

@Indika,

Pls note we need to provide a specific 'browse' permission option in queue
security model too.

*3. What would be the expiration time for messages in DLC?*

They will be in the queue for lifetime. Messages won't be removed from DLC
if not deleted/restored by the user.

@Pamod/Hasitha,
pls add if i missed anything.

Thanks!
Ishara

[1] https://wso2.org/jira/browse/MB-486


On Mon, Mar 24, 2014 at 3:11 PM, Ishara Premadasa  wrote:

> Hi Asanka/Shani,
>
>
> On Mon, Mar 24, 2014 at 12:11 PM, Shani Ranasinghe  wrote:
>
>> Hi,
>>
>> +1, yes we could use the same way the queue's are handled. Have the list
>> of queues in DLC with the destination queue name, and number of messages,
>> and through the browse button you can browse the message.
>>
>
> yes, we can do this categorization as a future improvement.
>
>>
>>
>> On Sun, Mar 23, 2014 at 11:36 PM, Pamod Sylvester  wrote:
>>
>>> +1 for the approach to add further filtering per queue. Currently from
>>> the server the destination queue information is sent to the UI. We might
>>> need to add some filtering per queue basis and re categorize them.
>>>
>>> @Ishara/Shani : WDYT about the approach ?
>>>
>>>
>>> On Mon, Mar 24, 2014 at 11:55 AM, Asanka Vithanage wrote:
>>>
>>>> Hi All,
>>>>
>>>> While going through the current DLC implementation, I felt there is a
>>>> room to improve the UI side of the DLC further.
>>>>
>>>> Currently we are storing all the dead letters in an single queue, and
>>>> only the interface [1] available to access DLC queue.
>>>> There can be thousand no of messages from different queues stored on
>>>> DLC queue So it wont be easy to sort out messages belong to a single queue
>>>> and do a required operation like restore, purge with the current
>>>> implementation.
>>>>
>>>> As a solution while keeping the dead letter channel UI, we can filter
>>>> out all the dead letters according to the queues and keep a link on the
>>>> available queue details UI [2] with the dead letter message count. So users
>>>> can get a full view of queue status in an one place and do the all queue
>>>> related operations.
>>>>
>>>
> +1, As i have stated above, we will enable per queue viewing of message
> count and browse the content in future so users will find it easy monitor
> the DLC. If so there won't be no need to get the DLC message count from
> original queue.
>
> Thanks!
>
>>
>>>> WDYT?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, Mar 22, 2014 at 2:42 PM, Pamod Sylvester wrote:
>>>>
>>>>> The latest code of the DLC implementation is committed with r198710.
>>>>> Currently we're progressing in implementing the feature to be tenant 
>>>>> aware,
>>>>>
>>>>> for the tenant aware model a DLC queue will be created per tenant, the
>>>>> queue signature will be *{tenantdomain}/DeadLetterChannel*.
>>>>>
>>>>> The above model should be adopted in the UI as well, where the DLC
>>>>> queue should be filtered and pointed based on the above signature.
>>>>>
>>>>> @Shani/Ishara : will it be possible to reflect the changes in the UI
>>>>> as well ?
>>>>>
>>>>>
>>>>> On Fri, Feb 28, 2014 at 2:39 PM, Pamod Sylvester wrote:
>>>>>
>>>>>> Attached diff contains the Dead Letter Channel (DLC) server
>>>>>> side implementation. Shani will be able t

Re: [Dev] Chunk08 Service Stubs build failure

[Ishara Premadasa]

Hi Lakmail,

Did you try with updating org.wso2.carbon.andes.stub in service-stubs and
rebuild? I tried in a clean repo and this builds fine for me. Can you
please try updating andes.stub/4.2.1?

thanks!


On Fri, Mar 21, 2014 at 7:58 PM, Lakmali Baminiwatta wrote:

> Hi all,
>
> I am getting below error while building the service stubs.
>
>  Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
> (default-compile) on project org.wso2.carbon.andes.stub: Compilation failure
> [ERROR]
> /home/lakmali/trunk/platform/branches/turing/service-stubs/org.wso2.carbon.andes.stub/4.2.1/target/generated-code/src/org/wso2/carbon/andes/stub/AndesAdminServiceStub.java:[199,25]
> cannot access javax.wsdl.Definition
> [ERROR] class file for javax.wsdl.Definition not found
> [ERROR] _serviceClient = new
> org.apache.axis2.client.ServiceClient(configurationContext,_service);
>
> My kernel changes are up to date , but getting this error. Any idea?
>
> Thanks,
> Lakmali
>
>
> --
> Lakmali Baminiwatta
>  Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> mobile:  +94 71 2335936
> blog : lakmali.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please deploy released MB Jars to nexus repos

[Ishara Premadasa]

Hi Pradeep,

MB 2.1.1 which was released this week is a Carbon 4.1.0 based patch
release. MB 2.2.0 is scheduled be released on Carbon 4.2.0 end of this
month or early April.

However we will be deploying 4.1.7 andes features into nexus repo asap.

Thanks!
Ishara


On Sun, Mar 16, 2014 at 5:05 PM, Pradeep Fernando  wrote:

> Hi MB team,
>
> Can you please do the $subject. I need carbon 4.2.0 based MB features. I
> think it is yet to be done since i can't find it here,
>
>
> http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/org.wso2.carbon.andes.feature/
>
> If not, it is understandable since latest MB got released days before. :)
> Please be kind enough to deploy the jars asap..
>
> thanks,
> --Pradeep
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Dev-MB] Guaranteed Message Delivery issue in fail over

[Ishara Premadasa]

Hi Iranga,

What are the failover options you have used in the connection string? Are
there 'retries' and 'connectdelay' options configured. They determine the
number of times a connection to a broker will be retried and the the length
of time to wait between successive connection attempts before moving on to
the next broker in. Have we tried with setting retires to 1 and
connectdelay to 0 ( which are default values) so then the broker will try
to connect immediately to the next one available?

Thanks!


On Thu, Mar 13, 2014 at 3:59 PM, Iranga Muthuthanthri wrote:

> Hi All,
>
> In a MB message produce consume scenario for fail over, if the message
> producing MB node fails before delivering all the messages it was observed
> that there was a message loss(by observing the Cassandra  queue count).
>
> What are the workaround possible for this considering the guaranteed
> message delivery model.
>
> Note: The message consuming and producing MB nodes are the same.
>
>
> --
> Thanks & Regards
>
> Iranga Muthuthanthri
> Technical Lead - QA
> (M) -0777-255773
>



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting OperationNotSupportedException when creating the initial context for tenants

[Ishara Premadasa]

Hi Melan,

IIRC we came through a similar issue when testing WSO2 MB 2.1.0 in tenant
mode as reported in [1].  The fix suggested by Ajanthan should work in here.

[1] https://wso2.org/jira/browse/MB-283

Thanks!


On Mon, Jan 27, 2014 at 1:26 PM, Ajanthan Balachandran wrote:

> Hi Melan ,
> Can you set "org.wso2.carbon.context.RequestBaseContext" property in
> the jndi environment properties  to  get InitialContext.?
>
> E.g :-
>
> environment = new Hashtable();
> 
> 
> environment.put(CarbonConstants.REQUEST_BASE_CONTEXT, "true");
> context = new InitialDirContext(environment);
>
> Thanks.
>
> On Fri, Jan 24, 2014 at 9:33 PM, Isuru Haththotuwa 
> wrote:
> > [looping in dev list]
> >
> >
> > On Fri, Jan 24, 2014 at 7:04 PM, Melan Nimesh  wrote:
> >>
> >> Hi,
> >>
> >> We noticed the error mentioned in $subject when creating tenants on
> >> Stratos manager (Carbon 4.2 based),  Any idea why this error occurring?
> >>
> >> TID: [0] [SCC] [2014-01-24 13:03:06,436] ERROR
> >> {org.apache.stratos.messaging.broker.publish.TopicPublisher} -  Error
> while
> >> publishing to the topic: tenant
> >> {org.apache.stratos.messaging.broker.publish.TopicPublisher}
> >> java.lang.RuntimeException: An error occurred while creating the initial
> >> context for tenant: 4
> >> at
> >>
> org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.getInitialContext(CarbonContextDataHolder.java:873)
> >> at
> >>
> org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.lookup(CarbonContextDataHolder.java:916)
> >> at javax.naming.InitialContext.lookup(InitialContext.java:392)
> >> at
> >>
> org.apache.stratos.messaging.broker.connect.TopicConnector.init(TopicConnector.java:60)
> >> at
> >>
> org.apache.stratos.messaging.broker.publish.TopicPublisher.setPublisher(TopicPublisher.java:120)
> >> at
> >>
> org.apache.stratos.messaging.broker.publish.TopicPublisher.doPublish(TopicPublisher.java:95)
> >> at
> >>
> org.apache.stratos.messaging.broker.publish.TopicPublisher.publish(TopicPublisher.java:75)
> >> at
> >>
> org.apache.stratos.messaging.broker.publish.EventPublisher.publish(EventPublisher.java:48)
> >> at
> >>
> org.apache.stratos.manager.subscription.utils.CartridgeSubscriptionUtils.publishTenantSubscribedEvent(CartridgeSubscriptionUtils.java:117)
> >> at
> >>
> org.apache.stratos.manager.manager.CartridgeSubscriptionManager.subscribeToCartridgeWithProperties(CartridgeSubscriptionManager.java:230)
> >> at
> >>
> org.apache.stratos.rest.endpoint.services.ServiceUtils.subscribe(ServiceUtils.java:645)
> >> at
> >>
> org.apache.stratos.rest.endpoint.services.StratosAdmin.subscribe(StratosAdmin.java:278)
> >> 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:597)
> >> at
> >>
> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
> >> at
> >>
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
> >> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
> >> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
> >> at
> >>
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
> >> at
> >>
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
> >> at
> >>
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
> >> at
> >>
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> >> at
> >>
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
> >> at
> >>
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
> >> at
> >>
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
> >> at
> >>
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
> >> at
> >>
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
> >> at
> >>
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
> >> at
> >>
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
> >> at
> >>
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:262)
> >> at
> >>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> >> at
> >>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> >> at
> >>
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWr

Re: [Dev] WSO2 MB Subscriber Client with Spring configuration

[Ishara Premadasa]

Hi Aliosha,

I tried the same example with above spring-config.xml and was able to run
the JMS Subscriber without issue.

However according to the error log it seems your spring configuration is
unable to find the InitialContextFactory of the JNDI Provider. Therefore
first make sure you have correctly added 'andes-client-0.13.wso2v8.jar'
file as a dependency into the project classpath.
If it is already there in the external libraries, please define
InitialContextFactory as  element in configuration as
below and see with running subscriber client back.




java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory



Thanks,
Ishara


On Wed, Jan 1, 2014 at 4:22 PM, Aliosha  wrote:

> I m facing up with the subscriber client configuration using spring-jms. I
> m following this example:
>
> http://docs.wso2.org/display/MB210/Topic+subscriber+and+topic+publisher
>
> in which the client is coded like this:
>
> import javax.jms.JMSException;
> import javax.jms.Message;
> import javax.jms.QueueSession;
> import javax.jms.TextMessage;
> import javax.jms.Topic;
> import javax.jms.TopicConnection;
> import javax.jms.TopicConnectionFactory;
> import javax.jms.TopicSession;
> import javax.naming.Context;
> import javax.naming.InitialContext;
> import javax.naming.NamingException;
> import java.util.Properties;
>
> public class TopicSubscriber {
> public static final String QPID_ICF = 
> "org.wso2.andes.jndi.PropertiesFileInitialContextFactory";
> private static final String CF_NAME_PREFIX = "connectionfactory.";
> private static final String CF_NAME = "qpidConnectionfactory";
> String userName = "admin";
> String password = "admin";
> private static String CARBON_CLIENT_ID = "carbon";
> private static String CARBON_VIRTUAL_HOST_NAME = "carbon";
> private static String CARBON_DEFAULT_HOSTNAME = "localhost";
> private static String CARBON_DEFAULT_PORT = "5672";
> String topicName = "MYTopic";
>
> public static void main(String[] args) throws NamingException, 
> JMSException {
> TopicSubscriber topicSubscriber = new TopicSubscriber();
> topicSubscriber.subscribe();
> }
> public void subscribe() throws NamingException, JMSException {
> Properties properties = new Properties();
> properties.put(Context.INITIAL_CONTEXT_FACTORY, QPID_ICF);
> properties.put(CF_NAME_PREFIX + CF_NAME, 
> getTCPConnectionURL(userName, password));
> System.out.println("getTCPConnectionURL(userName,password) = " +
> getTCPConnectionURL(userName, password));
> InitialContext ctx = new InitialContext(properties);
> // Lookup connection factory
> TopicConnectionFactory connFactory = (TopicConnectionFactory) 
> ctx.lookup(CF_NAME);
> TopicConnection topicConnection = connFactory.createTopicConnection();
> topicConnection.start();
> TopicSession topicSession =
> topicConnection.createTopicSession(false, 
> QueueSession.AUTO_ACKNOWLEDGE);
> // Send message
> Topic topic = topicSession.createTopic(topicName);
> javax.jms.TopicSubscriber topicSubscriber = 
> topicSession.createSubscriber(topic);
> Message message = topicSubscriber.receive();
> if (message instanceof TextMessage) {
> TextMessage textMessage = (TextMessage) message;
> System.out.println("textMessage.getText() = " + 
> textMessage.getText());
> }
> topicSubscriber.close();
> topicSession.close();
> topicConnection.stop();
> topicConnection.close();
> }
> public String getTCPConnectionURL(String username, String password) {
> // 
> amqp://{username}:{password}@carbon/carbon?brokerlist='tcp://{hostname}:{port}'
> return new StringBuffer()
> .append("amqp://").append(username).append(":").append(password)
> .append("@").append(CARBON_CLIENT_ID)
> .append("/").append(CARBON_VIRTUAL_HOST_NAME)
> 
> .append("?brokerlist='tcp://").append(CARBON_DEFAULT_HOSTNAME).append(":").append(CARBON_DEFAULT_PORT).append("'")
> .toString();
> }
> }
>
>
> By Spring i'm trying to set up the connection factory by this code:
>
> 
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xmlns:jms="http://www.springframework.org/schema/jms";
>   xmlns:jee="http://www.springframework.org/schema/jee";
>xsi:schemaLocation="http://www.springframework.org/schema/beans 
> http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
>http://www.springframework.org/schema/jms 
> http://www.springframework.org/schema/jms/spring-jms-3.0.xsd
>http://www.springframework.org/schema/jee 
> http://www.springframework.org/schema/jee/spring-jee.xsd";>
>
> 
>
>
> But in this way i get this error: javax.naming.NoInitialContextException: 
> Need to specify class name in environment or system p

Re: [Dev] WSO2 Committers += Shani

[Ishara Premadasa]

Congrats Shani... :)


On Mon, Dec 16, 2013 at 6:12 PM, Chanika Geeganage  wrote:

> Congratulations Shani!!
>
>
> On Mon, Dec 16, 2013 at 6:03 PM, Sajith Ravindra  wrote:
>
>> Congratulations :)
>>
>>
>> On Mon, Dec 16, 2013 at 2:24 PM, Thayalan  wrote:
>>
>>> Congratulations Shani!!
>>>
>>>
>>> On Mon, Dec 16, 2013 at 2:11 PM, Bhathiya Jayasekara 
>>> wrote:
>>>
 Congratulations Shani... :)


 On Mon, Dec 16, 2013 at 1:52 PM, Nuwan Silva  wrote:

> Congrats Shani!!!
>
>
> On Mon, Dec 16, 2013 at 1:50 PM, Ruwan Yatawara wrote:
>
>> Congrats Shani!
>>
>> Thanks and Regards,
>>
>> Ruwan Yatawara
>>
>> Software Engineer,
>> WSO2 Inc.
>>  lean . enterprise . middleware
>>
>> email : ruw...@wso2.com
>> mobile : +94 77 9110413
>> blog : http://ruwansrants.blogspot.com/
>> www: :http://wso2.com
>>
>>
>>
>> On Mon, Dec 16, 2013 at 1:42 PM, Harsha Thirimanna 
>> wrote:
>>
>>> Congratulations...
>>>
>>>
>>> *Harsha Thirimanna*
>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>> * *
>>> * email: **hars...@wso2.com* * cell: +94 71 5186770*
>>> * twitter: **http://twitter.com/ *
>>> *harshathirimann linked-in: **http:
>>> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>> *
>>>
>>>  *Lean . Enterprise . Middleware*
>>>
>>>
>>>
>>> On Mon, Dec 16, 2013 at 1:41 PM, Nirmal Fernando wrote:
>>>
 Congratulations Shani !


 On Monday, December 16, 2013, Dhanuka Ranasinghe wrote:

> Hi,
>
> Congrats Shani, and keep up the good work !!
>
> Cheers,
> Dhanuka
>
> *Dhanuka Ranasinghe*
>
> Senior Software Engineer
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 715381915
>
>
> On Mon, Dec 16, 2013 at 10:55 AM, Prabath Abeysekera <
> praba...@wso2.com> wrote:
>
>> Hi All,
>>
>> It's my pleasure to welcome Shani Ranasinghe as a WSO2 Committer.
>> Shani has been a key member of the team since she joined SS and has
>> contributed greatly to SS related developments with a great deal of
>> enthusiasm over the last couple of months. In recognition of her
>> contributions, Shani's been voted as a WSO2 comitter.
>>
>> Shani, Welcome aboard and keep up the good work!
>>
>>
>> Cheers,
>> Prabath
>>
>> --
>> Prabath Abeysekara
>> Associate Technical Lead, Data TG.
>> WSO2 Inc.
>> Email: praba...@wso2.com
>> Mobile: +94774171471
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>

 --

 Thanks & regards,
 Nirmal

 Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
>
> *Nuwan Silva*
> *Senior Software Engineer - QA*
> Mobile: +94779804543
>
> WSO2 Inc.
> lean . enterprise . middlewear.
> http://www.wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Bhathiya Jayasekara*
 *Software Engineer,*
 *WSO2 inc., http://wso2.com *

 *Phone: +94715478185 <%2B94715478185>*
 *LinkedIn: http://www.linkedin.com/in/bhathiyaj
 *
 *Twitter: https://twitter.com/bhathiyax *

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Regards,
>>> Thayalan Sivapaleswararajah
>>> Associate Technical Lead - QA
>>> Mob: +94(0)777872485
>>> Tel : +94(0)(11)2145345
>>> 

Re: [Dev] Can we set JMS properties from WSO2 MB GUI when publishing messages to Topics?

[Ishara Premadasa]

Hi Lahiru,

Topic message publishing UI in WSO2 MB currently support text messages and
hence only message body (as xml ) can be set from the UI. If you need to
set JMS  properties this needs to be done using an external JMS client.

Thanks,
Ishara


On Fri, Dec 6, 2013 at 6:01 PM, Lahiru Sandaruwan  wrote:

> Hi,
>
> $subject...
>
> Thanks.
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahi...@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Kernel Commit required to ESBJAVA-2638 in patch0002

[Ishara Premadasa]

Hi,

Please apply patch attached to below Jira [1].

[1] https://wso2.org/jira/browse/ESBJAVA-2638

Thanks,
Ishara

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Python client for WSO2 Message Broker

[Ishara Premadasa]

Hi Dinesh,

That is great :)

We hope to improve MB client samples stack to provide ability to connect
with WSO2 MB using various clients for MB 2.2.0 or 3.0.0 release.
Therefore can you please add these client samples to somewhere as we can
use it there too.

Thanks,
Ishara



On Wed, Oct 9, 2013 at 12:41 PM, Dinesh Bandara  wrote:

> Hi Ishara,
>
> Declare an exclusive subscriber will solve the issue.
> chan.basic_consume(queue='chatroom', no_ack=True, *exclusive=True*)
>
> Thanks for your great help.
>
> Regards,
> DineshB
>
>
>
> On Wed, Oct 9, 2013 at 11:10 AM, Ishara Premadasa  wrote:
>
>> Hi Dinesh,
>>
>> Do you see any error log there when running the subscriber ?  Also can
>> you see any terminal logs saying that 'Subscriber binded successfully with
>> ID_XX ' etc.  ? If possible please add the MB log here after running the
>> sample clients.
>>
>> Thanks,
>> Ishara
>>
>>
>> On Wed, Oct 9, 2013 at 11:00 AM, Dinesh Bandara  wrote:
>>
>>> Hi,
>>>
>>> I have tried to implement a python client for WSO2 MB by using the [1]
>>> which supports for RabbitMQ as well as Qpid. When use it with WSO2MB,
>>> publisher can publish into topic but subscriber could not be able to
>>> consume messages from the topic.
>>> Can anyone help me to figure this out?
>>>
>>> [1] https://launchpad.net/txamqp
>>>
>>> --
>>> *Dinesh Bandara*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> Twitter   :  https://twitter.com/ishadil
>> Mobile   : +94 714445832*
>>
>>
>>
>
>
> --
> *Dinesh Bandara*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Python client for WSO2 Message Broker

[Ishara Premadasa]

Hi Dinesh,

Do you see any error log there when running the subscriber ?  Also can you
see any terminal logs saying that 'Subscriber binded successfully with
ID_XX ' etc.  ? If possible please add the MB log here after running the
sample clients.

Thanks,
Ishara


On Wed, Oct 9, 2013 at 11:00 AM, Dinesh Bandara  wrote:

> Hi,
>
> I have tried to implement a python client for WSO2 MB by using the [1]
> which supports for RabbitMQ as well as Qpid. When use it with WSO2MB,
> publisher can publish into topic but subscriber could not be able to
> consume messages from the topic.
> Can anyone help me to figure this out?
>
> [1] https://launchpad.net/txamqp
>
> --
> *Dinesh Bandara*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Architecture] WSO2 Message Broker 2.1.1 - Alpha Released!

[Ishara Premadasa]

*WSO2 Message Broker 2.1.1- Alpha Released!*

WSO2 MB team is pleased to announce the 2.1.1- Alpha release of the WSO2
Message Broker.

WSO2 Message Broker 2.1.1, JMS message broker backed up with the wso2
distributed message brokering engine "Andes" is compliant with AMQP 0-91
version. The new alpha version which comes out as the successor of Message
broker 2.1.0, mainly contains LMAX Disruptor based performance
improvements, message counter improvements and several bug fixes and
improvements.

You can download this distribution from
http://dist.wso2.org/downloads/message-broker/2.1.1/alpha/wso2mb-2.1.1.zip


How to Run,

   1. Extract the downloaded zip
   2. Go to the bin directory in the extracted folder
   3. Run the wso2server.sh or wso2server.bat as appropriate
   4. Point your browser to the URL https://localhost:9443/carbon
   5. Use "admin", "admin" as the username and password to login as an
admin and create a user account
   6. Use the documentation to get to know on how to creating clients,
using clients and deployment guide to do clustering.

Your feedbacks are most welcome. Please report issues at [1] and specify
the affect version as MB 2.1.1.

-- WSO2 MB Team --

[1] https://wso2.org/jira/browse/MB

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Refactoring CarbonContext.getCurrentContext()

[Ishara Premadasa]

Adding Shammi into this thread since he is working on MB components.

Thanks!


On Mon, Sep 30, 2013 at 4:41 PM, Dhanuka Ranasinghe wrote:

> Hi,
>
> Please find the patch for cassandra components, I tried to commit but it
> seems I don't have been blocked.
>
> Cheers,
> Dhanuka
>
> *Dhanuka Ranasinghe*
>
> Senior Software Engineer
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 715381915
>
>
> On Mon, Sep 30, 2013 at 3:47 PM, Prabath Abeysekera wrote:
>
>> Hi Shani,
>>
>> Please do a smoke test on HDFS related functionalities and report if
>> there's any issue.
>>
>>
>> Cheers,
>> Prabath
>>
>>
>> On Thu, Sep 26, 2013 at 3:39 PM, Sumedha Rubasinghe wrote:
>>
>>> Folks in 'To' list,
>>> You guys will be working with Sameera on $subject from tomorrow for 4
>>> days.
>>> Sameera will provide more context, formulate a plan & inform.
>>>
>>> Please use a **single thread** to communicate all related issues with
>>> regard for future references.
>>>
>>>
>>>
>>> --
>>> /sumedha
>>> b :  bit.ly/sumedha
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Prabath Abeysekara
>> Associate Technical Lead, Data TG.
>> WSO2 Inc.
>> Email: praba...@wso2.com
>> Mobile: +94774171471
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += RajeevS

[Ishara Premadasa]

Congratulations Rajeev ...


On Tue, Sep 17, 2013 at 1:50 PM, Bhathiya Jayasekara wrote:

> Congratulations...
>
>
> On Tue, Sep 17, 2013 at 1:38 PM, Manula Chathurika Thantriwatte <
> manu...@wso2.com> wrote:
>
>> Congratulations Rajeev !!!
>>
>>
>> On Tue, Sep 17, 2013 at 1:23 PM, Pulasthi Supun wrote:
>>
>>> Congrats Rajeev !!!
>>>
>>>
>>> On Tue, Sep 17, 2013 at 11:12 AM, Mohanadarshan Vivekanandalingam <
>>> mo...@wso2.com> wrote:
>>>
 Congrats Rajeev !!!...

 Regards,
 Mohan


 On Tue, Sep 17, 2013 at 12:05 AM, Lasantha Fernando 
 wrote:

> Congrats Rajeev!... :-)
>
>
> On 16 September 2013 23:40, Sriskandarajah Suhothayan 
> wrote:
>
>> Hi All,
>>
>> It's my pleasure to welcome Rajeev Sampath as a WSO2 Committer.
>> RajeevS  has been a  contributor to CEP over the last six months
>> contributing greatly to both CEP and Siddhi. In acknowledgement of all 
>> his
>> contributions, he's been voted as a WSO2 committer.
>>
>> RajeevS, Keep up the good work!
>>
>> Cheers,
>> Suho
>>
>> --
>> *S. Suhothayan
>> *
>> Associate Technical Lead,
>>  *WSO2 Inc. *http://wso2.com *
>>  *
>> lean . enterprise . middleware
>>
>> *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
>> twitter: http://twitter.com/suhothayan | linked-in:
>> http://lk.linkedin.com/in/suhothayan*
>> *
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Lasantha Fernando*
> Software Engineer - Data Technologies Team
> WSO2 Inc. http://wso2.com
>
> email: lasan...@wso2.com
> mobile: (+94) 71 5247551
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *V. Mohanadarshan*
 *Software Engineer,*
 *Data Technologies Team,*
 *WSO2, Inc. http://wso2.com *
 *lean.enterprise.middleware.*
 *
 *
 email: mo...@wso2.com
 phone:(+94) 771117673

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> --
>>> Pulasthi Supun
>>> Software Engineer; WSO2 Inc.; http://wso2.com,
>>> Email: pulas...@wso2.com
>>> Mobile: +94 (71) 9258281
>>> Blog : http://pulasthisupun.blogspot.com/
>>> Git hub profile: https://github.com/pulasthi
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>> Manula Chathurika Thantriwatte
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>> lean . enterprise . middleware
>>
>> email : manu...@wso2.com / man...@apache.org
>> phone : +94 772492511
>> blog : http://manulachathurika.blogspot.com/
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Bhathiya Jayasekara*
> *Software Engineer,*
> *WSO2 inc., http://wso2.com*
> *
> *
> *Phone: +94715478185*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj*
> *Twitter: https://twitter.com/bhathiyax*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MB Log message {Binding Subscription x to queue JMSMS}

[Ishara Premadasa]

Hi Dushan/Chanaka,

The log message is added after creating a new subscription as below and it
is not just increasing a number.

Subscription subscription =

SubscriptionFactoryImpl.INSTANCE.createSubscription(_channelId, _session,
tag, acks, filters, noLocal, _creditManager);
return new SubscriptionImpl.AckSubscription(channel, protocolSession,
consumerTag,  filters, noLocal, creditManager, clientMethod, recordMethod);


What is the ESB version you are observing this and is this whole log is
seen at the server start up? If this is with ESB 4.8 MS/MP implementation,
I also tried and noticed a similar scenario where i have a MP named
RequestProcessor which listens on queue, request_queue, which is bound to
MS, RequestStore. If i add only a new MesageStore (say ResponseStore) i can
see the following log.

[2013-09-17 13:49:37,902]  INFO
{org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
-  Removing Subscription 2 from queue request_queue
[2013-09-17 13:49:38,639]  INFO
{org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
-  Binding Subscription 3 to queue request_queue

The again i edited a name of a proxy  service in my ESB pack and saved the
configuration back, and again there were two similar logs for removing and
binding existing MB subscription. Therefore i think MS/MP implementation is
written to create a new Subscription every time when synapse configuration
is changed?

On Tue, Sep 17, 2013 at 12:12 PM, Chanaka Fernando wrote:

> Hi Dushan,
>
> As per my understanding, this message is printed since the MB is creating
> a temporary subscription to the queue to create the queue dynamically (It
> will remove the subscription instantly). This happens at the startup to
> create the queue in MB side dynamically.
>

When adding the queue dynamically, it is true that a new subscription is
created. However in that case subscription is created and closed a single
time and it happens within few seconds. but when seen the logs it seems
removing of subscription  has happened after around 1 minute. Therefore i
feel this is not what has happened here.

Thanks!
Ishara

>
> +1 for the suggestion that we need to either remove the log or print a
> proper log message like "Creating the Queue JMSMS in the Message Broker"
>
>
> On Tue, Sep 17, 2013 at 11:51 AM, Dushan Abeyruwan wrote:
>
>> Hi
>>   Once MSMP configured, and  every time ESB starts,from MB side we can
>> see following logs [1], it seems like creating new subscription. as how the
>> * log message depicted*, but Isuruu pointed that it does not create any
>> new subscription, yet it will increase some number.
>>   Anyway the logs interprets a wrong message to the end users, so we need
>> to get rid of this or need a better message ..rather confusing ppl who uses
>> MB..
>>
>> [1]
>> [2013-09-17 11:32:23,104]  INFO
>> {org.wso2.andes.server.cassandra.QueueDeliveryWorker} -  Queue worker
>> started for queue: JMSMS with on flight message checks
>> [2013-09-17 11:32:23,140]  INFO
>> {org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
>> -  Binding Subscription 0 to queue JMSMS
>> [2013-09-17 11:34:55,843]  INFO
>> {org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
>> -  Removing Subscription 0 from queue JMSMS
>> [2013-09-17 11:40:05,774]  INFO
>> {org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
>> - * Binding Subscription 1 to queue JMSMS*
>> [2013-09-17 11:41:39,641]  INFO
>> {org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
>> -  Removing Subscription 1 from queue JMSMS
>> [2013-09-17 11:42:00,297]  INFO
>> {org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
>> - * Binding Subscription 2 to queue JMSMS*
>>
>> cheers,
>> Dushan Abeyruwan
>> Associate Tech Lead
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com/*
>> *Mobile:(+94)714408632*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> Chanaka Fernando
> Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
> Wordpress:http://chanakaudaya.wordpress.com
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need urgent help to disable features WSO2 ESB 4.0.3?

[Ishara Premadasa]

Hi Diwan,

On Sat, Sep 14, 2013 at 7:47 AM, Nirmal Fernando  wrote:

> Hi Diwan,
>
> Please see the answers for some of the questions.
>
>
> On Sat, Sep 14, 2013 at 6:28 AM, Abhijit Diwan  wrote:
>
>> Any Help on this. It is big company and if they do not find it secure we
>> have to drop the implementation.
>>
>> Please help.
>> thanks
>> Abhijit
>> On Sep 12, 2013, at 3:39 PM, Abhijit Diwan wrote:
>>
>> > Hi All
>> >
>> >   We are in final few steps of WSO2 ESB / Data services
>> implementation at very big company. They love your Data Services, I mean it
>> , love it !!
>> >
>> >   We are trying to pass the Information Security review of our WSO2
>> ESB implementation. We are using 4.0.3 EAB with 3.2.2 DSS feature.
>> >
>> >   Information security group has objected for following things in
>> default WSO2 ESB
>> >
>> >   1. QPID / AMQP server listening to 5672 / 8672 ports. Can
>> we disable the default message broker so that QPID will not start. If we
>> disable, will it affect any other functionality? We are
>> NOT using message brokers / any JMS related applications, mainly Data
>> Services.
>>
>
You can disable QPID server listening on 8672 TLS port with the following
configuration change.
Go to /repository/conf/advanced/qpid-config.xml file and change
the  entry as below.





*false*
false

repository/resources/security/wso2carbon.jks
wso2carbon


After that QPID Broker will not be starting on TLS port. However regarding
disabling the Qpid Server in 5672 TCP port, ESB 4.0.3 version comes with an
embedded QPID broker which is tightly coupled with other ESB components.
Therefore unfortunately it is not possible to detach the broker from the
ESB with a configuration setting. We have changed this after ESB 4.5.x
versions where the embedded Qpid broker is no longer shipped with ESB,
therefore if it is possible, you can upgrade the ESB version in order to
meet this requirement.

Thanks,
Ishara



> >
>> >   2. How to block JMX console being started? The JMX
>> console starts at 1 /  be default.
>>
>
> In {CARBON-HOME}/repository/conf/advanced/jmx.xml file, you can disable
> jmx console.
>
> false
>
>> >
>> >   3. We have already disabled Admin UI, however is there
>> any way where I can turn the logging levels for individual loggers with out
>> Admin UI and WITHOUT re-starting the ESB?
>>
>
> I'm afraid not (AFAIK). The only other way is by editing
> {CARBON-HOME}/repository/conf/log4j.properties file, which needs a restart
> of the server.
>
>  >
>> >   I would be extremely thankful if I can answers for above
>> questions.
>> >
>> >   Please help WSO2 implementation in very prestigious company.
>> >
>> >   WSO2 rocks !!!
>> >
>> > thanks
>> > Abhijit
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fixing Message Counters and Queue Purging features for MB 2.1.1 after disruptor implementation

[Ishara Premadasa]

Hi Malinga,

On Fri, Aug 30, 2013 at 2:42 PM, Malinga Purnasiri wrote:

> hi Ishara,
>
> As i remember since per message count increment to DB kill the performance
> of MB considerably; we all thought of removing it for the moment. With the
> new disruptor changes we thought of updating queue count periodically (not
> in real-time). So i think its not good idea to depend on the queue count
> for the purging operation. instead ..
>
> What if we use [1] receive(timeout). We can set the timeout to (may be) 5
> secs.
>
> Any ideas ?
>

I used [1] as suggested with a timeout of 30 secs and got queue purging
works fine. IIRC before introducing the disruptor we were unable to use
receive(timeout) method from API due to the latency of retrieving messages
from Queue, however the process has good speed now.

With new fix when purge is clicked it will empty the Queue in blocking
manner while a loading message is displayed and will return back after
purging is done. Fixed and committed in r184738.

Thanks!
Ishara


>
> [1]
> http://docs.oracle.com/javaee/1.4/api/javax/jms/MessageConsumer.html#receive(long)
>
>
>
>
> On Wed, Aug 28, 2013 at 2:01 PM, Ishara Premadasa  wrote:
>
>> Hi,
>>
>> Since we have removed the message counters after introducing the
>> disruptor based message processing  for MB 2.1.1  both the above features
>> are currently not working and we are trying to fix this. As the previous
>> MessageWriter,  implementations from 2.1.0 are no longer used, now we don't
>> keep message counts stored in Cassandra so the counters are always shown as
>> zero. Due to this the current queue purge feature has too broken since it
>> periodically checks the message counter and performs purge operation
>> continuously till the total message count in the queue is zero.
>>
>> IMO we need to find an alternative way to get message counters work in
>> the queue as the message writers are not used now. If not we may need to
>> remove these two features from UI, since purging too depending on the
>> counters.
>>
>> Thanks!
>> Ishara
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> Twitter   :  https://twitter.com/ishadil
>> Mobile   : +94 714445832*
>>
>>
>>
>
>
> --
> Malinga Pathmal,
> Technical Lead, WSO2, Inc. : http://wso2.com/
> Phone : (+94) 715335898
>



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Ayashkantha

[Ishara Premadasa]

Congratulations. :)


On Thu, Sep 5, 2013 at 2:56 PM, Shameera Rathnayaka wrote:

> Congratzzz Ayashkantha !!!
>
>
> On Thu, Sep 5, 2013 at 2:41 PM, Pulasthi Supun  wrote:
>
>> Congrats Ayashkantha
>>
>>
>> On Thu, Sep 5, 2013 at 2:38 PM, Manula Chathurika Thantriwatte <
>> manu...@wso2.com> wrote:
>>
>>> Congratulations !!!
>>>
>>>
>>> On Thu, Sep 5, 2013 at 2:36 PM, Dhanuka Ranasinghe wrote:
>>>
 Congratz... 

 *Dhanuka Ranasinghe*

 Senior Software Engineer
 WSO2 Inc. ; http://wso2.com

 lean . enterprise . middleware

 phone : +94 715381915


 On Thu, Sep 5, 2013 at 2:27 PM, Darshana Gunawardana >>> > wrote:

> Congratulations...!!!
>
>
> On Thu, Sep 5, 2013 at 2:25 PM, Dunith Dhanushka wrote:
>
>> Congrats Ayashkantha!
>>
>>
>> On Thu, Sep 5, 2013 at 2:13 PM, Anjana Fernando wrote:
>>
>>> Hi everyone,
>>>
>>> It's my pleasure to announce Ayashkantha as a WSO2 commiter.
>>> Ayashkantha has done many contributions to the BAM product, and I'm 
>>> sure he
>>> will continue to be a valuable member to the team. Ayashkantha, welcome
>>> aboard and keep up the good work! ..
>>>
>>>
>>> Cheers,
>>> Anjana.
>>>
>>> --
>>> *Anjana Fernando*
>>> Technical Lead
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> Dunith Dhanushka,
>> Senior Software Engineer - BAM,
>> WSO2 Inc,
>>
>> Mobile - +94 71 8615744
>> Blog - dunithd.wordpress.com 
>> Twitter - @dunithd 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
> *
> Darshana Gunawardana
> *Software Engineer
> WSO2 Inc.; http://wso2.com*
> E-mail: darsh...@wso2.com
> **Mobile: +94718566859
> *Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Regards,
>>> Manula Chathurika Thantriwatte
>>> Software Engineer
>>> WSO2 Inc. : http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> email : manu...@wso2.com / man...@apache.org
>>> phone : +94 772492511
>>> blog : http://manulachathurika.blogspot.com/
>>>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> --
>> Pulasthi Supun
>> Software Engineer; WSO2 Inc.; http://wso2.com,
>> Email: pulas...@wso2.com
>> Mobile: +94 (71) 9258281
>> Blog : http://pulasthisupun.blogspot.com/
>> Git hub profile: https://github.com/pulasthi
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Software Engineer - WSO2 Inc.*
> *email: shameera AT wso2.com  , shameera AT 
> apache.org
> *
> *phone:  +9471 922 1454*
> *
> *
> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
> *Twitter : *https://twitter.com/Shameera_R
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Gokul

[Ishara Premadasa]

Congratulations Gokul :)


On Thu, Aug 29, 2013 at 11:58 AM, Susinda Perera  wrote:

> Congratulations Gokul.
>
>
> On Thu, Aug 29, 2013 at 11:36 AM, Asanka Sanjeewa wrote:
>
>> Congratulations Gokul.
>>
>> Regards,
>> AsankaS.
>>
>>
>> On Thu, Aug 29, 2013 at 11:19 AM, Pulasthi Supun wrote:
>>
>>> Congratz Goku(l)!! :)
>>>
>>>
>>> On Thu, Aug 29, 2013 at 11:11 AM, Shameera Rathnayaka >> > wrote:
>>>
 Congratulation Gokul !!!


 On Wed, Aug 28, 2013 at 9:01 PM, Mohanadarshan Vivekanandalingam <
 mo...@wso2.com> wrote:

> Congrats Gokul !!!
>
>
> Regards,
> Mohan
>
>
> On Wed, Aug 28, 2013 at 6:11 PM, Manoj Kumara  wrote:
>
>> Congratulations Gokul ...
>>
>> Best Regards..
>>
>>
>> Manoj Kumara
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Twitter:  http://twitter.com/ManKuma
>> Mobile: +94713448188
>>
>>
>> On Wed, Aug 28, 2013 at 6:07 PM, Manula Chathurika Thantriwatte <
>> manu...@wso2.com> wrote:
>>
>>> Congratulations Gokul !!!
>>>
>>>
>>> On Wed, Aug 28, 2013 at 5:57 PM, Chanaka Fernando >> > wrote:
>>>
 Congrats Gokul 



 On Wed, Aug 28, 2013 at 5:30 PM, Maninda Edirisooriya <
 mani...@wso2.com> wrote:

> Congratulations Gokul. :-)
>
> *
> Maninda Edirisooriya*
> Software Engineer
> *WSO2, Inc.
> *lean.enterprise.middleware.
>
> *Blog* : http://maninda.blogspot.com/
> *Phone* : +94 777603226
>
>
> On Wed, Aug 28, 2013 at 5:15 PM, Bhathiya Jayasekara <
> bhath...@wso2.com> wrote:
>
>> Congratulations Gokul...
>>
>>
>> On Wed, Aug 28, 2013 at 5:07 PM, Darshana Gunawardana <
>> darsh...@wso2.com> wrote:
>>
>>> Congratulations Gokul...!!!
>>>
>>>
>>>  On Wed, Aug 28, 2013 at 4:59 PM, Anjana Fernando <
>>> anj...@wso2.com> wrote:
>>>
 Hi everyone,

 It's my pleasure to announce Gokul as a WSO2 commiter. Gokul
 has done many contributions in improving the BAM product. And I'm 
 sure he
 will continue to be a key member in the team. Gokul, welcome 
 aboard and
 keep it up! ..


 Cheers,
 Anjana.

 --
 *Anjana Fernando*
 Technical Lead
 WSO2 Inc. | http://wso2.com
 lean . enterprise . middleware

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Regards,
>>>
>>> *
>>> Darshana Gunawardana
>>> *Software Engineer
>>> WSO2 Inc.; http://wso2.com*
>>> E-mail: darsh...@wso2.com
>>> **Mobile: +94718566859
>>> *Lean . Enterprise . Middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Software Engineer,*
>> *WSO2 inc., http://wso2.com*
>> *
>> *
>> *Phone: +94715478185*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj*
>> *Twitter: https://twitter.com/bhathiyax*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 --
 Chanaka Fernando
 Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya
 Wordpress:http://chanakaudaya.wordpress.com




 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Regards,
>>> Manula Chathurika Thantriwatte
>>> Software Engineer
>>> WSO2 Inc. : http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> email : manu...@wso2

[Dev] Fixing Message Counters and Queue Purging features for MB 2.1.1 after disruptor implementation

[Ishara Premadasa]

Hi,

Since we have removed the message counters after introducing the disruptor
based message processing  for MB 2.1.1  both the above features are
currently not working and we are trying to fix this. As the previous
MessageWriter,  implementations from 2.1.0 are no longer used, now we don't
keep message counts stored in Cassandra so the counters are always shown as
zero. Due to this the current queue purge feature has too broken since it
periodically checks the message counter and performs purge operation
continuously till the total message count in the queue is zero.

IMO we need to find an alternative way to get message counters work in the
queue as the message writers are not used now. If not we may need to remove
these two features from UI, since purging too depending on the counters.

Thanks!
Ishara

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Welcome Lasantha Fernando as a WSO2 Committer

[Ishara Premadasa]

Congratulations... :)


On Mon, Aug 26, 2013 at 4:27 PM, Pushpalanka Jayawardhana wrote:

> Congratulations...!!!
>
> Pushpalanka Jayawardhana
>
> Software Engineer
>
> WSO2 Lanka (pvt) Ltd
> [image: 
> Facebook]
>  [image:
> Twitter]
>  [image:
> LinkedIn]
>  [image:
> Blogger]
>  [image:
> SlideShare]
> Mobile: +94779716248
>
> 
>
>
>
> On Mon, Aug 26, 2013 at 4:14 PM, Sriskandarajah Suhothayan 
> wrote:
>
>> Hi All,
>>
>> It is my pleasure to welcome Lasantha Fernando as a WSO2 Committer.
>>
>> Lasantha joined CEP team and have contributed a lot to CEP product, He
>> has also worked on Siddhi adding several improvements successfully.
>>
>> In recognition of his commitment and contributions, he has been voted as
>> a Committer for WSO2.
>>
>> Lasantha, Congratulations and Welcome Aboard! Keep up the good work!!
>>
>> Regards,
>> Suho
>>
>> --
>> *S. Suhothayan
>> *
>> Associate Technical Lead,
>>  *WSO2 Inc. *http://wso2.com *
>>  *
>> lean . enterprise . middleware
>>
>> *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
>> twitter: http://twitter.com/suhothayan | linked-in:
>> http://lk.linkedin.com/in/suhothayan*
>> *
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Welcome Rajeeva Uthayasangar as a WSO2 Committer

[Ishara Premadasa]

Congratulations Rajeeva :)


On Mon, Aug 26, 2013 at 8:38 AM, Chanaka Fernando  wrote:

> Congratulations Rajeeva !!!
>
>
> On Mon, Aug 26, 2013 at 4:30 AM, Nuwan Bandara  wrote:
>
>> Congratulations Rajeeva. Thanks for the hard work put in for building
>> jaggery tools. Hope you will continue to do so and make the IDE plugin
>> perfect :).
>>
>> Regards,
>> /nuwan
>>
>>
>> On Mon, Aug 26, 2013 at 2:00 AM, Harshana Martin wrote:
>>
>>> Hi All,
>>>
>>> It is our pleasure to welcome Rajeeva Uthayasangar as a WSO2 Committer.
>>>
>>> Rajeeva joined WSO2 Jaggery team and worked on implementing Jaggery
>>> Editor for WSO2 Developer Studio which is now distributed as a part of WSO2
>>> Developer Studio. Also she contributed to some of the important internal
>>> projects and completed them successfully.
>>>
>>> In recognition of her commitment and contributions, she has been voted
>>> as a Committer for WSO2.
>>>
>>> Rajeeva, Congratulations and Welcome Aboard! Keep up the good work!!
>>>
>>> Thanks and Regards,
>>> Nuwan & Harshana
>>> --
>>>
>>> Harshana Martin
>>> Associate Technical Lead
>>> WSO2 Inc. : http://wso2.com
>>>
>>> Mobile: +94 775 998 115
>>> Profile: https://www.google.com/profiles/harshana05
>>> Blog: http://harshana05.blogspot.com
>>> Twitter: http://twitter.com/harshana05
>>>
>>
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Technical Lead; **WSO2 Inc. *
>> *lean . enterprise . middleware |  http://wso2.com *
>> *blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
>> 9629
>> *
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> Chanaka Fernando
> Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http:// soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
> Wordpress:http://chanakaudaya.wordpress.com
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] AS not patched for the continuous JMS connection retry issue?

[Ishara Premadasa]

On Mon, Aug 19, 2013 at 11:29 PM, Kasun Gajasinghe  wrote:

>
>
>> However the only incident i have seen a rapid error log thrown
>> continuosly in the MB or ActiveMQ integration scenario is, when you start
>> AS for the first time, if you hadn't start the broker (MB/ActiveMQ etc.)
>> before starting AS it will throw a continuous error log as there is no
>> JMSConnection available. Apart from that if the broker fails in middle,
>> after successful start up, the reconnection should happen fine.
>>
>>
>>
> Yes... This is what I was doing. We should handle this scenario too,
> right?
>

@Shammi/Malinga

WDYT? Should we provide some notification and stop the server start if user
forgets to start JMS provider (broker) in prior to start AS, ESB etc.? IMO
as our documentation clearly says that it is needed to start the broker
first in  each integrating scenarios,  i am not sure whether it is needed
to handle this.


>
>>
>>
>> On Mon, Aug 19, 2013 at 4:44 PM, Kasun Gajasinghe wrote:
>>
>>> Hi Ishara,
>>>
>>> Please note that I tried this with ActiveMQ. I didn't see the
>>> reconnection attempts in the log rather a rapid generation of logs. The log
>>> file grew to 100MB in less than a minute.
>>>
>>>
>>> On Mon, Aug 19, 2013 at 4:21 PM, Ishara Premadasa wrote:
>>>
>>>> Hi Kasun,
>>>>
>>>> I first tried the JMS transport reconnection mechanism with AS 5.1.0
>>>> and then i tried with the newly built AS 5.2.0 pack. However with both
>>>> these packs the reconnection works fine where it waits for the
>>>> JMSConnection to come alive by retrying in exponentially increasing time
>>>> intervals. Please see the AS console log i get in the this situation below.
>>>>
>>>> [2013-08-19 15:28:02,454]  INFO {org.wso2.andes.client.AMQConnection}
>>>> -  Unable to connect to broker at tcp://localhost:5673
>>>> org.wso2.andes.transport.TransportException: Could not open connection
>>>> at
>>>> org.wso2.andes.transport.network.mina.MinaNetworkTransport$IoConnectorCreator.connect(MinaNetworkTransport.java:201)
>>>> at
>>>> org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(MinaNetworkTransport.java:71)
>>>> at
>>>> org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:110)
>>>> at
>>>> org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:616)
>>>> at
>>>> org.wso2.andes.client.AMQConnection.(AMQConnection.java:398)
>>>> at
>>>> org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:315)
>>>> at
>>>> org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:38)
>>>>
>>>> at
>>>> org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:629)
>>>> at
>>>> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:824)
>>>>  at
>>>> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getConnection(ServiceTaskManager.java:706)
>>>> at
>>>> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:496)
>>>> at
>>>> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:420)
>>>> at
>>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>> at java.lang.Thread.run(Thread.java:662)
>>>> [2013-08-19 15:28:02,454] ERROR
>>>> {org.apache.axis2.transport.jms.ServiceTaskManager} -  Error acquiring a
>>>> JMS connection to : QueueConnectionFactory using JNDI properties :
>>>> {java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory,
>>>> java.naming.provider.url=repository/conf/jndi.properties,
>>>> transport.jms.ConnectionFactoryType=queue,
>>>> ServiceClass=org.wso2.carbon.mashup.javascript.stubgenerator.JSStubGenerator
>>>> }
>>>> javax.jms.JMSException: Error creating connection: Could not open
&g

Re: [Dev] AS not patched for the continuous JMS connection retry issue?

[Ishara Premadasa]

SocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
>  at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
>  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> at java.net.Socket.connect(Socket.java:529)
>  at
> org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:435)
> at
> org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:401)
>  at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:53)
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:57)
>  at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:57)
> at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
>  at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:57)
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:57)
>  at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:260)
> ... 11 more
>
>
>
> On Mon, Aug 19, 2013 at 5:38 AM, Ishara Premadasa  wrote:
>
>> Hi Kasun,
>>
>> We will be looking into this today and update.
>> Thanks!
>>
>>
>> On Sun, Aug 18, 2013 at 12:14 PM, Kasun Gajasinghe wrote:
>>
>>> Hi,
>>>
>>> It seems that AS 5.2.0 is not patched with the issue with JMS transport
>>> where the services with JMS enabled repeatedly try to  establish a
>>> connection with the message broker. This results in GBs of logs in a matter
>>> of minutes filling up the disk.
>>>
>>> As I got to know from Shammi, the solution is to exponentially increase
>>> the waiting time for the connection. Something like, trying in 1sec, 2sec,
>>> 4sec, 8, 16, 32 etc. This fix is already impelemented but it seems that it
>>> didn't get in to AS packs that is about to be released. I tried a setup
>>> with ActiveMQ, and I can see that it tries to establish a connection with
>>> the broker every second or so.
>>>
>>> Can the MB team look in to this ASAP please? Carbon 4.2.0 is due on
>>> coming Thursday.
>>>
>>> Thanks,
>>> KasunG
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> Development Technologies Team, WSO2 Inc.; http://wso2.com
>>>
>>>
>>>  ,
>>> *email: **kasung AT spamfree wso2.com
>>>
>>>
>>> ** cell: **+94 (77) 678-0813*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>>
>>>
>>> *
>>> *
>>> *blog: **http://kasunbg.org* <http://kasunbg.org>
>>>
>>>
>>> *
>>> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>
>>>
>>>
>>> *
>>> *
>>>
>>
>>
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> Twitter   :  https://twitter.com/ishadil
>> Mobile   : +94 714445832*
>>
>>
>>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> Development Technologies Team, WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: **kasung AT spamfree wso2.com
>
>
> ** cell: **+94 (77) 678-0813*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
> *
> *
> *blog: **http://kasunbg.org* <http://kasunbg.org>
>
>
> *
> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>
>
>
> *
> *
>



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Chanaka Fernando

[Ishara Premadasa]

Congratz Chanaka :)


On Mon, Aug 19, 2013 at 11:49 AM, Susinda Perera  wrote:

> Congratz Chanaka!!!
>
>
>
> On Mon, Aug 19, 2013 at 11:44 AM, Rajeev Sampath  wrote:
>
>> Congrats!!
>>
>>
>> On Mon, Aug 19, 2013 at 10:50 AM, Kasun Indrasiri  wrote:
>>
>>> Hi all,
>>>
>>> Its my pleasure to welcome Chanaka Fernando as a WSO2 Committer.
>>>  ChanakaF has been contributing to ESB for last couple of months and has
>>> done an excellent job in recent cloud connector work.
>>>
>>> Chanaka, welcome aboard and keep up the good work.
>>>
>>> Thanks.
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 71 536 4128
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rajeev Sampath
>> Senior Software Engineer
>> WSO2, Inc.; http://www.wso2.com.
>>
>> Mobile:* +94716265766
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Susinda Perera*
> Software Engineer
> Mobile:(+94)716049075
>
> WSO2 Inc. http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] AS not patched for the continuous JMS connection retry issue?

[Ishara Premadasa]

Hi Kasun,

We will be looking into this today and update.
Thanks!


On Sun, Aug 18, 2013 at 12:14 PM, Kasun Gajasinghe  wrote:

> Hi,
>
> It seems that AS 5.2.0 is not patched with the issue with JMS transport
> where the services with JMS enabled repeatedly try to  establish a
> connection with the message broker. This results in GBs of logs in a matter
> of minutes filling up the disk.
>
> As I got to know from Shammi, the solution is to exponentially increase
> the waiting time for the connection. Something like, trying in 1sec, 2sec,
> 4sec, 8, 16, 32 etc. This fix is already impelemented but it seems that it
> didn't get in to AS packs that is about to be released. I tried a setup
> with ActiveMQ, and I can see that it tries to establish a connection with
> the broker every second or so.
>
> Can the MB team look in to this ASAP please? Carbon 4.2.0 is due on coming
> Thursday.
>
> Thanks,
> KasunG
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> Development Technologies Team, WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: **kasung AT spamfree wso2.com
>
>
> ** cell: **+94 (77) 678-0813*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
> *
> *
> *blog: **http://kasunbg.org* 
>
>
> *
> twitter: **http://twitter.com/kasunbg* 
>
>
> *
> *
>



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Tanya Madurapperuma

[Ishara Premadasa]

Congratulations Tanya!!!


On Fri, Aug 16, 2013 at 10:57 AM, Chanika Geeganage wrote:

> Congratzz Tanya !
>
>
> On Fri, Aug 16, 2013 at 10:53 AM, Pulasthi Supun wrote:
>
>> Congrats tanya :)
>>
>>
>> On Fri, Aug 16, 2013 at 10:11 AM, Nuwan Bandara  wrote:
>>
>>> Hi All,
>>>
>>> Its my pleasure to welcome Tanya to WSO2 developer community by granting
>>> WSO2 commitership. Tanya has been contributing to products such as Jaggery,
>>> UES, Enterprise Store and also was working extensively on internal
>>> engineering application.
>>>
>>> While appreciating her contribution, I wish her all the best and hoping
>>> to see more and more technical contributions to our products and solutions
>>> spaces.
>>>
>>> Welcome & Thank You
>>>
>>> --
>>> *Thanks & Regards,
>>>
>>> Nuwan Bandara
>>> Technical Lead; **WSO2 Inc. *
>>> *lean . enterprise . middleware |  http://wso2.com *
>>> *blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
>>> 9629
>>> *
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> --
>> Pulasthi Supun
>> Software Engineer; WSO2 Inc.; http://wso2.com,
>> Email: pulas...@wso2.com
>> Mobile: +94 (71) 9258281
>> Blog : http://pulasthisupun.blogspot.com/
>> Git hub profile: https://github.com/pulasthi
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Best Regards..
>
> Chanika Geeganage
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Mobile: +94773522586
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Piyum Fernando

[Ishara Premadasa]

Congratulations Piyum!


On Wed, Aug 14, 2013 at 2:53 PM, Praveena Sarathchandra
wrote:

> Congratulations!!!
>
>
> On Wed, Aug 14, 2013 at 2:50 PM, Inosh Goonewardena wrote:
>
>> Congratz piyum
>>
>>
>> On Wed, Aug 14, 2013 at 2:17 PM, Dunith Dhanushka wrote:
>>
>>> Congrats Piyum!
>>>
>>>
>>> On Wed, Aug 14, 2013 at 2:09 PM, Susankha Nirmala wrote:
>>>
 congratz  piyum 


 On Wed, Aug 14, 2013 at 2:05 PM, Pushpalanka Jayawardhana <
 la...@wso2.com> wrote:

> Congratulations...!!!
>
>  Pushpalanka Jayawardhana
>
> Software Engineer
>
> WSO2 Lanka (pvt) Ltd
> [image: 
> Facebook]
>  [image:
> Twitter]
>  [image:
> LinkedIn]
>  [image:
> Blogger]
>  [image:
> SlideShare]
> Mobile: +94779716248
> 
> On Wed, Aug 14, 2013 at 2:02 PM, Pulasthi Supun wrote:
>
>> Congrats Piyum :)
>>
>>
>> On Wed, Aug 14, 2013 at 2:00 PM, Gayan Dhanushka wrote:
>>
>>> Congratzz Piyum...!!!
>>>
>>>
>>> On Wed, Aug 14, 2013 at 1:47 PM, Sumedha Kodithuwakku <
>>> sumed...@wso2.com> wrote:
>>>
 Congratzz Piyum...!!


 On Wed, Aug 14, 2013 at 1:44 PM, Bhathiya Jayasekara <
 bhath...@wso2.com> wrote:

> Congratulations piyum...
>
>
> On Wed, Aug 14, 2013 at 1:42 PM, Asanka Sanjeewa  > wrote:
>
>> Congratulation Piyum.
>>
>> Regards,
>> AsankaS.
>>
>>
>> On Wed, Aug 14, 2013 at 1:40 PM, Asanka Dissanayake <
>> asan...@wso2.com> wrote:
>>
>>> Congratzz piyum!!
>>>
>>>
>>> On Wed, Aug 14, 2013 at 1:32 PM, Sagara Gunathunga <
>>> sag...@wso2.com> wrote:
>>>

 It is my pleasure to welcome Piyum Fernando as a WSO2 Committer.

 Piyum, Welcome Aboard!   please keep up the good work!!

 Thanks !
 --
 Sagara Gunathunga

 Senior Technical Lead; WSO2, Inc.;  http://wso2.com
 V.P Apache Web Services;http://ws.apache.org/
 Linkedin; http://www.linkedin.com/in/ssagara
 Blog ;  http://ssagara.blogspot.com


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>>
>>> *Asanka Dissanayake
>>> Software Engineer*
>>> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
>>> *
>>> email: asan...@wso2.com ,   blog:
>>> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile:
>>> +94 71 8373821*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Asanka Sanjeewa*
>> Senior Software Engineer
>> Mobile: +94772532924
>> WSO2 Inc. http://wso2.com/
>> Blog: http://asanka-tech-blog.blogspot.com/
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Bhathiya Jayasekara*
> *Software Engineer,*
> *WSO2 inc., http://wso2.com*
> *
> *
> *Phone: +94715478185*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj*
> *Twitter: https://twitter.com/bhathiyax*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>




 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>>

Re: [Dev] Once enable a transport its get apply to each and every service deployed on AS

[Ishara Premadasa]

Hi,


On Fri, Aug 9, 2013 at 7:09 PM, Kasun Gajasinghe  wrote:

> hi Asanka,
>
> If you enable a transport globally via axis2.xml, then all services
> inherit that. I thinm this is by design. We can't force the user to
> re-enable needed transports per service after enabling it globally.
>
> You can explicitly set the transports exposed by a service via its
> services.xml. Further, in the case of JMS, I think user have to define a
> jndi property per service to map jndi name to jms queue via
> repo/conf/jndi.properties. If you did not set this property, then the JMS
> transport is effectively disabled for that service. That was the case at
> least in previous releases in both AS and ESB. I believe this is a
> limitation with MB since it does not support dynamic queues.
>

With the previous releases in both AS and ESB, if you do not add queue name
into repo/conf/jndi.properties file, JMS transport will not be disabled for
that service, instead it will try to create a queue for the service/proxy
and throw error 'java.lang.UnsupportedOperationException: The new
addressing based sytanx is not supported for AMQP 0-8/0-9 versions' since
queue is not defined. But for the new releases of both products onwards,
WSO2 MB now supports dynamic queues [1].  Which means you don't need to
manually define the queue names in jndi.properties file and queues will be
created at the server start up for each proxy or service.

As i know you can't selectively enable jms transport for services therefore
for each AS service it will dynamically create a queue named after that
service. I have seen that this is common in other message brokers as well which
provides dynamic queue support.

Thanks!
Ishara

[1]
http://isharapremadasa.blogspot.com/2013/07/providing-dynamic-queue-support-when.html


>
>
> On Friday, August 9, 2013, Asanka Vithanage  wrote:
> > Hi All,
> >
> > When enable the JMS transport on axis2.xml as specified on [1]. All the
> deployed services enable the the JMS transport.so we can see every service
> creating an queue on message broker.
> > IMO this should not happen.
> >
> > Further suppose a situation like AS have 10 services deployed and user
> wants to deploy a new service which needs  listen to an queue. In this kind
> of situation user needs to update all previous services, simply he has to
> go to Tranport management (Home> Manage> Services> List> Service Dashboard>
> Transport Management) page of each and every service and remove JMS
> transport manually.
> >
> > As i see after enabled the JMS transport on global level, user should
> allow to select required transport on each service level. As we do on ESB
> proxy.
> >
> > WDYT?
> >
> > Note:
> > This concern is valid for other Transports as well.
> >
> >
> >
> > [1] http://docs.wso2.org/wiki/display/MB210/Integrating+WSO2+AS
> >
> > --
> > Asanka Vithanage
> > Senior Software Engineer -QA
> > Mobile: +94 0716286708
> > Email: asan...@wso2.com
> > WSO2 Inc. www.wso2.com
> >
> >
>
> --
> ~~--~~
> Sending this mail via my phone. Do excuse any typo or short replies
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failure in Trunk

[Ishara Premadasa]

Commits r180295 and r180262 seems to have changed this class. Is your repo
is been updated today?

Thanks!
Ishara


On Thu, Aug 8, 2013 at 4:21 PM, Shani Ranasinghe  wrote:

> Hi,
> I am facing the following issue.
>
> Any idea how I can resolve this?
>
> SKIPPED
> [INFO] WSO2 Carbon - Tenant Identity Provider Management . SKIPPED
> [INFO] WSO2 Carbon - Tenant Identity Provider Management UI  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 45:48.431s
> [INFO] Finished at: Thu Aug 08 16:04:06 IST 2013
> [INFO] Final Memory: 1460M/1920M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project
> org.wso2.carbon.appfactory.repository.mgt.service: Compilation failure:
> Compilation failure:
> [ERROR]
> /home/shani/sranasinghe/trunk/carbon/platform/trunk/components/appfac/org.wso2.carbon.appfactory.repository/src/main/java/org/wso2/carbon/appfactory/git/repository/provider/GITBlitBasedGITRepositoryProvider.java:[97,18]
> getAppRepositoryURL(java.lang.String,java.lang.String) is already defined
> in
> org.wso2.carbon.appfactory.git.repository.provider.GITBlitBasedGITRepositoryProvider
> [ERROR]
> /home/shani/sranasinghe/trunk/carbon/platform/trunk/components/appfac/org.wso2.carbon.appfactory.repository/src/main/java/org/wso2/carbon/appfactory/git/repository/provider/GITBlitBasedGITRepositoryProvider.java:[97,18]
> getAppRepositoryURL(java.lang.String,java.lang.String) is already defined
> in
> org.wso2.carbon.appfactory.git.repository.provider.GITBlitBasedGITRepositoryProvider
> [ERROR]
> /home/shani/sranasinghe/trunk/carbon/platform/trunk/components/appfac/org.wso2.carbon.appfactory.repository/src/main/java/org/wso2/carbon/appfactory/git/repository/provider/GITBlitBasedGITRepositoryProvider.java:[91,4]
> method does not override or implement a method from a supertype
> [ERROR]
> /home/shani/sranasinghe/trunk/carbon/platform/trunk/components/appfac/org.wso2.carbon.appfactory.repository/src/main/java/org/wso2/carbon/appfactory/git/repository/provider/GITBlitBasedGITRepositoryProvider.java:[96,4]
> method does not override or implement a method from a supertype
>
>
> --
> *Shani Ranasinghe*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 2273555
> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Asanka Vithanage

[Ishara Premadasa]

Congrats Asanka!


On Mon, Aug 5, 2013 at 11:51 AM, Suneth Ranasinghe  wrote:

> Congratz Asanka !
>
>
> On Mon, Aug 5, 2013 at 11:36 AM, Evanthika Amarasiri 
> wrote:
>
>> Hi,
>>
>> I would like to welcome Asanka Vithanage as a WSO2 Committer.
>>
>> AsankaV has made great contributions for the WSO2 Carbon platform,
>> specially Message Broker & App-Server products.
>>
>> Welcome aboard AsankaV & keep up the good work.
>>
>> Regards,
>> Evanthika Amarasiri
>> Senior Technical Lead - Quality Assurance
>> Mobile: +94773125935
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Suneth Ranasinghe
> Senior Software Engineer - QA
> Mobile: +94717387198
> *
> *
> wso2.com
> Lean Enterprise Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Chanika

[Ishara Premadasa]

Congratz Chanika :)


On Mon, Aug 5, 2013 at 10:19 AM, Balakrishnan Gokulakrishnan  wrote:

> Congrats Chanika!!
>
> On 5 August 2013 09:24, Anjana Fernando  wrote:
>
>> Hi everyone,
>>
>> It's my pleasure to announce Chanika as a WSO2 commiter. Chanika has done
>> many contribution in improving DSS features. And I'm sure she will continue
>> to be a key member in the team. Chanika, welcome aboard and keep it up! ..
>>
>> Cheers,
>> Anjana.
>> --
>> *Anjana Fernando*
>> Technical Lead
>>  WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Balakrishnan Gokulakrishnan*
> Software Engineer,
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/gokulbs
> Mobile: +94775935789
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Welcome Susankha Nirmala as a WSO2 Committer

[Ishara Premadasa]

Congratulations Susankha!


On Fri, Jul 26, 2013 at 11:57 AM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:

> Congratulations Susankha !!!
>
>
> On Fri, Jul 26, 2013 at 11:51 AM, Sumedha Kodithuwakku 
> wrote:
>
>> Congratz Susankha...!
>>
>>
>> On Fri, Jul 26, 2013 at 11:49 AM, Pulasthi Supun wrote:
>>
>>> Congratzz Susankha
>>>
>>> Regards
>>> Pulasthi
>>>
>>>
>>> On Fri, Jul 26, 2013 at 11:47 AM, Jasintha Dasanayake >> > wrote:
>>>

 Congratz

 /Jasintha


 On Fri, Jul 26, 2013 at 11:39 AM, Shameera Rathnayaka <
 shame...@wso2.com> wrote:

> Congratzz Susankha
>
>
>
>
> On Fri, Jul 26, 2013 at 11:36 AM, Harshana Martin 
> wrote:
>
>> Hi All,
>>
>> It is my distinct pleasure to welcome Susankha Nirmala as a WSO2
>> Committer.
>>
>> Susankha has made some great contributions to WSO2 Developer Studio
>> and the Carbon Platform during the last couple of months and in 
>> recognition
>> of his commitment and contributions, he has been voted as a Committer
>> for WSO2.
>>
>> Susankha, Congratulations and Welcome Aboard!
>>
>> Keep up the good work!!
>>
>> Thanks and Regards,
>> Harshana
>>  --
>>
>> Harshana Martin
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 775 998 115
>> Profile: https://www.google.com/profiles/harshana05
>> Blog: http://harshana05.blogspot.com
>> Twitter: http://twitter.com/harshana05
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Software Engineer - WSO2 Inc.*
> *email: shameera AT wso2.com  , shameera AT
> apache.org *
> *phone:  +9471 922 1454*
> *
> *
> *Linked in : *
> http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
> *Twitter : *https://twitter.com/Shameera_R
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Jasintha Dasanayake
 **Software Engineer
 WSO2 Inc. | http://wso2.com

 lean . enterprise . middleware
 *
 *
 *
 *mobile :- 077 291 6596*

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> --
>>> Pulasthi Supun
>>> Software Engineer; WSO2 Inc.; http://wso2.com,
>>> Email: pulas...@wso2.com
>>> Mobile: +94 (71) 9258281
>>> Blog : http://pulasthisupun.blogspot.com/
>>> Git hub profile: https://github.com/pulasthi
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Manula Chathurika Thantriwatte*
> Software Engineer
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 77 2492511
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Zookeeper] [MB] Log4j MBean registration gives errors when starting Apache Zookeeper server

[Ishara Premadasa]

Hi,

Apache ZooKeeper has extensive support for JMX and JMX console is enabled
by default at the server start up [1]. However with this ZooKeeper
registers log4j MBeans as well and this throws a following error log in the
MB admin console when ZooKeeper server is started in clustered mode of MB
though it doesn't break any functionality.

TID: [0] [MB] [2013-07-17 20:43:55,894]  INFO
{org.wso2.carbon.coordination.server.CoordinationServer} -  Starting
Coordination server in clustered mode...
{org.wso2.carbon.coordination.server.CoordinationServer}
TID: [0] [MB] [2013-07-17 20:43:55,916] ERROR
{org.apache.log4j.jmx.AppenderDynamicMBean} -  Could not add
DynamicLayoutMBean for
[CARBON_LOGFILE,layout=org.wso2.carbon.utils.logging.TenantAwarePatternLayout].
{org.apache.log4j.jmx.AppenderDynamicMBean}
javax.management.InstanceAlreadyExistsException:
log4j:appender=CARBON_LOGFILE,layout=org.wso2.carbon.utils.logging.TenantAwarePatternLayout
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:483)
at
org.apache.log4j.jmx.AppenderDynamicMBean.registerLayoutMBean(Unknown
Source)
at org.apache.log4j.jmx.AppenderDynamicMBean.preRegister(Unknown Source)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegisterInvoke(DefaultMBeanServerInterceptor.java:1010)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:938)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:483)
at
org.apache.log4j.jmx.LoggerDynamicMBean.registerAppenderMBean(Unknown
Source)
at
org.apache.log4j.jmx.LoggerDynamicMBean.appenderMBeanRegistration(Unknown
Source)
at org.apache.log4j.jmx.LoggerDynamicMBean.postRegister(Unknown Source)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postRegisterInvoke(DefaultMBeanServerInterceptor.java:1035)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:974)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:483)
at org.apache.log4j.jmx.HierarchyDynamicMBean.addLoggerMBean(Unknown
Source)
at org.apache.log4j.jmx.HierarchyDynamicMBean.addLoggerMBean(Unknown
Source)
at
org.apache.zookeeper.jmx.ManagedUtil.registerLog4jMBeans(ManagedUtil.java:67)
at
org.apache.zookeeper.server.quorum.QuorumPeerMain.runFromConfig(QuorumPeerMain.java:122)
at
org.wso2.carbon.coordination.server.CoordinationServer.run(CoordinationServer.java:78)
TID: [0] [MB] [2013-07-17 20:43:55,916] ERROR
{org.apache.log4j.jmx.AppenderDynamicMBean} -  Could not add
DynamicLayoutMBean for
[CARBON_LOGFILE,layout=org.wso2.carbon.utils.logging.TenantAwarePatternLayout].
{org.apache.log4j.jmx.AppenderDynamicMBean}
javax.management.InstanceAlreadyExistsException:
log4j:appender=CARBON_LOGFILE,layout=org.wso2.carbon.utils.logging.TenantAwarePatternLayout
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:483)
at
org.apache.log4j.jmx.AppenderDynamicMBean.registerLayoutMBean(Unknown
Source)
at org.apache.log4j.jmx.AppenderDynamicMBean.preRegister(Unknown Source)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegisterInvoke(DefaultMBeanServerInterceptor.java:1010)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:938)
at
com.sun.jmx.inter

[Dev] Build failure in platform/dependencies/andes/0.13.0-wso2v9 in 4.1.0 branch

[Ishara Premadasa]

Hi Srinath,

I am getting the following compilation errors when building andes
0.13.0-wso2v9. It seems that the package 'org.wso2.andes.kernel' and
DistrupterBasedCassandraExecuter class which were introduced in distrupter
based writing to cassandra, are not added to svn repo. Pls have a look.

Thanks!
Ishara

compile:
 [echo] Targeting : 1.5
[javac] Compiling 492 source files to
/home/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/build/scratch/broker/classes
[javac]
/home/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/broker/src/main/java/org/wso2/andes/server/AMQChannel.java:51:
package org.wso2.andes.kernel does not exist
[javac] import org.wso2.andes.kernel.AndesMessageMetadata;
[javac] ^
[javac]
/home/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/broker/src/main/java/org/wso2/andes/server/AMQChannel.java:101:
cannot find symbol
[javac] symbol  : class DistrupterBasedCassandraExecuter
[javac] location: package org.wso2.andes.tools.utils
[javac] import
org.wso2.andes.tools.utils.DistrupterBasedCassandraExecuter;
[javac]  ^
[javac]
/home/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/broker/src/main/java/org/wso2/andes/server/store/CassandraMessageStore.java:73:
package org.wso2.andes.kernel does not exist
[javac] import org.wso2.andes.kernel.AndesMessageMetadata;
[javac] ^
[javac]
/home/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/broker/src/main/java/org/wso2/andes/server/store/CassandraMessageStore.java:74:
package org.wso2.andes.kernel does not exist
[javac] import org.wso2.andes.kernel.AndesMessagePart;
[javac] ^
[javac]
/home/isha/Documents/ideaprojs/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/broker/src/main/java/org/wso2/andes/server/store/CassandraMessageStore.java:75:
package org.wso2.andes.kernel does not exist
[javac] import org.wso2.andes.kernel.MessageStore;
[javac] ^
[javac]
/home/isha/Documents/ideaprojs/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/broker/src/main/java/org/wso2/andes/server/store/CassandraMessageStore.java:109:
cannot find symbol
[javac] symbol  : class DistrupterBasedCassandraExecuter
[javac] location: package org.wso2.andes.tools.utils
[javac] import
org.wso2.andes.tools.utils.DistrupterBasedCassandraExecuter;
[javac]  ^
[javac]
/home/isha/Documents/ideaprojs/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/broker/src/main/java/org/wso2/andes/server/store/CassandraMessageStore.java:110:
package org.wso2.andes.tools.utils.DistrupterBasedCassandraExecuter does
not exist
[javac] import
org.wso2.andes.tools.utils.DistrupterBasedCassandraExecuter.PendingJob;

[javac]   ^
[javac]
/home/isha/Documents/ideaprojs/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/broker/src/main/java/org/wso2/andes/server/store/CassandraMessageStore.java:317:
cannot find symbol
[javac] symbol  : class DistrupterBasedCassandraExecuter
[javac] location: class
org.wso2.andes.server.store.CassandraMessageStore
[javac] private static DistrupterBasedCassandraExecuter
distrupterBasedCassandraExecuter;
[javac]^
[javac]
/home/isha/Documents/ideaprojs/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/broker/src/main/java/org/wso2/andes/server/store/CassandraMessageStore.java:327:
cannot find symbol
[javac] symbol  : class DistrupterBasedCassandraExecuter
[javac] location: class
org.wso2.andes.server.store.CassandraMessageStore
[javac] public static DistrupterBasedCassandraExecuter
getDistrupterBasedCassandraExecuter() {
[javac]   ^
[javac]
/home/isha/Documents/ideaprojs/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/broker/src/main/java/org/wso2/andes/server/store/CassandraMessageStore.java:5406:
package org.wso2.andes.kernel does not exist
[javac] public org.wso2.andes.kernel.MessageStore getMessageStore()
{
[javac] ^
[javac]
/home/isha/Documents/ideaprojs/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/broker/src/main/java/org/wso2/andes/server/AMQChannel.java:415:
cannot find symbol
[javac] symbol: class DistrupterBasedCassandraExecuter
[javac] DistrupterBasedCassandraExecuter
batchexec =
ClusterResourceHolder.getInstance().getCassandraMessageStore().getDistrupterBasedCassandraExecuter();
[javac] ^
[javac]
/home/isha/Documents/ideaprojs/carbon_4.1.0/platform/dependencies/andes/0.13.0-wso2v9/java/broker/src/main/java/org/wso2/andes/server/AMQChannel.java:428:
cannot find symbol
[javac] symbol: class AndesM

Re: [Dev] WSO2 Committers += Punnadi Goonewardena

[Ishara Premadasa]

Congratulations Punnadi!


On Wed, Jul 3, 2013 at 1:40 PM, Ramith Jayasinghe  wrote:

> Congrats 
>
> On Wed, Jul 3, 2013 at 1:37 PM, Dimuthu Leelarathne wrote:
>
>> Hi Punnadi,
>>
>> Congratulations!
>>
>> It is with great pleasure that we welcome you as a WSO2 committer. Thank
>> you for your contributions.
>>
>> thanks and best regards,
>> Dimuthu
>>
>> --
>> Dimuthu Leelarathne
>> Architect & Product Lead of App Factory
>>
>> WSO2, Inc. (http://wso2.com)
>> email: dimut...@wso2.com
>>
>> Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 776715671
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Shafreen Anfar

[Ishara Premadasa]

Congratz Shafreen!


On Wed, Jul 3, 2013 at 2:10 PM, Nihanth Joseph  wrote:

> Congrats Shafreen
>
>
> On Wed, Jul 3, 2013 at 2:08 PM, Ravi Undupitiya  wrote:
>
>> Congrats Shafreen! :)
>>
>>
>> On Wed, Jul 3, 2013 at 2:03 PM, Kasun Indrasiri  wrote:
>>
>>> Hi Folks,
>>>
>>> Its my pleasure to welcome Shafreen Anfar as a WSO2 Committer. He is a
>>> key contributor in bug fixing of 4.7 release and done a good job in ESB
>>> performance testing too.
>>>
>>> Shafreen, welcome aboard and keep up the good work.
>>>
>>> Thanks.
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 71 536 4128
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Ravi Undupitiya*
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> *
>> *
>> *E-mail: r...@wso2.com
>> **M: **+94 772 930 712*
>> *
>> *Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nihanth Joseph
> Senior Software Engineer
> Mob: +94719187136
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Build error when building Orbit in Carbon 4.1.0 branch

[Ishara Premadasa]

Hi Ravi,

I am getting following build error [1] when trying to build orbit in
https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.1.0/ branch. It
seems that you have removed the 'bsf' module from orbit but the orbit pom
file still refers to that. Can you pls have a look and fix the pom file
accordingly.

Thanks!
Ishara

[1].
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.wso2.carbon:orbit-parent:4.1.0
(/home/isha/Documents/ideaprojs/carbon_4.1.0/orbit/pom.xml) has 1 error
[ERROR] Child module /home/isha//carbon_4.1.0/orbit/bsf/3.0.0.wso2v3 of
/home/isha/carbon_4.1.0/orbit/pom.xml does not exist
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Shameera Rathnayaka

[Ishara Premadasa]

Congrats Shameera :)


On Mon, Jul 1, 2013 at 2:15 PM, Darshana Gunawardana wrote:

> Congratulations Shameera...!!!
>
> On Mon, Jul 1, 2013 at 1:58 PM, Danushka Fernando 
> wrote:
> > Congratz Shameera !!!
> >
> > Thanks & Regards
> > Danushka Fernando
> > Software Engineer
> > WSO2 inc. http://wso2.com/
> > Mobile : +94716332729
> >
> >
> > On Mon, Jul 1, 2013 at 1:54 PM, Gayan Dhanushka  wrote:
> >>
> >> Congratzz Shameera !!!
> >>
> >>
> >> On Mon, Jul 1, 2013 at 1:49 PM, Chanika Geeganage 
> >> wrote:
> >>>
> >>> Congratz Shameera 
> >>>
> >>>
> >>> On Mon, Jul 1, 2013 at 1:46 PM, Balakrishnan Gokulakrishnan
> >>>  wrote:
> 
>  Congratulations Shameera!
> 
>  On 1 July 2013 13:21, Pradeep Fernando  wrote:
> >
> > Hi Devs,
> >
> > Its my pleasure to welcome Shameera Rathnayaka as a WSO2 committer.
> > He has made valuable contributions to WSO2 Carbon platform over the
> > last few months. Thanks Shameera for the contributions and keep up
> the good
> > work.
> >
> >
> > Shameera, welcome aboard!!
> >
> > thanks,
> > --Pradeep
> >
> >
> >
> > ___
> > Dev mailing list
> > Dev@wso2.org
> > http://wso2.org/cgi-bin/mailman/listinfo/dev
> >
> 
> 
> 
>  --
>  Balakrishnan Gokulakrishnan
>  Software Engineer,
>  WSO2, Inc.; http://wso2.com
> 
>  Twitter:  http://twitter.com/gokulbs
>  Mobile: +94775935789
>  ___
>  Dev mailing list
>  Dev@wso2.org
>  http://wso2.org/cgi-bin/mailman/listinfo/dev
> 
> >>>
> >>>
> >>>
> >>> --
> >>> Best Regards..
> >>>
> >>> Chanika Geeganage
> >>> Software Engineer
> >>> WSO2, Inc.; http://wso2.com
> >>>
> >>> Mobile: +94773522586
> >>>
> >>> ___
> >>> Dev mailing list
> >>> Dev@wso2.org
> >>> http://wso2.org/cgi-bin/mailman/listinfo/dev
> >>>
> >>
> >>
> >>
> >> --
> >>
> >> Gayan Dhanushka
> >> Software Engineer
> >> WSO2 Inc.
> >> http://wso2.com
> >>
> >> Mobile : 0716662327
> >>
> >>
> >> ___
> >> Dev mailing list
> >> Dev@wso2.org
> >> http://wso2.org/cgi-bin/mailman/listinfo/dev
> >>
> >
> >
> > ___
> > Dev mailing list
> > Dev@wso2.org
> > http://wso2.org/cgi-bin/mailman/listinfo/dev
> >
>
>
>
> --
> Regards,
>
> Darshana Gunawardana
> Software Engineer
> WSO2 Inc.; http://wso2.com
> E-mail: darsh...@wso2.com
> Mobile: +94718566859
> Lean . Enterprise . Middleware
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Need to avoid stopping org.apache.cassandra.net.MessagingService before the OSGi framework is shut down

[Ishara Premadasa]

We experiencing the following issue when shutting down the MB server. While
performing read/write operations on cassandra and if the server shuts down
in middle (by clicking Ctl+C), we close the CassandraServerService first,
before closing the AndesService. This is done in order to stop any
operations currently running with Cassandra before shutting down the
broker. However ever if this is handled in OSGI level, at the server
shutdown the following logs are monitored,

[2013-06-28 14:47:41,745] INFO
{org.wso2.carbon.core.init.CarbonServerManager} - Shutdown hook
triggered
[2013-06-28 14:47:41,745] INFO
{org.wso2.carbon.core.init.CarbonServerManager} - Gracefully shutting down
WSO2 Message Broker...
[2013-06-28 14:47:41,747] INFO {org.wso2.carbon.core.ServerManagement} -
Starting to switch to maintenance mode...
*[2013-06-28 14:47:41,747] INFO {org.apache.cassandra.gms.Gossiper} -
Announcing shutdown
[2013-06-28 14:47:42,748] INFO {org.apache.cassandra.net.MessagingService}
- Waiting for messaging service to quiesce
[2013-06-28 14:47:42,749] INFO {org.apache.cassandra.net.MessagingService}
- MessagingService shutting down server thread. *
[2013-06-28 14:47:44,027] INFO {org.wso2.carbon.core.ServerManagement} -
Stopped all transport listeners
[2013-06-28 14:47:44,028] INFO {org.wso2.carbon.core.ServerManagement} -
Waiting for request service completion...
[2013-06-28 14:47:44,030] INFO {org.wso2.carbon.core.ServerManagement} -
All requests have been served.
[2013-06-28 14:47:44,030] INFO {org.wso2.carbon.core.ServerManagement} -
Waiting for deployment completion...
[2013-06-28 14:47:44,034] INFO {org.wso2.carbon.core.ServerManagement} -
All deployment tasks have been completed.
[2013-06-28 14:47:44,034] INFO {org.wso2.carbon.core.ServerManagement} -
Waiting for server task completion...
[2013-06-28 14:47:44,035] INFO {org.wso2.carbon.core.ServerManagement} -
All server tasks have been completed.
[2013-06-28 14:47:44,035] INFO
{org.wso2.carbon.core.init.CarbonServerManager} - Shutting down WSO2
Message Broker...
[2013-06-28 14:47:44,036] INFO
{org.apache.axis2.transport.tcp.TCPTransportSender} - TCP Sender Shutdown
[2013-06-28 14:47:44,036] INFO *{org.wso2.carbon.core.init.CarbonServerManager}
- Shutting down OSGi framework...*
[2013-06-28 14:47:44,198] INFO
{org.wso2.andes.server.registry.ApplicationRegistry} - Shutting down
ApplicationRegistry(
org.wso2.andes.server.registry.ConfigurationFileApplicationRegistry@74607cd0)

[2013-06-28 14:47:44,198] INFO
{org.wso2.andes.server.registry.ApplicationRegistry} - Shutting down
ApplicationRegistry:
org.wso2.andes.server.registry.ConfigurationFileApplicationRegistry@74607cd0
[2013-06-28 14:47:44,200] INFO
{org.wso2.andes.server.cluster.GlobalQueueManager} - Stopping all locally
existing global queue workers
[2013-06-28 14:47:44,200] INFO
{org.wso2.andes.server.cluster.GlobalQueueManager} - Removing Global Queue
Worker for Global Queue : GlobalQueue_0
[2013-06-28 14:47:44,200] INFO
{org.wso2.andes.server.cluster.GlobalQueueManager} - Removing Global Queue
Worker for Global Queue : GlobalQueue_6
[2013-06-28 14:47:44,200] INFO
{org.wso2.andes.server.cluster.GlobalQueueManager} - Removing Global Queue
Worker for Global Queue : GlobalQueue_8
[2013-06-28 14:47:44,201] INFO
{org.wso2.andes.server.cluster.GlobalQueueManager} - Removing Global Queue
Worker for Global Queue : GlobalQueue_7
[2013-06-28 14:47:44,201] INFO
{org.wso2.andes.server.cluster.GlobalQueueManager} - Removing Global Queue
Worker for Global Queue : GlobalQueue_5
[2013-06-28 14:47:44,201] INFO
{org.wso2.andes.server.cluster.GlobalQueueManager} - Removing Global Queue
Worker for Global Queue : GlobalQueue_4
[2013-06-28 14:47:44,201] INFO
{org.wso2.andes.server.cluster.GlobalQueueManager} - Removing Global Queue
Worker for Global Queue : GlobalQueue_1
[2013-06-28 14:47:44,201] INFO
{org.wso2.andes.server.cluster.GlobalQueueManager} - Removing Global Queue
Worker for Global Queue : GlobalQueue_3
[2013-06-28 14:47:44,201] INFO
{org.wso2.andes.server.cluster.GlobalQueueManager} - Removing Global Queue
Worker for Global Queue : GlobalQueue_2
[2013-06-28 14:47:44,201] INFO
{org.wso2.andes.server.cluster.GlobalQueueManager} - Removing Global Queue
Worker for Global Queue : GlobalQueue_9
[2013-06-28 14:47:44,201] INFO
{org.wso2.andes.server.store.CassandraMessageStore} - Stopping all current
queue message publishers
[2013-06-28 14:47:44,201] INFO
{org.wso2.andes.server.store.CassandraMessageStore} - Stopping all current
topic message publishers
[2013-06-28 14:47:44,201] INFO
{org.wso2.andes.server.store.CassandraMessageStore} - Stopping all global
queue workers locally
[2013-06-28 14:47:44,202] INFO
{org.wso2.andes.server.security.auth.manager.PrincipalDatabaseAuthenticationManager}
- Unregistering UserManagementMBean
[2013-06-28 14:47:44,205] INFO
{org.wso2.carbon.andes.internal.QpidServiceComponent} - Deactivating
Carbonized Cassandra Server...
[2013-06-28 14:47:44,310] INFO
{org.wso2.carbon.core.init.CarbonS

Re: [Dev] WSO2 Committers += Inosh Goonewardena

[Ishara Premadasa]

Congratz Inosh!


On Thu, Jun 27, 2013 at 10:54 AM, Malith Dhanushka  wrote:

> Congratz Inosh...!!!
>
> On Thu, Jun 27, 2013 at 10:27 AM, Kasun Weranga  wrote:
>
>> Hi all,
>>
>> Its my pleasure to welcome Inosh Goonewardena as a WSO2 Committer.
>> He has made great contributions to WSO2 BAM and other projects during the
>> last few months, Thank you so much for all your hard work.
>> Inosh, welcome aboard and keep up the good work.
>>
>>
>> Thanks,
>> KasunW
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Malith Dhanushka
>
> Engineer - Data Technologies
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Blog* :  mmalithh.blogspot.com
> *Linked-i*n  :   http://lk.linkedin.com/in/malithd
> *Twitter* :   https://twitter.com/MalithWD
> *Mobile*  : +94 716 506 693
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AS] [MB] Complexities in integrating AS with MB as JMS Transport is enabled for all the deployed services

[Ishara Premadasa]

Hi Shammi,

Thanks for this information. As the App Server 5.1.1 which comes with newly
changed JMS transport library is not released yet, i patched the
axis2-transport-jms_1.1.0.wso2v7 into AS 5.1.0 and now the integrations
works fine. However sample REST, JS services etc. still needs to be changed
in the services.xml file.

I have added the documentation in to [1] with explaining the necessary
configuration details.

Thanks!
Ishara

[1]  http://docs.wso2.org/wiki/display/MB210/Integrating+WSO2+AS


On Wed, Jun 19, 2013 at 1:21 PM, Shammi Jayasinghe  wrote:

> Hi Ishara,
>
> Yes, We are unable to support dynamic queues with AMQP 0-91 version.
> Because of that problem we have solved this issue in a different way.[1].
> If you get the latest JMS transport library in to the App Server, it should
> fix the problem of defining queue name in the jndi.properties file of the
> server. We have
> discussed this problem and the feasible solution in the mail thread "ESB
> and MB integration"
>
> Thanks
> Shammi
>
> [1]https://wso2.org/jira/browse/CARBON-14108
>
>
>
> On Wed, Jun 19, 2013 at 1:07 PM, Ishara Premadasa  wrote:
>
>> Hi,
>>
>> I am trying to integrate MB 2.1.0 with AS 5.1.0 in order to enable a
>> sample service deployed in App Server to be subscribed and receive messages
>> from a queue/topic registered in MB [1]. However when doing this there are
>> practical limitations in this scenario which makes it not useful to
>> integrate MB with App Server.
>>
>> As WSO2 MB currently do not have dynamic Queues/Topics support, it can't
>> dynamically create destinations when they are not defined in the JNDI
>> Initial Context. Once the JMS transport is enabled in App Server it tries
>> to create a JMS Queue for each deployed service in AS at the start up. As
>> there are no jms queues defined in jndi.properties file for these start up
>> services (except for the sample service which we going to use with MB) App
>> Server fails to start in this case and loops the following error in the
>> console.
>>
>> [2013-06-19 12:49:39,965]  INFO
>> {org.apache.axis2.transport.jms.ServiceTaskManager} -  Task manager for
>> service : JavaScriptStubGeneratorService [re-]initialized
>> [2013-06-19 12:49:39,985]  WARN {org.apache.axis2.transport.jms.JMSUtils}
>> -  Cannot locate destination : JavaScriptStubGeneratorService
>> [2013-06-19 12:49:39,993] ERROR
>> {org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
>> exception
>> java.lang.UnsupportedOperationException: The new addressing based sytanx
>> is not supported for AMQP 0-8/0-9 versions
>> at
>> org.wso2.andes.client.AMQSession_0_8.handleAddressBasedDestination(AMQSession_0_8.java:572)
>> at
>> org.wso2.andes.client.AMQSession.registerConsumer(AMQSession.java:2838)
>> at org.wso2.andes.client.AMQSession.access$500(AMQSession.java:117)
>> at org.wso2.andes.client.AMQSession$4.execute(AMQSession.java:2031)
>> at org.wso2.andes.client.AMQSession$4.execute(AMQSession.java:1997)
>> at
>> org.wso2.andes.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:305)
>> at
>> org.wso2.andes.client.AMQConnection.executeRetrySupport(AMQConnection.java:621)
>> at
>> org.wso2.andes.client.failover.FailoverRetrySupport.execute(FailoverRetrySupport.java:102)
>> at
>> org.wso2.andes.client.AMQSession.createConsumerImpl(AMQSession.java:1995)
>> at
>> org.wso2.andes.client.AMQSession.createConsumer(AMQSession.java:993)
>> at
>> org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:642)
>> at
>> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:871)
>> at
>> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getMessageConsumer(ServiceTaskManager.java:741)
>> at
>> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:498)
>> at
>> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:420)
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>>
>>
>>
>> Therefore if we are going to integrate MB into AS need to do one of the
>> below two configuration opti

[Dev] [AS] [MB] Complexities in integrating AS with MB as JMS Transport is enabled for all the deployed services

[Ishara Premadasa]

Hi,

I am trying to integrate MB 2.1.0 with AS 5.1.0 in order to enable a sample
service deployed in App Server to be subscribed and receive messages from a
queue/topic registered in MB [1]. However when doing this there are
practical limitations in this scenario which makes it not useful to
integrate MB with App Server.

As WSO2 MB currently do not have dynamic Queues/Topics support, it can't
dynamically create destinations when they are not defined in the JNDI
Initial Context. Once the JMS transport is enabled in App Server it tries
to create a JMS Queue for each deployed service in AS at the start up. As
there are no jms queues defined in jndi.properties file for these start up
services (except for the sample service which we going to use with MB) App
Server fails to start in this case and loops the following error in the
console.

[2013-06-19 12:49:39,965]  INFO
{org.apache.axis2.transport.jms.ServiceTaskManager} -  Task manager for
service : JavaScriptStubGeneratorService [re-]initialized
[2013-06-19 12:49:39,985]  WARN {org.apache.axis2.transport.jms.JMSUtils}
-  Cannot locate destination : JavaScriptStubGeneratorService
[2013-06-19 12:49:39,993] ERROR
{org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
exception
java.lang.UnsupportedOperationException: The new addressing based sytanx is
not supported for AMQP 0-8/0-9 versions
at
org.wso2.andes.client.AMQSession_0_8.handleAddressBasedDestination(AMQSession_0_8.java:572)
at
org.wso2.andes.client.AMQSession.registerConsumer(AMQSession.java:2838)
at org.wso2.andes.client.AMQSession.access$500(AMQSession.java:117)
at org.wso2.andes.client.AMQSession$4.execute(AMQSession.java:2031)
at org.wso2.andes.client.AMQSession$4.execute(AMQSession.java:1997)
at
org.wso2.andes.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:305)
at
org.wso2.andes.client.AMQConnection.executeRetrySupport(AMQConnection.java:621)
at
org.wso2.andes.client.failover.FailoverRetrySupport.execute(FailoverRetrySupport.java:102)
at
org.wso2.andes.client.AMQSession.createConsumerImpl(AMQSession.java:1995)
at org.wso2.andes.client.AMQSession.createConsumer(AMQSession.java:993)
at
org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:642)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:871)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getMessageConsumer(ServiceTaskManager.java:741)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:498)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:420)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)



Therefore if we are going to integrate MB into AS need to do one of the
below two configuration options.

1. Go through all other deployed services in AS and modify the services.xml
file in order to only listen via http,https transports.
2. Go through all other deployed services in AS and add a corresponding
queue name to jndi.properties file with each service name.

Any option of this two is not feasible and not acceptable in user's
perspective as well as AS server will fail immediately if there is new
service is deployed on the run. Is there any way whether we can only enable
the JMS transport for a selected service only?

In side note Apache ActiveMQ provides dynamic queue/topic support, [2]  so
AS starts fine with ActiveMQ while ActiveMQ creates a queue in the broker
for each deployed service in AS. Hence as a workaround this can be get
worked if MB adds dynamic queue support, however the correct solution would
be add a configuration to enable/disable JMS transport in services, as it
is done in ESB proxy services.

Thanks!
Ishara

 [1] https://wso2.org/jira/browse/MB-238
 [2] http://activemq.apache.org/how-do-i-create-new-destinations.html

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] build issue-trunk/registry uddi module

[Ishara Premadasa]

This error was reported in 'Re: [Bamboo-Build] WSO2 Carbon 4.1.x > Platform
4.1.3 > #153 has FAILED' mail thread for Carbon 4.1.0 branch  as well few
days back. seems it it not fixed yet.

- Ishara


On Mon, Jun 10, 2013 at 6:53 PM, Vijayaratha Vijayasingam
wrote:

> anyone from registry team pls chk this?
>
>
> On 10 June 2013 12:19, Vijayaratha Vijayasingam  wrote:
>
>>
>> Hi all;
>> Im getting
>> [INFO] Building WSO2 Carbon - Registry - UDDI Service 4.2.0-SNAPSHOT
>> [INFO]
>> 
>> [INFO]
>> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
>> org.wso2.carbon.registry.uddi ---
>> [INFO]
>> [INFO] --- incremental-build-plugin:1.3:incremental-build (default) @
>> org.wso2.carbon.registry.uddi ---
>> [INFO] Verifying module descriptor ...
>> [INFO] Pom descriptor modification detected.
>> [INFO] Deleting
>> C:\Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\target
>> [INFO]
>> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
>> org.wso2.carbon.registry.uddi ---
>> [debug] execute contextualize
>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>> [INFO] Copying 1 resource
>> [INFO]
>> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
>> org.wso2.carbon.registry.uddi ---
>> [INFO] Compiling 10 source files to
>> C:\Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\target\classes
>> [INFO] -
>> [ERROR] COMPILATION ERROR :
>> [INFO] -
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\utils\UDDIUtil.java:[21
>> ,32] package org.apache.juddi.api.impl does not exist
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\utils\UDDIUtil.java:[22
>> ,32] package org.apache.juddi.api.impl does not exist
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\utils\UDDIUtil.java:[23
>> ,32] package org.apache.juddi.api.impl does not exist
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\utils\UDDIUtil.java:[24
>> ,32] package org.apache.juddi.api.impl does not exist
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\utils\UDDIUtil.java:[49
>> ,19] cannot find symbol
>> symbol  : class UDDISecurityImpl
>> location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\utils\UDDIUtil.java:[50
>> ,19] cannot find symbol
>> symbol  : class UDDIPublicationImpl
>> location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\utils\UDDIUtil.java:[51
>> ,19] cannot find symbol
>> symbol  : class UDDIInquiryImpl
>> location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\utils\UDDIUtil.java:[15
>> 6,19] cannot find symbol
>> symbol  : class UDDISecurityImpl
>> location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\utils\UDDIUtil.java:[17
>> 0,19] cannot find symbol
>> symbol  : class UDDIPublicationImpl
>> location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\utils\UDDIUtil.java:[18
>> 3,19] cannot find symbol
>> symbol  : class UDDIInquiryImpl
>> location: class org.wso2.carbon.registry.uddi.utils.UDDIUtil
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\servlet\JUDDIRegistrySe
>> rvlet.java:[6,23] cannot find symbol
>> symbol  : class Registry
>> location: package org.apache.juddi
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\utils\UDDIUtil.java:[21
>> ,32] package org.apache.juddi.api.impl does not exist
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi\src\main\java\org\wso2\carbon\registry\uddi\utils\UDDIUtil.java:[22
>> ,32] package org.apache.juddi.api.impl does not exist
>> [ERROR]
>> \Projects\platform\trunk\components\registry\org.wso2.carbon.registry.uddi

[Dev] [MB] Improving MB 2.1.0 samples to get a clean map between samples in the pack and documentation

[Ishara Premadasa]

Hi all,

The current list of available samples in WSO2 MB has some inconsistencies
as the sample content included in the pack is not mapping clearly with what
is explained in the 'Samples' section of the documentation [1]. Therefore
for the MB 2.1.0 release we have rearranged the sample directory to
demonstrate this mapping between the sample and the doc as well as have
added some new samples for newly added features.

The following is the structure of the set of samples available now after
the changes. The new samples are highlighted in bold.

1. JMSClient samples
 -->  JMS Queue Client: re-mapped with queue sender/receiver
classes in doc
 -->  JMS Topic Client : re-mapped with topic
publisher/subscriber classes in doc
 *-->  JMS Message Listener Client :  A sample to display async
message listening aspects in both queue and topics

2. Durable Topics Subscriber sample : A sample to display how the durable
subscriptions work for  JMS Topics, mapped according to the existing doc in
the samples guide.

3. Hierarchical Topics Subscriber sample : A sample to display how
hierarchical topic subscriptions works in MB
 *
4. JMS Transports Sample - Not changed

5. WS client samples
  --> Web Service Client Sample   *  *
*  --> WS-Event Message Producer Client (yet to be added)

*6. Message Broker Clustering Example  - Not changed
*
*
*
*
All the sample guides are currently added into the MB documentation [2].
Please suggest me if there is any sample required to be added here, in
users' perspective.

Thanks!
Ishara

[1] https://wso2.org/jira/browse/MB-196
[2] http://docs.wso2.org/wiki/display/MB210/Samples


-- 
Ishara Premasada
Software Engineer, Integrations TG
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MB Integration Test Failures in 4.1.2 Branch

[Ishara Premadasa]

@ Shammi,

I was looking into this test failure and it seems the failed test which is
JMSQueueSubscribePublishTestCase has no errors but fails due to there are
no any messages received at the Message Listener end, hence the assertion
fails.

The reason for this is in the previous test case '
JMSQueuesSequentialTestCase ' there are 1 messages published into the
queue and because of this there is a latency in delivering the messages
into the queues. Because of this the messages published for the
JMSQueueSubscribePublishTestCase will not be received in the message
listeners' end within the configured waiting time.

We can simply move the JMSQueuesSequentialTestCase to be run as final test
and state in a comment that 'always run this test as the last' which will
fix this. I also tried that reducing the published message count upto 5000
in JMSQueuesSequentialTestCase and it worked too. WDYT?

Thanks!
Ishara


On Fri, May 31, 2013 at 10:34 AM, Shammi Jayasinghe  wrote:

> Hi Nuwan,
>
> Sure , we ll look in to this. For the moment we have to comment out the
> test case and will add it once
> properly fixing.
>
> Thanks
> Shammi
>
>
> On Fri, May 31, 2013 at 8:40 AM, Nuwan Dias  wrote:
>
>> Hi,
>>
>> When building the patch-releases/4.1.2 we have encountered a test failure
>> at MB integration tests. Can we have this fixed please?
>>
>> BTW, is MB being released today?
>>
>> Surefire Report attached.
>>
>> [INFO] WSO2 Message Broker - Distribution  SUCCESS
>> [1:04.844s]
>> [INFO] WSO2 MB - Integration Tests ... FAILURE
>> [5:14.530s]
>> [INFO] WSO2 Business Activity Monitor  SKIPPED
>> [INFO] WSO2 Business Activity Monitor Styles Parent .. SKIPPED
>> [INFO] WSO2 BAM UI styles  SKIPPED
>> [INFO] WSO2 BAM UI styles  SKIPPED
>> [INFO] WSO2 Stratos - Cloud BAM Login User Interface . SKIPPED
>> [INFO] WSO2 Stratos - Cloud BAM Dashboard User Interface . SKIPPED
>> [INFO] WSO2 Business Activity Monitor Features Parent  SKIPPED
>> [INFO] WSO2 BAM - Features Aggregator Module . SKIPPED
>> [INFO] WSO2 BAM - Style Features . SKIPPED
>> [INFO] WSO2 BAM - Style Features . SKIPPED
>> [INFO] WSO2 Carbon - Cloud BAM UI Feature  SKIPPED
>> [INFO] WSO2 Carbon - Cloud BAM Dashboard UI Feature .. SKIPPED
>> [INFO] WSO2 BAM - Features Aggregator Module . SKIPPED
>> [INFO] WSO2 Business Activity Monitor P2 Profile Generation  SKIPPED
>> [INFO] WSO2 BAM Sample ... SKIPPED
>> [INFO] WSO2 BAM Toolbox .. SKIPPED
>> [INFO] WSO2 BAM Migration  SKIPPED
>> [INFO] migration . SKIPPED
>> [INFO] WSO2 Business Activity Monitor - Product .. SKIPPED
>> [INFO] WSO2 BAM Integration .. SKIPPED
>> [INFO] WSO2 BAM - Integration Test ... SKIPPED
>> [INFO] WSO2 Carbon - Patch releases - products - Aggregator Module
>>  SKIPPED
>> [INFO] WSO2 Platform Automated Suite - Parent project  SKIPPED
>> [INFO] WSO2 Platform Automated Suite - Artifact Repository  SKIPPED
>> [INFO] WSO2 Platform Automated Suite - Executor .. SKIPPED
>> [INFO] WSO2 Platform Automated Suite - Platform scenarios  SKIPPED
>> [INFO] WSO2 Platform Automated Suite - Distribution .. SKIPPED
>> [INFO] WSO2 Carbon - Patch releases - Platform Automated Test Suite
>>  SKIPPED
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 55:44.598s
>> [INFO] Finished at: Thu May 30 10:59:26 PDT 2013
>> [INFO] Final Memory: 2241M/3527M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on
>> project mb-integration-tests: There are test failures.
>> [ERROR]
>> [ERROR] Please refer to
>> /home/wso2/4.1.0/temp/platform/4.1.0/products/mb/2.1.0/modules/integration/target/surefire-reports
>> for the individual test results.
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>>
>>
>> --
>> Nuwan Dias
>>
>> Senior Software Engineer - WSO2, Inc. http://wso2.com
>>  email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> Best Regards,*
>
> Shammi Jayasinghe*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer, In

Re: [Dev] MB support for the JMS Message Types and Message header properties

[Ishara Premadasa]

Hi Asanka,

Addressing the JMSDeliveryMode , in MB all the messages are PERSISTENT as
we write the messages to Cassandra storage before they are getting
delivered.  Therefore IIRC if you make the Delivery Mode into
Non-Persistent in message level it will be handled as Persistent by Qpid
level.

I will go through these JIRAs and verify. Will be updating the
documentation according to the results found.

@Shammi/Hasitha,

In case that some of these message attributes are not configurable, how
about removing the corresponding columns from the queue browser view?
i.e. The Delivery Mode is always set into '2' (which is persistent mode)
even if a publisher client set it to '1' and sent to the queue. In that
case the user might feel doubtful of the results he sees in the browser
view. If not as Asanka has suggested we should be explaining these info in
the doc.

Thanks!
Ishara


On Wed, May 29, 2013 at 7:47 PM, Asanka Vithanage  wrote:

> Hi All,
>
> I have cover up the test on MB compatibility on JMS Message Types with
> queue and Topic scenarios.According to that observed MB can support the all
> JMS message types but with empty payload message observed
> https://wso2.org/jira/browse/MB-262 issue.
> Further found https://wso2.org/jira/browse/MB-271 issue while trying to
> browse the queue with ObectMessages.
>
>
> According to the JMS API following Message header properties should be
> settable at message level,
>
> JMSCorrelationID
> JMSCorrelationIDAsBytes
> JMSDeliveryMode
> JMSDestination
> JMSExpiration
> JMSMessageID
> JMSPriority
> JMSRedelivered
> JMSReplyTo
> JMSTimestamp
> JMSType
>
> But when we set the following properties at message level,It seems MB
> overwrites the property values
> JMSDeliveryMode  https://wso2.org/jira/browse/MB-264
> JMSExpirationhttps://wso2.org/jira/browse/MB-267
> JMSMessageID  https://wso2.org/jira/browse/MB-273
> JMSPriorityMB currently not providing message priority
> feature,so we can skip this for now
> JMSRedelivered https://wso2.org/jira/browse/MB-268
> JMSTimestamp  https://wso2.org/jira/browse/MB-274
>
>
> Further observed when we set the following properties at the
> MessageProducer level, they won't get overwrites by the MB and delivered as
> set.
>
> JMSDeliveryMode
> queueSender.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
> JMSPriority  queueSender.setPriority(1);
> JMSExpiration  queueSender.setTimeToLive(9);
>
>
> So are we intentionally overwriting these properties at MB level or are we
> yet to implement these features?
> Can we update the documentation on these, so users can understand what we
> support exactly and what are the possible workarounds? (
> https://wso2.org/jira/browse/MB-272)
>
>
>
>
>
> --
> Asanka Vithanage
> Senior Software Engineer -QA
> Mobile: +94 0716286708
> Email: asan...@wso2.com
> WSO2 Inc. www.wso2.com
>
>


-- 
Ishara Premasada
Software Engineer, Integrations TG
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Configuring ESB mgt console with WSO2IS/SSO

[Ishara Premadasa]

Hi Pradeep,

I have encountered previously that the same encoding error happens with IS
4.1.0 version and that is the reason for you to get this error. If it is
possible you can use IS 3.2.3 version which works fine with SSO.

As i got to know this error will be fixed in the next release once the fix
in [1] is applied.

Thanks!
Ishara

[1] https://wso2.org/jira/browse/IDENTITY-679


On Sun, May 26, 2013 at 10:13 AM, Pradeep Fernando  wrote:

> Hi,
>
>
> I tried the $subject. The redirection happens fine. However the ESB
> backend gives the below error. Google searching revealed that it has to do
> with base64 encoded response string introduced with 4.1.1. Hence I tried
> 4.1.0 IS. Still getting the same error. May be a trivial config issue in my
> side. Please advice.
>
> thanks,
> --Pradeep
>
>
> [Fatal Error] :1:1: Content is not allowed in prolog.
> [2013-05-26 05:38:55,507] ERROR - Util Error in constructing AuthRequest
> from the encoded String
> org.xml.sax.SAXParseException: Content is not allowed in prolog.
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
> at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
> at
> org.wso2.carbon.identity.authenticator.saml2.sso.common.Util.unmarshall(Util.java:100)
> at
> org.wso2.carbon.identity.authenticator.saml2.sso.ui.SSOAssertionConsumerService.doPost(SSOAssertionConsumerService.java:120)
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer, Integrations TG
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Gihan Anuruddha

[Ishara Premadasa]

Congratz Gihan!


On Tue, May 21, 2013 at 1:10 PM, Isuru Perera  wrote:

> Congratulations Gihan!
>
>
> On Tue, May 21, 2013 at 10:56 AM, Kasun Weranga  wrote:
>
>> Hi all,
>>
>> Its my pleasure to welcome Gihan Anuruddha as a WSO2 Committer. Gihan has
>> made some great contributions to BAM during the last few months and in
>> recognition of his commitment and contributions the All-MC has voted Gihan
>> as a committer.
>>
>> Gihan, welcome aboard and keep up the good work.
>>
>>
>> Thanks,
>> KasunW.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>
> Lean . Enterprise . Middleware
>
> Twitter: http://twitter.com/chrishantha | LinkedIn:
> http://lk.linkedin.com/in/chrishantha/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer, Integrations TG
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IS] Bad file descriptor error when parsing identity.xml - IS 3.2.3

[Ishara Premadasa]

Hi,

I was adding new configuration parameters into identity.xml in WSO2 IS
3.2.3 and once the server is restarted i got the following error.

*ERROR {org.wso2.carbon.identity.core.util.IdentityConfigParser} -  Error
while loading Identity Configurations
java.lang.RuntimeException: [was class java.io.IOException] Bad file
descriptor
at
com.ctc.wstx.util.ExceptionUtil.throwRuntimeException(ExceptionUtil.java:18)
at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:731)
at
com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3657)
at com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:809)
at
org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.getText(XMLStreamReaderWrapper.java:164)
at
org.apache.axiom.om.impl.builder.StAXBuilder.createOMText(StAXBuilder.java:289)
at
org.apache.axiom.om.impl.builder.StAXBuilder.createOMText(StAXBuilder.java:252)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:252)
at
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:336)
at
org.apache.axiom.om.impl.traverse.OMChildElementIterator.next(OMChildElementIterator.java:104)
at
org.wso2.carbon.identity.core.util.IdentityConfigParser.readChildElements(IdentityConfigParser.java:154)
at
org.wso2.carbon.identity.core.util.IdentityConfigParser.(IdentityConfigParser.java:60)
at
org.wso2.carbon.identity.core.util.IdentityConfigParser.getInstance(IdentityConfigParser.java:71)
at
org.wso2.carbon.identity.core.util.IdentityUtil.populateProperties(IdentityUtil.java:58)
at
org.wso2.carbon.identity.sso.saml.ui.internal.SAMLSSOUIBundleActivator.start(SAMLSSOUIBundleActivator.java:33)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
Caused by: java.io.IOException: Bad file descriptor
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:198)
at com.ctc.wstx.io.ISOLatinReader.read(ISOLatinReader.java:79)
at com.ctc.wstx.io.ReaderSource.readInto(ReaderSource.java:84)
at
com.ctc.wstx.io.BranchingReaderSource.readInto(BranchingReaderSource.java:57)
at
com.ctc.wstx.sr.StreamScanner.loadMoreFromCurrent(StreamScanner.java:1046)
at com.ctc.wstx.sr.StreamScanner.peekNext(StreamScanner.java:783)
at com.ctc.wstx.sr.StreamScanner.skipCRLF(StreamScanner.java:912)
at
com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.java:4644)
at
com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.java:4126)
at
com.ctc.wstx.sr.BasicStreamReader.finishToken(BasicStreamReader.java:3701)
at
com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3649)
*

After reading the following thread  [1] i could get this resolved by
removing few blank spaces from the identity.xml. Apart from doing that is
there a permanent fix available for this?

Thanks!
Ishara

[1] http://mail.wso2.org/mailarchive/dev/2012-June/006566.html

-- 
Ishara Premasada
Software Engineer, Integrations TG
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] Yahoo Place Finder sample returns 404 not found response with API Manager 1.3.1

[Ishara Premadasa]

Hi,

I was trying the Yahoo Place Finder sample in AM 1.3.1 as in [1] and when i
use

"curl -v -H "Authorization: Bearer dulSxgK5mNRPbQBA0XJVM1OwsGYa"
http://10.200.3.176:8280/placeFinder/1.0.0?q=Colombo"; command the following
is the response given.

* About to connect() to 10.200.3.176 port 8280 (#0)
*   Trying 10.200.3.176... connected
> GET /placeFinder/1.0.0?q=Colombo HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: 10.200.3.176:8280
> Accept: */*
> Authorization: Bearer dulSxgK5mNRPbQBA0XJVM1OwsGYa
>
< HTTP/1.1 404 Not Found
< Via: HTTP/1.1 r15.ycpi.sp2.yahoo.net UserFiberFramework/1.0
< Server: HTTP/1.1 UserFiberFramework/1.0
< Date: Fri, 10 May 2013 11:19:26 GMT
< Transfer-Encoding: chunked
<
* Connection #0 to host 10.200.3.176 left intact
* Closing connection #0


I have run the samples set up instructions before running the samples. Is
this an error in the sample or am i doing anything wrong here?

Thanks!
Ishara

[1]
http://docs.wso2.org/wiki/display/AM131/Access+Yahoo%27s+Place+Finder+Search+Using+an+API

-- 
Ishara Premasada
Software Engineer, Integrations TG
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Isuru Haththotuwa

[Ishara Premadasa]

Congrats  Isuru :)


On Thu, May 9, 2013 at 5:18 PM, Sajith Kariyawasam  wrote:

> Congratulations Isuru ..!
>
>
> On Thu, May 9, 2013 at 11:51 AM, Lakmal Warusawithana wrote:
>
>> Hi,
>>
>> Its my pleasure to welcome Isuru Haththotuwa as a WSO2 Commiter.
>>
>> IsuruH has done excellent contribution in the areas of
>> Stratos2 specially git based depSync. Also his contribution to Stratos2
>> alpha, beta1 and beta2 was tremendous.
>>
>> IsuruH, welcome aboard and keep up the good work.
>>
>> regards
>>
>> --
>> Lakmal Warusawithana
>> Software Architect; WSO2 Inc.
>> Mobile : +94714289692
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Sajith Kariyawasam*
> *Senior Software Engineer; WSO2, Inc.*
> *AMIE (SL)*
> *Blog: http://sajithblogs.blogspot.com/*
> *Mobile: +94772269575*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
Integration Technology Team,
WSO2 Inc. http://wso2.com/
*Linked in   :  http://www.linkedin.com/pub/ishara-premadasa/1a/630/609
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Fwd: SAML2 Web Browser based SSO with WSO2 IS demo webapp doesn't work with IS 4.1.0

[Ishara Premadasa]

Hi,

Forwarding this to dev-group as this should be sent there. Sorry for the
mistake.

-Ishara

-- Forwarded message --
From: Ishara Premadasa 
Date: Wed, May 8, 2013 at 9:49 AM
Subject: [Dev] SAML2 Web Browser based SSO with WSO2 IS demo webapp doesn't
work with IS 4.1.0
To: support-dev-group 


Hi,

I was testing SSO with WSO2 IS as described in [1] and it seems the demo
web app doesn't work as expected with IS 4.1.0 version. When i try to log
in to Identity Server via the webapp, after entering the credentials and
trying to sign in it throws the following error.

java.lang.NullPointerException

org.wso2.identity.saml2.demo.SamlConsumerManager.getResult(SamlConsumerManager.java:278)

org.wso2.identity.saml2.demo.SamlConsumerManager.processResponseMessage(SamlConsumerManager.java:252)

org.wso2.identity.saml2.demo.SAML2ConsumerServlet.doPost(SAML2ConsumerServlet.java:77)
javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
javax.servlet.http.HttpServlet.service(HttpServlet.java:728)

*note* *The full stack trace of the root cause is available in the Apache
Tomcat/7.0.39 logs.*

I debugged the source and this is given as the reason for the exception.

[Fatal Error] :1:1: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
at
org.wso2.identity.saml2.demo.SamlConsumerManager.unmarshall(SamlConsumerManager.java:265)
at
org.wso2.identity.saml2.demo.SamlConsumerManager.processResponseMessage(SamlConsumerManager.java:238)
at
org.wso2.identity.saml2.demo.SAML2ConsumerServlet.doPost(SAML2ConsumerServlet.java:77)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
at


The webapp works fine as expected with the IS 3.2.3 version. May be this is
due to some changes made in the 4.1.0 version.

Thanks!
Ishara

[1]
http://wso2.org/library/articles/2010/07/saml2-web-browser-based-sso-wso2-identity-server


-- 
Ishara Premasada
Software Engineer,
Integration Technology Team,
WSO2 Inc. http://wso2.com/
*Linked in   :  http://www.linkedin.com/pub/ishara-premadasa/1a/630/609
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*





-- 
Ishara Premasada
Software Engineer,
Integration Technology Team,
WSO2 Inc. http://wso2.com/
*Linked in   :  http://www.linkedin.com/pub/ishara-premadasa/1a/630/609
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] Purging a queue makes the queue disappear from queue list in MB admin console

[Ishara Premadasa]

Hi Hasitha,

Good to hear that this is fixed now. Can you please resolve [1] too.
Thanks!


[1] https://wso2.org/jira/browse/MB-156


On Tue, Apr 16, 2013 at 10:14 AM, Hasitha Hiranya  wrote:

> Hi Ishara,
>
> This was intentionally done at first. When there are no subscribers and
> queue has no messages it was removed from queue list as no resource from MB
> is consumed by that queue.
>
> Yes, it is not needed. If a queue is registered in virtualhost, that queue
> is there and ready to be used, thus it is wrong to remove queue in above
> way.
>
> Fixed and committed to 4.1.2 branch. Noe purging will not make the queue
> disappear.
>
> Thanks.
>
>
> On Mon, Apr 15, 2013 at 8:41 AM, Shammi Jayasinghe wrote:
>
>> Hi Ishara,
>>
>> We added the 'purge' operation for the queue to "delete all the messages
>> on queue"[1]. So we should not delete the queue once we do the purge
>> operation and we should fix that.
>>
>>
>> [1]http://activemq.apache.org/how-do-i-purge-a-queue.html
>> Thanks
>> Shammi
>>
>>
>> On Sat, Apr 13, 2013 at 9:10 AM, Ishara Premadasa wrote:
>>
>>> Hi all,
>>>
>>> I was testing the new 'queue purging' feature in MB admin console and it
>>> seems that when a queue is purged and all messages are received, the queue
>>> gets removed from the 'Queue List' page in the admin console. I suppose
>>> this is a bug in the feature as there is no need to remove the queue when
>>> it is empty. Before i try to get this fixed can i get clarified whether
>>> this is the expected behaviour or should we avoid this getting happened?
>>>
>>> Thanks!
>>> Ishara
>>>
>>> --
>>> Ishara Premasada
>>> Software Engineer,
>>> Integration Technology Team,
>>> WSO2 Inc. http://wso2.com/
>>> *Linked in   :  http://www.linkedin.com/pub/ishara-premadasa/1a/630/609
>>> Twitter   :  https://twitter.com/ishadil
>>> Mobile   : +94 714445832*
>>>
>>>
>>>
>>
>>
>> --
>> Best Regards,*
>>
>> Shammi Jayasinghe*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
>> mobile: +94 71 4493085
>>
>>
>
>
> --
> *Hasitha Abeykoon*
>
> Software Engineer; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>* *
> *
> *
>



-- 
Ishara Premasada
Software Engineer,
Integration Technology Team,
WSO2 Inc. http://wso2.com/
*Linked in   :  http://www.linkedin.com/pub/ishara-premadasa/1a/630/609
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Testing and Bug Fixing for WSO2 Message Broker 2.1.0 Beta Release

[Ishara Premadasa]

Hi Hasitha,

Does [1] occurs in the queue purging? Because when i was testing the queue
purging, a similar scenario happens sometimes where the message count gets
into minus numbers.

If [1] it is not with purging, we will have to fix the same scenario with
purging too. I suspect that this is due to the synchronous nature of queue
receiving we use. May be we should try on adding a asynchronous message
receiver for purging?

Also when testing the new UI features we added, found [13] as a bug too.
Please note it  into bug fixing list (if it is concerned as a bug).

[13]. https://wso2.org/jira/browse/MB-156

Thanks!


On Fri, Apr 12, 2013 at 5:41 PM, Hasitha Hiranya  wrote:

> Hi Shammi/Ishara,
>
> It was great that we did a lot of bug fixing, improvements and also
> several new feature developments for WSO2 MB Alpha release we did last
> Friday.
>
> As we have planned, Beta release is going to be next Friday (19 th April).
>
> I have tested the alpha pack according to the "MB Testing Document" 
> here<https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0Ap7HoxWKqqNndFhGempQVTY1WU5rcHZLSGI0aEQwNHc#gid=0>,
> and found several issues we have to address before releasing the beta pack,
> and I have created Jiras to track those issues.
>
> Out of these, Issue [1] will be a blocker for us. Others I have put in
> high priority and issue [6] in highest priority (as of a message loss).
>
> Tests have been conducted under following areas:
>
>- Product based tests
>- Clustering related testing
>- UI testing
>- Integration with other products
>
>
> [1]. https://wso2.org/jira/browse/MB-146
> [2]. https://wso2.org/jira/browse/MB-147
> [3]. https://wso2.org/jira/browse/MB-148
> [4]. https://wso2.org/jira/browse/MB-149
> [5]. https://wso2.org/jira/browse/MB-150
> [6]. https://wso2.org/jira/browse/MB-151
> [7]. https://wso2.org/jira/browse/MB-152
> [8]. https://wso2.org/jira/browse/MB-153
> [9]. https://wso2.org/jira/browse/MB-154
> [10]. https://wso2.org/jira/browse/MB-142 (from Ishara)
> [11]. https://wso2.org/jira/browse/MB-155
> [12]. https://wso2.org/jira/browse/ESBJAVA-1874 (this is an ESB side
> issue)
>
> In order to make MB bug free I believe more testing and bug-fixing has to
> be conducted. I could complete only about 2/3 section of whole testing
> space in "Testing document".
>
> I am beginning to doubt with team's resource capacity will it be an
> achievable target to release Beta pack by Friday with all testing and all
> bug fixing done.
>
> Thanks.
>
> --
> *Hasitha Abeykoon*
> Software Engineer; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>* *
> *
> *
>



-- 
Ishara Premasada
Software Engineer,
Integration Technology Team,
WSO2 Inc. http://wso2.com/
*Linked in   :  http://www.linkedin.com/pub/ishara-premadasa/1a/630/609
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [MB] Purging a queue makes the queue disappear from queue list in MB admin console

[Ishara Premadasa]

Hi all,

I was testing the new 'queue purging' feature in MB admin console and it
seems that when a queue is purged and all messages are received, the queue
gets removed from the 'Queue List' page in the admin console. I suppose
this is a bug in the feature as there is no need to remove the queue when
it is empty. Before i try to get this fixed can i get clarified whether
this is the expected behaviour or should we avoid this getting happened?

Thanks!
Ishara

-- 
Ishara Premasada
Software Engineer,
Integration Technology Team,
WSO2 Inc. http://wso2.com/
*Linked in   :  http://www.linkedin.com/pub/ishara-premadasa/1a/630/609
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Providing queue browser support in WSO2 MB admin console

[Ishara Premadasa]

Hi Hasitha,

Noted this.  I created [1] for this bug and will attach the patch there
once this is fixed.
Thanks!

[1] https://wso2.org/jira/browse/MB-142


On Thu, Apr 4, 2013 at 11:49 AM, Hasitha Hiranya  wrote:

> Hi Ishara,
>
> Detected some issue in queue browser UI when MB server is started with an
> offset.
> When the server is started with an offset UI client tries to connect to
> the server running in default port.
> Instead what needs to be done is find the port defined using Carbon
> Environment and always connect to it.
>
> :
>
> Thanks.
>
>
>
> On Tue, Apr 2, 2013 at 11:23 PM, Sagara Gunathunga wrote:
>
>>
>>
>>
>> On Tue, Apr 2, 2013 at 11:20 PM, Hasitha Hiranya wrote:
>>
>>> Hi,
>>>
>>> It is nice to have feed-backs.
>>>
>>> 1. As Ishara says, "tryit" feature will be available with "MB 2.1.0"
>>> release.
>>>  2. Message deletion will be nice to have. But JMS spec does not mention
>>> about deleting messages. When you get messages from queue with "AUTO ACK"
>>> mode messages will be auto deleted. BTW, Websphere MQ support that feature
>>> (selective delete) by their implementation. We will consider on adding that
>>> feature for MB 3.0.0.
>>>
>>
>>  +1 ActiveMQ also support message deletion through it's web console.
>>
>> Thanks !
>>
>>>
>>> Thanks.
>>>
>>>
>>>
>>>
>>> On Tue, Apr 2, 2013 at 10:55 PM, Sagara Gunathunga wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Tue, Apr 2, 2013 at 10:53 PM, Ishara Premadasa wrote:
>>>>
>>>>> Hi Sagara,
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Apr 2, 2013 at 10:43 PM, Sagara Gunathunga wrote:
>>>>>
>>>>>>
>>>>>> Hi Ishara/Shammi,
>>>>>>
>>>>>> This is really cool addition ! As a MB user I also have list of
>>>>>> feature requests for web console :)
>>>>>>
>>>>>> 1.) Practically I have felt many time if we could have web based
>>>>>> sender ( or Try-It) feature with MB. This means there should be web
>>>>>> interface to send  messages to a destination without creating any JMS
>>>>>> client, it just a filling a HTML page with required data. ActiveMQ 
>>>>>> provide
>>>>>> such a web interface[1] and very useful too. As an example take a look at
>>>>>> this post[2] how I used ActiveMQ console to test Axis2 JMS transport
>>>>>> without writing any client side code. In my POV we need to have similar 
>>>>>> but
>>>>>> better Try-It or sender feature for MB.
>>>>>>
>>>>>
>>>>>
>>>>> Thank you very much for these suggestions. Actually our next task is
>>>>> adding a 'Test Message Sending' feature for MB admin console[1]. As 
>>>>> exactly
>>>>> you had mentioned, we hope to provide the ability to send a sample JMS
>>>>> message with setting the necessary parameters like in ActiveMQ. Hope to
>>>>> start this soon ASAP once we finalize the queue browser.
>>>>>
>>>>
>>>>  Great ! Nice to hear that.
>>>>
>>>>
>>>>>
>>>>>> 2.) I believe we can provide following details per topic, WDYT ?
>>>>>>
>>>>>> Name
>>>>>> Number Of Consumers
>>>>>> Messages Enqueued
>>>>>> Messages Dequeued
>>>>>>
>>>>>> 3.) It's better to have some XML indention on "message content" view.
>>>>>>
>>>>>
>>>>>
>>>>> Yes, the current message content view doesn't show the XML indentions
>>>>> properly when a user sends XML as content. I will try to fix this and get
>>>>> the proper indentation view.
>>>>>
>>>>> Thanks!
>>>>>
>>>>>
>>>>> [1] https://wso2.org/jira/browse/MB-139
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> [1] -
>>>>>> http://1.bp.blogspot.com/-dEQzkDJKOiE/T5LBe5xgneI/AJ4/qX1nr58yWJk/s1600/1.png
>>>>>> [2] -
>>>>>> http://ssagara.blogspot.com/2012/04/axis2-jm

Re: [Dev] Carbon - Component - Andes UI - Build Failure

[Ishara Premadasa]

Hi Nuwan,

This is due to the 'commons-lang-2.6' dependency is not updated into pom
file of org.wso2.carbon.andes.ui. Hasitha will be committing it back soon.



On Wed, Apr 3, 2013 at 8:37 AM, Nuwan Dias  wrote:

> Hi,
>
> I am getting the following build failure when building
> patch-releases/4.1.2/components.
>
> [INFO] WSO2 Carbon - Component - Andes UI  FAILURE [4.968s]
> [INFO] WSO2 Carbon - Patch releases - components - Aggregator Module
>  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 1:06.379s
> [INFO] Finished at: Tue Apr 02 20:07:53 PDT 2013
> [INFO] Final Memory: 483M/1679M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.andes.ui: Compilation failure:
> Compilation failure:
> [ERROR]
> /home/wso2/4.1.0/platform/4.1.0/components/andes/org.wso2.carbon.andes.ui/4.1.2/src/main/java/org/wso2/carbon/andes/ui/client/QueueBrowserClient.java:[20,30]
> package org.apache.commons.lang does not exist
> [ERROR]
> /home/wso2/4.1.0/platform/4.1.0/components/andes/org.wso2.carbon.andes.ui/4.1.2/src/main/java/org/wso2/carbon/andes/ui/client/QueueBrowserClient.java:[165,23]
> cannot find symbol
> [ERROR] symbol  : variable StringEscapeUtils
> [ERROR] location: class org.wso2.carbon.andes.ui.client.QueueBrowserClient
> [ERROR]
> /home/wso2/4.1.0/platform/4.1.0/components/andes/org.wso2.carbon.andes.ui/4.1.2/src/main/java/org/wso2/carbon/andes/ui/client/QueueBrowserClient.java:[187,27]
> cannot find symbol
> [ERROR] symbol  : variable StringEscapeUtils
> [ERROR] location: class org.wso2.carbon.andes.ui.client.QueueBrowserClient
> [ERROR]
> /home/wso2/4.1.0/platform/4.1.0/components/andes/org.wso2.carbon.andes.ui/4.1.2/src/main/java/org/wso2/carbon/andes/ui/client/QueueBrowserClient.java:[279,15]
> cannot find symbol
> [ERROR] symbol  : variable StringEscapeUtils
> [ERROR] location: class org.wso2.carbon.andes.ui.client.QueueBrowserClient
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :org.wso2.carbon.andes.ui
>
> Thanks,
> --
> Nuwan Dias
>
> Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
Integration Technology Team,
WSO2 Inc. http://wso2.com/
*Linked in   :  http://www.linkedin.com/pub/ishara-premadasa/1a/630/609
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Providing queue browser support in WSO2 MB admin console

[Ishara Premadasa]

Hi Sagara,




On Tue, Apr 2, 2013 at 10:43 PM, Sagara Gunathunga  wrote:

>
> Hi Ishara/Shammi,
>
> This is really cool addition ! As a MB user I also have list of feature
> requests for web console :)
>
> 1.) Practically I have felt many time if we could have web based sender (
> or Try-It) feature with MB. This means there should be web interface to
> send  messages to a destination without creating any JMS client, it just a
> filling a HTML page with required data. ActiveMQ provide such a web
> interface[1] and very useful too. As an example take a look at this post[2]
> how I used ActiveMQ console to test Axis2 JMS transport without writing any
> client side code. In my POV we need to have similar but better Try-It or
> sender feature for MB.
>


Thank you very much for these suggestions. Actually our next task is adding
a 'Test Message Sending' feature for MB admin console[1]. As exactly you
had mentioned, we hope to provide the ability to send a sample JMS message
with setting the necessary parameters like in ActiveMQ. Hope to start this
soon ASAP once we finalize the queue browser.

>
> 2.) I believe we can provide following details per topic, WDYT ?
>
> Name
> Number Of Consumers
> Messages Enqueued
> Messages Dequeued
>
> 3.) It's better to have some XML indention on "message content" view.
>


Yes, the current message content view doesn't show the XML indentions
properly when a user sends XML as content. I will try to fix this and get
the proper indentation view.

Thanks!


[1] https://wso2.org/jira/browse/MB-139




> [1] -
> http://1.bp.blogspot.com/-dEQzkDJKOiE/T5LBe5xgneI/AJ4/qX1nr58yWJk/s1600/1.png
> [2] -
> http://ssagara.blogspot.com/2012/04/axis2-jms-transport-and-activemq.html
>
>
> Thanks !
>
>
>
> On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa  wrote:
>
>> Hi,
>>
>> This is an update on  Feature#1207 [1], adding queue browsing ability
>> into MB. The following is the final outcome of the feature implementation
>> and this will be released with the upcoming MB 2.1.0 release.
>>
>> With queue browsing the user is capable of viewing the JMS Messages'
>> details inside particular queue, including message attributes, properties,
>> content type etc. and in addition the complete message body content can be
>> viewed for each message as shown in the screen shots attached below.
>>
>> Due to the performance concerns there will be a maximum message limit of
>> 200, that is displayed in the queue browser UI, even though the given queue
>> may have a larger amount of messages.  At the moment this can be configured
>> in the qpid_config.xml if necessary (explained in the documentation).
>>
>> However I would like to know that whether we should allow this is to be
>> configured into a higher amount as there is a possibility of crashing, when
>> loading a big amount of messages into memory.
>>
>> The MB 2.1.0 documentation is updated too [2].
>>
>> Thanks!
>> Ishara
>>
>> [1] https://redmine.wso2.com/issues/1207
>> [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues
>>
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> Integration Technology Team,
>> WSO2 Inc. http://wso2.com/
>> *Linked in   :  http://www.linkedin.com/pub/ishara-premadasa/1a/630/609
>> Twitter   :  https://twitter.com/ishadil
>> Mobile   : +94 714445832*
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sagara Gunathunga
>
> Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Blog ;  http://ssagara.blogspot.com
> Linkedin; http://www.linkedin.com/in/ssagara
>



-- 
Ishara Premasada
Software Engineer,
Integration Technology Team,
WSO2 Inc. http://wso2.com/
*Linked in   :  http://www.linkedin.com/pub/ishara-premadasa/1a/630/609
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Providing queue browser support in WSO2 MB admin console

[Ishara Premadasa]

Hi Nirmal,


On Tue, Apr 2, 2013 at 6:37 PM, Nirmal Fernando  wrote:

> Hi Ishara,
>
> This will be a very useful feature for MB.
>
>
> On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa  wrote:
>
>> Hi,
>>
>> This is an update on  Feature#1207 [1], adding queue browsing ability
>> into MB. The following is the final outcome of the feature implementation
>> and this will be released with the upcoming MB 2.1.0 release.
>>
>> With queue browsing the user is capable of viewing the JMS Messages'
>> details inside particular queue, including message attributes, properties,
>> content type etc. and in addition the complete message body content can be
>> viewed for each message as shown in the screen shots attached below.
>>
>
> However, as a topic browser, I'd love to see following information too.
>
> * Publisher's IP/port
> * Subscribers' IP/port, and the subscribers whom not yet received the
> message.
> * Message size
>


Actually we are working on providing more features support for the MB admin
console with the new release. However about a Topic browser, as i
understand you can't browse the messages in a topic because they are sent
to all subscribers immediately and don't get stored on the broker storage,
unlike a queue where the messages are stored when receiver is offline.
Therefore i don't think that we are able to get the message content
published for a topic. May be Shammi or Hasitha can correct me if  i am
wrong :)


>
>
> Also, what is 'delivery mode' attribute? Is it something I configure? Is
> it possible to use the meaningful string interpretation instead of an
> integer?
>


According to the JMS spec 'delivery mode' is  for marking the message as
PERSISTENT or NON_PERSISTENT [1]. By default JMS  messages are made
persistent ( stored in persistent storage to be delivered later if needed).
The only accepted values are 1 and 2;

1- Non persistent
2- Persistent

Hence we can't use any other value for this attribute when sending a
message.

>
>
>>
>> Due to the performance concerns there will be a maximum message limit of
>> 200, that is displayed in the queue browser UI, even though the given queue
>> may have a larger amount of messages.  At the moment this can be configured
>> in the qpid_config.xml if necessary (explained in the documentation).
>>
>> However I would like to know that whether we should allow this is to be
>> configured into a higher amount as there is a possibility of crashing, when
>> loading a big amount of messages into memory.
>>
>
> MB uses Cassandra, right? Isn't it the right place to store data instead
> of memory?
>


Yes the messages are in the storage. But the queue browser returns an
enumeration of the content of a queue [2], in runtime, and if there are
larger amount of messages in the queue (say 100,000) the enumeration loads
this entire content into memory. This makes the server crashes. By default
there are only 200 messages fetched, however if the user increases this
value a lot, it fails. I think Hasitha is going to update the configuration
documentation with proper 'Warnings' about these outcomes.

Ishara

[1] http://docs.oracle.com/javaee/6/api/javax/jms/DeliveryMode.html
[2]
http://docs.oracle.com/javaee/1.4/api/javax/jms/QueueBrowser.html#getEnumeration%28%29




>
>>
>> The MB 2.1.0 documentation is updated too [2].
>>
>> Thanks!
>> Ishara
>>
>> [1] https://redmine.wso2.com/issues/1207
>> [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues
>>
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> Integration Technology Team,
>> WSO2 Inc. http://wso2.com/
>> *Linked in   :  http://www.linkedin.com/pub/ishara-premadasa/1a/630/609
>> Twitter   :  https://twitter.com/ishadil
>> Mobile   : +94 714445832*
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
> <http://nirmalfdo.blogspot.com/>
>



-- 
Ishara Premasada
Software Engineer,
Integration Technology Team,
WSO2 Inc. http://wso2.com/
*Linked in   :  http://www.linkedin.com/pub/ishara-premadasa/1a/630/609
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev