Re: [Dev] cassandra.yaml default cluster name and cassandra-component.xml default cluster name does not match

[Deependra Ariyadewa]

There is not requirement to match the Cluster name we refer in the Hector
to the Cluster name in Cassandra but it is good to have same name to make
less confusions.

Thanks,

Deependra.


On Wed, Nov 13, 2013 at 12:54 PM, Chamara Ariyarathne wrote:

> https://wso2.org/jira/browse/SS-197
>
> --
> *Chamara Ariyarathne*
> Senior Software Engineer - QA;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; *+94772786766 <%2B94772786766>*
>



-- 
Deependra Ariyadewa
WSO2, Inc. http://wso2.com/ http://wso2.org

email d...@wso2.com; cell +94 71 403 5996 ;
Blog http://risenfall.wordpress.com/
PGP info: KeyID: 'DC627E6F'

*WSO2 - Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] cassandra.yaml default cluster name and cassandra-component.xml default cluster name does not match

[Chamara Ariyarathne]

Is it the same way the hector client work in BAM also ?


On Wed, Nov 13, 2013 at 2:02 PM, Deependra Ariyadewa  wrote:

> There is not requirement to match the Cluster name we refer in the Hector
> to the Cluster name in Cassandra but it is good to have same name to make
> less confusions.
>
> Thanks,
>
> Deependra.
>
>
> On Wed, Nov 13, 2013 at 12:54 PM, Chamara Ariyarathne 
> wrote:
>
>> https://wso2.org/jira/browse/SS-197
>>
>> --
>> *Chamara Ariyarathne*
>> Senior Software Engineer - QA;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; *+94772786766 <%2B94772786766>*
>>
>
>
>
> --
> Deependra Ariyadewa
> WSO2, Inc. http://wso2.com/ http://wso2.org
>
> email d...@wso2.com; cell +94 71 403 5996 ;
> Blog http://risenfall.wordpress.com/
> PGP info: KeyID: 'DC627E6F'
>
> *WSO2 - Lean . Enterprise . Middleware*
>



-- 
*Chamara Ariyarathne*
Senior Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; *+94772786766*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] cassandra.yaml default cluster name and cassandra-component.xml default cluster name does not match

[Chamara Ariyarathne]

On Wed, Nov 13, 2013 at 2:21 PM, Chamara Ariyarathne wrote:

> Is it the same way the hector client work in BAM also ?
>

>
> On Wed, Nov 13, 2013 at 2:02 PM, Deependra Ariyadewa wrote:
>
>> There is not requirement to match the Cluster name we refer in the Hector
>> to the Cluster name in Cassandra but it is good to have same name to make
>> less confusions.
>>
>
If so the docs also need to be modifed.
http://docs.wso2.org/display/SS110/Changing+the+Default+Cassandra+Configuration

Here it is said that the Hector reference name is mandatory.

>
>> Thanks,
>>
>> Deependra.
>>
>>
>> On Wed, Nov 13, 2013 at 12:54 PM, Chamara Ariyarathne 
>> wrote:
>>
>>> https://wso2.org/jira/browse/SS-197
>>>
>>> --
>>> *Chamara Ariyarathne*
>>> Senior Software Engineer - QA;
>>> WSO2 Inc; http://www.wso2.com/.
>>> Mobile; *+94772786766 <%2B94772786766>*
>>>
>>
>>
>>
>> --
>> Deependra Ariyadewa
>> WSO2, Inc. http://wso2.com/ http://wso2.org
>>
>> email d...@wso2.com; cell +94 71 403 5996 ;
>> Blog http://risenfall.wordpress.com/
>> PGP info: KeyID: 'DC627E6F'
>>
>> *WSO2 - Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *Chamara Ariyarathne*
> Senior Software Engineer - QA;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; *+94772786766 <%2B94772786766>*
>



-- 
*Chamara Ariyarathne*
Senior Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; *+94772786766*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ConcurrentModificationException while initializing w/m ESB 4.8.0 Pre RC1 build 20131112

[Kishanthan Thangarajah]

Looks like DeploymentEngine#addDeployer method is called from all the
synapse artifact related deployer components, which can cause this
concurrent modification exception intermittently. I can reproduce this in
ESB with some sleep introduced at axis2 level for RepositoryListener#
loadOtherDirectories.

A fix has to be added at axis2 level, since there are number of places in
synapse initialization process where the addDeployer method is called.

We can properly handle this at axis2 level by synchronizing the deployerMap
object in places (loadOtherDirectories & addDeployer).

But then the question would be will this cause any impact on the
performance? Since addDeployer only gets called during server start-up and
tenant loading, I think we can go ahead.

Thoughts?

Thanks,
Kishanthan.


On Wed, Nov 13, 2013 at 9:38 AM, Dushan Abeyruwan  wrote:

> rtifact repository at :
> /home/dushan/poc/server/4.1.2-pack/connnector-works/worker_mgr/wso2esb-4.8.0-mgr/repository/tenants/1/synapse-configs/default
> [2013-11-13 09:33:02,105]  INFO - Axis2SynapseController Loading mediator
> extensions...
> [2013-11-13 09:33:02,108] ERROR - CarbonDeploymentSchedulerTask Error
> while running deployment scheduler..
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
>  at java.util.HashMap$EntryIterator.next(HashMap.java:834)
> at java.util.HashMap$EntryIterator.next(HashMap.java:832)
>  at
> org.apache.axis2.deployment.RepositoryListener.loadOtherDirectories(RepositoryListener.java:270)
> at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:253)
>  at
> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
>  at
> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
>  at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>  at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>  at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>  at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> [2013-11-13 09:33:02,250]  INFO - LibraryArtifactDeployer Synapse Library
> named '{org.wso2.carbon.connectors}salesforce' has been deployed from file
> :
> /home/dushan/poc/server/4.1.2-pack/connnector-works/worker_mgr/wso2esb-4.8.0-mgr/repository/tenants/1/synapse-libs/salesforce-connector.zip
> [2013-11-13 09:33:02,439]  INFO - LibraryArtifactDeployer Synapse Library
> named '{org.wso2.carbon.connectors}googlespreadsheet' has been deployed
> from file :
> /home/dushan/poc/server/4.1.2-pack/connnector-works/worker_mgr/wso2esb-4.8.0-mgr/repository/tenants/1/synapse-libs/googlespreadsheet-connect
>
> Cheers,
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ *
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>



-- 
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] cassandra.yaml default cluster name and cassandra-component.xml default cluster name does not match

[Deependra Ariyadewa]

On Wed, Nov 13, 2013 at 2:21 PM, Chamara Ariyarathne wrote:

> Is it the same way the hector client work in BAM also ?
>

Yes, This is a Hector feature.

>
>
> On Wed, Nov 13, 2013 at 2:02 PM, Deependra Ariyadewa wrote:
>
>> There is not requirement to match the Cluster name we refer in the Hector
>> to the Cluster name in Cassandra but it is good to have same name to make
>> less confusions.
>>
>> Thanks,
>>
>> Deependra.
>>
>>
>> On Wed, Nov 13, 2013 at 12:54 PM, Chamara Ariyarathne 
>> wrote:
>>
>>> https://wso2.org/jira/browse/SS-197
>>>
>>> --
>>> *Chamara Ariyarathne*
>>> Senior Software Engineer - QA;
>>> WSO2 Inc; http://www.wso2.com/.
>>> Mobile; *+94772786766 <%2B94772786766>*
>>>
>>
>>
>>
>> --
>> Deependra Ariyadewa
>> WSO2, Inc. http://wso2.com/ http://wso2.org
>>
>> email d...@wso2.com; cell +94 71 403 5996 ;
>> Blog http://risenfall.wordpress.com/
>> PGP info: KeyID: 'DC627E6F'
>>
>> *WSO2 - Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *Chamara Ariyarathne*
> Senior Software Engineer - QA;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; *+94772786766 <%2B94772786766>*
>



-- 
Deependra Ariyadewa
WSO2, Inc. http://wso2.com/ http://wso2.org

email d...@wso2.com; cell +94 71 403 5996 ;
Blog http://risenfall.wordpress.com/
PGP info: KeyID: 'DC627E6F'

*WSO2 - Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon 4.2.0 branch build failure

[Sameera Jayasoma]

When I install IntellijIDEA, it asked me to install Java and I let him
install. So it installed 1.6 in the following location

/System/Library/Java/JavaVirtualMachines/1.6.0.jdk

Then I installed JDK 1.7 and it got installed to the following location.


/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk




I tried to install JDK 1.6 using the second step as described in the
following description from [1]


"1) As I recall, the first time you do something that needs Java the OS
will ask if you want to install it, and version 6 is what you get.
According to this
page,
typing java -version in the Terminal is enough to trigger the prompt.


2) For the JDK (and not the runtime), you'll need to log into
developer.apple.com ,
search for java, and download the Java for OS X 2012-006 Developer Package.
I just did this on my MacBook and now havejavac 1.6.0_37."



Thanks,
Sameera.

[1] http://stackoverflow.com/questions/13653597/jdk-6-on-mountain-lion




On Wed, Nov 13, 2013 at 12:58 PM, Afkham Azeez  wrote:

> From where did you download 1.6?
>
>
> On Wed, Nov 13, 2013 at 12:46 PM, Sameera Jayasoma wrote:
>
>> Yup. I did I am running both JDK 1.6 and JDK 1.7.
>>
>>
>> On Wed, Nov 13, 2013 at 11:50 AM, Afkham Azeez  wrote:
>>
>>> Anybody on Mavericks figured out how to find & install JDK 1.6?
>>>
>>>
>>> On Wed, Nov 13, 2013 at 9:32 AM, Asela Pathberiya wrote:
>>>
 Hi Azeez,

 I am sorry.  I have both JDKs in machine and just see that it has been
 built success with from 1.6, (not 1.7). It means that it fails with 1.7.
 AFAIK there are some other issues when we are building 1.7.  I guess we
 have mentioned it in the doc as well [1].  If we are planing to support for
 1.7 to build the source,  we must fix this in next release.

 [1] http://docs.wso2.org/display/Carbon420/Installation+Prerequisites

 Thanks,
 Asela.



 On Wed, Nov 13, 2013 at 8:35 AM, Afkham Azeez  wrote:

