Re: [Dev] Need a jaagery release for latest Carbon 4.3.0 products.

[Madhuka Udantha]

Hi,

'jaggery-0.9.0.ALPHA5.wso2v1' jaggery version[1] can be used for $subject.
Above jaggery version is using kernel 4.3.0

[1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0


On Fri, Feb 28, 2014 at 1:02 PM, Geeth Munasinghe  wrote:

> Hi
>
> We need to have a jaggery release from carbon kernal 4.3.0 to ship with
> Application Server 5.3.0.  New AS will be released on end of Q1. Latest
> jaggery release (version - 0.9.0.ALPHA4.wso2v3) is done on kernal 4.2.0
> branch.
>
> Thanks
> Geeth
>
>
>
> *G. K. S. Munasinghe*
> *Software Engineer,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226
>



-- 
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com

*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Data Services Server 3.2.0-M1 Released

[Chanika Geeganage]

*WSO2 Data Services Server 3.2.0-M1 Released!*


The Milestone-1 pack is available at:
http://svn.wso2.org/repos/wso2/people/chanika/DSS_3.2.0_M1/

To run the samples please follow the read-me, $DSS_HOME/samples/README.txt

Following are the bug fixes, improvements and the new features.

Bug

   - [DS-801 ] - Task Scheduling on
   task type based in a clustered setup
   - [DS-846 ] - DSS Batch Requests
   are failing when DTP is enabled
   - [DS-851 ] - Turn on content
   negotiation by default in axis2.xml
   - [DS-854 ] - Adding JNDI
   datasource ui password field is missing
   - [DS-856 ] - CLOB type does not
   appear in the input parameter list
   - [DS-858 ] - Fixing Round Robbin
   based Location Resolver

Improvement

   - [DS-844 ] - Resource Dispatching
   for Multiple parameters with the same base URL
   - [DS-855 ] - Data Services
   Streaming Improvements

New Feature

   - [DS-859 ] - Native JSON support

We welcome your feedback on this release of DSS.

Thanks
- WSO2 DSS Team -

-- 
Best Regards..

Chanika Geeganage
Software Engineer
WSO2, Inc.; http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Proposal to move admin service clients in test automation framework into relevant service stubs

[Krishantha Samaraweera]

Hi all,

I would like to propose $subject. The test automation framework heavily
depends on admin service clients which use service-stubs to invoke backend
admin services. This approach will by-pass the management UI and call the
backend web services directly. Maintaining set of Admin service clients
inside test automation framework has it's own pros and cons.

The main problems is maintenance overhead. There were incidents that
service API has changed and no one build the branch up to test framework
level before the commit. So this introduced compilation failures in test
framework API. With our new git based repository model, eliminating this
kind of mistakes are required to scale fast. Moving these clients to
service-stub level guarantee to detect any compilation failures at
repository level. Since the framework support for platform level test
automation, all most all service-stubs were taken as dependencies to test
framework API. This will introduce many drawbacks when it comes to single
product release.

Moving admin services clients will improve test-ability and provide user
friendly way for product users to consume admin services. Also this will
eliminate necessity of releasing all service stubs at the time of
automation framework release (in initial phase)

Please let me know your suggestions?

Thanks,
Krishantha.

-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 API Manager 1.6.0 - Thrift port is not affected by offset?

[Isuru Perera]

Hi,

$subject.

Cannot run two API Manager 1.6.0 instances in the same server with
different port offsets.

Is this a known issue?

Best Regards,

-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

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

[Dev] Can't Start wso2server.sh as root

[Chamila Wijayarathna]

Hi all,
I tried to run "./wso2server.sh start" from /bin after logging as
root.
When I ran this command it says "ps: write error: Bad file descriptor".
What is the reason for this? How can I solve this?

Thank You!

-- 
*Chamila Wijayarathna*
Engineering Intern,
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 API Manager 1.6.0 - Thrift port is not affected by offset?

[Nuwan Dias]

Yes, this is known. This has been discussed before and the decision was to
leave it as it is.

The reason in summary is, the Thrift server port is something external and
offsetting a Thrift server port with a carbon offset causes a lot more
confusions when setting up a distributed deployment. (i.e. thrift client
port should also offset with the same value as the server port, etc).

Thanks,
NuwanD.


On Mon, Mar 3, 2014 at 6:23 PM, Isuru Perera  wrote:

> Hi,
>
> $subject.
>
> Cannot run two API Manager 1.6.0 instances in the same server with
> different port offsets.
>
> Is this a known issue?
>
> Best Regards,
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Dias

Senior 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

[Dev] GSoC 2014

[Paramsothy Sanshayan]

Hi

I am Sanchayan , fourth year student studying Computer Engineering in
Faculty of Engineering University of Peradeniya, Srilanka.
and I would like to start contributing towards GSoC project  'Android
Display viewer for PDF, Doc, Excel files' and this idea is very
interesting, and I have also work with Android technologies.


How to contact this project mentor to discuss about contributing and  ideas

Any kind of guidance from mentors related to this project would be greatly
appreciated.Hope to hear a positive reply.

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

Re: [Dev] GSoC 2014

[Nirmal Fernando]

Hi Sanchayan,

Glad to hear that you are interested in the mentioned project. Here I am
adding set of people to the thread, from whom you can get better
understanding of the project.



On Mon, Mar 3, 2014 at 6:36 PM, Paramsothy Sanshayan wrote:

> Hi
>
> I am Sanchayan , fourth year student studying Computer Engineering in
> Faculty of Engineering University of Peradeniya, Srilanka.
> and I would like to start contributing towards GSoC project  'Android
> Display viewer for PDF, Doc, Excel files' and this idea is very
> interesting, and I have also work with Android technologies.
>
>
> How to contact this project mentor to discuss about contributing and  ideas
>
> Any kind of guidance from mentors related to this project would be greatly
> appreciated.Hope to hear a positive reply.
>
> Regards
> Sanchayan
>
> ___
> 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

Re: [Dev] Can't Start wso2server.sh as root

[Isuru Perera]

AFAIK, this is a known issue for some platforms and I reported a JIRA
sometime back [1].

However, the server should work fine.

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


On Mon, Mar 3, 2014 at 6:29 PM, Chamila Wijayarathna wrote:

> Hi all,
> I tried to run "./wso2server.sh start" from /bin after logging
> as root.
> When I ran this command it says "ps: write error: Bad file descriptor".
> What is the reason for this? How can I solve this?
>
> Thank You!
>
> --
> *Chamila Wijayarathna*
> Engineering Intern,
> WSO2 Inc.
>
>
> ___
> 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

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

Re: [Dev] Can't Start wso2server.sh as root

[Isuru Perera]

I have mentioned in the JIRA that I get that error in the second time.
However there are cases, which you will get this error in the first time
and always.

Perhaps you can add a comment to the JIRA.

Thanks!


On Mon, Mar 3, 2014 at 6:44 PM, Isuru Perera  wrote:

> AFAIK, this is a known issue for some platforms and I reported a JIRA
> sometime back [1].
>
> However, the server should work fine.
>
> [1] https://wso2.org/jira/browse/CARBON-14477
>
>
> On Mon, Mar 3, 2014 at 6:29 PM, Chamila Wijayarathna wrote:
>
>> Hi all,
>> I tried to run "./wso2server.sh start" from /bin after logging
>> as root.
>> When I ran this command it says "ps: write error: Bad file descriptor".
>> What is the reason for this? How can I solve this?
>>
>> Thank You!
>>
>> --
>> *Chamila Wijayarathna*
>> Engineering Intern,
>> WSO2 Inc.
>>
>>
>> ___
>> 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
>
> about.me/chrishantha
>



-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

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

[Dev] java.lang.OutOfMemoryError: GC overhead limit exceeded observed for ESB message store and forward scenario in MB Cluster Environment

[Iranga Muthuthanthri]

Hi All.

Following was noted in testing for 100,00 messages for the ESB (4.8.1)
message store and forward scenario in a MB 2.1.0 cluster environment.

*Issue*:Out of memory exception noted in ESB console.

[2014-03-03 04:37:36,065] ERROR - JmsStore Could not create a Message
Producer for Store [MessageStoreO1]. Error:GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.util.Arrays.copyOfRange(Arrays.java:3209)
at java.lang.String.(String.java:215)
at java.lang.StringBuilder.toString(StringBuilder.java:430)
at java.lang.Object.toString(Object.java:219)
at
org.wso2.andes.client.BasicMessageProducer.setPublishMode(BasicMessageProducer.java:167)
at
org.wso2.andes.client.BasicMessageProducer.(BasicMessageProducer.java:148)
at
org.wso2.andes.client.BasicMessageProducer_0_8.(BasicMessageProducer_0_8.java:51)
at
org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:411)
at
org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:82)
at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2632)
at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2627)
at
org.wso2.andes.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:315)
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.createProducerImpl(AMQSession.java:2625)
at org.wso2.andes.client.AMQSession.createProducerImpl(AMQSession.java:2619)
at org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:1231)
at org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:109)
at
org.apache.synapse.message.store.impl.jms.JmsStore.newProducer(JmsStore.java:346)
at
org.apache.synapse.message.store.impl.jms.JmsStore.getProducer(JmsStore.java:136)
at
org.apache.synapse.mediators.store.MessageStoreMediator.mediate(MessageStoreMediator.java:84)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
at
org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)


Issue details can be found on:https://wso2.org/jira/browse/ESBJAVA-3024



-- 
Thanks & Regards

Iranga Muthuthanthri
Technical Lead - QA
(M) -0777-255773
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] java.lang.OutOfMemoryError: GC overhead limit exceeded observed for ESB message store and forward scenario in MB Cluster Environment

[Udara Liyanage]

I saw a similar issue occurred in BAM. Have a look mail thread subjected "
[Dev] [BAM] java.lang.OutOfMemoryError: GC overhead limit exceeded"

Touched, not typed. Erroneous words are a feature, not a typo.
On Mar 3, 2014 6:57 PM, "Iranga Muthuthanthri"  wrote:

> Hi All.
>
> Following was noted in testing for 100,00 messages for the ESB (4.8.1)
> message store and forward scenario in a MB 2.1.0 cluster environment.
>
> *Issue*:Out of memory exception noted in ESB console.
>
> [2014-03-03 04:37:36,065] ERROR - JmsStore Could not create a Message
> Producer for Store [MessageStoreO1]. Error:GC overhead limit exceeded
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.util.Arrays.copyOfRange(Arrays.java:3209)
> at java.lang.String.(String.java:215)
>  at java.lang.StringBuilder.toString(StringBuilder.java:430)
> at java.lang.Object.toString(Object.java:219)
>  at
> org.wso2.andes.client.BasicMessageProducer.setPublishMode(BasicMessageProducer.java:167)
> at
> org.wso2.andes.client.BasicMessageProducer.(BasicMessageProducer.java:148)
>  at
> org.wso2.andes.client.BasicMessageProducer_0_8.(BasicMessageProducer_0_8.java:51)
> at
> org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:411)
>  at
> org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:82)
> at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2632)
>  at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2627)
> at
> org.wso2.andes.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:315)
>  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.createProducerImpl(AMQSession.java:2625)
> at
> org.wso2.andes.client.AMQSession.createProducerImpl(AMQSession.java:2619)
>  at org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:1231)
> at org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:109)
>  at
> org.apache.synapse.message.store.impl.jms.JmsStore.newProducer(JmsStore.java:346)
> at
> org.apache.synapse.message.store.impl.jms.JmsStore.getProducer(JmsStore.java:136)
>  at
> org.apache.synapse.mediators.store.MessageStoreMediator.mediate(MessageStoreMediator.java:84)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
>  at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
> at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
>  at
> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>  at
> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
> at
> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
>  at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
>
>
> Issue details can be found on:https://wso2.org/jira/browse/ESBJAVA-3024
>
>
>
> --
> Thanks & Regards
>
> Iranga Muthuthanthri
> Technical Lead - QA
> (M) -0777-255773
>
> ___
> 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] Proposal to move admin service clients in test automation framework into relevant service stubs

[Sagara Gunathunga]

On Mon, Mar 3, 2014 at 6:10 PM, Krishantha Samaraweera
wrote:

> Hi all,
>
> I would like to propose $subject. The test automation framework heavily
> depends on admin service clients which use service-stubs to invoke backend
> admin services. This approach will by-pass the management UI and call the
> backend web services directly. Maintaining set of Admin service clients
> inside test automation framework has it's own pros and cons.
>
> The main problems is maintenance overhead. There were incidents that
> service API has changed and no one build the branch up to test framework
> level before the commit. So this introduced compilation failures in test
> framework API. With our new git based repository model, eliminating this
> kind of mistakes are required to scale fast. Moving these clients to
> service-stub level guarantee to detect any compilation failures at
> repository level. Since the framework support for platform level test
> automation, all most all service-stubs were taken as dependencies to test
> framework API. This will introduce many drawbacks when it comes to single
> product release.
>
> Moving admin services clients will improve test-ability and provide user
> friendly way for product users to consume admin services. Also this will
> eliminate necessity of releasing all service stubs at the time of
> automation framework release (in initial phase)
>
> Please let me know your suggestions?
>

+1

I assume after moving these clients in to underline stub modules particular
team is responsible for maintenance. IMHO to make it more practical we
should add process so that when introducing a new stub there should be a
new service client as well WDYT ?

During the initial stage it would be better automation team can distribute
existing service clients into among platform projects to keep consistency.

Thanks !

>
> Thanks,
> Krishantha.
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>



-- 
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

Re: [Dev] Can't Start wso2server.sh as root

[Udara Rathnayake]

Hi,

Try updating "ps -p $PID >&- ; then" command in to "if ps -p $PID >
/dev/null ; then", not sure this is the exact solution for this.
Normally you get Bad file descriptor type errors due to non availability of
stdin,stdout or stderr for given command.

Regards,
UdaraR


On Mon, Mar 3, 2014 at 6:45 PM, Isuru Perera  wrote:

> I have mentioned in the JIRA that I get that error in the second time.
> However there are cases, which you will get this error in the first time
> and always.
>
> Perhaps you can add a comment to the JIRA.
>
> Thanks!
>
>
> On Mon, Mar 3, 2014 at 6:44 PM, Isuru Perera  wrote:
>
>> AFAIK, this is a known issue for some platforms and I reported a JIRA
>> sometime back [1].
>>
>> However, the server should work fine.
>>
>> [1] https://wso2.org/jira/browse/CARBON-14477
>>
>>
>> On Mon, Mar 3, 2014 at 6:29 PM, Chamila Wijayarathna wrote:
>>
>>> Hi all,
>>> I tried to run "./wso2server.sh start" from /bin after logging
>>> as root.
>>> When I ran this command it says "ps: write error: Bad file descriptor".
>>> What is the reason for this? How can I solve this?
>>>
>>> Thank You!
>>>
>>> --
>>> *Chamila Wijayarathna*
>>> Engineering Intern,
>>> WSO2 Inc.
>>>
>>>
>>> ___
>>> 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
>>
>> about.me/chrishantha
>>
>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Udara Rathnayake*
Software Engineer
WSO2 Inc. : http://wso2.com

Mobile : +94 772207239
Twitter : http://twitter.com/udarakr
Blog: http://udarakr.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Proposal to move admin service clients in test automation framework into relevant service stubs

[Krishantha Samaraweera]

On Mon, Mar 3, 2014 at 9:55 PM, Sagara Gunathunga  wrote:

>
>
>
> On Mon, Mar 3, 2014 at 6:10 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi all,
>>
>> I would like to propose $subject. The test automation framework heavily
>> depends on admin service clients which use service-stubs to invoke backend
>> admin services. This approach will by-pass the management UI and call the
>> backend web services directly. Maintaining set of Admin service clients
>> inside test automation framework has it's own pros and cons.
>>
>> The main problems is maintenance overhead. There were incidents that
>> service API has changed and no one build the branch up to test framework
>> level before the commit. So this introduced compilation failures in test
>> framework API. With our new git based repository model, eliminating this
>> kind of mistakes are required to scale fast. Moving these clients to
>> service-stub level guarantee to detect any compilation failures at
>> repository level. Since the framework support for platform level test
>> automation, all most all service-stubs were taken as dependencies to test
>> framework API. This will introduce many drawbacks when it comes to single
>> product release.
>>
>> Moving admin services clients will improve test-ability and provide user
>> friendly way for product users to consume admin services. Also this will
>> eliminate necessity of releasing all service stubs at the time of
>> automation framework release (in initial phase)
>>
>> Please let me know your suggestions?
>>
>
> +1
>
> I assume after moving these clients in to underline stub modules
> particular team is responsible for maintenance. IMHO to make it more
> practical we should add process so that when introducing a new stub there
> should be a new service client as well WDYT ?
>
> During the initial stage it would be better automation team can distribute
> existing service clients into among platform projects to keep consistency.
>

Automation team can own initial distribution of Service clients among
service-stub modules.

Thanks,
Krishantha.


> Thanks !
>
>>
>> Thanks,
>> Krishantha.
>>
>> --
>> Krishantha Samaraweera
>> Senior Technical Lead - Test Automation
>> Mobile: +94 77 7759918
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middlewear.
>>
>
>
>
> --
> 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
>
>


-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] java.lang.OutOfMemoryError: GC overhead limit exceeded observed for ESB message store and forward scenario in MB Cluster Environment

[Iranga Muthuthanthri]

Thanks Udara. Checked it before and the stack trace was different.The
culprit in this case appears to from the andes client.
On Mar 3, 2014 9:25 PM, "Udara Liyanage"  wrote:

> I saw a similar issue occurred in BAM. Have a look mail thread subjected "
> [Dev] [BAM] java.lang.OutOfMemoryError: GC overhead limit exceeded"
>
> Touched, not typed. Erroneous words are a feature, not a typo.
> On Mar 3, 2014 6:57 PM, "Iranga Muthuthanthri"  wrote:
>
>> Hi All.
>>
>> Following was noted in testing for 100,00 messages for the ESB (4.8.1)
>> message store and forward scenario in a MB 2.1.0 cluster environment.
>>
>> *Issue*:Out of memory exception noted in ESB console.
>>
>> [2014-03-03 04:37:36,065] ERROR - JmsStore Could not create a Message
>> Producer for Store [MessageStoreO1]. Error:GC overhead limit exceeded
>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>> at java.util.Arrays.copyOfRange(Arrays.java:3209)
>> at java.lang.String.(String.java:215)
>>  at java.lang.StringBuilder.toString(StringBuilder.java:430)
>> at java.lang.Object.toString(Object.java:219)
>>  at
>> org.wso2.andes.client.BasicMessageProducer.setPublishMode(BasicMessageProducer.java:167)
>> at
>> org.wso2.andes.client.BasicMessageProducer.(BasicMessageProducer.java:148)
>>  at
>> org.wso2.andes.client.BasicMessageProducer_0_8.(BasicMessageProducer_0_8.java:51)
>> at
>> org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:411)
>>  at
>> org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:82)
>> at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2632)
>>  at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2627)
>> at
>> org.wso2.andes.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:315)
>>  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.createProducerImpl(AMQSession.java:2625)
>> at
>> org.wso2.andes.client.AMQSession.createProducerImpl(AMQSession.java:2619)
>>  at org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:1231)
>> at org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:109)
>>  at
>> org.apache.synapse.message.store.impl.jms.JmsStore.newProducer(JmsStore.java:346)
>> at
>> org.apache.synapse.message.store.impl.jms.JmsStore.getProducer(JmsStore.java:136)
>>  at
>> org.apache.synapse.mediators.store.MessageStoreMediator.mediate(MessageStoreMediator.java:84)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
>>  at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
>> at
>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
>>  at
>> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>  at
>> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
>> at
>> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
>>  at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>  at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>> at java.lang.Thread.run(Thread.java:662)
>>
>>
>> Issue details can be found on:https://wso2.org/jira/browse/ESBJAVA-3024
>>
>>
>>
>> --
>> Thanks & Regards
>>
>> Iranga Muthuthanthri
>> Technical Lead - QA
>> (M) -0777-255773
>>
>> ___
>> 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] Test framework for carbon kernal 4.3.0 products.

[Krishantha Samaraweera]

Hi Eranda,

Can you create separate repository for platform automated test suite. This
repo will be build after building products with integration tests.

Thanks,
Krishantha.


On Mon, Mar 3, 2014 at 1:15 PM, Geeth Munasinghe  wrote:

> Can some one from QAA team re-factor carbon-platform-integration in git
> repo ?
>
> Please refer the mail thread [1] for the instructions regarding
> refactoring.
>
> [1] Guidelines to move project into GitHub.
>
> Thanks
> Geeth
>
>
>
>
> *G. K. S. Munasinghe *
> *Software Engineer,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226
>
>
> On Sun, Mar 2, 2014 at 9:59 PM, Eranda Sooriyabandara wrote:
>
>> Hi All,
>> This project is created by now in [1] but need to clarify what to include
>> and where.
>>
>> thanks
>> Eranda
>>
>> [1]. https://github.com/wso2/carbon-platform-integration
>>
>>
>> On Sat, Mar 1, 2014 at 7:45 PM, Geeth Munasinghe  wrote:
>>
>>> AFAIK We have not created a git repo for platform integration yet.
>>>
>>> @Eranda
>>> Can you please create git repo for platform integration?
>>>
>>> Thanks
>>> Geeth
>>>
>>>
>>> On Saturday, March 1, 2014, Krishantha Samaraweera 
>>> wrote:
>>>
 Kernel test framework is already available in 4.3.0, and AFAIK all
 kernel tests are passing.

 Anybody created git repo for Platform-integration ? platform level test
 framework is required for AS integration tests.

 Also we need to migrate all AS integration tests to our new framework.
 I will work with you on this.

 Thanks,
 Krishantha.


 On Sat, Mar 1, 2014 at 2:46 PM, Geeth Munasinghe wrote:

> Hi,
>
> To release kernal 4.3.0 based products we will have to run test
> automation framework with all the products. For that we will need to have
> the test automation framework on kernal 4.3.0.
> And we will have to move test framework to github too.  We will have
> to do this soon, because AS release need to go on Q1.
>
> Can someone from QAA team help with this task ?
>
> Thanks
> Geeth
>
>
>
>
> *G. K. S. Munasinghe*
> *Software Engineer,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226
>



 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.

>>>
>>>
>>> --
>>>
>>> *G. K. S. Munasinghe*
>>> *Software Engineer,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: ge...@wso2.com
>>> phone:(+94) 777911226
>>>
>>>
>>
>>
>> --
>>
>> *Eranda Sooriyabandara*Senior Software Engineer;
>> Integration Technologies Team;
>> WSO2 Inc.; http://wso2.com
>> Lean . Enterprise . Middleware
>>
>> E-mail: eranda AT wso2.com
>> Mobile: +94 716 472 816
>> Linked-In: http://www.linkedin.com/in/erandasooriyabandara
>> Blog: http://emsooriyabandara.blogspot.com/
>>
>>
>>
>>
>>
>


-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Kasun Gajasinghe]

Hi,

Shall we $subject from Carbon 4.3.0? And then, force the users to enable
workerNode mode by modifying the startup script itself, instead of passing
-DworkerNode=true property via command-line?

We have noticed that lot of users are passing the said property via the
command-line, but they sometimes miss to set that. That might lead to lot
of issues especially in DepSync. If we set as above, we can lower the human
errors. WDYT?

Thanks,
KasunG

-- 
*Kasun Gajasinghe*
Software Engineer;
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* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Sagara Gunathunga]

On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe  wrote:

> Hi,
>
> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
> workerNode mode by modifying the startup script itself, instead of passing
> -DworkerNode=true property via command-line?
>
> We have noticed that lot of users are passing the said property via the
> command-line, but they sometimes miss to set that. That might lead to lot
> of issues especially in DepSync. If we set as above, we can lower the human
> errors. WDYT?
>

+ 1 IMHO we can support for both options like we support for portOffset.

Thanks !

>
> Thanks,
> KasunG
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>


-- 
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

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Miyuru Wanninayaka]

How about during startup, log a message telling that
Starting as a manager|worker node.

So less chance of missing proper configuration and also by just looking at
logs anyone can say that log in from worker/manager node.

On Monday, March 3, 2014, Kasun Gajasinghe  wrote:

> Hi,
>
> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
> workerNode mode by modifying the startup script itself, instead of passing
> -DworkerNode=true property via command-line?
>
> We have noticed that lot of users are passing the said property via the
> command-line, but they sometimes miss to set that. That might lead to lot
> of issues especially in DepSync. If we set as above, we can lower the human
> errors. WDYT?
>
> Thanks,
> KasunG
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> 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* 
>
>
>
>

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

Re: [Dev] java.lang.OutOfMemoryError: GC overhead limit exceeded observed for ESB message store and forward scenario in MB Cluster Environment

[Chamila Wijayarathna]

Hi,
I got a similar error when running a cassandra archive job on BAM. By
analyzing "heap-dump.hprof" file, using Eclipse Memory Analyzer, I found
that 1 memory table has grow more than 600MB.
In this case, what I did as solution is reducing
"flush_largest_memtables_at" value in cassandra.yaml from 0.75 to 0.4.
As Dr. Srinath explained, jvm starts to flush its largest memory table at
the point it jvm consume 0.75 of memory. But before that process finishes
memory overflow can occur. But reducing that value this can be solved if
this occurs due to same reason. I am not sure if this works in ESB case.

Thank You!


On Mon, Mar 3, 2014 at 10:09 PM, Iranga Muthuthanthri wrote:

> Thanks Udara. Checked it before and the stack trace was different.The
> culprit in this case appears to from the andes client.
> On Mar 3, 2014 9:25 PM, "Udara Liyanage"  wrote:
>
>> I saw a similar issue occurred in BAM. Have a look mail thread subjected
>> " [Dev] [BAM] java.lang.OutOfMemoryError: GC overhead limit exceeded"
>>
>> Touched, not typed. Erroneous words are a feature, not a typo.
>> On Mar 3, 2014 6:57 PM, "Iranga Muthuthanthri"  wrote:
>>
>>> Hi All.
>>>
>>> Following was noted in testing for 100,00 messages for the ESB (4.8.1)
>>> message store and forward scenario in a MB 2.1.0 cluster environment.
>>>
>>> *Issue*:Out of memory exception noted in ESB console.
>>>
>>> [2014-03-03 04:37:36,065] ERROR - JmsStore Could not create a Message
>>> Producer for Store [MessageStoreO1]. Error:GC overhead limit exceeded
>>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>>> at java.util.Arrays.copyOfRange(Arrays.java:3209)
>>> at java.lang.String.(String.java:215)
>>>  at java.lang.StringBuilder.toString(StringBuilder.java:430)
>>> at java.lang.Object.toString(Object.java:219)
>>>  at
>>> org.wso2.andes.client.BasicMessageProducer.setPublishMode(BasicMessageProducer.java:167)
>>> at
>>> org.wso2.andes.client.BasicMessageProducer.(BasicMessageProducer.java:148)
>>>  at
>>> org.wso2.andes.client.BasicMessageProducer_0_8.(BasicMessageProducer_0_8.java:51)
>>> at
>>> org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:411)
>>>  at
>>> org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:82)
>>> at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2632)
>>>  at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2627)
>>> at
>>> org.wso2.andes.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:315)
>>>  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.createProducerImpl(AMQSession.java:2625)
>>> at
>>> org.wso2.andes.client.AMQSession.createProducerImpl(AMQSession.java:2619)
>>>  at
>>> org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:1231)
>>> at org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:109)
>>>  at
>>> org.apache.synapse.message.store.impl.jms.JmsStore.newProducer(JmsStore.java:346)
>>> at
>>> org.apache.synapse.message.store.impl.jms.JmsStore.getProducer(JmsStore.java:136)
>>>  at
>>> org.apache.synapse.mediators.store.MessageStoreMediator.mediate(MessageStoreMediator.java:84)
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
>>>  at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
>>> at
>>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
>>>  at
>>> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>>  at
>>> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
>>> at
>>> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
>>>  at
>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>>  at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>> at java.lang.Thread.run(Thread.java:662)
>>>
>>>
>>> Issue details can be found on:https://wso2.org/jira/browse/ESBJAVA-3024
>>>
>>>
>>>
>>> --
>>> Thanks & Regards
>>>
>>> Iranga Muthuthanthri
>>> Technical Lead - QA
>>> (M) -0777-255773
>>>
>>> ___
>>> 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
>
>


-- 
*Chamila Wijayarathna*
Engineering Intern,
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Kasun Gajasinghe]

On Mon, Mar 3, 2014 at 10:45 PM, Sagara Gunathunga  wrote:

>
>
>
> On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe  wrote:
>
>> Hi,
>>
>> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
>> workerNode mode by modifying the startup script itself, instead of passing
>> -DworkerNode=true property via command-line?
>>
>> We have noticed that lot of users are passing the said property via the
>> command-line, but they sometimes miss to set that. That might lead to lot
>> of issues especially in DepSync. If we set as above, we can lower the human
>> errors. WDYT?
>>
>
> + 1 IMHO we can support for both options like we support for portOffset.
>
>

Yes. Thinking along this line, I guess the best place for this attribute is
the carbon.xml just like portOffset. If this property is not passed via the
command-line, then we read the carbon.xml, and set that value as a system
property.


> Thanks !
>
>>
>> Thanks,
>> KasunG
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> WSO2 Inc.; http://wso2.com
>>
>>
>>  ,
>> *email: *
>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>
>>
>>
>> *blog: **http://kasunbg.org* 
>>
>>
>>
>> *twitter: **http://twitter.com/kasunbg* 
>>
>>
>>
>>
>
>
> --
> 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
>
>


-- 
*Kasun Gajasinghe*
Software Engineer;
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* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Kasun Gajasinghe]

On Mon, Mar 3, 2014 at 10:50 PM, Miyuru Wanninayaka  wrote:

> How about during startup, log a message telling that
> Starting as a manager|worker node.
>
> So less chance of missing proper configuration and also by just looking at
> logs anyone can say that log in from worker/manager node.
>
>
+1. I will do that as well.


>
> On Monday, March 3, 2014, Kasun Gajasinghe  wrote:
>
>>  Hi,
>>
>> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
>> workerNode mode by modifying the startup script itself, instead of passing
>> -DworkerNode=true property via command-line?
>>
>> We have noticed that lot of users are passing the said property via the
>> command-line, but they sometimes miss to set that. That might lead to lot
>> of issues especially in DepSync. If we set as above, we can lower the human
>> errors. WDYT?
>>
>> Thanks,
>> KasunG
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> WSO2 Inc.; http://wso2.com
>>
>>
>>  ,
>> *email: *
>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>
>>
>>
>> *blog: **http://kasunbg.org* 
>>
>>
>>
>> *twitter: **http://twitter.com/kasunbg* 
>>
>>
>>
>>
>
> --
> Sent from my iPad
>



-- 
*Kasun Gajasinghe*
Software Engineer;
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* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] java.lang.OutOfMemoryError: GC overhead limit exceeded observed for ESB message store and forward scenario in MB Cluster Environment

[Miyuru Wanninayaka]

You can't decide where the memory leak happened by just looking at stack
trace. Stack trace logs unfortunate call which jvm can't allocate memory,
however it might be something else which eats most of memory. So you need
to analyze created heap dump in repository/logs using something like
eclipse memory analyzer to decide from where leak happens .

On Monday, March 3, 2014, Iranga Muthuthanthri  wrote:

> Thanks Udara. Checked it before and the stack trace was different.The
> culprit in this case appears to from the andes client.
> On Mar 3, 2014 9:25 PM, "Udara Liyanage"  wrote:
>
> I saw a similar issue occurred in BAM. Have a look mail thread subjected "
> [Dev] [BAM] java.lang.OutOfMemoryError: GC overhead limit exceeded"
>
> Touched, not typed. Erroneous words are a feature, not a typo.
> On Mar 3, 2014 6:57 PM, "Iranga Muthuthanthri"  wrote:
>
> Hi All.
>
> Following was noted in testing for 100,00 messages for the ESB (4.8.1)
> message store and forward scenario in a MB 2.1.0 cluster environment.
>
> *Issue*:Out of memory exception noted in ESB console.
>
> [2014-03-03 04:37:36,065] ERROR - JmsStore Could not create a Message
> Producer for Store [MessageStoreO1]. Error:GC overhead limit exceeded
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.util.Arrays.copyOfRange(Arrays.java:3209)
> at java.lang.String.(String.java:215)
>  at java.lang.StringBuilder.toString(StringBuilder.java:430)
> at java.lang.Object.toString(Object.java:219)
>  at
> org.wso2.andes.client.BasicMessageProducer.setPublishMode(BasicMessageProducer.java:167)
> at
> org.wso2.andes.client.BasicMessageProducer.(BasicMessageProducer.java:148)
>  at
> org.wso2.andes.client.BasicMessageProducer_0_8.(BasicMessageProducer_0_8.java:51)
> at
> org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:411)
>  at
> org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:82)
> at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2632)
>  at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2627)
> at
> org.wso2.andes.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:315)
>  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.createProducerImpl(AMQSession.java:2625)
> at
> org.wso2.andes.client.AMQSession.createProducerImpl(AMQSession.java:2619)
>  at org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:1231)
> at org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:109)
>  at
> org.apache.synapse.message.store.impl.jms.JmsStore.newProducer(JmsStore.java:346)
> at
> org.apache.synapse.message.store.impl.jms.JmsStore.getProducer(JmsStore.java:136)
>  at
> org.apache.synapse.mediators.store.MessageStoreMediator.mediate(MessageStoreMediator.java:84)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
>  at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
> at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
>  at
> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.<
>
>

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

Re: [Dev] java.lang.OutOfMemoryError: GC overhead limit exceeded observed for ESB message store and forward scenario in MB Cluster Environment

[Srinath Perera]

GC overhead exceeded means more than 99% CPU spent of GC. Reason is you are
creating too many/ too complex objects.

Any chance you can reduce amount of object you create? Allocation view of a
profiler can help.

--Srinath


On Mon, Mar 3, 2014 at 10:51 PM, Chamila Wijayarathna wrote:

> Hi,
> I got a similar error when running a cassandra archive job on BAM. By
> analyzing "heap-dump.hprof" file, using Eclipse Memory Analyzer, I found
> that 1 memory table has grow more than 600MB.
> In this case, what I did as solution is reducing
> "flush_largest_memtables_at" value in cassandra.yaml from 0.75 to 0.4.
> As Dr. Srinath explained, jvm starts to flush its largest memory table at
> the point it jvm consume 0.75 of memory. But before that process finishes
> memory overflow can occur. But reducing that value this can be solved if
> this occurs due to same reason. I am not sure if this works in ESB case.
>
> Thank You!
>
>
> On Mon, Mar 3, 2014 at 10:09 PM, Iranga Muthuthanthri wrote:
>
>> Thanks Udara. Checked it before and the stack trace was different.The
>> culprit in this case appears to from the andes client.
>>  On Mar 3, 2014 9:25 PM, "Udara Liyanage"  wrote:
>>
>>> I saw a similar issue occurred in BAM. Have a look mail thread subjected
>>> " [Dev] [BAM] java.lang.OutOfMemoryError: GC overhead limit exceeded"
>>>
>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>> On Mar 3, 2014 6:57 PM, "Iranga Muthuthanthri"  wrote:
>>>
 Hi All.

 Following was noted in testing for 100,00 messages for the ESB (4.8.1)
 message store and forward scenario in a MB 2.1.0 cluster environment.

 *Issue*:Out of memory exception noted in ESB console.

 [2014-03-03 04:37:36,065] ERROR - JmsStore Could not create a Message
 Producer for Store [MessageStoreO1]. Error:GC overhead limit exceeded
 java.lang.OutOfMemoryError: GC overhead limit exceeded
 at java.util.Arrays.copyOfRange(Arrays.java:3209)
 at java.lang.String.(String.java:215)
  at java.lang.StringBuilder.toString(StringBuilder.java:430)
 at java.lang.Object.toString(Object.java:219)
  at
 org.wso2.andes.client.BasicMessageProducer.setPublishMode(BasicMessageProducer.java:167)
 at
 org.wso2.andes.client.BasicMessageProducer.(BasicMessageProducer.java:148)
  at
 org.wso2.andes.client.BasicMessageProducer_0_8.(BasicMessageProducer_0_8.java:51)
 at
 org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:411)
  at
 org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:82)
 at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2632)
  at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2627)
 at
 org.wso2.andes.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:315)
  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.createProducerImpl(AMQSession.java:2625)
 at
 org.wso2.andes.client.AMQSession.createProducerImpl(AMQSession.java:2619)
  at
 org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:1231)
 at org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:109)
  at
 org.apache.synapse.message.store.impl.jms.JmsStore.newProducer(JmsStore.java:346)
 at
 org.apache.synapse.message.store.impl.jms.JmsStore.getProducer(JmsStore.java:136)
  at
 org.apache.synapse.mediators.store.MessageStoreMediator.mediate(MessageStoreMediator.java:84)
 at
 org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
  at
 org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
 at
 org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
  at
 org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
  at
 org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
 at
 org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
  at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
  at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
 at java.lang.Thread.run(Thread.java:662)


 Issue details can be found on:https://wso2.org/jira/browse/ESBJAVA-3024



 --
 Thanks & Regards

 Iranga Muthuthanthri
 Technical Lead - QA
 (M) -0777-255773

 __

Re: [Dev] Stuck on Pipes

[Chan]

I have made the change for this but unfortunately it's not directly linked
to git. Below is the code of the route action wrapper -

*Route Action wrapper*
/*
A wrapper object that wraps request, response, session and few utility
methods
*/
var RouteAction = function(request, response, session, params){
var route_action = {};
route_action._req = request;
route_action._res = response;
route_action._session = session;
route_action._params = params;
route_action._query = function(){
return request.getAllParameters();
};
route_action._body = function(){
var content=request.getContent();
var contentObj={};
//Only parse if the user has provided any content
if(content){
   contentObj=parse(content);
}
return contentObj;
};
route_action._headers = function(){
return request.getAllHeaders();
};
route_action._files = function(){
var files = request.getAllFiles();
var files_array = [];
for(var name in files) {
if(files.hasOwnProperty(name)) {
files_array.push({
name : name,
file : files[name]
});
}
}
return files_array;
}
return route_action;
}

*Implementation to the route.js*
var route_action = new RouteAction(req,res,session, match.params);
return match.ref(route_action)||{};

Cheers~


On Mon, Mar 3, 2014 at 11:37 AM, Chan  wrote:

> Thanks Sameera. Other than that I started working on the jaggery-router to
> improve it in the below method
>
>- Change public signature of a route as router.get($route,
>function($ctx){});
>- $ctx will have _request, _response, _session, _headers(), _params,
>_body(), _files()
>
> We'll review these changes and merge them to the main router.
> Cheers~
>
>
> On Mon, Mar 3, 2014 at 1:12 AM, Sameera Medagammaddegedara <
> samee...@wso2.com> wrote:
>
>> Hello Chan,
>>
>> Can try you changing the following line ;
>>
>> router.get('resource',function ...
>>
>>
>> to:
>>
>> router.get('/resource',function 
>>
>>
>> Please let me know if this fixes your problem.
>>
>> Thank You,
>> Sameera
>>
>>
>> On Sun, Mar 2, 2014 at 11:39 PM, Chan  wrote:
>>
>>> Hi Sameera,
>>> I am faced in an issue where my route is not being accessed. My code is
>>> at on github [1]. I think the route is being added to the route tree but
>>> it's not being executed.
>>>
>>> Also it would be better make the public api of a route function in the
>>> below construct.
>>>
>>> function(context){
>>>
>>> context._request // for request object
>>>
>>> context._response // for response object
>>>
>>> context._session // for session object
>>> context._param // for params hash
>>> context._body // for body
>>>
>>> context._files // for files coming in the request
>>>
>>> }
>>>
>>> [1] - https://github.com/dulichan/storage
>>>
>>> --
>>> Chan (Dulitha Wijewantha)
>>> Software Engineer - Mobile Development
>>> WSO2Mobile
>>> Lean.Enterprise.Mobileware
>>>  * ~Email   duli...@wso2.com *
>>> *  ~Mobile +94712112165 <%2B94712112165>*
>>>
>>> *  ~Website   dulithawijewantha.com  *
>>>
>>> *  ~Blog blog.dulithawijewantha.com
>>> *
>>> *  ~Twitter @dulitharw *
>>>
>>
>>
>>
>> --
>> Sameera Medagammaddegedara
>> Software Engineer
>>
>> Contact:
>> Email: samee...@wso2.com
>> Mobile: + 94 077 255 3005
>>
>
>
>
> --
> Chan (Dulitha Wijewantha)
> Software Engineer - Mobile Development
> WSO2Mobile
> Lean.Enterprise.Mobileware
>  * ~Email   duli...@wso2.com *
> *  ~Mobile +94712112165 <%2B94712112165>*
> *  ~Website   dulitha.me *
> *  ~Twitter @dulitharw *
>   *~SO @chan *
>



-- 
Chan (Dulitha Wijewantha)
Software Engineer - Mobile Development
WSO2Mobile
Lean.Enterprise.Mobileware
 * ~Email   duli...@wso2.com *
*  ~Mobile +94712112165*
*  ~Website   dulitha.me *
*  ~Twitter @dulitharw *
  *~SO @chan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Shameera Rathnayaka]

Hi
On Mon, Mar 3, 2014 at 10:45 PM, Sagara Gunathunga  wrote:

>
>> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
>> workerNode mode by modifying the startup script itself, instead of passing
>> -DworkerNode=true property via command-line?
>>
>> We have noticed that lot of users are passing the said property via the
>> command-line, but they sometimes miss to set that. That might lead to lot
>> of issues especially in DepSync. If we set as above, we can lower the human
>> errors. WDYT?
>>
>
> + 1 IMHO we can support for both options like we support for portOffset.
>

+1 for having both options, otherwise the one how you addicted to
commadline will need to figure it out again :).

Thanks,
Shameera.


>
> Thanks !
>
>>
>> Thanks,
>> KasunG
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> WSO2 Inc.; http://wso2.com
>>
>>
>>  ,
>> *email: *
>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>
>>
>>
>> *blog: **http://kasunbg.org* 
>>
>>
>>
>> *twitter: **http://twitter.com/kasunbg* 
>>
>>
>>
>>
>
>
> --
> 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
>
>


-- 
*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

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Isuru Perera]

On Mon, Mar 3, 2014 at 10:54 PM, Kasun Gajasinghe  wrote:

>
>
>
> On Mon, Mar 3, 2014 at 10:45 PM, Sagara Gunathunga wrote:
>
>>
>>
>>
>> On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe wrote:
>>
>>> Hi,
>>>
>>> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
>>> workerNode mode by modifying the startup script itself, instead of passing
>>> -DworkerNode=true property via command-line?
>>>
>>> We have noticed that lot of users are passing the said property via the
>>> command-line, but they sometimes miss to set that. That might lead to lot
>>> of issues especially in DepSync. If we set as above, we can lower the human
>>> errors. WDYT?
>>>
>>
>> + 1 IMHO we can support for both options like we support for portOffset.
>>
>>
>
> Yes. Thinking along this line, I guess the best place for this attribute
> is the carbon.xml just like portOffset. If this property is not passed via
> the command-line, then we read the carbon.xml, and set that value as a
> system property.
>
+1. It's better to have this as a configuration in carbon.xml. It makes
easier to automate configurations using puppet etc.

>
>
>> Thanks !
>>
>>>
>>> Thanks,
>>> KasunG
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> WSO2 Inc.; http://wso2.com
>>>
>>>
>>>  ,
>>> *email: *
>>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>>
>>>
>>>
>>> *blog: **http://kasunbg.org* 
>>>
>>>
>>>
>>> *twitter: **http://twitter.com/kasunbg* 
>>>
>>>
>>>
>>>
>>
>>
>> --
>> 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
>>
>>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>
> ___
> 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

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

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Shameera Rathnayaka]

Hi Miyuru/Kasun,


On Mon, Mar 3, 2014 at 10:54 PM, Kasun Gajasinghe  wrote:

>
> On Mon, Mar 3, 2014 at 10:50 PM, Miyuru Wanninayaka wrote:
>
>> How about during startup, log a message telling that
>> Starting as a manager|worker node.
>>
>> So less chance of missing proper configuration and also by just looking
>> at logs anyone can say that log in from worker/manager node.
>>
>
+1 for logging the type, but not the worker or manager, as now we are
supporting multiple profile with carbon kernel , best way is log the
profile name.  WDYS?

@Kasun,
Can you explain how you gonna add this to carbon.xml ? what is the element
name?

Thanks,
Shameera.



>
>>
> +1. I will do that as well.
>
>
>>
>> On Monday, March 3, 2014, Kasun Gajasinghe  wrote:
>>
>>>  Hi,
>>>
>>> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
>>> workerNode mode by modifying the startup script itself, instead of passing
>>> -DworkerNode=true property via command-line?
>>>
>>> We have noticed that lot of users are passing the said property via the
>>> command-line, but they sometimes miss to set that. That might lead to lot
>>> of issues especially in DepSync. If we set as above, we can lower the human
>>> errors. WDYT?
>>>
>>> Thanks,
>>> KasunG
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> WSO2 Inc.; http://wso2.com
>>>
>>>
>>>  ,
>>> *email: *
>>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>>
>>>
>>>
>>> *blog: **http://kasunbg.org* 
>>>
>>>
>>>
>>> *twitter: **http://twitter.com/kasunbg* 
>>>
>>>
>>>
>>>
>>
>> --
>> Sent from my iPad
>>
>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>
> ___
> 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

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Shameera Rathnayaka]

Hi All,

If we didn't start the server as worker, "default" is the profile name
which will load, if we start as worker then there should be a profile name
"woker" directory in the repository/components.

Thanks,
Shameera.


On Mon, Mar 3, 2014 at 11:26 PM, Shameera Rathnayaka wrote:

> Hi Miyuru/Kasun,
>
>
> On Mon, Mar 3, 2014 at 10:54 PM, Kasun Gajasinghe  wrote:
>
>>
>> On Mon, Mar 3, 2014 at 10:50 PM, Miyuru Wanninayaka wrote:
>>
>>> How about during startup, log a message telling that
>>> Starting as a manager|worker node.
>>>
>>> So less chance of missing proper configuration and also by just looking
>>> at logs anyone can say that log in from worker/manager node.
>>>
>>
> +1 for logging the type, but not the worker or manager, as now we are
> supporting multiple profile with carbon kernel , best way is log the
> profile name.  WDYS?
>
> @Kasun,
> Can you explain how you gonna add this to carbon.xml ? what is the element
> name?
>
>  Thanks,
> Shameera.
>
>
>
>>
>>>
>> +1. I will do that as well.
>>
>>
>>>
>>> On Monday, March 3, 2014, Kasun Gajasinghe  wrote:
>>>
  Hi,

 Shall we $subject from Carbon 4.3.0? And then, force the users to
 enable workerNode mode by modifying the startup script itself, instead of
 passing -DworkerNode=true property via command-line?

 We have noticed that lot of users are passing the said property via the
 command-line, but they sometimes miss to set that. That might lead to lot
 of issues especially in DepSync. If we set as above, we can lower the human
 errors. WDYT?

 Thanks,
 KasunG

 --
 *Kasun Gajasinghe*
 Software Engineer;
 WSO2 Inc.; http://wso2.com


  ,
 *email: *
 *kasung AT spamfree wso2.com    ** cell: **+94 (77)
 678-0813 <%2B94%20%2877%29%20678-0813>*
 *linked-in: *http://lk.linkedin.com/in/gajasinghe



 *blog: **http://kasunbg.org* 



 *twitter: **http://twitter.com/kasunbg* 




>>>
>>> --
>>> Sent from my iPad
>>>
>>
>>
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> WSO2 Inc.; http://wso2.com
>>
>>
>>  ,
>> *email: *
>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>
>>
>>
>> *blog: **http://kasunbg.org* 
>>
>>
>>
>> *twitter: **http://twitter.com/kasunbg* 
>>
>>
>>
>>
>> ___
>> 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 <%2B9471%20922%201454>*
>
> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
> *Twitter : *https://twitter.com/Shameera_R
>



-- 
*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

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Supun Malinga]

Hi,

+1.
@Kasung AFAIR you need to update this in code level (in carbon.util
package) as well. Currently I don't think its written to parse the false
argument..

thanks,


On Mon, Mar 3, 2014 at 1:01 PM, Shameera Rathnayaka wrote:

> Hi All,
>
> If we didn't start the server as worker, "default" is the profile name
> which will load, if we start as worker then there should be a profile name
> "woker" directory in the repository/components.
>
> Thanks,
> Shameera.
>
>
> On Mon, Mar 3, 2014 at 11:26 PM, Shameera Rathnayaka wrote:
>
>> Hi Miyuru/Kasun,
>>
>>
>> On Mon, Mar 3, 2014 at 10:54 PM, Kasun Gajasinghe wrote:
>>
>>>
>>> On Mon, Mar 3, 2014 at 10:50 PM, Miyuru Wanninayaka wrote:
>>>
 How about during startup, log a message telling that
 Starting as a manager|worker node.

 So less chance of missing proper configuration and also by just looking
 at logs anyone can say that log in from worker/manager node.

>>>
>> +1 for logging the type, but not the worker or manager, as now we are
>> supporting multiple profile with carbon kernel , best way is log the
>> profile name.  WDYS?
>>
>> @Kasun,
>> Can you explain how you gonna add this to carbon.xml ? what is the
>> element name?
>>
>>  Thanks,
>> Shameera.
>>
>>
>>
>>>

>>> +1. I will do that as well.
>>>
>>>

 On Monday, March 3, 2014, Kasun Gajasinghe  wrote:

>  Hi,
>
> Shall we $subject from Carbon 4.3.0? And then, force the users to
> enable workerNode mode by modifying the startup script itself, instead of
> passing -DworkerNode=true property via command-line?
>
> We have noticed that lot of users are passing the said property via
> the command-line, but they sometimes miss to set that. That might lead to
> lot of issues especially in DepSync. If we set as above, we can lower the
> human errors. WDYT?
>
> Thanks,
> KasunG
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>

 --
 Sent from my iPad

>>>
>>>
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> WSO2 Inc.; http://wso2.com
>>>
>>>
>>>  ,
>>> *email: *
>>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>>
>>>
>>>
>>> *blog: **http://kasunbg.org* 
>>>
>>>
>>>
>>> *twitter: **http://twitter.com/kasunbg* 
>>>
>>>
>>>
>>>
>>> ___
>>> 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 <%2B9471%20922%201454>*
>>
>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
>> *Twitter : *https://twitter.com/Shameera_R
>>
>
>
>
> --
> *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
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
email: sup...@wso2.com 
mobile: +94 (0)71 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] java.lang.OutOfMemoryError: GC overhead limit exceeded observed for ESB message store and forward scenario in MB Cluster Environment

[Iranga]

Thanks for the info will check as suggested and update.

-Iranga

On 2014 මාර්තු 3, at ප.ව. 10.57, Srinath Perera  wrote:

> GC overhead exceeded means more than 99% CPU spent of GC. Reason is you are 
> creating too many/ too complex objects. 
> 
> Any chance you can reduce amount of object you create? Allocation view of a 
> profiler can help. 
> 
> --Srinath
> 
> 
> On Mon, Mar 3, 2014 at 10:51 PM, Chamila Wijayarathna  
> wrote:
>> Hi,
>> I got a similar error when running a cassandra archive job on BAM. By 
>> analyzing "heap-dump.hprof" file, using Eclipse Memory Analyzer, I found 
>> that 1 memory table has grow more than 600MB. 
>> In this case, what I did as solution is reducing 
>> "flush_largest_memtables_at" value in cassandra.yaml from 0.75 to 0.4. 
>> As Dr. Srinath explained, jvm starts to flush its largest memory table at 
>> the point it jvm consume 0.75 of memory. But before that process finishes 
>> memory overflow can occur. But reducing that value this can be solved if 
>> this occurs due to same reason. I am not sure if this works in ESB case.
>> 
>> Thank You!
>> 
>> 
>> On Mon, Mar 3, 2014 at 10:09 PM, Iranga Muthuthanthri  
>> wrote:
>>> Thanks Udara. Checked it before and the stack trace was different.The 
>>> culprit in this case appears to from the andes client.
>>> 
>>> On Mar 3, 2014 9:25 PM, "Udara Liyanage"  wrote:
 I saw a similar issue occurred in BAM. Have a look mail thread subjected " 
 [Dev] [BAM] java.lang.OutOfMemoryError: GC overhead limit exceeded"
 
 Touched, not typed. Erroneous words are a feature, not a typo.
 
 On Mar 3, 2014 6:57 PM, "Iranga Muthuthanthri"  wrote:
> Hi All.
> 
> Following was noted in testing for 100,00 messages for the ESB (4.8.1) 
> message store and forward scenario in a MB 2.1.0 cluster environment.
> 
> Issue:Out of memory exception noted in ESB console.
> 
> [2014-03-03 04:37:36,065] ERROR - JmsStore Could not create a Message 
> Producer for Store [MessageStoreO1]. Error:GC overhead limit exceeded
> java.lang.OutOfMemoryError: GC overhead limit exceeded
>   at java.util.Arrays.copyOfRange(Arrays.java:3209)
>   at java.lang.String.(String.java:215)
>   at java.lang.StringBuilder.toString(StringBuilder.java:430)
>   at java.lang.Object.toString(Object.java:219)
>   at 
> org.wso2.andes.client.BasicMessageProducer.setPublishMode(BasicMessageProducer.java:167)
>   at 
> org.wso2.andes.client.BasicMessageProducer.(BasicMessageProducer.java:148)
>   at 
> org.wso2.andes.client.BasicMessageProducer_0_8.(BasicMessageProducer_0_8.java:51)
>   at 
> org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:411)
>   at 
> org.wso2.andes.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:82)
>   at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2632)
>   at org.wso2.andes.client.AMQSession$7.execute(AMQSession.java:2627)
>   at 
> org.wso2.andes.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:315)
>   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.createProducerImpl(AMQSession.java:2625)
>   at 
> org.wso2.andes.client.AMQSession.createProducerImpl(AMQSession.java:2619)
>   at org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:1231)
>   at org.wso2.andes.client.AMQSession.createProducer(AMQSession.java:109)
>   at 
> org.apache.synapse.message.store.impl.jms.JmsStore.newProducer(JmsStore.java:346)
>   at 
> org.apache.synapse.message.store.impl.jms.JmsStore.getProducer(JmsStore.java:136)
>   at 
> org.apache.synapse.mediators.store.MessageStoreMediator.mediate(MessageStoreMediator.java:84)
>   at 
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77)
>   at 
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
>   at 
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131)
>   at 
> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166)
>   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>   at 
> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411)
>   at 
> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183)
>   at 
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Ashansa Perera]

+1 for adding this to carbon.xml to avoid the human errors, since passing
this param can be easily missed by someone who is not used to it. And
supporting both ways ( if not given as command line input, take the
configured value ) would be great.

And as like we have the logs when applying patch changes ( which is really
helpful IMO ), logging the profile name would too help a lot.


On Mon, Mar 3, 2014 at 11:41 PM, Supun Malinga  wrote:

> Hi,
>
> +1.
> @Kasung AFAIR you need to update this in code level (in carbon.util
> package) as well. Currently I don't think its written to parse the false
> argument..
>
> thanks,
>
>
> On Mon, Mar 3, 2014 at 1:01 PM, Shameera Rathnayaka wrote:
>
>> Hi All,
>>
>> If we didn't start the server as worker, "default" is the profile name
>> which will load, if we start as worker then there should be a profile name
>> "woker" directory in the repository/components.
>>
>> Thanks,
>> Shameera.
>>
>>
>> On Mon, Mar 3, 2014 at 11:26 PM, Shameera Rathnayaka 
>> wrote:
>>
>>> Hi Miyuru/Kasun,
>>>
>>>
>>> On Mon, Mar 3, 2014 at 10:54 PM, Kasun Gajasinghe wrote:
>>>

 On Mon, Mar 3, 2014 at 10:50 PM, Miyuru Wanninayaka wrote:

> How about during startup, log a message telling that
> Starting as a manager|worker node.
>
> So less chance of missing proper configuration and also by just
> looking at logs anyone can say that log in from worker/manager node.
>

>>> +1 for logging the type, but not the worker or manager, as now we are
>>> supporting multiple profile with carbon kernel , best way is log the
>>> profile name.  WDYS?
>>>
>>> @Kasun,
>>> Can you explain how you gonna add this to carbon.xml ? what is the
>>> element name?
>>>
>>>  Thanks,
>>> Shameera.
>>>
>>>
>>>

>
 +1. I will do that as well.


>
> On Monday, March 3, 2014, Kasun Gajasinghe  wrote:
>
>>  Hi,
>>
>> Shall we $subject from Carbon 4.3.0? And then, force the users to
>> enable workerNode mode by modifying the startup script itself, instead of
>> passing -DworkerNode=true property via command-line?
>>
>> We have noticed that lot of users are passing the said property via
>> the command-line, but they sometimes miss to set that. That might lead to
>> lot of issues especially in DepSync. If we set as above, we can lower the
>> human errors. WDYT?
>>
>> Thanks,
>> KasunG
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> WSO2 Inc.; http://wso2.com
>>
>>
>>  ,
>> *email: *
>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>
>>
>>
>> *blog: **http://kasunbg.org* 
>>
>>
>>
>> *twitter: **http://twitter.com/kasunbg* 
>>
>>
>>
>>
>
> --
> Sent from my iPad
>



 --
 *Kasun Gajasinghe*
 Software Engineer;
 WSO2 Inc.; http://wso2.com


  ,
 *email: *
 *kasung AT spamfree wso2.com    ** cell: **+94 (77)
 678-0813 <%2B94%20%2877%29%20678-0813>*
 *linked-in: *http://lk.linkedin.com/in/gajasinghe



 *blog: **http://kasunbg.org* 



 *twitter: **http://twitter.com/kasunbg* 




 ___
 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 <%2B9471%20922%201454>*
>>>
>>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
>>> *Twitter : *https://twitter.com/Shameera_R
>>>
>>
>>
>>
>> --
>> *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
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Supun Malinga,
>
> Senior Software Engineer,
> WSO2 Inc.
> http://wso2.com
> email: sup...@wso2.com 
> mobile: +94 (0)71 56 91 321
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

Ashansa Perera
Software Engineer
WSO2, Inc
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Sameera Jayasoma]

We process carbon.xml only when we launch the OSGi framework. I.e inside
the Carbon base bundle. But we need workerNode property before the launch
the OSGi framework. I.e. inside the Carbon main jar.

So IMV easiest option would be the put this property in the server startup
script files. Lets keep the portOffset property as it is in the carbon.xml

Thanks,
Sameera.


On Tue, Mar 4, 2014 at 7:48 AM, Ashansa Perera  wrote:

> +1 for adding this to carbon.xml to avoid the human errors, since passing
> this param can be easily missed by someone who is not used to it. And
> supporting both ways ( if not given as command line input, take the
> configured value ) would be great.
>
> And as like we have the logs when applying patch changes ( which is really
> helpful IMO ), logging the profile name would too help a lot.
>
>
> On Mon, Mar 3, 2014 at 11:41 PM, Supun Malinga  wrote:
>
>> Hi,
>>
>> +1.
>> @Kasung AFAIR you need to update this in code level (in carbon.util
>> package) as well. Currently I don't think its written to parse the false
>> argument..
>>
>> thanks,
>>
>>
>> On Mon, Mar 3, 2014 at 1:01 PM, Shameera Rathnayaka wrote:
>>
>>> Hi All,
>>>
>>> If we didn't start the server as worker, "default" is the profile name
>>> which will load, if we start as worker then there should be a profile name
>>> "woker" directory in the repository/components.
>>>
>>> Thanks,
>>> Shameera.
>>>
>>>
>>> On Mon, Mar 3, 2014 at 11:26 PM, Shameera Rathnayaka 
>>> wrote:
>>>
 Hi Miyuru/Kasun,


 On Mon, Mar 3, 2014 at 10:54 PM, Kasun Gajasinghe wrote:

>
> On Mon, Mar 3, 2014 at 10:50 PM, Miyuru Wanninayaka 
> wrote:
>
>> How about during startup, log a message telling that
>> Starting as a manager|worker node.
>>
>> So less chance of missing proper configuration and also by just
>> looking at logs anyone can say that log in from worker/manager node.
>>
>
 +1 for logging the type, but not the worker or manager, as now we are
 supporting multiple profile with carbon kernel , best way is log the
 profile name.  WDYS?

 @Kasun,
 Can you explain how you gonna add this to carbon.xml ? what is the
 element name?

  Thanks,
 Shameera.



>
>>
> +1. I will do that as well.
>
>
>>
>> On Monday, March 3, 2014, Kasun Gajasinghe  wrote:
>>
>>>  Hi,
>>>
>>> Shall we $subject from Carbon 4.3.0? And then, force the users to
>>> enable workerNode mode by modifying the startup script itself, instead 
>>> of
>>> passing -DworkerNode=true property via command-line?
>>>
>>> We have noticed that lot of users are passing the said property via
>>> the command-line, but they sometimes miss to set that. That might lead 
>>> to
>>> lot of issues especially in DepSync. If we set as above, we can lower 
>>> the
>>> human errors. WDYT?
>>>
>>> Thanks,
>>> KasunG
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> WSO2 Inc.; http://wso2.com
>>>
>>>
>>>  ,
>>> *email: *
>>> *kasung AT spamfree wso2.com    ** cell: **+94
>>> (77) 678-0813 <%2B94%20%2877%29%20678-0813>*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>>
>>>
>>>
>>> *blog: **http://kasunbg.org* 
>>>
>>>
>>>
>>> *twitter: **http://twitter.com/kasunbg* 
>>>
>>>
>>>
>>>
>>
>> --
>> Sent from my iPad
>>
>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>
> ___
> 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 <%2B9471%20922%201454>*

 *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
 *Twitter : *https://twitter.com/Shameera_R

>>>
>>>
>>>
>>> --
>>> *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
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailma

[Dev] Class Loading details for Axis2 Services

[Isuru Perera]

Hi,

I cannot find $subject in latest AS 5.2.1 wiki docs [1].

I can see the details at [2].

Why is it missing in latest docs?

[1]
https://docs.wso2.org/display/AS521/WSO2+Application+Server+Documentation
[2] https://docs.wso2.org/display/AS412/Class+Loading+for+Services

-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

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

[Dev] [ActiveMQ 5.9.0 with ESB 4.8.1]

[Gayan Gunawardana]

Hi,

Is it possible to use ActiveMQ 5.9.0 as a JMS provider to ESB 4.8.1.

I have seen activemq-core-*.jar is not exist in ActiveMQ 5.9.0

-- 
Gayan Gunawardana
Software Engineer; WSO2 Inc.; http://wso2.com/
Email: ga...@wso2.com
Mobile: +94 (71) 8020933
Blog: http://gayanj2ee.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ActiveMQ 5.9.0 with ESB 4.8.1]

[Isuru Udana]

Hi Gayan,

In ActiveMQ version 5.8.0 and above, activemq-core-*.jar has been split
into activemq-broker-*.jar and activemq-client-*.jar.

https://docs.wso2.org/display/ESB481/Configure+with+ActiveMQ

Thanks.


On Tue, Mar 4, 2014 at 10:04 AM, Gayan Gunawardana  wrote:

> Hi,
>
> Is it possible to use ActiveMQ 5.9.0 as a JMS provider to ESB 4.8.1.
>
> I have seen activemq-core-*.jar is not exist in ActiveMQ 5.9.0
>
> --
> Gayan Gunawardana
> Software Engineer; WSO2 Inc.; http://wso2.com/
> Email: ga...@wso2.com
> Mobile: +94 (71) 8020933
> Blog: http://gayanj2ee.blogspot.com/
>



-- 
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ActiveMQ 5.9.0 with ESB 4.8.1]

[Gayan Gunawardana]

Hi,

Thanks a lot it works fine after copying all jars as mention in above the
above link.


On Tue, Mar 4, 2014 at 10:07 AM, Isuru Udana  wrote:

> Hi Gayan,
>
> In ActiveMQ version 5.8.0 and above, activemq-core-*.jar has been split
> into activemq-broker-*.jar and activemq-client-*.jar.
>
> https://docs.wso2.org/display/ESB481/Configure+with+ActiveMQ
>
> Thanks.
>
>
> On Tue, Mar 4, 2014 at 10:04 AM, Gayan Gunawardana  wrote:
>
>> Hi,
>>
>> Is it possible to use ActiveMQ 5.9.0 as a JMS provider to ESB 4.8.1.
>>
>>  I have seen activemq-core-*.jar is not exist in ActiveMQ 5.9.0
>>
>> --
>> Gayan Gunawardana
>> Software Engineer; WSO2 Inc.; http://wso2.com/
>> Email: ga...@wso2.com
>> Mobile: +94 (71) 8020933
>> Blog: http://gayanj2ee.blogspot.com/
>>
>
>
>
> --
> *Isuru Udana*
> Senior
> * Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
> twitter: http://twitter.com/isudana
>



-- 
Gayan Gunawardana
Software Engineer; WSO2 Inc.; http://wso2.com/
Email: ga...@wso2.com
Mobile: +94 (71) 8020933
Blog: http://gayanj2ee.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [API-M] Issue with JSON result in API-M

[Indika Sampath]

Hi API-M team,

I encounter an issue with the JSON message in API-M. The WSO2 Con API
backend currently deploy in the API-M. It has number of Jaggery endpoints.

When I call the endpoint [1] I come up with the following JSON result.

[
{
"id": {},
"title": "Registration",
"description": "Registration",
"venue": "Ball Room",
"eventTypeId": {},
"fromDateTime": "2014-03-25 08:30:00",
"toDateTime": "2014-03-25 09:00:00",
"isCrossTrack": {}
}
]

But If I call the same endpoint which is locally deployed Jaggery server
[2] I end up with the following JSON result.

[
{
"id": "1",
"title": "Registration",
"description": "Registration",
"venue": "Ball Room",
"eventTypeId": "1",
"fromDateTime": "2014-03-25 08:30:00",
"toDateTime": "2014-03-25 09:00:00",
"isCrossTrack": "1"
}
]

All the integer fields empty in the API-M JSON result. Can you guys look in
to this issue.

[1] curl -i -H "Accept: application/json" -X GET
http://api.wso2con.com:8280/wso2_con_public_api/1.0/conferences/1/agendas/1/tracks/1/events

[2] curl -i -H "Accept: application/json" -X GET
http://127.0.0.1:9763/con_api/conferences/1/agendas/1/tracks/1/events

Thank you.

-- 
Indika Sampath
Software Engineer
WSO2 Inc.
http://wso2.com

Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Log mediator changes the content type of the response?

[Bhathiya Jayasekara]

Hi devs,

I was trying to run the sample in here [1]. It works fine as mentioned, and
the client gets the response in json like this.

{"Customer":{"id":123,"name":"John"}}

Then I added a   in out sequence.

  
 
 
  

Now the response which client gets is like this.

123John

but the Content-Type header is still *application/json*.

Is this a known bug or am I missing something?

[1]
https://docs.wso2.org/display/ESB460/Using+REST+with+a+Proxy+Service#UsingRESTwithaProxyService-RESTClientandRESTService

Thanks,

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

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 BAM 2.4.1-M2

[Dunith Dhanushka]

Hi all,

BAM 2.4.1-Milestone2 distribution is available at
https://svn.wso2.org/repos/wso2/people/malith/2.4.1-m2/wso2bam-2.4.1.zip

Following are the bug fixes, improvements and the new features available
with this release.

Bug

[BAM-1437 ] - Server startup on
Windows throwing exception
[BAM-1454 ] - mysql.sql script is
missing from dbscripts folder
[BAM-1456 ] - Include
hector-config.xml file to the product


Improvement

[BAM-1460 ] - Toolbox artifacts
deployed, should not be editable
[BAM-1463 ] - Migrate BAM specific
data sources from master-datasources.xml to bam-datasources.xml
[BAM-1464 ] - Fixing issues in
Incremetal Data Processing in Distributed mode.


New Feature

[BAM-1428 ] -  HL7 Message
Interceptor/Publisher


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

Re: [Dev] Investigating on the Chrome page download issue

[Isuru Perera]

Hi Amila,

Were you able to find out more clues on this issue?


On Fri, Feb 28, 2014 at 4:23 PM, Amila Maha Arachchi wrote:

> When the page loads successfully, then also content is gzip encoded. So,
> that can't be the reason.
>
>
> On Fri, Feb 28, 2014 at 2:42 PM, Kasun Gajasinghe  wrote:
>
>> Hi Amila,
>>
>> If the response contains the Content-Type as text/html, then it would
>> displayed in the browser itself. But that's not the issue in your case.
>>
>> It seems the response you are seeing is GZip encoded since the
>> Content-Encoding header is set to GZip. It's hard to understand why Chrome
>> wouldn't decode it!
>>
>>
>>
>> On Fri, Feb 28, 2014 at 2:30 PM, Amila Maha Arachchi wrote:
>>
>>> I am re-posting the request headers with clarity.
>>>
>>> Isuru, yes, response headers were seen inside the downloaded file.
>>>
>>> Request URL:
>>> https://cloudmgt.cloudpreview.wso2.com/cloudmgt/site/pages/index.jag
>>> Request Method: GET
>>> Status Code:200 OK
>>> Request Headersview source
>>>
>>> Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
>>> Accept-Encoding:gzip,deflate,sdch
>>> Accept-Language:en-US,en;q=0.8
>>> Connection:keep-alive
>>> Cookie:JSESSIONID=D4F2E51261E81DDAA3C70FDB96A30A84;
>>> __utma=213501382.1702684681.1392966199.1392966199.1393574823.2;
>>> __utmb=213501382.2.10.1393574823; __utmc=213501382;
>>> __utmz=213501382.1393574823.2.2.utmcsr=identity.cloudpreview.wso2.com
>>> |utmccn=(referral)|utmcmd=referral|utmcct=/commonauth
>>> Host:cloudmgt.cloudpreview.wso2.com
>>> Referer:https://cloudmgt.cloudpreview.wso2.com/cloudmgt/
>>> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0)
>>> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 Safari/537.36
>>>
>>>
>>> On Fri, Feb 28, 2014 at 2:20 PM, Isuru Perera  wrote:
>>>
 Hmm.. That's strange. You see HTTP Headers in the downloaded file
 itself?


 On Fri, Feb 28, 2014 at 1:43 PM, Amila Maha Arachchi 
 wrote:

> Following are the request headers
>
>
>1. Request URL:
>
>https://cloudmgt.cloudpreview.wso2.com/cloudmgt/site/pages/index.jag
>2. Request Method:
>GET
>3. Status Code:
>200 OK
>4. Request Headersview source
>   1. Accept:
>
>   
> text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
>   2. Accept-Encoding:
>   gzip,deflate,sdch
>   3. Accept-Language:
>   en-US,en;q=0.8
>   4. Connection:
>   keep-alive
>   5. Cookie:
>   JSESSIONID=D4F2E51261E81DDAA3C70FDB96A30A84;
>   __utma=213501382.1702684681.1392966199.1392966199.1393574823.2;
>   __utmb=213501382.2.10.1393574823; __utmc=213501382;
>   __utmz=213501382.1393574823.2.2.utmcsr=
>   identity.cloudpreview.wso2.com
>   |utmccn=(referral)|utmcmd=referral|utmcct=/commonauth
>   6. Host:
>   cloudmgt.cloudpreview.wso2.com
>   7. Referer:
>   https://cloudmgt.cloudpreview.wso2.com/cloudmgt/
>   8. User-Agent:
>   Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0)
>   AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 
> Safari/537.36
>
>
> No response headers can be found in the chrome developer tools. But,
> when I open the downloaded file I see the following.
>
> 0
>
> HTTP/1.1 200 OK
> Vary: Accept-Encoding
> Content-Encoding: gzip
> Set-Cookie: JSESSIONID=4B4399DD1E8FA49FB17B6DC9A650DAF8;
> Path=/cloudmgt/; Secure; HttpOnly
> Content-Type: text/html
> Date: Fri, 28 Feb 2014 08:07:09 GMT
> Server: WSO2-PassThrough-HTTP
> Transfer-Encoding: chunked
> Connection: keep-alive
>
> a43
> ã ΩZks⁄8 ˛‹ŒÙ?hΩ; ôçm ó&
> ∞ °$dìê
> inùNFÿ¬à»ñ+… x∑ˇ˝=≤
> 1ó϶€d…Lâ•£sëŒyŒ#ßÔfiæ{˜∂¸S£Ω qsˆ ız¿4?” b
> µ>¢˜_™(˛îı4r ñ≤b ‹ Hê0)ŸMævíؘF ï ˙L óˆæòfF]V◊3‘˝ùûùÁËyRÅßR
> z†∫BAº“4ÁW'∂ v”flı vOˇºâÁ\:¨¶ø«œaıÜG Ç >BÇ∏T G )éZ. Uc µzHıIf›TêÚı0er
> Öå`I¿EÍ‹ki r©P7Rä VŸ µŸ¨Â >ÚâÍs∑bhY ·Xa≈Ë+ ∂Mß 8åGn(»êíë5íºd9‹∑%ˆôî‹» î µ0
> è“ å R„êÄ ÍÇn ÿáßN̉¯ú|çàvbàY cgç›ÕÓ’»s˝À±Sb√Ó†@O:õ£ ≠≥Æ :º=`—̧@//œ
> é/ q„≥ j¥ıëMúçK÷π⁄ö∏ Õ»mÄ/É⁄√È~atB „vÛœQª¡Gß >jÔonúNé0¯yu{}4¡Wª—Yß5> Äû√æÍ
> lM⁄¡‘œ uØè¢∂ø€á 'm ∆/a˛|–fßıãO£Ì ∫9j 
> ıqw„|xS⁄ï≠¡ÊéSj™n£µ›π>ù∏Wó„EΩgù£¢„onwKÕ æ>ŸÓ˙Mu
> flÓ¡…ˆßBÛÙ¢¡µ?€7∞ |,h [É≠˙ßf˝‚¸ÚË͸≤µsºëËjfl'±;3ªG£ˆ}ÏÁ—y≥ ˚ƒ §SØ√~
> ›¬È¯ˆ™Y∏ΩÄ∏ èä∑ùñwÓÔéª0ˆ\ü‚Ò+v |u;t¸bflmѨ úáÓ·==ûlŒ¸Zq∆ø
> ˆw&fi9ax‹QXëYfiuI°∏MJƒ$Æ≥en v\ ; %s úÕç
> ÔÏ‚Ô∂”È¥këÍwàîP`≠∆Ã⁄f}scw∑—(~‹i÷6wõı‚˚˙vc ∑∂ΩUh‘ö;OXJ™:5%£ÆOïQ=kw.
> v2µTíˆ\Mñm]˝”ë≤ùA•≤t
> ì0P ä<({Äá8 7–Çjó;ë 0aiçÚs·ãï¯ì_€õ©OñVc åˇ) Ó`‰Ù±êDUåHıà Ÿ –L$4 ô
> tX1ÆÕO5sü˚!V¥À‡¿ (0\1Z +ƒı»£Ç2Ä #’´NªÑˆ5tïÌd$ùéu''£ -‰Be‘ç®´˙ 
> ¿Œ!f¸∞éh@≈Ãî f§R¥
> ∆
> ].I Ö#Œ®[%â! ∏X J≈2˚_Yfi})úäa«xÏ{ ñT ¿fi'“vI GLŸ–¢àíˆ@⁄CËL\ÿ
> @V16ã÷{´h˘4∞tÛö; }$?l ∞Á-j ô†¥r…É“*Ì/i#fi™8ó_'é•√π%ÇÔ3 v9 Ó¸”™sö’«flzR

[Dev] JaxwsWebappAdmin admin service is replaced with from carbon 4.3.0

[Kasun Gajasinghe]

Hi Krishantha,

JaxwsWebappAdmin admin service is replaced with WebappAdmin from carbon
4.3.0. So, I guess the test automation framework needs to be updated
accordingly.

Thanks,
KasunG

-- 
*Kasun Gajasinghe*
Software Engineer;
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* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] JaxwsWebappAdmin admin service is replaced with from carbon 4.3.0

[Kasun Gajasinghe]

Specifically, the automation api class
- org.wso2.carbon.automation.api.clients.webapp.mgt.JAXWSWebappAdminClient.


On Tue, Mar 4, 2014 at 12:44 PM, Kasun Gajasinghe  wrote:

> Hi Krishantha,
>
> JaxwsWebappAdmin admin service is replaced with WebappAdmin from carbon
> 4.3.0. So, I guess the test automation framework needs to be updated
> accordingly.
>
> Thanks,
> KasunG
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>


-- 
*Kasun Gajasinghe*
Software Engineer;
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* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] JaxwsWebappAdmin admin service is replaced with from carbon 4.3.0

[Krishantha Samaraweera]

Thanks Kasun!! noted.

-Krishantha.


On Tue, Mar 4, 2014 at 12:44 PM, Kasun Gajasinghe  wrote:

> Specifically, the automation api class
> - org.wso2.carbon.automation.api.clients.webapp.mgt.JAXWSWebappAdminClient.
>
>
> On Tue, Mar 4, 2014 at 12:44 PM, Kasun Gajasinghe  wrote:
>
>> Hi Krishantha,
>>
>> JaxwsWebappAdmin admin service is replaced with WebappAdmin from carbon
>> 4.3.0. So, I guess the test automation framework needs to be updated
>> accordingly.
>>
>> Thanks,
>> KasunG
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> WSO2 Inc.; http://wso2.com
>>
>>
>>  ,
>> *email: *
>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>
>>
>>
>> *blog: **http://kasunbg.org* 
>>
>>
>>
>> *twitter: **http://twitter.com/kasunbg* 
>>
>>
>>
>>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>


-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Log mediator changes the content type of the response?

[Chanaka Fernando]

Hi Bhathiya,

With the latest ESB, you can use the log mediator to print JSON messages.
Please refer the below documentation. This documentation has a detailed
description about using JSON with WSO2 ESB.

https://docs.wso2.org/display/ESB481/JSON+Support


Thanks,
Chanaka


On Tue, Mar 4, 2014 at 11:57 AM, Bhathiya Jayasekara wrote:

> Hi devs,
>
> I was trying to run the sample in here [1]. It works fine as mentioned,
> and the client gets the response in json like this.
>
> {"Customer":{"id":123,"name":"John"}}
>
> Then I added a   in out sequence.
>
>   
>  
>  
>   
>
> Now the response which client gets is like this.
>
> 123John
>
> but the Content-Type header is still *application/json*.
>
> Is this a known bug or am I missing something?
>
> [1]
> https://docs.wso2.org/display/ESB460/Using+REST+with+a+Proxy+Service#UsingRESTwithaProxyService-RESTClientandRESTService
>
> Thanks,
>
> --
> *Bhathiya Jayasekara*
> *Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>
> ___
> 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

Re: [Dev] Exception handling on REST call

[Waruna Jayaweera]

Hi Krishantha,
I also need to handle some exceptions on Rest calls.
Is there any default value for HTTP_SC ?
or Do we need to set it based on the filtering of ERROR_CODE.

Thanks,
Waruna


On Tue, Feb 11, 2014 at 4:48 PM, Krishantha Dinesh wrote:

> problem solved. Thanks Dushan for guidance
>
> regex based on [1]
>
>  regex="[1|3|4][0-9][0-9][0-9][0-9][0-9]">
> 
> 
> 
> 
>
> [1] http://docs.wso2.org/display/ESB460/Error+Handling+and+Error+Codes
>
>
>
> On Tue, Feb 11, 2014 at 10:48 AM, Dushan Abeyruwan wrote:
>
>> Hi
>> You can setup HTTP_SC in axis2 context set 400 (which represents bad
>> Request)
>>
>>
>> On Tue, Feb 11, 2014 at 10:42 AM, Krishantha Dinesh > > wrote:
>>
>>> Hi Dushan,
>>> Thanks for prompt reply.
>>> I do agree with you. my concern is http response got which client get on
>>> transport headers.
>>> pls refer below
>>>
>>> This is what client get as exception
>>>
>>> http://cd-rhettige/services/paypal_lookupSale";>
>>>
>>>101503
>>>
>>>Error connecting to the back end
>>>
>>> 
>>>
>>>
>>> 
>>> this is the raw content. pls pay your attention for http status code
>>>
>>> HTTP/1.1 200 OK
>>>
>>> Authorization: Bearer OQaph7mMZJbvNDJ-8u9ICVm4Q4kkJmNj.w5dQJZ5u8E
>>>
>>> Host: cd-rhettige:8280
>>>
>>> Accept-Encoding: gzip,deflate
>>>
>>> Content-Type: application/json
>>>
>>> Date: Tue, 11 Feb 2014 05:06:58 GMT
>>>
>>> Server: WSO2-PassThrough-HTTP
>>>
>>> Transfer-Encoding: chunked
>>>
>>> Connection: Keep-Alive
>>>
>>>
>>>
>>> {  "error_code":"101503",
>>>
>>> "error_message":"Error connecting to the back end"
>>>
>>>  }
>>>
>>>
>>>
>>> On Tue, Feb 11, 2014 at 10:04 AM, Dushan Abeyruwan wrote:
>>>
 Hi,
 No its wrong, we shouldn't response with 200 OK for  exceptions. IMO
 ideal way as I think, to do this by keep the catalog of connector specific
 error code and embedded in the error message and explain those _ _connector
 specific error _ _  catalog in documentation more specifically, and
  returning a generic error with status code to client.

 for error catalogs you could refer [1][2]
 [1]http://www.twilio.com/docs/errors/reference
 [2]
 http://www.stormpath.com/blog/spring-mvc-rest-exception-handling-best-practices-part-1
 e.g



 {
 "status": 404,
* "code": 40483,*
 "message": "Oops! It looks like that file does not exist.",
 "developerMessage": "File resource for path /uploads/foobar.txt does 
 not exist.  Please wait 10 minutes until the upload batch completes before 
 checking again.",
 "moreInfo": "http://www.mycompany.com/errors/40483";
 }



 On Tue, Feb 11, 2014 at 9:51 AM, Krishantha Dinesh <
 kr...@krishantha.com> wrote:

> Hi Dushan/Dev
> I tried ur solution and its work. but i have other question. when it
> catch FAULT (500 error) on return message of client http code is 200 OK
> for example let say endpoint is fail the it catch that fault. but in
> client point of view http respond code of his response is 200
>
> other than 500 client getting correct http response code. the problem
> may be this is originate by ESB it self than come as response to ESB. btw
> is there any solution for this.
>
>
>
> On Sat, Feb 8, 2014 at 7:30 PM, Dushan Abeyruwan wrote:
>
>> Hi Kirshantha,
>>   Handling fault has two flavors,
>>
>>- Handle internal fault such as service EP not available and all
>>the issues related .
>>- Handle Service faults.
>>
>>
>>   Ideally when BE is SOAP and if it returns SOAP fault in order to
>> handle such queries we normally append FORCE_ERROR_ON_SOAP_FAULT 
>> property,
>> this works only of BE return Service faults and when such happen if we 
>> need
>> to divert such responses to the faultSequence that we have defined.
>>On the other hand if that is RESTful BE,  we do not have a inbuilt
>> function  to determine whether its a fault at transport level, so the
>> workaround that we normally do is to use the Filter base on the HTTP_SC.
>>   If you look at [1] status codes represents 100 series and 200-
>> series regards as non faulty responses, and other than that we can
>> determine them as faults or defect, to overcome such station when deal 
>> with
>> RESTful services personally I am using filters i.e
>>
>> OutSequence ..etc , below logic just evaluates the response and if
>> that not falls between 200 series normally you can add your customize
>> faulty response logic ..
>>
>>  
>> 
>>
>>
>>- can include payload
>>   - can setup HTTP_SC to axis2 context
>>   - can use  mediator to reply client with error.
>>
>>  ..
>>  ..
>>
>>  

Re: [Dev] Log mediator changes the content type of the response?

[Isuru Udana]

Hi Bathiya,

When there is no content-aware mediators present in the message flow (in
here at outSequence), message get parsed as it is through the ESB without
building. And when you put a log mediator, since log is a content-aware
mediator, message builder get invoked. So issue is something to do with
builders and content-type.
You can enable wire logs for ESB and see the wire level messages in the
response path to get a clue.






On Tue, Mar 4, 2014 at 1:00 PM, Chanaka Fernando  wrote:

> Hi Bhathiya,
>
> With the latest ESB, you can use the log mediator to print JSON messages.
> Please refer the below documentation. This documentation has a detailed
> description about using JSON with WSO2 ESB.
>
> https://docs.wso2.org/display/ESB481/JSON+Support
>
>
> Thanks,
> Chanaka
>
>
>  On Tue, Mar 4, 2014 at 11:57 AM, Bhathiya Jayasekara 
> wrote:
>
>>  Hi devs,
>>
>> I was trying to run the sample in here [1]. It works fine as mentioned,
>> and the client gets the response in json like this.
>>
>> {"Customer":{"id":123,"name":"John"}}
>>
>> Then I added a   in out sequence.
>>
>>   
>>  
>>  
>>   
>>
>> Now the response which client gets is like this.
>>
>> 123John
>>
>> but the Content-Type header is still *application/json*.
>>
>> Is this a known bug or am I missing something?
>>
>> [1]
>> https://docs.wso2.org/display/ESB460/Using+REST+with+a+Proxy+Service#UsingRESTwithaProxyService-RESTClientandRESTService
>>
>> Thanks,
>>
>> --
>> *Bhathiya Jayasekara*
>> *Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185 <%2B94715478185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>> ___
>> 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
>
>


-- 
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev