Re: [Dev] [che-dev] Trying Eclipse Che latest release on ubuntu

[Awanthika Senarath]

Hello Alexander,

After quite a bit of trouble-shooting from our end we got the script to
running,

We had to change all your functions declarations from

functions abc {}  ==> abc () {}

in the script, which caused issues in the bash. I have attached the changed
script herewith.

After changing them and running the script as ./che.sh run I get the
following error[1] ,

I have jdk 1.8 and docker installed. So the possible error is  "6. (Linux)
Permissions not properly set  ==> Che must run as UID 1000 with
user in docker group".

I have docker installed and my default user can run docker without sudo
permission. Anything that I have missed?

Any idea how to solve this?


[1]
/home/awanthika/WSO2/Eclipse-Che/eclipse-che-4.0.0-beta-13
Docker is natively installed and reachable...

## HOW TO CONNECT YOUR CHE CLIENT ###
After Che server has booted, you can connect your clients by:
1. Open browser to http://localhost:8080, or:
2. Open native chromium app.
#


JAVA_HOME is not set. Please set to directory of JVM or JRE.

Looks like something went wrong. Possible issues:
  1. (Win | Mac) VirtualBox not installed  ==> Rerun Docker Toolbox
installation
  2. (Win | Mac) Docker Machine not installed  ==> Rerun Docker Toolbox
installation
  3. (Win | Mac) Docker is not reachable   ==> Docker VM failed to
start
  4. (Win | Mac) Docker ok, but docker ps fails==> Docker environment
variables not set properly
  5. (Linux) Docker is not reachable   ==> Install: wget -qO-
https://get.docker.com/ | sh
  6. (Linux) Permissions not properly set  ==> Che must run as UID
1000 with user in docker group
  7. Could not find the Che app server ==> Did /tomcat get
moved away from CHE_HOME?
  8. Wrong version of Java found   ==> Che requires Java 1.8
  9. Did you use the right parameter syntax?   ==> See usage

We have seen issues with VirtualBox on Windows where your VM gets corrupted
when your computer is
suspended while the VM is still running. This will appear as SSH or
ethernet connection issues. This is
rare, but if encountered, current known solution is to uninstall VirtualBox
and Docker Toolbox, and then
reinstall.

Che Environment Variables:
  (REQUIRED) JAVA_HOME ==> Location of Java
runtime
  (REQUIRED: WIN|MAC) DOCKER_TOOLBOX_INSTALL_PATH  ==> Location of Docker
Toolbox
  (REQUIRED: WIN|MAC) VBOX_MSI_INSTALL_PATH==> Location of
VirtualBox
  (OPTIONAL) CHE_HOME  ==> Directory where Che
is installed
  (OPTIONAL) CHE_LOCAL_CONF_DIR==> Directory with
custom Che .properties files
  (OPTIONAL) CHE_LOGS_DIR  ==> Directory for Che
output logs
  (OPTIONAL) CHE_DOCKER_MACHINE_NAME   ==> (Win | Mac) Name of
VM created by docker-machine
  (OPTIONAL) DOCKER_MACHINE_HOST   ==> (Linux) Docker host
IP - set if browser clients remote

Usage:
  che [OPTIONS] [run | start | stop]
 -i,--imageLaunches Che within a Docker container using
latest image
 -i:tag,--image:tagLaunches Che within a Docker container using
specific image tag
 -p:port,   --port:portPort that Che server will use for HTTP
requests; default=8080
 -r:ip, --remote:ipIf Che clients are not localhost, set to IP
address of Che server
 -g,--registry Launch Docker registry as a container (used
for ws snapshots)
 -m:vm, --machine:vm   For Win & Mac, sets the docker-machine VM
name to vm; default=default
 -s:client, --skip:client  Do not print browser client connection
information
 -s:uid,--skip:uid Do not enforce UID=1000 for Docker
 -h,--help Show this help
 -d,--debugUse debug mode (prints command line options
+ app server debug)
 run Starts Che application server in current
console
 start   Starts Che application server in new console
 stopStops Che application server

The -r flag sets the DOCKER_MACHINE_HOST system environment variable. Set
this to the IP address of the node
that is running your Docker daemon. Only necessary to set this if on Linux
and your browser clients are not
localhost, ie they are remote. This property automatically set for Che on
Windows and Mac.


Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Tue, Feb 2, 2016 at 8:26 AM, Awanthika Senarath 
wrote:

> Hi Alexander,
>
> Running the exact script given by you results in the following error[1]. I
> will try in another machine to see whether this is related to my local
> setup.
>
> It says that the che.sh file has some syntax errors..
>
> My OS does not seem to recognize the function declarations in the SH file.
>
> [1] GNU bash, version 4.3.8(1)-release (x86_64-pc-linux-gnu)
> Copyright

Re: [Dev] [IS Authenticator] Issue in logout from mailchimp authenticator

[Chamara Philips]

Hi Hariprasath,
It is because the sessionID is null. It will be helpfull, if you can attach
the SSO tracer.

Thanks.

On Tue, Feb 2, 2016 at 11:58 AM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:

> Hi All,
>
> I have implemented mailChimp Authenticator for IS. When I logout from
> sample webapp(travelocity.com) i got the below error,
>
> [2016-02-02 11:41:01,907] ERROR
> {org.wso2.carbon.identity.sso.saml.processors.SPInitLogoutRequestProcessor}
> -  ssoTokenId cookie not found in the logout request
>
>
> Any suggestions?
>
> --
>
>
> *Thank you and Regards**Hariprasath Thanarajah*
> Associate Software Engineer | WSO2
> E: haripras...@wso2.com
> M: +94752806528
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Hareendra Chamara Philips
*Software  Engineer*
Mobile : +94 (0) 767 184161 <%2B94%20%280%29%20773%20451194>
chama...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Requesting pull request to be merged into app-manager-4.4.1-kernel branch in carbon-store

[Thilini Shanika]

Hi ES team,

During the integration test run in App Manager, we get a Connection pool
exhausted exception [1] which has been triggered from social component in
Enterprise Store. This occurs due to a failure in closing DB connections
created in warmUpRatingCache method in SQLActivityPublisher.

The issue is already fixed in ES master branch and we need to get the fix
[2] applied into app-manager-4.4.1-kernel branch also.

[1] - https://wso2.org/jira/browse/APPM-1268
[2] - https://github.com/wso2/carbon-store/pull/301

Thanks,
Thilini

-- 
Thilini Shanika
Software Engineer
WSO2, Inc.; http://wso2.com
20, Palmgrove Avenue, Colombo 3

E-mail: tgtshan...@gmail.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Requesting pull request to be merged into app-manager-4.4.1-kernel branch in carbon-store

[Ayesha Dissanayaka]

Hi Thilini,

Merged the pull request.


Thanks,
-Ayesha

On Tue, Feb 2, 2016 at 3:01 PM, Thilini Shanika  wrote:

> Hi ES team,
>
> During the integration test run in App Manager, we get a Connection pool
> exhausted exception [1] which has been triggered from social component in
> Enterprise Store. This occurs due to a failure in closing DB connections
> created in warmUpRatingCache method in SQLActivityPublisher.
>
> The issue is already fixed in ES master branch and we need to get the fix
> [2] applied into app-manager-4.4.1-kernel branch also.
>
> [1] - https://wso2.org/jira/browse/APPM-1268
> [2] - https://github.com/wso2/carbon-store/pull/301
>
> Thanks,
> Thilini
>
> --
> Thilini Shanika
> Software Engineer
> WSO2, Inc.; http://wso2.com
> 20, Palmgrove Avenue, Colombo 3
>
> E-mail: tgtshan...@gmail.com
>
>


-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [che-dev] Trying Eclipse Che latest release on ubuntu

[Awanthika Senarath]

Thanks for the reply,

I will create the issues in github as you have mentioned.


I changed the line USE_DOCKER=false to USE_DOCKER=true in the script,
without adding the modifications you suggested  I attached and then it
downloaded an image from the che site and started the che instance.

Should I configure an image in my docker instance prior to running che? Is
that why che was complaining of not having a JDK ?

Regards
Awanthika

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Tue, Feb 2, 2016 at 3:19 PM, Alexander Garagatyi 
wrote:

> Thank you for your investigation.
>
> So the problem in function syntax is that you are using POSIX compliant
> mode of bash. In this mode bash doesn't support modern features of bash.
> Try to add "set –o posix" line before "set -e" in the origin script. It
> should disable POSIX compliant mode in che script. I hope it will allow you
> to run unchanged script.
> But now with changed syntax of functions you have another problem:
>
>> JAVA_HOME is not set. Please set to directory of JVM or JRE.
>
> It is possible that parsing fails because of POSIX compliant mode of bash.
> Check if this error happens when you disable that mode. If it still
> present, please, ping me again.
>
> BTW looks like we need improve script to disable POSIX compliant mode at
> the beginning of the script. Can you create an issue on github with
> description of your problem.
> Also output is too messy and doesn't allow to identify error message
> easily. If you think so, please, create issue on github with example of
> output you've provided. It is a good example.
>
> On Tue, Feb 2, 2016 at 10:30 AM, Awanthika Senarath 
> wrote:
>
>> Hello Alexander,
>>
>> After quite a bit of trouble-shooting from our end we got the script to
>> running,
>>
>> We had to change all your functions declarations from
>>
>> functions abc {}  ==> abc () {}
>>
>> in the script, which caused issues in the bash. I have attached the
>> changed script herewith.
>>
>> After changing them and running the script as ./che.sh run I get the
>> following error[1] ,
>>
>> I have jdk 1.8 and docker installed. So the possible error is  "6.
>> (Linux) Permissions not properly set  ==> Che must run as UID 1000
>> with user in docker group".
>>
>> I have docker installed and my default user can run docker without sudo
>> permission. Anything that I have missed?
>>
>> Any idea how to solve this?
>>
>>
>> [1]
>> /home/awanthika/WSO2/Eclipse-Che/eclipse-che-4.0.0-beta-13
>> Docker is natively installed and reachable...
>>
>> ## HOW TO CONNECT YOUR CHE CLIENT ###
>> After Che server has booted, you can connect your clients by:
>> 1. Open browser to http://localhost:8080, or:
>> 2. Open native chromium app.
>> #
>>
>>
>> JAVA_HOME is not set. Please set to directory of JVM or JRE.
>>
>> Looks like something went wrong. Possible issues:
>>   1. (Win | Mac) VirtualBox not installed  ==> Rerun Docker
>> Toolbox installation
>>   2. (Win | Mac) Docker Machine not installed  ==> Rerun Docker
>> Toolbox installation
>>   3. (Win | Mac) Docker is not reachable   ==> Docker VM failed
>> to start
>>   4. (Win | Mac) Docker ok, but docker ps fails==> Docker environment
>> variables not set properly
>>   5. (Linux) Docker is not reachable   ==> Install: wget -qO-
>> https://get.docker.com/ | sh
>>   6. (Linux) Permissions not properly set  ==> Che must run as
>> UID 1000 with user in docker group
>>   7. Could not find the Che app server ==> Did /tomcat get
>> moved away from CHE_HOME?
>>   8. Wrong version of Java found   ==> Che requires Java
>> 1.8
>>   9. Did you use the right parameter syntax?   ==> See usage
>>
>> We have seen issues with VirtualBox on Windows where your VM gets
>> corrupted when your computer is
>> suspended while the VM is still running. This will appear as SSH or
>> ethernet connection issues. This is
>> rare, but if encountered, current known solution is to uninstall
>> VirtualBox and Docker Toolbox, and then
>> reinstall.
>>
>> Che Environment Variables:
>>   (REQUIRED) JAVA_HOME ==> Location of Java
>> runtime
>>   (REQUIRED: WIN|MAC) DOCKER_TOOLBOX_INSTALL_PATH  ==> Location of Docker
>> Toolbox
>>   (REQUIRED: WIN|MAC) VBOX_MSI_INSTALL_PATH==> Location of
>> VirtualBox
>>   (OPTIONAL) CHE_HOME  ==> Directory where
>> Che is installed
>>   (OPTIONAL) CHE_LOCAL_CONF_DIR==> Directory with
>> custom Che .properties files
>>   (OPTIONAL) CHE_LOGS_DIR  ==> Directory for Che
>> output logs
>>   (OPTIONAL) CHE_DOCKER_MACHINE_NAME   ==> (Win | Mac) Name
>> of VM created by docker-machine
>>   (OPTIONAL) DOCKER_MACHINE_HOST   ==> (Linux) Docker
>> host IP - set if browser clients remote
>>
>> Usage:
>>   ch

[Dev] WSO2 Committers += Malith Munasinghe

[Amila Maha Arachchi]

Hi all,

Its my pleasure to welcome Malith Munasinghe as a WSO2 Committer. Malith is
a member of WSO2 Cloud Dev team and has been contributing to the team in
development, integration, deployment and alerting work. In recognition of
his contribution, he has been voted as a WSO2 Committer.

Malith, welcome aboard and keep up the good work..

Regards,
Amila.

-- 
*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] WSO2 Committers += Malith Munasinghe

[Jithendra Sirimanne]

Congrats :)

Best Regards
Jithendra

--
Jithendra Sirimanne
*Systems Engineer*
Mobile: +94 (0) 716 374696 <+94+(0)+716+374696>
Tel  : +94 112 145 345
Email  : jithen...@wso2.com

On Tue, Feb 2, 2016 at 4:38 PM, Amila Maha Arachchi  wrote:

> Hi all,
>
> Its my pleasure to welcome Malith Munasinghe as a WSO2 Committer. Malith
> is a member of WSO2 Cloud Dev team and has been contributing to the team in
> development, integration, deployment and alerting work. In recognition of
> his contribution, he has been voted as a WSO2 Committer.
>
> Malith, welcome aboard and keep up the good work..
>
> Regards,
> Amila.
>
> --
> *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

[Dev] TESTING MAIL SERVER SETTINGS - PLEASE IGNORE THIS

[Chamara Thilina]