>  java version "1.7.0_45"
>
> Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
>
> Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
>
>
> On Wed, Nov 13, 2013 at 8:11 AM, Asela Pathberiya wrote:
>
>>
>> On Wed, Nov 13, 2013 at 6:21 AM, Afkham Azeez  wrote:
>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.1:compile
>>> (default-compile) on project wss4j: Compilation failure: Compilation
>>> failure:
>>>
>>> [ERROR]
>>> /Users/azeez/projects/wso2/public2/kernel/trunk/branches/4.2.0/dependencies/wss4j/1.5.11-wso2v6/src/org/apache/ws/security/kerberos/KrbTicketDecoder.java:[10,24]
>>> EncryptionKey is internal proprietary API and may be removed in a future
>>> release
>>>
>>> [ERROR]
>>>
>>> [ERROR]
>>> /Users/azeez/projects/wso2/public2/kernel/trunk/branches/4.2.0/dependencies/wss4j/1.5.11-wso2v6/src/org/apache/ws/security/kerberos/KrbTicketDecoder.java:[11,33]
>>> EncTicketPart is internal proprietary API and may be removed in a future
>>> release
>>>
>>
>> We have experienced this as "[WARNING]"  messages not errors..  I
>> just tried this with JDK 1.7 and mvn clean install.
>>
>> Thanks,
>> Asela.
>>
>>
>>
>>> [ERROR]
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * *
>>> *email: **az...@wso2.com* 
>>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>>> *http://blog.afkham.org* 
>>> *twitter: 
>>> **http://twitter.com/afkham_azeez*
>>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>> *
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>> Asela
>>
>> ATL
>> Mobile : +94 777 625 933
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* 
> *twitter: 
> **http://twitter.com/afkham_azeez*
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



 --
 Thanks & Regards,
 Asela

 ATL
 Mobile : +94 777 625 933

>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> 

[Dev] [Turing][Chunk 04] Build failure in Proxy Services Core Feature 4.2.0

[Hasitha Aravinda]

Hi,

Getting following error in clean repo. Please have a look.

[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 17.547s
[INFO] Finished at: Wed Nov 13 15:27:51 IST 2013
[INFO] Final Memory: 148M/1322M
[INFO]

[ERROR] Failed to execute goal on project
org.wso2.carbon.proxyadmin.server.feature: Could not resolve dependencies
for project
org.wso2.carbon:org.wso2.carbon.proxyadmin.server.feature:pom:4.2.0: *Could
not find artifact
org.wso2.carbon:org.wso2.carbon.proxyadmin.common:jar:4.2.0* in wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.

Thanks,
Hasitha.


-- 
Hasitha Aravinda,
Software Engineer,
WSO2 Inc.
Email: hasi...@wso2.com
Mobile: +94 71 8 210 200
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] cassandra.yaml default cluster name and cassandra-component.xml default cluster name does not match

[Prabath Abeysekera]

Hi Guys,

I guess it's perfectly fine to have those parameter values the way we
already have 'em, given that we clearly mention in docs that there's no
direct relationship between those params (and maybe as a comment in the
configuration file itself too). Because, if we make the values of those two
parameters the same, then it sort of implies that they both correspond to
the same configuration, which is not valid, I believe.

However, there seems to be a few other usability issues with these
configuration files which sort of related to the issue raised.

* "cassandra-component.xml" is used to configure some Hector related
parameters so it would be more intuitive to have it renamed as
"hector-config.xml" or something similar.

* The contents of the aforementioned file too need to be modified
reflecting the first point. Maybe we should replace "Cassandra" which is
currently the top level element, to be something like "HectorConfig".

I guess we need to fix these in a future release. Deep, WDYT?


Created a JIRA [1] to track this.

[1] https://wso2.org/jira/browse/SS-199


Cheers,
Prabath


On Wed, Nov 13, 2013 at 3:06 PM, Deependra Ariyadewa  wrote:

>
>
>
> On Wed, Nov 13, 2013 at 2:21 PM, Chamara Ariyarathne wrote:
>
>> Is it the same way the hector client work in BAM also ?
>>
>
> Yes, This is a Hector feature.
>
>>
>>
>> On Wed, Nov 13, 2013 at 2:02 PM, Deependra Ariyadewa wrote:
>>
>>> There is not requirement to match the Cluster name we refer in the
>>> Hector to the Cluster name in Cassandra but it is good to have same name to
>>> make less confusions.
>>>
>>> Thanks,
>>>
>>> Deependra.
>>>
>>>
>>> On Wed, Nov 13, 2013 at 12:54 PM, Chamara Ariyarathne >> > wrote:
>>>
 https://wso2.org/jira/browse/SS-197

 --
 *Chamara Ariyarathne*
 Senior Software Engineer - QA;
 WSO2 Inc; http://www.wso2.com/.
 Mobile; *+94772786766 <%2B94772786766>*

>>>
>>>
>>>
>>> --
>>> Deependra Ariyadewa
>>> WSO2, Inc. http://wso2.com/ http://wso2.org
>>>
>>> email d...@wso2.com; cell +94 71 403 5996 ;
>>> Blog http://risenfall.wordpress.com/
>>> PGP info: KeyID: 'DC627E6F'
>>>
>>> *WSO2 - Lean . Enterprise . Middleware*
>>>
>>
>>
>>
>> --
>> *Chamara Ariyarathne*
>> Senior Software Engineer - QA;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; *+94772786766 <%2B94772786766>*
>>
>
>
>
> --
> Deependra Ariyadewa
> WSO2, Inc. http://wso2.com/ http://wso2.org
>
> email d...@wso2.com; cell +94 71 403 5996 ;
> Blog http://risenfall.wordpress.com/
> PGP info: KeyID: 'DC627E6F'
>
> *WSO2 - Lean . Enterprise . Middleware*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Prabath Abeysekara
Associate Technical Lead, Data TG.
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Turing][Chunk 04] Build failure in Proxy Services Core Feature 4.2.0

[Hasitha Aravinda]

HI,

Chunk 4 feature pom has different versions of proxyadmin feature[1] . what
is the correct one. ?

../../../features/proxyadmin

../../../features/proxyadmin/org.wso2.carbon.proxyadmin.ui.feature/4.2.1

../../../features/proxyadmin/org.wso2.carbon.proxyadmin.server.feature/4.2.1

../../../features/proxyadmin/org.wso2.carbon.proxyadmin.feature/4.2.2


[1] -
https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/product-releases/chunk-04/features/pom.xml

Thanks,
Hasitha.


On Wed, Nov 13, 2013 at 3:33 PM, Hasitha Aravinda  wrote:

> Hi,
>
> Getting following error in clean repo. Please have a look.
>
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 17.547s
> [INFO] Finished at: Wed Nov 13 15:27:51 IST 2013
> [INFO] Final Memory: 148M/1322M
> [INFO]
> 
> [ERROR] Failed to execute goal on project
> org.wso2.carbon.proxyadmin.server.feature: Could not resolve dependencies
> for project
> org.wso2.carbon:org.wso2.carbon.proxyadmin.server.feature:pom:4.2.0: *Could
> not find artifact
> org.wso2.carbon:org.wso2.carbon.proxyadmin.common:jar:4.2.0* in
> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
>
> Thanks,
> Hasitha.
>
>
> --
> Hasitha Aravinda,
> Software Engineer,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile: +94 71 8 210 200
>
>
>


-- 
Hasitha Aravinda,
Software Engineer,
WSO2 Inc.
Email: hasi...@wso2.com
Mobile: +94 71 8 210 200
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] cassandra.yaml default cluster name and cassandra-component.xml default cluster name does not match

[Deependra Ariyadewa]

On Wed, Nov 13, 2013 at 3:33 PM, Prabath Abeysekera wrote:

> Hi Guys,
>
> I guess it's perfectly fine to have those parameter values the way we
> already have 'em, given that we clearly mention in docs that there's no
> direct relationship between those params (and maybe as a comment in the
> configuration file itself too). Because, if we make the values of those two
> parameters the same, then it sort of implies that they both correspond to
> the same configuration, which is not valid, I believe.
>
> However, there seems to be a few other usability issues with these
> configuration files which sort of related to the issue raised.
>
> * "cassandra-component.xml" is used to configure some Hector related
> parameters so it would be more intuitive to have it renamed as
> "hector-config.xml" or something similar.
>
> * The contents of the aforementioned file too need to be modified
> reflecting the first point. Maybe we should replace "Cassandra" which is
> currently the top level element, to be something like "HectorConfig".
>
> I guess we need to fix these in a future release. Deep, WDYT?
>

+1

Thanks,

Deependra.

>
>
> Created a JIRA [1] to track this.
>
> [1] https://wso2.org/jira/browse/SS-199
>
>
> Cheers,
> Prabath
>
>
> On Wed, Nov 13, 2013 at 3:06 PM, Deependra Ariyadewa wrote:
>
>>
>>
>>
>> On Wed, Nov 13, 2013 at 2:21 PM, Chamara Ariyarathne 
>> wrote:
>>
>>> Is it the same way the hector client work in BAM also ?
>>>
>>
>> Yes, This is a Hector feature.
>>
>>>
>>>
>>> On Wed, Nov 13, 2013 at 2:02 PM, Deependra Ariyadewa wrote:
>>>
 There is not requirement to match the Cluster name we refer in the
 Hector to the Cluster name in Cassandra but it is good to have same name to
 make less confusions.

 Thanks,

 Deependra.


 On Wed, Nov 13, 2013 at 12:54 PM, Chamara Ariyarathne <
 chama...@wso2.com> wrote:

