Re: [Dev] [BPS][BPMN]: Rest API - Create New Deployment

[Firzhan Naqash]

Hi Chaturika,

When you are using the activiti rest-api, the process artifacts won't get
copied to the deployment/server/bpmn folder.
Thus it won't get synchronized with the rest of the nodes.

When you upload the archived bar file, it copies to the respective location
and then passes the process artifacts to the activiti api.


Regards,
Firzhan


-- 
*Firzhan Naqash*
Senior Software Engineer - Integration Platform Team
WSO2 Inc. http://wso2.com

email: firz...@wso2.com 
mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
blog: http://firzhanblogger.blogspot.com/
  *
*twitter: https://twitter.com/firzhan007  |
linked-in: **https://www.linkedin.com/in/firzhan
*

On Mon, Oct 5, 2015 at 12:15 PM, Chathurika De Silva 
wrote:

> Hi
>
> I am trying to use the $subject through jmeter. I am getting response code
> 201 which is the success code for deployment [1].
>
> In the BPS logs i am observing the following
>
> TID: [-1234] [] [2015-10-05 06:21:15,781]  INFO
> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} -  LDAP
> connection created successfully in read-write mode
> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager}
> TID: [-1234] [] [2015-10-05 06:21:15,823]  INFO
> {org.activiti.engine.impl.bpmn.deployer.BpmnDeployer} -  Processing
> resource manualTask.bpmn20.xml
> {org.activiti.engine.impl.bpmn.deployer.BpmnDeployer}
>
> The test is done in a Worker/Manager cluster fronted by Nginx with dep
> sync enabled. For manual uploads it works fine with manager syncing the
> deployed to the workers. But when done with the api there is no proper
> deployment being done.
>
> The jira [2] contains the debug logs of activiti and the script i have
> used.
>
> [1] http://www.activiti.org/userguide/#_create_a_new_deployment
> [2] https://wso2.org/jira/browse/BPS-892
>
> Any help regarding this is highly appreciated.
>
> 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
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [BPS][BPMN]: Rest API - Create New Deployment

[Chathurika De Silva]

Hi

I am trying to use the $subject through jmeter. I am getting response code
201 which is the success code for deployment [1].

In the BPS logs i am observing the following

TID: [-1234] [] [2015-10-05 06:21:15,781]  INFO
{org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} -  LDAP
connection created successfully in read-write mode
{org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager}
TID: [-1234] [] [2015-10-05 06:21:15,823]  INFO
{org.activiti.engine.impl.bpmn.deployer.BpmnDeployer} -  Processing
resource manualTask.bpmn20.xml
{org.activiti.engine.impl.bpmn.deployer.BpmnDeployer}

The test is done in a Worker/Manager cluster fronted by Nginx with dep sync
enabled. For manual uploads it works fine with manager syncing the deployed
to the workers. But when done with the api there is no proper deployment
being done.

The jira [2] contains the debug logs of activiti and the script i have used.

[1] http://www.activiti.org/userguide/#_create_a_new_deployment
[2] https://wso2.org/jira/browse/BPS-892

Any help regarding this is highly appreciated.

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] WSO2 Committers += Pandula Kariyawasam

[Malintha Adikari]

Congratz Pandula


On Mon, Oct 5, 2015 at 11:54 AM, Chanaka Fernando  wrote:

> Congratulations Pandula !!!
>
> On Mon, Oct 5, 2015 at 11:13 AM, Pavithra Madurangi 
> wrote:
>
>> Hi All,
>>
>> It's my pleasure to announce Pandula Kariyawasam as a WSO2 Committer.
>> Pandula is an active member of QA team and has given a great contribution
>> to Application Server, API Manager, G-Reg, ESB, EMM, BAM, App Factory and
>> IS product releases. So in recognition of his contribution, dedication and
>> ownership shown towards the tasks given to him, he has been voted as a WSO2
>> Committer.
>>
>> Pandula, congratulations and keep up the good work...!
>>
>> Regards,
>> Pavithra
>> --
>> *Pavithra Madurangi*
>> Associate Technical Lead - QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: 0777207357 / 0112747089
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>
> ___
> 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] WSO2 Committers += Pandula Kariyawasam

[Chanaka Fernando]

Congratulations Pandula !!!

On Mon, Oct 5, 2015 at 11:13 AM, Pavithra Madurangi 
wrote:

> Hi All,
>
> It's my pleasure to announce Pandula Kariyawasam as a WSO2 Committer.
> Pandula is an active member of QA team and has given a great contribution
> to Application Server, API Manager, G-Reg, ESB, EMM, BAM, App Factory and
> IS product releases. So in recognition of his contribution, dedication and
> ownership shown towards the tasks given to him, he has been voted as a WSO2
> Committer.
>
> Pandula, congratulations and keep up the good work...!
>
> Regards,
> Pavithra
> --
> *Pavithra Madurangi*
> Associate Technical Lead - QA.
> WSO2 Inc.: http://wso2.com/
> Mobile: 0777207357 / 0112747089
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] Moving Nginx Extension Changes Upstream

[Reka Thirunavukkarasu]

Hi Imesh,

I have added all the changes to Stratos-4.1.x branch now..

Thanks,
Reka

On Mon, Oct 5, 2015 at 10:20 AM, Imesh Gunaratne  wrote:

> Thanks Reka!
>
> On Mon, Oct 5, 2015 at 8:20 AM, Reka Thirunavukkarasu 
> wrote:
>
>> Hi
>>
>> Thanks Imesh..Sure..I will Integrate those changes to Stratos 4.1.x
>> branch..
>>
>> Thanks,
>> Reka
>>
>> On Mon, Oct 5, 2015 at 12:02 AM, Imesh Gunaratne  wrote:
>>
>>> Hi Reka,
>>>
>>> I removed nginx extension source from Private PaaS repository to be
>>> added to Stratos 4.1.x branch [1]. This is to make sure that we do not
>>> release nginx extension with Private PaaS 4.1.0-Beta/GA rather it to be
>>> taken from corresponding Stratos release.
>>>
>>> Would you mind sending these changes to Stratos 4.1.x branch? I did not
>>> do this because it contains few great improvements you did recently and
>>> wanted you to commit them.
>>>
>>> [1]
>>> https://github.com/wso2/product-private-paas/commit/1402f40a9199f39ab0fe72f27dfa14f6510be08f
>>>
>>> Thanks
>>>
>>> --
>>> *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
>>>
>>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> *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
>
>


-- 
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Pandula Kariyawasam

[Pavithra Madurangi]

Hi All,

It's my pleasure to announce Pandula Kariyawasam as a WSO2 Committer.
Pandula is an active member of QA team and has given a great contribution
to Application Server, API Manager, G-Reg, ESB, EMM, BAM, App Factory and
IS product releases. So in recognition of his contribution, dedication and
ownership shown towards the tasks given to him, he has been voted as a WSO2
Committer.

Pandula, congratulations and keep up the good work...!

Regards,
Pavithra
-- 
*Pavithra Madurangi*
Associate Technical Lead - QA.
WSO2 Inc.: http://wso2.com/
Mobile: 0777207357 / 0112747089
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Indunil Upeksha Rathnayake]

Hi,

As per my understanding on the non durable subscription flow in MB, when
adding a subscription for a topic (ex:topic1), it will create an internal
role if topic1 is not exists. After adding an internal role, it'll add
permissions to the role such as publish, subscribe etc. This will update
the UM_PERMISSION and UM_ROLE_PERMISSION tables. In UM_PERMISSION table it
will add a resourceId per a topic. And the role created for a topic will be
deleted with the permissions available to that, when all the subscriptions
for the same topic are disconnected. So that the row level changes in
UM_PERMISSION will occur when adding and deleting a topic.

When adding a topic, an INSERT statement in UM_PERMISSION table, will place
an exclusive lock on rows until that has been committed (or rolled back).
In there, a SELECT might be blocked, since in the mean time this
subscription in another node, will be accessing permissions for the same
topic in UM_PERMISSION table, by considering that the permissions are
available since the role is created for the topic. But the deadlock occurs
in "addAuthorizationForRole" method in JDBCAuthorizationManager class,
where it adds permissions for the role. Two nodes can't be adding and
giving permissions to the same topic, so that this can't be a row level
locking and has to be a table level locking.  When deleting a topic,
another subscription for same topic can't be exists, so in that scenario
also a row level locking can't be occur due to SELECT, but a table level
locking can be exists.

This may be the reason that this works for oracle but not for mssql and can
be because of the Lock Escalation available in SQL Server or as in the [1]
some versions of SQL Server doesn't support row level locking. Please refer
[1] for the difference in locking mechanism in Oracle and SQL Server .

If the reason behind this is lock escalation, that can be avoided by
introducing proper indexing mechanism. And "WITH (NOLOCK)" or "WITH
(READPAST)" also can be useful in mssql to avoid deadlocks, but it'll lead
to invalid results or dirty reads. So as tharindu mentioned, the best way
to avoid this can be removing changes done in UM_PERMISSION table.

[1]
https://docs.oracle.com/cd/E10405_01/appdev.120/e10379/ss_oracle_compared.htm#i1038519

Thanks and Regards
-- 
Indunil Upeksha Rathnayake
Software Engineer | WSO2 Inc
Emailindu...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS][IS] BPEL faile to pass headers from tenant mode

[Harsha Thirimanna]

Hi All,
It seems this is a bug and I have upgraded BPS features to 4.4.3 and it was
working fine now. There was this issue in BPS 3.2.0 and component 4.4.2.


*Harsha Thirimanna*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
* *
*email: **hars...@wso2.com* * cell: +94 71 5186770 *
*twitter: **http://twitter.com/ *
*harshathirimannlinked-in: **http:
**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
*

*Lean . Enterprise . Middleware*


On Fri, Oct 2, 2015 at 6:22 PM, Harsha Thirimanna  wrote:

> Did you see my wire logs ? It doesn't have any, what that mean. That is
> same bpel package we are using that you gave
>
>
> *Harsha Thirimanna*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> * *
> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
> *twitter: **http://twitter.com/ *
> *harshathirimannlinked-in: **http:
> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
> *
>
> *Lean . Enterprise . Middleware*
>
>
> On Fri, Oct 2, 2015 at 6:17 PM, Vinod Kavinda  wrote:
>
>> Hi Harsha,
>> I observed the requests using tcpMon(Used http). Seem to be it contains
>> the basic author headers in both tenant and super tenant mode. Please see
>> the attached logs.
>>
>> Regards,
>> Vinod
>>
>> On Fri, Oct 2, 2015 at 11:47 AM, Harsha Thirimanna 
>> wrote:
>>
>>> I have created a Jira for this[1]
>>>
>>> [1] https://wso2.org/jira/browse/BPS-888 because we are blocked.
>>>
>>>
>>> *Harsha Thirimanna*
>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>> * *
>>> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
>>> *twitter: **http://twitter.com/ *
>>> *harshathirimannlinked-in: **http:
>>> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>> *
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> On Fri, Oct 2, 2015 at 11:35 AM, Harsha Thirimanna 
>>> wrote:
>>>
 Hi ,

 We have deployed bpel to BPS in tenant mode and it will call back to
 IS. That call back endpoint is admin service in IS. It is fail and says
 unauthorized from BPS side and IS side we can't see
 the Authorization headers. This is working fine in supper tenant mode.

 I checked with BPS 3.2.0
 And
 BPS 4.4.2 features embeded in IS

 I have attached wire logs from BPS for super tenant and a tenant.

 In BPS side exception :


 TID: [0] [BPS] [2015-10-02 09:09:41,829]  INFO
 {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  '
 a...@abc.com [1]' logged in at [2015-10-02 09:09:41,828+0530]
 {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
 TID: [0] [BPS] [2015-10-02 09:10:12,129]  INFO
 {org.apache.axis2.transport.http.HTTPSender} -  Unable to sendViaPost to
 url[https://localhost:9443/services/WorkflowCallbackService]
 {org.apache.axis2.transport.http.HTTPSender}
 org.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
 at
 org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:308)
 at
 org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:194)
 at
 org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
 at
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
 at
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
 at
 org.wso2.carbon.core.multitenancy.transports.TenantTransportSender.invoke(TenantTransportSender.java:198)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
 at
 org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
 at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
 at
 org.wso2.carbon.bpel.core.ode.integration.utils.AxisServiceUtils.invokeService(AxisServiceUtils.java:305)
 at
 org.wso2.carbon.bpel.core.ode.integration.PartnerService.invoke(PartnerService.java:324)
 at
 org.wso2.carbon.bpel.core.ode.integration.BPELMessageExchangeContextImpl.invokePartner(BPELMessageExchangeContextImpl.java:43)
 at
 org.apache.ode.bpel.engine.BpelRuntimeContextImpl.invoke(BpelRuntimeContextImpl.java:793)
 at org.apache.ode.bpel.runtime.INVOKE.run(INVOKE.java:130)
 at sun.reflect

Re: [Dev] [Private PaaS] Moving Nginx Extension Changes Upstream

[Imesh Gunaratne]

Thanks Reka!

On Mon, Oct 5, 2015 at 8:20 AM, Reka Thirunavukkarasu  wrote:

> Hi
>
> Thanks Imesh..Sure..I will Integrate those changes to Stratos 4.1.x
> branch..
>
> Thanks,
> Reka
>
> On Mon, Oct 5, 2015 at 12:02 AM, Imesh Gunaratne  wrote:
>
>> Hi Reka,
>>
>> I removed nginx extension source from Private PaaS repository to be added
>> to Stratos 4.1.x branch [1]. This is to make sure that we do not release
>> nginx extension with Private PaaS 4.1.0-Beta/GA rather it to be taken from
>> corresponding Stratos release.
>>
>> Would you mind sending these changes to Stratos 4.1.x branch? I did not
>> do this because it contains few great improvements you did recently and
>> wanted you to commit them.
>>
>> [1]
>> https://github.com/wso2/product-private-paas/commit/1402f40a9199f39ab0fe72f27dfa14f6510be08f
>>
>> Thanks
>>
>> --
>> *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
>>
>>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>


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

[Dev] WSO2 Committers += Keerthika Mahendralingam

[Malaka Silva]

Hi Devs,

Its my pleasure to welcome Keerthika Mahendralingam as a WSO2 Committer.

Keerthika has been a key member of the Platform Extensions Team (Earlier
Connector Team) contributing immensely to many aspects ESB Connectors
development and connector store ever since she joined us. In recognition of
her contributions, ownership shown towards the tasks/responsibilities
assigned to her. She has always taken an extra mile related to the tasks
assigned to her.

Keerthika, welcome aboard and keep up the good work .. !

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/


Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB-4.9.0]NPE at save configuration