TESTING MAIL SERVER SETTINGS - PLEASE IGNORE THIS

-- 
Chamara Thilina Samarakoon
Senior Systems Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94772929487
blog: http://mageconfig.blogspot.com/
linkedin: https://www.linkedin.com/pub/chamara-samarakoon
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS Authenticator] Issue in logout from mailchimp authenticator

[Hariprasath Thanarajah]

Hi Philips,

You can find the SSO tracer in the following attachment.



On Tue, Feb 2, 2016 at 2:22 PM, Chamara Philips  wrote:

> Hi Hariprasath,
> It is because the sessionID is null. It will be helpfull, if you can
> attach the SSO tracer.
>
> Thanks.
>
> On Tue, Feb 2, 2016 at 11:58 AM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi All,
>>
>> I have implemented mailChimp Authenticator for IS. When I logout from
>> sample webapp(travelocity.com) i got the below error,
>>
>> [2016-02-02 11:41:01,907] ERROR
>> {org.wso2.carbon.identity.sso.saml.processors.SPInitLogoutRequestProcessor}
>> -  ssoTokenId cookie not found in the logout request
>>
>>
>> Any suggestions?
>>
>> --
>>
>>
>> *Thank you and Regards**Hariprasath Thanarajah*
>> Associate Software Engineer | WSO2
>> E: haripras...@wso2.com
>> M: +94752806528
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Hareendra Chamara Philips
> *Software  Engineer*
> Mobile : +94 (0) 767 184161 <%2B94%20%280%29%20773%20451194>
> chama...@wso2.com 
>
>


-- 


*Thank you and Regards**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528


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

Re: [Dev] WSO2 Committers += Malith Munasinghe

[Shabir Mohamed]

Congrats Bro :D

-
*Shabir Mohamed*
*Software Engineer*
WSO2 Inc.; http://wso2.com
Email: sha...@wso2.com 
Mobile: +94 77 3516019 | +94 71 6583393

On Tue, Feb 2, 2016 at 4:48 PM, Jithendra Sirimanne 
wrote:

> Congrats :)
>
> Best Regards
> Jithendra
>
> --
> Jithendra Sirimanne
> *Systems Engineer*
> Mobile: +94 (0) 716 374696 <+94+(0)+716+374696>
> Tel  : +94 112 145 345
> Email  : jithen...@wso2.com
>
> On Tue, Feb 2, 2016 at 4:38 PM, Amila Maha Arachchi 
> wrote:
>
>> Hi all,
>>
>> Its my pleasure to welcome Malith Munasinghe as a WSO2 Committer. Malith
>> is a member of WSO2 Cloud Dev team and has been contributing to the team in
>> development, integration, deployment and alerting work. In recognition of
>> his contribution, he has been voted as a WSO2 Committer.
>>
>> Malith, welcome aboard and keep up the good work..
>>
>> Regards,
>> Amila.
>>
>> --
>> *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
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Malith Munasinghe

[Menaka Jayawardena]

Congratulations Malith

On Tue, Feb 2, 2016 at 4:52 PM, Shabir Mohamed  wrote:

> Congrats Bro :D
>
> -
> *Shabir Mohamed*
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> Email: sha...@wso2.com 
> Mobile: +94 77 3516019 | +94 71 6583393
>
> On Tue, Feb 2, 2016 at 4:48 PM, Jithendra Sirimanne 
> wrote:
>
>> Congrats :)
>>
>> Best Regards
>> Jithendra
>>
>> --
>> Jithendra Sirimanne
>> *Systems Engineer*
>> Mobile: +94 (0) 716 374696 <+94+(0)+716+374696>
>> Tel  : +94 112 145 345
>> Email  : jithen...@wso2.com
>>
>> On Tue, Feb 2, 2016 at 4:38 PM, Amila Maha Arachchi 
>> wrote:
>>
>>> Hi all,
>>>
>>> Its my pleasure to welcome Malith Munasinghe as a WSO2 Committer. Malith
>>> is a member of WSO2 Cloud Dev team and has been contributing to the team in
>>> development, integration, deployment and alerting work. In recognition of
>>> his contribution, he has been voted as a WSO2 Committer.
>>>
>>> Malith, welcome aboard and keep up the good work..
>>>
>>> Regards,
>>> Amila.
>>>
>>> --
>>> *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
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Issue when starting the server - SSLException: Connection has been shutdown

[Dilini Gunatilake]

Hi Carbon Team,

I wanted to browse the H2 repository and followed the blog in [1] and
configured the carbon.xml file accordingly. But, when I started the pack, I
observed the following error. What could be the reason for this?

This issue was observed in WSO2 ESB 4.10.0-Milestone 2 and DS 2.0.0 Beta 2
packs. (carbon 4.4.3)

ubuntu@ds-long-n1:~/releases/wso2ds-2.0.0-SNAPSHOT/bin$ sh wso2server.sh
JAVA_HOME environment variable is set to /home/ubuntu/software/jdk1.8.0_51
CARBON_HOME environment variable is set to
/home/ubuntu/releases/wso2ds-2.0.0-SNAPSHOT
Using Java memory options: -Xms256m -Xmx1024m

[2016-02-02 11:26:27,394]  INFO
{org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 Web
server...
[2016-02-02 11:26:28,006]  INFO
{org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 TCP
server...
[2016-02-02 11:26:28,030]  INFO
{org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 PG server...
org.h2.server.TcpServerThread@273ec7dc Connect
Connect
Disconnect
Close
javax.net.ssl.SSLException: Connection has been shutdown:
javax.net.ssl.SSLHandshakeException: Remote host closed connection during
handshake
at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1541)
at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1553)
at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:71)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at java.io.DataOutputStream.flush(DataOutputStream.java:123)
at org.h2.value.Transfer.flush(Transfer.java:85)
at org.h2.server.TcpServerThread.sendError(TcpServerThread.java:197)
at org.h2.server.TcpServerThread.run(TcpServerThread.java:129)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed
connection during handshake
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
at
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:928)
at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
at java.io.DataInputStream.readInt(DataInputStream.java:387)
at org.h2.value.Transfer.readInt(Transfer.java:145)
at org.h2.server.TcpServerThread.run(TcpServerThread.java:71)
... 1 more
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at sun.security.ssl.InputRecord.read(InputRecord.java:505)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
... 9 more
org.h2.server.TcpServerThread@273ec7dc Disconnect
org.h2.server.TcpServerThread@273ec7dc Close
[2016-02-02 11:26:29,170]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
Carbon...
[2016-02-02 11:26:29,177]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
Linux 3.13.0-36-generic, amd64
[2016-02-02 11:26:29,177]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
/home/ubuntu/software/jdk1.8.0_51/jre
[2016-02-02 11:26:29,178]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
1.8.0_51
[2016-02-02 11:26:29,181]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
Java HotSpot(TM) 64-Bit Server VM 25.51-b03,Oracle Corporation


[1] http://www.vitharana.org/2012/04/how-to-browse-h2-database-of-wso2.html


Thank you.

Regards,

-- 

*Dilini GunatilakeSoftware Engineer - QA Team*
Mobile : +94 (0) 771 162518
dili...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [che-dev] Trying Eclipse Che latest release on ubuntu

[Awanthika Senarath]

Still when I try to create a project it fails with the following exception,

 Creating machine [ws = workspacec3uqzvrq98trmwr5: env = wksp-vo1e: machine
= ws-machine]
Exception in thread "WorkspaceManager-0" java.lang.RuntimeException:
java.lang.IllegalArgumentException: protocol = http host = null
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1455)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
at
sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2979)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:489)
at
org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.doRequest(DefaultHttpJsonRequest.java:225)
at
org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.request(DefaultHttpJsonRequest.java:136)
at
org.eclipse.che.api.machine.server.WsAgentLauncherImpl.pingWsAgent(WsAgentLauncherImpl.java:122)
at
org.eclipse.che.api.machine.server.WsAgentLauncherImpl.startWsAgent(WsAgentLauncherImpl.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
at com.sun.proxy.$Proxy52.startWsAgent(Unknown Source)
at
org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:370)
at
org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:337)
at
org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:168)
at
org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.createMachine(RuntimeWorkspaceRegistry.java:451)
at
org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.startEnvironment(RuntimeWorkspaceRegistry.java:319)
at
org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.start(RuntimeWorkspaceRegistry.java:145)
at
org.eclipse.che.api.workspace.server.WorkspaceManager.performSyncStart(WorkspaceManager.java:642)
at
org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$9(WorkspaceManager.java:613)
at
org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: protocol = http host = null
at sun.net.spi.DefaultProxySelector.select(DefaultProxySelector.java:176)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1099)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
at
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1513)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
... 22 more


Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Tue, Feb 2, 2016 at 6:52 PM, Awanthika Senarath 
wrote:

> thanks for the explanation Alexander,
>
> It worked after I exported the JAVA_HOME. JAVA_HOME was declared but not
> exported in the bashrc file.
>
> I will create the issues.
>
> Regards
> Awanthika
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Tue, Feb 2, 2016 at 6:24 PM, Alexander Garagatyi <
> agaraga...@codenvy.com> wrote:
>
>> Would appreciate a clarification on this as your docs are a bit confusing
>>> :)
>>
>> Please create an issue on github.
>>
>> Is this correct? Do I need to create a docker image for Che to create the
>>> workspace in?
>>>
>> It is correct. You don't have to do anything else with docker.
>>
>> when we have the USE_DOCKER parameter false Che is not starting with
>>> docker? In that case is Che using the local file system of the machine?
>>>
>>> if not What is that parameter being used for?
>>>
>> when USE_DOCKER is false Che runs on localhost, but workspaces are still
>> in docker containers.
>> when USE_DOCKER is true Che runs in docker container, and workspaces are
>> in docker containers inside container where Che runs. It is called dind -
>> docker in docker.
>>
>> Your script failed because it was not able to detect JAVA_HOME variable.
>> Please check that it is set and exported. e.g.
>> *export JAVA_HOME=/my/path/to/java/folder*
>> in ~/.bashrc file
>>
>>
>> On Tue, Feb 2, 2016 at 1:14 PM, Awanthika Senarath 
>> wrote:
>>
>>> Hello Alexander,
>>>
>>> output is at [1].
>>>
>>> Would appreciate a clarification on this as your docs are a bit
>>> confusing :)
>

Re: [Dev] Issue when starting the server - SSLException: Connection has been shutdown

[Lahiru Cooray]

Hi Dilini,

Could you please share the carbon.xml file

On Tue, Feb 2, 2016 at 5:37 PM, Dilini Gunatilake  wrote:

> Hi Carbon Team,
>
> I wanted to browse the H2 repository and followed the blog in [1] and
> configured the carbon.xml file accordingly. But, when I started the pack, I
> observed the following error. What could be the reason for this?
>
> This issue was observed in WSO2 ESB 4.10.0-Milestone 2 and DS 2.0.0 Beta 2
> packs. (carbon 4.4.3)
>
> ubuntu@ds-long-n1:~/releases/wso2ds-2.0.0-SNAPSHOT/bin$ sh wso2server.sh
> JAVA_HOME environment variable is set to /home/ubuntu/software/jdk1.8.0_51
> CARBON_HOME environment variable is set to
> /home/ubuntu/releases/wso2ds-2.0.0-SNAPSHOT
> Using Java memory options: -Xms256m -Xmx1024m
>
> [2016-02-02 11:26:27,394]  INFO
> {org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 Web
> server...
> [2016-02-02 11:26:28,006]  INFO
> {org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 TCP
> server...
> [2016-02-02 11:26:28,030]  INFO
> {org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 PG server...
> org.h2.server.TcpServerThread@273ec7dc Connect
> Connect
> Disconnect
> Close
> javax.net.ssl.SSLException: Connection has been shutdown:
> javax.net.ssl.SSLHandshakeException: Remote host closed connection during
> handshake
> at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1541)
> at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1553)
> at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:71)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at java.io.DataOutputStream.flush(DataOutputStream.java:123)
> at org.h2.value.Transfer.flush(Transfer.java:85)
> at org.h2.server.TcpServerThread.sendError(TcpServerThread.java:197)
> at org.h2.server.TcpServerThread.run(TcpServerThread.java:129)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed
> connection during handshake
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:928)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
> at java.io.DataInputStream.readInt(DataInputStream.java:387)
> at org.h2.value.Transfer.readInt(Transfer.java:145)
> at org.h2.server.TcpServerThread.run(TcpServerThread.java:71)
> ... 1 more
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> at sun.security.ssl.InputRecord.read(InputRecord.java:505)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
> ... 9 more
> org.h2.server.TcpServerThread@273ec7dc Disconnect
> org.h2.server.TcpServerThread@273ec7dc Close
> [2016-02-02 11:26:29,170]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon...
> [2016-02-02 11:26:29,177]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Linux 3.13.0-36-generic, amd64
> [2016-02-02 11:26:29,177]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> /home/ubuntu/software/jdk1.8.0_51/jre
> [2016-02-02 11:26:29,178]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.8.0_51
> [2016-02-02 11:26:29,181]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 25.51-b03,Oracle Corporation
>
>
> [1]
> http://www.vitharana.org/2012/04/how-to-browse-h2-database-of-wso2.html
>
>
> Thank you.
>
> Regards,
>
> --
>
> *Dilini GunatilakeSoftware Engineer - QA Team*
> Mobile : +94 (0) 771 162518
> dili...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Lahiru Cooray*
Software Engineer
WSO2, Inc.;http://wso2.com/
lean.enterprise.middleware

Mobile: +94 715 654154
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Issue in worker/manager separated cluster in Kubernetes

[Vishanth Balasubramaniam]

Hi,

I have been working on WSO2 AS worker/manager separated cluster in
Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
CoreOs [1].
I built the docker images for manager and worker with the following
Kubernetes membership scheme configurations in the profile.

wso2::clustering :
>   enabled : true
>   local_member_host : local.as.wso2.com
>   local_member_port : 4000
>   membership_scheme : kubernetes
>   k8 :
> k8_master : http://172.17.8.101:8080
> k8_namespace : default
> k8_services : wso2as-manager,wso2as-worker
>   subDomain : mgt


