Re: [Dev] Getting error when starting WSO2 IS 5.1.0 Key Manager in Mesos DC/OS

2016-06-28 Thread Thanuja Uruththirakodeeswaran 
Hi Udara,

On Tue, Jun 28, 2016 at 5:11 PM, Udara Liyanage  wrote:

> Hi Thanuja,
>
> Not to deviate the conversation, but to provide some information
>
> We are  running IS as KM pack in Mesos 1.6 environment and we don't get
> this error.
> Our Mesos nodes are Debian 7.
>

I tested this using Mesos DC/OS vagrant setup [1] where the nodes have
CentOS  7.

>
> Do we get this error only when running on DCOS or in all environment?
>

We are getting this only in CentOS 7 environment.  I tested the same pack
in Ubuntu 14.04 and didn't get any issues when starting the server.

[1]. https://github.com/dcos/dcos-vagrant

Thanks.

>
> On Tue, Jun 28, 2016 at 4:50 PM, Nuwan Dias  wrote:
>
>>
>>
>> On Tuesday, 28 June 2016, Akila Ravihansa Perera 
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> I think ideally this should have been automated as a maven task and
>>> added to the product-apim repo as a tool. The distribution that you have
>>> built via UI cannot be replicated. We don't even recommend installing
>>> features via UI for a production deployment then why have we hosted this
>>> publicly?
>>>
>>
>> We don't recommend? I didn't know that. What is the purpose of leaving
>> the feature management UI then? Why doesn't it even have a warning?
>>
>> Anyhow, many people are using this pack without any issues. And we have
>> followed this practise for several releases now. No issues so far. So we
>> can't prioritise your request right now since it involves in a significant
>> testing effort and we have many things to attend to right now. What does
>> it mean to you guys? Are you guys blocked and unable to proceed unless this
>> is rehosted?
>>
>>>
>>> Thanks.
>>>
>>> On Tue, Jun 28, 2016 at 3:47 PM, Imesh Gunaratne  wrote:
>>>
 Hi Nuwan,

 It would be ideal to fix this issue and re-host the distribution or we
 can even fix it in the next release. For the time being will mention this
 in the documentation and provide steps for the user to overcome this
 problem.

 Thanks

 On Tue, Jun 28, 2016 at 2:41 PM, Niranjan Karunanandham <
 niran...@wso2.com> wrote:

> Hi Thanuja / Nuwan,
>
> On Tue, Jun 28, 2016 at 2:08 PM, Nuwan Dias  wrote:
>
>>
>>
>> On Tue, Jun 28, 2016 at 11:27 AM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I'm getting below error when deploying WSO2 IS 5.1.0 Key Manager
>>> application [1] in Mesos DC/OS. I have used the hosted IS-5.1.0 Key 
>>> Manager
>>> pack [2] to build the docker image.
>>>
>>> I0627 02:40:36.478433 27342 exec.cpp:143] Version: 0.28.1
>>> I0627 02:40:36.481850 27369 exec.cpp:217] Executor registered on
>>> slave 877f8cbc-9f5d-4fed-ab3d-82e145e8d33a-S3
>>> rm: cannot remove
>>> '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/axis2-tmp-6697148023468900485.tmp':
>>> Directory not empty
>>> rm: cannot remove
>>> '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/bundles_info_f09679b3-4b3d-4f19-8ddf-139763830045':
>>> Directory not empty
>>> java.lang.reflect.InvocationTargetException
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
>>> at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)
>>> Caused by: java.lang.RuntimeException:
>>> /mnt/wso2is-km-5.1.0/repository/components/default/configuration/org.eclipse.osgi/.manager/.fileTable.9
>>> (No such file or directory)
>>> at
>>> org.wso2.carbon.server.CarbonLauncher.launch(CarbonLauncher.java:115)
>>> at org.wso2.carbon.server.Main.launchCarbon(Main.java:160)
>>> at org.wso2.carbon.server.Main.main(Main.java:94)
>>> ... 6 more
>>>
>>> If I remove the files in
>>> [CARBON_HOME]/repository/components/default/configuration/org.eclipse.osgi/.manager/
>>> directory in the hosted KM pack and use it to build the docker images, 
>>> I am
>>> able to deploy it in successfully and the server starts without any 
>>> issue.
>>>
>>> As per the offline discussion with Niranjan, the above mentioned
>>> files will be created if we install the features via UI. If we can 
>>> install
>>> Key Manager features using pom files, then above issue will be resolved.
>>>
>>
>> What does it mean? Does it mean that installing features via UI has a
>> bug and it should not be used?
>>
> AFAIU in the pack, the features have been installed via the feature
> management UI which requires in starting the server. This create