> https://wso2.org/jira/browse/SS-197
>
> --
> *Chamara Ariyarathne*
> Senior Software Engineer - QA;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; *+94772786766 <%2B94772786766>*
>



 --
 Deependra Ariyadewa
 WSO2, Inc. http://wso2.com/ http://wso2.org

 email d...@wso2.com; cell +94 71 403 5996 ;
 Blog http://risenfall.wordpress.com/
 PGP info: KeyID: 'DC627E6F'

 *WSO2 - Lean . Enterprise . Middleware*

>>>
>>>
>>>
>>> --
>>> *Chamara Ariyarathne*
>>> Senior Software Engineer - QA;
>>> WSO2 Inc; http://www.wso2.com/.
>>> Mobile; *+94772786766 <%2B94772786766>*
>>>
>>
>>
>>
>> --
>> Deependra Ariyadewa
>> WSO2, Inc. http://wso2.com/ http://wso2.org
>>
>> email d...@wso2.com; cell +94 71 403 5996 ;
>> Blog http://risenfall.wordpress.com/
>> PGP info: KeyID: 'DC627E6F'
>>
>> *WSO2 - Lean . Enterprise . Middleware*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Prabath Abeysekara
> Associate Technical Lead, Data TG.
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>



-- 
Deependra Ariyadewa
WSO2, Inc. http://wso2.com/ http://wso2.org

email d...@wso2.com; cell +94 71 403 5996 ;
Blog http://risenfall.wordpress.com/
PGP info: KeyID: 'DC627E6F'

*WSO2 - Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ConcurrentModificationException while initializing w/m ESB 4.8.0 Pre RC1 build 20131112

[Kishanthan Thangarajah]

We already have this reported at https://wso2.org/jira/browse/CARBON-14435
 and https://issues.apache.org/jira/browse/AXIS2-5152.


On Wed, Nov 13, 2013 at 2:43 PM, Kishanthan Thangarajah  wrote:

> Looks like DeploymentEngine#addDeployer method is called from all the
> synapse artifact related deployer components, which can cause this
> concurrent modification exception intermittently. I can reproduce this in
> ESB with some sleep introduced at axis2 level for RepositoryListener#
> loadOtherDirectories.
>
> A fix has to be added at axis2 level, since there are number of places in
> synapse initialization process where the addDeployer method is called.
>
> We can properly handle this at axis2 level by synchronizing the
> deployerMap object in places (loadOtherDirectories & addDeployer).
>
> But then the question would be will this cause any impact on the
> performance? Since addDeployer only gets called during server start-up and
> tenant loading, I think we can go ahead.
>
>  Thoughts?
>
> Thanks,
> Kishanthan.
>
>
> On Wed, Nov 13, 2013 at 9:38 AM, Dushan Abeyruwan  wrote:
>
>> rtifact repository at :
>> /home/dushan/poc/server/4.1.2-pack/connnector-works/worker_mgr/wso2esb-4.8.0-mgr/repository/tenants/1/synapse-configs/default
>> [2013-11-13 09:33:02,105]  INFO - Axis2SynapseController Loading mediator
>> extensions...
>> [2013-11-13 09:33:02,108] ERROR - CarbonDeploymentSchedulerTask Error
>> while running deployment scheduler..
>> java.util.ConcurrentModificationException
>> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
>>  at java.util.HashMap$EntryIterator.next(HashMap.java:834)
>> at java.util.HashMap$EntryIterator.next(HashMap.java:832)
>>  at
>> org.apache.axis2.deployment.RepositoryListener.loadOtherDirectories(RepositoryListener.java:270)
>> at
>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:253)
>>  at
>> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
>> at
>> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
>>  at
>> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
>> at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
>>  at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>>  at
>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>>  at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>>  at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>  at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>> [2013-11-13 09:33:02,250]  INFO - LibraryArtifactDeployer Synapse Library
>> named '{org.wso2.carbon.connectors}salesforce' has been deployed from file
>> :
>> /home/dushan/poc/server/4.1.2-pack/connnector-works/worker_mgr/wso2esb-4.8.0-mgr/repository/tenants/1/synapse-libs/salesforce-connector.zip
>> [2013-11-13 09:33:02,439]  INFO - LibraryArtifactDeployer Synapse Library
>> named '{org.wso2.carbon.connectors}googlespreadsheet' has been deployed
>> from file :
>> /home/dushan/poc/server/4.1.2-pack/connnector-works/worker_mgr/wso2esb-4.8.0-mgr/repository/tenants/1/synapse-libs/googlespreadsheet-connect
>>
>> Cheers,
>> Dushan Abeyruwan
>> Associate Tech Lead
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com/ *
>> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Senior Software Engineer,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>



-- 
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon 4.2.0 branch build failure

[Sameera Jayasoma]

More proof :)

*JAVA_HOME environment variable is set to
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home*

CARBON_HOME environment variable is set to
/Users/sameera/Work/wso2/distributions/carbon/wso2carbon-4.2.0

[2013-11-13 16:27:11,934]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
Carbon...

[2013-11-13 16:27:11,936]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
Mac OS X 10.9, x86_64

*[2013-11-13 16:27:11,936]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home*

[2013-11-13 16:27:11,936]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
1.6.0_65

[2013-11-13 16:27:11,936]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
Java HotSpot(TM) 64-Bit Server VM 20.65-b04-462,Apple Inc.


.bash_profile


export
JAVA_HOME_17="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"

export
JAVA_HOME_16="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"

export JAVA_HOME=$JAVA_HOME_17


On Wed, Nov 13, 2013 at 3:26 PM, Sameera Jayasoma  wrote:

> When I install IntellijIDEA, it asked me to install Java and I let him
> install. So it installed 1.6 in the following location
>
> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk
>
> Then I installed JDK 1.7 and it got installed to the following location.
>
>
> /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk
>
>
>
>
> I tried to install JDK 1.6 using the second step as described in the
> following description from [1]
>
>
> "1) As I recall, the first time you do something that needs Java the OS
> will ask if you want to install it, and version 6 is what you get.
> According to this 
> page,
> typing java -version in the Terminal is enough to trigger the prompt.
>
>
> 2) For the JDK (and not the runtime), you'll need to log into
> developer.apple.com ,
> search for java, and download the Java for OS X 2012-006 Developer
> Package. I just did this on my MacBook and now havejavac 1.6.0_37."
>
>
>
> Thanks,
> Sameera.
>
> [1] http://stackoverflow.com/questions/13653597/jdk-6-on-mountain-lion
>
>
>
>
> On Wed, Nov 13, 2013 at 12:58 PM, Afkham Azeez  wrote:
>
>> From where did you download 1.6?
>>
>>
>> On Wed, Nov 13, 2013 at 12:46 PM, Sameera Jayasoma wrote:
>>
>>> Yup. I did I am running both JDK 1.6 and JDK 1.7.
>>>
>>>
>>> On Wed, Nov 13, 2013 at 11:50 AM, Afkham Azeez  wrote:
>>>
 Anybody on Mavericks figured out how to find & install JDK 1.6?


 On Wed, Nov 13, 2013 at 9:32 AM, Asela Pathberiya wrote:

> Hi Azeez,
>
> I am sorry.  I have both JDKs in machine and just see that it has been
> built success with from 1.6, (not 1.7). It means that it fails with 1.7.
> AFAIK there are some other issues when we are building 1.7.  I guess we
> have mentioned it in the doc as well [1].  If we are planing to support 
> for
> 1.7 to build the source,  we must fix this in next release.
>
> [1] http://docs.wso2.org/display/Carbon420/Installation+Prerequisites
>
> Thanks,
> Asela.
>
>
>
> On Wed, Nov 13, 2013 at 8:35 AM, Afkham Azeez  wrote:
>
>>  java version "1.7.0_45"
>>
>> Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
>>
>> Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
>>
>>
>> On Wed, Nov 13, 2013 at 8:11 AM, Asela Pathberiya wrote:
>>
>>>
>>> On Wed, Nov 13, 2013 at 6:21 AM, Afkham Azeez wrote:
>>>
 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.1:compile
 (default-compile) on project wss4j: Compilation failure: Compilation
 failure:

 [ERROR]
 /Users/azeez/projects/wso2/public2/kernel/trunk/branches/4.2.0/dependencies/wss4j/1.5.11-wso2v6/src/org/apache/ws/security/kerberos/KrbTicketDecoder.java:[10,24]
 EncryptionKey is internal proprietary API and may be removed in a 
 future
 release

 [ERROR]

 [ERROR]
 /Users/azeez/projects/wso2/public2/kernel/trunk/branches/4.2.0/dependencies/wss4j/1.5.11-wso2v6/src/org/apache/ws/security/kerberos/KrbTicketDecoder.java:[11,33]
 EncTicketPart is internal proprietary API and may be removed in a 
 future
 release

>>>
>>> We have experienced this as "[WARNING]"  messages not errors..  I
>>> just tried this with JDK 1.7 and mvn clean install.
>>>
>>> Thanks,
>>> Asela.
>>>
>>>
>>>
 [ERROR]

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * 

[Dev] SS-1.1.0 pack for QA

[Bhathiya Jayasekara]

Hi all,

Please find the pack URL below.

https://svn.wso2.org/repos/wso2/scratch/ss-dev/SS-1.1.0-QA/2/wso2ss-1.1.0.zip

Thanks,
Bhathiya

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

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