wso2::clustering :
>   enabled : true
>   local_member_host : worker.as.wso2.com
>   local_member_port : 4000
>   membership_scheme : kubernetes
>   k8 :
> k8_master : http://172.17.8.101:8080
> k8_namespace : default
> k8_services : wso2as-manager,wso2as-worker
>   subDomain : worker


I SCP-ed the saved zip file of built images and loaded them in the
Kubernetes minion. Then I deployed the worker/manager service and
controller. I SSH-ed into the container where the manager node is running,
and there are no error logs as you can see below.

TID: [-1234] [] [2016-02-02 12:43:53,892]  INFO
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
> Using kubernetes based membership management scheme
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
> TID: [-1234] [] [2016-02-02 12:43:53,905]  INFO
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> -  Initializing kubernetes membership scheme...
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> -  Kubernetes clustering configuration: [master] http://172.17.8.101:8080
> [namespace] default [services] wso2as-manager
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> TID: [-1234] [] [2016-02-02 12:43:54,499]  INFO
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
> : https://10.244.78.4:9443/carbon/
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}


But it doesn't become the cluster coordinator node and there is no any
other log after this. Also I am not able to access the carbon management
console from my local machine.

But whereas, when I deploy only the default profile (not cluster), then it
runs fine and I am able to access the carbon management console from my
local machine with the provided nodeport.

Have I misconfigured anything in worker/manager cluster setup?