Re: [Dev] Getting error when starting WSO2 IS 5.1.0 Key Manager in Mesos DC/OS

2016-06-28 Thread Udara Liyanage 
Hi Thanuja,

Not to deviate the conversation, but to provide some information

We are  running IS as KM pack in Mesos 1.6 environment and we don't get
this error.
Our Mesos nodes are Debian 7.

Do we get this error only when running on DCOS or in all environment?

On Tue, Jun 28, 2016 at 4:50 PM, Nuwan Dias  wrote:

>
>
> On Tuesday, 28 June 2016, Akila Ravihansa Perera 
> wrote:
>
>> Hi Nuwan,
>>
>> I think ideally this should have been automated as a maven task and added
>> to the product-apim repo as a tool. The distribution that you have built
>> via UI cannot be replicated. We don't even recommend installing features
>> via UI for a production deployment then why have we hosted this publicly?
>>
>
> We don't recommend? I didn't know that. What is the purpose of leaving the
> feature management UI then? Why doesn't it even have a warning?
>
> Anyhow, many people are using this pack without any issues. And we have
> followed this practise for several releases now. No issues so far. So we
> can't prioritise your request right now since it involves in a significant
> testing effort and we have many things to attend to right now. What does
> it mean to you guys? Are you guys blocked and unable to proceed unless this
> is rehosted?
>
>>
>> Thanks.
>>
>> On Tue, Jun 28, 2016 at 3:47 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Nuwan,
>>>
>>> It would be ideal to fix this issue and re-host the distribution or we
>>> can even fix it in the next release. For the time being will mention this
>>> in the documentation and provide steps for the user to overcome this
>>> problem.
>>>
>>> Thanks
>>>
>>> On Tue, Jun 28, 2016 at 2:41 PM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Thanuja / Nuwan,

 On Tue, Jun 28, 2016 at 2:08 PM, Nuwan Dias  wrote:

>
>
> On Tue, Jun 28, 2016 at 11:27 AM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Hi All,
>>
>> I'm getting below error when deploying WSO2 IS 5.1.0 Key Manager
>> application [1] in Mesos DC/OS. I have used the hosted IS-5.1.0 Key 
>> Manager
>> pack [2] to build the docker image.
>>
>> I0627 02:40:36.478433 27342 exec.cpp:143] Version: 0.28.1
>> I0627 02:40:36.481850 27369 exec.cpp:217] Executor registered on
>> slave 877f8cbc-9f5d-4fed-ab3d-82e145e8d33a-S3
>> rm: cannot remove
>> '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/axis2-tmp-6697148023468900485.tmp':
>> Directory not empty
>> rm: cannot remove
>> '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/bundles_info_f09679b3-4b3d-4f19-8ddf-139763830045':
>> Directory not empty
>> java.lang.reflect.InvocationTargetException
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
>> at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)
>> Caused by: java.lang.RuntimeException:
>> /mnt/wso2is-km-5.1.0/repository/components/default/configuration/org.eclipse.osgi/.manager/.fileTable.9
>> (No such file or directory)
>> at
>> org.wso2.carbon.server.CarbonLauncher.launch(CarbonLauncher.java:115)
>> at org.wso2.carbon.server.Main.launchCarbon(Main.java:160)
>> at org.wso2.carbon.server.Main.main(Main.java:94)
>> ... 6 more
>>
>> If I remove the files in
>> [CARBON_HOME]/repository/components/default/configuration/org.eclipse.osgi/.manager/
>> directory in the hosted KM pack and use it to build the docker images, I 
>> am
>> able to deploy it in successfully and the server starts without any 
>> issue.
>>
>> As per the offline discussion with Niranjan, the above mentioned
>> files will be created if we install the features via UI. If we can 
>> install
>> Key Manager features using pom files, then above issue will be resolved.
>>
>
> What does it mean? Does it mean that installing features via UI has a
> bug and it should not be used?
>
 AFAIU in the pack, the features have been installed via the feature
 management UI which requires in starting the server. This create temporary
 files as mentioned above. In Ubuntu / windows environment, when we start
 the pack, there are no issue. But in Mesos, it refers to the old files. The
 issue was resolved by deleting the temporary file. IMO since we have a
 workaround by deleting these temporary files and upload it to docker
 registry. In which case we do not have to recreate IS 5.1.0 Key Manager
 again.


