Re: [Dev] CEP 400 (Beta) NotStormManagerException
Great! Thanks Suho!
On Tue, Jul 28, 2015 at 11:04 AM, Sriskandarajah Suhothayan s...@wso2.com
wrote:
There was a bug where coordinator was trying to be come coordinator again
and failing, fixed and gave a patch to Lasindu
Suho
- Sent from phone -
On Jul 28, 2015 10:55 AM, Sajith Ravindra saji...@wso2.com wrote:
Hi Imesh,
We select coordinator among managers.
Thanks
*,Sajith Ravindra*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
mobile: +94 77 2273550
blog: http://sajithr.blogspot.com/
http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
On Mon, Jul 27, 2015 at 4:37 PM, Imesh Gunaratne im...@wso2.com wrote:
Hi Suho,
Do we select a coordinator within the manager nodes or is it just the
client that decides which manager to talk to?
Thanks
On Mon, Jul 27, 2015 at 2:45 PM, Sriskandarajah Suhothayan
s...@wso2.com wrote:
CEP Managers are must for Strom based coordination, so use the CEP
Managers to be the carbon cluster as well-known members, else it does not
make sense for CEP deployment. We have also done the testing like that.
Regards
Suho
On Mon, Jul 27, 2015 at 2:16 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 2:15 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
+1 Azeez
[I mean adding Azeez into the loop]
On Mon, Jul 27, 2015 at 2:07 PM, Lasindu Charith lasi...@wso2.com
wrote:
Hi all,
We are having a clustered deployment of CEP 400 Beta in Stratos
4.1.0(in Kubernetes), similar to following. Instead of using hazelcast
clustering, I'm using 'Stratos Membership scheme' [1] which considers
all
the members in the carbon cluster as well-known members. I have done CEP
Distributed deployment according to [3][4].
[image: Inline image 1]
When CEP workers start up, I can see the following log [2] in worker
nodes. 10.244.28.23/24 are manager IPs. When the CEP managers are
restarted, the error goes away(Workers can connect to CEP Manager).
According to above membership scheme, any of the CEP
workers/managers can be the hazelcast coordinator. *Does CEP
requires a member who is both CEP manager as well as a hazelcast
coordinator to be elected as the Storm manager? *
Should CEP workers be always non-wka? How can we overcome this issue?
[1] [Architecture] Stratos Membership Scheme for Automatically
Discovering Carbon Instances in a Carbon Cluster
[2]
TID: [-1] [] [2015-07-27 04:51:11,885] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher
with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:16,887] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP
publisher
for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next
manager
NotStormManagerException(message:10.244.28.23:8904 not a storm
manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at
org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP
publisher
for 10.244.28.24:15000 with manager 10.244.3.29:8904. Trying next
manager
NotStormManagerException(message:10.244.3.29:8904 not a storm
manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at
org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
Re: [Dev] Developer Studio custom mediator pack dependencies
Hi Rajitha, Thanks for the information. I tried packing all dependencies with *, but it did not pack any dependencies. configuration instructions Bundle-SymbolicNameJsonValidatorMediator/Bundle-SymbolicName Bundle-NameJsonValidatorMediator/Bundle-Name Export-Packageorg.udara.mediation,/Export-Package DynamicImport-Package*/DynamicImport-Package /instructions Embed-Dependency*/Embed-Dependency /configuration On Tue, Jul 28, 2015 at 10:43 AM, Rajith Vitharana raji...@wso2.com wrote: Hi Udara, This is ok too, but AFAIK it's better to use Private-Packageorg.foo.myproject.*/Private-Package as in [1] o that those classes won't get exposed to others(Since only you need these packages). Or either you can use Embed-Dependencydependencies/Embed-Dependency as well. Then those jars will be embedded in the osgi jar [1] - http://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html Thanks, On Tue, Jul 28, 2015 at 10:36 AM, Udara Liyanage ud...@wso2.com wrote: Hi, I'v created a mediator project in order to write a custom mediator. However if I am using some dependencies(not available in ESB) how can I bundle them with the mediator jar. Dependencies were added to the pom, yet they are not bundled by default. Dependencies were bundled when I added them to export package. Is this the correct way of packing dependencies, or is there is another way I can specify which dependencies to be packed. Export-Packageorg.udara.mediation, org.mydependency/Export-Package -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/ -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Why 'Show Dependency' view is not enable into new RXTs
Hi Chandana/Manu, I have added a new RXT but in publisher I can't see 'Show Dependency' button, according to ES2 default concept it should enable all these G-Reg specific default features into newly added RXTs as well. This is a random test but there can be some other defaults features missing too, shall we have a review on this ? Thanks ! -- Sagara Gunathunga Architect; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [App Factory] UX/UI Incorporation
Hi All,
We have added custom URL mapping pages to git.
1. custom_url_initial.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/custom_url_initial.html
2. custom_url_listing.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/custom_url_listing.html
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Fri, Jul 24, 2015 at 5:32 PM, Dakshika Jayathilaka daksh...@wso2.com
wrote:
Hi All,
We have added another page to git.
4. database_permission_listing.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/database_permission_listing.html
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Fri, Jul 17, 2015 at 6:03 PM, Dakshika Jayathilaka daksh...@wso2.com
wrote:
Hi All,
We have added few other pages into git.
1. database_initial.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/database_initial.html
2. database_initial_listing.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/database_initial_listing.html
3. database_new.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/database_new.html
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Tue, Jul 14, 2015 at 10:10 AM, Dakshika Jayathilaka daksh...@wso2.com
wrote:
Hi All,
We have added content loading methods to
cloud_app_details_initial_content_load.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/cloud_app_details_initial_content_load.html
.
you can select any div and call 'show'/ 'hide' method.
*Sample: *
*$('selector').loading('show/hide');*
*Preview: *
https://cdn.rawgit.com/wso2-dev-ux/product-cloud/master/Markup/cloud_app_details_initial_content_load.html
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Mon, Jul 13, 2015 at 5:00 PM, Mahesh Chinthaka mahe...@wso2.com
wrote:
adding RoshanD. He is doing 009_cloud_app_details_initial.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/009_cloud_app_details_initial.html
page.
On Mon, Jul 13, 2015 at 3:53 PM, Dakshika Jayathilaka
daksh...@wso2.com wrote:
Hi All,
We have added notification updates on below pages.
1. form_notification.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/form_notification.html
2. block type notification - 009_cloud_app_details_initial.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/009_cloud_app_details_initial.html
please be kind enough to merge above changes.
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Wed, Jul 8, 2015 at 6:19 PM, Dakshika Jayathilaka
daksh...@wso2.com wrote:
Hi All,
We have added application notification pane to overview
page(009_cloud_app_details_initial.html). please check.
https://raw.githubusercontent.com/wso2-dev-ux/product-cloud/master/Markup/009_cloud_app_details_initial.html
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Wed, Jul 8, 2015 at 10:50 AM, Mahesh Chinthaka mahe...@wso2.com
wrote:
Hi Dakshika ,
I remember the wireframes. Actually 2 things,
1. Where can I find the markup for issues_initial_blank page
(Actually for the button Report an Issue)?
2. Last time when I took a git pull (before sending my last mail)
create issue button was not there in the issues_initial page. Now its
there
:) thank you.
On Wed, Jul 8, 2015 at 6:19 AM, Dakshika Jayathilaka
daksh...@wso2.com wrote:
Hi,
this is the updated listing page..
https://cdn.rawgit.com/wso2-dev-ux/product-cloud/master/Markup/issues_initial.html
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Wed, Jul 8, 2015 at 6:15 AM, Dakshika Jayathilaka
daksh...@wso2.com wrote:
Hi Mahesh,
Its already there..(issues_initial_blank) seems you missed
important points that we discussed on the meeting.. :). I have
attached
wireframes for further reference. please be kind enough to check. We
usually update markup pages everyday. so please take pull and
continue your
work.
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Tue, Jul 7, 2015 at 7:00 PM, Mahesh Chinthaka mahe...@wso2.com
wrote:
Hi Dakshika,
In issue_initial.html we dont have a Create Issue
[Dev] Please Review and Merge the PR
$Subject the Fix [1] for Public JIRA [2]. [1] https://github.com/wso2/carbon-apimgt/pull/852 [2] https://wso2.org/jira/browse/APIMANAGER-3973 -- Thanks Regards, *Chamalee De Silva* Software Engineer *WS**O2* Inc. .:http://wso2.com Office :- *+94 11 2145345 %2B94%2011%202145345* mobile :- *+94 7 %2B94%2077%2027820391 4315942* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][DAS] Spark cluster in DAS does not have worker nodes
Hi Maheshakya, I've fixed this issue. Pls take an update of the carbon-analytics repo rgds On Mon, Jul 27, 2015 at 12:12 PM, Maheshakya Wijewardena mahesha...@wso2.com wrote: Hi Niranda, I started those one by one. On Mon, Jul 27, 2015 at 12:07 PM, Niranda Perera nira...@wso2.com wrote: Hi Maheshakya, I will look into this. According to your setting, the ideal scenario is, node1 - spark master (active) + worker node2 - spark master (standby) + worker node3 - worker did you start the servers all at once or one by one? rgds On Mon, Jul 27, 2015 at 11:07 AM, Anjana Fernando anj...@wso2.com wrote: Hi, Actually, when the 3'rd sever has started up, all 3 servers should have worker instances. This seems to be a bug. @Niranda, please check it out ASAP. Cheers, Anjana. On Mon, Jul 27, 2015 at 11:01 AM, Maheshakya Wijewardena mahesha...@wso2.com wrote: Hi, I have tried to create a Spark cluster with DAS using Carbon clustering. 3 DAS nodes are configured and number of Spark masters is set to 2. In this setting, one of the 3 nodes should have a Spark worker node, but all 3 nodes are starting as Spark masters. What can be the reason for this? Configuration files (one of *axis2.xml* files of DAS clusters and *spark-defaults.conf*) of DAS are attached herewith. Best regards. -- Pruthuvi Maheshakya Wijewardena Software Engineer WSO2 : http://wso2.com/ Email: mahesha...@wso2.com Mobile: +94711228855 -- *Anjana Fernando* Senior Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware -- *Niranda Perera* Software Engineer, WSO2 Inc. Mobile: +94-71-554-8430 Twitter: @n1r44 https://twitter.com/N1R44 https://pythagoreanscript.wordpress.com/ -- Pruthuvi Maheshakya Wijewardena Software Engineer WSO2 : http://wso2.com/ Email: mahesha...@wso2.com Mobile: +94711228855 -- *Niranda Perera* Software Engineer, WSO2 Inc. Mobile: +94-71-554-8430 Twitter: @n1r44 https://twitter.com/N1R44 https://pythagoreanscript.wordpress.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Identity Providers UI in AS-5.3.0
Hi IS folks, Is there any use cases of having $subject? At the moment, Identity Providers menu item comes as the first in the main menu in the management console. This is due to a modification introduced in org.wso2.carbon.idp.mgt.ui 4.2.1 [1] (IDP menu has been moved from configure menu to main menu in MC). There are [2] and [3] raised to remove/change the order of the menu item. I would like to know if there are any possible use cases, if not we can remove it. [1] http://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/idp-mgt/org.wso2.carbon.idp.mgt.ui/4.2.1/src/main/resources/META-INF/component.xml [2] https://wso2.org/jira/browse/WSAS-1963 [3] https://wso2.org/jira/browse/WSAS-2018 -- Best Regards, Kalpa Welivitigoda Software Engineer, WSO2 Inc. http://wso2.com Email: kal...@wso2.com Mobile: +94776509215 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] CEP 400 (Beta) NotStormManagerException
Hi Suho,
Do we select a coordinator within the manager nodes or is it just the
client that decides which manager to talk to?
Thanks
On Mon, Jul 27, 2015 at 2:45 PM, Sriskandarajah Suhothayan s...@wso2.com
wrote:
CEP Managers are must for Strom based coordination, so use the CEP
Managers to be the carbon cluster as well-known members, else it does not
make sense for CEP deployment. We have also done the testing like that.
Regards
Suho
On Mon, Jul 27, 2015 at 2:16 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 2:15 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
+1 Azeez
[I mean adding Azeez into the loop]
On Mon, Jul 27, 2015 at 2:07 PM, Lasindu Charith lasi...@wso2.com
wrote:
Hi all,
We are having a clustered deployment of CEP 400 Beta in Stratos
4.1.0(in Kubernetes), similar to following. Instead of using hazelcast
clustering, I'm using 'Stratos Membership scheme' [1] which considers all
the members in the carbon cluster as well-known members. I have done CEP
Distributed deployment according to [3][4].
[image: Inline image 1]
When CEP workers start up, I can see the following log [2] in worker
nodes. 10.244.28.23/24 are manager IPs. When the CEP managers are
restarted, the error goes away(Workers can connect to CEP Manager).
According to above membership scheme, any of the CEP workers/managers
can be the hazelcast coordinator. *Does CEP requires a member who is
both CEP manager as well as a hazelcast coordinator to be elected as the
Storm manager? *
Should CEP workers be always non-wka? How can we overcome this issue?
[1] [Architecture] Stratos Membership Scheme for Automatically
Discovering Carbon Instances in a Carbon Cluster
[2]
TID: [-1] [] [2015-07-27 04:51:11,885] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:16,887] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next
manager
NotStormManagerException(message:10.244.28.23:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.3.29:8904. Trying next
manager
NotStormManagerException(message:10.244.3.29:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP
Re: [Dev] [IS] No Established session issue at the session timeout
Hi all, I have taken over looking into this issue https://wso2.org/jira/browse/STORE-875 in ES pack. As of now we have decided to increase this session-timeout duration to a higher value. We can achieve that by setting SessionIdleTimeout(default 15 min) to a higher value in identity.xml. But we cannot override this value coming from IS-components, since SessionIdleTimeout is not parameterized. As a workaround, we are going to maintain a local copy of identity.xml in ES repository with this particular value increased. Can we get SessionIdleTimeout entry parameterized from IS side, so that we can override it at build time? Or any other better way to do this? [1] https://wso2.org/jira/browse/STORE-875 Thanks! -Ayesha On Thu, Jul 16, 2015 at 5:31 PM, Johann Nallathamby joh...@wso2.com wrote: Hi Manu, Sorry couldn't give a timely update in the thread. We discussed this internally with the presence of Tanya from UES as well. We concluded that this is not a blocker or not very easily reproducible by a single user at a browser without help of automating the interactions. This could only happen if there is a huge network delay. Implementing this stuff will take a considerable time. None of our users have faced any issue so far. We will consider this for a future release. Also Thanuja is currently developing some thing for IS 5.1.0 where if something like this occurs, the user won't land in an error page but instead land in a logged out page of the Identity Server. Thanks. On Thu, Jul 16, 2015 at 11:54 AM, Manuranga Perera m...@wso2.com wrote: Hi IS team, How is the progress on this issue? We need this fix soon for the RC1 release. On Mon, Jun 15, 2015 at 7:02 PM, Ruchira Wageesha ruch...@wso2.com wrote: We have following concern with the above suggested approach. Say we make the call1 and then receive the response 1 as the session still exists. But between the time that we make the call2, session gets expired. (since these are network calls and delays may occur.) So at that point we face the same original problem again. Isn't the proper approach is to send a logout response from the identity side with a proper message (no session exists) to the application side rather than breaking the flow in the middle? @IS Team, Can you please share your thoughts on this and any fixes if needed please :). Senior Software Engineer, WSO2 Inc. : wso2.com Mobile : +94718184439 Blog : http://tanyamadurapperuma.blogspot.com -- *Ruchira Wageesha**Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com* *email: ruch...@wso2.com ruch...@wso2.com, blog: ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com, mobile: +94 77 5493444 %2B94%2077%205493444* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com -- Thanks Regards, *Johann Dilantha Nallathamby* Technical Lead Product Lead of WSO2 Identity Server Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+9476950* Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why 'Show Dependency' view is not enable into new RXTs
Hi Sagara, A public JIRA[1] is created to track this. [1] - https://wso2.org/jira/browse/REGISTRY-2718 Thanks On Mon, Jul 27, 2015 at 6:48 PM, Prasanna Dangalla prasa...@wso2.com wrote: Hi Sagara, At the moment in all the assets, 'view-asset-details-container.hbs' page includes the Show dependency button. +1 We'll review these kind of duplicates and move them to the default. Thanks On Mon, Jul 27, 2015 at 6:42 PM, Sagara Gunathunga sag...@wso2.com wrote: Hi Chandana/Manu, I have added a new RXT but in publisher I can't see 'Show Dependency' button, according to ES2 default concept it should enable all these G-Reg specific default features into newly added RXTs as well. This is a random test but there can be some other defaults features missing too, shall we have a review on this ? Thanks ! -- Sagara Gunathunga Architect; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- Prasanna Dangalla Software Engineer, WSO2, Inc.; http://wso2.com/ lean.enterprise.middleware cell: +94 777 55 80 30 | +94 718 11 27 51 twitter: @prasa77 -- Prasanna Dangalla Software Engineer, WSO2, Inc.; http://wso2.com/ lean.enterprise.middleware cell: +94 777 55 80 30 | +94 718 11 27 51 twitter: @prasa77 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][DAS] Spark cluster in DAS does not have worker nodes
Thanks Niranda. Best regards. On Mon, Jul 27, 2015 at 5:40 PM, Niranda Perera nira...@wso2.com wrote: Hi Maheshakya, I've fixed this issue. Pls take an update of the carbon-analytics repo rgds On Mon, Jul 27, 2015 at 12:12 PM, Maheshakya Wijewardena mahesha...@wso2.com wrote: Hi Niranda, I started those one by one. On Mon, Jul 27, 2015 at 12:07 PM, Niranda Perera nira...@wso2.com wrote: Hi Maheshakya, I will look into this. According to your setting, the ideal scenario is, node1 - spark master (active) + worker node2 - spark master (standby) + worker node3 - worker did you start the servers all at once or one by one? rgds On Mon, Jul 27, 2015 at 11:07 AM, Anjana Fernando anj...@wso2.com wrote: Hi, Actually, when the 3'rd sever has started up, all 3 servers should have worker instances. This seems to be a bug. @Niranda, please check it out ASAP. Cheers, Anjana. On Mon, Jul 27, 2015 at 11:01 AM, Maheshakya Wijewardena mahesha...@wso2.com wrote: Hi, I have tried to create a Spark cluster with DAS using Carbon clustering. 3 DAS nodes are configured and number of Spark masters is set to 2. In this setting, one of the 3 nodes should have a Spark worker node, but all 3 nodes are starting as Spark masters. What can be the reason for this? Configuration files (one of *axis2.xml* files of DAS clusters and *spark-defaults.conf*) of DAS are attached herewith. Best regards. -- Pruthuvi Maheshakya Wijewardena Software Engineer WSO2 : http://wso2.com/ Email: mahesha...@wso2.com Mobile: +94711228855 -- *Anjana Fernando* Senior Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware -- *Niranda Perera* Software Engineer, WSO2 Inc. Mobile: +94-71-554-8430 Twitter: @n1r44 https://twitter.com/N1R44 https://pythagoreanscript.wordpress.com/ -- Pruthuvi Maheshakya Wijewardena Software Engineer WSO2 : http://wso2.com/ Email: mahesha...@wso2.com Mobile: +94711228855 -- *Niranda Perera* Software Engineer, WSO2 Inc. Mobile: +94-71-554-8430 Twitter: @n1r44 https://twitter.com/N1R44 https://pythagoreanscript.wordpress.com/ -- Pruthuvi Maheshakya Wijewardena Software Engineer WSO2 : http://wso2.com/ Email: mahesha...@wso2.com Mobile: +94711228855 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Automated tests to tests Application Server with Apache Ldap as a User Store
Thanks Nuwan for checking into this. On Wed, Jul 22, 2015 at 2:18 PM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi Kasun, Please find the inline answers. On Tue, Jul 21, 2015 at 8:39 PM, KasunG Gajasinghe kas...@wso2.com wrote: Hi Nuwan, Can you please answer following questions regarding this PR? 1. Can you rename to module name tests-with-ldap to tests-ldap-userstores. I believe that's more meaningful. Yes. This is more meaningful. will rename the module 2. Shouldn't the distribution-with-apache-ldap be placed under tests-common module? We need a proper name for this module as well, since for new eyes, the name seems to be less meaningful. How about ldap-installed-wso2as-distribution? Please let me know if you have a better name. :-) I do not think the module which build distribution move into tests-common module. tests-common module contains the AS test utilities. Having a new distribution in integration level is fine. I will discuss and put a meaningful name for the module which built AS distribution having Apache Ldap server feature itself 3. What does it mean to have a test case with only a @Factory annotation - ReadWriteLdapUserStoreAdminUserTestCase I did not duplicate the UserManagement Test cases in this test module. I reuse the same user management test cases which are in the tests module already implemented for JDBC user store. So I implement a new class extending the existing class. Then same test methods are executing against the readwrite Ldap user store . In that class We have to implement a constructor with @Factory annotation referring the same data provider in order to execute the test class. 4. The sub-modules should not have the version tag in maven dependencies. The version should be defined in the root pom. Fixed it by removing version. Thanks, Nuwanw Thanks. On Tue, Jul 21, 2015 at 2:53 PM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi, We have integrate a tests module(tests-with-ldap)[1] in AS integration to test the user management in AS with apache Ldap server as the user store. Ldap server feature is installed on AS by building a distribution with ldap server feature and the built server is used by the tests-with-ldap module throughout the test execution. This module executes 100 test cases with the user store as ReadWrite and ReadOnly modes by changing the user-mgt.xml. All the user management test cases in tests module are executed against the ReadWrite Ldap user store and implemented a test class to test the ReadOnly Ldap functionalities as well. [1] https://github.com/wso2/product-as/pull/152 Please refer the attached surefire-reports.zip for test cases Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why 'Show Dependency' view is not enable into new RXTs
Hi Sagara, At the moment in all the assets, 'view-asset-details-container.hbs' page includes the Show dependency button. +1 We'll review these kind of duplicates and move them to the default. Thanks On Mon, Jul 27, 2015 at 6:42 PM, Sagara Gunathunga sag...@wso2.com wrote: Hi Chandana/Manu, I have added a new RXT but in publisher I can't see 'Show Dependency' button, according to ES2 default concept it should enable all these G-Reg specific default features into newly added RXTs as well. This is a random test but there can be some other defaults features missing too, shall we have a review on this ? Thanks ! -- Sagara Gunathunga Architect; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- Prasanna Dangalla Software Engineer, WSO2, Inc.; http://wso2.com/ lean.enterprise.middleware cell: +94 777 55 80 30 | +94 718 11 27 51 twitter: @prasa77 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [App Factory] UX/UI Incorporation
Adding Anuruddha and Samith
On Mon, Jul 27, 2015 at 5:48 PM, Dakshika Jayathilaka daksh...@wso2.com
wrote:
Hi All,
We have added custom URL mapping pages to git.
1. custom_url_initial.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/custom_url_initial.html
2. custom_url_listing.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/custom_url_listing.html
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Fri, Jul 24, 2015 at 5:32 PM, Dakshika Jayathilaka daksh...@wso2.com
wrote:
Hi All,
We have added another page to git.
4. database_permission_listing.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/database_permission_listing.html
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Fri, Jul 17, 2015 at 6:03 PM, Dakshika Jayathilaka daksh...@wso2.com
wrote:
Hi All,
We have added few other pages into git.
1. database_initial.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/database_initial.html
2. database_initial_listing.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/database_initial_listing.html
3. database_new.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/database_new.html
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Tue, Jul 14, 2015 at 10:10 AM, Dakshika Jayathilaka
daksh...@wso2.com wrote:
Hi All,
We have added content loading methods to
cloud_app_details_initial_content_load.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/cloud_app_details_initial_content_load.html
.
you can select any div and call 'show'/ 'hide' method.
*Sample: *
*$('selector').loading('show/hide');*
*Preview: *
https://cdn.rawgit.com/wso2-dev-ux/product-cloud/master/Markup/cloud_app_details_initial_content_load.html
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Mon, Jul 13, 2015 at 5:00 PM, Mahesh Chinthaka mahe...@wso2.com
wrote:
adding RoshanD. He is doing 009_cloud_app_details_initial.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/009_cloud_app_details_initial.html
page.
On Mon, Jul 13, 2015 at 3:53 PM, Dakshika Jayathilaka
daksh...@wso2.com wrote:
Hi All,
We have added notification updates on below pages.
1. form_notification.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/form_notification.html
2. block type notification - 009_cloud_app_details_initial.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/009_cloud_app_details_initial.html
please be kind enough to merge above changes.
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Wed, Jul 8, 2015 at 6:19 PM, Dakshika Jayathilaka
daksh...@wso2.com wrote:
Hi All,
We have added application notification pane to overview
page(009_cloud_app_details_initial.html). please check.
https://raw.githubusercontent.com/wso2-dev-ux/product-cloud/master/Markup/009_cloud_app_details_initial.html
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Wed, Jul 8, 2015 at 10:50 AM, Mahesh Chinthaka mahe...@wso2.com
wrote:
Hi Dakshika ,
I remember the wireframes. Actually 2 things,
1. Where can I find the markup for issues_initial_blank page
(Actually for the button Report an Issue)?
2. Last time when I took a git pull (before sending my last mail)
create issue button was not there in the issues_initial page. Now its
there
:) thank you.
On Wed, Jul 8, 2015 at 6:19 AM, Dakshika Jayathilaka
daksh...@wso2.com wrote:
Hi,
this is the updated listing page..
https://cdn.rawgit.com/wso2-dev-ux/product-cloud/master/Markup/issues_initial.html
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Wed, Jul 8, 2015 at 6:15 AM, Dakshika Jayathilaka
daksh...@wso2.com wrote:
Hi Mahesh,
Its already there..(issues_initial_blank) seems you missed
important points that we discussed on the meeting.. :). I have
attached
wireframes for further reference. please be kind enough to check. We
usually update markup pages everyday. so please take pull and
continue your
work.
Regards,
*Dakshika Jayathilaka*
PMC Member Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Tue, Jul 7, 2015 at
Re: [Dev] Why 'Show Dependency' view is not enable into new RXTs
This is fixed now. There's an app called greg-publisher-defaults in publisher where we can add whatever should come to a default asset which we do not override. Shazni Nazeer Mob : +94 37331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com On Mon, Jul 27, 2015 at 7:34 PM, Prasanna Dangalla prasa...@wso2.com wrote: Hi Sagara, A public JIRA[1] is created to track this. [1] - https://wso2.org/jira/browse/REGISTRY-2718 Thanks On Mon, Jul 27, 2015 at 6:48 PM, Prasanna Dangalla prasa...@wso2.com wrote: Hi Sagara, At the moment in all the assets, 'view-asset-details-container.hbs' page includes the Show dependency button. +1 We'll review these kind of duplicates and move them to the default. Thanks On Mon, Jul 27, 2015 at 6:42 PM, Sagara Gunathunga sag...@wso2.com wrote: Hi Chandana/Manu, I have added a new RXT but in publisher I can't see 'Show Dependency' button, according to ES2 default concept it should enable all these G-Reg specific default features into newly added RXTs as well. This is a random test but there can be some other defaults features missing too, shall we have a review on this ? Thanks ! -- Sagara Gunathunga Architect; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- Prasanna Dangalla Software Engineer, WSO2, Inc.; http://wso2.com/ lean.enterprise.middleware cell: +94 777 55 80 30 | +94 718 11 27 51 twitter: @prasa77 -- Prasanna Dangalla Software Engineer, WSO2, Inc.; http://wso2.com/ lean.enterprise.middleware cell: +94 777 55 80 30 | +94 718 11 27 51 twitter: @prasa77 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Does IS has mutual authenticator packed in IS 5.1.0 disctribution?
+1. Yes it must be removed because if it is available there, then latest
patches (given after SP1) also should be there.
On Mon, Jul 27, 2015 at 9:27 PM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 9:24 PM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
Thanks a lot Tharindu for confirming it. I guess it is better to update
the pre-configured pack with this change.
I meant it is better to remove TenantConfig.properties file from
pre-configured IS pack.
Thanks,
Raj.
On Mon, Jul 27, 2015 at 9:21 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Raj,
I tested the same and reproduced the issue... The fix is to delete the
TenantConfig.properties file from IS_HOME/repository/conf/ directory.
Ideally this file should not be there with Service Pack 1. I wonder how it
got there because this was introduced in patch1040 which was released after
service pack 1. If the TenantConfig.properties file is in conf directory,
then there should be the latest authentication.endpoint webapp from support
branch.
Regards,
Tharindu
On Mon, Jul 27, 2015 at 8:19 PM, Tharindu Edirisinghe
tharin...@wso2.com wrote:
Hi Raj,
This was done after SP1 release. You can find the source for the custom
secret callback handler in the patch1040 [1]. But this is needed only if
the Tenat List Dropdown feature [2] in the SSO login page is enabled and
also if secure vault is added for the TenantConfig.properties file. By
default this feature is disabled. If we get the error when this feature is
disabled, it is not correct. If so we need to patch authentication.endpoint
webapp that is delivered in the pack. Let's have a review on this tomorrow.
[1]
https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/patches/patch1040/
[2]
http://tharindue.blogspot.com/2015/04/enabling-tenant-domains-dropdown-in-sso.html
On Mon, Jul 27, 2015 at 3:15 PM, Darshana Gunawardana
darsh...@wso2.com wrote:
On Mon, Jul 27, 2015 at 2:22 PM, Samuel Gnaniah sam...@wso2.com
wrote:
Adding TharinduA.
*Samuel Gnaniah*
Lead Technical Writer
WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798
On Mon, Jul 27, 2015 at 12:33 PM, Rajkumar Rajaratnam
rajkum...@wso2.com wrote:
Hi Tharindu
On Sun, Apr 26, 2015 at 9:11 AM, Tharindu Edirisinghe
tharin...@wso2.com wrote:
Hi Firzan,
The custom secret callback handler should be included in
authenticanendpoint/WEB-INF/lib directory only if secure vault is
added. We
should write proper documentation for enabling secure vault for the
dropdown feature and mention that. However the error handling of the
feature is improved than the service pack when comes to the next
release of
IS.
Where can I get CustomSecretCallbackHandler jar?
Check :
https://wso2.org/jira/browse/IDENTITY-2981?focusedCommentId=95432page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-95432
Thanks,
Darshana.
I couldn't find it in SP01. The pre-configured IS pack [1] has
TenantConfig.properties file which references
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler. It
throws
following CNF exceptions since the jar is not included anywhere. Please
advice.
TID: [0] [IS] [2015-07-26 08:28:18,874] ERROR
{org.wso2.securevault.secret.SecretCallbackHandlerFactory} - A
SecretCallbackHandler cannot be found for class name :
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
{org.wso2.securevault.secret.SecretCallbackHandlerFactory}
java.lang.ClassNotFoundException:
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
at
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:138)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
at
org.wso2.securevault.secret.SecretCallbackHandlerFactory.createSecretCallbackHandler(SecretCallbackHandlerFactory.java:62)
at
org.wso2.securevault.SecretResolverFactory.initPasswordManager(SecretResolverFactory.java:278)
at
org.wso2.securevault.SecretResolverFactory.create(SecretResolverFactory.java:218)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.resolveSecrets(TenantDataManager.java:282)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.init(TenantDataManager.java:88)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.isTenantListEnabled(TenantDataManager.java:267)
at
org.apache.jsp.login_jsp._jspService(org.apache.jsp.login_jsp:329)
at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at
Re: [Dev] Does IS has mutual authenticator packed in IS 5.1.0 disctribution?
Hi Raj,
I tested the same and reproduced the issue... The fix is to delete the
TenantConfig.properties file from IS_HOME/repository/conf/ directory.
Ideally this file should not be there with Service Pack 1. I wonder how it
got there because this was introduced in patch1040 which was released after
service pack 1. If the TenantConfig.properties file is in conf directory,
then there should be the latest authentication.endpoint webapp from support
branch.
Regards,
Tharindu
On Mon, Jul 27, 2015 at 8:19 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Raj,
This was done after SP1 release. You can find the source for the custom
secret callback handler in the patch1040 [1]. But this is needed only if
the Tenat List Dropdown feature [2] in the SSO login page is enabled and
also if secure vault is added for the TenantConfig.properties file. By
default this feature is disabled. If we get the error when this feature is
disabled, it is not correct. If so we need to patch authentication.endpoint
webapp that is delivered in the pack. Let's have a review on this tomorrow.
[1]
https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/patches/patch1040/
[2]
http://tharindue.blogspot.com/2015/04/enabling-tenant-domains-dropdown-in-sso.html
On Mon, Jul 27, 2015 at 3:15 PM, Darshana Gunawardana darsh...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 2:22 PM, Samuel Gnaniah sam...@wso2.com wrote:
Adding TharinduA.
*Samuel Gnaniah*
Lead Technical Writer
WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798
On Mon, Jul 27, 2015 at 12:33 PM, Rajkumar Rajaratnam
rajkum...@wso2.com wrote:
Hi Tharindu
On Sun, Apr 26, 2015 at 9:11 AM, Tharindu Edirisinghe
tharin...@wso2.com wrote:
Hi Firzan,
The custom secret callback handler should be included in
authenticanendpoint/WEB-INF/lib directory only if secure vault is added.
We
should write proper documentation for enabling secure vault for the
dropdown feature and mention that. However the error handling of the
feature is improved than the service pack when comes to the next release
of
IS.
Where can I get CustomSecretCallbackHandler jar?
Check :
https://wso2.org/jira/browse/IDENTITY-2981?focusedCommentId=95432page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-95432
Thanks,
Darshana.
I couldn't find it in SP01. The pre-configured IS pack [1] has
TenantConfig.properties file which references
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler. It throws
following CNF exceptions since the jar is not included anywhere. Please
advice.
TID: [0] [IS] [2015-07-26 08:28:18,874] ERROR
{org.wso2.securevault.secret.SecretCallbackHandlerFactory} - A
SecretCallbackHandler cannot be found for class name :
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
{org.wso2.securevault.secret.SecretCallbackHandlerFactory}
java.lang.ClassNotFoundException:
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
at
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:138)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
at
org.wso2.securevault.secret.SecretCallbackHandlerFactory.createSecretCallbackHandler(SecretCallbackHandlerFactory.java:62)
at
org.wso2.securevault.SecretResolverFactory.initPasswordManager(SecretResolverFactory.java:278)
at
org.wso2.securevault.SecretResolverFactory.create(SecretResolverFactory.java:218)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.resolveSecrets(TenantDataManager.java:282)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.init(TenantDataManager.java:88)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.isTenantListEnabled(TenantDataManager.java:267)
at org.apache.jsp.login_jsp._jspService(org.apache.jsp.login_jsp:329)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:412)
at
Re: [Dev] Does IS has mutual authenticator packed in IS 5.1.0 disctribution?
On Mon, Jul 27, 2015 at 9:24 PM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
Thanks a lot Tharindu for confirming it. I guess it is better to update
the pre-configured pack with this change.
I meant it is better to remove TenantConfig.properties file from
pre-configured IS pack.
Thanks,
Raj.
On Mon, Jul 27, 2015 at 9:21 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Raj,
I tested the same and reproduced the issue... The fix is to delete the
TenantConfig.properties file from IS_HOME/repository/conf/ directory.
Ideally this file should not be there with Service Pack 1. I wonder how it
got there because this was introduced in patch1040 which was released after
service pack 1. If the TenantConfig.properties file is in conf directory,
then there should be the latest authentication.endpoint webapp from support
branch.
Regards,
Tharindu
On Mon, Jul 27, 2015 at 8:19 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Raj,
This was done after SP1 release. You can find the source for the custom
secret callback handler in the patch1040 [1]. But this is needed only if
the Tenat List Dropdown feature [2] in the SSO login page is enabled and
also if secure vault is added for the TenantConfig.properties file. By
default this feature is disabled. If we get the error when this feature is
disabled, it is not correct. If so we need to patch authentication.endpoint
webapp that is delivered in the pack. Let's have a review on this tomorrow.
[1]
https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/patches/patch1040/
[2]
http://tharindue.blogspot.com/2015/04/enabling-tenant-domains-dropdown-in-sso.html
On Mon, Jul 27, 2015 at 3:15 PM, Darshana Gunawardana darsh...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 2:22 PM, Samuel Gnaniah sam...@wso2.com
wrote:
Adding TharinduA.
*Samuel Gnaniah*
Lead Technical Writer
WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798
On Mon, Jul 27, 2015 at 12:33 PM, Rajkumar Rajaratnam
rajkum...@wso2.com wrote:
Hi Tharindu
On Sun, Apr 26, 2015 at 9:11 AM, Tharindu Edirisinghe
tharin...@wso2.com wrote:
Hi Firzan,
The custom secret callback handler should be included in
authenticanendpoint/WEB-INF/lib directory only if secure vault is
added. We
should write proper documentation for enabling secure vault for the
dropdown feature and mention that. However the error handling of the
feature is improved than the service pack when comes to the next
release of
IS.
Where can I get CustomSecretCallbackHandler jar?
Check :
https://wso2.org/jira/browse/IDENTITY-2981?focusedCommentId=95432page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-95432
Thanks,
Darshana.
I couldn't find it in SP01. The pre-configured IS pack [1] has
TenantConfig.properties file which references
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler. It throws
following CNF exceptions since the jar is not included anywhere. Please
advice.
TID: [0] [IS] [2015-07-26 08:28:18,874] ERROR
{org.wso2.securevault.secret.SecretCallbackHandlerFactory} - A
SecretCallbackHandler cannot be found for class name :
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
{org.wso2.securevault.secret.SecretCallbackHandlerFactory}
java.lang.ClassNotFoundException:
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
at
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:138)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
at
org.wso2.securevault.secret.SecretCallbackHandlerFactory.createSecretCallbackHandler(SecretCallbackHandlerFactory.java:62)
at
org.wso2.securevault.SecretResolverFactory.initPasswordManager(SecretResolverFactory.java:278)
at
org.wso2.securevault.SecretResolverFactory.create(SecretResolverFactory.java:218)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.resolveSecrets(TenantDataManager.java:282)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.init(TenantDataManager.java:88)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.isTenantListEnabled(TenantDataManager.java:267)
at org.apache.jsp.login_jsp._jspService(org.apache.jsp.login_jsp:329)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
Re: [Dev] Does IS has mutual authenticator packed in IS 5.1.0 disctribution?
Thanks a lot Tharindu for confirming it. I guess it is better to update the
pre-configured pack with this change.
Thanks,
Raj.
On Mon, Jul 27, 2015 at 9:21 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Raj,
I tested the same and reproduced the issue... The fix is to delete the
TenantConfig.properties file from IS_HOME/repository/conf/ directory.
Ideally this file should not be there with Service Pack 1. I wonder how it
got there because this was introduced in patch1040 which was released after
service pack 1. If the TenantConfig.properties file is in conf directory,
then there should be the latest authentication.endpoint webapp from support
branch.
Regards,
Tharindu
On Mon, Jul 27, 2015 at 8:19 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Raj,
This was done after SP1 release. You can find the source for the custom
secret callback handler in the patch1040 [1]. But this is needed only if
the Tenat List Dropdown feature [2] in the SSO login page is enabled and
also if secure vault is added for the TenantConfig.properties file. By
default this feature is disabled. If we get the error when this feature is
disabled, it is not correct. If so we need to patch authentication.endpoint
webapp that is delivered in the pack. Let's have a review on this tomorrow.
[1]
https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/patches/patch1040/
[2]
http://tharindue.blogspot.com/2015/04/enabling-tenant-domains-dropdown-in-sso.html
On Mon, Jul 27, 2015 at 3:15 PM, Darshana Gunawardana darsh...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 2:22 PM, Samuel Gnaniah sam...@wso2.com wrote:
Adding TharinduA.
*Samuel Gnaniah*
Lead Technical Writer
WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798
On Mon, Jul 27, 2015 at 12:33 PM, Rajkumar Rajaratnam
rajkum...@wso2.com wrote:
Hi Tharindu
On Sun, Apr 26, 2015 at 9:11 AM, Tharindu Edirisinghe
tharin...@wso2.com wrote:
Hi Firzan,
The custom secret callback handler should be included in
authenticanendpoint/WEB-INF/lib directory only if secure vault is added.
We
should write proper documentation for enabling secure vault for the
dropdown feature and mention that. However the error handling of the
feature is improved than the service pack when comes to the next release
of
IS.
Where can I get CustomSecretCallbackHandler jar?
Check :
https://wso2.org/jira/browse/IDENTITY-2981?focusedCommentId=95432page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-95432
Thanks,
Darshana.
I couldn't find it in SP01. The pre-configured IS pack [1] has
TenantConfig.properties file which references
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler. It throws
following CNF exceptions since the jar is not included anywhere. Please
advice.
TID: [0] [IS] [2015-07-26 08:28:18,874] ERROR
{org.wso2.securevault.secret.SecretCallbackHandlerFactory} - A
SecretCallbackHandler cannot be found for class name :
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
{org.wso2.securevault.secret.SecretCallbackHandlerFactory}
java.lang.ClassNotFoundException:
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
at
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:138)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
at
org.wso2.securevault.secret.SecretCallbackHandlerFactory.createSecretCallbackHandler(SecretCallbackHandlerFactory.java:62)
at
org.wso2.securevault.SecretResolverFactory.initPasswordManager(SecretResolverFactory.java:278)
at
org.wso2.securevault.SecretResolverFactory.create(SecretResolverFactory.java:218)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.resolveSecrets(TenantDataManager.java:282)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.init(TenantDataManager.java:88)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.isTenantListEnabled(TenantDataManager.java:267)
at org.apache.jsp.login_jsp._jspService(org.apache.jsp.login_jsp:329)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
Re: [Dev] Does IS has mutual authenticator packed in IS 5.1.0 disctribution?
Hi Raj,
This was done after SP1 release. You can find the source for the custom
secret callback handler in the patch1040 [1]. But this is needed only if
the Tenat List Dropdown feature [2] in the SSO login page is enabled and
also if secure vault is added for the TenantConfig.properties file. By
default this feature is disabled. If we get the error when this feature is
disabled, it is not correct. If so we need to patch authentication.endpoint
webapp that is delivered in the pack. Let's have a review on this tomorrow.
[1]
https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/patches/patch1040/
[2]
http://tharindue.blogspot.com/2015/04/enabling-tenant-domains-dropdown-in-sso.html
On Mon, Jul 27, 2015 at 3:15 PM, Darshana Gunawardana darsh...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 2:22 PM, Samuel Gnaniah sam...@wso2.com wrote:
Adding TharinduA.
*Samuel Gnaniah*
Lead Technical Writer
WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798
On Mon, Jul 27, 2015 at 12:33 PM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
Hi Tharindu
On Sun, Apr 26, 2015 at 9:11 AM, Tharindu Edirisinghe
tharin...@wso2.com wrote:
Hi Firzan,
The custom secret callback handler should be included in
authenticanendpoint/WEB-INF/lib directory only if secure vault is added. We
should write proper documentation for enabling secure vault for the
dropdown feature and mention that. However the error handling of the
feature is improved than the service pack when comes to the next release of
IS.
Where can I get CustomSecretCallbackHandler jar?
Check :
https://wso2.org/jira/browse/IDENTITY-2981?focusedCommentId=95432page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-95432
Thanks,
Darshana.
I couldn't find it in SP01. The pre-configured IS pack [1] has
TenantConfig.properties file which references
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler. It throws
following CNF exceptions since the jar is not included anywhere. Please
advice.
TID: [0] [IS] [2015-07-26 08:28:18,874] ERROR
{org.wso2.securevault.secret.SecretCallbackHandlerFactory} - A
SecretCallbackHandler cannot be found for class name :
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
{org.wso2.securevault.secret.SecretCallbackHandlerFactory}
java.lang.ClassNotFoundException:
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
at
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:138)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
at
org.wso2.securevault.secret.SecretCallbackHandlerFactory.createSecretCallbackHandler(SecretCallbackHandlerFactory.java:62)
at
org.wso2.securevault.SecretResolverFactory.initPasswordManager(SecretResolverFactory.java:278)
at
org.wso2.securevault.SecretResolverFactory.create(SecretResolverFactory.java:218)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.resolveSecrets(TenantDataManager.java:282)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.init(TenantDataManager.java:88)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.isTenantListEnabled(TenantDataManager.java:267)
at org.apache.jsp.login_jsp._jspService(org.apache.jsp.login_jsp:329)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:412)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at
org.wso2.carbon.identity.application.authentication.endpoint.oauth2.OAuth2Login.doGet(OAuth2Login.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
[Dev] Does IS support session replication?
Hi all, I want to use two IDPs when setting up APPM internal deployment. IDPs are fronted by an nginx. So, I have 2 options. 1. Session Replication *@IS team *- Does IS support session replication? Can we achieve that with session persistence feature? 2. Sticky Sessions (have to find how to do this with nginx) Please share your ideas. Thanks, -- Lakshani Gamage *Software Engineer* Mobile : +94 (0) 71 5478184 %2B94%20%280%29%20773%20451194 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.1 RC1
Hi Devs, WSO2 Carbon Kernel 4.4.1. RC1 Release Vote This release fixes the following issues: https://wso2.org/jira/issues/?filter=12323 Please download kernel RC1 and test your products with the kernel 4.4.1 RC1 and vote. Vote will be open for 72 hours or as needed. *Source binary distribution files:* http://maven.wso2.org/nexus/content/repositories/staging/org/wso2/carbon/wso2carbon/4.4.1/ *Maven staging repository:* http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-012/ *The tag to be voted upon :* https://github.com/wso2/carbon4-kernel/tree/v4.4.1-RC1 [ ] Broken - do not release (explain why) [ ] Stable - go ahead and release Thanks, Best Regards Carbon Team. -- Thusitha Dayaratne Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com Mobile +94712756809 Blog alokayasoya.blogspot.com Abouthttp://about.me/thusithathilina ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.1 RC1
Hi guys, I don't think LICENSE.txt file within the pack has been updated for the 4.4.1 version. Shouldn't we be updating that as well for the RC pack? Thanks, Lasantha On 28 July 2015 at 00:23, Thusitha Thilina Dayaratne thusit...@wso2.com wrote: Hi Devs, WSO2 Carbon Kernel 4.4.1. RC1 Release Vote This release fixes the following issues: https://wso2.org/jira/issues/?filter=12323 Please download kernel RC1 and test your products with the kernel 4.4.1 RC1 and vote. Vote will be open for 72 hours or as needed. *Source binary distribution files:* http://maven.wso2.org/nexus/content/repositories/staging/org/wso2/carbon/wso2carbon/4.4.1/ *Maven staging repository:* http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-012/ *The tag to be voted upon :* https://github.com/wso2/carbon4-kernel/tree/v4.4.1-RC1 [ ] Broken - do not release (explain why) [ ] Stable - go ahead and release Thanks, Best Regards Carbon Team. -- Thusitha Dayaratne Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com Mobile +94712756809 Blog alokayasoya.blogspot.com Abouthttp://about.me/thusithathilina ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Senior Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.1 RC1
I tested out the basic functionality of the carbon management console and also tested the basic functionality of OSGi console and it is working fine... :-). But I don't think we can proceed with the vote until the license is updated, right? Thanks, Lasantha On 28 July 2015 at 01:42, Lasantha Fernando lasan...@wso2.com wrote: Hi guys, I don't think LICENSE.txt file within the pack has been updated for the 4.4.1 version. Shouldn't we be updating that as well for the RC pack? Thanks, Lasantha On 28 July 2015 at 00:23, Thusitha Thilina Dayaratne thusit...@wso2.com wrote: Hi Devs, WSO2 Carbon Kernel 4.4.1. RC1 Release Vote This release fixes the following issues: https://wso2.org/jira/issues/?filter=12323 Please download kernel RC1 and test your products with the kernel 4.4.1 RC1 and vote. Vote will be open for 72 hours or as needed. *Source binary distribution files:* http://maven.wso2.org/nexus/content/repositories/staging/org/wso2/carbon/wso2carbon/4.4.1/ *Maven staging repository:* http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-012/ *The tag to be voted upon :* https://github.com/wso2/carbon4-kernel/tree/v4.4.1-RC1 [ ] Broken - do not release (explain why) [ ] Stable - go ahead and release Thanks, Best Regards Carbon Team. -- Thusitha Dayaratne Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com Mobile +94712756809 Blog alokayasoya.blogspot.com Abouthttp://about.me/thusithathilina ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Senior Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 -- *Lasantha Fernando* Senior Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Script Mediator Error in Developer Studio 3.7.1
Hi,
I'm using Developer Studio version 3.7.1 on MacOS. When I try to use the
Script Mediator within an API Resource's in-sequence, it doesn't allow me
to save the API and gives an error. The following is the error message
*Save failed. Following error(s) have been detected. Please see the error
log for more details.*
*Reason:*
*Exception initializing inline script*
And following is the content of the javascript
*![CDATA[*
*var doctorId =
mc.getPayloadJSON().createChannelRecord.doctorId.toString();*
*var patientName =
mc.getPayloadJSON().createChannelRecord.patientName.toString();*
*var date =
mc.getPayloadJSON().createChannelRecord.date.toString();*
*var time =
mc.getPayloadJSON().createChannelRecord.time.toString();*
*mc.setPayloadXML(*
*ser:createChannelRecord
xmlns:ser=http://com.example.service/ http://com.example.service/*
* doctorId{doctorId}/doctorId*
* patientName{patientName}/patientName*
* date{date}/date*
* time{time}/time*
*/ser:createChannelRecord*
* );*
*]]*
Any ideas about this error? Where can I find additional logs? The same
script works fine if I create an API using the management console of the
ESB.
Thanks,
NuwanD.
--
Nuwan Dias
Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Script Mediator Error in Developer Studio 3.7.1
Hi Nuwan,
It seems this exception occurs in ScriptMediator.java (at
org.apache.synapse.mediators.bsf - line 354) when trying to compile the
script.
*compiledScript = ((Compilable) scriptEngine).compile(scriptSourceCode);*
@Jasintha/ Viraj : This can be reproduced even in linux and any idea about
this error?
@Nuwan: The error log can be found at the workspace of the project at
/.metadata/.log
Thanks,
Sohani
Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com
Mobile : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter : https://twitter.com/sohanichristine
On Tue, Jul 28, 2015 at 5:43 AM, Nuwan Dias nuw...@wso2.com wrote:
Hi,
I'm using Developer Studio version 3.7.1 on MacOS. When I try to use the
Script Mediator within an API Resource's in-sequence, it doesn't allow me
to save the API and gives an error. The following is the error message
*Save failed. Following error(s) have been detected. Please see the error
log for more details.*
*Reason:*
*Exception initializing inline script*
And following is the content of the javascript
*![CDATA[*
*var doctorId =
mc.getPayloadJSON().createChannelRecord.doctorId.toString();*
*var patientName =
mc.getPayloadJSON().createChannelRecord.patientName.toString();*
*var date =
mc.getPayloadJSON().createChannelRecord.date.toString();*
*var time =
mc.getPayloadJSON().createChannelRecord.time.toString();*
*mc.setPayloadXML(*
*ser:createChannelRecord
xmlns:ser=http://com.example.service/ http://com.example.service/*
* doctorId{doctorId}/doctorId*
* patientName{patientName}/patientName*
* date{date}/date*
* time{time}/time*
*/ser:createChannelRecord*
* );*
*]]*
Any ideas about this error? Where can I find additional logs? The same
script works fine if I create an API using the management console of the
ESB.
Thanks,
NuwanD.
--
Nuwan Dias
Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Script Mediator Error in Developer Studio 3.7.1
Hi Jasintha, This is the error I am getting org.apache.synapse.SynapseException: Exception initializing inline script at org.apache.synapse.mediators.bsf.ScriptMediator.initInlineScript(ScriptMediator.java:365) at org.apache.synapse.mediators.bsf.ScriptMediator.init(ScriptMediator.java:152) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.ScriptMediatorTransformer.createScriptMediator(ScriptMediatorTransformer.java:58) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.ScriptMediatorTransformer.transformWithinSequence(ScriptMediatorTransformer.java:45) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.AbstractEsbNodeTransformer.doTransformWithinSequence(AbstractEsbNodeTransformer.java:118) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.SequenceTransformer.transformWithinSequence(SequenceTransformer.java:88) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.DefaultEsbModelExporter.transformSequence(DefaultEsbModelExporter.java:193) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.DefaultEsbModelExporter.designToSource(DefaultEsbModelExporter.java:349) at org.wso2.developerstudio.eclipse.gmf.esb.diagram.part.EsbMultiPageEditor.updateAssociatedXMLFile(EsbMultiPageEditor.java:593) at org.wso2.developerstudio.eclipse.gmf.esb.diagram.part.EsbMultiPageEditor.doSave(EsbMultiPageEditor.java:676) at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:154) at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:283) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374) at org.eclipse.ui.internal.WorkbenchWindow$13.run(WorkbenchWindow.java:2157) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2153) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:291) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:269) at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:159) at org.eclipse.ui.internal.WorkbenchPage.saveSaveable(WorkbenchPage.java:3915) at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3929) at org.eclipse.ui.internal.handlers.SaveHandler.execute(SaveHandler.java:54) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) 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.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at
Re: [Dev] Script Mediator Error in Developer Studio 3.7.1
On Tue, Jul 28, 2015 at 7:07 AM, Sohani Weerasinghe soh...@wso2.com wrote:
Hi Nuwan,
It seems this exception occurs in ScriptMediator.java (at
org.apache.synapse.mediators.bsf - line 354) when trying to compile the
script.
*compiledScript = ((Compilable) scriptEngine).compile(scriptSourceCode);*
if this line give an error that mean script has some issue , @Sohani what
is the error thrown by bsf ?
/Jasintha
@Jasintha/ Viraj : This can be reproduced even in linux and any idea about
this error?
@Nuwan: The error log can be found at the workspace of the project at
/.metadata/.log
Thanks,
Sohani
Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com
Mobile : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter : https://twitter.com/sohanichristine
On Tue, Jul 28, 2015 at 5:43 AM, Nuwan Dias nuw...@wso2.com wrote:
Hi,
I'm using Developer Studio version 3.7.1 on MacOS. When I try to use the
Script Mediator within an API Resource's in-sequence, it doesn't allow me
to save the API and gives an error. The following is the error message
*Save failed. Following error(s) have been detected. Please see the
error log for more details.*
*Reason:*
*Exception initializing inline script*
And following is the content of the javascript
*![CDATA[*
*var doctorId =
mc.getPayloadJSON().createChannelRecord.doctorId.toString();*
*var patientName =
mc.getPayloadJSON().createChannelRecord.patientName.toString();*
*var date =
mc.getPayloadJSON().createChannelRecord.date.toString();*
*var time =
mc.getPayloadJSON().createChannelRecord.time.toString();*
*mc.setPayloadXML(*
*ser:createChannelRecord
xmlns:ser=http://com.example.service/ http://com.example.service/*
* doctorId{doctorId}/doctorId*
* patientName{patientName}/patientName*
* date{date}/date*
* time{time}/time*
*/ser:createChannelRecord*
* );*
*]]*
Any ideas about this error? Where can I find additional logs? The same
script works fine if I create an API using the management console of the
ESB.
Thanks,
NuwanD.
--
Nuwan Dias
Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Jasintha Dasanayake*
*Senior Software EngineerWSO2 Inc. | http://wso2.com http://wso2.com/lean
. enterprise . middleware*
*mobile :- 0711368118*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fix for ESBJAVA-3957
Hi Elilmatha, PR is merged. Please resolve the issue [1] [1] https://wso2.org/jira/browse/ESBJAVA-3957 On Mon, Jul 27, 2015 at 2:25 PM, Elilmatha Sivanesan elilma...@wso2.com wrote: Hi Malaka, Please review and merge the PR [1] for $Subject. [1] https://github.com/wso2/carbon-mediation/pull/332 https://github.com/wso2/carbon-mediation/pull/332 Thank you. -- *S.Elilmatha* Associate Software Engineer, WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile 0779842221. ___ 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 Wordpress:http://chanakaudaya.wordpress.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] axis2 set-property in different scope in ScriptMediator?
Hi Folks, Inside a scriptmediator I can set-property($axis2:username, value). This variable is then available to me later on in the sequence as if it has been set on the axis2 context e.g. in the logmediator as axis2:username. However, when I then have an EntitlementMediator after the setting of this property it doesn't pick up the $axis2:username variable. It only picks it up if I set the 'username' variable in a PropertyMediator with scope axis2. Is there something special I should be doing in the scriptmediator to change the property setting or is this a bug? It feels as if the scriptmediator $axis2 is not actually the 'real' $axis2' context ? many thanks, John. John Hawkins Director: Solutions Architecture ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Does IS support session replication?
IS5(with SP) provides sso session persistence through tomcat session persistence and DB when the feature is enabled. The IS team should be able to provide more info. Thanks, Dumidu On Mon, Jul 27, 2015 at 11:29 PM, Lakshani Gamage laksh...@wso2.com wrote: Hi all, I want to use two IDPs when setting up APPM internal deployment. IDPs are fronted by an nginx. So, I have 2 options. 1. Session Replication *@IS team *- Does IS support session replication? Can we achieve that with session persistence feature? 2. Sticky Sessions (have to find how to do this with nginx) Please share your ideas. Thanks, -- Lakshani Gamage *Software Engineer* Mobile : +94 (0) 71 5478184 %2B94%20%280%29%20773%20451194 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Dumidu Handakumbura* Software Engineer - QA WSO2 Inc; http://www.wso2.com/. Mobile; *+9406740 * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Developer Studio custom mediator pack dependencies
Hi, I'v created a mediator project in order to write a custom mediator. However if I am using some dependencies(not available in ESB) how can I bundle them with the mediator jar. Dependencies were added to the pom, yet they are not bundled by default. Dependencies were bundled when I added them to export package. Is this the correct way of packing dependencies, or is there is another way I can specify which dependencies to be packed. Export-Packageorg.udara.mediation, org.mydependency/Export-Package -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Developer Studio custom mediator pack dependencies
Hi Udara, This is ok too, but AFAIK it's better to use Private-Packageorg.foo.myproject.*/Private-Package as in [1] o that those classes won't get exposed to others(Since only you need these packages). Or either you can use Embed-Dependencydependencies/Embed-Dependency as well. Then those jars will be embedded in the osgi jar [1] - http://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html Thanks, On Tue, Jul 28, 2015 at 10:36 AM, Udara Liyanage ud...@wso2.com wrote: Hi, I'v created a mediator project in order to write a custom mediator. However if I am using some dependencies(not available in ESB) how can I bundle them with the mediator jar. Dependencies were added to the pom, yet they are not bundled by default. Dependencies were bundled when I added them to export package. Is this the correct way of packing dependencies, or is there is another way I can specify which dependencies to be packed. Export-Packageorg.udara.mediation, org.mydependency/Export-Package -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Does IS support session replication?
Can you please elaborate more on your requirement ? Are you referring to the session maintained by authentication framework ?. In brief, yes, IS supports session replication and session persistence (IS 5.0.0). Session persistence can be achieved by installing SP 1 and enabling required configurations. But the answer depends on your use case. On Tue, Jul 28, 2015 at 10:23 AM, Dumidu Handakumbura dum...@wso2.com wrote: IS5(with SP) provides sso session persistence through tomcat session persistence and DB when the feature is enabled. The IS team should be able to provide more info. Thanks, Dumidu On Mon, Jul 27, 2015 at 11:29 PM, Lakshani Gamage laksh...@wso2.com wrote: Hi all, I want to use two IDPs when setting up APPM internal deployment. IDPs are fronted by an nginx. So, I have 2 options. 1. Session Replication *@IS team *- Does IS support session replication? Can we achieve that with session persistence feature? 2. Sticky Sessions (have to find how to do this with nginx) Please share your ideas. Thanks, -- Lakshani Gamage *Software Engineer* Mobile : +94 (0) 71 5478184 %2B94%20%280%29%20773%20451194 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Dumidu Handakumbura* Software Engineer - QA WSO2 Inc; http://www.wso2.com/. Mobile; *+9406740 %2B9406740 * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hasintha Indrajee Software Engineer WSO2, Inc. Mobile:+94 771892453 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Finding tomcat version of Carbon products
Hi, How do we find the tomcat version of Carbon products rather than searching for the jar in plugins folder. Don't we mention the tomcat version of Carbon products at any configuration file? -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Tharindu Dharmarathna
Hi, It is with great pleasure we welcome Tharindu Dharmarathna as a WSO2 Committer. @Tharindu, congratulations and keep up the good work! Thanks, NuwanD. -- Nuwan Dias Technical Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Tharindu Dharmarathna
Congratulations! On Tue, Jul 28, 2015 at 10:47 AM, Nuwan Dias nuw...@wso2.com wrote: Hi, It is with great pleasure we welcome Tharindu Dharmarathna as a WSO2 Committer. @Tharindu, congratulations and keep up the good work! Thanks, NuwanD. -- Nuwan Dias Technical Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Roshan Wijesena. Senior Software Engineer-WSO2 Inc. Mobile: *+94719154640* Email: ros...@wso2.com *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [PPaaS] Need to update Private PaaS P2 profile to refer Stratos 4.1.0 Features
I have now done this modification with the following commit revision: https://github.com/wso2/product-private-paas/commit/376eb325d00f8251e5c0a2f9e3e7d2134efb9935 On Mon, Jul 27, 2015 at 1:48 PM, Imesh Gunaratne im...@wso2.com wrote: Hi Devs, Apache Stratos 4.1.0 is was released few days back [1]. Now we can update Private PaaS product's P2 profile [2] to use Stratos 4.1.0 features. It would be better if we can introduce a maven property to configure this. [1] https://dist.apache.org/repos/dist/release/stratos/4.1.0/ [2] https://github.com/wso2/product-private-paas/tree/master/products/ppaas/modules/p2-profile-gen 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 -- *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] CEP 400 (Beta) NotStormManagerException
Hi Imesh,
We select coordinator among managers.
Thanks
*,Sajith Ravindra*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
mobile: +94 77 2273550
blog: http://sajithr.blogspot.com/
http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
On Mon, Jul 27, 2015 at 4:37 PM, Imesh Gunaratne im...@wso2.com wrote:
Hi Suho,
Do we select a coordinator within the manager nodes or is it just the
client that decides which manager to talk to?
Thanks
On Mon, Jul 27, 2015 at 2:45 PM, Sriskandarajah Suhothayan s...@wso2.com
wrote:
CEP Managers are must for Strom based coordination, so use the CEP
Managers to be the carbon cluster as well-known members, else it does not
make sense for CEP deployment. We have also done the testing like that.
Regards
Suho
On Mon, Jul 27, 2015 at 2:16 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 2:15 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
+1 Azeez
[I mean adding Azeez into the loop]
On Mon, Jul 27, 2015 at 2:07 PM, Lasindu Charith lasi...@wso2.com
wrote:
Hi all,
We are having a clustered deployment of CEP 400 Beta in Stratos
4.1.0(in Kubernetes), similar to following. Instead of using hazelcast
clustering, I'm using 'Stratos Membership scheme' [1] which considers all
the members in the carbon cluster as well-known members. I have done CEP
Distributed deployment according to [3][4].
[image: Inline image 1]
When CEP workers start up, I can see the following log [2] in worker
nodes. 10.244.28.23/24 are manager IPs. When the CEP managers are
restarted, the error goes away(Workers can connect to CEP Manager).
According to above membership scheme, any of the CEP workers/managers
can be the hazelcast coordinator. *Does CEP requires a member who is
both CEP manager as well as a hazelcast coordinator to be elected as the
Storm manager? *
Should CEP workers be always non-wka? How can we overcome this issue?
[1] [Architecture] Stratos Membership Scheme for Automatically
Discovering Carbon Instances in a Carbon Cluster
[2]
TID: [-1] [] [2015-07-27 04:51:11,885] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher
with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:16,887] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next
manager
NotStormManagerException(message:10.244.28.23:8904 not a storm
manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.3.29:8904. Trying next
manager
NotStormManagerException(message:10.244.3.29:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
at
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.1 RC1
Hi Lasnatha, Yes we should generate the correct licende.txt file with the RC1. But we are unable to generate the LICENSE.txt at the moment. Therefore we will generate it and update the pack by tomorrow. Since this is not a blocker for the testing could you guys please carry on the testing and let us know if there are any blockers. We will send a new voting mail as soon as we generate the new license.txt Thanks On Tue, Jul 28, 2015 at 1:59 AM, Lasantha Fernando lasan...@wso2.com wrote: I tested out the basic functionality of the carbon management console and also tested the basic functionality of OSGi console and it is working fine... :-). But I don't think we can proceed with the vote until the license is updated, right? Thanks, Lasantha On 28 July 2015 at 01:42, Lasantha Fernando lasan...@wso2.com wrote: Hi guys, I don't think LICENSE.txt file within the pack has been updated for the 4.4.1 version. Shouldn't we be updating that as well for the RC pack? Thanks, Lasantha On 28 July 2015 at 00:23, Thusitha Thilina Dayaratne thusit...@wso2.com wrote: Hi Devs, WSO2 Carbon Kernel 4.4.1. RC1 Release Vote This release fixes the following issues: https://wso2.org/jira/issues/?filter=12323 Please download kernel RC1 and test your products with the kernel 4.4.1 RC1 and vote. Vote will be open for 72 hours or as needed. *Source binary distribution files:* http://maven.wso2.org/nexus/content/repositories/staging/org/wso2/carbon/wso2carbon/4.4.1/ *Maven staging repository:* http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-012/ *The tag to be voted upon :* https://github.com/wso2/carbon4-kernel/tree/v4.4.1-RC1 [ ] Broken - do not release (explain why) [ ] Stable - go ahead and release Thanks, Best Regards Carbon Team. -- Thusitha Dayaratne Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com Mobile +94712756809 Blog alokayasoya.blogspot.com Abouthttp://about.me/thusithathilina ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Senior Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 -- *Lasantha Fernando* Senior Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 -- Thusitha Dayaratne Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com Mobile +94712756809 Blog alokayasoya.blogspot.com Abouthttp://about.me/thusithathilina ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] CEP 400 (Beta) NotStormManagerException
There was a bug where coordinator was trying to be come coordinator again
and failing, fixed and gave a patch to Lasindu
Suho
- Sent from phone -
On Jul 28, 2015 10:55 AM, Sajith Ravindra saji...@wso2.com wrote:
Hi Imesh,
We select coordinator among managers.
Thanks
*,Sajith Ravindra*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
mobile: +94 77 2273550
blog: http://sajithr.blogspot.com/
http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
On Mon, Jul 27, 2015 at 4:37 PM, Imesh Gunaratne im...@wso2.com wrote:
Hi Suho,
Do we select a coordinator within the manager nodes or is it just the
client that decides which manager to talk to?
Thanks
On Mon, Jul 27, 2015 at 2:45 PM, Sriskandarajah Suhothayan s...@wso2.com
wrote:
CEP Managers are must for Strom based coordination, so use the CEP
Managers to be the carbon cluster as well-known members, else it does not
make sense for CEP deployment. We have also done the testing like that.
Regards
Suho
On Mon, Jul 27, 2015 at 2:16 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 2:15 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
+1 Azeez
[I mean adding Azeez into the loop]
On Mon, Jul 27, 2015 at 2:07 PM, Lasindu Charith lasi...@wso2.com
wrote:
Hi all,
We are having a clustered deployment of CEP 400 Beta in Stratos
4.1.0(in Kubernetes), similar to following. Instead of using hazelcast
clustering, I'm using 'Stratos Membership scheme' [1] which considers all
the members in the carbon cluster as well-known members. I have done CEP
Distributed deployment according to [3][4].
[image: Inline image 1]
When CEP workers start up, I can see the following log [2] in worker
nodes. 10.244.28.23/24 are manager IPs. When the CEP managers are
restarted, the error goes away(Workers can connect to CEP Manager).
According to above membership scheme, any of the CEP workers/managers
can be the hazelcast coordinator. *Does CEP requires a member who is
both CEP manager as well as a hazelcast coordinator to be elected as the
Storm manager? *
Should CEP workers be always non-wka? How can we overcome this issue?
[1] [Architecture] Stratos Membership Scheme for Automatically
Discovering Carbon Instances in a Carbon Cluster
[2]
TID: [-1] [] [2015-07-27 04:51:11,885] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher
with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:16,887] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next
manager
NotStormManagerException(message:10.244.28.23:8904 not a storm
manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at
org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.3.29:8904. Trying next
manager
NotStormManagerException(message:10.244.3.29:8904 not a storm
manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at
org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
Re: [Dev] CEP 400 (Beta) NotStormManagerException
Thanks Sajith/Tishan/Suho,
This issue is now fixed. I have verified it in the latest build.
Thanks,
On Tue, Jul 28, 2015 at 10:55 AM, Sajith Ravindra saji...@wso2.com wrote:
Hi Imesh,
We select coordinator among managers.
Thanks
*,Sajith Ravindra*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
mobile: +94 77 2273550
blog: http://sajithr.blogspot.com/
http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
On Mon, Jul 27, 2015 at 4:37 PM, Imesh Gunaratne im...@wso2.com wrote:
Hi Suho,
Do we select a coordinator within the manager nodes or is it just the
client that decides which manager to talk to?
Thanks
On Mon, Jul 27, 2015 at 2:45 PM, Sriskandarajah Suhothayan s...@wso2.com
wrote:
CEP Managers are must for Strom based coordination, so use the CEP
Managers to be the carbon cluster as well-known members, else it does not
make sense for CEP deployment. We have also done the testing like that.
Regards
Suho
On Mon, Jul 27, 2015 at 2:16 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 2:15 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
+1 Azeez
[I mean adding Azeez into the loop]
On Mon, Jul 27, 2015 at 2:07 PM, Lasindu Charith lasi...@wso2.com
wrote:
Hi all,
We are having a clustered deployment of CEP 400 Beta in Stratos
4.1.0(in Kubernetes), similar to following. Instead of using hazelcast
clustering, I'm using 'Stratos Membership scheme' [1] which considers all
the members in the carbon cluster as well-known members. I have done CEP
Distributed deployment according to [3][4].
[image: Inline image 1]
When CEP workers start up, I can see the following log [2] in worker
nodes. 10.244.28.23/24 are manager IPs. When the CEP managers are
restarted, the error goes away(Workers can connect to CEP Manager).
According to above membership scheme, any of the CEP workers/managers
can be the hazelcast coordinator. *Does CEP requires a member who is
both CEP manager as well as a hazelcast coordinator to be elected as the
Storm manager? *
Should CEP workers be always non-wka? How can we overcome this issue?
[1] [Architecture] Stratos Membership Scheme for Automatically
Discovering Carbon Instances in a Carbon Cluster
[2]
TID: [-1] [] [2015-07-27 04:51:11,885] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher
with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:16,887] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next
manager
NotStormManagerException(message:10.244.28.23:8904 not a storm
manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at
org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.3.29:8904. Trying next
manager
NotStormManagerException(message:10.244.3.29:8904 not a storm
manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at
org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
Re: [Dev] Script Mediator Error in Developer Studio 3.7.1
I doubt its due to the CDATA tags. I tried both with and without CDATA tags, but it throws the same error always. I even tried providing the content through the source editor, but saving from the source editor also gives the same error. Please note that an API with the exact configuration can be deployed on ESB 4.8.1 without any issues. However, for the script to execute correctly the CDATA tags are required. If the CDATA tags were missing, it would throw the following exception at runtime (only). *org.mozilla.javascript.EvaluatorException: Can't find method org.apache.synapse.mediators.bsf.ScriptMessageContext.setPayloadXML().* Thanks, NuwanD. On Tue, Jul 28, 2015 at 7:45 AM, Sohani Weerasinghe soh...@wso2.com wrote: Hi Jasintha, This is the error I am getting org.apache.synapse.SynapseException: Exception initializing inline script at org.apache.synapse.mediators.bsf.ScriptMediator.initInlineScript(ScriptMediator.java:365) at org.apache.synapse.mediators.bsf.ScriptMediator.init(ScriptMediator.java:152) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.ScriptMediatorTransformer.createScriptMediator(ScriptMediatorTransformer.java:58) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.ScriptMediatorTransformer.transformWithinSequence(ScriptMediatorTransformer.java:45) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.AbstractEsbNodeTransformer.doTransformWithinSequence(AbstractEsbNodeTransformer.java:118) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.SequenceTransformer.transformWithinSequence(SequenceTransformer.java:88) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.DefaultEsbModelExporter.transformSequence(DefaultEsbModelExporter.java:193) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.DefaultEsbModelExporter.designToSource(DefaultEsbModelExporter.java:349) at org.wso2.developerstudio.eclipse.gmf.esb.diagram.part.EsbMultiPageEditor.updateAssociatedXMLFile(EsbMultiPageEditor.java:593) at org.wso2.developerstudio.eclipse.gmf.esb.diagram.part.EsbMultiPageEditor.doSave(EsbMultiPageEditor.java:676) at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:154) at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:283) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374) at org.eclipse.ui.internal.WorkbenchWindow$13.run(WorkbenchWindow.java:2157) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2153) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:291) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:269) at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:159) at org.eclipse.ui.internal.WorkbenchPage.saveSaveable(WorkbenchPage.java:3915) at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3929) at org.eclipse.ui.internal.handlers.SaveHandler.execute(SaveHandler.java:54) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) 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.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at
Re: [Dev] [DAS 3.0.0 Beta] No FileSystem for scheme: file
Hi Gokul,
Thanks for the reply.
Yes this runs on a HBase cluster. I have added the properties and it fixed
the No FileSystem for scheme: file Error. Now I am getting following error.
org.wso2.carbon.analytics.datasource.commons.exception.AnalyticsException:
Error checking existence of table __SHARD_INDEX_UPDATE_RECORDS__1 for
tenant -1000
at
org.wso2.carbon.analytics.datasource.hbase.HBaseAnalyticsRecordStore.tableExists(HBaseAnalyticsRecordStore.java:126)
at
org.wso2.carbon.analytics.datasource.hbase.HBaseAnalyticsRecordStore.get(HBaseAnalyticsRecordStore.java:274)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer.loadIndexOperationRecords(AnalyticsDataIndexer.java:554)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer.loadIndexOperationUpdateRecords(AnalyticsDataIndexer.java:519)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer.loadIndexOperationUpdateRecords(AnalyticsDataIndexer.java:515)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer.processIndexUpdateOperations(AnalyticsDataIndexer.java:403)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer.processIndexOperations(AnalyticsDataIndexer.java:491)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer.access$200(AnalyticsDataIndexer.java:118)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer$IndexWorker.run(AnalyticsDataIndexer.java:1744)
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: org.apache.hadoop.hbase.client.RetriesExhaustedException: Can't
get the locations
at
org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.getRegionLocations(RpcRetryingCallerWithReadReplicas.java:305)
at
org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:131)
at
org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:56)
at
org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:200)
at org.apache.hadoop.hbase.client.ClientScanner.call(ClientScanner.java:287)
at
org.apache.hadoop.hbase.client.ClientScanner.nextScanner(ClientScanner.java:267)
at
org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:139)
at
org.apache.hadoop.hbase.client.ClientScanner.init(ClientScanner.java:134)
at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:823)
at
org.apache.hadoop.hbase.MetaTableAccessor.fullScan(MetaTableAccessor.java:601)
at
org.apache.hadoop.hbase.MetaTableAccessor.tableExists(MetaTableAccessor.java:365)
at
org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:281)
at
org.wso2.carbon.analytics.datasource.hbase.HBaseAnalyticsRecordStore.tableExists(HBaseAnalyticsRecordStore.java:123)
... 11 more
On Mon, Jul 27, 2015 at 10:54 AM, Gokul Balakrishnan go...@wso2.com wrote:
Hi Anuruddha,
Are you running HBase on a cluster (i.e. on top of HDFS)? If yes, can you
ensure that you have the following in the analytics-datasource.xml for the
HBase datasource?
property
namefs.hdfs.impl/name
valueorg.apache.hadoop.hdfs.DistributedFileSystem/value
/property
property
namefs.file.impl/name
valueorg.apache.hadoop.fs.LocalFileSystem/value
/property
Thanks,
On 27 July 2015 at 10:43, Anuruddha Liyanarachchi anurudd...@wso2.com
wrote:
Hi DAS team,
I have created DAS receiver and analytics cluster as in the diagram [1].
In the setup DAS receivers are connected to MySQL (FS_DB) and HBase
(EventStore).
I am getting following errors when I start DAS receivers. What could be
the reason for this error ?
I have attached the carbon log as well.
TID: [-1] [] [2015-07-27 04:37:40,838] WARN
{org.apache.hadoop.hbase.util.DynamicClassLoader} - Failed to identify the
fs of dir /opt/wso2das-3.0.0-SNAPSHOT/tmp/hbase-root/hbase/lib, ignored
{org.apac
he.hadoop.hbase.util.DynamicClassLoader}
java.io.IOException: No FileSystem for scheme: file
at
org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:2584)
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2591)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:91)
at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2630)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2612)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:370)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:169)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:354)
at org.apache.hadoop.fs.Path.getFileSystem(Path.java:296)
at
org.apache.hadoop.hbase.util.DynamicClassLoader.init(DynamicClassLoader.java:104)
at
org.apache.hadoop.hbase.protobuf.ProtobufUtil.clinit(ProtobufUtil.java:229)
at
Re: [Dev] [DEV][DAS] Spark cluster in DAS does not have worker nodes
Hi Maheshakya, I will look into this. According to your setting, the ideal scenario is, node1 - spark master (active) + worker node2 - spark master (standby) + worker node3 - worker did you start the servers all at once or one by one? rgds On Mon, Jul 27, 2015 at 11:07 AM, Anjana Fernando anj...@wso2.com wrote: Hi, Actually, when the 3'rd sever has started up, all 3 servers should have worker instances. This seems to be a bug. @Niranda, please check it out ASAP. Cheers, Anjana. On Mon, Jul 27, 2015 at 11:01 AM, Maheshakya Wijewardena mahesha...@wso2.com wrote: Hi, I have tried to create a Spark cluster with DAS using Carbon clustering. 3 DAS nodes are configured and number of Spark masters is set to 2. In this setting, one of the 3 nodes should have a Spark worker node, but all 3 nodes are starting as Spark masters. What can be the reason for this? Configuration files (one of *axis2.xml* files of DAS clusters and *spark-defaults.conf*) of DAS are attached herewith. Best regards. -- Pruthuvi Maheshakya Wijewardena Software Engineer WSO2 : http://wso2.com/ Email: mahesha...@wso2.com Mobile: +94711228855 -- *Anjana Fernando* Senior Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware -- *Niranda Perera* Software Engineer, WSO2 Inc. Mobile: +94-71-554-8430 Twitter: @n1r44 https://twitter.com/N1R44 https://pythagoreanscript.wordpress.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][DAS] Spark cluster in DAS does not have worker nodes
Hi Niranda, I started those one by one. On Mon, Jul 27, 2015 at 12:07 PM, Niranda Perera nira...@wso2.com wrote: Hi Maheshakya, I will look into this. According to your setting, the ideal scenario is, node1 - spark master (active) + worker node2 - spark master (standby) + worker node3 - worker did you start the servers all at once or one by one? rgds On Mon, Jul 27, 2015 at 11:07 AM, Anjana Fernando anj...@wso2.com wrote: Hi, Actually, when the 3'rd sever has started up, all 3 servers should have worker instances. This seems to be a bug. @Niranda, please check it out ASAP. Cheers, Anjana. On Mon, Jul 27, 2015 at 11:01 AM, Maheshakya Wijewardena mahesha...@wso2.com wrote: Hi, I have tried to create a Spark cluster with DAS using Carbon clustering. 3 DAS nodes are configured and number of Spark masters is set to 2. In this setting, one of the 3 nodes should have a Spark worker node, but all 3 nodes are starting as Spark masters. What can be the reason for this? Configuration files (one of *axis2.xml* files of DAS clusters and *spark-defaults.conf*) of DAS are attached herewith. Best regards. -- Pruthuvi Maheshakya Wijewardena Software Engineer WSO2 : http://wso2.com/ Email: mahesha...@wso2.com Mobile: +94711228855 -- *Anjana Fernando* Senior Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware -- *Niranda Perera* Software Engineer, WSO2 Inc. Mobile: +94-71-554-8430 Twitter: @n1r44 https://twitter.com/N1R44 https://pythagoreanscript.wordpress.com/ -- Pruthuvi Maheshakya Wijewardena Software Engineer WSO2 : http://wso2.com/ Email: mahesha...@wso2.com Mobile: +94711228855 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DAS 3.0.0 Beta] No FileSystem for scheme: file
Hi Anuruddha,
This seems to be an issue with the HBase cluster itself rather than an
integration issue. Could you check the HBase logs and see if anything is
reported there? In any case, please also specify the zookeeper quorum
property as well (hbase.zookeeper.quorum and specify the zk nodes)
Thanks,
On 27 July 2015 at 11:45, Anuruddha Liyanarachchi anurudd...@wso2.com
wrote:
Hi Gokul,
Thanks for the reply.
Yes this runs on a HBase cluster. I have added the properties and it fixed
the No FileSystem for scheme: file Error. Now I am getting following error.
org.wso2.carbon.analytics.datasource.commons.exception.AnalyticsException:
Error checking existence of table __SHARD_INDEX_UPDATE_RECORDS__1 for
tenant -1000
at
org.wso2.carbon.analytics.datasource.hbase.HBaseAnalyticsRecordStore.tableExists(HBaseAnalyticsRecordStore.java:126)
at
org.wso2.carbon.analytics.datasource.hbase.HBaseAnalyticsRecordStore.get(HBaseAnalyticsRecordStore.java:274)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer.loadIndexOperationRecords(AnalyticsDataIndexer.java:554)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer.loadIndexOperationUpdateRecords(AnalyticsDataIndexer.java:519)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer.loadIndexOperationUpdateRecords(AnalyticsDataIndexer.java:515)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer.processIndexUpdateOperations(AnalyticsDataIndexer.java:403)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer.processIndexOperations(AnalyticsDataIndexer.java:491)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer.access$200(AnalyticsDataIndexer.java:118)
at
org.wso2.carbon.analytics.dataservice.indexing.AnalyticsDataIndexer$IndexWorker.run(AnalyticsDataIndexer.java:1744)
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: org.apache.hadoop.hbase.client.RetriesExhaustedException: Can't
get the locations
at
org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.getRegionLocations(RpcRetryingCallerWithReadReplicas.java:305)
at
org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:131)
at
org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:56)
at
org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:200)
at
org.apache.hadoop.hbase.client.ClientScanner.call(ClientScanner.java:287)
at
org.apache.hadoop.hbase.client.ClientScanner.nextScanner(ClientScanner.java:267)
at
org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:139)
at
org.apache.hadoop.hbase.client.ClientScanner.init(ClientScanner.java:134)
at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:823)
at
org.apache.hadoop.hbase.MetaTableAccessor.fullScan(MetaTableAccessor.java:601)
at
org.apache.hadoop.hbase.MetaTableAccessor.tableExists(MetaTableAccessor.java:365)
at
org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:281)
at
org.wso2.carbon.analytics.datasource.hbase.HBaseAnalyticsRecordStore.tableExists(HBaseAnalyticsRecordStore.java:123)
... 11 more
On Mon, Jul 27, 2015 at 10:54 AM, Gokul Balakrishnan go...@wso2.com
wrote:
Hi Anuruddha,
Are you running HBase on a cluster (i.e. on top of HDFS)? If yes, can you
ensure that you have the following in the analytics-datasource.xml for the
HBase datasource?
property
namefs.hdfs.impl/name
valueorg.apache.hadoop.hdfs.DistributedFileSystem/value
/property
property
namefs.file.impl/name
valueorg.apache.hadoop.fs.LocalFileSystem/value
/property
Thanks,
On 27 July 2015 at 10:43, Anuruddha Liyanarachchi anurudd...@wso2.com
wrote:
Hi DAS team,
I have created DAS receiver and analytics cluster as in the diagram [1].
In the setup DAS receivers are connected to MySQL (FS_DB) and HBase
(EventStore).
I am getting following errors when I start DAS receivers. What could be
the reason for this error ?
I have attached the carbon log as well.
TID: [-1] [] [2015-07-27 04:37:40,838] WARN
{org.apache.hadoop.hbase.util.DynamicClassLoader} - Failed to identify the
fs of dir /opt/wso2das-3.0.0-SNAPSHOT/tmp/hbase-root/hbase/lib, ignored
{org.apac
he.hadoop.hbase.util.DynamicClassLoader}
java.io.IOException: No FileSystem for scheme: file
at
org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:2584)
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2591)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:91)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2630)
at
Re: [Dev] Does IS has mutual authenticator packed in IS 5.1.0 disctribution?
Hi Tharindu
On Sun, Apr 26, 2015 at 9:11 AM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Firzan,
The custom secret callback handler should be included in
authenticanendpoint/WEB-INF/lib directory only if secure vault is added. We
should write proper documentation for enabling secure vault for the
dropdown feature and mention that. However the error handling of the
feature is improved than the service pack when comes to the next release of
IS.
Where can I get CustomSecretCallbackHandler jar? I couldn't find it in
SP01. The pre-configured IS pack [1] has TenantConfig.properties file which
references org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler.
It throws following CNF exceptions since the jar is not included anywhere.
Please advice.
TID: [0] [IS] [2015-07-26 08:28:18,874] ERROR
{org.wso2.securevault.secret.SecretCallbackHandlerFactory} - A
SecretCallbackHandler cannot be found for class name :
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
{org.wso2.securevault.secret.SecretCallbackHandlerFactory}
java.lang.ClassNotFoundException:
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
at
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:138)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
at
org.wso2.securevault.secret.SecretCallbackHandlerFactory.createSecretCallbackHandler(SecretCallbackHandlerFactory.java:62)
at
org.wso2.securevault.SecretResolverFactory.initPasswordManager(SecretResolverFactory.java:278)
at
org.wso2.securevault.SecretResolverFactory.create(SecretResolverFactory.java:218)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.resolveSecrets(TenantDataManager.java:282)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.init(TenantDataManager.java:88)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.isTenantListEnabled(TenantDataManager.java:267)
at org.apache.jsp.login_jsp._jspService(org.apache.jsp.login_jsp:329)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:412)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at
org.wso2.carbon.identity.application.authentication.endpoint.oauth2.OAuth2Login.doGet(OAuth2Login.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:412)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at
org.wso2.carbon.identity.application.authentication.endpoint.AuthenticationEndpoint.doGet(AuthenticationEndpoint.java:82)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
[Dev] [PPaaS] Need to update Private PaaS P2 profile to refer Stratos 4.1.0 Features
Hi Devs, Apache Stratos 4.1.0 is was released few days back [1]. Now we can update Private PaaS product's P2 profile [2] to use Stratos 4.1.0 features. It would be better if we can introduce a maven property to configure this. [1] https://dist.apache.org/repos/dist/release/stratos/4.1.0/ [2] https://github.com/wso2/product-private-paas/tree/master/products/ppaas/modules/p2-profile-gen 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] How to handle REST_URL_POSTFIX property when Query Parameter values are defined
In conclusion we will handling this in the following way,
if a given endpoint URL contains a ? character we will ideitify this as a
scenario where query parameters are used and we will add the property
name=REST_URL_POSTFIX scope=axis2 action=remove/ so that it applied
for the given endpoint.
This will be handled at velocity template level.
On 24 July 2015 at 15:04, Uvindra Dias Jayasinha uvin...@wso2.com wrote:
I found the following on SO[1] which is the exact same problem we are
discussing here. The solution for it provided here[2]. So is this the way
we should go about it? We can adjust our velocity_template to generate the
synapse config conditionally. That way no need to do any changes to
publisher and the fix will be seamless from a user perspective.
[1]
http://stackoverflow.com/questions/19978652/wso2-esb-http-endpoint-uri-parameters
[2]
http://stackoverflow.com/questions/19774923/wso2-esb-4-7-0-api-url-mapping
On 24 July 2015 at 14:49, Uvindra Dias Jayasinha uvin...@wso2.com wrote:
Ok so from what you saying is that even though we are setting that
attribute at resource level it is not getting considered at endpoint level.
So have been doing things incorrectly? How is the correct way of achieving
this functionality with synapse?
On 24 July 2015 at 14:46, Isuru Udana isu...@wso2.com wrote:
It's related to the API Resource not to the HTTP Endpoint.
Please note that there is no relationship between how we define resource
url (whether it is url-template or url-mapping) with the HTTP Endpoint url.
And we can't even introduce a such relationship.
On Fri, Jul 24, 2015 at 2:41 PM, Uvindra Dias Jayasinha
uvin...@wso2.com wrote:
Im referring to the attribute in the* resource* tag, that how we are
triggering the different functionalities
On 24 July 2015 at 14:39, Isuru Udana isu...@wso2.com wrote:
In both scenarios you can see, HTTP Endpoint contains an url-template.
endpoint name=admin--pathParam_APIproductionEndpoint_0
http uri-template=
http://ws.cdyne.com/phoneverify/phoneverify.asmx?name={uri.var.name}
/
/endpoint
endpoint name=admin--noPathParam_APIproductionEndpoint_0
http uri-template=
http://ws.cdyne.com/phoneverify/phoneverify.asmx/
/endpoint
On Fri, Jul 24, 2015 at 2:35 PM, Uvindra Dias Jayasinha
uvin...@wso2.com wrote:
Attached are two synpase files generated with API Manager for the
above use cases. Ok end of the day we need to support both attributes,
its
critical to API Manager functionality. Do you agree that from a
functional
perspective our expectation is correct? Because there is nothing to stop
someone from writing an API in this manner.
On 24 July 2015 at 14:23, Isuru Udana isu...@wso2.com wrote:
On Fri, Jul 24, 2015 at 2:10 PM, Uvindra Dias Jayasinha
uvin...@wso2.com wrote:
In our velocity template we are conditionally deciding when the
url-mapping attribute or uri-template attribute should be used in the
synapse config generated for each API, eher is the velocity template
logic,
#if($resource.getUriTemplate().contains({) ||
($resource.getUriTemplate().contains(*)
!$resource.getUriTemplate().endsWith(/*)))
*uri-template=*$resource.getUriTemplate()
#else
*url-mapping=*$resource.getUriTemplate()
#end
So we are specifying this attribute based on API Managers
requirement. The synapse engine does not consider this as invalid
so we expect that the synapse engine should honour the attribute
defined.
HTTP Endpoint in synapse doesn't support url-mapping attribute. Can
you post a sample generated API Config with this ?
So we need the functionality of both the uri-template and
url-mapping attributes for our HTTP endpoint based APIs, but not at the
same time obviously. Its either one or the other for a given resource.
There is no relationship between API resources and HTTP endpoint
By specifying these two attributes we are already implying that we
are expecting different functionality(the user expects the same). So
its a
bit difficult justifying having to manually set this from the
publisher.
WDYT?
+1. If we can handle this automatically without a user interaction,
that's the best way to handle it. And we need to consider the impact of
the
changes (config migration issues, etc.)
On 24 July 2015 at 13:45, Isuru Udana isu...@wso2.com wrote:
Hi Uvindra,
I think the correct approach is to completely remove
REST_URL_POSTFIX getting appended for HTTP Endpoint. And append only
if the
user configure to do so.
Initially we implemented HTTP Endpoint in that way. But somehow
implementation has changed now.
I am not sure whether we are too late to revert to the original
implementation now.
If we cannot revert back,
For ESB, we can simply remove the REST_URL_POSTFIX from the config
and for AM, we need a easy way to do that from UI.
On Fri, Jul 24,
[Dev] CEP 400 (Beta) NotStormManagerException
Hi all,
We are having a clustered deployment of CEP 400 Beta in Stratos 4.1.0(in
Kubernetes), similar to following. Instead of using hazelcast clustering,
I'm using 'Stratos Membership scheme' [1] which considers all the members
in the carbon cluster as well-known members. I have done CEP Distributed
deployment according to [3][4].
[image: Inline image 1]
When CEP workers start up, I can see the following log [2] in worker nodes.
10.244.28.23/24 are manager IPs. When the CEP managers are restarted, the
error goes away(Workers can connect to CEP Manager).
According to above membership scheme, any of the CEP workers/managers can
be the hazelcast coordinator. *Does CEP requires a member who is both CEP
manager as well as a hazelcast coordinator to be elected as the Storm
manager? *
Should CEP workers be always non-wka? How can we overcome this issue?
[1] [Architecture] Stratos Membership Scheme for Automatically Discovering
Carbon Instances in a Carbon Cluster
[2]
TID: [-1] [] [2015-07-27 04:51:11,885] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:16,887] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next manager
NotStormManagerException(message:10.244.28.23:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.3.29:8904. Trying next manager
NotStormManagerException(message:10.244.3.29:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:21,892] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next manager
NotStormManagerException(message:10.244.28.23:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
[Dev] Fix for ESBJAVA-3957
Hi Malaka, Please review and merge the PR [1] for $Subject. [1] https://github.com/wso2/carbon-mediation/pull/332 https://github.com/wso2/carbon-mediation/pull/332 Thank you. -- *S.Elilmatha* Associate Software Engineer, WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile 0779842221. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Does IS has mutual authenticator packed in IS 5.1.0 disctribution?
On Mon, Jul 27, 2015 at 2:22 PM, Samuel Gnaniah sam...@wso2.com wrote:
Adding TharinduA.
*Samuel Gnaniah*
Lead Technical Writer
WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798
On Mon, Jul 27, 2015 at 12:33 PM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
Hi Tharindu
On Sun, Apr 26, 2015 at 9:11 AM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Firzan,
The custom secret callback handler should be included in
authenticanendpoint/WEB-INF/lib directory only if secure vault is added. We
should write proper documentation for enabling secure vault for the
dropdown feature and mention that. However the error handling of the
feature is improved than the service pack when comes to the next release of
IS.
Where can I get CustomSecretCallbackHandler jar?
Check :
https://wso2.org/jira/browse/IDENTITY-2981?focusedCommentId=95432page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-95432
Thanks,
Darshana.
I couldn't find it in SP01. The pre-configured IS pack [1] has
TenantConfig.properties file which references
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler. It throws
following CNF exceptions since the jar is not included anywhere. Please
advice.
TID: [0] [IS] [2015-07-26 08:28:18,874] ERROR
{org.wso2.securevault.secret.SecretCallbackHandlerFactory} - A
SecretCallbackHandler cannot be found for class name :
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
{org.wso2.securevault.secret.SecretCallbackHandlerFactory}
java.lang.ClassNotFoundException:
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
at
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:138)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
at
org.wso2.securevault.secret.SecretCallbackHandlerFactory.createSecretCallbackHandler(SecretCallbackHandlerFactory.java:62)
at
org.wso2.securevault.SecretResolverFactory.initPasswordManager(SecretResolverFactory.java:278)
at
org.wso2.securevault.SecretResolverFactory.create(SecretResolverFactory.java:218)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.resolveSecrets(TenantDataManager.java:282)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.init(TenantDataManager.java:88)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.isTenantListEnabled(TenantDataManager.java:267)
at org.apache.jsp.login_jsp._jspService(org.apache.jsp.login_jsp:329)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:412)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at
org.wso2.carbon.identity.application.authentication.endpoint.oauth2.OAuth2Login.doGet(OAuth2Login.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:412)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at
org.wso2.carbon.identity.application.authentication.endpoint.AuthenticationEndpoint.doGet(AuthenticationEndpoint.java:82)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
Re: [Dev] CEP 400 (Beta) NotStormManagerException
+1 Azeez
On Mon, Jul 27, 2015 at 2:07 PM, Lasindu Charith lasi...@wso2.com wrote:
Hi all,
We are having a clustered deployment of CEP 400 Beta in Stratos 4.1.0(in
Kubernetes), similar to following. Instead of using hazelcast clustering,
I'm using 'Stratos Membership scheme' [1] which considers all the members
in the carbon cluster as well-known members. I have done CEP Distributed
deployment according to [3][4].
[image: Inline image 1]
When CEP workers start up, I can see the following log [2] in worker
nodes. 10.244.28.23/24 are manager IPs. When the CEP managers are
restarted, the error goes away(Workers can connect to CEP Manager).
According to above membership scheme, any of the CEP workers/managers can
be the hazelcast coordinator. *Does CEP requires a member who is both CEP
manager as well as a hazelcast coordinator to be elected as the Storm
manager? *
Should CEP workers be always non-wka? How can we overcome this issue?
[1] [Architecture] Stratos Membership Scheme for Automatically Discovering
Carbon Instances in a Carbon Cluster
[2]
TID: [-1] [] [2015-07-27 04:51:11,885] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:16,887] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next
manager
NotStormManagerException(message:10.244.28.23:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.3.29:8904. Trying next manager
NotStormManagerException(message:10.244.3.29:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:21,892] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next
manager
NotStormManagerException(message:10.244.28.23:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
Re: [Dev] CEP 400 (Beta) NotStormManagerException
On Mon, Jul 27, 2015 at 2:15 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
+1 Azeez
[I mean adding Azeez into the loop]
On Mon, Jul 27, 2015 at 2:07 PM, Lasindu Charith lasi...@wso2.com wrote:
Hi all,
We are having a clustered deployment of CEP 400 Beta in Stratos 4.1.0(in
Kubernetes), similar to following. Instead of using hazelcast clustering,
I'm using 'Stratos Membership scheme' [1] which considers all the members
in the carbon cluster as well-known members. I have done CEP Distributed
deployment according to [3][4].
[image: Inline image 1]
When CEP workers start up, I can see the following log [2] in worker
nodes. 10.244.28.23/24 are manager IPs. When the CEP managers are
restarted, the error goes away(Workers can connect to CEP Manager).
According to above membership scheme, any of the CEP workers/managers can
be the hazelcast coordinator. *Does CEP requires a member who is both
CEP manager as well as a hazelcast coordinator to be elected as the Storm
manager? *
Should CEP workers be always non-wka? How can we overcome this issue?
[1] [Architecture] Stratos Membership Scheme for Automatically
Discovering Carbon Instances in a Carbon Cluster
[2]
TID: [-1] [] [2015-07-27 04:51:11,885] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:16,887] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next
manager
NotStormManagerException(message:10.244.28.23:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.3.29:8904. Trying next
manager
NotStormManagerException(message:10.244.3.29:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:21,892] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next
manager
NotStormManagerException(message:10.244.28.23:8904 not a storm manager)
at
Re: [Dev] Does IS has mutual authenticator packed in IS 5.1.0 disctribution?
Adding TharinduA.
*Samuel Gnaniah*
Lead Technical Writer
WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798
On Mon, Jul 27, 2015 at 12:33 PM, Rajkumar Rajaratnam rajkum...@wso2.com
wrote:
Hi Tharindu
On Sun, Apr 26, 2015 at 9:11 AM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Firzan,
The custom secret callback handler should be included in
authenticanendpoint/WEB-INF/lib directory only if secure vault is added. We
should write proper documentation for enabling secure vault for the
dropdown feature and mention that. However the error handling of the
feature is improved than the service pack when comes to the next release of
IS.
Where can I get CustomSecretCallbackHandler jar? I couldn't find it in
SP01. The pre-configured IS pack [1] has TenantConfig.properties file which
references org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler.
It throws following CNF exceptions since the jar is not included anywhere.
Please advice.
TID: [0] [IS] [2015-07-26 08:28:18,874] ERROR
{org.wso2.securevault.secret.SecretCallbackHandlerFactory} - A
SecretCallbackHandler cannot be found for class name :
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
{org.wso2.securevault.secret.SecretCallbackHandlerFactory}
java.lang.ClassNotFoundException:
org.wso2.carbon.securevault.custom.CustomSecretCallbackHandler
at
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:138)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)
at
org.wso2.securevault.secret.SecretCallbackHandlerFactory.createSecretCallbackHandler(SecretCallbackHandlerFactory.java:62)
at
org.wso2.securevault.SecretResolverFactory.initPasswordManager(SecretResolverFactory.java:278)
at
org.wso2.securevault.SecretResolverFactory.create(SecretResolverFactory.java:218)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.resolveSecrets(TenantDataManager.java:282)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.init(TenantDataManager.java:88)
at
org.wso2.carbon.identity.application.authentication.endpoint.util.TenantDataManager.isTenantListEnabled(TenantDataManager.java:267)
at org.apache.jsp.login_jsp._jspService(org.apache.jsp.login_jsp:329)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:412)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at
org.wso2.carbon.identity.application.authentication.endpoint.oauth2.OAuth2Login.doGet(OAuth2Login.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:412)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at
org.wso2.carbon.identity.application.authentication.endpoint.AuthenticationEndpoint.doGet(AuthenticationEndpoint.java:82)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
Re: [Dev] CEP 400 (Beta) NotStormManagerException
CEP Managers are must for Strom based coordination, so use the CEP Managers
to be the carbon cluster as well-known members, else it does not make sense
for CEP deployment. We have also done the testing like that.
Regards
Suho
On Mon, Jul 27, 2015 at 2:16 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
On Mon, Jul 27, 2015 at 2:15 PM, Lakmal Warusawithana lak...@wso2.com
wrote:
+1 Azeez
[I mean adding Azeez into the loop]
On Mon, Jul 27, 2015 at 2:07 PM, Lasindu Charith lasi...@wso2.com
wrote:
Hi all,
We are having a clustered deployment of CEP 400 Beta in Stratos 4.1.0(in
Kubernetes), similar to following. Instead of using hazelcast clustering,
I'm using 'Stratos Membership scheme' [1] which considers all the members
in the carbon cluster as well-known members. I have done CEP Distributed
deployment according to [3][4].
[image: Inline image 1]
When CEP workers start up, I can see the following log [2] in worker
nodes. 10.244.28.23/24 are manager IPs. When the CEP managers are
restarted, the error goes away(Workers can connect to CEP Manager).
According to above membership scheme, any of the CEP workers/managers
can be the hazelcast coordinator. *Does CEP requires a member who is
both CEP manager as well as a hazelcast coordinator to be elected as the
Storm manager? *
Should CEP workers be always non-wka? How can we overcome this issue?
[1] [Architecture] Stratos Membership Scheme for Automatically
Discovering Carbon Instances in a Carbon Cluster
[2]
TID: [-1] [] [2015-07-27 04:51:11,885] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:16,887] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.28.23:8904. Trying next
manager
NotStormManagerException(message:10.244.28.23:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error in registering CEP publisher
for 10.244.28.24:15000 with manager 10.244.3.29:8904. Trying next
manager
NotStormManagerException(message:10.244.3.29:8904 not a storm manager)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$registerCEPPublisher_result.read(StormManagerService.java:2116)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_registerCEPPublisher(StormManagerService.java:120)
at
org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.registerCEPPublisher(StormManagerService.java:104)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.registerCEPPublisherWithStormMangerService(SiddhiStormOutputEventListener.java:181)
at
org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener$Registrar.run(SiddhiStormOutputEventListener.java:128)
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)
TID: [-1] [] [2015-07-27 04:51:16,890] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP Publisher] Error registering CEP publisher with
current manager. Retrying after 5000ms
TID: [-1] [] [2015-07-27 04:51:21,892] ERROR
{org.wso2.carbon.event.processor.core.internal.storm.SiddhiStormOutputEventListener}
- [-1234:ExecutionPlan:CEP