[1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster

Regards,
Vishanth

-- 
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com

mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in worker/manager separated cluster in Kubernetes

[Pubudu Gunatilaka]

Hi Vishanth,

Looks like you haven't configured the proxy port in catalina-server.xml.

In k8 we create a service for each port mapping according to [1]. This port
will be accessible via the nodeport in k8. So you need to set this node
port value in the catalina-sever.xml using hiera data. If this is not set
correctly you cannot access the management console.

[1] -
https://github.com/wso2/kubernetes-artifacts/blob/master/wso2as/kubernetes/wso2as-manager-service.yaml#L13

Thank you!

On Tue, Feb 2, 2016 at 9:49 PM, Vishanth Balasubramaniam  wrote:

> Hi,
>
> I have been working on WSO2 AS worker/manager separated cluster in
> Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
> CoreOs [1].
> I built the docker images for manager and worker with the following
> Kubernetes membership scheme configurations in the profile.
>
> wso2::clustering :
>>   enabled : true
>>   local_member_host : local.as.wso2.com
>>   local_member_port : 4000
>>   membership_scheme : kubernetes
>>   k8 :
>> k8_master : http://172.17.8.101:8080
>> k8_namespace : default
>> k8_services : wso2as-manager,wso2as-worker
>>   subDomain : mgt
>
>
> wso2::clustering :
>>   enabled : true
>>   local_member_host : worker.as.wso2.com
>>   local_member_port : 4000
>>   membership_scheme : kubernetes
>>   k8 :
>> k8_master : http://172.17.8.101:8080
>> k8_namespace : default
>> k8_services : wso2as-manager,wso2as-worker
>>   subDomain : worker
>
>
> I SCP-ed the saved zip file of built images and loaded them in the
> Kubernetes minion. Then I deployed the worker/manager service and
> controller. I SSH-ed into the container where the manager node is running,
> and there are no error logs as you can see below.
>
> TID: [-1234] [] [2016-02-02 12:43:53,892]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>> Using kubernetes based membership management scheme
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>> TID: [-1234] [] [2016-02-02 12:43:53,905]  INFO
>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>> -  Initializing kubernetes membership scheme...
>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>> TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>> -  Kubernetes clustering configuration: [master] http://172.17.8.101:8080
>> [namespace] default [services] wso2as-manager
>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>> TID: [-1234] [] [2016-02-02 12:43:54,499]  INFO
>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
>> : https://10.244.78.4:9443/carbon/
>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
>
>
> But it doesn't become the cluster coordinator node and there is no any
> other log after this. Also I am not able to access the carbon management
> console from my local machine.
>
> But whereas, when I deploy only the default profile (not cluster), then it
> runs fine and I am able to access the carbon management console from my
> local machine with the provided nodeport.
>
> Have I misconfigured anything in worker/manager cluster setup?
>
> [1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster
>
> Regards,
> Vishanth
>
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94 77 17 377 18*
> about me: *http://about.me/vishanth *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774079049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in worker/manager separated cluster in Kubernetes

[Imesh Gunaratne]

I noted one other thing in the log:

TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
{org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme} -
 Kubernetes clustering configuration: [master] http://172.17.8.101:8080
[namespace] default [services] wso2as-manager
{org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}

K8S services only has manager service. See the highlighted text. We need to
add both manager and worker here to let them connect to the same carbon
cluster.

Thanks

On Wed, Feb 3, 2016 at 12:19 AM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:

> Hi,
>
> I have been working on WSO2 AS worker/manager separated cluster in
> Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
> CoreOs [1].
> I built the docker images for manager and worker with the following
> Kubernetes membership scheme configurations in the profile.
>
> wso2::clustering :
>>   enabled : true
>>   local_member_host : local.as.wso2.com
>>   local_member_port : 4000
>>   membership_scheme : kubernetes
>>   k8 :
>> k8_master : http://172.17.8.101:8080
>> k8_namespace : default
>> k8_services : wso2as-manager,wso2as-worker
>>   subDomain : mgt
>
>
> wso2::clustering :
>>   enabled : true
>>   local_member_host : worker.as.wso2.com
>>   local_member_port : 4000
>>   membership_scheme : kubernetes
>>   k8 :
>> k8_master : http://172.17.8.101:8080
>> k8_namespace : default
>> k8_services : wso2as-manager,wso2as-worker
>>   subDomain : worker
>
>
> I SCP-ed the saved zip file of built images and loaded them in the
> Kubernetes minion. Then I deployed the worker/manager service and
> controller. I SSH-ed into the container where the manager node is running,
> and there are no error logs as you can see below.
>
> TID: [-1234] [] [2016-02-02 12:43:53,892]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>> Using kubernetes based membership management scheme
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>> TID: [-1234] [] [2016-02-02 12:43:53,905]  INFO
>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>> -  Initializing kubernetes membership scheme...
>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>> TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>> -  Kubernetes clustering configuration: [master] http://172.17.8.101:8080
>> [namespace] default [services] wso2as-manager
>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>> TID: [-1234] [] [2016-02-02 12:43:54,499]  INFO
>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
>> : https://10.244.78.4:9443/carbon/
>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
>
>
> But it doesn't become the cluster coordinator node and there is no any
> other log after this. Also I am not able to access the carbon management
> console from my local machine.
>
> But whereas, when I deploy only the default profile (not cluster), then it
> runs fine and I am able to access the carbon management console from my
> local machine with the provided nodeport.
>
> Have I misconfigured anything in worker/manager cluster setup?
>
> [1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster
>
> Regards,
> Vishanth
>
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94 77 17 377 18*
> about me: *http://about.me/vishanth *
>



-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in worker/manager separated cluster in Kubernetes

[Isuru Haththotuwa]

On Tue, Feb 2, 2016 at 10:28 PM, Imesh Gunaratne  wrote:

> I noted one other thing in the log:
>
> TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme} -
>  Kubernetes clustering configuration: [master] http://172.17.8.101:8080
> [namespace] default [services] wso2as-manager
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>
> K8S services only has manager service. See the highlighted text. We need
> to add both manager and worker here to let them connect to the same carbon
> cluster.
>
AFAIK this is the correct way. If we start the manager first, there is no
worker pod at that moment. So the manager can start on its own. When the
worker pod is being created, it can add both manager and worker services'
IPs and connect to the manager node.

>
> Thanks
>
> On Wed, Feb 3, 2016 at 12:19 AM, Vishanth Balasubramaniam <
> vishan...@wso2.com> wrote:
>
>> Hi,
>>
>> I have been working on WSO2 AS worker/manager separated cluster in
>> Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
>> CoreOs [1].
>> I built the docker images for manager and worker with the following
>> Kubernetes membership scheme configurations in the profile.
>>
>> wso2::clustering :
>>>   enabled : true
>>>   local_member_host : local.as.wso2.com
>>>   local_member_port : 4000
>>>   membership_scheme : kubernetes
>>>   k8 :
>>> k8_master : http://172.17.8.101:8080
>>> k8_namespace : default
>>> k8_services : wso2as-manager,wso2as-worker
>>>   subDomain : mgt
>>
>>
>> wso2::clustering :
>>>   enabled : true
>>>   local_member_host : worker.as.wso2.com
>>>   local_member_port : 4000
>>>   membership_scheme : kubernetes
>>>   k8 :
>>> k8_master : http://172.17.8.101:8080
>>> k8_namespace : default
>>> k8_services : wso2as-manager,wso2as-worker
>>>   subDomain : worker
>>
>>
>> I SCP-ed the saved zip file of built images and loaded them in the
>> Kubernetes minion. Then I deployed the worker/manager service and
>> controller. I SSH-ed into the container where the manager node is running,
>> and there are no error logs as you can see below.
>>
>> TID: [-1234] [] [2016-02-02 12:43:53,892]  INFO
>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>> Using kubernetes based membership management scheme
>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>>> TID: [-1234] [] [2016-02-02 12:43:53,905]  INFO
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> -  Initializing kubernetes membership scheme...
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> -  Kubernetes clustering configuration: [master]
>>> http://172.17.8.101:8080 [namespace] default [services] wso2as-manager
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> TID: [-1234] [] [2016-02-02 12:43:54,499]  INFO
>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
>>> : https://10.244.78.4:9443/carbon/
>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
>>
>>
>> But it doesn't become the cluster coordinator node and there is no any
>> other log after this. Also I am not able to access the carbon management
>> console from my local machine.
>>
>> But whereas, when I deploy only the default profile (not cluster), then
>> it runs fine and I am able to access the carbon management console from my
>> local machine with the provided nodeport.
>>
>> Have I misconfigured anything in worker/manager cluster setup?
>>
>> [1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster
>>
>> Regards,
>> Vishanth
>>
>> --
>> *Vishanth Balasubramaniam*
>> Committer & PMC Member, Apache Stratos,
>> Software Engineer, WSO2 Inc.; http://wso2.com
>>
>> mobile: *+94 77 17 377 18*
>> about me: *http://about.me/vishanth *
>>
>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in worker/manager separated cluster in Kubernetes

[Vishanth Balasubramaniam]

On Tue, Feb 2, 2016 at 10:28 PM, Imesh Gunaratne  wrote:

> I noted one other thing in the log:
>
> TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme} -
>  Kubernetes clustering configuration: [master] http://172.17.8.101:8080
> [namespace] default [services] wso2as-manager
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>
> K8S services only has manager service. See the highlighted text. We need
> to add both manager and worker here to let them connect to the same carbon
> cluster.
>

I tried with both [services] wso2as-manager,wso2as-worker as well as
[services] wso2as-manager


>
> Thanks
>
> On Wed, Feb 3, 2016 at 12:19 AM, Vishanth Balasubramaniam <
> vishan...@wso2.com> wrote:
>
>> Hi,
>>
>> I have been working on WSO2 AS worker/manager separated cluster in
>> Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
>> CoreOs [1].
>> I built the docker images for manager and worker with the following
>> Kubernetes membership scheme configurations in the profile.
>>
>> wso2::clustering :
>>>   enabled : true
>>>   local_member_host : local.as.wso2.com
>>>   local_member_port : 4000
>>>   membership_scheme : kubernetes
>>>   k8 :
>>> k8_master : http://172.17.8.101:8080
>>> k8_namespace : default
>>> k8_services : wso2as-manager,wso2as-worker
>>>   subDomain : mgt
>>
>>
>> wso2::clustering :
>>>   enabled : true
>>>   local_member_host : worker.as.wso2.com
>>>   local_member_port : 4000
>>>   membership_scheme : kubernetes
>>>   k8 :
>>> k8_master : http://172.17.8.101:8080
>>> k8_namespace : default
>>> k8_services : wso2as-manager,wso2as-worker
>>>   subDomain : worker
>>
>>
>> I SCP-ed the saved zip file of built images and loaded them in the
>> Kubernetes minion. Then I deployed the worker/manager service and
>> controller. I SSH-ed into the container where the manager node is running,
>> and there are no error logs as you can see below.
>>
>> TID: [-1234] [] [2016-02-02 12:43:53,892]  INFO
>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>> Using kubernetes based membership management scheme
>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>>> TID: [-1234] [] [2016-02-02 12:43:53,905]  INFO
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> -  Initializing kubernetes membership scheme...
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> -  Kubernetes clustering configuration: [master]
>>> http://172.17.8.101:8080 [namespace] default [services] wso2as-manager
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> TID: [-1234] [] [2016-02-02 12:43:54,499]  INFO
>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
>>> : https://10.244.78.4:9443/carbon/
>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
>>
>>
>> But it doesn't become the cluster coordinator node and there is no any
>> other log after this. Also I am not able to access the carbon management
>> console from my local machine.
>>
>> But whereas, when I deploy only the default profile (not cluster), then
>> it runs fine and I am able to access the carbon management console from my
>> local machine with the provided nodeport.
>>
>> Have I misconfigured anything in worker/manager cluster setup?
>>
>> [1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster
>>
>> Regards,
>> Vishanth
>>
>> --
>> *Vishanth Balasubramaniam*
>> Committer & PMC Member, Apache Stratos,
>> Software Engineer, WSO2 Inc.; http://wso2.com
>>
>> mobile: *+94 77 17 377 18*
>> about me: *http://about.me/vishanth *
>>
>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>


-- 
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com

mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in worker/manager separated cluster in Kubernetes

[Imesh Gunaratne]

On Wed, Feb 3, 2016 at 1:13 AM, Isuru Haththotuwa  wrote:

>
> AFAIK this is the correct way. If we start the manager first, there is no
> worker pod at that moment. So the manager can start on its own. When the
> worker pod is being created, it can add both manager and worker services'
> IPs and connect to the manager node.
>

No Isuru, this is the list of services [1] given to each Carbon server
instance to query Pods. So ideally it should have both worker service and
manager service.

[1]
https://github.com/wso2/kubernetes-artifacts/blob/master/common/kubernetes-membership-scheme/src/main/java/org/wso2/carbon/membership/scheme/kubernetes/KubernetesMembershipScheme.java#L141

>
>> Thanks
>>
>> On Wed, Feb 3, 2016 at 12:19 AM, Vishanth Balasubramaniam <
>> vishan...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I have been working on WSO2 AS worker/manager separated cluster in
>>> Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
>>> CoreOs [1].
>>> I built the docker images for manager and worker with the following
>>> Kubernetes membership scheme configurations in the profile.
>>>
>>> wso2::clustering :
   enabled : true
   local_member_host : local.as.wso2.com
   local_member_port : 4000
   membership_scheme : kubernetes
   k8 :
 k8_master : http://172.17.8.101:8080
 k8_namespace : default
 k8_services : wso2as-manager,wso2as-worker
   subDomain : mgt
>>>
>>>
>>> wso2::clustering :
   enabled : true
   local_member_host : worker.as.wso2.com
   local_member_port : 4000
   membership_scheme : kubernetes
   k8 :
 k8_master : http://172.17.8.101:8080
 k8_namespace : default
 k8_services : wso2as-manager,wso2as-worker
   subDomain : worker
>>>
>>>
>>> I SCP-ed the saved zip file of built images and loaded them in the
>>> Kubernetes minion. Then I deployed the worker/manager service and
>>> controller. I SSH-ed into the container where the manager node is running,
>>> and there are no error logs as you can see below.
>>>
>>> TID: [-1234] [] [2016-02-02 12:43:53,892]  INFO
 {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
 Using kubernetes based membership management scheme
 {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
 TID: [-1234] [] [2016-02-02 12:43:53,905]  INFO
 {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
 -  Initializing kubernetes membership scheme...
 {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
 TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
 {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
 -  Kubernetes clustering configuration: [master]
 http://172.17.8.101:8080 [namespace] default [services] wso2as-manager
 {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
 TID: [-1234] [] [2016-02-02 12:43:54,499]  INFO
 {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
 : https://10.244.78.4:9443/carbon/
 {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
>>>
>>>
>>> But it doesn't become the cluster coordinator node and there is no any
>>> other log after this. Also I am not able to access the carbon management
>>> console from my local machine.
>>>
>>> But whereas, when I deploy only the default profile (not cluster), then
>>> it runs fine and I am able to access the carbon management console from my
>>> local machine with the provided nodeport.
>>>
>>> Have I misconfigured anything in worker/manager cluster setup?
>>>
>>> [1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster
>>>
>>> Regards,
>>> Vishanth
>>>
>>> --
>>> *Vishanth Balasubramaniam*
>>> Committer & PMC Member, Apache Stratos,
>>> Software Engineer, WSO2 Inc.; http://wso2.com
>>>
>>> mobile: *+94 77 17 377 18*
>>> about me: *http://about.me/vishanth *
>>>
>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> Lean . Enterprise . Middleware
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in worker/manager separated cluster in Kubernetes

[Vishanth Balasubramaniam]

Hi Pubudu,

Even with the proxy port set in the manager and worker profiles, it is
still having the same problem. Sharing the axis2.xml and
catalina-server.xml [1] [2] of the manager node.

[1] -
https://drive.google.com/a/wso2.com/file/d/0B1Vp6McRCyeJVVJiZ0pMaUcwVEE/view?usp=sharing
[2] -
https://drive.google.com/a/wso2.com/file/d/0B1Vp6McRCyeJTFFPOEpNTFB5Y00/view?usp=sharing

Regards,
Vishanth

On Tue, Feb 2, 2016 at 10:25 PM, Pubudu Gunatilaka  wrote:

> Hi Vishanth,
>
> Looks like you haven't configured the proxy port in catalina-server.xml.
>
> In k8 we create a service for each port mapping according to [1]. This
> port will be accessible via the nodeport in k8. So you need to set this
> node port value in the catalina-sever.xml using hiera data. If this is not
> set correctly you cannot access the management console.
>
> [1] -
> https://github.com/wso2/kubernetes-artifacts/blob/master/wso2as/kubernetes/wso2as-manager-service.yaml#L13
>
> Thank you!
>
> On Tue, Feb 2, 2016 at 9:49 PM, Vishanth Balasubramaniam <
> vishan...@wso2.com> wrote:
>
>> Hi,
>>
>> I have been working on WSO2 AS worker/manager separated cluster in
>> Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
>> CoreOs [1].
>> I built the docker images for manager and worker with the following
>> Kubernetes membership scheme configurations in the profile.
>>
>> wso2::clustering :
>>>   enabled : true
>>>   local_member_host : local.as.wso2.com
>>>   local_member_port : 4000
>>>   membership_scheme : kubernetes
>>>   k8 :
>>> k8_master : http://172.17.8.101:8080
>>> k8_namespace : default
>>> k8_services : wso2as-manager,wso2as-worker
>>>   subDomain : mgt
>>
>>
>> wso2::clustering :
>>>   enabled : true
>>>   local_member_host : worker.as.wso2.com
>>>   local_member_port : 4000
>>>   membership_scheme : kubernetes
>>>   k8 :
>>> k8_master : http://172.17.8.101:8080
>>> k8_namespace : default
>>> k8_services : wso2as-manager,wso2as-worker
>>>   subDomain : worker
>>
>>
>> I SCP-ed the saved zip file of built images and loaded them in the
>> Kubernetes minion. Then I deployed the worker/manager service and
>> controller. I SSH-ed into the container where the manager node is running,
>> and there are no error logs as you can see below.
>>
>> TID: [-1234] [] [2016-02-02 12:43:53,892]  INFO
>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>> Using kubernetes based membership management scheme
>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>>> TID: [-1234] [] [2016-02-02 12:43:53,905]  INFO
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> -  Initializing kubernetes membership scheme...
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> -  Kubernetes clustering configuration: [master]
>>> http://172.17.8.101:8080 [namespace] default [services] wso2as-manager
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> TID: [-1234] [] [2016-02-02 12:43:54,499]  INFO
>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
>>> : https://10.244.78.4:9443/carbon/
>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
>>
>>
>> But it doesn't become the cluster coordinator node and there is no any
>> other log after this. Also I am not able to access the carbon management
>> console from my local machine.
>>
>> But whereas, when I deploy only the default profile (not cluster), then
>> it runs fine and I am able to access the carbon management console from my
>> local machine with the provided nodeport.
>>
>> Have I misconfigured anything in worker/manager cluster setup?
>>
>> [1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster
>>
>> Regards,
>> Vishanth
>>
>> --
>> *Vishanth Balasubramaniam*
>> Committer & PMC Member, Apache Stratos,
>> Software Engineer, WSO2 Inc.; http://wso2.com
>>
>> mobile: *+94 77 17 377 18*
>> about me: *http://about.me/vishanth *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774079049 <%2B94772207163>
>
>


-- 
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com

mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue when starting the server - SSLException: Connection has been shutdown

[Vishanth Balasubramaniam]

Hi Dilini,

Try commenting out the rest of the properties in H2DatabaseConfiguration in
carbon.xml.


> 
> 8082
> 
>
> **
> 


Regards,
Vishanth

On Tue, Feb 2, 2016 at 5:37 PM, Dilini Gunatilake  wrote:

> Hi Carbon Team,
>
> I wanted to browse the H2 repository and followed the blog in [1] and
> configured the carbon.xml file accordingly. But, when I started the pack, I
> observed the following error. What could be the reason for this?
>
> This issue was observed in WSO2 ESB 4.10.0-Milestone 2 and DS 2.0.0 Beta 2
> packs. (carbon 4.4.3)
>
> ubuntu@ds-long-n1:~/releases/wso2ds-2.0.0-SNAPSHOT/bin$ sh wso2server.sh
> JAVA_HOME environment variable is set to /home/ubuntu/software/jdk1.8.0_51
> CARBON_HOME environment variable is set to
> /home/ubuntu/releases/wso2ds-2.0.0-SNAPSHOT
> Using Java memory options: -Xms256m -Xmx1024m
>
> [2016-02-02 11:26:27,394]  INFO
> {org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 Web
> server...
> [2016-02-02 11:26:28,006]  INFO
> {org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 TCP
> server...
> [2016-02-02 11:26:28,030]  INFO
> {org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 PG server...
> org.h2.server.TcpServerThread@273ec7dc Connect
> Connect
> Disconnect
> Close
> javax.net.ssl.SSLException: Connection has been shutdown:
> javax.net.ssl.SSLHandshakeException: Remote host closed connection during
> handshake
> at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1541)
> at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1553)
> at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:71)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at java.io.DataOutputStream.flush(DataOutputStream.java:123)
> at org.h2.value.Transfer.flush(Transfer.java:85)
> at org.h2.server.TcpServerThread.sendError(TcpServerThread.java:197)
> at org.h2.server.TcpServerThread.run(TcpServerThread.java:129)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed
> connection during handshake
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:928)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
> at java.io.DataInputStream.readInt(DataInputStream.java:387)
> at org.h2.value.Transfer.readInt(Transfer.java:145)
> at org.h2.server.TcpServerThread.run(TcpServerThread.java:71)
> ... 1 more
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> at sun.security.ssl.InputRecord.read(InputRecord.java:505)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
> ... 9 more
> org.h2.server.TcpServerThread@273ec7dc Disconnect
> org.h2.server.TcpServerThread@273ec7dc Close
> [2016-02-02 11:26:29,170]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon...
> [2016-02-02 11:26:29,177]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Linux 3.13.0-36-generic, amd64
> [2016-02-02 11:26:29,177]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> /home/ubuntu/software/jdk1.8.0_51/jre
> [2016-02-02 11:26:29,178]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.8.0_51
> [2016-02-02 11:26:29,181]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 25.51-b03,Oracle Corporation
>
>
> [1]
> http://www.vitharana.org/2012/04/how-to-browse-h2-database-of-wso2.html
>
>
> Thank you.
>
> Regards,
>
> --
>
> *Dilini GunatilakeSoftware Engineer - QA Team*
> Mobile : +94 (0) 771 162518
> dili...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com

mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in worker/manager separated cluster in Kubernetes

[Isuru Haththotuwa]

Hi,

Debugged the code to find the problem. In the K8s membership scheme, we
were earlier creating a HTTPS connection always, which was attempting to
create a HTTPS connection even to a non secure endpoint. That was the
issue. I changed that to create a secure/non-secure connection depending on
the URL, and that resolved the issue. Committed the fix now.

On Wed, Feb 3, 2016 at 1:20 AM, Vishanth Balasubramaniam  wrote:

> Hi Pubudu,
>
> Even with the proxy port set in the manager and worker profiles, it is
> still having the same problem. Sharing the axis2.xml and
> catalina-server.xml [1] [2] of the manager node.
>
> [1] -
> https://drive.google.com/a/wso2.com/file/d/0B1Vp6McRCyeJVVJiZ0pMaUcwVEE/view?usp=sharing
> [2] -
> https://drive.google.com/a/wso2.com/file/d/0B1Vp6McRCyeJTFFPOEpNTFB5Y00/view?usp=sharing
>
> Regards,
> Vishanth
>
> On Tue, Feb 2, 2016 at 10:25 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Vishanth,
>>
>> Looks like you haven't configured the proxy port in catalina-server.xml.
>>
>> In k8 we create a service for each port mapping according to [1]. This
>> port will be accessible via the nodeport in k8. So you need to set this
>> node port value in the catalina-sever.xml using hiera data. If this is not
>> set correctly you cannot access the management console.
>>
>> [1] -
>> https://github.com/wso2/kubernetes-artifacts/blob/master/wso2as/kubernetes/wso2as-manager-service.yaml#L13
>>
>> Thank you!
>>
>> On Tue, Feb 2, 2016 at 9:49 PM, Vishanth Balasubramaniam <
>> vishan...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I have been working on WSO2 AS worker/manager separated cluster in
>>> Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
>>> CoreOs [1].
>>> I built the docker images for manager and worker with the following
>>> Kubernetes membership scheme configurations in the profile.
>>>
>>> wso2::clustering :
   enabled : true
   local_member_host : local.as.wso2.com
   local_member_port : 4000
   membership_scheme : kubernetes
   k8 :
 k8_master : http://172.17.8.101:8080
 k8_namespace : default
 k8_services : wso2as-manager,wso2as-worker
   subDomain : mgt
>>>
>>>
>>> wso2::clustering :
   enabled : true
   local_member_host : worker.as.wso2.com
   local_member_port : 4000
   membership_scheme : kubernetes
   k8 :
 k8_master : http://172.17.8.101:8080
 k8_namespace : default
 k8_services : wso2as-manager,wso2as-worker
   subDomain : worker
>>>
>>>
>>> I SCP-ed the saved zip file of built images and loaded them in the
>>> Kubernetes minion. Then I deployed the worker/manager service and
>>> controller. I SSH-ed into the container where the manager node is running,
>>> and there are no error logs as you can see below.
>>>
>>> TID: [-1234] [] [2016-02-02 12:43:53,892]  INFO
 {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
 Using kubernetes based membership management scheme
 {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
 TID: [-1234] [] [2016-02-02 12:43:53,905]  INFO
 {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
 -  Initializing kubernetes membership scheme...
 {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
 TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
 {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
 -  Kubernetes clustering configuration: [master]
 http://172.17.8.101:8080 [namespace] default [services] wso2as-manager
 {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
 TID: [-1234] [] [2016-02-02 12:43:54,499]  INFO
 {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
 : https://10.244.78.4:9443/carbon/
 {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
>>>
>>>
>>> But it doesn't become the cluster coordinator node and there is no any
>>> other log after this. Also I am not able to access the carbon management
>>> console from my local machine.
>>>
>>> But whereas, when I deploy only the default profile (not cluster), then
>>> it runs fine and I am able to access the carbon management console from my
>>> local machine with the provided nodeport.
>>>
>>> Have I misconfigured anything in worker/manager cluster setup?
>>>
>>> [1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster
>>>
>>> Regards,
>>> Vishanth
>>>
>>> --
>>> *Vishanth Balasubramaniam*
>>> Committer & PMC Member, Apache Stratos,
>>> Software Engineer, WSO2 Inc.; http://wso2.com
>>>
>>> mobile: *+94 77 17 377 18*
>>> about me: *http://about.me/vishanth *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : 

Re: [Dev] Issue in worker/manager separated cluster in Kubernetes

[Vishanth Balasubramaniam]

Hi,

I will test it with the latest changes and see if it fixes the issue.

Regards,
Vishanth

On Wed, Feb 3, 2016 at 2:05 AM, Isuru Haththotuwa  wrote:

> Hi,
>
> Debugged the code to find the problem. In the K8s membership scheme, we
> were earlier creating a HTTPS connection always, which was attempting to
> create a HTTPS connection even to a non secure endpoint. That was the
> issue. I changed that to create a secure/non-secure connection depending on
> the URL, and that resolved the issue. Committed the fix now.
>
> On Wed, Feb 3, 2016 at 1:20 AM, Vishanth Balasubramaniam <
> vishan...@wso2.com> wrote:
>
>> Hi Pubudu,
>>
>> Even with the proxy port set in the manager and worker profiles, it is
>> still having the same problem. Sharing the axis2.xml and
>> catalina-server.xml [1] [2] of the manager node.
>>
>> [1] -
>> https://drive.google.com/a/wso2.com/file/d/0B1Vp6McRCyeJVVJiZ0pMaUcwVEE/view?usp=sharing
>> [2] -
>> https://drive.google.com/a/wso2.com/file/d/0B1Vp6McRCyeJTFFPOEpNTFB5Y00/view?usp=sharing
>>
>> Regards,
>> Vishanth
>>
>> On Tue, Feb 2, 2016 at 10:25 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Vishanth,
>>>
>>> Looks like you haven't configured the proxy port in catalina-server.xml.
>>>
>>> In k8 we create a service for each port mapping according to [1]. This
>>> port will be accessible via the nodeport in k8. So you need to set this
>>> node port value in the catalina-sever.xml using hiera data. If this is not
>>> set correctly you cannot access the management console.
>>>
>>> [1] -
>>> https://github.com/wso2/kubernetes-artifacts/blob/master/wso2as/kubernetes/wso2as-manager-service.yaml#L13
>>>
>>> Thank you!
>>>
>>> On Tue, Feb 2, 2016 at 9:49 PM, Vishanth Balasubramaniam <
>>> vishan...@wso2.com> wrote:
>>>
 Hi,

 I have been working on WSO2 AS worker/manager separated cluster in
 Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
 CoreOs [1].
 I built the docker images for manager and worker with the following
 Kubernetes membership scheme configurations in the profile.

 wso2::clustering :
>   enabled : true
>   local_member_host : local.as.wso2.com
>   local_member_port : 4000
>   membership_scheme : kubernetes
>   k8 :
> k8_master : http://172.17.8.101:8080
> k8_namespace : default
> k8_services : wso2as-manager,wso2as-worker
>   subDomain : mgt


 wso2::clustering :
>   enabled : true
>   local_member_host : worker.as.wso2.com
>   local_member_port : 4000
>   membership_scheme : kubernetes
>   k8 :
> k8_master : http://172.17.8.101:8080
> k8_namespace : default
> k8_services : wso2as-manager,wso2as-worker
>   subDomain : worker


 I SCP-ed the saved zip file of built images and loaded them in the
 Kubernetes minion. Then I deployed the worker/manager service and
 controller. I SSH-ed into the container where the manager node is running,
 and there are no error logs as you can see below.

 TID: [-1234] [] [2016-02-02 12:43:53,892]  INFO
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
> Using kubernetes based membership management scheme
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
> TID: [-1234] [] [2016-02-02 12:43:53,905]  INFO
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> -  Initializing kubernetes membership scheme...
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> -  Kubernetes clustering configuration: [master]
> http://172.17.8.101:8080 [namespace] default [services]
> wso2as-manager
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> TID: [-1234] [] [2016-02-02 12:43:54,499]  INFO
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
> : https://10.244.78.4:9443/carbon/
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}


 But it doesn't become the cluster coordinator node and there is no any
 other log after this. Also I am not able to access the carbon management
 console from my local machine.

 But whereas, when I deploy only the default profile (not cluster), then
 it runs fine and I am able to access the carbon management console from my
 local machine with the provided nodeport.

 Have I misconfigured anything in worker/manager cluster setup?

 [1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster

 Regards,
 Vishanth

 --
 *Vishanth Balasubramaniam*
 Committer & PMC Member, Apache Stratos,
 Software Engineer, WSO2 Inc.; http://wso2.com

 mobile: *+94 77 17 377 18*
 about me: *http://about.me/vishanth 

Re: [Dev] Issue in worker/manager separated cluster in Kubernetes

[Isuru Haththotuwa]

On Tue, Feb 2, 2016 at 10:47 PM, Imesh Gunaratne  wrote:

>
>
> On Wed, Feb 3, 2016 at 1:13 AM, Isuru Haththotuwa  wrote:
>
>>
>> AFAIK this is the correct way. If we start the manager first, there is no
>> worker pod at that moment. So the manager can start on its own. When the
>> worker pod is being created, it can add both manager and worker services'
>> IPs and connect to the manager node.
>>
>
> No Isuru, this is the list of services [1] given to each Carbon server
> instance to query Pods. So ideally it should have both worker service and
> manager service.
>
Thanks Imesh. I was of the idea that we should add individual pod IPs.

>
> [1]
> https://github.com/wso2/kubernetes-artifacts/blob/master/common/kubernetes-membership-scheme/src/main/java/org/wso2/carbon/membership/scheme/kubernetes/KubernetesMembershipScheme.java#L141
>
>>
>>> Thanks
>>>
>>> On Wed, Feb 3, 2016 at 12:19 AM, Vishanth Balasubramaniam <
>>> vishan...@wso2.com> wrote:
>>>
 Hi,

 I have been working on WSO2 AS worker/manager separated cluster in
 Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
 CoreOs [1].
 I built the docker images for manager and worker with the following
 Kubernetes membership scheme configurations in the profile.

 wso2::clustering :
>   enabled : true
>   local_member_host : local.as.wso2.com
>   local_member_port : 4000
>   membership_scheme : kubernetes
>   k8 :
> k8_master : http://172.17.8.101:8080
> k8_namespace : default
> k8_services : wso2as-manager,wso2as-worker
>   subDomain : mgt


 wso2::clustering :
>   enabled : true
>   local_member_host : worker.as.wso2.com
>   local_member_port : 4000
>   membership_scheme : kubernetes
>   k8 :
> k8_master : http://172.17.8.101:8080
> k8_namespace : default
> k8_services : wso2as-manager,wso2as-worker
>   subDomain : worker


 I SCP-ed the saved zip file of built images and loaded them in the
 Kubernetes minion. Then I deployed the worker/manager service and
 controller. I SSH-ed into the container where the manager node is running,
 and there are no error logs as you can see below.

 TID: [-1234] [] [2016-02-02 12:43:53,892]  INFO
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
> Using kubernetes based membership management scheme
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
> TID: [-1234] [] [2016-02-02 12:43:53,905]  INFO
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> -  Initializing kubernetes membership scheme...
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> TID: [-1234] [] [2016-02-02 12:43:53,909]  INFO
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> -  Kubernetes clustering configuration: [master]
> http://172.17.8.101:8080 [namespace] default [services]
> wso2as-manager
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> TID: [-1234] [] [2016-02-02 12:43:54,499]  INFO
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} -  Mgt Console URL
> : https://10.244.78.4:9443/carbon/
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}


 But it doesn't become the cluster coordinator node and there is no any
 other log after this. Also I am not able to access the carbon management
 console from my local machine.

 But whereas, when I deploy only the default profile (not cluster), then
 it runs fine and I am able to access the carbon management console from my
 local machine with the provided nodeport.

 Have I misconfigured anything in worker/manager cluster setup?

 [1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster

 Regards,
 Vishanth

 --
 *Vishanth Balasubramaniam*
 Committer & PMC Member, Apache Stratos,
 Software Engineer, WSO2 Inc.; http://wso2.com

 mobile: *+94 77 17 377 18*
 about me: *http://about.me/vishanth *

>>>
>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.gunaratne.org
>>> Lean . Enterprise . Middleware
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev m

Re: [Dev] [che-dev] Trying Eclipse Che latest release on ubuntu

[Awanthika Senarath]

Hello Alexander,

I have created the issues [1]  [2] and [3]


Regards
Awanthika


[1] https://github.com/codenvy/che/issues/260

[2] https://github.com/codenvy/che/issues/261

[3] https://github.com/codenvy/che/issues/262


Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Tue, Feb 2, 2016 at 6:54 PM, Awanthika Senarath 
wrote:

> Still when I try to create a project it fails with the following exception,
>
>  Creating machine [ws = workspacec3uqzvrq98trmwr5: env = wksp-vo1e:
> machine = ws-machine]
> Exception in thread "WorkspaceManager-0" java.lang.RuntimeException:
> java.lang.IllegalArgumentException: protocol = http host = null
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1455)
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
> at
> sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2979)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:489)
> at
> org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.doRequest(DefaultHttpJsonRequest.java:225)
> at
> org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.request(DefaultHttpJsonRequest.java:136)
> at
> org.eclipse.che.api.machine.server.WsAgentLauncherImpl.pingWsAgent(WsAgentLauncherImpl.java:122)
> at
> org.eclipse.che.api.machine.server.WsAgentLauncherImpl.startWsAgent(WsAgentLauncherImpl.java:95)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
> at com.sun.proxy.$Proxy52.startWsAgent(Unknown Source)
> at
> org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:370)
> at
> org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:337)
> at
> org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:168)
> at
> org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.createMachine(RuntimeWorkspaceRegistry.java:451)
> at
> org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.startEnvironment(RuntimeWorkspaceRegistry.java:319)
> at
> org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.start(RuntimeWorkspaceRegistry.java:145)
> at
> org.eclipse.che.api.workspace.server.WorkspaceManager.performSyncStart(WorkspaceManager.java:642)
> at
> org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$9(WorkspaceManager.java:613)
> at
> org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: protocol = http host = null
> at sun.net.spi.DefaultProxySelector.select(DefaultProxySelector.java:176)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1099)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
> at
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1513)
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
> ... 22 more
>
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Tue, Feb 2, 2016 at 6:52 PM, Awanthika Senarath 
> wrote:
>
>> thanks for the explanation Alexander,
>>
>> It worked after I exported the JAVA_HOME. JAVA_HOME was declared but not
>> exported in the bashrc file.
>>
>> I will create the issues.
>>
>> Regards
>> Awanthika
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> On Tue, Feb 2, 2016 at 6:24 PM, Alexander Garagatyi <
>> agaraga...@codenvy.com> wrote:
>>
>>> Would appreciate a clarification on this as your docs are a bit
 confusing :)
>>>
>>> Please create an issue on github.
>>>
>>> Is this correct? Do I need to create a docker image for Che to create
 the workspace in?

>>> It is correct. You don't have to do anything else with docker.
>>>
>>> when we have the USE_DOCKER parameter false Che is not starting with
 docker? In that case is Che using the local file system of the machine?

 if not What is that parameter being used for?

>>> when USE_DOCKER is false Che runs on localhost, but workspaces are
>>> still in docker containe

Re: [Dev] [DEV][JAGGERY] Getting Empty JSON when logging(log.info)

[Rajeenthini Satkunam]

HI All,

Thank you chamara and sajith for your valuable suggestions.I have done the
improvement in Jaggery to log the java Object.

improvement
-
1)
https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/src/main/java/org/jaggeryjs/scriptengine/util/HostObjectUtil.java#L78

Added new code segment as per sajith's suggestion

try{
return (new ObjectMapper().writeValueAsString(obj));
}catch (Exception e){
log.debug("Object " + obj.toString() + " of class " +
obj.getClass() + " cannot be converted to JSON");
}

return "{}";


2) https://github.com/wso2/jaggery/blob/master/pom.xml

Added maven dependencies for Jackson data-bind and annotations


com.fasterxml.jackson.core
jackson-annotations
${jackson.version}


com.fasterxml.jackson.core
jackson-databind
${jackson.version}


3) 
https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/pom.xml

Added maven dependencies for Jackson data-bind and annotations


I have tried to build(mvn clean install) Jaggery and product-Jaggery
respectively.I can build Jaggery successfully But It has failed when
building product Jaggery at Jaggery - Profile Generation.

As per offline discussion with Niranjan I have added  and <
*dependency*> for Jackson data-bind and annotation in POM.xml[
https://github.com/wso2/jaggery/blob/master/features/org.jaggeryjs.server.feature/pom.xml]
file as below.

com.fasterxml.jackson.core:jackson-databind
com.fasterxml.jackson.core:jackson-annotations



com.fasterxml.jackson.core
jackson-databind


com.fasterxml.jackson.core
jackson-annotations



But Still I am getting product Jaggery build fail at the point Jaggery
- Profile Generation,following error can be observe in the command
line.


Installation failed.Cannot complete the install because one or more
required items could not be found.

 Software being installed: uuid Module - Feature 1.4.3
(org.jaggeryjs.modules.uuid.feature.group 1.4.3)
 Missing requirement: jackson-databind 2.0.0 (jackson-databind 2.0.0)
requires 'package com.fasterxml.jackson.core [2.0.0,3.0.0)' but it
could not be found
 Cannot satisfy dependency:
  From: org.jaggeryjs.modules.uuid 1.4.3 (org.jaggeryjs.modules.uuid 1.4.3)
  To: package org.jaggeryjs.scriptengine.exceptions [0.11.0,1.0.0)
 Cannot satisfy dependency:

  From: uuid Module - Feature 1.4.3
(org.jaggeryjs.modules.uuid.feature.group 1.4.3)
  To: org.jaggeryjs.modules.uuid [1.4.3]
 Cannot satisfy dependency:
  From: org.jaggeryjs.scriptengine 0.12.1.SNAPSHOT
(org.jaggeryjs.scriptengine 0.12.1.SNAPSHOT)
  To: package com.fasterxml.jackson.databind [2.0.0,3.0.0)
Application failed, log file location:
/home/rajee/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1454469448601.log


Can anyone help me to figure out the cause of build fail.Hope I have
included all the steps I have followed.Your help would be appreciated.




On Tue, Feb 2, 2016 at 10:23 AM, Rajeenthini Satkunam 
wrote:

> Hi sajith,
>
> Noted and thank you for the suggestions.
>
> On Mon, Feb 1, 2016 at 11:53 PM, Sajith Ariyarathna 
> wrote:
>
>> Hi Rajeenthini,
>>
>> You are hoping to add the following code snippet to the serializeJSON
>> method [1] of the org.jaggeryjs.scriptengine.util.HostObjectUtil class.
>>
>>> String JsonString = null;
>>> try{
>>> ObjectMapper mapper = new ObjectMapper();
>>> JsonString = mapper.writeValueAsString(obj);
>>> }catch (Exception e){
>>> System.out.println(e.getMessage());
>>> }
>>>
>>> return "{\"javaObject\":\"true\",\"object\":\"" + JsonString + "\"}";
>>>
>>> There are few issue in this code snippet.
>>
>>- Don't catch generic Exception, always catch a specific exception.
>>In here you should catch JsonProcessingException [2].
>>- Don't use System.out.println to log exceptions. Instead use a
>>proper logger. HostObjectUtil class has a log object defined in line
>>30 [3], you can use that.
>>- Returning '{"javaObject": "true", "object": "{ ... }"}' string
>>gives a wrong impression that there are two attributes called 'javaObject'
>>& 'object' in the logged object. I think just returning the JSON string
>>will be enough.
>>
>> After corrections (I also took the liberty to reduce no of lines):
>>
>> try {
>>
>> return (new ObjectMapper()).writeValueAsString(obj);
>>
>> } catch (JsonProcessingException e) {
>>
>> log.debug("Object " + obj.toString() + " of class " + obj.getClassName()
>> + " cannot be converted to JSON");
>>
>> }
>>
>> return "{}";
>>
>>
>> [1]
>> https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/src/main/java/org/jaggeryjs/scriptengine/util/HostObjectUtil.java#L78
>> [2]
>> https://static.javadoc.io/com.fasterxml.jackson.core/jackson-databind/2.6.3/com/fasterxml/jackson/databind/ObjectMapper.html#writeValueAsString(java.lang.Object)
>> [3]
>> https:

Re: [Dev] [DEV][JAGGERY] Getting Empty JSON when logging(log.info)

[Niranjan Karunanandham]

Hi Rajeenthini,


On Wed, Feb 3, 2016 at 9:19 AM, Rajeenthini Satkunam 
wrote:

> HI All,
>
> Thank you chamara and sajith for your valuable suggestions.I have done the
> improvement in Jaggery to log the java Object.
>
> improvement
> -
> 1)
> https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/src/main/java/org/jaggeryjs/scriptengine/util/HostObjectUtil.java#L78
>
> Added new code segment as per sajith's suggestion
>
> try{
> return (new ObjectMapper().writeValueAsString(obj));
> }catch (Exception e){
> log.debug("Object " + obj.toString() + " of class " + obj.getClass() + " 
> cannot be converted to JSON");
> }
>
> return "{}";
>
>
> 2) https://github.com/wso2/jaggery/blob/master/pom.xml
>
> Added maven dependencies for Jackson data-bind and annotations
>
> 
> com.fasterxml.jackson.core
> jackson-annotations
> ${jackson.version}
> 
> 
> com.fasterxml.jackson.core
> jackson-databind
> ${jackson.version}
> 
>
> 3) 
> https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/pom.xml
>
> Added maven dependencies for Jackson data-bind and annotations
>
>
> I have tried to build(mvn clean install) Jaggery and product-Jaggery
> respectively.I can build Jaggery successfully But It has failed when
> building product Jaggery at Jaggery - Profile Generation.
>
> As per offline discussion with Niranjan I have added 
> and <*dependency*> for Jackson data-bind and annotation in POM.xml[
> https://github.com/wso2/jaggery/blob/master/features/org.jaggeryjs.server.feature/pom.xml]
> file as below.
>
> com.fasterxml.jackson.core:jackson-databind
> com.fasterxml.jackson.core:jackson-annotations
>
>
> 
> com.fasterxml.jackson.core
> jackson-databind
> 
> 
> com.fasterxml.jackson.core
> jackson-annotations
> 
>
>
> But Still I am getting product Jaggery build fail at the point Jaggery - 
> Profile Generation,following error can be observe in the command line.
>
>
> Installation failed.Cannot complete the install because one or more required 
> items could not be found.
>
>  Software being installed: uuid Module - Feature 1.4.3 
> (org.jaggeryjs.modules.uuid.feature.group 1.4.3)
>  Missing requirement: jackson-databind 2.0.0 (jackson-databind 2.0.0) 
> requires 'package com.fasterxml.jackson.core [2.0.0,3.0.0)' but it could not 
> be found
>  Cannot satisfy dependency:
>   From: org.jaggeryjs.modules.uuid 1.4.3 (org.jaggeryjs.modules.uuid 1.4.3)
>   To: package org.jaggeryjs.scriptengine.exceptions [0.11.0,1.0.0)
>  Cannot satisfy dependency:
>
>   From: uuid Module - Feature 1.4.3 (org.jaggeryjs.modules.uuid.feature.group 
> 1.4.3)
>   To: org.jaggeryjs.modules.uuid [1.4.3]
>  Cannot satisfy dependency:
>   From: org.jaggeryjs.scriptengine 0.12.1.SNAPSHOT 
> (org.jaggeryjs.scriptengine 0.12.1.SNAPSHOT)
>   To: package com.fasterxml.jackson.databind [2.0.0,3.0.0)
> Application failed, log file location: 
> /home/rajee/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1454469448601.log
>
>
> Can anyone help me to figure out the cause of build fail.Hope I have included 
> all the steps I have followed.Your help would be appreciated.
>
> As per the error, the build is failing because jackson-databind requires
com.fasterxml.jackson.core within the range 2.0.0 and 3.0.0. If this is
required by the feature then you need to bundle it in the feature. Shall we
have a look at this today?

>
>
>
> On Tue, Feb 2, 2016 at 10:23 AM, Rajeenthini Satkunam <
> rajeenth...@wso2.com> wrote:
>
>> Hi sajith,
>>
>> Noted and thank you for the suggestions.
>>
>> On Mon, Feb 1, 2016 at 11:53 PM, Sajith Ariyarathna 
>> wrote:
>>
>>> Hi Rajeenthini,
>>>
>>> You are hoping to add the following code snippet to the serializeJSON
>>> method [1] of the org.jaggeryjs.scriptengine.util.HostObjectUtil class.
>>>
 String JsonString = null;
 try{
 ObjectMapper mapper = new ObjectMapper();
 JsonString = mapper.writeValueAsString(obj);
 }catch (Exception e){
 System.out.println(e.getMessage());
 }

 return "{\"javaObject\":\"true\",\"object\":\"" + JsonString + "\"}";

 There are few issue in this code snippet.
>>>
>>>- Don't catch generic Exception, always catch a specific exception.
>>>In here you should catch JsonProcessingException [2].
>>>- Don't use System.out.println to log exceptions. Instead use a
>>>proper logger. HostObjectUtil class has a log object defined in line
>>>30 [3], you can use that.
>>>- Returning '{"javaObject": "true", "object": "{ ... }"}' string
>>>gives a wrong impression that there are two attributes called 
>>> 'javaObject'
>>>& 'object' in the logged object. I think just returning the JSON string
>>>will be enough.
>>>
>>> After corrections (I also took the liberty to reduce no of lines):
>>>
>>> try {
>>>
>>> return (new ObjectMapper()).

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2

[Chamila De Alwis]

+1 release

Verified the Puppet manifests for BRS, MB, and GREG (default profile)

Additional changes to templates and hieradata have to be added to cater for
the majority of the possible use cases, however this release can be done
without those changes. More sophisticated and configurable templates can be
added later to each product.


Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com



On Mon, Feb 1, 2016 at 12:47 PM, Isuru Haththotuwa  wrote:

> Hi,
>
> AFAIU we can't just use this templates anyway as they are, but might need
> to modify to fit to the usecase. These modules do not cover all the
> parameters that each of the products have, just have the most basic set.
> More importantly this set of puppet modules have standardized the
> separation of data from puppet code by using hiera to use as a common set
> of puppet modules for all WSO2 use cases. We can improve them as we move
> along.
>
> On Mon, Feb 1, 2016 at 11:46 AM, Ramith Jayasinghe 
> wrote:
>
>> had a chat with IsuruH and agreed to add the ability to configure this
>> on next release.
>>
>> On Mon, Feb 1, 2016 at 11:25 AM, Ramith Jayasinghe 
>> wrote:
>> > HI,
>> >  in :
>> https://github.com/wso2/puppet-modules/blob/v1.0.0-rc2/modules/wso2mb/templates/3.0.0/repository/conf/datasources/master-datasources.xml.erb
>> >  I see that,
>> >  false is not added to MB
>> > data-source (only MB data-source requires that). that would lead to
>> > problems. shall we fix that.
>> >  regards
>> > Ramith
>> >
>> > On Mon, Feb 1, 2016 at 11:14 AM, Isuru Haththotuwa 
>> wrote:
>> >> Hi devs,
>> >>
>> >> This is the second release candidate of WSO2 Puppet Modules 1.0.0.
>> Please
>> >> download, test and vote.
>> >>
>> >> [ ] Broken - do not release (explain why)
>> >> [ ] Stable - go ahead and release
>> >>
>> >> The tag to be voted upon:
>> >> https://github.com/wso2/puppet-modules/tree/v1.0.0-rc2
>> >>
>> >> Source and binary distribution files:
>> >> https://github.com/wso2/puppet-modules/releases/tag/v1.0.0-rc2
>> >>
>> >> The vote will be open for 72 hours or as needed.
>> >>
>> >> --
>> >> Thanks,
>> >> The WSO2 Private PaaS Team
>> >>
>> >>
>> >>
>> >> ___
>> >> Dev mailing list
>> >> Dev@wso2.org
>> >> http://wso2.org/cgi-bin/mailman/listinfo/dev
>> >>
>> >
>> >
>> >
>> > --
>> > Ramith Jayasinghe
>> > Technical Lead
>> > WSO2 Inc., http://wso2.com
>> > lean.enterprise.middleware
>> >
>> > E: ram...@wso2.com
>> > P: +94 777542851
>>
>>
>>
>> --
>> Ramith Jayasinghe
>> Technical Lead
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> E: ram...@wso2.com
>> P: +94 777542851
>>
>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>
> ___
> 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] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2

[Thanuja Uruththirakodeeswaran]

+1 for the release

Verified following products with clustering:

1. DSS 3.5.0
2. ESB 4.9.0
3. AS 5.3.0

Also tested DAS 3.0.0 default profile.

Thanks.

On Wed, Feb 3, 2016 at 9:32 AM, Chamila De Alwis  wrote:

> +1 release
>
> Verified the Puppet manifests for BRS, MB, and GREG (default profile)
>
> Additional changes to templates and hieradata have to be added to cater
> for the majority of the possible use cases, however this release can be
> done without those changes. More sophisticated and configurable templates
> can be added later to each product.
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Mon, Feb 1, 2016 at 12:47 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi,
>>
>> AFAIU we can't just use this templates anyway as they are, but might need
>> to modify to fit to the usecase. These modules do not cover all the
>> parameters that each of the products have, just have the most basic set.
>> More importantly this set of puppet modules have standardized the
>> separation of data from puppet code by using hiera to use as a common set
>> of puppet modules for all WSO2 use cases. We can improve them as we move
>> along.
>>
>> On Mon, Feb 1, 2016 at 11:46 AM, Ramith Jayasinghe 
>> wrote:
>>
>>> had a chat with IsuruH and agreed to add the ability to configure this
>>> on next release.
>>>
>>> On Mon, Feb 1, 2016 at 11:25 AM, Ramith Jayasinghe 
>>> wrote:
>>> > HI,
>>> >  in :
>>> https://github.com/wso2/puppet-modules/blob/v1.0.0-rc2/modules/wso2mb/templates/3.0.0/repository/conf/datasources/master-datasources.xml.erb
>>> >  I see that,
>>> >  false is not added to MB
>>> > data-source (only MB data-source requires that). that would lead to
>>> > problems. shall we fix that.
>>> >  regards
>>> > Ramith
>>> >
>>> > On Mon, Feb 1, 2016 at 11:14 AM, Isuru Haththotuwa 
>>> wrote:
>>> >> Hi devs,
>>> >>
>>> >> This is the second release candidate of WSO2 Puppet Modules 1.0.0.
>>> Please
>>> >> download, test and vote.
>>> >>
>>> >> [ ] Broken - do not release (explain why)
>>> >> [ ] Stable - go ahead and release
>>> >>
>>> >> The tag to be voted upon:
>>> >> https://github.com/wso2/puppet-modules/tree/v1.0.0-rc2
>>> >>
>>> >> Source and binary distribution files:
>>> >> https://github.com/wso2/puppet-modules/releases/tag/v1.0.0-rc2
>>> >>
>>> >> The vote will be open for 72 hours or as needed.
>>> >>
>>> >> --
>>> >> Thanks,
>>> >> The WSO2 Private PaaS Team
>>> >>
>>> >>
>>> >>
>>> >> ___
>>> >> Dev mailing list
>>> >> Dev@wso2.org
>>> >> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Ramith Jayasinghe
>>> > Technical Lead
>>> > WSO2 Inc., http://wso2.com
>>> > lean.enterprise.middleware
>>> >
>>> > E: ram...@wso2.com
>>> > P: +94 777542851
>>>
>>>
>>>
>>> --
>>> Ramith Jayasinghe
>>> Technical Lead
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> E: ram...@wso2.com
>>> P: +94 777542851
>>>
>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>> ___
>> 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
>
>


-- 
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] Issue when starting the server - SSLException: Connection has been shutdown

[Dilini Gunatilake]

Hi All,

Thanks for the suggestions. I didn't observe the exception after commenting
out the other properties. It is thrown only when starting the H2 PG server.
Also, a 500 error page is displayed when login to the Portal of the
Dashboard Server 2.0.0 when H2 TCP server is also started. Raised a JIRA
[1] to address these issues.

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

Thank you.

Regards,
Dilini

On Wed, Feb 3, 2016 at 1:46 AM, Vishanth Balasubramaniam  wrote:

> Hi Dilini,
>
> Try commenting out the rest of the properties in H2DatabaseConfiguration
> in carbon.xml.
>
> 
>> 
>> 8082
>> 
>>
>> **
>> 
>
>
> Regards,
> Vishanth
>
> On Tue, Feb 2, 2016 at 5:37 PM, Dilini Gunatilake 
> wrote:
>
>> Hi Carbon Team,
>>
>> I wanted to browse the H2 repository and followed the blog in [1] and
>> configured the carbon.xml file accordingly. But, when I started the pack, I
>> observed the following error. What could be the reason for this?
>>
>> This issue was observed in WSO2 ESB 4.10.0-Milestone 2 and DS 2.0.0 Beta
>> 2 packs. (carbon 4.4.3)
>>
>> ubuntu@ds-long-n1:~/releases/wso2ds-2.0.0-SNAPSHOT/bin$ sh wso2server.sh
>> JAVA_HOME environment variable is set to /home/ubuntu/software/jdk1.8.0_51
>> CARBON_HOME environment variable is set to
>> /home/ubuntu/releases/wso2ds-2.0.0-SNAPSHOT
>> Using Java memory options: -Xms256m -Xmx1024m
>>
>> [2016-02-02 11:26:27,394]  INFO
>> {org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 Web
>> server...
>> [2016-02-02 11:26:28,006]  INFO
>> {org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 TCP
>> server...
>> [2016-02-02 11:26:28,030]  INFO
>> {org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 PG server...
>> org.h2.server.TcpServerThread@273ec7dc Connect
>> Connect
>> Disconnect
>> Close
>> javax.net.ssl.SSLException: Connection has been shutdown:
>> javax.net.ssl.SSLHandshakeException: Remote host closed connection during
>> handshake
>> at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1541)
>> at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1553)
>> at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:71)
>> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
>> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
>> at java.io.DataOutputStream.flush(DataOutputStream.java:123)
>> at org.h2.value.Transfer.flush(Transfer.java:85)
>> at org.h2.server.TcpServerThread.sendError(TcpServerThread.java:197)
>> at org.h2.server.TcpServerThread.run(TcpServerThread.java:129)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed
>> connection during handshake
>> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
>> at
>> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
>> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:928)
>> at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
>> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
>> at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
>> at java.io.DataInputStream.readInt(DataInputStream.java:387)
>> at org.h2.value.Transfer.readInt(Transfer.java:145)
>> at org.h2.server.TcpServerThread.run(TcpServerThread.java:71)
>> ... 1 more
>> Caused by: java.io.EOFException: SSL peer shut down incorrectly
>> at sun.security.ssl.InputRecord.read(InputRecord.java:505)
>> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
>> ... 9 more
>> org.h2.server.TcpServerThread@273ec7dc Disconnect
>> org.h2.server.TcpServerThread@273ec7dc Close
>> [2016-02-02 11:26:29,170]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
>> Carbon...
>> [2016-02-02 11:26:29,177]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
>> Linux 3.13.0-36-generic, amd64
>> [2016-02-02 11:26:29,177]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
>> /home/ubuntu/software/jdk1.8.0_51/jre
>> [2016-02-02 11:26:29,178]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
>> 1.8.0_51
>> [2016-02-02 11:26:29,181]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
>> Java HotSpot(TM) 64-Bit Server VM 25.51-b03,Oracle Corporation
>>
>>
>> [1]
>> http://www.vitharana.org/2012/04/how-to-browse-h2-database-of-wso2.html
>>
>>
>> Thank you.
>>
>> Regards,
>>
>> --
>>
>> *Dilini GunatilakeSoftware Engineer - QA Team*
>> Mobile : +94 (0) 771 162518
>> dili...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94 77 17 377 18*
> about me: *http://about.me/vishanth 

Re: [Dev] [DEV][JAGGERY] Getting Empty JSON when logging(log.info)

[Rajeenthini Satkunam]

HI Niranjan,

Ya sure.I will meet you today.

On Wed, Feb 3, 2016 at 9:25 AM, Niranjan Karunanandham 
wrote:

> Hi Rajeenthini,
>
>
> On Wed, Feb 3, 2016 at 9:19 AM, Rajeenthini Satkunam  > wrote:
>
>> HI All,
>>
>> Thank you chamara and sajith for your valuable suggestions.I have done
>> the improvement in Jaggery to log the java Object.
>>
>> improvement
>> -
>> 1)
>> https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/src/main/java/org/jaggeryjs/scriptengine/util/HostObjectUtil.java#L78
>>
>> Added new code segment as per sajith's suggestion
>>
>> try{
>> return (new ObjectMapper().writeValueAsString(obj));
>> }catch (Exception e){
>> log.debug("Object " + obj.toString() + " of class " + obj.getClass() + " 
>> cannot be converted to JSON");
>> }
>>
>> return "{}";
>>
>>
>> 2) https://github.com/wso2/jaggery/blob/master/pom.xml
>>
>> Added maven dependencies for Jackson data-bind and annotations
>>
>> 
>> com.fasterxml.jackson.core
>> jackson-annotations
>> ${jackson.version}
>> 
>> 
>> com.fasterxml.jackson.core
>> jackson-databind
>> ${jackson.version}
>> 
>>
>> 3) 
>> https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/pom.xml
>>
>> Added maven dependencies for Jackson data-bind and annotations
>>
>>
>> I have tried to build(mvn clean install) Jaggery and product-Jaggery
>> respectively.I can build Jaggery successfully But It has failed when
>> building product Jaggery at Jaggery - Profile Generation.
>>
>> As per offline discussion with Niranjan I have added 
>> and <*dependency*> for Jackson data-bind and annotation in POM.xml[
>> https://github.com/wso2/jaggery/blob/master/features/org.jaggeryjs.server.feature/pom.xml]
>> file as below.
>>
>> com.fasterxml.jackson.core:jackson-databind
>> com.fasterxml.jackson.core:jackson-annotations
>>
>>
>> 
>> com.fasterxml.jackson.core
>> jackson-databind
>> 
>> 
>> com.fasterxml.jackson.core
>> jackson-annotations
>> 
>>
>>
>> But Still I am getting product Jaggery build fail at the point Jaggery - 
>> Profile Generation,following error can be observe in the command line.
>>
>>
>> Installation failed.Cannot complete the install because one or more required 
>> items could not be found.
>>
>>  Software being installed: uuid Module - Feature 1.4.3 
>> (org.jaggeryjs.modules.uuid.feature.group 1.4.3)
>>  Missing requirement: jackson-databind 2.0.0 (jackson-databind 2.0.0) 
>> requires 'package com.fasterxml.jackson.core [2.0.0,3.0.0)' but it could not 
>> be found
>>  Cannot satisfy dependency:
>>   From: org.jaggeryjs.modules.uuid 1.4.3 (org.jaggeryjs.modules.uuid 1.4.3)
>>   To: package org.jaggeryjs.scriptengine.exceptions [0.11.0,1.0.0)
>>  Cannot satisfy dependency:
>>
>>   From: uuid Module - Feature 1.4.3 
>> (org.jaggeryjs.modules.uuid.feature.group 1.4.3)
>>   To: org.jaggeryjs.modules.uuid [1.4.3]
>>  Cannot satisfy dependency:
>>   From: org.jaggeryjs.scriptengine 0.12.1.SNAPSHOT 
>> (org.jaggeryjs.scriptengine 0.12.1.SNAPSHOT)
>>   To: package com.fasterxml.jackson.databind [2.0.0,3.0.0)
>> Application failed, log file location: 
>> /home/rajee/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1454469448601.log
>>
>>
>> Can anyone help me to figure out the cause of build fail.Hope I have 
>> included all the steps I have followed.Your help would be appreciated.
>>
>> As per the error, the build is failing because jackson-databind requires
> com.fasterxml.jackson.core within the range 2.0.0 and 3.0.0. If this is
> required by the feature then you need to bundle it in the feature. Shall we
> have a look at this today?
>
>>
>>
>>
>> On Tue, Feb 2, 2016 at 10:23 AM, Rajeenthini Satkunam <
>> rajeenth...@wso2.com> wrote:
>>
>>> Hi sajith,
>>>
>>> Noted and thank you for the suggestions.
>>>
>>> On Mon, Feb 1, 2016 at 11:53 PM, Sajith Ariyarathna 
>>> wrote:
>>>
 Hi Rajeenthini,

 You are hoping to add the following code snippet to the serializeJSON
 method [1] of the org.jaggeryjs.scriptengine.util.HostObjectUtil class.

> String JsonString = null;
> try{
> ObjectMapper mapper = new ObjectMapper();
> JsonString = mapper.writeValueAsString(obj);
> }catch (Exception e){
> System.out.println(e.getMessage());
> }
>
> return "{\"javaObject\":\"true\",\"object\":\"" + JsonString + "\"}";
>
> There are few issue in this code snippet.

- Don't catch generic Exception, always catch a specific exception.
In here you should catch JsonProcessingException [2].
- Don't use System.out.println to log exceptions. Instead use a
proper logger. HostObjectUtil class has a log object defined in
line 30 [3], you can use that.
- Returning '{"javaObject": "true", "object": "{ ... }"}' string
gives a wrong impression that there are two at

[Dev] Issue with multiple dependencies in IS

[Keerthika Mahendralingam]

Hi All,

I am implementing totp authenticator. For that I need to encode the secret
key in Base32 encoding. Since Base32 class is not available in the
commons-codec 1.4.0.wso2v1 version which WSO2 IS using, I need to use the
latest version. If I use commons-codec 1.10, other modules in IS not get
deployed. How to resolve this multiple dependency issue?


Thanks,

-- 

Keerthika Mahendralingam
Associate Software Engineer
Mobile :+94 (0) 776 121144
keerth...@wso2.com
WSO2, Inc.
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Malith Munasinghe

[Erandi Ganepola]

Congrats :-)

Erandi Ganepola
Software Engineering Intern
+94710695692
+94754191524


On Tue, Feb 2, 2016 at 5:11 PM, Menaka Jayawardena  wrote:

> Congratulations Malith
>
> On Tue, Feb 2, 2016 at 4:52 PM, Shabir Mohamed  wrote:
>
>> Congrats Bro :D
>>
>> -
>> *Shabir Mohamed*
>> *Software Engineer*
>> WSO2 Inc.; http://wso2.com
>> Email: sha...@wso2.com 
>> Mobile: +94 77 3516019 | +94 71 6583393
>>
>> On Tue, Feb 2, 2016 at 4:48 PM, Jithendra Sirimanne 
>> wrote:
>>
>>> Congrats :)
>>>
>>> Best Regards
>>> Jithendra
>>>
>>> --
>>> Jithendra Sirimanne
>>> *Systems Engineer*
>>> Mobile: +94 (0) 716 374696 <+94+(0)+716+374696>
>>> Tel  : +94 112 145 345
>>> Email  : jithen...@wso2.com
>>>
>>> On Tue, Feb 2, 2016 at 4:38 PM, Amila Maha Arachchi 
>>> wrote:
>>>
 Hi all,

 Its my pleasure to welcome Malith Munasinghe as a WSO2 Committer.
 Malith is a member of WSO2 Cloud Dev team and has been contributing to the
 team in development, integration, deployment and alerting work. In
 recognition of his contribution, he has been voted as a WSO2 Committer.

 Malith, welcome aboard and keep up the good work..

 Regards,
 Amila.

 --
 *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
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Menaka Madushanka Jayawardena
> Software Engineering Intern
> men...@wso2.com
> Mobile:- +94 71 8851183/ +94 71 3505470
> LinkedIn - Menaka Jayawardena
> 
>
> ___
> 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] WSO2 Committers += Malith Munasinghe

[Nipuna Prashan]

Congratulations!!!


On Tue, Feb 2, 2016 at 4:38 PM, Amila Maha Arachchi  wrote:

> Hi all,
>
> Its my pleasure to welcome Malith Munasinghe as a WSO2 Committer. Malith
> is a member of WSO2 Cloud Dev team and has been contributing to the team in
> development, integration, deployment and alerting work. In recognition of
> his contribution, he has been voted as a WSO2 Committer.
>
> Malith, welcome aboard and keep up the good work..
>
> Regards,
> Amila.
>
> --
> *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
>
>


-- 
*Nipuna Prashan*
Software Engineering Intern
+94711852792
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Malith Munasinghe

[Yasassri Ratnayake]

Congrats Malith :)

On Wed, Feb 3, 2016 at 11:08 AM, Nipuna Prashan  wrote:

> Congratulations!!!
>
>
> On Tue, Feb 2, 2016 at 4:38 PM, Amila Maha Arachchi 
> wrote:
>
>> Hi all,
>>
>> Its my pleasure to welcome Malith Munasinghe as a WSO2 Committer. Malith
>> is a member of WSO2 Cloud Dev team and has been contributing to the team in
>> development, integration, deployment and alerting work. In recognition of
>> his contribution, he has been voted as a WSO2 Committer.
>>
>> Malith, welcome aboard and keep up the good work..
>>
>> Regards,
>> Amila.
>>
>> --
>> *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
>>
>>
>
>
> --
> *Nipuna Prashan*
> Software Engineering Intern
> +94711852792
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Yasassri Ratnayake
Software Engineer - QA
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
*Mobile : +94715933168*
*Blogs : http://yasassriratnayake.blogspot.com
*
*http://wso2logs.blogspot.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Load balance endpoint: Session Management

[Chathurika De Silva]

Hi

In [1] there are two session management methods as "Transport" and "Soap".
The document does not provide comprehensive details on their usage. Can you
please explain their usage with a user scenario?

Thank You
Erandi

-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Load balance endpoint: Session Management

[Chathurika De Silva]

Adding the doc link [1]

[1] https://docs.wso2.com/display/ESB4100/Load-balance+Group

On Wed, Feb 3, 2016 at 11:13 AM, Chathurika De Silva 
wrote:

> Hi
>
> In [1] there are two session management methods as "Transport" and "Soap".
> The document does not provide comprehensive details on their usage. Can you
> please explain their usage with a user scenario?
>
> Thank You
> Erandi
>
> --
> *Chathurika Erandi*
> Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] API Manager Integration test cases to be run through Heartbeat