>
>> @APIM_team: Shall we fix this and host the new IS 5.1.0 Key

Re: [Dev] Getting error when starting WSO2 IS 5.1.0 Key Manager in Mesos DC/OS

2016-06-28 Thread Nuwan Dias 
On Tuesday, 28 June 2016, Akila Ravihansa Perera  wrote:

> Hi Nuwan,
>
> I think ideally this should have been automated as a maven task and added
> to the product-apim repo as a tool. The distribution that you have built
> via UI cannot be replicated. We don't even recommend installing features
> via UI for a production deployment then why have we hosted this publicly?
>

We don't recommend? I didn't know that. What is the purpose of leaving the
feature management UI then? Why doesn't it even have a warning?

Anyhow, many people are using this pack without any issues. And we have
followed this practise for several releases now. No issues so far. So we
can't prioritise your request right now since it involves in a significant
testing effort and we have many things to attend to right now. What does it
mean to you guys? Are you guys blocked and unable to proceed unless this is
rehosted?

>
> Thanks.
>
> On Tue, Jun 28, 2016 at 3:47 PM, Imesh Gunaratne  > wrote:
>
>> Hi Nuwan,
>>
>> It would be ideal to fix this issue and re-host the distribution or we
>> can even fix it in the next release. For the time being will mention this
>> in the documentation and provide steps for the user to overcome this
>> problem.
>>
>> Thanks
>>
>> On Tue, Jun 28, 2016 at 2:41 PM, Niranjan Karunanandham <
>> niran...@wso2.com >
>> wrote:
>>
>>> Hi Thanuja / Nuwan,
>>>
>>> On Tue, Jun 28, 2016 at 2:08 PM, Nuwan Dias >> > wrote:
>>>


 On Tue, Jun 28, 2016 at 11:27 AM, Thanuja Uruththirakodeeswaran <
 thanu...@wso2.com >
 wrote:

> Hi All,
>
> I'm getting below error when deploying WSO2 IS 5.1.0 Key Manager
> application [1] in Mesos DC/OS. I have used the hosted IS-5.1.0 Key 
> Manager
> pack [2] to build the docker image.
>
> I0627 02:40:36.478433 27342 exec.cpp:143] Version: 0.28.1
> I0627 02:40:36.481850 27369 exec.cpp:217] Executor registered on slave
> 877f8cbc-9f5d-4fed-ab3d-82e145e8d33a-S3
> rm: cannot remove
> '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/axis2-tmp-6697148023468900485.tmp':
> Directory not empty
> rm: cannot remove
> '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/bundles_info_f09679b3-4b3d-4f19-8ddf-139763830045':
> Directory not empty
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
> at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)
> Caused by: java.lang.RuntimeException:
> /mnt/wso2is-km-5.1.0/repository/components/default/configuration/org.eclipse.osgi/.manager/.fileTable.9
> (No such file or directory)
> at
> org.wso2.carbon.server.CarbonLauncher.launch(CarbonLauncher.java:115)
> at org.wso2.carbon.server.Main.launchCarbon(Main.java:160)
> at org.wso2.carbon.server.Main.main(Main.java:94)
> ... 6 more
>
> If I remove the files in
> [CARBON_HOME]/repository/components/default/configuration/org.eclipse.osgi/.manager/
> directory in the hosted KM pack and use it to build the docker images, I 
> am
> able to deploy it in successfully and the server starts without any issue.
>
> As per the offline discussion with Niranjan, the above mentioned files
> will be created if we install the features via UI. If we can install Key
> Manager features using pom files, then above issue will be resolved.
>

 What does it mean? Does it mean that installing features via UI has a
 bug and it should not be used?