[Nirdesha Munasinghe]

Done.
Thank you!

On Mon, Oct 5, 2015 at 9:17 AM, Ajith Vitharana  wrote:

> Please remove  "DurableSubscriberEndpoint" />   from  sub1_fails sequence.
>
> -Ajith
>
> On Sun, Oct 4, 2015 at 11:44 PM, Nirdesha Munasinghe 
> wrote:
>
>> Hi Ajith,
>>
>> Thanks for the info. I made the suggested edits.
>>
>> Cheers,
>> -Nirdesha
>>
>> On Mon, Oct 5, 2015 at 2:59 AM, Ajith Vitharana  wrote:
>>
>>> While debugging found that task manager is not initialize. This is due
>>> to outdated configurations. The EIP sample should be updated with following
>>> configuration changes.
>>>
>>> 1. add  >> "org.wso2.carbon.mediation.ntask.NTaskTaskManager"/>
>>> 2. class should be org.apache.synapse.message.processor.*impl*
>>> .forwarder.ScheduledMessageForwardingProcessor
>>> 3. target.endpoint parameter is missing in messageProcessor
>>> configurations.
>>>
>>> [1]
>>> https://docs.wso2.com/display/ESB490/Sample+702%3A+Introduction+to+Message+Forwarding+Processor
>>>
>>>  -Ajith
>>>
>>> On Sun, Oct 4, 2015 at 3:54 PM, Ajith Vitharana  wrote:
>>>
 Hi All,

 First I replaced the source view from the configuration [1] and it
 worked. Then I just click on update button. Now each time getting this NPE.

 [1]
 https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber


 [2015-10-04 15:50:36,869] ERROR - ConfigAdmin Error while updating the
 Synapse configuration
 j*ava.lang.NullPointerException*
 * at
 org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.destroy(ScheduledMessageProcessor.java:309)*
 at
 org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.cleanupCurrentConfiguration(ConfigurationUpdater.java:202)
 at
 org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.update(ConfigurationUpdater.java:130)
 at
 org.wso2.carbon.mediation.configadmin.ConfigAdmin.updateConfiguration(ConfigAdmin.java:150)
 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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
 at
 org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
 at
 org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
 at
 org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
 at
 org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
 at
 org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
 at
 org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
 at
 org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
 at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
 at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
 at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
 at
 org.wso2.carbon.mediation.configadmin.stub.ConfigServiceAdminStub.updateConfiguration(ConfigServiceAdminStub.java:1340)
 at
 org.wso2.carbon.mediation.configadmin.ui.ConfigManagementClient.updateConfiguration(ConfigManagementClient.java:98)
 at
 org.apache.jsp.configadmin.saveconfig_jsp._jspService(saveconfig_jsp.java:169)
 at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
 at
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
 at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at
 org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
 at
 org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
 at
 org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
 at
 org.eclipse.equinox.http.servlet.

Re: [Dev] About Edge Analytics Service-Mobile IOT

[Lakini Senanayaka]

Hi,

I was on leave  on 1st of October so I couldn't reach your message.I'm
really sorry for that.
I can give you an update today.

Thank you.

On Thu, Oct 1, 2015 at 7:52 AM, Srinath Perera  wrote:

> Can we have an update today 1.30pm @Trace?
>
> --Srinath
>
> On Sat, Aug 29, 2015 at 12:26 AM, Lasantha Fernando 
> wrote:
>
>> That's great!...
>>
>> On 28 August 2015 at 18:25, Lakini Senanayaka  wrote:
>>
>>> Hi Lasantha,
>>>
>>> I have corrected the issue you mentioned above.Now the events are
>>> processing correctly.
>>>
>>> Thank you.
>>>
>>> On Tue, Aug 25, 2015 at 11:38 PM, Lasantha Fernando 
>>> wrote:
>>>
 Hi Lakini,

 I earlier assumed that you would be using the latest Siddhi-3.0.0 which
 has the concept of different ExecutionPlanRuntimes. But looking at the
 code, it seems you are using Siddhi-2.1.0.wso2v1. In that case, my
 explanation about ExecutionPlanRuntime would be incorrect since
 Siddhi-2.1.0 did not have ExecutionPlanRuntimes. For Siddhi-2.1.0,

 1. Multi-threading when sending events would work. But Siddhi itself
 would not streamline the events coming from different threads and handover
 the work to Siddhi's own threads. i.e. the thread that sends the event
 would be involved in processing and send the output event (unless
 siddhi-windows were involved). The Siddhi engine itself was not
 multithreaded, but it can handle events coming in from multiple threads. It
 is thread-safe.

 2. When modifying queries using multiple threads, the queries were
 tracked by the query-id which involved a generated UUID. So if you added
 similar queries to the same SiddhiManager instance, it would be added as
 two different queries. To edit a query, you would have to remove the old
 query first using its query id and add the modified query.

 But looking at your code, it seems the two client apps are calling the
 IEdgeAnalyticsService.Stub.getService() method and in that method you are
 creating a new CEP instance each time, which in turn creates a new Siddhi
 manager. Given that, your two client apps would deploy their queries on two
 different Siddhi instances.

 However, if there is only one instance of the service itself, calling
 the RemoteService.getService() method simply creates a new CEP instance and
 assigns that to the instance variable. i.e. the second call would overwrite
 the reference to the CEP instance created by the first call. So definitely
 when you call the RemoteService.sendData() method, it would send those
 events to the CEP/Siddhi instance that was created by the second call, even
 if it is the first client that is sending the events.

 I think there is an issue in simply assigning a new instance to the
 'cep' variable
 in com.example.lakini.edgeanalyticsservice.EdgeAnalyticsService
 IEdgeAnalyticsService.Stub.getService() method.

 Can you please correct this issue and see whether events are being
 processed correctly?

 Thanks,
 Lasantha

 On 25 August 2015 at 18:53, Lakini Senanayaka  wrote:

> Hi all,
>
> As per request I have shared my source code.You can find my sample
> project [1] from this link and I have point out the place[2][3][4] it will
> be easier to you to understand.
>
> [1] - sample edgeAnalyticsService
> 
> [2] - EdgeAnalyticsService
> 
> [3] - ClientApp1
> 
> [4] -ClientApp2
> 
>
> Thank you.
>
> On Tue, Aug 25, 2015 at 4:30 PM, Lasantha Fernando 
> wrote:
>
>> Hi Srinath, Lakini,
>>
>> Siddhi is thread safe when sending events. You can send events via
>> multiple threads without any issue.
>>
>> When changing queries via multiple threads, the execution plan
>> runtime of the previous query would have to be shutdown manually. Looking
>> at the current code, it seems that an ExecutionPlanRuntime instance would
>> be created after the query is parsed and that would be put to a
>> ConcurrentHashMap with the execution plan name (specified via 
>> annotations)
>> as the key. So if you do not shutdown that old runtime, it will still 
>> keep
>> running. But if you shutdown the execution plan from the client code, you
>> should not encounter any issue. @Suho, please correct if my understanding
>> is incorrect on this.
>>>

Re: [Dev] [ESB-4.9.0]NPE at save configuration

[Ajith Vitharana]

Please removefrom  sub1_fails sequence.

-Ajith

On Sun, Oct 4, 2015 at 11:44 PM, Nirdesha Munasinghe 
wrote:

> Hi Ajith,
>
> Thanks for the info. I made the suggested edits.
>
> Cheers,
> -Nirdesha
>
> On Mon, Oct 5, 2015 at 2:59 AM, Ajith Vitharana  wrote:
>
>> While debugging found that task manager is not initialize. This is due to
>> outdated configurations. The EIP sample should be updated with following
>> configuration changes.
>>
>> 1. add  > "org.wso2.carbon.mediation.ntask.NTaskTaskManager"/>
>> 2. class should be org.apache.synapse.message.processor.*impl*
>> .forwarder.ScheduledMessageForwardingProcessor
>> 3. target.endpoint parameter is missing in messageProcessor
>> configurations.
>>
>> [1]
>> https://docs.wso2.com/display/ESB490/Sample+702%3A+Introduction+to+Message+Forwarding+Processor
>>
>>  -Ajith
>>
>> On Sun, Oct 4, 2015 at 3:54 PM, Ajith Vitharana  wrote:
>>
>>> Hi All,
>>>
>>> First I replaced the source view from the configuration [1] and it
>>> worked. Then I just click on update button. Now each time getting this NPE.
>>>
>>> [1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
>>>
>>>
>>> [2015-10-04 15:50:36,869] ERROR - ConfigAdmin Error while updating the
>>> Synapse configuration
>>> j*ava.lang.NullPointerException*
>>> * at
>>> org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.destroy(ScheduledMessageProcessor.java:309)*
>>> at
>>> org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.cleanupCurrentConfiguration(ConfigurationUpdater.java:202)
>>> at
>>> org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.update(ConfigurationUpdater.java:130)
>>> at
>>> org.wso2.carbon.mediation.configadmin.ConfigAdmin.updateConfiguration(ConfigAdmin.java:150)
>>> 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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>>> at
>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>>> at
>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>> at
>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at
>>> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
>>> at
>>> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
>>> at
>>> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
>>> at
>>> org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>> at
>>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>>> at
>>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>>> at
>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>>> at
>>> org.wso2.carbon.mediation.configadmin.stub.ConfigServiceAdminStub.updateConfiguration(ConfigServiceAdminStub.java:1340)
>>> at
>>> org.wso2.carbon.mediation.configadmin.ui.ConfigManagementClient.updateConfiguration(ConfigManagementClient.java:98)
>>> at
>>> org.apache.jsp.configadmin.saveconfig_jsp._jspService(saveconfig_jsp.java:169)
>>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>> at
>>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
>>> at
>>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
>>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
>>> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>> at
>>> org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>> at
>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>> 

Re: [Dev] [ESB-4.9.0]NPE at save configuration

[Nirdesha Munasinghe]

Hi Ajith,

Thanks for the info. I made the suggested edits.

Cheers,
-Nirdesha

On Mon, Oct 5, 2015 at 2:59 AM, Ajith Vitharana  wrote:

> While debugging found that task manager is not initialize. This is due to
> outdated configurations. The EIP sample should be updated with following
> configuration changes.
>
> 1. add   "org.wso2.carbon.mediation.ntask.NTaskTaskManager"/>
> 2. class should be org.apache.synapse.message.processor.*impl*
> .forwarder.ScheduledMessageForwardingProcessor
> 3. target.endpoint parameter is missing in messageProcessor
> configurations.
>
> [1]
> https://docs.wso2.com/display/ESB490/Sample+702%3A+Introduction+to+Message+Forwarding+Processor
>
>  -Ajith
>
> On Sun, Oct 4, 2015 at 3:54 PM, Ajith Vitharana  wrote:
>
>> Hi All,
>>
>> First I replaced the source view from the configuration [1] and it
>> worked. Then I just click on update button. Now each time getting this NPE.
>>
>> [1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
>>
>>
>> [2015-10-04 15:50:36,869] ERROR - ConfigAdmin Error while updating the
>> Synapse configuration
>> j*ava.lang.NullPointerException*
>> * at
>> org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.destroy(ScheduledMessageProcessor.java:309)*
>> at
>> org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.cleanupCurrentConfiguration(ConfigurationUpdater.java:202)
>> at
>> org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.update(ConfigurationUpdater.java:130)
>> at
>> org.wso2.carbon.mediation.configadmin.ConfigAdmin.updateConfiguration(ConfigAdmin.java:150)
>> 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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>> at
>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>> at
>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>> at
>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at
>> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
>> at
>> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
>> at
>> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
>> at
>> org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>> at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>> at
>> org.wso2.carbon.mediation.configadmin.stub.ConfigServiceAdminStub.updateConfiguration(ConfigServiceAdminStub.java:1340)
>> at
>> org.wso2.carbon.mediation.configadmin.ui.ConfigManagementClient.updateConfiguration(ConfigManagementClient.java:98)
>> at
>> org.apache.jsp.configadmin.saveconfig_jsp._jspService(saveconfig_jsp.java:169)
>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
>> at
>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
>> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
>> at
>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.ca

Re: [Dev] Critical issue for IS 5.1.0 Beta

[Prasad Tissera]

Hi All,

Following exception can be avoided using unique h2 database urls for all
the cluster nodes.

TID: [1] [] [2015-10-02 18:35:07,720] @tenny1.com [1] [IS]ERROR
{org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO} -  Failed to
add resource to path /_system/governance. Referential integrity
constraint violation: "REG_RESOURCE_FK_BY_PATH_ID: PUBLIC.REG_RESOURCE
FOREIGN KEY(REG_PATH_ID, REG_TENANT_ID) REFERENCES
PUBLIC.REG_PATH(REG_PATH_ID, REG_TENANT_ID)"; SQL statement:


Regards,
Prasad.

On Mon, Oct 5, 2015 at 6:16 AM, Chandana Napagoda  wrote:

> Adding Prassad.
> On Oct 5, 2015 6:15 AM, "Chandana Napagoda"  wrote:
>
>> Hi Johan,
>>
>> I think this is the same issue PrassadT worked on last week. Please
>> verify cluster configuration with him.
>>
>> Regards,
>> Chandana
>> On Oct 4, 2015 10:17 PM, "Johann Nallathamby"  wrote:
>>
>>> Hi GReg Team,
>>>
>>> [1] has been reported by QA while running a load test on IS 5.1.0 Alpha.
>>> Looks like this is coming from registry kernel specific code. [2] is the
>>> code which executes this from IS side.
>>>
>>> I think one obvious improvement we can do in [2] is invoke following line
>>> IdentityTenantUtil.initializeRegistry(tenantId, tenantDomain);
>>> only under tenant condition in line 241. Because we don't need to load
>>> super tenant registry right?
>>>
>>> Can you please look into this problem and let us know if this is a
>>> problem in carbon-identity code or registry-kernel code ?
>>>
>>> [1] https://wso2.org/jira/browse/REGISTRY-3023
>>> [2]
>>> https://github.com/wso2/carbon-identity/blob/master/components/idp-mgt/org.wso2.carbon.idp.mgt/src/main/java/org/wso2/carbon/idp/mgt/IdentityProviderManager.java#L237-L255
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> *Johann Dilantha Nallathamby*
>>> Technical Lead & Product Lead of WSO2 Identity Server
>>> Governance Technologies Team
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - *+9476950*
>>> Blog - *http://nallaa.wordpress.com *
>>>
>>


-- 
Prasad Tissera
Software Engineer.
Mobile : +94777223444
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 BPS 3.5.0 RC2

[Firzhan Naqash]

Hi Devs,

Since this vote has been open for more than 72 hours and no -1s, we are
closing this vote. This vote passed with 9 *+1s* and 0  *-1*.

Regards,
Firzhan


-- 
*Firzhan Naqash*
Senior Software Engineer - Integration Platform Team
WSO2 Inc. http://wso2.com

email: firz...@wso2.com 
mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
blog: http://firzhanblogger.blogspot.com/
  *
*twitter: https://twitter.com/firzhan007  |
linked-in: **https://www.linkedin.com/in/firzhan
*

On Fri, Oct 2, 2015 at 11:53 AM, Chathura Ekanayake 
wrote:

> [+] Stable - go ahead and release
>
> Thanks,
> Chathura
>
> On Fri, Oct 2, 2015 at 11:35 AM, Milinda Perera  wrote:
>
>> Hi,
>>
>> I did smoke test in clustered setup + depsync with mysql database for
>> BPS, UM and registry (config registry and governance)
>>
>> 1. deploying / undeploying bpel
>> 1.1. with several versions
>> 1.2. with many (completed)
>> 2. deploying / undeploying bpmn and humantasks with versions
>> 3. bpel / humantask / bpmn versioning
>> 4. bpmn / humantask explorers simple smoke test of basic
>> functionalities + load balanced by fronting by nginx with sticky session
>> enabled
>> 5. Test bpel process cleanup tool
>>
>> [+] Stable - go ahead and release
>>
>> Thanks,
>> Milinda
>>
>> On Fri, Oct 2, 2015 at 11:25 AM, Nandika Jayawardana 
>> wrote:
>>
>>> Tested the cluster deployment, dep sync, bpel and bpmn functionality in
>>> cluster.
>>>
>>> [x] Stable- go ahead and release.
>>>
>>> Regards
>>> Nandika
>>>
>>> On Fri, Oct 2, 2015 at 6:47 AM, Natasha Wijesekara 
>>> wrote:
>>>
 Hi All,

 I tested the  functionalities of the  bpmn-explorer and the human-task
 explorer.

 [x] Stable- go ahead and release.

 Thanks,


 On Fri, Oct 2, 2015 at 2:28 AM, Shiva Balachandran 
 wrote:

> HI All,
>
> Tested the BPMN functionalites as well as the bpmn explorer. Looks
> amazing!
>
> ​
> ​
> [+] Stable - go ahead and release
>
> On Fri, Oct 2, 2015 at 1:10 AM, Hasitha Aravinda 
> wrote:
>
>> Hi
>>
>> I have tested and Reviewed followings and found no issues.
>>
>>- INSTALL.txt
>>- LICENSE.txt
>>- README.txt
>>- Tested Server start with MySQL -Dsetup.
>>
>> BPEL
>>
>>- Tested Correlation Scenario.
>>- Tested Correlation Violation scenario.
>>
>> HumanTask
>>
>>- HumanTask creation and basic task commands : Claim, Suspend,
>>Resume, Start, Complete, Skip, Fail, Delegate.
>>- HumanTask coordination - Process termination and Task Skip
>>scenario.
>>- HumanTask Notification creation.
>>
>> BPMN
>>
>>- Tested Service Tasks, User Tasks, Parallel Gateway,  Exclusive
>>Gateway processes.
>>
>>
>> ​
>> ​
>> [+] Stable - go ahead and release
>>
>> ​Thanks,
>> Hasitha.
>>
>>
>> On Wed, Sep 30, 2015 at 11:03 AM, Firzhan Naqash 
>> wrote:
>>
>>>
>>> Hi Devs,
>>>
>>> *WSO2 BPS 3.5.0 RC2 Release Vote*
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/browse/BPS-604?filter=12415
>>>
>>> Please download BPS 3.5.0 RC2 and test the functionality and vote.
>>> Vote will be open for 72 hours or as needed.
>>>
>>> Binary distribution at:
>>> http://svn.wso2.org/repos/wso2/people/firzhan/packs/bps/3.5.0/RC2/
>>>
>>> Maven staging repository:
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2bps-158/
>>>
>>> The tag to be voted upon :
>>> https://github.com/wso2/product-bps/releases/tag/v3.5.0-RC2
>>>
>>>
>>> [-] Broken - do not release (explain why)
>>> ​​
>>> [+] Stable - go ahead and release
>>>
>>> Thanks and Regards,
>>> WSO2 BPS Team
>>>
>>>
>>>
>>> Regards,
>>> Firzhan
>>>
>>>
>>> --
>>> *Firzhan Naqash*
>>> Senior Software Engineer - Integration Platform Team
>>> WSO2 Inc. http://wso2.com
>>>
>>> email: firz...@wso2.com 
>>> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
>>> blog: http://firzhanblogger.blogspot.com/
>>>   
>>> *
>>> *twitter: https://twitter.com/firzhan007
>>>  | linked-in: 
>>> **https://www.linkedin.com/in/firzhan
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> --
>> Hasitha Aravinda,
>> Senior Software Engineer,
>> WSO2 Inc.
>> E

Re: [Dev] [Private PaaS] Moving Nginx Extension Changes Upstream

[Reka Thirunavukkarasu]

Hi

Thanks Imesh..Sure..I will Integrate those changes to Stratos 4.1.x branch..

Thanks,
Reka

On Mon, Oct 5, 2015 at 12:02 AM, Imesh Gunaratne  wrote:

> Hi Reka,
>
> I removed nginx extension source from Private PaaS repository to be added
> to Stratos 4.1.x branch [1]. This is to make sure that we do not release
> nginx extension with Private PaaS 4.1.0-Beta/GA rather it to be taken from
> corresponding Stratos release.
>
> Would you mind sending these changes to Stratos 4.1.x branch? I did not do
> this because it contains few great improvements you did recently and wanted
> you to commit them.
>
> [1]
> https://github.com/wso2/product-private-paas/commit/1402f40a9199f39ab0fe72f27dfa14f6510be08f
>
> Thanks
>
> --
> *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
>
>


-- 
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Critical issue for IS 5.1.0 Beta

[Chandana Napagoda]

Adding Prassad.
On Oct 5, 2015 6:15 AM, "Chandana Napagoda"  wrote:

> Hi Johan,
>
> I think this is the same issue PrassadT worked on last week. Please verify
> cluster configuration with him.
>
> Regards,
> Chandana
> On Oct 4, 2015 10:17 PM, "Johann Nallathamby"  wrote:
>
>> Hi GReg Team,
>>
>> [1] has been reported by QA while running a load test on IS 5.1.0 Alpha.
>> Looks like this is coming from registry kernel specific code. [2] is the
>> code which executes this from IS side.
>>
>> I think one obvious improvement we can do in [2] is invoke following line
>> IdentityTenantUtil.initializeRegistry(tenantId, tenantDomain);
>> only under tenant condition in line 241. Because we don't need to load
>> super tenant registry right?
>>
>> Can you please look into this problem and let us know if this is a
>> problem in carbon-identity code or registry-kernel code ?
>>
>> [1] https://wso2.org/jira/browse/REGISTRY-3023
>> [2]
>> https://github.com/wso2/carbon-identity/blob/master/components/idp-mgt/org.wso2.carbon.idp.mgt/src/main/java/org/wso2/carbon/idp/mgt/IdentityProviderManager.java#L237-L255
>>
>> --
>> Thanks & Regards,
>>
>> *Johann Dilantha Nallathamby*
>> Technical Lead & Product Lead of WSO2 Identity Server
>> Governance Technologies Team
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - *+9476950*
>> Blog - *http://nallaa.wordpress.com *
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Critical issue for IS 5.1.0 Beta

[Chandana Napagoda]

Hi Johan,

I think this is the same issue PrassadT worked on last week. Please verify
cluster configuration with him.

Regards,
Chandana
On Oct 4, 2015 10:17 PM, "Johann Nallathamby"  wrote:

> Hi GReg Team,
>
> [1] has been reported by QA while running a load test on IS 5.1.0 Alpha.
> Looks like this is coming from registry kernel specific code. [2] is the
> code which executes this from IS side.
>
> I think one obvious improvement we can do in [2] is invoke following line
> IdentityTenantUtil.initializeRegistry(tenantId, tenantDomain);
> only under tenant condition in line 241. Because we don't need to load
> super tenant registry right?
>
> Can you please look into this problem and let us know if this is a problem
> in carbon-identity code or registry-kernel code ?
>
> [1] https://wso2.org/jira/browse/REGISTRY-3023
> [2]
> https://github.com/wso2/carbon-identity/blob/master/components/idp-mgt/org.wso2.carbon.idp.mgt/src/main/java/org/wso2/carbon/idp/mgt/IdentityProviderManager.java#L237-L255
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB-4.9.0]NPE at save configuration

[Ajith Vitharana]

While debugging found that task manager is not initialize. This is due to
outdated configurations. The EIP sample should be updated with following
configuration changes.

1. add  
2. class should be org.apache.synapse.message.processor.*impl*
.forwarder.ScheduledMessageForwardingProcessor
3. target.endpoint parameter is missing in messageProcessor configurations.

[1]
https://docs.wso2.com/display/ESB490/Sample+702%3A+Introduction+to+Message+Forwarding+Processor

 -Ajith

On Sun, Oct 4, 2015 at 3:54 PM, Ajith Vitharana  wrote:

> Hi All,
>
> First I replaced the source view from the configuration [1] and it worked.
> Then I just click on update button. Now each time getting this NPE.
>
> [1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
>
>
> [2015-10-04 15:50:36,869] ERROR - ConfigAdmin Error while updating the
> Synapse configuration
> j*ava.lang.NullPointerException*
> * at
> org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.destroy(ScheduledMessageProcessor.java:309)*
> at
> org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.cleanupCurrentConfiguration(ConfigurationUpdater.java:202)
> at
> org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.update(ConfigurationUpdater.java:130)
> at
> org.wso2.carbon.mediation.configadmin.ConfigAdmin.updateConfiguration(ConfigAdmin.java:150)
> 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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
> at
> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
> at
> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
> at
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
> at
> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
> at
> org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.carbon.mediation.configadmin.stub.ConfigServiceAdminStub.updateConfiguration(ConfigServiceAdminStub.java:1340)
> at
> org.wso2.carbon.mediation.configadmin.ui.ConfigManagementClient.updateConfiguration(ConfigManagementClient.java:98)
> at
> org.apache.jsp.configadmin.saveconfig_jsp._jspService(saveconfig_jsp.java:169)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:604)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:543)
> at
> org.eclipse.equinox.http.servlet.i

[Dev] [ESB-4.9.0]NPE at save configuration

[Ajith Vitharana]

Hi All,

First I replaced the source view from the configuration [1] and it worked.
Then I just click on update button. Now each time getting this NPE.

[1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber


[2015-10-04 15:50:36,869] ERROR - ConfigAdmin Error while updating the
Synapse configuration
j*ava.lang.NullPointerException*
* at
org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.destroy(ScheduledMessageProcessor.java:309)*
at
org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.cleanupCurrentConfiguration(ConfigurationUpdater.java:202)
at
org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.update(ConfigurationUpdater.java:130)
at
org.wso2.carbon.mediation.configadmin.ConfigAdmin.updateConfiguration(ConfigAdmin.java:150)
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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.mediation.configadmin.stub.ConfigServiceAdminStub.updateConfiguration(ConfigServiceAdminStub.java:1340)
at
org.wso2.carbon.mediation.configadmin.ui.ConfigManagementClient.updateConfiguration(ConfigManagementClient.java:98)
at
org.apache.jsp.configadmin.saveconfig_jsp._jspService(saveconfig_jsp.java:169)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:604)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:543)
at
org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
at
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:954)
at
org.apache.jasper.runtime.PageContextImpl.doInclude(PageContextImpl.java:688)
at
org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:682)
at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tiles.jsp.context.JspUtil.doInclude(Jsp

[Dev] [ESB] NPE with EIP guide sample.

[Ajith Vitharana]

Hi All

I did a slight change to sample [1] (used  instead of  at the
outSequence) , now I'm getting following exception.

[1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber



[2015-10-04 15:19:30,891] DEBUG - wire << "[\r][\n]"
[2015-10-04 15:19:30,892] ERROR - PassThroughHttpSender Failed to submit
the response
j*ava.lang.NullPointerException*
* at
org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64)*
* at
org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:462)*
* at
org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:267)*
* at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)*
at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:444)
at
org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:102)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:297)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[2015-10-04 15:19:30,894] ERROR - Axis2Sender
Content-Type:application/soap+xml; charset=UTF-8;
action="urn:getQuoteResponse",http://www.w3.org/2003/05/soap-envelope";>
Unexpected error sending message back
org.apache.axis2.AxisFault: Failed to submit the response
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.handleException(PassThroughHttpSender.java:610)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:269)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:444)
at
org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:102)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:297)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
*Caused by: java.lang.NullPointerException*
* at
org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64)*
* at
org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:462)*
* at
org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:267)*
* ... 16 more*
[2015-10-04 15:19:30,898]  INFO - LogMediator To:
http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: ,
MessageID: urn:uuid:4acfe16a-ee7d-4ab6-b35b-f0e3946160c9, Direction:
response, MESSAGE = Executing default "fault" sequence, ERROR_CODE = 0,
ERROR_MESSAGE = Content-Type:application/soap+xml; charset=UTF-8;
action="urn:getQuoteResponse",http://www.w3.org/2003/05/soap-envelope";>
Unexpected error sending message back, Envelope: http://www.w3.org/2003/05/soap-envelope";>http://services.samples";>http://services.samples/xsd"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance";
xsi:type="ax21:GetQuoteResponse">-2.320226667754610612.650295806384626-152.04270426044403154.1916889021466Sun
Oct 04 15:19:30 EDT
2

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

[Imesh Gunaratne]

It looks good Akila!

On Mon, Oct 5, 2015 at 12:01 AM, Akila Ravihansa Perera 
wrote:

> Hi,
>
> I've restructured the repo considering what we discussed here. I've also
> added a distribution for VM related files.
>
> Final directory structure as follows;
>
> ├── common
> │   ├── configurator
> │   │   ├── live-test
> │   │   │   ├── src
> │   │   ├── src
> │   │   │   ├── assembly
> │   │   │   └── main
> │   ├── docker
> │   │   ├── base-image
> │   │   │   ├── packages
> │   │   │   └── scripts
> │   │   └── scripts
> │   ├── plugins
> │   └── vm
> │   ├── assembly
> │   ├── init-scripts
> │   │   ├── ec2
> │   │   ├── gce
> │   │   ├── openstack
> │   │   └── vcloud
> │   ├── puppet
> │   │   ├── manifests
> │   │   └── modules
> ├── wso2am
> │   ├── 1.9.0
> │   │   ├── assembly
> │   │   ├── docker
> │   │   │   ├── packages
> │   │   │   ├── plugins
> │   │   │   └── scripts
> │   │   ├── plugins
> │   │   ├── samples
> │   │   │   ├── application-policies
> │   │   │   ├── applications
> │   │   │   ├── autoscaling-policies
> │   │   │   ├── cartridge-groups
> │   │   │   ├── cartridges
> │   │   │   ├── deployment-policies
> │   │   │   ├── kubernetes-clusters
> │   │   │   ├── network-partitions
> │   │   │   └── template-modules
> │   │   └── template-module
> │   │   ├── files
> │   │   ├── src
> │   │   └── templates
> ├── wso2as
> │   ├── 5.2.1
> │   │   ├── assembly
> │   │   ├── docker
> │   │   │   ├── packages
> │   │   │   ├── plugins
> │   │   │   └── scripts
> │   │   ├── plugins
> │   │   ├── samples
> │   │   │   ├── application-policies
> │   │   │   ├── applications
> │   │   │   ├── autoscaling-policies
> │   │   │   ├── cartridge-groups
> │   │   │   ├── cartridges
> │   │   │   ├── deployment-policies
> │   │   │   ├── kubernetes-clusters
> │   │   │   ├── network-partitions
> │   │   │   ├── signups
> │   │   │   └── template-modules
> │   │   └── template-module
> │   │   ├── files
> │   │   ├── src
> │   │   └── templates
> ├── wso2esb
> │   ├── 4.8.1
> │   │   ├── assembly
> │   │   ├── docker
> │   │   │   ├── packages
> │   │   │   ├── plugins
> │   │   │   └── scripts
> │   │   ├── plugins
> │   │   ├── samples
> │   │   │   ├── application-policies
> │   │   │   ├── applications
> │   │   │   ├── autoscaling-policies
> │   │   │   ├── cartridge-groups
> │   │   │   ├── cartridges
> │   │   │   ├── deployment-policies
> │   │   │   ├── kubernetes-clusters
> │   │   │   ├── network-partitions
> │   │   │   ├── signups
> │   │   │   └── template-modules
> │   │   │   ├── archive-tmp
> │   │   │   └── maven-shared-archive-resources
> │   │   └── template-module
> │   │   ├── files
> │   │   ├── src
> │   │   └── templates
> └── wso2is
> ├── 5.0.0
> │   ├── assembly
> │   ├── docker
> │   │   ├── packages
> │   │   ├── plugins
> │   │   └── scripts
> │   ├── plugins
> │   ├── samples
> │   │   ├── application-policies
> │   │   ├── applications
> │   │   ├── autoscaling-policies
> │   │   ├── cartridge-groups
> │   │   ├── cartridges
> │   │   ├── deployment-policies
> │   │   ├── kubernetes-clusters
> │   │   ├── network-partitions
> │   │   ├── signups
> │   │   └── template-modules
> │   └── template-module
> │   ├── files
> │   ├── src
> │   └── templates
>
>
> On Sun, Oct 4, 2015 at 10:04 PM, Imesh Gunaratne  wrote:
>
>> On Fri, Oct 2, 2015 at 2:25 PM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> We have folder for base-image and inside that we have a folder called
>>> 'docker' for docker base image. In the VM scenario, we are using
>>> init-scripts to create the vm base image. So what if we move the
>>> init-scripts folder inside /common/base-image/vm/ path?
>>>
>>
>> Yes, a good point! May be we can do the necessary changes.
>>
>> Thanks
>>
>> On Fri, Oct 2, 2015 at 2:25 PM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> We have folder for base-image and inside that we have a folder called
>>> 'docker' for docker base image. In the VM scenario, we are using
>>> init-scripts to create the vm base image. So what if we move the
>>> init-scripts folder inside /common/base-image/vm/ path?
>>>
>>> ├── common
>>> │   ├── base-image
>>> │   │   └── docker
>>> │   ├── common-plugins
>>> │   │   ├── wso2-cleanup-handler.py
>>> │   │   └── wso2-cleanup-handler.yapsy-plugin
>>> │   ├── configurator
>>> │   │   ├── live-test
>>> │   │   ├── org.wso2.ppaas.cartridges.common.configurator.iml
>>> │   │   ├── pom.xml
>>> │   │   ├── README.md
>>> │   │   ├── src
>>> │   │   └── target
>>> │   ├── init-scripts
>>> │   │   ├── ec2
>>> │   │   ├── gce
>>> │   │   ├── openstack
>>> │   │   ├── README.md
>>> │   │   └── vcloud
>>>
>>> Thanks.
>>>
>>> On Thu, Oct 1, 2015 at 6:32 PM, Reka Thirunavukkarasu 
>>> wrote:
>>>
 Hi Gayan

 On T

[Dev] [Private PaaS] Moving Nginx Extension Changes Upstream

[Imesh Gunaratne]

Hi Reka,

I removed nginx extension source from Private PaaS repository to be added
to Stratos 4.1.x branch [1]. This is to make sure that we do not release
nginx extension with Private PaaS 4.1.0-Beta/GA rather it to be taken from
corresponding Stratos release.

Would you mind sending these changes to Stratos 4.1.x branch? I did not do
this because it contains few great improvements you did recently and wanted
you to commit them.

[1]
https://github.com/wso2/product-private-paas/commit/1402f40a9199f39ab0fe72f27dfa14f6510be08f

Thanks

-- 
*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] [PPaaS] private-paas-cartridges repository structure

[Akila Ravihansa Perera]

Hi,

I've restructured the repo considering what we discussed here. I've also
added a distribution for VM related files.

Final directory structure as follows;

├── common
│   ├── configurator
│   │   ├── live-test
│   │   │   ├── src
│   │   ├── src
│   │   │   ├── assembly
│   │   │   └── main
│   ├── docker
│   │   ├── base-image
│   │   │   ├── packages
│   │   │   └── scripts
│   │   └── scripts
│   ├── plugins
│   └── vm
│   ├── assembly
│   ├── init-scripts
│   │   ├── ec2
│   │   ├── gce
│   │   ├── openstack
│   │   └── vcloud
│   ├── puppet
│   │   ├── manifests
│   │   └── modules
├── wso2am
│   ├── 1.9.0
│   │   ├── assembly
│   │   ├── docker
│   │   │   ├── packages
│   │   │   ├── plugins
│   │   │   └── scripts
│   │   ├── plugins
│   │   ├── samples
│   │   │   ├── application-policies
│   │   │   ├── applications
│   │   │   ├── autoscaling-policies
│   │   │   ├── cartridge-groups
│   │   │   ├── cartridges
│   │   │   ├── deployment-policies
│   │   │   ├── kubernetes-clusters
│   │   │   ├── network-partitions
│   │   │   └── template-modules
│   │   └── template-module
│   │   ├── files
│   │   ├── src
│   │   └── templates
├── wso2as
│   ├── 5.2.1
│   │   ├── assembly
│   │   ├── docker
│   │   │   ├── packages
│   │   │   ├── plugins
│   │   │   └── scripts
│   │   ├── plugins
│   │   ├── samples
│   │   │   ├── application-policies
│   │   │   ├── applications
│   │   │   ├── autoscaling-policies
│   │   │   ├── cartridge-groups
│   │   │   ├── cartridges
│   │   │   ├── deployment-policies
│   │   │   ├── kubernetes-clusters
│   │   │   ├── network-partitions
│   │   │   ├── signups
│   │   │   └── template-modules
│   │   └── template-module
│   │   ├── files
│   │   ├── src
│   │   └── templates
├── wso2esb
│   ├── 4.8.1
│   │   ├── assembly
│   │   ├── docker
│   │   │   ├── packages
│   │   │   ├── plugins
│   │   │   └── scripts
│   │   ├── plugins
│   │   ├── samples
│   │   │   ├── application-policies
│   │   │   ├── applications
│   │   │   ├── autoscaling-policies
│   │   │   ├── cartridge-groups
│   │   │   ├── cartridges
│   │   │   ├── deployment-policies
│   │   │   ├── kubernetes-clusters
│   │   │   ├── network-partitions
│   │   │   ├── signups
│   │   │   └── template-modules
│   │   │   ├── archive-tmp
│   │   │   └── maven-shared-archive-resources
│   │   └── template-module
│   │   ├── files
│   │   ├── src
│   │   └── templates
└── wso2is
├── 5.0.0
│   ├── assembly
│   ├── docker
│   │   ├── packages
│   │   ├── plugins
│   │   └── scripts
│   ├── plugins
│   ├── samples
│   │   ├── application-policies
│   │   ├── applications
│   │   ├── autoscaling-policies
│   │   ├── cartridge-groups
│   │   ├── cartridges
│   │   ├── deployment-policies
│   │   ├── kubernetes-clusters
│   │   ├── network-partitions
│   │   ├── signups
│   │   └── template-modules
│   └── template-module
│   ├── files
│   ├── src
│   └── templates


On Sun, Oct 4, 2015 at 10:04 PM, Imesh Gunaratne  wrote:

> On Fri, Oct 2, 2015 at 2:25 PM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Hi All,
>>
>> We have folder for base-image and inside that we have a folder called
>> 'docker' for docker base image. In the VM scenario, we are using
>> init-scripts to create the vm base image. So what if we move the
>> init-scripts folder inside /common/base-image/vm/ path?
>>
>
> Yes, a good point! May be we can do the necessary changes.
>
> Thanks
>
> On Fri, Oct 2, 2015 at 2:25 PM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Hi All,
>>
>> We have folder for base-image and inside that we have a folder called
>> 'docker' for docker base image. In the VM scenario, we are using
>> init-scripts to create the vm base image. So what if we move the
>> init-scripts folder inside /common/base-image/vm/ path?
>>
>> ├── common
>> │   ├── base-image
>> │   │   └── docker
>> │   ├── common-plugins
>> │   │   ├── wso2-cleanup-handler.py
>> │   │   └── wso2-cleanup-handler.yapsy-plugin
>> │   ├── configurator
>> │   │   ├── live-test
>> │   │   ├── org.wso2.ppaas.cartridges.common.configurator.iml
>> │   │   ├── pom.xml
>> │   │   ├── README.md
>> │   │   ├── src
>> │   │   └── target
>> │   ├── init-scripts
>> │   │   ├── ec2
>> │   │   ├── gce
>> │   │   ├── openstack
>> │   │   ├── README.md
>> │   │   └── vcloud
>>
>> Thanks.
>>
>> On Thu, Oct 1, 2015 at 6:32 PM, Reka Thirunavukkarasu 
>> wrote:
>>
>>> Hi Gayan
>>>
>>> On Thu, Oct 1, 2015 at 6:16 PM, Gayan Gunarathne 
>>> wrote:
>>>


 On Thu, Oct 1, 2015 at 6:06 PM, Reka Thirunavukkarasu 
 wrote:

> Hi
>
> Shall we maintain an installer as well(specially for VM cartridges) in
> this repository to quickly create specific cartridges in puppet? What this
> installer could do is,
>
> User has to provide the pa

[Dev] Critical issue for IS 5.1.0 Beta

[Johann Nallathamby]

Hi GReg Team,

[1] has been reported by QA while running a load test on IS 5.1.0 Alpha.
Looks like this is coming from registry kernel specific code. [2] is the
code which executes this from IS side.

I think one obvious improvement we can do in [2] is invoke following line
IdentityTenantUtil.initializeRegistry(tenantId, tenantDomain);
only under tenant condition in line 241. Because we don't need to load
super tenant registry right?

Can you please look into this problem and let us know if this is a problem
in carbon-identity code or registry-kernel code ?

[1] https://wso2.org/jira/browse/REGISTRY-3023
[2]
https://github.com/wso2/carbon-identity/blob/master/components/idp-mgt/org.wso2.carbon.idp.mgt/src/main/java/org/wso2/carbon/idp/mgt/IdentityProviderManager.java#L237-L255

-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

[Imesh Gunaratne]

On Fri, Oct 2, 2015 at 2:25 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi All,
>
> We have folder for base-image and inside that we have a folder called
> 'docker' for docker base image. In the VM scenario, we are using
> init-scripts to create the vm base image. So what if we move the
> init-scripts folder inside /common/base-image/vm/ path?
>

Yes, a good point! May be we can do the necessary changes.

Thanks

On Fri, Oct 2, 2015 at 2:25 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi All,
>
> We have folder for base-image and inside that we have a folder called
> 'docker' for docker base image. In the VM scenario, we are using
> init-scripts to create the vm base image. So what if we move the
> init-scripts folder inside /common/base-image/vm/ path?
>
> ├── common
> │   ├── base-image
> │   │   └── docker
> │   ├── common-plugins
> │   │   ├── wso2-cleanup-handler.py
> │   │   └── wso2-cleanup-handler.yapsy-plugin
> │   ├── configurator
> │   │   ├── live-test
> │   │   ├── org.wso2.ppaas.cartridges.common.configurator.iml
> │   │   ├── pom.xml
> │   │   ├── README.md
> │   │   ├── src
> │   │   └── target
> │   ├── init-scripts
> │   │   ├── ec2
> │   │   ├── gce
> │   │   ├── openstack
> │   │   ├── README.md
> │   │   └── vcloud
>
> Thanks.
>
> On Thu, Oct 1, 2015 at 6:32 PM, Reka Thirunavukkarasu 
> wrote:
>
>> Hi Gayan
>>
>> On Thu, Oct 1, 2015 at 6:16 PM, Gayan Gunarathne  wrote:
>>
>>>
>>>
>>> On Thu, Oct 1, 2015 at 6:06 PM, Reka Thirunavukkarasu 
>>> wrote:
>>>
 Hi

 Shall we maintain an installer as well(specially for VM cartridges) in
 this repository to quickly create specific cartridges in puppet? What this
 installer could do is,

 User has to provide the packs and set of values for the environment
 variables.

 - Install puppet master
 - Locate the relevant cartridges puppet modules
 - Place the packs, template modules and plugins to right location
 - Export all the user given environment variables
 - Execute configurator to configure the samples

 WDYT?

>>>
>>> Good thought reka. As our offline chat , we can plan to have two
>>> installers for ppaas and ppaas cartridges.We can have the ppaas installer
>>> to set up the ppaas related stuff while ppaas cartridge installer to set up
>>> the cartridge specific installations.
>>>
>> +1. We can check whether we can modify the stratos-installer and use it
>> as a ppaas-installer rather writing it from the scratch.
>>
>> Thanks,
>> Reka
>>
>>>
 Thanks,
 Reka

 On Thu, Oct 1, 2015 at 2:01 PM, Gayan Gunarathne 
 wrote:

> Hi Akila,
>
> Common folder has all the common stuff related to the cartridges.So if
> someone can navigate to the common folder and get the stuff shared among
> the cartridges.
>
> I think it is meaningful to have those common stuff at a one place,
> then someone new to this repository also have a feeling those stuff will 
> be
> common for all the cartridges.Common PCA plugins and utils also we can 
> have
> inside the common folder
>
> Thanks,
> Gayan
>
> On Thu, Oct 1, 2015 at 12:52 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Gayan,
>>
>> Wouldn't it be easier to navigate if we move those common folders to
>> root folder?
>>
>> We can create a common folder under /plugins/ folder to keep common
>> PCA plugins and util files.
>>
>> Just a thought...wdyt?
>>
>> Thanks.
>>
>> On Thu, Oct 1, 2015 at 10:29 AM, Gayan Gunarathne 
>> wrote:
>>
>>> Adding to the Dev list
>>>
>>>
>>> On Thu, Oct 1, 2015 at 7:05 AM, Imesh Gunaratne 
>>> wrote:
>>>
 Shall we move this discussion to Dev?

 Thanks

 On Wed, Sep 30, 2015 at 11:02 PM, Gayan Gunarathne >>> > wrote:

> As puppet,init-scripts,base image are common for all the
> cartridges,shall we group them under common?
> Also what about the configurator?I can see two options
> One option will be move the configurator to the private-paas
> repository and release it with the private paas.Other option will be 
> we can
> do the separate release for the configurator.Seems it is better to 
> have a
> separate release for the configurator. WDYT?
>
> Thanks,
> Gayan
>
> On Wed, Sep 30, 2015 at 10:44 PM, Gayan Gunarathne <
> gay...@wso2.com> wrote:
>
>> Hi,
>>
>> On Wed, Sep 30, 2015 at 9:48 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> +1 for having a simple folder structure. I think we can move the
>>> contents in /common/ folder to root folder. One can easily identify 
>>> the
>>> important files available and easy to n

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

[Imesh Gunaratne]

On Thu, Oct 1, 2015 at 6:06 PM, Reka Thirunavukkarasu  wrote:

> Hi
>
> Shall we maintain an installer as well (specially for VM cartridges) in
> this repository to quickly create specific cartridges in puppet?
>

+1

On Thu, Oct 1, 2015 at 6:14 PM, Akila Ravihansa Perera 
 wrote:
>
>
> I'm looking into creating a single set of templates using Jinja template
> language to cater for all IaaS requirements. We can maintain separate set
> of module.ini files to create artifacts for different IaaS's.
>

+1 My initial thought was to make the existing set of files in the samples
folder, Jinja2 templates. If so we don't need to maintain another set of
the same file set as the templates.

On Thu, Oct 1, 2015 at 6:16 PM, Gayan Gunarathne  wrote:
>
>
> Good thought reka. As our offline chat , we can plan to have two
> installers for ppaas and ppaas cartridges.We can have the ppaas installer
> to set up the ppaas related stuff while ppaas cartridge installer to set up
> the cartridge specific installations.
>

Would it be difficult to handle this using a single installer? IMO having
two installers would confuse the users and add more overhead to the
installation process.

May be we can introduce a separate installer for the cartridges (assuming
that there could be cartridge specific requirements to be added to the
installer) and integrate it with the private paas installer. This would
nicely decouple cartridge installation steps from the private paas
installer and at the same time give a better user experience. WDYT?

Thanks

-- 
*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] SSLPeerUnverifiedException: SSL peer failed hostname validation

[Charitha Goonetilleke]

Hi Manu & Darshana,

Thank you so much for your help. Now we fixed it with manu's guidelines.

On Sun, Oct 4, 2015 at 7:06 PM, Manuranga Perera  wrote:

> it is taking from server's local IP. please use host name instead
>
> var CarbonUtils = Packages.org.wso2.carbon.utils.CarbonUtils;
> var localHost =
> CarbonUtils.getServerConfiguration().getFirstProperty("HostName");
>
> On Sun, Oct 4, 2015 at 7:05 PM, Darshana Gunawardana 
> wrote:
>
>> Hi Charitha,
>>
>> Have you log the URL as manu requested? ie. what is the value of "
>> carbonHttpsServletTransport"?
>>
>> Thanks,
>>
>> On Sun, Oct 4, 2015 at 6:59 PM, Charitha Goonetilleke > > wrote:
>>
>>> Hi Manu,
>>>
>>> This[1] is the file which you are requested. Btw, please note that we
>>> are still didn't complete re-factoring properly. So code contains both OSGi
>>> calls and JAX-RS calls inside. We are moving all device-management related
>>> services to JAX-RS as a design requirement.
>>>
>>> [1]
>>> https://github.com/wso2-incubator/device-cloud/blob/build-pack/features/iotserver-feature/org.wso2.carbon.device.mgt.iot.feature/src/main/resources/jaggeryapps/store/extensions/app/store-device-type/modules/device.js
>>>
>>>
>>>
>>> On Sun, Oct 4, 2015 at 6:42 PM, Manuranga Perera  wrote:
>>>
 Hi Charitha,
 can you share me the repo location for
 /store/extensions/app/store-device-type/modules/device.js:310
 any way you must be doing a back-end http call from that code line,
 please log the URL. currently it should be an IP. where is it coming from?
 try changing that to localhost.

 On Sun, Oct 4, 2015 at 3:04 PM, Charitha Goonetilleke <
 charit...@wso2.com> wrote:

> Hi Darshana,
>
> +Adding Manu to the conversation
>
> Thanks for the suggestion. I have changed hostname and mgthostname in
> carbon.xml to localhost as you suggested and, checked certificate CN. CN 
> is
> showing as localhost. This time mgt console url appeared as
> https://localhost:9443/carbon/. But when I tried to access store
> extension page/api, it showing the same error as previous. And saying "SSL
> peer failed hostname validation for name: 192.168.122.1" As I understood,
> that issue only affected to store extensions only. It won't affected to
> others like, publisher, other store pages and apis except store 
> extensions.
>
> On Sun, Oct 4, 2015 at 2:37 PM, Darshana Gunawardana <
> darsh...@wso2.com> wrote:
>
>> Hi Charitha,
>>
>> Quoting [1],
>> "A host name verifier ensures the host name in the URL to which the
>> client connects matches the host name in the digital certificate that the
>> server sends back as part of the SSL connection"
>>
>> Here its checking,
>> a: host name in the URL \ endpoint you invoke : "192.168.122.1"
>> b: host name in the digital certificate of the server : refer [2]; if
>> this is a carbon server, localhost is the default value of the 
>> certificate
>> host name
>> and those does not match in your case.
>>
>> So in the code it seems using IP to invoke some endpoint (a).
>>
>> Probably setting hostname\mgthostname (to localhost?) of the
>> carbon.xml would change the endpoint invoke by code. Here we change a to
>> make it same as b.
>>
>> Set other configs(sso-idp-config.xml) to use hostname, and retry.
>> Hopefully now you would not get above issue.
>>
>> [1]
>> http://docs.oracle.com/cd/E13222_01/wls/docs100/ConsoleHelp/taskhelp/security/VerifyHostNameVerification.html
>>
>> [2] Follow : https://support.google.com/chrome/answer/95617?hl=en
>>Goto Connection tab, click on Certificate Information, Check
>> the value of CN
>>
>> Thanks,
>> Darshana
>>
>> On Sun, Oct 4, 2015 at 1:55 PM, Charitha Goonetilleke <
>> charit...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I'm working on IoTServer product development and using
>>> IS authenticationendpoint for SSO. This is the sso-idp-config.xml I 
>>> used.
>>>
>>> 
>>> 
>>> https://stratos-local.wso2.com/carbon/tenant-register/select_domain.jsp
>>> 
>>> 
>>> 
>>> store
>>>
>>> 
>>> https://localhost:9443/store/acs
>>> 
>>> 
>>> https://localhost:9443/store/acs
>>> 
>>> true
>>> /store/login.jag
>>> 
>>> 
>>> social
>>>
>>> 
>>> https://localhost:9443/social/acs
>>> 
>>> 
>>> https://localhost:9443/social/acs
>>> 
>>> 
>>> https://localhost:9443/social/acs
>>> true
>>> /social/login
>>> 
>>> 
>>> publisher
>>>
>>> 
>>> https://localhost:9443/publisher/acs
>>> 
>>> 
>>> https://localhost:9443/publ

Re: [Dev] SSLPeerUnverifiedException: SSL peer failed hostname validation

[Manuranga Perera]

it is taking from server's local IP. please use host name instead

var CarbonUtils = Packages.org.wso2.carbon.utils.CarbonUtils;
var localHost =
CarbonUtils.getServerConfiguration().getFirstProperty("HostName");

On Sun, Oct 4, 2015 at 7:05 PM, Darshana Gunawardana 
wrote:

> Hi Charitha,
>
> Have you log the URL as manu requested? ie. what is the value of "
> carbonHttpsServletTransport"?
>
> Thanks,
>
> On Sun, Oct 4, 2015 at 6:59 PM, Charitha Goonetilleke 
> wrote:
>
>> Hi Manu,
>>
>> This[1] is the file which you are requested. Btw, please note that we are
>> still didn't complete re-factoring properly. So code contains both OSGi
>> calls and JAX-RS calls inside. We are moving all device-management related
>> services to JAX-RS as a design requirement.
>>
>> [1]
>> https://github.com/wso2-incubator/device-cloud/blob/build-pack/features/iotserver-feature/org.wso2.carbon.device.mgt.iot.feature/src/main/resources/jaggeryapps/store/extensions/app/store-device-type/modules/device.js
>>
>>
>>
>> On Sun, Oct 4, 2015 at 6:42 PM, Manuranga Perera  wrote:
>>
>>> Hi Charitha,
>>> can you share me the repo location for
>>> /store/extensions/app/store-device-type/modules/device.js:310
>>> any way you must be doing a back-end http call from that code line,
>>> please log the URL. currently it should be an IP. where is it coming from?
>>> try changing that to localhost.
>>>
>>> On Sun, Oct 4, 2015 at 3:04 PM, Charitha Goonetilleke <
>>> charit...@wso2.com> wrote:
>>>
 Hi Darshana,

 +Adding Manu to the conversation

 Thanks for the suggestion. I have changed hostname and mgthostname in
 carbon.xml to localhost as you suggested and, checked certificate CN. CN is
 showing as localhost. This time mgt console url appeared as
 https://localhost:9443/carbon/. But when I tried to access store
 extension page/api, it showing the same error as previous. And saying "SSL
 peer failed hostname validation for name: 192.168.122.1" As I understood,
 that issue only affected to store extensions only. It won't affected to
 others like, publisher, other store pages and apis except store extensions.

 On Sun, Oct 4, 2015 at 2:37 PM, Darshana Gunawardana >>> > wrote:

> Hi Charitha,
>
> Quoting [1],
> "A host name verifier ensures the host name in the URL to which the
> client connects matches the host name in the digital certificate that the
> server sends back as part of the SSL connection"
>
> Here its checking,
> a: host name in the URL \ endpoint you invoke : "192.168.122.1"
> b: host name in the digital certificate of the server : refer [2]; if
> this is a carbon server, localhost is the default value of the certificate
> host name
> and those does not match in your case.
>
> So in the code it seems using IP to invoke some endpoint (a).
>
> Probably setting hostname\mgthostname (to localhost?) of the
> carbon.xml would change the endpoint invoke by code. Here we change a to
> make it same as b.
>
> Set other configs(sso-idp-config.xml) to use hostname, and retry.
> Hopefully now you would not get above issue.
>
> [1]
> http://docs.oracle.com/cd/E13222_01/wls/docs100/ConsoleHelp/taskhelp/security/VerifyHostNameVerification.html
>
> [2] Follow : https://support.google.com/chrome/answer/95617?hl=en
>Goto Connection tab, click on Certificate Information, Check
> the value of CN
>
> Thanks,
> Darshana
>
> On Sun, Oct 4, 2015 at 1:55 PM, Charitha Goonetilleke <
> charit...@wso2.com> wrote:
>
>> Hi all,
>>
>> I'm working on IoTServer product development and using
>> IS authenticationendpoint for SSO. This is the sso-idp-config.xml I used.
>>
>> 
>> 
>> https://stratos-local.wso2.com/carbon/tenant-register/select_domain.jsp
>> 
>> 
>> 
>> store
>>
>> 
>> https://localhost:9443/store/acs
>> 
>> 
>> https://localhost:9443/store/acs
>> true
>> /store/login.jag
>> 
>> 
>> social
>>
>> 
>> https://localhost:9443/social/acs
>> 
>> 
>> https://localhost:9443/social/acs
>> 
>> 
>> https://localhost:9443/social/acs
>> true
>> /social/login
>> 
>> 
>> publisher
>>
>> 
>> https://localhost:9443/publisher/acs
>> 
>> 
>> https://localhost:9443/publisher/acs
>> 
>> 
>> https://localhost:9443/publisher/acs
>> true
>>
>> /publisher/controllers/login.jag
>> 
>> 
>> 
>>
>>
>> I can login in to store in IoTServer without any issue, but when I
>> tried to access extension pages, which secured, following exception
>

Re: [Dev] SSLPeerUnverifiedException: SSL peer failed hostname validation

[Darshana Gunawardana]

Hi Charitha,

Have you log the URL as manu requested? ie. what is the value of "
carbonHttpsServletTransport"?

Thanks,

On Sun, Oct 4, 2015 at 6:59 PM, Charitha Goonetilleke 
wrote:

> Hi Manu,
>
> This[1] is the file which you are requested. Btw, please note that we are
> still didn't complete re-factoring properly. So code contains both OSGi
> calls and JAX-RS calls inside. We are moving all device-management related
> services to JAX-RS as a design requirement.
>
> [1]
> https://github.com/wso2-incubator/device-cloud/blob/build-pack/features/iotserver-feature/org.wso2.carbon.device.mgt.iot.feature/src/main/resources/jaggeryapps/store/extensions/app/store-device-type/modules/device.js
>
>
>
> On Sun, Oct 4, 2015 at 6:42 PM, Manuranga Perera  wrote:
>
>> Hi Charitha,
>> can you share me the repo location for
>> /store/extensions/app/store-device-type/modules/device.js:310
>> any way you must be doing a back-end http call from that code line,
>> please log the URL. currently it should be an IP. where is it coming from?
>> try changing that to localhost.
>>
>> On Sun, Oct 4, 2015 at 3:04 PM, Charitha Goonetilleke > > wrote:
>>
>>> Hi Darshana,
>>>
>>> +Adding Manu to the conversation
>>>
>>> Thanks for the suggestion. I have changed hostname and mgthostname in
>>> carbon.xml to localhost as you suggested and, checked certificate CN. CN is
>>> showing as localhost. This time mgt console url appeared as
>>> https://localhost:9443/carbon/. But when I tried to access store
>>> extension page/api, it showing the same error as previous. And saying "SSL
>>> peer failed hostname validation for name: 192.168.122.1" As I understood,
>>> that issue only affected to store extensions only. It won't affected to
>>> others like, publisher, other store pages and apis except store extensions.
>>>
>>> On Sun, Oct 4, 2015 at 2:37 PM, Darshana Gunawardana 
>>> wrote:
>>>
 Hi Charitha,

 Quoting [1],
 "A host name verifier ensures the host name in the URL to which the
 client connects matches the host name in the digital certificate that the
 server sends back as part of the SSL connection"

 Here its checking,
 a: host name in the URL \ endpoint you invoke : "192.168.122.1"
 b: host name in the digital certificate of the server : refer [2]; if
 this is a carbon server, localhost is the default value of the certificate
 host name
 and those does not match in your case.

 So in the code it seems using IP to invoke some endpoint (a).

 Probably setting hostname\mgthostname (to localhost?) of the carbon.xml
 would change the endpoint invoke by code. Here we change a to make it same
 as b.

 Set other configs(sso-idp-config.xml) to use hostname, and retry.
 Hopefully now you would not get above issue.

 [1]
 http://docs.oracle.com/cd/E13222_01/wls/docs100/ConsoleHelp/taskhelp/security/VerifyHostNameVerification.html

 [2] Follow : https://support.google.com/chrome/answer/95617?hl=en
Goto Connection tab, click on Certificate Information, Check the
 value of CN

 Thanks,
 Darshana

 On Sun, Oct 4, 2015 at 1:55 PM, Charitha Goonetilleke <
 charit...@wso2.com> wrote:

> Hi all,
>
> I'm working on IoTServer product development and using
> IS authenticationendpoint for SSO. This is the sso-idp-config.xml I used.
>
> 
> 
> https://stratos-local.wso2.com/carbon/tenant-register/select_domain.jsp
> 
> 
> 
> store
> 
> https://localhost:9443/store/acs
> 
> 
> https://localhost:9443/store/acs
> true
> /store/login.jag
> 
> 
> social
> 
> https://localhost:9443/social/acs
> 
> 
> https://localhost:9443/social/acs
> 
> https://localhost:9443/social/acs
> true
> /social/login
> 
> 
> publisher
> 
> https://localhost:9443/publisher/acs
> 
> 
> https://localhost:9443/publisher/acs
> 
> 
> https://localhost:9443/publisher/acs
> true
>
> /publisher/controllers/login.jag
> 
> 
> 
>
>
> I can login in to store in IoTServer without any issue, but when I
> tried to access extension pages, which secured, following exception
> occurred. In my laptop, I have virtual network adapter which has
> 192.168.122.1 as IP address. Usually, carbon server always stating with
> binned to that address and other products functioning without any issue
> with it. Also same issue is occurred to Ayyoob and Raskia, even they don't
> have such virtual IP. And they have faced this issue with their WLAN IP.
>
>
> [2015-10-04 13:41:48,852] ERROR
>

Re: [Dev] Please merge the PR

[Sajith Abeywardhana]

Yes. rpc library inherited from the feature as Manu said. The problem was
not in the rpc library. It was in with the carbon-dashboard version which
we include in the UES release. Current carbon-dashboard version
is 1.5.0.SNAPSHOT but in my product-ues pom file it was 1.4.0. Also in the
product-ues GitHub, it is mentioned as*
1.0.4 *but in the
carbon-dashboard pom file it is
*1.0.5-SNAPSHOT*
 Shouldn't we sync those two versions?

Dashboard json file slightly changes in carbon-dashboard version 1.4.0 and
carbon-dashboard version 1.5.0. SNAPSHOT. That was the root cause for this
issue. I fixed the code according to the new version.

@Sameera,
I commit the changes and please review and marge below PRs.
 https://github.com/wso2/carbon-dashboards/pull/53 for
https://wso2.org/jira/browse/UES-585
 https://github.com/wso2/carbon-dashboards/pull/54 for
https://wso2.org/jira/browse/UES-573

@Ayesha,
Please review and merge https://github.com/wso2/carbon-dashboards/pull/60
 for https://wso2.org/jira/browse/UES-595




*Sajith Abeywardhana* | Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka.
Mobile: +94772260485
Email: saji...@wso2.com | Web: www.wso2.com

On Sat, Oct 3, 2015 at 10:09 PM, Manuranga Perera  wrote:

> the rpc library should come automatically whit with Feature tag for set
> pref. no need to include it manually.
>
> On Fri, Oct 2, 2015 at 7:36 PM, Sajith Abeywardhana 
> wrote:
>
>> Hi Sameera,
>>
>> On Wed, Sep 30, 2015 at 1:12 PM, Sajith Abeywardhana 
>> wrote:
>>
>>> Please review and merge
>>> https://github.com/wso2/carbon-dashboards/pull/53 for
>>> https://wso2.org/jira/browse/UES-585
>>>
>>> For this we need to have rpc.js as a library. When I was testing it I
>> directly included it to the index.xml as  *> src="http://sandbox.ig.gmodules.com/gadgets/js/rpc.js
>> <http://sandbox.ig.gmodules.com/gadgets/js/rpc.js>">.* But when
>> you were trying, we didn't include that rpc library. That was the reason
>> for the conflict.
>> Now I have changed the designer.js to loads the rpc library along with UI
>> initialization(This is the time set_pref get registered) and I added rcp.js
>> to the portal/js/ folder.
>> Please let me know If you have any concerns.
>>
>> *Sajith Abeywardhana* | Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka.
>> Mobile: +94772260485
>> Email: saji...@wso2.com | Web: www.wso2.com
>>
>>
>>
>>
>>>
>>> *Sajith Abeywardhana* | Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka.
>>> Mobile: +94772260485
>>> Email: saji...@wso2.com | Web: www.wso2.com
>>>
>>
>>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SSLPeerUnverifiedException: SSL peer failed hostname validation

[Charitha Goonetilleke]

Hi Manu,

This[1] is the file which you are requested. Btw, please note that we are
still didn't complete re-factoring properly. So code contains both OSGi
calls and JAX-RS calls inside. We are moving all device-management related
services to JAX-RS as a design requirement.

[1]
https://github.com/wso2-incubator/device-cloud/blob/build-pack/features/iotserver-feature/org.wso2.carbon.device.mgt.iot.feature/src/main/resources/jaggeryapps/store/extensions/app/store-device-type/modules/device.js



On Sun, Oct 4, 2015 at 6:42 PM, Manuranga Perera  wrote:

> Hi Charitha,
> can you share me the repo location for
> /store/extensions/app/store-device-type/modules/device.js:310
> any way you must be doing a back-end http call from that code line, please
> log the URL. currently it should be an IP. where is it coming from?
> try changing that to localhost.
>
> On Sun, Oct 4, 2015 at 3:04 PM, Charitha Goonetilleke 
> wrote:
>
>> Hi Darshana,
>>
>> +Adding Manu to the conversation
>>
>> Thanks for the suggestion. I have changed hostname and mgthostname in
>> carbon.xml to localhost as you suggested and, checked certificate CN. CN is
>> showing as localhost. This time mgt console url appeared as
>> https://localhost:9443/carbon/. But when I tried to access store
>> extension page/api, it showing the same error as previous. And saying "SSL
>> peer failed hostname validation for name: 192.168.122.1" As I understood,
>> that issue only affected to store extensions only. It won't affected to
>> others like, publisher, other store pages and apis except store extensions.
>>
>> On Sun, Oct 4, 2015 at 2:37 PM, Darshana Gunawardana 
>> wrote:
>>
>>> Hi Charitha,
>>>
>>> Quoting [1],
>>> "A host name verifier ensures the host name in the URL to which the
>>> client connects matches the host name in the digital certificate that the
>>> server sends back as part of the SSL connection"
>>>
>>> Here its checking,
>>> a: host name in the URL \ endpoint you invoke : "192.168.122.1"
>>> b: host name in the digital certificate of the server : refer [2]; if
>>> this is a carbon server, localhost is the default value of the certificate
>>> host name
>>> and those does not match in your case.
>>>
>>> So in the code it seems using IP to invoke some endpoint (a).
>>>
>>> Probably setting hostname\mgthostname (to localhost?) of the carbon.xml
>>> would change the endpoint invoke by code. Here we change a to make it same
>>> as b.
>>>
>>> Set other configs(sso-idp-config.xml) to use hostname, and retry.
>>> Hopefully now you would not get above issue.
>>>
>>> [1]
>>> http://docs.oracle.com/cd/E13222_01/wls/docs100/ConsoleHelp/taskhelp/security/VerifyHostNameVerification.html
>>>
>>> [2] Follow : https://support.google.com/chrome/answer/95617?hl=en
>>>Goto Connection tab, click on Certificate Information, Check the
>>> value of CN
>>>
>>> Thanks,
>>> Darshana
>>>
>>> On Sun, Oct 4, 2015 at 1:55 PM, Charitha Goonetilleke <
>>> charit...@wso2.com> wrote:
>>>
 Hi all,

 I'm working on IoTServer product development and using
 IS authenticationendpoint for SSO. This is the sso-idp-config.xml I used.

 
 
 https://stratos-local.wso2.com/carbon/tenant-register/select_domain.jsp
 
 
 
 store
 
 https://localhost:9443/store/acs
 
 
 https://localhost:9443/store/acs
 true
 /store/login.jag
 
 
 social
 
 https://localhost:9443/social/acs
 
 
 https://localhost:9443/social/acs
 https://localhost:9443/social/acs
 
 true
 /social/login
 
 
 publisher
 
 https://localhost:9443/publisher/acs
 
 
 https://localhost:9443/publisher/acs
 
 
 https://localhost:9443/publisher/acs
 true

 /publisher/controllers/login.jag
 
 
 


 I can login in to store in IoTServer without any issue, but when I
 tried to access extension pages, which secured, following exception
 occurred. In my laptop, I have virtual network adapter which has
 192.168.122.1 as IP address. Usually, carbon server always stating with
 binned to that address and other products functioning without any issue
 with it. Also same issue is occurred to Ayyoob and Raskia, even they don't
 have such virtual IP. And they have faced this issue with their WLAN IP.


 [2015-10-04 13:41:48,852] ERROR
 {org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject} -  SSL peer failed
 hostname validation for name: 192.168.122.1
 javax.net.ssl.SSLPeerUnverifiedException: SSL peer failed hostname
 validation for name: 192.168.122.1
 at
 org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.verifyHostname(T

Re: [Dev] SSLPeerUnverifiedException: SSL peer failed hostname validation

[Manuranga Perera]

Hi Charitha,
can you share me the repo location for
/store/extensions/app/store-device-type/modules/device.js:310
any way you must be doing a back-end http call from that code line, please
log the URL. currently it should be an IP. where is it coming from?
try changing that to localhost.

On Sun, Oct 4, 2015 at 3:04 PM, Charitha Goonetilleke 
wrote:

> Hi Darshana,
>
> +Adding Manu to the conversation
>
> Thanks for the suggestion. I have changed hostname and mgthostname in
> carbon.xml to localhost as you suggested and, checked certificate CN. CN is
> showing as localhost. This time mgt console url appeared as
> https://localhost:9443/carbon/. But when I tried to access store
> extension page/api, it showing the same error as previous. And saying "SSL
> peer failed hostname validation for name: 192.168.122.1" As I understood,
> that issue only affected to store extensions only. It won't affected to
> others like, publisher, other store pages and apis except store extensions.
>
> On Sun, Oct 4, 2015 at 2:37 PM, Darshana Gunawardana 
> wrote:
>
>> Hi Charitha,
>>
>> Quoting [1],
>> "A host name verifier ensures the host name in the URL to which the
>> client connects matches the host name in the digital certificate that the
>> server sends back as part of the SSL connection"
>>
>> Here its checking,
>> a: host name in the URL \ endpoint you invoke : "192.168.122.1"
>> b: host name in the digital certificate of the server : refer [2]; if
>> this is a carbon server, localhost is the default value of the certificate
>> host name
>> and those does not match in your case.
>>
>> So in the code it seems using IP to invoke some endpoint (a).
>>
>> Probably setting hostname\mgthostname (to localhost?) of the carbon.xml
>> would change the endpoint invoke by code. Here we change a to make it same
>> as b.
>>
>> Set other configs(sso-idp-config.xml) to use hostname, and retry.
>> Hopefully now you would not get above issue.
>>
>> [1]
>> http://docs.oracle.com/cd/E13222_01/wls/docs100/ConsoleHelp/taskhelp/security/VerifyHostNameVerification.html
>>
>> [2] Follow : https://support.google.com/chrome/answer/95617?hl=en
>>Goto Connection tab, click on Certificate Information, Check the
>> value of CN
>>
>> Thanks,
>> Darshana
>>
>> On Sun, Oct 4, 2015 at 1:55 PM, Charitha Goonetilleke > > wrote:
>>
>>> Hi all,
>>>
>>> I'm working on IoTServer product development and using
>>> IS authenticationendpoint for SSO. This is the sso-idp-config.xml I used.
>>>
>>> 
>>> 
>>> https://stratos-local.wso2.com/carbon/tenant-register/select_domain.jsp
>>> 
>>> 
>>> 
>>> store
>>> 
>>> https://localhost:9443/store/acs
>>> 
>>> 
>>> https://localhost:9443/store/acs
>>> true
>>> /store/login.jag
>>> 
>>> 
>>> social
>>> 
>>> https://localhost:9443/social/acs
>>> 
>>> 
>>> https://localhost:9443/social/acs
>>> https://localhost:9443/social/acs
>>> 
>>> true
>>> /social/login
>>> 
>>> 
>>> publisher
>>> 
>>> https://localhost:9443/publisher/acs
>>> 
>>> 
>>> https://localhost:9443/publisher/acs
>>> 
>>> 
>>> https://localhost:9443/publisher/acs
>>> true
>>>
>>> /publisher/controllers/login.jag
>>> 
>>> 
>>> 
>>>
>>>
>>> I can login in to store in IoTServer without any issue, but when I tried
>>> to access extension pages, which secured, following exception occurred. In
>>> my laptop, I have virtual network adapter which has 192.168.122.1 as IP
>>> address. Usually, carbon server always stating with binned to that address
>>> and other products functioning without any issue with it. Also same issue
>>> is occurred to Ayyoob and Raskia, even they don't have such virtual IP. And
>>> they have faced this issue with their WLAN IP.
>>>
>>>
>>> [2015-10-04 13:41:48,852] ERROR
>>> {org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject} -  SSL peer failed
>>> hostname validation for name: 192.168.122.1
>>> javax.net.ssl.SSLPeerUnverifiedException: SSL peer failed hostname
>>> validation for name: 192.168.122.1
>>> at
>>> org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.verifyHostname(TLSProtocolSocketFactory.java:233)
>>> at
>>> org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.createSocket(TLSProtocolSocketFactory.java:186)
>>> at
>>> org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
>>> at
>>> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
>>> at
>>> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
>>> at
>>> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
>>> at
>>> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
>>> at
>>> org.apache.commons.htt

[Dev] UpdateCredentialByAdmin doesn't support a byte array

[Dulitha Wijewantha]

Hi Johann/Dulanja,
I am using the user store API to update credential of a user. The API seem
to support an object (a byte array) but the implementation gives an error.
Below is a code snippet

byte[] decodedBytes = Base64.decodeBase64(userWrapper.getPassword());
log.info(new String(decodedBytes));
userStoreManager.updateCredentialByAdmin(userWrapper.getUsername(),
decodedBytes);

I can see that the implementation checks if the credential is a String
object [1]. Shouldn't we be using byte arrays to pass around passwords in
the code?

Attached the exact error I got to the end of the email.

[1] -
https://github.com/wso2/carbon-kernel/blob/master/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/AbstractUserStoreManager.java#L3278

Cheers~

*Error stack*

org.wso2.carbon.user.core.UserStoreException: Can handle only string type
credentials
at
org.wso2.carbon.user.core.common.AbstractUserStoreManager.checkUserPasswordValid(AbstractUserStoreManager.java:2799)
at
org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager.doUpdateCredentialByAdmin(JDBCUserStoreManager.java:1949)
at
org.wso2.carbon.user.core.common.AbstractUserStoreManager.updateCredentialByAdmin(AbstractUserStoreManager.java:777)
at org.wso2.carbon.mdm.api.User.updateUser(User.java:174)
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.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
at
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:262)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:613)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
at
org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationHandler.invoke(WebappAuthenticationHandler.java:43)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at
org.apache.catalina.connector.CoyoteAdapter.servi

Re: [Dev] SSLPeerUnverifiedException: SSL peer failed hostname validation

[Charitha Goonetilleke]

Hi Darshana,

+Adding Manu to the conversation

Thanks for the suggestion. I have changed hostname and mgthostname in
carbon.xml to localhost as you suggested and, checked certificate CN. CN is
showing as localhost. This time mgt console url appeared as
https://localhost:9443/carbon/. But when I tried to access store extension
page/api, it showing the same error as previous. And saying "SSL peer
failed hostname validation for name: 192.168.122.1" As I understood, that
issue only affected to store extensions only. It won't affected to others
like, publisher, other store pages and apis except store extensions.

On Sun, Oct 4, 2015 at 2:37 PM, Darshana Gunawardana 
wrote:

> Hi Charitha,
>
> Quoting [1],
> "A host name verifier ensures the host name in the URL to which the client
> connects matches the host name in the digital certificate that the server
> sends back as part of the SSL connection"
>
> Here its checking,
> a: host name in the URL \ endpoint you invoke : "192.168.122.1"
> b: host name in the digital certificate of the server : refer [2]; if this
> is a carbon server, localhost is the default value of the certificate host
> name
> and those does not match in your case.
>
> So in the code it seems using IP to invoke some endpoint (a).
>
> Probably setting hostname\mgthostname (to localhost?) of the carbon.xml
> would change the endpoint invoke by code. Here we change a to make it same
> as b.
>
> Set other configs(sso-idp-config.xml) to use hostname, and retry.
> Hopefully now you would not get above issue.
>
> [1]
> http://docs.oracle.com/cd/E13222_01/wls/docs100/ConsoleHelp/taskhelp/security/VerifyHostNameVerification.html
>
> [2] Follow : https://support.google.com/chrome/answer/95617?hl=en
>Goto Connection tab, click on Certificate Information, Check the
> value of CN
>
> Thanks,
> Darshana
>
> On Sun, Oct 4, 2015 at 1:55 PM, Charitha Goonetilleke 
> wrote:
>
>> Hi all,
>>
>> I'm working on IoTServer product development and using
>> IS authenticationendpoint for SSO. This is the sso-idp-config.xml I used.
>>
>> 
>> 
>> https://stratos-local.wso2.com/carbon/tenant-register/select_domain.jsp
>> 
>> 
>> 
>> store
>> 
>> https://localhost:9443/store/acs
>> 
>> 
>> https://localhost:9443/store/acs
>> true
>> /store/login.jag
>> 
>> 
>> social
>> 
>> https://localhost:9443/social/acs
>> 
>> 
>> https://localhost:9443/social/acs
>> https://localhost:9443/social/acs
>> 
>> true
>> /social/login
>> 
>> 
>> publisher
>> 
>> https://localhost:9443/publisher/acs
>> 
>> 
>> https://localhost:9443/publisher/acs
>> 
>> https://localhost:9443/publisher/acs
>> true
>>
>> /publisher/controllers/login.jag
>> 
>> 
>> 
>>
>>
>> I can login in to store in IoTServer without any issue, but when I tried
>> to access extension pages, which secured, following exception occurred. In
>> my laptop, I have virtual network adapter which has 192.168.122.1 as IP
>> address. Usually, carbon server always stating with binned to that address
>> and other products functioning without any issue with it. Also same issue
>> is occurred to Ayyoob and Raskia, even they don't have such virtual IP. And
>> they have faced this issue with their WLAN IP.
>>
>>
>> [2015-10-04 13:41:48,852] ERROR
>> {org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject} -  SSL peer failed
>> hostname validation for name: 192.168.122.1
>> javax.net.ssl.SSLPeerUnverifiedException: SSL peer failed hostname
>> validation for name: 192.168.122.1
>> at
>> org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.verifyHostname(TLSProtocolSocketFactory.java:233)
>> at
>> org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.createSocket(TLSProtocolSocketFactory.java:186)
>> at
>> org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
>> at
>> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
>> at
>> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
>> at
>> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
>> at
>> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
>> at
>> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
>> at
>> org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.executeRequest(XMLHttpRequestHostObject.java:538)
>> at
>> org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.send(XMLHttpRequestHostObject.java:532)
>> at
>> org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.jsFunction_send(XMLHttpRequestHostObject.java:284)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.in

Re: [Dev] SSLPeerUnverifiedException: SSL peer failed hostname validation

[Darshana Gunawardana]

Hi Charitha,

Quoting [1],
"A host name verifier ensures the host name in the URL to which the client
connects matches the host name in the digital certificate that the server
sends back as part of the SSL connection"

Here its checking,
a: host name in the URL \ endpoint you invoke : "192.168.122.1"
b: host name in the digital certificate of the server : refer [2]; if this
is a carbon server, localhost is the default value of the certificate host
name
and those does not match in your case.

So in the code it seems using IP to invoke some endpoint (a).

Probably setting hostname\mgthostname (to localhost?) of the carbon.xml
would change the endpoint invoke by code. Here we change a to make it same
as b.

Set other configs(sso-idp-config.xml) to use hostname, and retry. Hopefully
now you would not get above issue.

[1]
http://docs.oracle.com/cd/E13222_01/wls/docs100/ConsoleHelp/taskhelp/security/VerifyHostNameVerification.html

[2] Follow : https://support.google.com/chrome/answer/95617?hl=en
   Goto Connection tab, click on Certificate Information, Check the
value of CN

Thanks,
Darshana

On Sun, Oct 4, 2015 at 1:55 PM, Charitha Goonetilleke 
wrote:

> Hi all,
>
> I'm working on IoTServer product development and using
> IS authenticationendpoint for SSO. This is the sso-idp-config.xml I used.
>
> 
> 
> https://stratos-local.wso2.com/carbon/tenant-register/select_domain.jsp
> 
> 
> 
> store
> 
> https://localhost:9443/store/acs
> 
> 
> https://localhost:9443/store/acs
> true
> /store/login.jag
> 
> 
> social
> 
> https://localhost:9443/social/acs
> 
> 
> https://localhost:9443/social/acs
> https://localhost:9443/social/acs
> 
> true
> /social/login
> 
> 
> publisher
> 
> https://localhost:9443/publisher/acs
> 
> 
> https://localhost:9443/publisher/acs
> https://localhost:9443/publisher/acs
> 
> true
>
> /publisher/controllers/login.jag
> 
> 
> 
>
>
> I can login in to store in IoTServer without any issue, but when I tried
> to access extension pages, which secured, following exception occurred. In
> my laptop, I have virtual network adapter which has 192.168.122.1 as IP
> address. Usually, carbon server always stating with binned to that address
> and other products functioning without any issue with it. Also same issue
> is occurred to Ayyoob and Raskia, even they don't have such virtual IP. And
> they have faced this issue with their WLAN IP.
>
>
> [2015-10-04 13:41:48,852] ERROR
> {org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject} -  SSL peer failed
> hostname validation for name: 192.168.122.1
> javax.net.ssl.SSLPeerUnverifiedException: SSL peer failed hostname
> validation for name: 192.168.122.1
> at
> org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.verifyHostname(TLSProtocolSocketFactory.java:233)
> at
> org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.createSocket(TLSProtocolSocketFactory.java:186)
> at
> org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
> at
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
> at
> org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.executeRequest(XMLHttpRequestHostObject.java:538)
> at
> org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.send(XMLHttpRequestHostObject.java:532)
> at
> org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.jsFunction_send(XMLHttpRequestHostObject.java:284)
> 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.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
> at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
> at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
> at
> org.jaggeryjs.rhino.<>.META_INF.scripts.c0._c_anonymous_5(<>/META-INF/scripts/http.js:220)
> at
> org.jaggeryjs.rhino.<>.META_INF.scripts.c0.call(<>/META-INF/scripts/http.js)
> at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
> at
> org.jaggeryjs.rhino.<>.META_INF.scripts.c0._c_anonymous_7(<>/META-INF/scripts/http.js:228)
> at
> org.jaggeryjs.rhino.<>.META_INF.scripts.c0.call(<>/META-INF/scrip

Re: [Dev] SSLPeerUnverifiedException: SSL peer failed hostname validation

[Charitha Goonetilleke]

Hi,

I also tried with following sso-idp-config, but still getting the same
error. This time I tried to access store[1] with my IP address(i.e.
192.168.122.1) instead of localhost. That problem only exist for store
extension pages only even they are not secured. Publisher working fine
without any issue.



https://stratos-local.wso2.com/carbon/tenant-register/select_domain.jsp



store

https://192.168.122.1:9443/store/acs


https://192.168.122.1:9443/store/acs
true
/store/login.jag


social

https://192.168.122.1:9443/social/acs


https://192.168.122.1:9443/social/acs
https://192.168.122.1:9443/social/acs

true
/social/login


publisher

https://192.168.122.1:9443/publisher/acs


https://192.168.122.1:9443/publisher/acs


https://192.168.122.1:9443/publisher/acs
true

/publisher/controllers/login.jag




[1] https://192.168.122.1:9443/store/

On Sun, Oct 4, 2015 at 1:55 PM, Charitha Goonetilleke 
wrote:

> Hi all,
>
> I'm working on IoTServer product development and using
> IS authenticationendpoint for SSO. This is the sso-idp-config.xml I used.
>
> 
> 
> https://stratos-local.wso2.com/carbon/tenant-register/select_domain.jsp
> 
> 
> 
> store
> 
> https://localhost:9443/store/acs
> 
> 
> https://localhost:9443/store/acs
> true
> /store/login.jag
> 
> 
> social
> 
> https://localhost:9443/social/acs
> 
> 
> https://localhost:9443/social/acs
> https://localhost:9443/social/acs
> 
> true
> /social/login
> 
> 
> publisher
> 
> https://localhost:9443/publisher/acs
> 
> 
> https://localhost:9443/publisher/acs
> https://localhost:9443/publisher/acs
> 
> true
>
> /publisher/controllers/login.jag
> 
> 
> 
>
>
> I can login in to store in IoTServer without any issue, but when I tried
> to access extension pages, which secured, following exception occurred. In
> my laptop, I have virtual network adapter which has 192.168.122.1 as IP
> address. Usually, carbon server always stating with binned to that address
> and other products functioning without any issue with it. Also same issue
> is occurred to Ayyoob and Raskia, even they don't have such virtual IP. And
> they have faced this issue with their WLAN IP.
>
>
> [2015-10-04 13:41:48,852] ERROR
> {org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject} -  SSL peer failed
> hostname validation for name: 192.168.122.1
> javax.net.ssl.SSLPeerUnverifiedException: SSL peer failed hostname
> validation for name: 192.168.122.1
> at
> org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.verifyHostname(TLSProtocolSocketFactory.java:233)
> at
> org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.createSocket(TLSProtocolSocketFactory.java:186)
> at
> org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
> at
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
> at
> org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.executeRequest(XMLHttpRequestHostObject.java:538)
> at
> org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.send(XMLHttpRequestHostObject.java:532)
> at
> org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.jsFunction_send(XMLHttpRequestHostObject.java:284)
> 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.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
> at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
> at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
> at
> org.jaggeryjs.rhino.<>.META_INF.scripts.c0._c_anonymous_5(<>/META-INF/scripts/http.js:220)
> at
> org.jaggeryjs.rhino.<>.META_INF.scripts.c0.call(<>/META-INF/scripts/http.js)
> at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
> at
> org.jaggeryjs.rhino.<>.META_INF.scripts.c0._c_anonymous_7(<>/META-INF/scripts/http.js:228)
> at
> org.jaggeryjs.rhino.<>.META_INF.scripts.c0.call(<>/META-INF/scripts

[Dev] SSLPeerUnverifiedException: SSL peer failed hostname validation

[Charitha Goonetilleke]

Hi all,

I'm working on IoTServer product development and using
IS authenticationendpoint for SSO. This is the sso-idp-config.xml I used.



https://stratos-local.wso2.com/carbon/tenant-register/select_domain.jsp



store

https://localhost:9443/store/acs


https://localhost:9443/store/acs
true
/store/login.jag


social

https://localhost:9443/social/acs


https://localhost:9443/social/acs
https://localhost:9443/social/acs

true
/social/login


publisher

https://localhost:9443/publisher/acs


https://localhost:9443/publisher/acs
https://localhost:9443/publisher/acs

true

/publisher/controllers/login.jag





I can login in to store in IoTServer without any issue, but when I tried to
access extension pages, which secured, following exception occurred. In my
laptop, I have virtual network adapter which has 192.168.122.1 as IP
address. Usually, carbon server always stating with binned to that address
and other products functioning without any issue with it. Also same issue
is occurred to Ayyoob and Raskia, even they don't have such virtual IP. And
they have faced this issue with their WLAN IP.


[2015-10-04 13:41:48,852] ERROR
{org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject} -  SSL peer failed
hostname validation for name: 192.168.122.1
javax.net.ssl.SSLPeerUnverifiedException: SSL peer failed hostname
validation for name: 192.168.122.1
at
org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.verifyHostname(TLSProtocolSocketFactory.java:233)
at
org.opensaml.ws.soap.client.http.TLSProtocolSocketFactory.createSocket(TLSProtocolSocketFactory.java:186)
at
org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at
org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.executeRequest(XMLHttpRequestHostObject.java:538)
at
org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.send(XMLHttpRequestHostObject.java:532)
at
org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.jsFunction_send(XMLHttpRequestHostObject.java:284)
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.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.<>.META_INF.scripts.c0._c_anonymous_5(<>/META-INF/scripts/http.js:220)
at
org.jaggeryjs.rhino.<>.META_INF.scripts.c0.call(<>/META-INF/scripts/http.js)
at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
at
org.jaggeryjs.rhino.<>.META_INF.scripts.c0._c_anonymous_7(<>/META-INF/scripts/http.js:228)
at
org.jaggeryjs.rhino.<>.META_INF.scripts.c0.call(<>/META-INF/scripts/http.js)
at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
at
org.jaggeryjs.rhino.store.extensions.app.store_device_type.modules.c0._c_anonymous_15(/store/extensions/app/store-device-type/modules/device.js:310)
at
org.jaggeryjs.rhino.store.extensions.app.store_device_type.modules.c0.call(/store/extensions/app/store-device-type/modules/device.js)
at org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)
at
org.jaggeryjs.rhino.store.extensions.app.store_device_type.modules.c0._c_anonymous_17(/store/extensions/app/store-device-type/modules/device.js:334)
at
org.jaggeryjs.rhino.store.extensions.app.store_device_type.modules.c0.call(/store/extensions/app/store-device-type/modules/device.js)
at org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)
at
org.jaggeryjs.rhino.store.extensions.app.store_device_type.pages.c0._c_anonymous_1(/store/extensions/app/store-device-type/pages/dashboard.jag:31)
at
org.jaggeryjs.rhino.store.extensions.app.store_device_type.pages.c0.call(/store/extensions/app/store-device-type/pages/dashboard.jag)
at org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
at org.mozilla.javascript.optimizer.OptRu

Re: [Dev] [IS] - Unable to decrypt the SAML Assertion When Authenticating to Travelocity app

[Gayan Gunawardana]

Hi Nadeesha,

I just checked Federated SSO scenario  (product-is build 02/10/2015) you
mentioned in the initial mail. It works fine for me except I had to replace
commons-collections-3.1.jar with commons-collections-3.2.1.jar inside
travelocity.com web app.

Thanks,
Gayan

On Fri, Oct 2, 2015 at 9:11 PM, Nadeesha Meegoda  wrote:

> Hi Tharindu,
>
> When I tested this with single IS for SAML SSO (not the federated
> scenario) everything worked fine for super tenant. I doubt this is related
> to the federated scenario. Please have a look and let me know.
>
> Thanks!
>
> On Fri, Oct 2, 2015 at 8:52 PM, Tharindu Edirisinghe 
> wrote:
>
>> Hi Nadeesha,
>>
>> For super tenant, sso.agent should be able to decrypt the encrypted saml
>> assertion. However there was an issue [1] where for a tenant, when the
>> tenant encrypts the SAML assertion from the public certificate of the
>> client (i.e travelocity app), then sso.agent could not decrypt the
>> assertion because in the code, the private key of travelocity's key store
>> was not getting picked up because of the particular method called in open
>> saml library. This was patched sometimes back for sso.agent 1.2 version but
>> we need to check whether the same fix got correctly merged to higher
>> versions (i.e 1.4). Ideally this should anyway work for super tenant, but
>> we'll check the same scenario more and let you know.
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-3186
>>
>> Regards,
>> TharinduE
>>
>> On Fri, Oct 2, 2015 at 3:34 PM, Nadeesha Meegoda 
>> wrote:
>>
>>> Hi Darshana,
>>>
>>> Yes the response is encrypted. Sending the SAML sso trace attached with
>>> the mail.
>>>
>>> @Ishara I used wso2carbon as the certificate alias since I'm using the
>>> default key stores and also I'm testing this in super tenant mode.  Do I
>>> need to import the public certificate of the private key of travelocity app
>>> to IS keystores in super tenant mode?
>>>
>>> On Fri, Oct 2, 2015 at 3:19 PM, Ishara Karunarathna 
>>> wrote:
>>>
 Hi Nadeesha,

 On Fri, Oct 2, 2015 at 3:04 PM, Darshana Gunawardana >>> > wrote:

> Hi Nadeesha,
>
> Have you checked whether the assertion is encrypted in the response IS
> send back to travelocity app?
>
> And please provide the SSO Trace (save as a text file and attach in
> the mail) for the whole flow.
>
> Thanks,
> Darshana
>
> On Fri, Oct 2, 2015 at 2:53 PM, Nadeesha Meegoda 
> wrote:
>
>> Hi.
>>
>> I have configured the setup to Login to the Identity Server Using
>> Another Identity Server as per the details in [1] in Super tenant mode.
>> With the happy scenario according to the documentation this works fine. 
>> But
>> I have enabled some additional properties in IDP and SP used for IDP as
>> following :
>>
>> *Properties enabled for Federated Authenticators* - SAML2 Web SSO
>> Configuration
>>
>> 1. Enabled Assertion Encryption
>> 2. Enable Assertion Signing
>> 3. Enable Authentication Response Signing
>>
>> *Properties enabled fo SP used for IDP *
>>
>> 1. Enabled Assertion Encryption
>> 2. Enabled Response Signing
>>
>> *Properties enabled fo SP used for travelocity app*
>>
>> 1. Enabled Assertion Encryption
>>
> What is the Certificate Alias you used here ?
 is that the public key in travelocity app ?

> 2. Enabled Response Signing
>>
>> In the travelocity.properties file also I have enabled Assertion
>> Encryption,Response signing and Assertion signing. I have already 
>> imported
>> the Identity Provider Public Certificate to IDP
>>
>> When I'm signing in to travelocity.com I get Unable to decrypt the
>> SAML Assertion error and error in [2] in tomcat.
>>
>> Note that only enabling "assertion signing" in IDP I was successfully
>> able to login and no error was displayed. When I enabled the Assertion
>> Encryption this error occurred. Why is this error occurred when I enable
>> this property as mentioned above?
>>
>> Any help regarding this is highly appreciated!
>>
>>
>>
>> [1] -
>> https://docs.wso2.com/pages/viewpage.action?title=Login%2Bto%2Bthe%2BIdentity%2BServer%2BUsing%2BAnother%2BIdentity%2BServer&spaceKey=IS510
>>
>> [2] - Oct 02, 2015 2:10:47 PM
>> org.wso2.carbon.identity.sso.agent.SSOAgentFilter doFilter
>> SEVERE: An error has occurred
>> org.wso2.carbon.identity.sso.agent.exception.SSOAgentException:
>> Unable to decrypt the SAML Assertion
>> at
>> org.wso2.carbon.identity.sso.agent.saml.SAML2SSOManager.processSSOResponse(SAML2SSOManager.java:254)
>> at
>> org.wso2.carbon.identity.sso.agent.saml.SAML2SSOManager.processResponse(SAML2SSOManager.java:198)
>> at
>> org.wso2.carbon.identity.sso.agent.SSOAgentFilter.doFilter(SSOAgentFilter.java:89)
>> at
>> org.apache