[Erandi Ganepola]

Hi All,

I'm going to run Api manager integration test cases through Heartbeat
system in cloud.

So I need to clarify the tests which have been written in "tenant mood"
because only those will be tested in Heartbeat (test cases written in
"super tenant mood" won't be checked).

Please mention the test cases which have been written in "tenant mood".

Thanks and Regards,
Erandi.

Erandi Ganepola
Software Engineering Intern
+94710695692
+94754191524
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] API Manager Integration test cases to be run through Heartbeat

[Malintha Adikari]

Hi Erandi,

We use AutomationContext object to store all test environment related
information. If we want to run a test case using tenant user, we have to
create AutomationContext object providing that tenant user information. So
we are creating AutomationContext object before we start executing test
case (we create this object under @BeforeClass annotation).

When we create AutomationContext object we are getting user related data
through TestUserMode object. Incase, we need to execute same test case for
both super tenant  and tenant user, we create data provider with all those
users and provide that data provider to the test case. Then test case will
be executed sequentially for all users mentioned in the data provider (for
each test run , separate AutomationContext object will be created for the
current user).

Each test case inherits from base test class where we create
AutomationContext object in it's init() method. In APIMIntergrationBaseTest
class there are two overloading methods

1. init() - AutomationContext is created using super tenant
2. init(TestUserMode userMode) - Automation context is created using the
provided TenantUserMode object.