>>> AFAIU in the pack, the features have been installed via the feature
>>> management UI which requires in starting the server. This create temporary
>>> files as mentioned above. In Ubuntu / windows environment, when we start
>>> the pack, there are no issue. But in Mesos, it refers to the old files. The
>>> issue was resolved by deleting the temporary file. IMO since we have a
>>> workaround by deleting these temporary files and upload it to docker
>>> registry. In which case we do not have to recreate IS 5.1.0 Key Manager
>>> again.
>>>
>>>

> @APIM_team: Shall we fix this and host the new IS 5.1.0 Key Manager
> pack?
>

 You have now successfully created the docker image right? Why do you
 need the pack to be re-hosted? Its quite unlikely that we'll do it because
 its a huge testing effort. And so far many people have been using

Re: [Dev] Getting error when starting WSO2 IS 5.1.0 Key Manager in Mesos DC/OS

2016-06-28 Thread Akila Ravihansa Perera 
Hi Nuwan,

I think ideally this should have been automated as a maven task and added
to the product-apim repo as a tool. The distribution that you have built
via UI cannot be replicated. We don't even recommend installing features
via UI for a production deployment then why have we hosted this publicly?

Thanks.

On Tue, Jun 28, 2016 at 3:47 PM, Imesh Gunaratne  wrote:

> Hi Nuwan,
>
> It would be ideal to fix this issue and re-host the distribution or we can
> even fix it in the next release. For the time being will mention this in
> the documentation and provide steps for the user to overcome this problem.
>
> Thanks
>
> On Tue, Jun 28, 2016 at 2:41 PM, Niranjan Karunanandham  > wrote:
>
>> Hi Thanuja / Nuwan,
>>
>> On Tue, Jun 28, 2016 at 2:08 PM, Nuwan Dias  wrote:
>>
>>>
>>>
>>> On Tue, Jun 28, 2016 at 11:27 AM, Thanuja Uruththirakodeeswaran <
>>> thanu...@wso2.com> wrote:
>>>
 Hi All,

 I'm getting below error when deploying WSO2 IS 5.1.0 Key Manager
 application [1] in Mesos DC/OS. I have used the hosted IS-5.1.0 Key Manager
 pack [2] to build the docker image.

 I0627 02:40:36.478433 27342 exec.cpp:143] Version: 0.28.1
 I0627 02:40:36.481850 27369 exec.cpp:217] Executor registered on slave
 877f8cbc-9f5d-4fed-ab3d-82e145e8d33a-S3
 rm: cannot remove
 '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/axis2-tmp-6697148023468900485.tmp':
 Directory not empty
 rm: cannot remove
 '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/bundles_info_f09679b3-4b3d-4f19-8ddf-139763830045':
 Directory not empty
 java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
 at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)
 Caused by: java.lang.RuntimeException:
 /mnt/wso2is-km-5.1.0/repository/components/default/configuration/org.eclipse.osgi/.manager/.fileTable.9
 (No such file or directory)
 at org.wso2.carbon.server.CarbonLauncher.launch(CarbonLauncher.java:115)
 at org.wso2.carbon.server.Main.launchCarbon(Main.java:160)
 at org.wso2.carbon.server.Main.main(Main.java:94)
 ... 6 more

 If I remove the files in
 [CARBON_HOME]/repository/components/default/configuration/org.eclipse.osgi/.manager/
 directory in the hosted KM pack and use it to build the docker images, I am
 able to deploy it in successfully and the server starts without any issue.

 As per the offline discussion with Niranjan, the above mentioned files
 will be created if we install the features via UI. If we can install Key
 Manager features using pom files, then above issue will be resolved.

>>>
>>> What does it mean? Does it mean that installing features via UI has a
>>> bug and it should not be used?
>>>
>> AFAIU in the pack, the features have been installed via the feature
>> management UI which requires in starting the server. This create temporary
>> files as mentioned above. In Ubuntu / windows environment, when we start
>> the pack, there are no issue. But in Mesos, it refers to the old files. The
>> issue was resolved by deleting the temporary file. IMO since we have a
>> workaround by deleting these temporary files and upload it to docker
>> registry. In which case we do not have to recreate IS 5.1.0 Key Manager
>> again.
>>
>>
>>>
 @APIM_team: Shall we fix this and host the new IS 5.1.0 Key Manager
 pack?

>>>
>>> You have now successfully created the docker image right? Why do you
>>> need the pack to be re-hosted? Its quite unlikely that we'll do it because
>>> its a huge testing effort. And so far many people have been using this
>>> without any issues.
>>>

 [1]. https://github.com/wso2/mesos-artifacts/tree/master/wso2is-km
 [2].
 http://product-dist.wso2.com/downloads/api-manager/1.10.0/identity-server/wso2is-5.1.0.zip

 Thanks.

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

 mobile: +94 774363167

>>>
>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Technical Lead - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>
>> Regards,
>> Nira
>>
>> --
>>
>>
>> *Niranjan Karunanandham*
>> Associate Technical Lead - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> Lean . Enterprise . Middleware
>
>
> ___
> Dev

Re: [Dev] Getting error when starting WSO2 IS 5.1.0 Key Manager in Mesos DC/OS

2016-06-28 Thread Imesh Gunaratne 
Hi Nuwan,

It would be ideal to fix this issue and re-host the distribution or we can
even fix it in the next release. For the time being will mention this in
the documentation and provide steps for the user to overcome this problem.

Thanks

On Tue, Jun 28, 2016 at 2:41 PM, Niranjan Karunanandham 
wrote:

> Hi Thanuja / Nuwan,
>
> On Tue, Jun 28, 2016 at 2:08 PM, Nuwan Dias  wrote:
>
>>
>>
>> On Tue, Jun 28, 2016 at 11:27 AM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I'm getting below error when deploying WSO2 IS 5.1.0 Key Manager
>>> application [1] in Mesos DC/OS. I have used the hosted IS-5.1.0 Key Manager
>>> pack [2] to build the docker image.
>>>
>>> I0627 02:40:36.478433 27342 exec.cpp:143] Version: 0.28.1
>>> I0627 02:40:36.481850 27369 exec.cpp:217] Executor registered on slave
>>> 877f8cbc-9f5d-4fed-ab3d-82e145e8d33a-S3
>>> rm: cannot remove
>>> '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/axis2-tmp-6697148023468900485.tmp':
>>> Directory not empty
>>> rm: cannot remove
>>> '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/bundles_info_f09679b3-4b3d-4f19-8ddf-139763830045':
>>> Directory not empty
>>> java.lang.reflect.InvocationTargetException
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
>>> at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)
>>> Caused by: java.lang.RuntimeException:
>>> /mnt/wso2is-km-5.1.0/repository/components/default/configuration/org.eclipse.osgi/.manager/.fileTable.9
>>> (No such file or directory)
>>> at org.wso2.carbon.server.CarbonLauncher.launch(CarbonLauncher.java:115)
>>> at org.wso2.carbon.server.Main.launchCarbon(Main.java:160)
>>> at org.wso2.carbon.server.Main.main(Main.java:94)
>>> ... 6 more
>>>
>>> If I remove the files in
>>> [CARBON_HOME]/repository/components/default/configuration/org.eclipse.osgi/.manager/
>>> directory in the hosted KM pack and use it to build the docker images, I am
>>> able to deploy it in successfully and the server starts without any issue.
>>>
>>> As per the offline discussion with Niranjan, the above mentioned files
>>> will be created if we install the features via UI. If we can install Key
>>> Manager features using pom files, then above issue will be resolved.
>>>
>>
>> What does it mean? Does it mean that installing features via UI has a bug
>> and it should not be used?
>>
> AFAIU in the pack, the features have been installed via the feature
> management UI which requires in starting the server. This create temporary
> files as mentioned above. In Ubuntu / windows environment, when we start
> the pack, there are no issue. But in Mesos, it refers to the old files. The
> issue was resolved by deleting the temporary file. IMO since we have a
> workaround by deleting these temporary files and upload it to docker
> registry. In which case we do not have to recreate IS 5.1.0 Key Manager
> again.
>
>
>>
>>> @APIM_team: Shall we fix this and host the new IS 5.1.0 Key Manager pack?
>>>
>>
>> You have now successfully created the docker image right? Why do you need
>> the pack to be re-hosted? Its quite unlikely that we'll do it because its a
>> huge testing effort. And so far many people have been using this without
>> any issues.
>>
>>>
>>> [1]. https://github.com/wso2/mesos-artifacts/tree/master/wso2is-km
>>> [2].
>>> http://product-dist.wso2.com/downloads/api-manager/1.10.0/identity-server/wso2is-5.1.0.zip
>>>
>>> Thanks.
>>>
>>> --
>>> Thanuja Uruththirakodeeswaran
>>> Software Engineer
>>> WSO2 Inc.;http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 774363167
>>>
>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Technical Lead - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
> Regards,
> Nira
>
> --
>
>
> *Niranjan Karunanandham*
> Associate Technical Lead - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>



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

Re: [Dev] Getting error when starting WSO2 IS 5.1.0 Key Manager in Mesos DC/OS

2016-06-28 Thread Niranjan Karunanandham 
Hi Thanuja / Nuwan,

On Tue, Jun 28, 2016 at 2:08 PM, Nuwan Dias  wrote:

>
>
> On Tue, Jun 28, 2016 at 11:27 AM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Hi All,
>>
>> I'm getting below error when deploying WSO2 IS 5.1.0 Key Manager
>> application [1] in Mesos DC/OS. I have used the hosted IS-5.1.0 Key Manager
>> pack [2] to build the docker image.
>>
>> I0627 02:40:36.478433 27342 exec.cpp:143] Version: 0.28.1
>> I0627 02:40:36.481850 27369 exec.cpp:217] Executor registered on slave
>> 877f8cbc-9f5d-4fed-ab3d-82e145e8d33a-S3
>> rm: cannot remove
>> '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/axis2-tmp-6697148023468900485.tmp':
>> Directory not empty
>> rm: cannot remove
>> '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/bundles_info_f09679b3-4b3d-4f19-8ddf-139763830045':
>> Directory not empty
>> java.lang.reflect.InvocationTargetException
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
>> at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)
>> Caused by: java.lang.RuntimeException:
>> /mnt/wso2is-km-5.1.0/repository/components/default/configuration/org.eclipse.osgi/.manager/.fileTable.9
>> (No such file or directory)
>> at org.wso2.carbon.server.CarbonLauncher.launch(CarbonLauncher.java:115)
>> at org.wso2.carbon.server.Main.launchCarbon(Main.java:160)
>> at org.wso2.carbon.server.Main.main(Main.java:94)
>> ... 6 more
>>
>> If I remove the files in
>> [CARBON_HOME]/repository/components/default/configuration/org.eclipse.osgi/.manager/
>> directory in the hosted KM pack and use it to build the docker images, I am
>> able to deploy it in successfully and the server starts without any issue.
>>
>> As per the offline discussion with Niranjan, the above mentioned files
>> will be created if we install the features via UI. If we can install Key
>> Manager features using pom files, then above issue will be resolved.
>>
>
> What does it mean? Does it mean that installing features via UI has a bug
> and it should not be used?
>
AFAIU in the pack, the features have been installed via the feature
management UI which requires in starting the server. This create temporary
files as mentioned above. In Ubuntu / windows environment, when we start
the pack, there are no issue. But in Mesos, it refers to the old files. The
issue was resolved by deleting the temporary file. IMO since we have a
workaround by deleting these temporary files and upload it to docker
registry. In which case we do not have to recreate IS 5.1.0 Key Manager
again.


>
>> @APIM_team: Shall we fix this and host the new IS 5.1.0 Key Manager pack?
>>
>
> You have now successfully created the docker image right? Why do you need
> the pack to be re-hosted? Its quite unlikely that we'll do it because its a
> huge testing effort. And so far many people have been using this without
> any issues.
>
>>
>> [1]. https://github.com/wso2/mesos-artifacts/tree/master/wso2is-km
>> [2].
>> http://product-dist.wso2.com/downloads/api-manager/1.10.0/identity-server/wso2is-5.1.0.zip
>>
>> Thanks.
>>
>> --
>> Thanuja Uruththirakodeeswaran
>> Software Engineer
>> WSO2 Inc.;http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 774363167
>>
>
>
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>

Regards,
Nira

-- 


*Niranjan Karunanandham*
Associate Technical Lead - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting error when starting WSO2 IS 5.1.0 Key Manager in Mesos DC/OS

2016-06-28 Thread Nuwan Dias 
On Tue, Jun 28, 2016 at 11:27 AM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi All,
>
> I'm getting below error when deploying WSO2 IS 5.1.0 Key Manager
> application [1] in Mesos DC/OS. I have used the hosted IS-5.1.0 Key Manager
> pack [2] to build the docker image.
>
> I0627 02:40:36.478433 27342 exec.cpp:143] Version: 0.28.1
> I0627 02:40:36.481850 27369 exec.cpp:217] Executor registered on slave
> 877f8cbc-9f5d-4fed-ab3d-82e145e8d33a-S3
> rm: cannot remove
> '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/axis2-tmp-6697148023468900485.tmp':
> Directory not empty
> rm: cannot remove
> '/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/bundles_info_f09679b3-4b3d-4f19-8ddf-139763830045':
> Directory not empty
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
> at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)
> Caused by: java.lang.RuntimeException:
> /mnt/wso2is-km-5.1.0/repository/components/default/configuration/org.eclipse.osgi/.manager/.fileTable.9
> (No such file or directory)
> at org.wso2.carbon.server.CarbonLauncher.launch(CarbonLauncher.java:115)
> at org.wso2.carbon.server.Main.launchCarbon(Main.java:160)
> at org.wso2.carbon.server.Main.main(Main.java:94)
> ... 6 more
>
> If I remove the files in
> [CARBON_HOME]/repository/components/default/configuration/org.eclipse.osgi/.manager/
> directory in the hosted KM pack and use it to build the docker images, I am
> able to deploy it in successfully and the server starts without any issue.
>
> As per the offline discussion with Niranjan, the above mentioned files
> will be created if we install the features via UI. If we can install Key
> Manager features using pom files, then above issue will be resolved.
>

What does it mean? Does it mean that installing features via UI has a bug
and it should not be used?

>
> @APIM_team: Shall we fix this and host the new IS 5.1.0 Key Manager pack?
>

You have now successfully created the docker image right? Why do you need
the pack to be re-hosted? Its quite unlikely that we'll do it because its a
huge testing effort. And so far many people have been using this without
any issues.

>
> [1]. https://github.com/wso2/mesos-artifacts/tree/master/wso2is-km
> [2].
> http://product-dist.wso2.com/downloads/api-manager/1.10.0/identity-server/wso2is-5.1.0.zip
>
> Thanks.
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>



-- 
Nuwan Dias

Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Getting error when starting WSO2 IS 5.1.0 Key Manager in Mesos DC/OS

2016-06-27 Thread Thanuja Uruththirakodeeswaran 
Hi All,

I'm getting below error when deploying WSO2 IS 5.1.0 Key Manager
application [1] in Mesos DC/OS. I have used the hosted IS-5.1.0 Key Manager
pack [2] to build the docker image.

I0627 02:40:36.478433 27342 exec.cpp:143] Version: 0.28.1
I0627 02:40:36.481850 27369 exec.cpp:217] Executor registered on slave
877f8cbc-9f5d-4fed-ab3d-82e145e8d33a-S3
rm: cannot remove
'/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/axis2-tmp-6697148023468900485.tmp':
Directory not empty
rm: cannot remove
'/mnt/192.168.65.111-172.17.0.6/wso2is-km-5.1.0/tmp/bundles_info_f09679b3-4b3d-4f19-8ddf-139763830045':
Directory not empty
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)
Caused by: java.lang.RuntimeException:
/mnt/wso2is-km-5.1.0/repository/components/default/configuration/org.eclipse.osgi/.manager/.fileTable.9
(No such file or directory)
at org.wso2.carbon.server.CarbonLauncher.launch(CarbonLauncher.java:115)
at org.wso2.carbon.server.Main.launchCarbon(Main.java:160)
at org.wso2.carbon.server.Main.main(Main.java:94)
... 6 more

If I remove the files in
[CARBON_HOME]/repository/components/default/configuration/org.eclipse.osgi/.manager/
directory in the hosted KM pack and use it to build the docker images, I am
able to deploy it in successfully and the server starts without any issue.

As per the offline discussion with Niranjan, the above mentioned files will
be created if we install the features via UI. If we can install Key Manager
features using pom files, then above issue will be resolved.

@APIM_team: Shall we fix this and host the new IS 5.1.0 Key Manager pack?

[1]. https://github.com/wso2/mesos-artifacts/tree/master/wso2is-km
[2].
http://product-dist.wso2.com/downloads/api-manager/1.10.0/identity-server/wso2is-5.1.0.zip

Thanks.

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