[Dev] [dev] Servicemeta file not deleting properly {https://wso2.org/jira/browse/ESBJAVA-2616}

[Dushan Abeyruwan]

Hi All,

It seems like service metatafile not deleted properly when deleting proxy
as in AbstractFilePersistenceManager. it looks *detach* nodes *instead of
deleting* is this a correct behavior..


 public boolean delete(String resourceId, String xpathStr) {
ResourceFileData fileData = resourceMap.get(resourceId);

try {
if (fileData != null && fileData.isTransactionStarted()) {
OMElement sgElement = fileData.getOMElement();
AXIOMXPath xpathExpr = new AXIOMXPath(xpathStr);
OMElement el = (OMElement)
xpathExpr.selectSingleNode(sgElement);
if (el == null) {
return false;
}
if (el.getParent() == null) { //this is the root element
fileData.setOMElement(null);
} *else {*
*el.detach();*
*}*
setMetaFileModification(resourceId);
return true;
} else {
log.error("The Element specified by path not found or a
transaction isn't started yet. " +
xpathStr);
return false;
}
} catch (JaxenException e) {
log.error("Error parsing xpath string " + resourceId +
xpathStr, e);
return false;
}
}


Cheers,
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Compilation error in P2-profile in SS

[Shani Ranasinghe]

Hi,

I get a  $subject when compiling the ss p2-profile. Please find the stack
trace below.

[INFO] Running Equinox P2 Publisher Application for Repository Generation
[INFO] Command line:
/bin/sh -c cd
/home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile
&& /opt/java/jdk1.6.0_45/jre/bin/java -jar
/home/shani/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
-nosplash -application
org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher -source
/home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile/target/tmp.1384344139652/featureExtract
-metadataRepository
file:/home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile/target/p2-repo
-metadataRepositoryName wso2ss-p2-profile -artifactRepository
file:/home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile/target/p2-repo
-artifactRepositoryName wso2ss-p2-profile -publishArtifacts
-publishArtifactRepository -compress -append
Generating metadata for ..
Status ERROR: org.eclipse.equinox.p2.artifact.repository code=0 For input
string: "${exp" java.lang.NumberFormatException: For input string: "${exp"

Product publishing ended with the following exception:
java.lang.NumberFormatException: For input string: "${exp"
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:449)
at java.lang.Integer.parseInt(Integer.java:499)
at org.osgi.framework.Version.(Version.java:127)
at org.osgi.framework.Version.parseVersion(Version.java:225)
at
org.eclipse.osgi.internal.resolver.StateBuilder.addExportPackages(StateBuilder.java:338)
at
org.eclipse.osgi.internal.resolver.StateBuilder.createExportPackages(StateBuilder.java:320)
at
org.eclipse.osgi.internal.resolver.StateBuilder.createBundleDescription(StateBuilder.java:110)
at
org.eclipse.osgi.internal.resolver.StateObjectFactoryImpl.createBundleDescription(StateObjectFactoryImpl.java:32)
at
org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.createBundleDescription(BundlesAction.java:531)
at
org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.createBundleDescription(BundlesAction.java:546)
at
org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.getBundleDescriptions(BundlesAction.java:846)
at
org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.perform(BundlesAction.java:657)
at
org.eclipse.equinox.p2.publisher.Publisher$ArtifactProcess.run(Publisher.java:207)
at
org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.executeBatch(SimpleArtifactRepository.java:1294)
at
org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher.java:231)
at
org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:283)
at
org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:253)
at
org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.start(AbstractPublisherApplication.java:315)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.equinox.internal.app.AnyThreadAppLauncher.run(AnyThreadAppLauncher.java:26)
at java.lang.Thread.run(Thread.java:662)

Product publisher application was executed with the following arguments:
-source
/home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile/target/tmp.1384344139652/featureExtract
-metadataRepository
file:/home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile/target/p2-repo
-metadataRepositoryName
wso2ss-p2-profile
-artifactRepository
file:/home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile/target/p2-repo
-artifactRepositoryName
wso2ss-p2-profile
-publishArtifacts
-publishArtifactRepository
-compress
-append
[ERROR] P2 publisher return code was 1
org.apache.maven.plugin.MojoFailureException: P2 publisher return code was 1
at
org.wso2.maven.p2.RepositoryGenMojo.generateRepository(RepositoryGenMojo.java:255)
at
org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:204)
at
org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleMo

Re: [Dev] [dev] Servicemeta file not deleting properly {https://wso2.org/jira/browse/ESBJAVA-2616}

[Dushan Abeyruwan]

commitTransaction has some relation with the above method, which means
el.detach means not setting to  fileData.setOMElement(null); thus skipping
the deletion operation

 public synchronized void commitTransaction(String resourceId) throws
PersistenceException {

if (fileData != null &&* fileData.getOMElement() == null) {*   //the
resource has been deleted
String childFilePath =
getFilePathFromResourceId(resourceId);
f = new File(metafilesDir, childFilePath);
if (f.exists()) {
  *  FileUtils.forceDelete(f);*
}

if(log.isDebugEnabled()){
log.debug("Successfully deleted persisted resource
contents " + resourceId + " " + f.getName());
}
resourceMap.remove(resourceId);
return;
} else if (fileData != null) {
f = fileData.getFile();
} else {
resourceMap.remove(resourceId);
throw new PersistenceException("persistence data not
found");
}


On Wed, Nov 13, 2013 at 5:19 PM, Dushan Abeyruwan  wrote:

> Hi All,
>
> It seems like service metatafile not deleted properly when deleting proxy
> as in AbstractFilePersistenceManager. it looks *detach* nodes *instead of
> deleting* is this a correct behavior..
>
>
>  public boolean delete(String resourceId, String xpathStr) {
> ResourceFileData fileData = resourceMap.get(resourceId);
>
> try {
> if (fileData != null && fileData.isTransactionStarted()) {
> OMElement sgElement = fileData.getOMElement();
> AXIOMXPath xpathExpr = new AXIOMXPath(xpathStr);
> OMElement el = (OMElement)
> xpathExpr.selectSingleNode(sgElement);
> if (el == null) {
> return false;
> }
> if (el.getParent() == null) { //this is the root element
> fileData.setOMElement(null);
> } *else {*
> *el.detach();*
> *}*
> setMetaFileModification(resourceId);
> return true;
> } else {
> log.error("The Element specified by path not found or a
> transaction isn't started yet. " +
> xpathStr);
> return false;
> }
> } catch (JaxenException e) {
> log.error("Error parsing xpath string " + resourceId +
> xpathStr, e);
> return false;
> }
> }
>
>
> Cheers,
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ *
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>



-- 
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)714408632 <%28%2B94%29714408632>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Compilation error in P2-profile in SS

[Prabath Abeysekera]

Hi Shani,

It looks like, version of one of the artifacts being published is supplied
with an un-resolvable property (or some malformed string) which forces
artifact publishing phase of p2 profile generation to fail. Please check
whether the property aliases used are properly configured.


Cheers,
Prabath


On Wed, Nov 13, 2013 at 5:40 PM, Shani Ranasinghe  wrote:

>
> Hi,
>
> I get a  $subject when compiling the ss p2-profile. Please find the stack
> trace below.
>
> [INFO] Running Equinox P2 Publisher Application for Repository Generation
> [INFO] Command line:
> /bin/sh -c cd
> /home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile
> && /opt/java/jdk1.6.0_45/jre/bin/java -jar
> /home/shani/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
> -nosplash -application
> org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher -source
> /home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile/target/tmp.1384344139652/featureExtract
> -metadataRepository
> file:/home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile/target/p2-repo
> -metadataRepositoryName wso2ss-p2-profile -artifactRepository
> file:/home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile/target/p2-repo
> -artifactRepositoryName wso2ss-p2-profile -publishArtifacts
> -publishArtifactRepository -compress -append
> Generating metadata for ..
> Status ERROR: org.eclipse.equinox.p2.artifact.repository code=0 For input
> string: "${exp" java.lang.NumberFormatException: For input string: "${exp"
>
> Product publishing ended with the following exception:
> java.lang.NumberFormatException: For input string: "${exp"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Integer.parseInt(Integer.java:449)
> at java.lang.Integer.parseInt(Integer.java:499)
> at org.osgi.framework.Version.(Version.java:127)
> at org.osgi.framework.Version.parseVersion(Version.java:225)
> at
> org.eclipse.osgi.internal.resolver.StateBuilder.addExportPackages(StateBuilder.java:338)
> at
> org.eclipse.osgi.internal.resolver.StateBuilder.createExportPackages(StateBuilder.java:320)
> at
> org.eclipse.osgi.internal.resolver.StateBuilder.createBundleDescription(StateBuilder.java:110)
> at
> org.eclipse.osgi.internal.resolver.StateObjectFactoryImpl.createBundleDescription(StateObjectFactoryImpl.java:32)
> at
> org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.createBundleDescription(BundlesAction.java:531)
> at
> org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.createBundleDescription(BundlesAction.java:546)
> at
> org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.getBundleDescriptions(BundlesAction.java:846)
> at
> org.eclipse.equinox.p2.publisher.eclipse.BundlesAction.perform(BundlesAction.java:657)
> at
> org.eclipse.equinox.p2.publisher.Publisher$ArtifactProcess.run(Publisher.java:207)
> at
> org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.executeBatch(SimpleArtifactRepository.java:1294)
> at
> org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher.java:231)
> at
> org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:283)
> at
> org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:253)
> at
> org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.start(AbstractPublisherApplication.java:315)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at
> org.eclipse.equinox.internal.app.AnyThreadAppLauncher.run(AnyThreadAppLauncher.java:26)
> at java.lang.Thread.run(Thread.java:662)
>
> Product publisher application was executed with the following arguments:
> -source
>
> /home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile/target/tmp.1384344139652/featureExtract
> -metadataRepository
>
> file:/home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile/target/p2-repo
> -metadataRepositoryName
> wso2ss-p2-profile
> -artifactRepository
>
> file:/home/shani/sranasinghe/trunk/carbon/platform/branches/turing/products/ss/1.1.0/modules/p2-profile/target/p2-repo
> -artifactRepositoryName
> wso2ss-p2-profile
> -publishArtifacts
> -publishArtifactRepository
> -compress
> -append
> [ERROR] P2 publisher return code was 1
> org.apache.maven.plugin.MojoFailureException: P2 publisher return code was
> 1
> at
> org.wso2.maven.p2.RepositoryGenMojo.generateRepository(RepositoryGenMojo.java:255)
> at
> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:204)
> at
> org.wso2.maven.p2.RepositoryGenMojo.execute(Reposit

[Dev] WSO2 ESB 4.8.0 - Alpha Released !

[Shafreen Anfar]

Hi,

ESB version 4.8.0 Alpha is available at,
https://svn.wso2.org/repos/wso2/people/shafreen/ESB480/alpha/wso2esb-4.8.0.zip

Connectors can be found in
$ESB_HOME/repository/connectors

-- 
Regards,
*Shafreen*
Software Engineer
WSO2 Inc
Mobile : 077-556-395-1
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Caching with multi-tenant applications

[Supun Malinga]

Hi Azeez/All,

As per [1] we can use the platform provided cache. My question is how do we
handle multi tenancy here. Do we have a cache manager per tenant?. Or
what's the way to handle multi tenant scenario..

[1]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/as/5.2.0/modules/samples/common/webapp/src/main/resources/carbon/caching/index.jsp

thanks,
-- 
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] WSO2 ESB 4.8.0 - Alpha Released !