We can use following logic to differentiate test cases which are running in
super tenant + tenant mode or only in super tenant mode.

   - If a test case has a data provider and AutomationContext has been
   created using TestUserMode object provided by that data provider, that test
   case will be executed for all users

ex:
[2]

@Factory(dataProvider = "userModeDataProvider") public ESBJAVA3380TestCase(
TestUserMode userMode) {
this.userMode = userMode;
}
@DataProvider(name = "userModeDataProvider")
public static Object[][] userModeDataProvider() {
return new Object[][]{
new Object[]{TestUserMode.SUPER_TENANT_ADMIN},
new Object[]{TestUserMode.TENANT_ADMIN},
};
}
@BeforeClass(alwaysRun = true)
public void setEnvironment() throws Exception {
.
super.init(userMode);
Here we run test case using both super tenant and tenant


   - If a test case has no data provider and it is using super class inti()
   method, that test case is executed only for super tenant.


[3]

public void initialize() throws APIManagerIntegrationTestException,
XPathExpressionException,
MalformedURLException {
super.init();


[1]
https://github.com/wso2/product-apim/blob/master/modules/integration/tests-common/integration-test-utils/src/main/java/org/wso2/am/integration/test/utils/base/APIMIntegrationBaseTest.java
[2]
https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/json/ESBJAVA3380TestCase.java
[3].
https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/api/lifecycle/APIAccessibilityOfPublishedOldAPIAndPublishedCopyAPITestCase.java

Regards,
Malintha


On Wed, Feb 3, 2016 at 11:28 AM, Erandi Ganepola  wrote:

> Hi All,
>
> I'm going to run Api manager integration test cases through Heartbeat
> system in cloud.
>
> So I need to clarify the tests which have been written in "tenant mood"
> because only those will be tested in Heartbeat (test cases written in
> "super tenant mood" won't be checked).
>
> Please mention the test cases which have been written in "tenant mood".
>
> Thanks and Regards,
> Erandi.
>
> Erandi Ganepola
> Software Engineering Intern
> +94710695692
> +94754191524
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Malintha Adikari*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

Mobile: +94 71 2312958
Blog:http://malinthas.blogspot.com
Page:   http://about.me/malintha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [che-dev] Trying Eclipse Che latest release on ubuntu

[Awanthika Senarath]

Thanks Alexander,

Ill try to debug from my end too.

Regards
Awanthika

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Wed, Feb 3, 2016 at 12:47 PM, Alexander Garagatyi  wrote:

> Thank you.
> About current failure you've got. I don't know where the problem is right
> now. I need some time to investigate.
>
> On Wed, Feb 3, 2016 at 4:56 AM, Awanthika Senarath 
> wrote:
>
>> Hello Alexander,
>>
>> I have created the issues [1]  [2] and [3]
>>
>>
>> Regards
>> Awanthika
>>
>>
>> [1] https://github.com/codenvy/che/issues/260
>>
>> [2] https://github.com/codenvy/che/issues/261
>>
>> [3] https://github.com/codenvy/che/issues/262
>> 
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> On Tue, Feb 2, 2016 at 6:54 PM, Awanthika Senarath 
>> wrote:
>>
>>> Still when I try to create a project it fails with the following
>>> exception,
>>>
>>>  Creating machine [ws = workspacec3uqzvrq98trmwr5: env = wksp-vo1e:
>>> machine = ws-machine]
>>> Exception in thread "WorkspaceManager-0" java.lang.RuntimeException:
>>> java.lang.IllegalArgumentException: protocol = http host = null
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1455)
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2979)
>>> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:489)
>>> at
>>> org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.doRequest(DefaultHttpJsonRequest.java:225)
>>> at
>>> org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.request(DefaultHttpJsonRequest.java:136)
>>> at
>>> org.eclipse.che.api.machine.server.WsAgentLauncherImpl.pingWsAgent(WsAgentLauncherImpl.java:122)
>>> at
>>> org.eclipse.che.api.machine.server.WsAgentLauncherImpl.startWsAgent(WsAgentLauncherImpl.java:95)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>> at
>>> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
>>> at com.sun.proxy.$Proxy52.startWsAgent(Unknown Source)
>>> at
>>> org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:370)
>>> at
>>> org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:337)
>>> at
>>> org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:168)
>>> at
>>> org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.createMachine(RuntimeWorkspaceRegistry.java:451)
>>> at
>>> org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.startEnvironment(RuntimeWorkspaceRegistry.java:319)
>>> at
>>> org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.start(RuntimeWorkspaceRegistry.java:145)
>>> at
>>> org.eclipse.che.api.workspace.server.WorkspaceManager.performSyncStart(WorkspaceManager.java:642)
>>> at
>>> org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$9(WorkspaceManager.java:613)
>>> at
>>> org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>> at java.lang.Thread.run(Thread.java:745)
>>> Caused by: java.lang.IllegalArgumentException: protocol = http host =
>>> null
>>> at sun.net.spi.DefaultProxySelector.select(DefaultProxySelector.java:176)
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1099)
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1513)
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
>>> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
>>> ... 22 more
>>>
>>>
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>> On Tue, Feb 2, 2016 at 6:52 PM, Awanthika Senarath 
>>> wrote:
>>>
 thanks for the explanation Alexander,

 It worked after I exported the JAVA_HOME. JAVA_HOME was declared but
 not exported in the bashrc file.

 I will create the issues.

 Regards
 Awanthika

 Awanthika Senarath
 Software Engineer, WSO2 Inc.
 Mobile: +94717681791



 On Tue, Feb 2, 2016 at 6:24 PM, Alexander 

Re: [Dev] [DEV][JAGGERY] Getting Empty JSON when logging(log.info)

[Rajeenthini Satkunam]

HI all,

The issue was solved by adding  for
jackson-databind,jackson-annotations,jackson-core for POM[1] .

By the Way I would like to discuss more regarding this mail.

*Issue I am trying to solve*

 - I am getting empty JSON string ("{}") when logging Java object.
 - Empty JSON string("{}") will give wrong information to user.

*Proposed solution*

  - give the user proper understandable log message.
  - the logging need to be fast and summarized.

So I am planning to log in-case of Java object as below without logging
whole object.
{ "javaObject" : true, "hashCode" : "39d92a", "class" :
"org.wso2.apim.StoreHostObject"}

You can find these links[2][3] as resources to get an idea.

[1] -
https://github.com/wso2/jaggery/blob/master/features/org.jaggeryjs.server.feature/pom.xml
[2] -
https://github.com/wso2/jaggery/blob/master/components/hostobjects/org.jaggeryjs.hostobjects.log/src/main/java/org/jaggeryjs/hostobjects/log/LogHostObject.java
[3] -
https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/src/main/java/org/jaggeryjs/scriptengine/util/HostObjectUtil.java


On Wed, Feb 3, 2016 at 10:27 AM, Rajeenthini Satkunam 
wrote:

> HI Niranjan,
>
> Ya sure.I will meet you today.
>
> On Wed, Feb 3, 2016 at 9:25 AM, Niranjan Karunanandham 
> wrote:
>
>> Hi Rajeenthini,
>>
>>
>> On Wed, Feb 3, 2016 at 9:19 AM, Rajeenthini Satkunam <
>> rajeenth...@wso2.com> wrote:
>>
>>> HI All,
>>>
>>> Thank you chamara and sajith for your valuable suggestions.I have done
>>> the improvement in Jaggery to log the java Object.
>>>
>>> improvement
>>> -
>>> 1)
>>> https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/src/main/java/org/jaggeryjs/scriptengine/util/HostObjectUtil.java#L78
>>>
>>> Added new code segment as per sajith's suggestion
>>>
>>> try{
>>> return (new ObjectMapper().writeValueAsString(obj));
>>> }catch (Exception e){
>>> log.debug("Object " + obj.toString() + " of class " + obj.getClass() + 
>>> " cannot be converted to JSON");
>>> }
>>>
>>> return "{}";
>>>
>>>
>>> 2) https://github.com/wso2/jaggery/blob/master/pom.xml
>>>
>>> Added maven dependencies for Jackson data-bind and annotations
>>>
>>> 
>>> com.fasterxml.jackson.core
>>> jackson-annotations
>>> ${jackson.version}
>>> 
>>> 
>>> com.fasterxml.jackson.core
>>> jackson-databind
>>> ${jackson.version}
>>> 
>>>
>>> 3) 
>>> https://github.com/wso2/jaggery/blob/master/components/script-engine/org.jaggeryjs.scriptengine/pom.xml
>>>
>>> Added maven dependencies for Jackson data-bind and annotations
>>>
>>>
>>> I have tried to build(mvn clean install) Jaggery and product-Jaggery
>>> respectively.I can build Jaggery successfully But It has failed when
>>> building product Jaggery at Jaggery - Profile Generation.
>>>
>>> As per offline discussion with Niranjan I have added 
>>> and <*dependency*> for Jackson data-bind and annotation in POM.xml[
>>> https://github.com/wso2/jaggery/blob/master/features/org.jaggeryjs.server.feature/pom.xml]
>>> file as below.
>>>
>>> com.fasterxml.jackson.core:jackson-databind
>>> com.fasterxml.jackson.core:jackson-annotations
>>>
>>>
>>> 
>>> com.fasterxml.jackson.core
>>> jackson-databind
>>> 
>>> 
>>> com.fasterxml.jackson.core
>>> jackson-annotations
>>> 
>>>
>>>
>>> But Still I am getting product Jaggery build fail at the point Jaggery - 
>>> Profile Generation,following error can be observe in the command line.
>>>
>>>
>>> Installation failed.Cannot complete the install because one or more 
>>> required items could not be found.
>>>
>>>  Software being installed: uuid Module - Feature 1.4.3 
>>> (org.jaggeryjs.modules.uuid.feature.group 1.4.3)
>>>  Missing requirement: jackson-databind 2.0.0 (jackson-databind 2.0.0) 
>>> requires 'package com.fasterxml.jackson.core [2.0.0,3.0.0)' but it could 
>>> not be found
>>>  Cannot satisfy dependency:
>>>   From: org.jaggeryjs.modules.uuid 1.4.3 (org.jaggeryjs.modules.uuid 1.4.3)
>>>   To: package org.jaggeryjs.scriptengine.exceptions [0.11.0,1.0.0)
>>>  Cannot satisfy dependency:
>>>
>>>   From: uuid Module - Feature 1.4.3 
>>> (org.jaggeryjs.modules.uuid.feature.group 1.4.3)
>>>   To: org.jaggeryjs.modules.uuid [1.4.3]
>>>  Cannot satisfy dependency:
>>>   From: org.jaggeryjs.scriptengine 0.12.1.SNAPSHOT 
>>> (org.jaggeryjs.scriptengine 0.12.1.SNAPSHOT)
>>>   To: package com.fasterxml.jackson.databind [2.0.0,3.0.0)
>>> Application failed, log file location: 
>>> /home/rajee/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1454469448601.log
>>>
>>>
>>> Can anyone help me to figure out the cause of build fail.Hope I have 
>>> included all the steps I have followed.Your help would be appreciated.
>>>
>>> As per the error, the build is failing because jackson-databind requires
>> com.fasterxml.jackson.core within the range 2.0.0 and 3.0.0. If this is
>> required by the feature then you need to bundle it in the