[Dushan Abeyruwan]

Hi
  It seems like connectors are not updated correctly with the Alpha pack
shared, anyway for QA process for 4.8.0 Alpha please do download the latest
connectors from [1]

[1]https://svn.wso2.org/repos/wso2/people/shafreen/connectors/


On Wed, Nov 13, 2013 at 8:16 PM, Shafreen Anfar  wrote:

> Hi,
>
> ESB version 4.8.0 Alpha is available at,
>
> https://svn.wso2.org/repos/wso2/people/shafreen/ESB480/alpha/wso2esb-4.8.0.zip
>
> Connectors can be found in
> $ESB_HOME/repository/connectors
>
> --
> Regards,
> *Shafreen*
> Software Engineer
> WSO2 Inc
> Mobile : 077-556-395-1
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 ESB 4.8.0 - Alpha Released !

[Evanthika Amarasiri]

Noted Dushan,

Evanthika

On Wed, Nov 13, 2013 at 10:49 PM, Dushan Abeyruwan  wrote:

> Hi
>   It seems like connectors are not updated correctly with the Alpha pack
> shared, anyway for QA process for 4.8.0 Alpha please do download the latest
> connectors from [1]
>
> [1]https://svn.wso2.org/repos/wso2/people/shafreen/connectors/
>
>
> On Wed, Nov 13, 2013 at 8:16 PM, Shafreen Anfar  wrote:
>
>> Hi,
>>
>> ESB version 4.8.0 Alpha is available at,
>>
>> https://svn.wso2.org/repos/wso2/people/shafreen/ESB480/alpha/wso2esb-4.8.0.zip
>>
>> Connectors can be found in
>> $ESB_HOME/repository/connectors
>>
>> --
>> Regards,
>> *Shafreen*
>> Software Engineer
>> WSO2 Inc
>> Mobile : 077-556-395-1
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ *
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Caching with multi-tenant applications

[Afkham Azeez]

Any cache manager (and therefore all its caches) you request for is
automatically tenant qualified. A tenant can have multiple cache managers.


On Wed, Nov 13, 2013 at 8:47 PM, Supun Malinga  wrote:

> Hi Azeez/All,
>
> As per [1] we can use the platform provided cache. My question is how do
> we handle multi tenancy here. Do we have a cache manager per tenant?. Or
> what's the way to handle multi tenant scenario..
>
> [1]
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/as/5.2.0/modules/samples/common/webapp/src/main/resources/carbon/caching/index.jsp
>
> thanks,
> --
> Supun Malinga,
>
> Senior Software Engineer,
> WSO2 Inc.
> http://wso2.com
> email: sup...@wso2.com 
> mobile: +94 (0)71 56 91 321
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919 blog: **http://blog.afkham.org*
*twitter: **http://twitter.com/afkham_azeez*
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

[Dev] (no subject)

[Vanjikumaran Sivajothy]

Hi all,

Currently i am in the process of setting up a WSO2 MB cluster based on [1].
Some time I am getting OOM in internal Cassandra server. Therefore i found
there is another document that explain about [2]
Tuning the external  Cassandra server. Nevertheless, [1] uses the Internal
Cassandra server.

I was unable to find any document for tuning Internal Cassandra server. If
there is any document of knowledge please share with me.

Thank you in advance :)



[1]
http://docs.wso2.org/display/CLUSTER420/Default+Cassandra+and+Zookeeper+Servers
[2]http://docs.wso2.org/display/MB210/Cassandra+Tuned+Up+Configurations
-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)777219209*
*Mobile USA:**(+1)918 813 2403*
[image: Facebook]  [image:
Twitter] [image:
LinkedIn] 
[image:
Blogger]  [image:
SlideShare]
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 MB- Internal Cassandra tuning Guide

[Vanjikumaran Sivajothy]

Hi all,

Currently i am in the process of setting up a WSO2 MB cluster based on [1].
Some time I am getting OOM in internal Cassandra server. Therefore i found
there is another document that explain about [2]
Tuning the external  Cassandra server. Nevertheless, [1] uses the Internal
Cassandra server.

I was unable to find any document for tuning Internal Cassandra server. If
there is any document of knowledge please share with me.

Thank you in advance :)



[1]
http://docs.wso2.org/display/CLUSTER420/Default+Cassandra+and+Zookeeper+Servers
[2]http://docs.wso2.org/display/MB210/Cassandra+Tuned+Up+Configurations

-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)777219209*
*Mobile USA:**(+1)918 813 2403*
[image: Facebook]  [image:
Twitter] [image:
LinkedIn] 
[image:
Blogger]  [image:
SlideShare]
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Caching with multi-tenant applications

[Supun Malinga]

Thanks



On Wed, Nov 13, 2013 at 11:05 PM, Afkham Azeez  wrote:

> Any cache manager (and therefore all its caches) you request for is
> automatically tenant qualified. A tenant can have multiple cache managers.
>
>
> On Wed, Nov 13, 2013 at 8:47 PM, Supun Malinga  wrote:
>
>> Hi Azeez/All,
>>
>> As per [1] we can use the platform provided cache. My question is how do
>> we handle multi tenancy here. Do we have a cache manager per tenant?. Or
>> what's the way to handle multi tenant scenario..
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/as/5.2.0/modules/samples/common/webapp/src/main/resources/carbon/caching/index.jsp
>>
>> thanks,
>> --
>> Supun Malinga,
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> email: sup...@wso2.com 
>> mobile: +94 (0)71 56 91 321
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



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

[Dev] [dev] ELB 2.1.0 with ESB W/M, Continues looping never ends when ESB EP goes suspended or timedout

[Dushan Abeyruwan]

$subject,when ELB 2.1.0 with W/M  when particular EP goes suspend or
timeout, LB keep tying the same message forever..

This required immediate attention

FYI QA team pls try to reproduce this , did test with ESB 4.8.0 alpha pack.

Cheers,
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)714408632 <%28%2B94%29714408632>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ELB 2.1.0 with ESB W/M, Continues looping never ends when ESB EP goes suspended or timedout

[Miyuru Wanninayaka]

I think what happens is leaf endpoints never get suspended and failover
retry set to true. So request keeps retrying with next active endpoint
forever.


On Thu, Nov 14, 2013 at 9:29 AM, Dushan Abeyruwan  wrote:

> $subject,when ELB 2.1.0 with W/M  when particular EP goes suspend or
> timeout, LB keep tying the same message forever..
>
> This required immediate attention
>
> FYI QA team pls try to reproduce this , did test with ESB 4.8.0 alpha pack.
>
> Cheers,
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ *
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>



-- 
Miyuru Wanninayaka
Technical Lead
WSO2 Inc. : http://wso2.com

Mobile : +94 77 209 9788
Blog : http://miyurudw.blogspot.com
Flickr : http://www.flickr.com/photos/miyuru_daminda
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ELB 2.1.0 with ESB W/M, Continues looping never ends when ESB EP goes suspended or timedout

[Dushan Abeyruwan]

This should be something ELB team need to attend and fix am I?


On Thu, Nov 14, 2013 at 9:34 AM, Miyuru Wanninayaka  wrote:

> I think what happens is leaf endpoints never get suspended and failover
> retry set to true. So request keeps retrying with next active endpoint
> forever.
>
>
> On Thu, Nov 14, 2013 at 9:29 AM, Dushan Abeyruwan  wrote:
>
>> $subject,when ELB 2.1.0 with W/M  when particular EP goes suspend or
>> timeout, LB keep tying the same message forever..
>>
>> This required immediate attention
>>
>> FYI QA team pls try to reproduce this , did test with ESB 4.8.0 alpha
>> pack.
>>
>> Cheers,
>> Dushan Abeyruwan
>> Associate Tech Lead
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com/ *
>> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>>
>
>
>
> --
> Miyuru Wanninayaka
> Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile : +94 77 209 9788
> Blog : http://miyurudw.blogspot.com
> Flickr : http://www.flickr.com/photos/miyuru_daminda
>



-- 
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining

[Dushan Abeyruwan]

$subject,
  when ELB shutdown and restarts and expecting Mgt's and Wrk's to be
rejoined ASAP  but seems this not happening(some time it takes while to
join,or never joins),but when mgrs's and wrks restarts those will be
joining back

FYI : QA team please do verify this..

Cheers,
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)714408632 <%28%2B94%29714408632>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ELB 2.1.0 with ESB W/M, Continues looping never ends when ESB EP goes suspended or timedout

[Miyuru Wanninayaka]

We can't fix it now as ELB is already released.

Any fix has to go to next ELB release. Pls report a L1 against it.


On Thu, Nov 14, 2013 at 9:35 AM, Dushan Abeyruwan  wrote:

> This should be something ELB team need to attend and fix am I?
>
>
> On Thu, Nov 14, 2013 at 9:34 AM, Miyuru Wanninayaka wrote:
>
>> I think what happens is leaf endpoints never get suspended and failover
>> retry set to true. So request keeps retrying with next active endpoint
>> forever.
>>
>>
>> On Thu, Nov 14, 2013 at 9:29 AM, Dushan Abeyruwan wrote:
>>
>>> $subject,when ELB 2.1.0 with W/M  when particular EP goes suspend or
>>> timeout, LB keep tying the same message forever..
>>>
>>> This required immediate attention
>>>
>>> FYI QA team pls try to reproduce this , did test with ESB 4.8.0 alpha
>>> pack.
>>>
>>> Cheers,
>>> Dushan Abeyruwan
>>> Associate Tech Lead
>>> *Integration Technologies Team*
>>> *WSO2 Inc. http://wso2.com/ *
>>> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>>>
>>
>>
>>
>> --
>> Miyuru Wanninayaka
>> Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile : +94 77 209 9788
>> Blog : http://miyurudw.blogspot.com
>> Flickr : http://www.flickr.com/photos/miyuru_daminda
>>
>
>
>
> --
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ *
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>



-- 
Miyuru Wanninayaka
Technical Lead
WSO2 Inc. : http://wso2.com

Mobile : +94 77 209 9788
Blog : http://miyurudw.blogspot.com
Flickr : http://www.flickr.com/photos/miyuru_daminda
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ELB 2.1.0 with ESB W/M, Continues looping never ends when ESB EP goes suspended or timedout

[Dushan Abeyruwan]

https://wso2.org/jira/browse/LB-126


On Thu, Nov 14, 2013 at 9:40 AM, Miyuru Wanninayaka  wrote:

> We can't fix it now as ELB is already released.
>
> Any fix has to go to next ELB release. Pls report a L1 against it.
>
>
>
> On Thu, Nov 14, 2013 at 9:35 AM, Dushan Abeyruwan  wrote:
>
>> This should be something ELB team need to attend and fix am I?
>>
>>
>> On Thu, Nov 14, 2013 at 9:34 AM, Miyuru Wanninayaka wrote:
>>
>>> I think what happens is leaf endpoints never get suspended and failover
>>> retry set to true. So request keeps retrying with next active endpoint
>>> forever.
>>>
>>>
>>> On Thu, Nov 14, 2013 at 9:29 AM, Dushan Abeyruwan wrote:
>>>
 $subject,when ELB 2.1.0 with W/M  when particular EP goes suspend or
 timeout, LB keep tying the same message forever..

 This required immediate attention

 FYI QA team pls try to reproduce this , did test with ESB 4.8.0 alpha
 pack.

 Cheers,
 Dushan Abeyruwan
 Associate Tech Lead
 *Integration Technologies Team*
 *WSO2 Inc. http://wso2.com/ *
 *Mobile:(+94)714408632 <%28%2B94%29714408632>*

>>>
>>>
>>>
>>> --
>>> Miyuru Wanninayaka
>>> Technical Lead
>>> WSO2 Inc. : http://wso2.com
>>>
>>> Mobile : +94 77 209 9788
>>> Blog : http://miyurudw.blogspot.com
>>> Flickr : http://www.flickr.com/photos/miyuru_daminda
>>>
>>
>>
>>
>> --
>> Dushan Abeyruwan
>> Associate Tech Lead
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com/ *
>> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>>
>
>
>
> --
> Miyuru Wanninayaka
> Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile : +94 77 209 9788
> Blog : http://miyurudw.blogspot.com
> Flickr : http://www.flickr.com/photos/miyuru_daminda
>



-- 
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining

[Evanthika Amarasiri]

We are trying this with the latest packs now.

Evanthika

On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan  wrote:

> $subject,
>   when ELB shutdown and restarts and expecting Mgt's and Wrk's to be
> rejoined ASAP  but seems this not happening(some time it takes while to
> join,or never joins),but when mgrs's and wrks restarts those will be
> joining back
>
> FYI : QA team please do verify this..
>
> Cheers,
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ *
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining

[Dushan Abeyruwan]

This required immediate attention..https://wso2.org/jira/browse/LB-127


On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan  wrote:

> $subject,
>   when ELB shutdown and restarts and expecting Mgt's and Wrk's to be
> rejoined ASAP  but seems this not happening(some time it takes while to
> join,or never joins),but when mgrs's and wrks restarts those will be
> joining back
>
> FYI : QA team please do verify this..
>
> Cheers,
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ *
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>



-- 
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining

[Dushan Abeyruwan]

Once more shutting down ELB cause following NEP

ctive:true
[2013-11-14 09:49:37,179] ERROR - NativeWorkerPool Uncaught exception
java.lang.NullPointerException
 at
org.apache.synapse.endpoints.DynamicLoadbalanceEndpoint.getEndpoint(DynamicLoadbalanceEndpoint.java:435)
at
org.apache.synapse.endpoints.DynamicLoadbalanceEndpoint.sendToApplicationMember(DynamicLoadbalanceEndpoint.java:304)
 at
org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint.access$400(TenantAwareLoadBalanceEndpoint.java:46)
at
org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint$TenantDynamicLoadBalanceFaultHandlerImpl.onFault(TenantAwareLoadBalanceEndpoint.java:518)
 at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:54)
at
org.apache.synapse.endpoints.AbstractEndpoint.invokeNextFaultHandler(AbstractEndpoint.java:622)
 at
org.apache.synapse.endpoints.AbstractEndpoint.onFault(AbstractEndpoint.java:471)
at
org.apache.synapse.endpoints.AddressEndpoint.onFault(AddressEndpoint.java:43)
 at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:102)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:249)
 at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:167)
at
org.apache.synapse.transport.passthru.TargetErrorHandler$1.run(TargetErrorHandler.java:134)
 at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
[2013-11-14 09:49:37,352]  INFO - CarbonServerManager Shutdown complete
[2013-11-14 09:49:37,352]  INFO - CarbonServerManager Halting JVM



On Thu, Nov 14, 2013 at 9:48 AM, Dushan Abeyruwan  wrote:

> This required immediate attention..https://wso2.org/jira/browse/LB-127
>
>
> On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan  wrote:
>
>> $subject,
>>   when ELB shutdown and restarts and expecting Mgt's and Wrk's to be
>> rejoined ASAP  but seems this not happening(some time it takes while to
>> join,or never joins),but when mgrs's and wrks restarts those will be
>> joining back
>>
>> FYI : QA team please do verify this..
>>
>> Cheers,
>> Dushan Abeyruwan
>> Associate Tech Lead
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com/ *
>> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>>
>
>
>
> --
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ *
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>



-- 
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining

[Amila Maha Arachchi]

You need to have at least one WK member in a given time when you are
dealing with hazelcast. If ELB is the only WK member in your setup, when
you restart the ELB, others will never join the ELB until they are
restarted.

To get this working, ELB also should have a WK member (can be the ESB mgt
node) and workers should have both ELB and MGT node as WK members.

AFAIK QA team is aware of this. If you want, talk to IsuruW.


On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan  wrote:

> $subject,
>   when ELB shutdown and restarts and expecting Mgt's and Wrk's to be
> rejoined ASAP  but seems this not happening(some time it takes while to
> join,or never joins),but when mgrs's and wrks restarts those will be
> joining back
>
> FYI : QA team please do verify this..
>
> Cheers,
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ *
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

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

Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining

[Dushan Abeyruwan]

On Thu, Nov 14, 2013 at 9:50 AM, Amila Maha Arachchi wrote:

> You need to have at least one WK member in a given time when you are
> dealing with hazelcast. If ELB is the only WK member in your setup, when
> you restart the ELB, others will never join the ELB until they are
> restarted.
>

Is this kind of a norm .. a hard fasten rule we have seutp with the
newst WK implementation. ? Wonder I should agree on this or not..assume
there is a pool which as larger number of wrks..and Do i need to restart
them all? Is that what you trying to emphasis..

  l.e assume my prod set has only 1 ELB and 30 works.. :)... so I need to
start all 30 if  ELB goes down ...woops..  :(


> To get this working, ELB also should have a WK member (can be the ESB mgt
> node) and workers should have both ELB and MGT node as WK members.
>
> AFAIK QA team is aware of this. If you want, talk to IsuruW.
>
>
> On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan  wrote:
>
>> $subject,
>>   when ELB shutdown and restarts and expecting Mgt's and Wrk's to be
>> rejoined ASAP  but seems this not happening(some time it takes while to
>> join,or never joins),but when mgrs's and wrks restarts those will be
>> joining back
>>
>> FYI : QA team please do verify this..
>>
>> Cheers,
>> Dushan Abeyruwan
>> Associate Tech Lead
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com/ *
>> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>


-- 
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining

[Dushan Abeyruwan]

On Thu, Nov 14, 2013 at 9:55 AM, Dushan Abeyruwan  wrote:

>
>
>
> On Thu, Nov 14, 2013 at 9:50 AM, Amila Maha Arachchi wrote:
>
>> You need to have at least one WK member in a given time when you are
>> dealing with hazelcast. If ELB is the only WK member in your setup, when
>> you restart the ELB, others will never join the ELB until they are
>> restarted.
>>
>
>
>
>> To get this working, ELB also should have a WK member (can be the ESB mgt
>> node) and workers should have both ELB and MGT node as WK members.
>>
>> AFAIK QA team is aware of this. If you want, talk to IsuruW.
>>
>

   Do we have any document reference  ?  FYI Jackie


>
>>
>> On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan wrote:
>>
>>> $subject,
>>>   when ELB shutdown and restarts and expecting Mgt's and Wrk's to be
>>> rejoined ASAP  but seems this not happening(some time it takes while to
>>> join,or never joins),but when mgrs's and wrks restarts those will be
>>> joining back
>>>
>>> FYI : QA team please do verify this..
>>>
>>> Cheers,
>>> Dushan Abeyruwan
>>> Associate Tech Lead
>>> *Integration Technologies Team*
>>> *WSO2 Inc. http://wso2.com/ *
>>> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Amila Maharachchi*
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>>
>> Blog: http://maharachchi.blogspot.com
>> Mobile: +94719371446
>>
>>
>
>
> --
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ *
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>



-- 
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ELB 2.1.0 with ESB W/M, Continues looping never ends when ESB EP goes suspended or timedout

[Evanthika Amarasiri]

This was reported by Ushani.

https://wso2.org/jira/browse/LB-125

Evanthika


On Thu, Nov 14, 2013 at 9:44 AM, Dushan Abeyruwan  wrote:

> https://wso2.org/jira/browse/LB-126
>
>
> On Thu, Nov 14, 2013 at 9:40 AM, Miyuru Wanninayaka wrote:
>
>> We can't fix it now as ELB is already released.
>>
>> Any fix has to go to next ELB release. Pls report a L1 against it.
>>
>>
>>
>> On Thu, Nov 14, 2013 at 9:35 AM, Dushan Abeyruwan wrote:
>>
>>> This should be something ELB team need to attend and fix am I?
>>>
>>>
>>> On Thu, Nov 14, 2013 at 9:34 AM, Miyuru Wanninayaka wrote:
>>>
 I think what happens is leaf endpoints never get suspended and failover
 retry set to true. So request keeps retrying with next active endpoint
 forever.


 On Thu, Nov 14, 2013 at 9:29 AM, Dushan Abeyruwan wrote:

> $subject,when ELB 2.1.0 with W/M  when particular EP goes suspend or
> timeout, LB keep tying the same message forever..
>
> This required immediate attention
>
> FYI QA team pls try to reproduce this , did test with ESB 4.8.0 alpha
> pack.
>
> Cheers,
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ *
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>



 --
 Miyuru Wanninayaka
 Technical Lead
 WSO2 Inc. : http://wso2.com

 Mobile : +94 77 209 9788
 Blog : http://miyurudw.blogspot.com
 Flickr : http://www.flickr.com/photos/miyuru_daminda

>>>
>>>
>>>
>>> --
>>> Dushan Abeyruwan
>>> Associate Tech Lead
>>> *Integration Technologies Team*
>>> *WSO2 Inc. http://wso2.com/ *
>>> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>>>
>>
>>
>>
>> --
>> Miyuru Wanninayaka
>> Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile : +94 77 209 9788
>> Blog : http://miyurudw.blogspot.com
>> Flickr : http://www.flickr.com/photos/miyuru_daminda
>>
>
>
>
> --
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ *
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining

[Evanthika Amarasiri]

I'm sorry I did not quite get what Dushan said in the intial email.

Yes Dushan, this is a known fact. When ELB is restarted, you will have to
restart all other nodes unless you have another WKA member in your cluster.
As AmilaM mentioned, this can either be another ELB or a Mgt/Wrk node.

Evanthika

On Thu, Nov 14, 2013 at 9:50 AM, Amila Maha Arachchi wrote:

> You need to have at least one WK member in a given time when you are
> dealing with hazelcast. If ELB is the only WK member in your setup, when
> you restart the ELB, others will never join the ELB until they are
> restarted.
>
> To get this working, ELB also should have a WK member (can be the ESB mgt
> node) and workers should have both ELB and MGT node as WK members.
>
> AFAIK QA team is aware of this. If you want, talk to IsuruW.
>
>
> On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan  wrote:
>
>> $subject,
>>   when ELB shutdown and restarts and expecting Mgt's and Wrk's to be
>> rejoined ASAP  but seems this not happening(some time it takes while to
>> join,or never joins),but when mgrs's and wrks restarts those will be
>> joining back
>>
>> FYI : QA team please do verify this..
>>
>> Cheers,
>> Dushan Abeyruwan
>> Associate Tech Lead
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com/ *
>> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>
> ___
> 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] [Jaggery] [Test] Test framework for jaggery

[Madhuka Udantha]

Hi Krishantha and test automation team,

I would like to get your opinion on this task regard to

is there standard methodology on current testing framework where we can
added such testing framework or better to go on fully independent model?


My thinking is,

   -  As it is application level testing frame work, better to work with
   much independent of the current system
   - Where application writer (developer) can run test for specific
  application rather running all test for platform or product
  - It will help to maintain both test framework with low cost
  - Each test frame have it's own scope (such as
  platform/product/appilcation). if not, complexity of the code and system
  will be increase but there will be API interface for interaction
among the
  test framework.
   -  And I thought to have interface (simple REST interface) in jaggery
   test frame work where current test framework also can interact with it into
   some extend.

 Thanks


On Tue, Nov 12, 2013 at 5:57 PM, Madhuka Udantha  wrote:

> Hi,
>
>
> Still we do not have jaggery test framework even though there are
> considerable jaggery applications were developed. It is not easy maintain
> those jaggery applications/APIs steady without testing frame work.
>
>
> Now onward we will starting $subject as it is important for jaggery as
> well as there is no JS testing framework under WSO2 Platform. Testing
> framework will be under application level such as mocha, jasmine.  Test
> frame will be apply to (basically)test.
>
>
>
>- jaggery API (js functions and arguments )
>- REST APIs that are expose under jaggery application
>- With test coverage reporting
>
>
> We will be evaluating existing JavaScript test frame works  regard
> mocha[1], jasmine[2], Qunit[3], Vows[4],  expresso[5], nodeunit[6] and
> jsunit[7]  to $subject.
>
>
>
> All suggestions are welcome.
>
>
> [1] http://visionmedia.github.io/mocha/
>
> [2] http://pivotal.github.io/jasmine/
>
> [3] http://qunitjs.com/
>
> [4] http://vowsjs.org/
>
> [5] http://visionmedia.github.io/expresso/
>
> [6] https://github.com/caolan/nodeunit
>
> [7] https://github.com/pivotal/jsunit
>
>
>
> Thanks
> --
> *Madhuka* Udantha
> Senior Software Engineer
> Development Technologies
> WSO2 Inc. : http://wso2.com
>
> *Mobile*: +94774066336
> *Blog*: http://madhukaudantha.blogspot.com/
>



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

Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining

[Jackie Wheeler]

Copying Sam, who is handling the clustering docs.


On Wed, Nov 13, 2013 at 8:38 PM, Evanthika Amarasiri wrote:

> I'm sorry I did not quite get what Dushan said in the intial email.
>
> Yes Dushan, this is a known fact. When ELB is restarted, you will have to
> restart all other nodes unless you have another WKA member in your cluster.
> As AmilaM mentioned, this can either be another ELB or a Mgt/Wrk node.
>
> Evanthika
>
> On Thu, Nov 14, 2013 at 9:50 AM, Amila Maha Arachchi wrote:
>
>> You need to have at least one WK member in a given time when you are
>> dealing with hazelcast. If ELB is the only WK member in your setup, when
>> you restart the ELB, others will never join the ELB until they are
>> restarted.
>>
>> To get this working, ELB also should have a WK member (can be the ESB mgt
>> node) and workers should have both ELB and MGT node as WK members.
>>
>> AFAIK QA team is aware of this. If you want, talk to IsuruW.
>>
>>
>> On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan wrote:
>>
>>> $subject,
>>>   when ELB shutdown and restarts and expecting Mgt's and Wrk's to be
>>> rejoined ASAP  but seems this not happening(some time it takes while to
>>> join,or never joins),but when mgrs's and wrks restarts those will be
>>> joining back
>>>
>>> FYI : QA team please do verify this..
>>>
>>> Cheers,
>>> Dushan Abeyruwan
>>> Associate Tech Lead
>>> *Integration Technologies Team*
>>> *WSO2 Inc. http://wso2.com/ *
>>> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Amila Maharachchi*
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>>
>> Blog: http://maharachchi.blogspot.com
>> Mobile: +94719371446
>>
>>
>> ___
>> 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
>
>


-- 
*Jackie Wheeler*
VP, Technical Content
WSO2, Inc.
Mobile: +1 510 725-2876
http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining

[Samuel Gnaniah]

Added a note to capture this.

http://docs.wso2.org/display/CLUSTER420/Creating+a+Cluster

*Samuel Gnaniah*
Senior Technical Writer

WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798


On Thu, Nov 14, 2013 at 11:28 AM, Jackie Wheeler  wrote:

> Copying Sam, who is handling the clustering docs.
>
>
> On Wed, Nov 13, 2013 at 8:38 PM, Evanthika Amarasiri 
> wrote:
>
>> I'm sorry I did not quite get what Dushan said in the intial email.
>>
>> Yes Dushan, this is a known fact. When ELB is restarted, you will have to
>> restart all other nodes unless you have another WKA member in your cluster.
>> As AmilaM mentioned, this can either be another ELB or a Mgt/Wrk node.
>>
>> Evanthika
>>
>> On Thu, Nov 14, 2013 at 9:50 AM, Amila Maha Arachchi wrote:
>>
>>> You need to have at least one WK member in a given time when you are
>>> dealing with hazelcast. If ELB is the only WK member in your setup, when
>>> you restart the ELB, others will never join the ELB until they are
>>> restarted.
>>>
>>> To get this working, ELB also should have a WK member (can be the ESB
>>> mgt node) and workers should have both ELB and MGT node as WK members.
>>>
>>> AFAIK QA team is aware of this. If you want, talk to IsuruW.
>>>
>>>
>>> On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan wrote:
>>>
 $subject,
   when ELB shutdown and restarts and expecting Mgt's and Wrk's to be
 rejoined ASAP  but seems this not happening(some time it takes while to
 join,or never joins),but when mgrs's and wrks restarts those will be
 joining back

 FYI : QA team please do verify this..

 Cheers,
 Dushan Abeyruwan
 Associate Tech Lead
 *Integration Technologies Team*
 *WSO2 Inc. http://wso2.com/ *
 *Mobile:(+94)714408632 <%28%2B94%29714408632>*

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


>>>
>>>
>>> --
>>> *Amila Maharachchi*
>>> Senior Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>>
>>> Blog: http://maharachchi.blogspot.com
>>> Mobile: +94719371446
>>>
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> *Jackie Wheeler*
> VP, Technical Content
> WSO2, Inc.
> Mobile: +1 510 725-2876
> http://wso2.com/
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Adding removeObserver() method to AxisConfiguration

[Lakmali Baminiwatta]

Hi all,

In AxisSericeTracker@stop() method, it retrieves the observers list from
the AxisConfiguration and removes the already added AxisSericeTracker
observer[1]. But what is returned from AxisConfiguration is a copy of
actual observers, hence this removal doesn not actually happens.

config.getObserversList().remove(observer);

This causes issues when transports are updated at runtime.

I noticed that this is fixed in axis2 trunk by adding removeObserver method
to AxisConfiguration.java. Therefore I will be adding the same fix.

[1]
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/dependencies/transports/1.1.0-wso2v9/modules/base/src/main/java/org/apache/axis2/transport/base/tracker/AxisServiceTracker.java

Thanks,
Lakmali

-- 
Lakmali Baminiwatta
 Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon Cassandra Authenticator

[Chan]

Hi Bhathiya,

I added the patch but the following error comes -

 java.lang.NullPointerException

at
org.wso2.carbon.identity.authentication.AuthenticationServiceImpl.authenticate(AuthenticationServiceImpl.java:64)

at
org.wso2.carbon.cassandra.server.CarbonCassandraAuthenticator.authenticateUser(CarbonCassandraAuthenticator.java:169)

at
org.wso2.carbon.cassandra.server.CarbonCassandraAuthenticator.authenticate(CarbonCassandraAuthenticator.java:105)

at org.apache.cassandra.service.ClientState.login(ClientState.java:124)

at
org.apache.cassandra.thrift.CassandraServer.login(CassandraServer.java:904)

at
org.apache.cassandra.thrift.Cassandra$Processor$login.getResult(Cassandra.java:2843)

at
org.apache.cassandra.thrift.Cassandra$Processor$login.getResult(Cassandra.java:2831)

at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)

at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)

at
org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:186)

at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)

at java.lang.Thread.run(Thread.java:722)


On Wed, Nov 6, 2013 at 2:59 PM, Bhathiya Jayasekara wrote:

> Hi Chan,
>
> Please find the attached jar for authenticator class. Please put this to
> dropins directory and change *authenticator* parameter value in
> *cassandra.yaml* to
> *org.wso2.carbon.cassandra.server.CarbonCassandraExternalAuthenticator*
>
> Let me know if there are any issues.
>
> Thanks,
> Bhathiya
>
> --
> *Bhathiya Jayasekara*
> *Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
>



-- 
Chan (Dulitha Wijewantha)
Software Engineer - Mobile Development
WSO2Mobile
Lean.Enterprise.Mobileware
 * ~Email   duli...@wso2mobile.com *
*  ~Mobile +94712112165*

*  ~Website   dulithawijewantha.com *

*  ~Blog blog.dulithawijewantha.com
*
*  ~Twitter @dulitharw *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [jira] (ESBJAVA-2680) Unable to Invoke the JIRA Connector an error occured.

[Dushan Abeyruwan]

how its working for me  W/M with latest Alpha pack with latest connectors
shared https://svn.wso2.org/repos/wso2/people/shafreen/connectors/

http://ws.apache.org/ns/synapse";
   name="JiraConnector"
   transports="https,http"
   statistics="disable"
   trace="disable"
   startOnLoad="true">
   
  
 
dus...@wso2.com
{wso2:vault-lookup('dushan.ot.password')}
https://wso2.org/jira
 
 
ESBJAVA-2632
 
 
  
   
   






dushan@dushan-ThinkPad-T520:~/poc/server/4.1.2-pack/connnector-works/worker_mgr/wso2elb-2.1.0/bin$
curl -v -X GET http://esb.wso2.com:8280/services/JiraConnector
* Adding handle: conn: 0x20aab90
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x20aab90) send_pipe: 1, recv_pipe: 0
* About to connect() to esb.wso2.com port 8280 (#0)
*   Trying 192.168.1.3...
* Connected to esb.wso2.com (192.168.1.3) port 8280 (#0)
> GET /services/JiraConnector HTTP/1.1
> User-Agent: curl/7.32.0
> Host: esb.wso2.com:8280
> Accept: */*
>
< HTTP/1.1 200 OK
< X-ASESSIONID: 130dp0l
< Set-Cookie: JSESSIONID=10AE871A5000B8784228045C1CFBA27B; Path=/jira/;
HttpOnly
< Set-Cookie:
atlassian.xsrf.token=A6BL-PURG-37QO-G55K|52b6f6a31898930c9bae0db4016245046df44826|lin;
Path=/jira
< X-AUSERNAME: dus...@wso2.com
< Content-Type: application/json;charset=UTF-8
< X-Seraph-LoginReason: OK
< X-AREQUESTID: 754x6241238x1
< Cache-Control: no-cache, no-store, no-transform
< Date: Thu, 14 Nov 2013 07:04:06 GMT
< Transfer-Encoding: chunked
<
{"expand":"renderedFields,names,schema,transitions,operations,editmeta,changelog","id":"51027","self":"https:\/\/
wso2.org\/jira\/rest\/api\/2\/issue\/51027","key":"ESBJAVA-2632","fields":{"progress":{"progress":"0","total":"0"},"summary":"Messages
are not transformed in to json when \"Accept: application\/json\"  is set
in Restful services in
NHTTP","timetracking":"","customfield_10084":"","customfield_10113":"","issuetype":{"self":"https:\/\/
wso2.org\/jira\/rest\/api\/2\/issuetype\/1","id":"1","description":"A
problem which impairs or prevents the functions of the
product.","iconUrl":"https:\/\/wso2.org
\/jira\/images\/icons\/issuetypes\/bug.png","name":"Bug","subtask":"false"},"customfield_10080":"","votes":{"self":"https:\/\/
wso2.org
\/jira\/rest\/api\/2\/issue\/ESBJAVA-2632\/votes","votes":"0","hasVoted":"false"},"resolution":"","fixVersions":{"self":"https:\/\/
wso2.org\/jira\/rest\/api\/2\/version\/11344","id":"11344","description":"ESB
4.8.0 release based on Carbon 4.2.0 - Alpha","

On Thu, Nov 14, 2013 at 12:22 PM, Chathurika Mahaarachchci (JIRA) <
j...@wso2.org> wrote:

>Chathurika 
> Mahaarachchcireopened
>  [image:
> Bug] ESBJAVA-2680 
>  *Unable to Invoke the JIRA Connector an error 
> occured.*
>This issue is still exist in ESB 4.8.0 Alpha pack
>*Change By:*  Chathurika 
> Mahaarachchci(14/Nov/13
>  12:21 PM)
> *Resolution:*  Fixed   *Status:*  Resolved Reopened   This message is
> automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>



-- 
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ *
*Mobile:(+94)714408632 <%28%2B94%29714408632>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Adding removeObserver() method to AxisConfiguration

[Sagara Gunathunga]

+1

I think you are referring to following commit[1] on Axis2 trunk.

[1] - http://svn.apache.org/viewvc?view=revision&revision=1324666

Thanks !


On Thu, Nov 14, 2013 at 12:33 PM, Lakmali Baminiwatta wrote:

> Hi all,
>
> In AxisSericeTracker@stop() method, it retrieves the observers list from
> the AxisConfiguration and removes the already added AxisSericeTracker
> observer[1]. But what is returned from AxisConfiguration is a copy of
> actual observers, hence this removal doesn not actually happens.
>
> config.getObserversList().remove(observer);
>
> This causes issues when transports are updated at runtime.
>
> I noticed that this is fixed in axis2 trunk by adding removeObserver
> method to AxisConfiguration.java. Therefore I will be adding the same fix.
>
> [1]
> https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/dependencies/transports/1.1.0-wso2v9/modules/base/src/main/java/org/apache/axis2/transport/base/tracker/AxisServiceTracker.java
>
> Thanks,
> Lakmali
>
> --
> Lakmali Baminiwatta
>  Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> mobile:  +94 71 2335936
> blog : lakmali.com
>
>


-- 
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] Adding removeObserver() method to AxisConfiguration

[Lakmali Baminiwatta]

Hi Sagara,


On 14 November 2013 12:49, Sagara Gunathunga  wrote:

>
> +1
>
> I think you are referring to following commit[1] on Axis2 trunk.
>
> [1] - 
> http://svn.apache.org/viewvc?view=revision&revision=1324666
>
> Yes, this is the fix.

Thanks,
Lakmali

> Thanks !
>
>
> On Thu, Nov 14, 2013 at 12:33 PM, Lakmali Baminiwatta wrote:
>
>> Hi all,
>>
>> In AxisSericeTracker@stop() method, it retrieves the observers list from
>> the AxisConfiguration and removes the already added AxisSericeTracker
>> observer[1]. But what is returned from AxisConfiguration is a copy of
>> actual observers, hence this removal doesn not actually happens.
>>
>> config.getObserversList().remove(observer);
>>
>> This causes issues when transports are updated at runtime.
>>
>> I noticed that this is fixed in axis2 trunk by adding removeObserver
>> method to AxisConfiguration.java. Therefore I will be adding the same fix.
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/dependencies/transports/1.1.0-wso2v9/modules/base/src/main/java/org/apache/axis2/transport/base/tracker/AxisServiceTracker.java
>>
>> Thanks,
>> Lakmali
>>
>> --
>> Lakmali Baminiwatta
>>  Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean.enterprise.middleware
>> mobile:  +94 71 2335936
>> blog : lakmali.com
>>
>>
>
>
> --
> 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
>
>


-- 
Lakmali Baminiwatta
 Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev