date:20140807

[Dev] [DSS]The process of DSS will be killed after running for a period of time

2014-08-07 Thread stevegyc

Hi:

Recently I found after running for a period of time, The process of DSS 
will be killed. 
In the log, the following information is displayed: 
wso2server.sh: line 300: 8634 killed.

I checked the file wso2server.sh, it seems like somehow the state has 
changed.
Had anyone encountered this problem?




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

Re: [Dev] Please merge the pull #7 to wso2-dev/carbon-identity

2014-08-07 Thread Chamil Jeewantha

Hi All,

Please merge this pull request.


On Wed, Aug 6, 2014 at 7:35 PM, Chamil Jeewantha  wrote:

> Please review & merge the [1]
>
> [1] https://github.com/wso2-dev/carbon-identity/pull/7
>
> --
> K.D. Chamil Jeewantha
> Associate Technical Lead
> WSO2, Inc.;  http://wso2.com
> Mobile: +94716813892
>
>


-- 
K.D. Chamil Jeewantha
Associate Technical Lead
WSO2, Inc.;  http://wso2.com
http://kdchamil.blogspot.com
Mobile: +94716813892
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [G-Reg 5.0.0] Improved Notifications Support

2014-08-07 Thread Heshani Gamage

Hi Senaka et. al,

Thanks for your suggestions/Information.

I prepared the attached document [1] considering all the stages of service
life cycle as Senaka mentioned.
Based on identified life cycle stages I've come up with set of roles
associated with those stages, and notifications that can be generated in
each of those stage.

Please give your suggestions and feel free to add/remove or edit the
entries.

Thanks,
Heshani

[1] Service Life cycle and roles associated



On Wed, Aug 6, 2014 at 5:33 PM, Senaka Fernando  wrote:

> Hi Subash,
>
> IMHO, In terms of gathering information, I think we should not restrict
> ourselves to the current situation. We should just collect all possible
> information. We can decide what gets included when, but that's secondary.
>
> And, even notification types, I think we should not be very
> implementation-specific. I agree we need to understand whether a Transition
> Was Successful or Whether it Failed and Why it Failed. But, for example, it
> could be just one-single Transition Failed notification too. Same goes for
> Approvals. The term "vote" is what we use for the concept of approvals. We
> should be focusing on Approval related notifications in general without
> restricting ourselves to what we have.
>
> Thanks,
> Senaka.
>
>
> On Wed, Aug 6, 2014 at 12:49 PM, Subash Chaturanga 
> wrote:
>
>> Hi,
>>
>> On Wed, Aug 6, 2014 at 4:52 PM, Senaka Fernando  wrote:
>>
>>> Hi Heshani,
>>>
>>> The developer and the operations roles seem to be a little overwhelming.
>>> For example, I feel its better to have a slight distinction between
>>> developers and testers so that they can request for specific lifecycle
>>> changes to be notified.
>>>
>>> Also, the lifecycles do not begin with the development of a service and
>>> ends once it goes into production. There are some activities related to
>>> designing the service (these are mainly architects) and also deprecating
>>> the service (these are mainly managers and operations people). Also, a
>>> service can go through a bug fix cycle where developers, testers and ops
>>> are involved. Therefore, think a bit along these lines as well.
>>>
>>>
>> Are we planning to add "Deprecate" like state. I think we better have it
>> (it should be aline with API deprecate LC state), anyways that will be
>> decided with the unified governance models we have.
>>
>> Some notification types to consider on lifecycle space;
>>
>>- Transition Validation Failure/ Transition Exection Failure
>>- When votes/check items are defined in a LC state, if there are roles
>> assigned to those check items/votes in a given state, those users should be
>> notified, reminding they have a vote to make.
>>
>>
>>
>>> We should have notifications once scheduled reports have been generated.
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Wed, Aug 6, 2014 at 5:09 AM, Heshani Gamage  wrote:
>>>
 Hi all,

 I did a small research on roles and notification types of existing
 registry,repositories and came up with a set of common roles, and
 notifications that might be useful to those roles.
 Details can be found in the attached document[1].
 Please feel free to add/remove and edit entries.
 Appreciate any suggestions to finalize a set of roles and notifications
 to be added in the feature $subject.

 Thanks,
 Heshani

 [1]. Roles and Notifications
 
 
  Roles and Notifications
 
 


 On Mon, Aug 4, 2014 at 4:24 PM, Heshani Gamage 
 wrote:

> Hi Senaka et. al,
>
> First of all, thanks all for your information & suggestions.
>
> Apart for the things Subash has mentioned is there anything to be
> added or removed?
>
> Shall we arrange a meeting to discuss this further? Please suggest a
> convenient time for you.
>
> Thanks,
>
> Heshani
>
>
>
> On Mon, Aug 4, 2014 at 12:16 PM, Subash Chaturanga 
> wrote:
>
>> Hi Senaka et al,
>> In G-Reg mgt console, current notification types we have are
>>
>> - General:
>> resource Delete and Update
>>
>> - Lifecycle related
>> - check/uncheck LC item
>> - create/delete/state change in LC
>> - LC approvals
>>
>> *Service Provider; *
>> (It will be more like similar to what we had in mgt-console.)
>>
>>  - All above types of notifications make sense for the provider and
>> if we support similar in service provider page , provider will subscribe 
>> to
>> interested events at his will similarly as in mgt console. Hence only 
>> what
>> provider want's to get n

Re: [Dev] Regrouping the CEP components

2014-08-07 Thread Lasantha Fernando

Hi all,

Will be deleting the old unreleased versions inside
components/event-processing from the public branch since this can lead to
confusion when browsing the repo.

Thanks,
Lasantha


On 24 February 2014 11:50, Shavantha Weerasinghe  wrote:

> HI Mohan
>
> Is it possible for the QA team to meet with CEP team to discuss on the
> changes before the QA Cycle
>
> regards,
> Shavantha Weerasinghe
> Senior Software Engineer QA
> WSO2, Inc.
> lean.enterprise.middleware.
> http://wso2.com
> http://wso2.org
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
>
>
> On Mon, Feb 17, 2014 at 11:01 PM, Mohanadarshan Vivekanandalingam
>  wrote:
> > Hi All,
> >
> > Hope you all already know that we have done a major CEP release (version
> > 3.0.0) which is a complete rewrite of WSO2 CEP. It was built based on a
> > completely new architecture.. After the CEP 3.0.0 release, we have done
> > major UI improvements as well as many functionality improvements in
> various
> > features.. You can see the architecture mail subjected with "CEP UI
> > re-factoring and adding much more functionality" for more information
> about
> > the UI re-factoring. Initially all the CEP specific  components
> > (event-processing components) grouped under the high level
> event-processing
> > component in the code base, but we have decided to move these components
> in
> > to three major groups since no of high level components increased and to
> > give better understanding about the functionality of the components.
> >
> > Below is the information on how CEP components are grouped,
> >
> > Event-Processor : Moved as an high level component.
> > (platform/components/event-processor)
> > Event-Stream : Contains event-stream-manager, event-formatter,
> > event-builder, event-input-adaptor, event-output-adaptor &
> event-dashboard
> > (platform/components/event-stream)
> > Event-Monitor : Contains event-tracer & event-statistics.
> > (platform/components/event-monitor)
> >
> > Furthermore, all the active development will be happen on these
> components
> > targeting next CEP release 3.1.0..
> >
> > @BAM Team : Please refer above locations for CEP related components.
> >
> >
> > Thanks & Regards,
> > Mohan
> >
> > --
> > V. Mohanadarshan
> > Software Engineer,
> > Data Technologies Team,
> > WSO2, Inc. http://wso2.com
> > lean.enterprise.middleware.
> >
> > email: mo...@wso2.com
> > phone:(+94) 771117673
> >
> > ___
> > 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
>



-- 
*Lasantha Fernando*
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] [GReg] Build failure on carbon-governance wso2-dev git repo

2014-08-07 Thread Shameera Rathnayaka

Hi Subash,

Thanks for the quick reply, If this is because of latest change then you
can simply revert it back to previous stable state. Later you can merge the
changes once you confirm it will not cause to any build issue. This is one
of major feature we get with git.

Thanks,
Shameera.


On Wed, Aug 6, 2014 at 11:39 PM, Subash Chaturanga  wrote:

> Hi Shameera,
> Currently entire team on support/patches. Will followup once those are
> sorted out.
>
>
> On Wed, Aug 6, 2014 at 10:57 PM, Shameera Rathnayaka 
> wrote:
>
>> Hi Greg team,
>>
>> This issue is still there, please fix this. Jenkins build will not work
>> because of this.  find the error log below.
>>
>>  T E S T S
>> ---
>> Running org.wso2.carbon.governance.api.test.WSDLTest
>> log4j:WARN No appenders could be found for logger
>> (org.wso2.carbon.context.internal.CarbonContextDataHolder).
>> log4j:WARN Please initialize the log4j system properly.
>> Retrieving document at '
>> http://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.api/src/test/resources/test-resources/wsdl/BizService.wsdl
>> '.
>> Retrieving schema at '../xsd/purchasing.xsd', relative to '
>> http://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.api/src/test/resources/test-resources/wsdl/BizService.wsdl
>> '.
>> Retrieving document at '
>> http://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.api/src/test/resources/test-resources/wsdl/BizService.wsdl
>> '.
>> Retrieving schema at '../xsd/purchasing.xsd', relative to '
>> http://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.api/src/test/resources/test-resources/wsdl/BizService.wsdl
>> '.
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.203 sec
>> <<< FAILURE!
>> Running org.wso2.carbon.governance.api.test.SchemaTest
>> log4j:WARN No appenders could be found for logger
>> (org.wso2.carbon.context.internal.CarbonContextDataHolder).
>> log4j:WARN Please initialize the log4j system properly.
>> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.762 sec
>> Running org.wso2.carbon.governance.api.test.PolicyTest
>> log4j:WARN No appenders could be found for logger
>> (org.wso2.carbon.context.internal.CarbonContextDataHolder).
>> log4j:WARN Please initialize the log4j system properly.
>> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.196 sec
>>
>> Results :
>>
>> Tests in error:
>>   testAddWSDL(org.wso2.carbon.governance.api.test.WSDLTest): Error in
>> adding the wsdl. wsdl id: bcb699c4-3134-4442-92f3-e28900805942.
>>
>>
>> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
>>
>>
>>
>>
>>
>>
>>
>>
>> On Tue, Aug 5, 2014 at 3:24 PM, Gayashan Amarasinghe 
>> wrote:
>>
>>> Hi GReg team,
>>>
>>> I am getting the following test failures when building carbon-governance
>>> git repo. (mvn 3.0.5, java 1.6) Can we get this fixed?
>>>
>>> Results :
>>>
>>> Tests in error:
>>>   testAddWSDL(org.wso2.carbon.governance.api.test.WSDLTest): Error in
>>> adding the wsdl. wsdl id: 758ae3e7-7c2e-4dab-8f55-70406525e207.
>>>
>>> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
>>>
>>> [INFO]
>>> 
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] WSO2 Carbon - Platform Aggregator Pom . SUCCESS
>>> [0.103s]
>>> [INFO] WSO2 Carbon - Service Stubs - Aggregator Module ... SUCCESS
>>> [0.008s]
>>> [INFO] WSO2 Carbon - Governance - Notifications Work list Human Task
>>> Stub  SUCCESS [3.893s]
>>> [INFO] WSO2 Carbon - Governance - Gadgets User Interface Stub  SUCCESS
>>> [4.622s]
>>> [INFO] WSO2 Carbon - Governance - Generic Artifact User Interface Stub
>>> SUCCESS [2.137s]
>>> [INFO] WSO2 Carbon - Governance - Custom Lifecycle Checklist Stub
>>> SUCCESS [1.474s]
>>> [INFO] WSO2 Carbon - Governance - Life Cycles User Interface Stub
>>> SUCCESS [1.720s]
>>> [INFO] WSO2 Carbon - Governance - List Metadata User Interface Stub
>>> SUCCESS [1.973s]
>>> [INFO] WSO2 Carbon - Governance - Notifications User Interface Stub
>>> SUCCESS [2.365s]
>>> [INFO] WSO2 Carbon - Governance - People User Interface Stub  SUCCESS
>>> [1.664s]
>>> [INFO] WSO2 Carbon - Governance - Processes User Interface Stub  SUCCESS
>>> [1.649s]
>>> [INFO] WSO2 Carbon - Governance - Services User Interface Stub  SUCCESS
>>> [1.499s]
>>> [INFO] WSO2 Carbon - Governance - SLA User Interface Stub  SUCCESS
>>> [1.542s]
>>> [INFO] WSO2 Carbon - Governance - WSDL Tool Stub . SUCCESS
>>> [1.176s]
>>> [INFO] WSO2 Carbon - Governance Aggregator Module  SUCCESS
>>> [0.012s]
>>> [INFO] WSO2 Carbon - Governance .. FAILURE
>>> [9.120s]
>>> [INFO] WSO2 Carbon - Governance - S-Ramp Implementation .. SKIPPED
>>> 
>>>
>>> Any help is much appreciated.
>>>
>>> Thanks.
>>>
>>> --
>>> *Gayashan Amarasing

[Dev] App Manager latest build pack - 07-08-2014

2014-08-07 Thread Dinusha Senanayaka

Hi,

Please find the $subject in [1].

[1]. http://builder1.us1.wso2.org/~appm/07-08-2014/

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Senior Software Engineer
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Commits to kernel patch0009

2014-08-07 Thread Shameera Rathnayaka

Hi Asela,

Applied patches , Committed revision 206380, please send pull request to
4.3.0 git repo too.

Thanks,
Shameera.


On Wed, Aug 6, 2014 at 7:45 PM, Afkham Azeez  wrote:

> Here is the new patch with eviction made a private package, and also
> removing API additions in CacheImpl. Asela, we need to test with the new
> caching jar.
>
>
> On Wed, Aug 6, 2014 at 5:52 PM, Afkham Azeez  wrote:
>
>>
>>
>>
>> On Wed, Aug 6, 2014 at 5:35 PM, Shameera Rathnayaka 
>> wrote:
>>
>>> Hi Azeez,
>>>
>>> On Wed, Aug 6, 2014 at 5:11 PM, Afkham Azeez  wrote:
>>>
 Yes, ideally we should have exported only javax.cache.*. However, I
 think one of Asela's patch has a coupling to CacheImpl since caching API
 does not provide a way to set the cache capacity. However, there are no API
 changes in CacheImpl.

>>>
>>> There are API changes in CacheImpl class ( it has two public method to
>>> get size and cache capacity). and both are used in classes in eviction
>>> package. In that case what should we do?
>>> 
>>>  
>>>
>>
>> I can remove those methods. Let me do that & resend the patch.
>>
>>
>>> Thanks,
>>> Shameera.
>>>
>>>
>>> The only API changes are in the org.wso2.carbon.caching.impl.eviction
 package. That package is totally internal to the caching impl. We can make
 that private.


 On Wed, Aug 6, 2014 at 4:50 PM, Shameera Rathnayaka 
 wrote:

> Hi Azeez,
>
> Saw that "org.wso2.carbon.caching.impl.*, " is there under export
> packages, should this expose the latest API addition to the outside at
> runtime?. My understand is this can be an issue in future. WDYT?  if this
> is the only way to patch this, isn't it better we make all new API private
> to this bundle, i mean configure it as private package?
>
> Thanks,
> Shameera.
>   
>
>
>
> On Wed, Aug 6, 2014 at 2:32 PM, Afkham Azeez  wrote:
>
>> There are API changes within java.cache, but all of those changes
>> affect only that bundle, and are internal to that bundle, and don't 
>> affect
>> the bundles outside it. Hence, there is no issue in committing the 
>> caching
>> fix.
>>
>>
>> On Wed, Aug 6, 2014 at 2:28 PM, Asela Pathberiya 
>> wrote:
>>
>>> Hi Shameera,
>>>
>>> There is no any API in user core patch...  We have only added a
>>> private method.  As i got to know,  It is not allowed to add even
>>> private method.  Therefore i modified the code and attached the patch
>>> in to the jira.
>>>
>>> AFAIK, there is no any caching API changes in caching.core as well...
>>>
>>> Therefore i hope it is fine to apply the patches...
>>>
>>> Adding Azeez...
>>>
>>> Thanks,
>>> Asela.
>>>
>>> On Wed, Aug 6, 2014 at 2:13 PM, Shameera Rathnayaka <
>>> shame...@wso2.com> wrote:
>>> > Hi Asela,
>>> >
>>> > As we discussed,  it is not allowed to do any API changes to 4.2.0
>>> patches.
>>> > So please reattached the patch removing all API changes. And the
>>> already
>>> > attached patch can be applied to 4.3.0 git repo. So please send
>>> those as
>>> > pull request.
>>> >
>>> > Thanks,
>>> > Shameera.
>>> >
>>> >
>>> > On Wed, Aug 6, 2014 at 1:02 PM, Asela Pathberiya 
>>> wrote:
>>> >>
>>> >> Hi All,
>>> >>
>>> >> Please commit following
>>> >>
>>> >> https://wso2.org/jira/browse/CARBON-14891
>>> >> https://wso2.org/jira/browse/CARBON-14905
>>> >>
>>> >> Thanks,
>>> >> Asela.
>>> >>
>>> >> --
>>> >> Thanks & Regards,
>>> >> Asela
>>> >>
>>> >> ATL
>>> >> Mobile : +94 777 625 933
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Software Engineer - WSO2 Inc.
>>> > email: shameera AT wso2.com , shameera AT apache.org
>>> > phone:  +9471 922 1454
>>> >
>>> > Linked in :
>>> http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
>>> > Twitter : https://twitter.com/Shameera_R
>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>> Asela
>>>
>>> ATL
>>> Mobile : +94 777 625 933
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> * linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *Software Engineer - WSO2 Inc.*
> *email: shameera AT wso2.com  , shameera AT
> apache.org *
> *phone:  +9471 922

[Dev] Please merge pull #16 for wso2-dev/carbon-commons

2014-08-07 Thread Tishan Dahanayakage

Please review and merge [1]

[1] https://github.com/wso2-dev/carbon-commons/pull/16

-- 
Tishan Dahanayakage
Software Engineer
WSO2, Inc.
Mobile:+94 716481328

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
re-transmit, disseminate, or otherwise use the information contained in
this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please merge pull #16 for wso2-dev/carbon-commons

2014-08-07 Thread Sinthuja Ragendran

Done.

Thanks,
Sinthuja


On Thu, Aug 7, 2014 at 4:22 PM, Tishan Dahanayakage  wrote:

> Please review and merge [1]
>
> [1] https://github.com/wso2-dev/carbon-commons/pull/16
>
> --
> Tishan Dahanayakage
> Software Engineer
> WSO2, Inc.
> Mobile:+94 716481328
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, re-transmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>



-- 
*Sinthuja Rajendran*
Senior Software Engineer 
WSO2, Inc.:http://wso2.com

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

Re: [Dev] Please merge pull #16 for wso2-dev/carbon-commons

2014-08-07 Thread Tishan Dahanayakage

Thanks

On Thu, Aug 7, 2014 at 4:30 PM, Sinthuja Ragendran 
wrote:

> Done.
>
> Thanks,
> Sinthuja
>
>
> On Thu, Aug 7, 2014 at 4:22 PM, Tishan Dahanayakage 
> wrote:
>
>> Please review and merge [1]
>>
>> [1] https://github.com/wso2-dev/carbon-commons/pull/16
>>
>> --
>> Tishan Dahanayakage
>> Software Engineer
>> WSO2, Inc.
>> Mobile:+94 716481328
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, re-transmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>
>
>
> --
> *Sinthuja Rajendran*
> Senior Software Engineer 
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>

-- 
Tishan Dahanayakage
Software Engineer
WSO2, Inc.
Mobile:+94 716481328

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
re-transmit, disseminate, or otherwise use the information contained in
this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [AF] Error while creating an application

2014-08-07 Thread Danushka Fernando

Hi
I am getting following error while creating the application. But
application get created. Any idea whats going wrong here?

TID: [0] [Carbon] [2014-08-07 16:42:54,059]  INFO
{org.wso2.carbon.appfactory.utilities.project.ProjectUtils} -  Maven
archetype generation completed successfully
{org.wso2.carbon.appfactory.utilities.project.ProjectUtils}
TID: [0] [Carbon] [2014-08-07 16:42:54,483] ERROR
{org.wso2.carbon.identity.authenticator.mutualssl.MutualSSLAuthenticator} -
 Authentication Request is rejected. User doesnot exists in userstore
{org.wso2.carbon.identity.authenticator.mutualssl.MutualSSLAuthenticator}
TID: [0] [Carbon] [2014-08-07 16:42:54,483]  WARN
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
Administrator login attempt 'gitblitsystemadmin[-1234]' at [2014-08-07
16:42:54,483+0530]
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
TID: [0] [Carbon] [2014-08-07 16:42:54,483]  WARN
{org.wso2.carbon.server.admin.module.handler.AuthenticationHandler} -
 Illegal access attempt at [2014-08-07 16:42:54,0483] from IP address
192.168.16.4 : Service is RepositoryManagementService
{org.wso2.carbon.server.admin.module.handler.AuthenticationHandler}
TID: [0] [Carbon] [2014-08-07 16:42:54,484] ERROR
{org.apache.axis2.engine.AxisEngine} -  Access Denied. Please login first.
{org.apache.axis2.engine.AxisEngine}
org.apache.axis2.AxisFault: Access Denied. Please login first.
at
org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:97)
at
org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.invoke(AuthenticationHandler.java:66)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
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
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecu

Re: [Dev] [AF] Error while creating an application

2014-08-07 Thread Gayan Dhanushka

Hi Danushka,

This happens due to the newly added notifycommits.groovy hook. Since the
git commit at application creation is done as the gitblitsystemadmin and
not the actual user. Hence the mutual authentication fails. I will provide
a fix for this.

Regards



On Thu, Aug 7, 2014 at 4:42 PM, Danushka Fernando 
wrote:

> Hi
> I am getting following error while creating the application. But
> application get created. Any idea whats going wrong here?
>
> TID: [0] [Carbon] [2014-08-07 16:42:54,059]  INFO
> {org.wso2.carbon.appfactory.utilities.project.ProjectUtils} -  Maven
> archetype generation completed successfully
> {org.wso2.carbon.appfactory.utilities.project.ProjectUtils}
> TID: [0] [Carbon] [2014-08-07 16:42:54,483] ERROR
> {org.wso2.carbon.identity.authenticator.mutualssl.MutualSSLAuthenticator} -
>  Authentication Request is rejected. User doesnot exists in userstore
> {org.wso2.carbon.identity.authenticator.mutualssl.MutualSSLAuthenticator}
> TID: [0] [Carbon] [2014-08-07 16:42:54,483]  WARN
> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
> Administrator login attempt 'gitblitsystemadmin[-1234]' at [2014-08-07
> 16:42:54,483+0530]
> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
> TID: [0] [Carbon] [2014-08-07 16:42:54,483]  WARN
> {org.wso2.carbon.server.admin.module.handler.AuthenticationHandler} -
>  Illegal access attempt at [2014-08-07 16:42:54,0483] from IP address
> 192.168.16.4 : Service is RepositoryManagementService
> {org.wso2.carbon.server.admin.module.handler.AuthenticationHandler}
> TID: [0] [Carbon] [2014-08-07 16:42:54,484] ERROR
> {org.apache.axis2.engine.AxisEngine} -  Access Denied. Please login first.
> {org.apache.axis2.engine.AxisEngine}
> org.apache.axis2.AxisFault: Access Denied. Please login first.
>  at
> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:97)
> at
> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.invoke(AuthenticationHandler.java:66)
>  at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>  at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>  at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
> at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>  at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>  at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>  at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  at
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>  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
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>  at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>  at
> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
> at
> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>  at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>  at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>  at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)

Re: [Dev] [AF] Error while creating an application

2014-08-07 Thread Danushka Fernando

Created the jira [1].

[1] https://wso2.org/jira/browse/APPFAC-2401

Thanks & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729


On Thu, Aug 7, 2014 at 4:52 PM, Gayan Dhanushka  wrote:

> Hi Danushka,
>
> This happens due to the newly added notifycommits.groovy hook. Since the
> git commit at application creation is done as the gitblitsystemadmin and
> not the actual user. Hence the mutual authentication fails. I will provide
> a fix for this.
>
> Regards
>
>
>
> On Thu, Aug 7, 2014 at 4:42 PM, Danushka Fernando 
> wrote:
>
>> Hi
>> I am getting following error while creating the application. But
>> application get created. Any idea whats going wrong here?
>>
>> TID: [0] [Carbon] [2014-08-07 16:42:54,059]  INFO
>> {org.wso2.carbon.appfactory.utilities.project.ProjectUtils} -  Maven
>> archetype generation completed successfully
>> {org.wso2.carbon.appfactory.utilities.project.ProjectUtils}
>> TID: [0] [Carbon] [2014-08-07 16:42:54,483] ERROR
>> {org.wso2.carbon.identity.authenticator.mutualssl.MutualSSLAuthenticator} -
>>  Authentication Request is rejected. User doesnot exists in userstore
>> {org.wso2.carbon.identity.authenticator.mutualssl.MutualSSLAuthenticator}
>> TID: [0] [Carbon] [2014-08-07 16:42:54,483]  WARN
>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
>> Administrator login attempt 'gitblitsystemadmin[-1234]' at [2014-08-07
>> 16:42:54,483+0530]
>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
>> TID: [0] [Carbon] [2014-08-07 16:42:54,483]  WARN
>> {org.wso2.carbon.server.admin.module.handler.AuthenticationHandler} -
>>  Illegal access attempt at [2014-08-07 16:42:54,0483] from IP address
>> 192.168.16.4 : Service is RepositoryManagementService
>> {org.wso2.carbon.server.admin.module.handler.AuthenticationHandler}
>> TID: [0] [Carbon] [2014-08-07 16:42:54,484] ERROR
>> {org.apache.axis2.engine.AxisEngine} -  Access Denied. Please login first.
>> {org.apache.axis2.engine.AxisEngine}
>> org.apache.axis2.AxisFault: Access Denied. Please login first.
>>  at
>> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:97)
>> at
>> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.invoke(AuthenticationHandler.java:66)
>>  at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>>  at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>>  at
>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>> at
>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>>  at
>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>> at
>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>>  at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>>  at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>>  at
>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
>>  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
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>>  at
>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>>  at
>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>> at
>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>>  at
>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetecti

[Dev] Issue in Permission Saving and Notifications in EMM

2014-08-07 Thread Kasun Dananjaya Delgolla

Hi Guys,

I found these 2 issues when I was working on the dev-service where when you
try to save Messaging permission to a particular role, it doesn't get
saved. I figured out it's happening because of the permission trees we have
there. We have an empty tree for messaging so the permission logic always
searches for child elements in that tree and save only child elements. I
fixed it in my working copy for me to continue my work temporarily. Is this
resolved in dev branch? I created a JIRA[1] on this as well.

Another issue that I came across was there's a problem when displaying
notification table contents. It should always show the latest record
content if the same command been executed 2+ times and it should remove the
old record from the table as well. It's currently not happening as well.
Are these issues fixed on the dev branch?

[1] - https://wso2.org/jira/browse/EMM-705

Thanks
-- 
Kasun Dananjaya Delgolla

Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
Tel:  +94 11 214 5345
Fax: +94 11 2145300
Mob: + 94 777 997 850
Blog: http://kddcodingparadise.blogspot.com
Linkedin: *http://lk.linkedin.com/in/kasundananjaya
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in Permission Saving and Notifications in EMM

2014-08-07 Thread Niranjan Karunanandham

Hi Kasun,

Please see my comments below:


> I found these 2 issues when I was working on the dev-service where when
> you try to save Messaging permission to a particular role, it doesn't get
> saved. I figured out it's happening because of the permission trees we have
> there. We have an empty tree for messaging so the permission logic always
> searches for child elements in that tree and save only child elements. I
> fixed it in my working copy for me to continue my work temporarily. Is this
> resolved in dev branch? I created a JIRA[1] on this as well.
>
This is an issue with the insert script in mysql.sql for the table
features. I will look into it.


> Another issue that I came across was there's a problem when displaying
> notification table contents. It should always show the latest record
> content if the same command been executed 2+ times and it should remove the
> old record from the table as well. It's currently not happening as well.
> Are these issues fixed on the dev branch?
>
This is how EMM currently works. We only prevent from having duplicate
monitor requests if the previous Monitor request is not served. If it is an
operation then we allow to have multiple entry. If you want to define
certain operations from being duplicated, the permanent fix will be to have
a field in the featuers table called AllowDuplicate. If this field is true
then we allow duplicate operations and false we don't. This is because for
operations like Messaging, duplicate entries are required.

Regards,
Nira


On Thu, Aug 7, 2014 at 5:24 PM, Kasun Dananjaya Delgolla 
wrote:

> Hi Guys,
>
> I found these 2 issues when I was working on the dev-service where when
> you try to save Messaging permission to a particular role, it doesn't get
> saved. I figured out it's happening because of the permission trees we have
> there. We have an empty tree for messaging so the permission logic always
> searches for child elements in that tree and save only child elements. I
> fixed it in my working copy for me to continue my work temporarily. Is this
> resolved in dev branch? I created a JIRA[1] on this as well.
>
> Another issue that I came across was there's a problem when displaying
> notification table contents. It should always show the latest record
> content if the same command been executed 2+ times and it should remove the
> old record from the table as well. It's currently not happening as well.
> Are these issues fixed on the dev branch?
>
> [1] - https://wso2.org/jira/browse/EMM-705
>
> Thanks
> --
> Kasun Dananjaya Delgolla
>
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
> Tel:  +94 11 214 5345
> Fax: +94 11 2145300
> Mob: + 94 777 997 850
> Blog: http://kddcodingparadise.blogspot.com
> Linkedin: *http://lk.linkedin.com/in/kasundananjaya
> *
>



-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
M: +94 777 749 661 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] G-reg is not starting

2014-08-07 Thread Akila Nimantha [IT/EKO/LOITS]

Hi all,

When we start G-reg it hangs and the following message keep repeating.


TID: [0] [Greg] [2014-08-07 17:12:03,829]  INFO 
{org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent} -  Carbon 
UserStoreMgtDSComponent activated successfully. 
{org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent}
TID: [0] [Greg] [2014-08-07 17:12:10,649]  INFO 
{org.apache.catalina.startup.TaglibUriRule} -  TLD skipped. URI: 
http://tiles.apache.org/tags-tiles is already defined 
{org.apache.catalina.startup.TaglibUriRule}
TID: [0] [Greg] [2014-08-07 17:13:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:13:11,623]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:14:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:14:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:15:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:15:11,623]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:16:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:16:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:17:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:17:11,623]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:18:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:18:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:19:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:19:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:20:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:20:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:21:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:21:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:22:11,623]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:22:11,623]  WARN 
{org.wso2.carbon.core.init.CarbonServerMan

Re: [Dev] [DSS]The process of DSS will be killed after running for a period of time

2014-08-07 Thread Harsha Kumara

Hi Stevegyc

It's stranged.  Process may be killed due to ran out of memory,disk space
and etc. So it would be great if you can provide more details about it. May
be you find more info from server logs.
What you mean by sever state has changed in wso2server.sh and roughly how
many days you mean by long period time ?

Thanks,
Harsha

On Thu, Aug 7, 2014 at 3:15 PM, stevegyc  wrote:

>  Hi:
>
>
> Recently I found after running for a period of time, The process of DSS will 
> be killed.
> In the log, the following information is displayed:
> wso2server.sh: line 300: 8634 killed.
>
>
> I checked the file wso2server.sh, it seems like somehow the state has changed.
> Had anyone encountered this problem?
>
> --
> stevegyc
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] G-reg is not starting

2014-08-07 Thread Harsha Kumara

Hi Akila,
What is the installation environment and the G-Reg version you using? Did
you install any additional features?
Thanks,
Harsha


On Thu, Aug 7, 2014 at 6:25 PM, Akila Nimantha [IT/EKO/LOITS] <
aki...@lolctech.com> wrote:

>  *Hi all,*
>
>
>
> When we start G-reg it hangs and the following message keep repeating.
>
>
>
>
>
> TID: [0] [Greg] [2014-08-07 17:12:03,829]  INFO
> {org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent} -  Carbon
> UserStoreMgtDSComponent activated successfully.
> {org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent}
>
> TID: [0] [Greg] [2014-08-07 17:12:10,649]  INFO
> {org.apache.catalina.startup.TaglibUriRule} -  TLD skipped. URI:
> http://tiles.apache.org/tags-tiles is already defined
> {org.apache.catalina.startup.TaglibUriRule}
>
> TID: [0] [Greg] [2014-08-07 17:13:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:13:11,623]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:14:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:14:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:15:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:15:11,623]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:16:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:16:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:17:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:17:11,623]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:18:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:18:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:19:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:19:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:20:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:20:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:21:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:21:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.cor

[Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?

2014-08-07 Thread Ishara Premadasa

Hi all,

I get the following build error when trying to check out remote ESB
mediator project and trying to build it online. Since there are test cases
created for the class mediators, it is required to add synapse-core-tests
dependency into the pom.xml and use that in the test cases. Below is the
dependency and my maven repository entry.


org.apache.synapse
synapse-core-tests
2.1.2-wso2v4
 


true
daily
ignore

wso2-nexus
http://maven.wso2.org/nexus/content/groups/wso2-public/



Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure
to find org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 in
http://maven.wso2.org/nexus/content/groups/ws
o2-public/ was cached in the local repository, resolution will not be
reattempted until the update interval of wso2-nexus has elapsed or updates
are forced
at
org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:232)
at
org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:599)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:518)
at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:436)
... 26 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]

This says unable to find
org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 jar but if you
traverse this can be located in neus-repo [1].
Any help is appreciated.

[1]
http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/synapse/synapse-core/2.1.2-wso2v4/

Thanks!
Ishara
-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failed in Jenkins: carbon-apimgt #144

2014-08-07 Thread Afkham Azeez

Sagara,
Can you provide some insight?

On Thu, Aug 7, 2014 at 2:29 PM, Maheshika Goonetilleke 
wrote:

> Hi Jaminda & Ruwan
>
> The wso2/jenkins has built with the latest revision (
> e396cd1d2252daa0656be4c3e6ca229dbed836cf). However the wso2-pr-builder is
> building at an older revision (0cc5599c57f443a937affcd2045617d8660a58e4).
>
> Hence, the build is failing as the auto merge has not been carried out.
>
> We have carried out some config changes few days back to the pr-builder to
> capture the latest revision[2].
>
> [1] https://github.com/wso2/carbon-commons/commits/master
> [2] Mail with subject : Add origin/master refspec to Jenkins PR Builder
> jobs
>
>
> @Kasun : Please check and advice any config change or workaround for this.
>
>
> On Thu, Aug 7, 2014 at 1:58 PM, Jaminda Batuwangala 
> wrote:
>
>> Hi Azeez/Maheshika,
>>
>>  Can you please look into this. Sumedha noted this as well before. There
>> are continuous build failure messages getting generated and need to avoid
>> this scenario.
>>
>> Thanks,
>> Jaminda
>>
>>
>> On Thu, Aug 7, 2014 at 8:17 AM, Ruwan Yatawara  wrote:
>>
>>> Hi Azeez / Mahesika,
>>>
>>> I believe this is happening due to the following pull request @ [1] not
>>> getting merged. As you suggested the other day we tried closing and
>>> reopening same, but seems it has still not been merged automatically. Can
>>> you please help us do the needful to resolve this matter.
>>>
>>>
>>> [1] - https://github.com/wso2/carbon-commons/pull/15
>>>
>>>  Thanks and Regards,
>>>
>>> Ruwan Yatawara
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>>
>>> email : ruw...@wso2.com
>>> mobile : +94 77 9110413
>>> blog : http://thoughts.ruwan-ace.com/
>>> www: :http://wso2.com
>>>
>>>
>>>
>>> On Thu, Aug 7, 2014 at 12:30 AM,  wrote:
>>>
 See 

 --
 [...truncated 2105 lines...]
 [INFO] WSO2 Carbon - Api management Feature .. SKIPPED
 [INFO] WSO2 Carbon - Forum Feature Aggregator Module . SKIPPED
 [INFO] WSO2 Carbon - Forum Server Feature  SKIPPED
 [INFO] WSO2 Carbon - Forum Feature ... SKIPPED
 [INFO]

 [INFO] BUILD FAILURE
 [INFO]

 [INFO] Total time: 12:23.919s
 [INFO] Finished at: Wed Aug 06 19:00:35 UTC 2014
 [INFO] Final Memory: 117M/475M
 [INFO]

 ERROR: Asynchronous execution failure
 java.util.concurrent.ExecutionException: java.lang.ClassCastException:
 java.lang.String cannot be cast to hudson.model.Fingerprint
 at hudson.remoting.Channel$3.adapt(Channel.java:772)
 at hudson.remoting.Channel$3.adapt(Channel.java:767)
 at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
 at
 hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:185)
 at hudson.maven.Maven3Builder.call(Maven3Builder.java:141)
 at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
 at hudson.remoting.UserRequest.perform(UserRequest.java:118)
 at hudson.remoting.UserRequest.perform(UserRequest.java:48)
 at hudson.remoting.Request$2.run(Request.java:328)
 at
 hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 at
 java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: java.lang.ClassCastException: java.lang.String cannot be
 cast to hudson.model.Fingerprint
 at hudson.model.Fingerprint.load(Fingerprint.java:1232)
 at hudson.model.Fingerprint.load(Fingerprint.java:1220)
 at hudson.model.FingerprintMap.load(FingerprintMap.java:94)
 at hudson.model.FingerprintMap.load(FingerprintMap.java:45)
 at hudson.util.KeyedDataStorage.get(KeyedDataStorage.java:154)
 at hudson.model.FingerprintMap.get(FingerprintMap.java:79)
 at hudson.model.FingerprintMap.get(FingerprintMap.java:45)
 at
 hudson.util.KeyedDataStorage.getOrCreate(KeyedDataStorage.java:108)
 at
 hudson.model.FingerprintMap.getOrCreate(FingerprintMap.java:65)
 at
 hudson.maven.reporters.MavenFingerprinter$1.call(MavenFingerprinter.java:125)
 at
 hudson.maven.reporters.MavenFingerprinter$1.call(MavenFingerprinter.

[Dev] [G-Reg 5.0.0][RXT] Cannot add RXTs with "maxoccurs=unbounded" table elements

2014-08-07 Thread Sameera Kannangara

HI all,

$subject is reported at [1] by Ayesha.
And this blocks the testing of the fix I created for [2].

So I compared rxt.xsd files from both 4.6.0 and 5.0.0-SNAPSHOT G-Reg packs.
And found out following lines are missing in 5.0.0-SNAPSHOT G-Reg pack's
rxt.xsd file.
(Followings marks the changes done in 5.0.0-SNAPSHOT to 4.6.0 rxt.xsd)

@@ -8,9 +8,8 @@




- 




@@ -87,9 +86,8 @@




- 




@@ -121,10 +119,9 @@




- 
- 
+ 




@@ -147,9 +144,8 @@




- 





How should we approach fixing this issue?
What could be the reason for above changes?

Thank you,
SameeraK.


[1] https://wso2.org/jira/browse/REGISTRY-2221
[2] https://wso2.org/jira/browse/REGISTRY-2248

-- 
Sameera Kannangara,
Software Engineer,
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failed in Jenkins: carbon-apimgt #144

2014-08-07 Thread Sagara Gunathunga

On Thu, Aug 7, 2014 at 7:56 PM, Afkham Azeez  wrote:

> Sagara,
> Can you provide some insight?
>

As nobody actively work on carbon-apimgt I haven't look into this but I
guess this should be a misconfiguration issue ( Other PRB jobs are running
smoothly even today I have merged some changes to carbon-deployment,
carbon-common through PRB).   We can look into this issue on carbon-apimgt
but before that I want to ensure someone actively work on this project
otherwise for the moment we can disable this job.

Thanks !


>
>
> On Thu, Aug 7, 2014 at 2:29 PM, Maheshika Goonetilleke  > wrote:
>
>> Hi Jaminda & Ruwan
>>
>> The wso2/jenkins has built with the latest revision (
>> e396cd1d2252daa0656be4c3e6ca229dbed836cf). However the wso2-pr-builder
>> is building at an older revision (
>> 0cc5599c57f443a937affcd2045617d8660a58e4).
>>
>> Hence, the build is failing as the auto merge has not been carried out.
>>
>> We have carried out some config changes few days back to the pr-builder
>> to capture the latest revision[2].
>>
>> [1] https://github.com/wso2/carbon-commons/commits/master
>> [2] Mail with subject : Add origin/master refspec to Jenkins PR Builder
>> jobs
>>
>>
>> @Kasun : Please check and advice any config change or workaround for this.
>>
>>
>> On Thu, Aug 7, 2014 at 1:58 PM, Jaminda Batuwangala 
>> wrote:
>>
>>> Hi Azeez/Maheshika,
>>>
>>>  Can you please look into this. Sumedha noted this as well before. There
>>> are continuous build failure messages getting generated and need to avoid
>>> this scenario.
>>>
>>> Thanks,
>>> Jaminda
>>>
>>>
>>> On Thu, Aug 7, 2014 at 8:17 AM, Ruwan Yatawara  wrote:
>>>
 Hi Azeez / Mahesika,

 I believe this is happening due to the following pull request @ [1] not
 getting merged. As you suggested the other day we tried closing and
 reopening same, but seems it has still not been merged automatically. Can
 you please help us do the needful to resolve this matter.


 [1] - https://github.com/wso2/carbon-commons/pull/15

  Thanks and Regards,

 Ruwan Yatawara

 Senior Software Engineer,
 WSO2 Inc.

 email : ruw...@wso2.com
 mobile : +94 77 9110413
 blog : http://thoughts.ruwan-ace.com/
 www: :http://wso2.com



 On Thu, Aug 7, 2014 at 12:30 AM,  wrote:

> See 
>
> --
> [...truncated 2105 lines...]
> [INFO] WSO2 Carbon - Api management Feature .. SKIPPED
> [INFO] WSO2 Carbon - Forum Feature Aggregator Module . SKIPPED
> [INFO] WSO2 Carbon - Forum Server Feature  SKIPPED
> [INFO] WSO2 Carbon - Forum Feature ... SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 12:23.919s
> [INFO] Finished at: Wed Aug 06 19:00:35 UTC 2014
> [INFO] Final Memory: 117M/475M
> [INFO]
> 
> ERROR: Asynchronous execution failure
> java.util.concurrent.ExecutionException: java.lang.ClassCastException:
> java.lang.String cannot be cast to hudson.model.Fingerprint
> at hudson.remoting.Channel$3.adapt(Channel.java:772)
> at hudson.remoting.Channel$3.adapt(Channel.java:767)
> at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
> at
> hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:185)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:141)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:328)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.ClassCastException: java.lang.String cannot be
> cast to hudson.model.Fingerprint
> at hudson.model.Fingerprint.load(Fingerprint.java:1232)
> at hudson.model.Fingerprint.load(Fingerprint.java:1220)
> at hudson.model.FingerprintMap.load(FingerprintMap.java:94)
> at hudson.model.FingerprintMap.load(Fin

Re: [Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?

2014-08-07 Thread Shameera Rathnayaka

Even though jar name is synapse-core-test its artifactId is synapse-core ,
try with


org.apache.synapse
synapse-core
2.1.2-wso2v4
 

~Shameera.


On Thu, Aug 7, 2014 at 9:58 PM, Ishara Premadasa  wrote:

> Hi all,
>
> I get the following build error when trying to check out remote ESB
> mediator project and trying to build it online. Since there are test cases
> created for the class mediators, it is required to add synapse-core-tests
> dependency into the pom.xml and use that in the test cases. Below is the
> dependency and my maven repository entry.
>
> 
> org.apache.synapse
> synapse-core-tests
> 2.1.2-wso2v4
>  
> 
> 
> true
> daily
> ignore
> 
> wso2-nexus
> http://maven.wso2.org/nexus/content/groups/wso2-public/
> 
> 
>
> Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure
> to find org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 in
> http://maven.wso2.org/nexus/content/groups/ws
> o2-public/ was cached in the local repository, resolution will not be
> reattempted until the update interval of wso2-nexus has elapsed or updates
> are forced
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:232)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:599)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:518)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:436)
> ... 26 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
>
> This says unable to find
> org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 jar but if you
> traverse this can be located in neus-repo [1].
> Any help is appreciated.
>
> [1]
> http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/synapse/synapse-core/2.1.2-wso2v4/
>
> Thanks!
> Ishara
> --
> Ishara Premasada
> Software Engineer,
> WSO2 Inc. http://wso2.com/
>
>
> *Blog   :  http://isharapremadasa.blogspot.com/
> Twitter   :
> https://twitter.com/ishadil  Mobile   :
> +94 714445832 <%2B94%20714445832>*
>
>
>


-- 
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com  , shameera AT apache.org
*
*phone:  +9471 922 1454*

*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?

2014-08-07 Thread Ishara Premadasa

Hi Shameera,

I tried with the synapse-core dependency only at first. However there is
this TestUtils class which is required to Junit test class for custom
mediator that is not coming from synapse-core.

@Chamara,
Can you please clarify here on this TestUtils class?

Thanks!
Ishara


On Thu, Aug 7, 2014 at 1:44 PM, Shameera Rathnayaka 
wrote:

> Even though jar name is synapse-core-test its artifactId is synapse-core ,
> try with
>
> 
> org.apache.synapse
> synapse-core
> 2.1.2-wso2v4
>  
>
> ~Shameera.
>
>
> On Thu, Aug 7, 2014 at 9:58 PM, Ishara Premadasa  wrote:
>
>> Hi all,
>>
>> I get the following build error when trying to check out remote ESB
>> mediator project and trying to build it online. Since there are test cases
>> created for the class mediators, it is required to add synapse-core-tests
>> dependency into the pom.xml and use that in the test cases. Below is the
>> dependency and my maven repository entry.
>>
>> 
>> org.apache.synapse
>> synapse-core-tests
>> 2.1.2-wso2v4
>>  
>> 
>> 
>> true
>> daily
>> ignore
>> 
>> wso2-nexus
>> http://maven.wso2.org/nexus/content/groups/wso2-public/
>> 
>> 
>>
>> Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure
>> to find org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 in
>> http://maven.wso2.org/nexus/content/groups/ws
>> o2-public/ was cached in the local repository, resolution will not be
>> reattempted until the update interval of wso2-nexus has elapsed or updates
>> are forced
>> at
>> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:232)
>> at
>> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
>> at
>> org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:599)
>> at
>> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:518)
>> at
>> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:436)
>> ... 26 more
>> [ERROR]
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>>
>> This says unable to find
>> org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 jar but if you
>> traverse this can be located in neus-repo [1].
>> Any help is appreciated.
>>
>> [1]
>> http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/synapse/synapse-core/2.1.2-wso2v4/
>>
>> Thanks!
>> Ishara
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>>
>>
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> Twitter   :
>> https://twitter.com/ishadil  Mobile   :
>> +94 714445832 <%2B94%20714445832>*
>>
>>
>>
>
>
> --
> *Software Engineer - WSO2 Inc.*
> *email: shameera AT wso2.com  , shameera AT apache.org
> *
> *phone:  +9471 922 1454 <%2B9471%20922%201454>*
>
> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
> *Twitter : *https://twitter.com/Shameera_R
>



-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :
https://twitter.com/ishadil Mobile   : +94
714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?

2014-08-07 Thread Chamara Ariyarathne

This is the method I'm using.

public static org.apache.synapse.MessageContext
getTestContext(java.lang.String bodyText, java.util.Map props) throws
java.lang.Exception;


On Thu, Aug 7, 2014 at 11:32 PM, Ishara Premadasa  wrote:

> Hi Shameera,
>
> I tried with the synapse-core dependency only at first. However there is
> this TestUtils class which is required to Junit test class for custom
> mediator that is not coming from synapse-core.
>
> @Chamara,
> Can you please clarify here on this TestUtils class?
>
> Thanks!
> Ishara
>
>
> On Thu, Aug 7, 2014 at 1:44 PM, Shameera Rathnayaka 
> wrote:
>
>> Even though jar name is synapse-core-test its artifactId is synapse-core
>> , try with
>>
>> 
>> org.apache.synapse
>> synapse-core
>> 2.1.2-wso2v4
>>  
>>
>> ~Shameera.
>>
>>
>> On Thu, Aug 7, 2014 at 9:58 PM, Ishara Premadasa  wrote:
>>
>>> Hi all,
>>>
>>> I get the following build error when trying to check out remote ESB
>>> mediator project and trying to build it online. Since there are test cases
>>> created for the class mediators, it is required to add synapse-core-tests
>>> dependency into the pom.xml and use that in the test cases. Below is the
>>> dependency and my maven repository entry.
>>>
>>> 
>>> org.apache.synapse
>>> synapse-core-tests
>>> 2.1.2-wso2v4
>>>  
>>> 
>>> 
>>> true
>>> daily
>>> ignore
>>> 
>>> wso2-nexus
>>> http://maven.wso2.org/nexus/content/groups/wso2-public/
>>> 
>>> 
>>>
>>> Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException:
>>> Failure to find org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 in
>>> http://maven.wso2.org/nexus/content/groups/ws
>>> o2-public/ was cached in the local repository, resolution will not be
>>> reattempted until the update interval of wso2-nexus has elapsed or updates
>>> are forced
>>> at
>>> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:232)
>>> at
>>> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
>>> at
>>> org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:599)
>>> at
>>> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:518)
>>> at
>>> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:436)
>>> ... 26 more
>>> [ERROR]
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>>
>>> This says unable to find
>>> org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 jar but if you
>>> traverse this can be located in neus-repo [1].
>>> Any help is appreciated.
>>>
>>> [1]
>>> http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/synapse/synapse-core/2.1.2-wso2v4/
>>>
>>> Thanks!
>>> Ishara
>>> --
>>> Ishara Premasada
>>> Software Engineer,
>>> WSO2 Inc. http://wso2.com/
>>>
>>>
>>> *Blog   :  http://isharapremadasa.blogspot.com/
>>> Twitter   :
>>> https://twitter.com/ishadil  Mobile   :
>>> +94 714445832 <%2B94%20714445832>*
>>>
>>>
>>>
>>
>>
>> --
>> *Software Engineer - WSO2 Inc.*
>> *email: shameera AT wso2.com  , shameera AT apache.org
>> *
>> *phone:  +9471 922 1454 <%2B9471%20922%201454>*
>>
>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
>> *Twitter : *https://twitter.com/Shameera_R
>>
>
>
>
> --
> Ishara Premasada
> Software Engineer,
> WSO2 Inc. http://wso2.com/
>
>
> *Blog   :  http://isharapremadasa.blogspot.com/
> Twitter   :
> https://twitter.com/ishadil  Mobile   :
> +94 714445832 <%2B94%20714445832>*
>
>
>


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

Re: [Dev] G-reg is not starting

2014-08-07 Thread Akila Nimantha [IT/EKO/LOITS]

Hi Harsha,

I installed in oracle Linux environment. G-Reg version is 4.6.0. and I didn’t 
install additional features.

Regards,
Akila

From: Harsha Kumara [mailto:hars...@wso2.com]
Sent: Thursday, August 07, 2014 6:39 PM
To: Akila Nimantha [IT/EKO/LOITS]
Cc: dev@wso2.org
Subject: Re: [Dev] G-reg is not starting

Hi Akila,
What is the installation environment and the G-Reg version you using? Did you 
install any additional features?
Thanks,
Harsha

On Thu, Aug 7, 2014 at 6:25 PM, Akila Nimantha [IT/EKO/LOITS] 
mailto:aki...@lolctech.com>> wrote:
Hi all,

When we start G-reg it hangs and the following message keep repeating.


TID: [0] [Greg] [2014-08-07 17:12:03,829]  INFO 
{org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent} -  Carbon 
UserStoreMgtDSComponent activated successfully. 
{org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent}
TID: [0] [Greg] [2014-08-07 17:12:10,649]  INFO 
{org.apache.catalina.startup.TaglibUriRule} -  TLD skipped. URI: 
http://tiles.apache.org/tags-tiles is already defined 
{org.apache.catalina.startup.TaglibUriRule}
TID: [0] [Greg] [2014-08-07 17:13:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:13:11,623]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:14:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:14:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:15:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:15:11,623]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:16:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:16:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:17:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:17:11,623]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:18:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:18:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:19:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:19:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:20:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:20:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:21:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}

Re: [Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?

2014-08-07 Thread Nuwan Wimalasekara

Hi Ishara,
In your dependency, ArtifactId is not correct. and In order to get the
tests-jars you need to define classifier too. Please try out the bellow
dependency configuration and  build again.

org.apache.synapse
synapse-core
2.1.2-wso2v4
tests

Thanks,
Nuwanw

On Fri, Aug 8, 2014 at 9:34 AM, Chamara Ariyarathne 
wrote:

> This is the method I'm using.
>
> public static org.apache.synapse.MessageContext
> getTestContext(java.lang.String bodyText, java.util.Map props) throws
> java.lang.Exception;
>
>
> On Thu, Aug 7, 2014 at 11:32 PM, Ishara Premadasa  wrote:
>
>> Hi Shameera,
>>
>> I tried with the synapse-core dependency only at first. However there is
>> this TestUtils class which is required to Junit test class for custom
>> mediator that is not coming from synapse-core.
>>
>> @Chamara,
>> Can you please clarify here on this TestUtils class?
>>
>> Thanks!
>> Ishara
>>
>>
>> On Thu, Aug 7, 2014 at 1:44 PM, Shameera Rathnayaka 
>> wrote:
>>
>>> Even though jar name is synapse-core-test its artifactId is synapse-core
>>> , try with
>>>
>>> 
>>> org.apache.synapse
>>> synapse-core
>>> 2.1.2-wso2v4
>>>  
>>>
>>> ~Shameera.
>>>
>>>
>>> On Thu, Aug 7, 2014 at 9:58 PM, Ishara Premadasa 
>>> wrote:
>>>
 Hi all,

 I get the following build error when trying to check out remote ESB
 mediator project and trying to build it online. Since there are test cases
 created for the class mediators, it is required to add synapse-core-tests
 dependency into the pom.xml and use that in the test cases. Below is the
 dependency and my maven repository entry.

 org.apache.synapse
 synapse-core-tests
 2.1.2-wso2v4

 true
 daily
 ignore

 wso2-nexus

 http://maven.wso2.org/nexus/content/groups/wso2-public/

 Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException:
 Failure to find org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 in
 http://maven.wso2.org/nexus/content/groups/ws
 o2-public/ was cached in the local repository, resolution will not be
 reattempted until the update interval of wso2-nexus has elapsed or updates
 are forced
 at
 org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:232)
 at
 org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
 at
 org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:599)
 at
 org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:518)
 at
 org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:436)
 ... 26 more
 [ERROR]
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]

 This says unable to find
 org.apache.synapse:synapse-core-tests:jar:2.1.2-wso2v4 jar but if you
 traverse this can be located in neus-repo [1].
 Any help is appreciated.

 [1]
 http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/synapse/synapse-core/2.1.2-wso2v4/

 Thanks!
 Ishara
 --
 Ishara Premasada
 Software Engineer,
 WSO2 Inc. http://wso2.com/

 *Blog   :  http://isharapremadasa.blogspot.com/
 Twitter   :
 https://twitter.com/ishadil  Mobile   :
 +94 714445832 <%2B94%20714445832>*

>>>
>>>
>>> --
>>> *Software Engineer - WSO2 Inc.*
>>> *email: shameera AT wso2.com  , shameera AT
>>> apache.org *
>>> *phone:  +9471 922 1454 <%2B9471%20922%201454>*
>>>
>>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
>>> *Twitter : *https://twitter.com/Shameera_R
>>>
>>
>>
>>
>> --
>> Ishara Premasada
>> Software Engineer,
>> WSO2 Inc. http://wso2.com/
>>
>>
>> *Blog   :  http://isharapremadasa.blogspot.com/
>> Twitter   :
>> https://twitter.com/ishadil  Mobile   :
>> +94 714445832 <%2B94%20714445832>*
>>
>>
>>
>
>
> --
> *Chamara Ariyarathne*
> Senior Software Engineer - QA;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; *+94772786766 <%2B94772786766>*
>

-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [javascript] Generating UUID in javascript

2014-08-07 Thread Rushmin Fernando

whats our standard way of $subject ?

-- 
*Rushmin Fernando*
*Technical Lead*

WSO2 Inc.  - Lean . Enterprise . Middleware

email : rush...@wso2.com
mobile : +94772310855
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [javascript] Generating UUID in javascript

2014-08-07 Thread Dakshika Jayathilaka

Hi,

AFAIK you need to follow RFC 4122[1] to generate UUID. There are few js
libs that we can use to generate it easily or you can write your own
function based on [1]

https://github.com/LiosK/UUID.js

[1] http://www.ietf.org/rfc/rfc4122.txt

*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911

On Fri, Aug 8, 2014 at 4:55 AM, Rushmin Fernando  wrote:

> whats our standard way of $subject ?
>
> --
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> email : rush...@wso2.com
> mobile : +94772310855
>
>
>
> ___
> 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] [DEV] [javascript] Generating UUID in javascript

2014-08-07 Thread madhuka udantha

Hi,

If you are jaggery Dev, you have jaggery module[1] for it.

[1] https://github.com/wso2/jaggery-extensions/tree/master/uuid


On Fri, Aug 8, 2014 at 10:25 AM, Rushmin Fernando  wrote:

> whats our standard way of $subject ?
>
> --
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> email : rush...@wso2.com
> mobile : +94772310855
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Cheers,
Madhuka Udantha
http://madhukaudantha.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [javascript] Generating UUID in javascript

2014-08-07 Thread Rushmin Fernando

Thanks Dakshika ! Found [1] which is a clean and simple implementation.

@Maduka : Thanks, but this is not jaggery :-)

[1] http://byronsalau.com/blog/how-to-create-a-guid-uuid-in-javascript/


On Fri, Aug 8, 2014 at 11:00 AM, madhuka udantha 
wrote:

> Hi,
>
> If you are jaggery Dev, you have jaggery module[1] for it.
>
> [1] https://github.com/wso2/jaggery-extensions/tree/master/uuid
>
>
> On Fri, Aug 8, 2014 at 10:25 AM, Rushmin Fernando 
> wrote:
>
>> whats our standard way of $subject ?
>>
>> --
>> *Rushmin Fernando*
>> *Technical Lead*
>>
>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>
>> email : rush...@wso2.com
>> mobile : +94772310855
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Cheers,
> Madhuka Udantha
> http://madhukaudantha.blogspot.com
>



-- 
*Rushmin Fernando*
*Technical Lead*

WSO2 Inc.  - Lean . Enterprise . Middleware

email : rush...@wso2.com
mobile : +94772310855
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [javascript] Generating UUID in javascript

2014-08-07 Thread Dakshika Jayathilaka

better to check this before you use

http://stackoverflow.com/questions/6906916/collisions-when-generating-uuids-in-javascript

*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911


On Fri, Aug 8, 2014 at 5:45 AM, Rushmin Fernando  wrote:

> Thanks Dakshika ! Found [1] which is a clean and simple implementation.
>
> @Maduka : Thanks, but this is not jaggery :-)
>
> [1] http://byronsalau.com/blog/how-to-create-a-guid-uuid-in-javascript/
>
>
> On Fri, Aug 8, 2014 at 11:00 AM, madhuka udantha  > wrote:
>
>> Hi,
>>
>> If you are jaggery Dev, you have jaggery module[1] for it.
>>
>> [1] https://github.com/wso2/jaggery-extensions/tree/master/uuid
>>
>>
>> On Fri, Aug 8, 2014 at 10:25 AM, Rushmin Fernando 
>> wrote:
>>
>>> whats our standard way of $subject ?
>>>
>>> --
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>>
>>> email : rush...@wso2.com
>>> mobile : +94772310855
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Cheers,
>> Madhuka Udantha
>> http://madhukaudantha.blogspot.com
>>
>
>
>
> --
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> email : rush...@wso2.com
> mobile : +94772310855
>
>
>
> ___
> 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] G-reg is not starting

2014-08-07 Thread Harsha Kumara

What's the JDK version you using for the installation and the oracle linux
version? We recommend to use oracle java 6 and our products can be run in
oracle java 7. It's better you can ask these kind of question through
stackoverflow[1] in next time.
[1]-http://stackoverflow.com/questions/tagged/wso2


On Fri, Aug 8, 2014 at 9:50 AM, Akila Nimantha [IT/EKO/LOITS] <
aki...@lolctech.com> wrote:

>  Hi Harsha,
>
>
>
> I installed in oracle Linux environment. G-Reg version is 4.6.0. and I
> didn’t install additional features.
>
>
>
> Regards,
>
> Akila
>
>
>
> *From:* Harsha Kumara [mailto:hars...@wso2.com]
> *Sent:* Thursday, August 07, 2014 6:39 PM
> *To:* Akila Nimantha [IT/EKO/LOITS]
> *Cc:* dev@wso2.org
> *Subject:* Re: [Dev] G-reg is not starting
>
>
>
> Hi Akila,
>
> What is the installation environment and the G-Reg version you using? Did
> you install any additional features?
>
> Thanks,
>
> Harsha
>
>
>
> On Thu, Aug 7, 2014 at 6:25 PM, Akila Nimantha [IT/EKO/LOITS] <
> aki...@lolctech.com> wrote:
>
>  *Hi all,*
>
>
>
> When we start G-reg it hangs and the following message keep repeating.
>
>
>
>
>
> TID: [0] [Greg] [2014-08-07 17:12:03,829]  INFO
> {org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent} -  Carbon
> UserStoreMgtDSComponent activated successfully.
> {org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent}
>
> TID: [0] [Greg] [2014-08-07 17:12:10,649]  INFO
> {org.apache.catalina.startup.TaglibUriRule} -  TLD skipped. URI:
> http://tiles.apache.org/tags-tiles is already defined
> {org.apache.catalina.startup.TaglibUriRule}
>
> TID: [0] [Greg] [2014-08-07 17:13:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:13:11,623]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:14:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:14:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:15:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:15:11,623]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:16:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:16:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:17:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:17:11,623]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:18:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:18:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:19:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
> delayed due to the following unsatisfied items:
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:19:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
> OSGi Service: org.wso2.carbon.humantask.core.HumanTaskEngineService
> {org.wso2.carbon.core.init.CarbonServerManager}
>
> TID: [0] [Greg] [2014-08-07 17:20:11,622]  WARN
> {org.wso2.carbon.core.init.CarbonS

Re: [Dev] G-reg is not starting

2014-08-07 Thread Akila Nimantha [IT/EKO/LOITS]

Hi Harsha,

Thanks for the reply. We use  oraclelinux-release-6Server-3.0.2.x86_64 and java 
7.
Actually I searched in the internet and also in stackoverflow like sites for 
this problem.but couldn’t find any correct solution.
Is there a problem with my linux version…???

Regards,
Akila

From: Harsha Kumara [mailto:hars...@wso2.com]
Sent: Friday, August 08, 2014 12:02 PM
To: Akila Nimantha [IT/EKO/LOITS]
Cc: dev@wso2.org
Subject: Re: [Dev] G-reg is not starting

What's the JDK version you using for the installation and the oracle linux 
version? We recommend to use oracle java 6 and our products can be run in 
oracle java 7. It's better you can ask these kind of question through 
stackoverflow[1] in next time.
[1]-http://stackoverflow.com/questions/tagged/wso2

On Fri, Aug 8, 2014 at 9:50 AM, Akila Nimantha [IT/EKO/LOITS] 
mailto:aki...@lolctech.com>> wrote:
Hi Harsha,

I installed in oracle Linux environment. G-Reg version is 4.6.0. and I didn’t 
install additional features.

Regards,
Akila

From: Harsha Kumara [mailto:hars...@wso2.com]
Sent: Thursday, August 07, 2014 6:39 PM
To: Akila Nimantha [IT/EKO/LOITS]
Cc: dev@wso2.org
Subject: Re: [Dev] G-reg is not starting

Hi Akila,
What is the installation environment and the G-Reg version you using? Did you 
install any additional features?
Thanks,
Harsha

On Thu, Aug 7, 2014 at 6:25 PM, Akila Nimantha [IT/EKO/LOITS] 
mailto:aki...@lolctech.com>> wrote:
Hi all,

When we start G-reg it hangs and the following message keep repeating.


TID: [0] [Greg] [2014-08-07 17:12:03,829]  INFO 
{org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent} -  Carbon 
UserStoreMgtDSComponent activated successfully. 
{org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent}
TID: [0] [Greg] [2014-08-07 17:12:10,649]  INFO 
{org.apache.catalina.startup.TaglibUriRule} -  TLD skipped. URI: 
http://tiles.apache.org/tags-tiles is already defined 
{org.apache.catalina.startup.TaglibUriRule}
TID: [0] [Greg] [2014-08-07 17:13:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:13:11,623]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:14:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:14:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:15:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:15:11,623]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:16:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:16:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:17:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:17:11,623]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:18:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:18:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required OSGi 
Service: org.wso2.carbon.humantask.core.HumanTaskEngineService 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0] [Greg] [2014-08-07 17:19:11,622]  WARN 
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is 
delayed due to the following unsatisfied items: 
{org.wso2.carbon.core.init.CarbonServerManager}
TID: [0

[Dev] [DSS]The process of DSS will be killed after running for a period of time

Re: [Dev] Please merge the pull #7 to wso2-dev/carbon-identity

Re: [Dev] [G-Reg 5.0.0] Improved Notifications Support

Re: [Dev] Regrouping the CEP components

Re: [Dev] [GReg] Build failure on carbon-governance wso2-dev git repo

[Dev] App Manager latest build pack - 07-08-2014

Re: [Dev] Commits to kernel patch0009

[Dev] Please merge pull #16 for wso2-dev/carbon-commons

Re: [Dev] Please merge pull #16 for wso2-dev/carbon-commons

Re: [Dev] Please merge pull #16 for wso2-dev/carbon-commons

[Dev] [AF] Error while creating an application

Re: [Dev] [AF] Error while creating an application

Re: [Dev] [AF] Error while creating an application

[Dev] Issue in Permission Saving and Notifications in EMM

Re: [Dev] Issue in Permission Saving and Notifications in EMM

[Dev] G-reg is not starting

Re: [Dev] [DSS]The process of DSS will be killed after running for a period of time

Re: [Dev] G-reg is not starting

[Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?

Re: [Dev] Build failed in Jenkins: carbon-apimgt #144

[Dev] [G-Reg 5.0.0][RXT] Cannot add RXTs with "maxoccurs=unbounded" table elements

Re: [Dev] Build failed in Jenkins: carbon-apimgt #144

Re: [Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?

Re: [Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?

Re: [Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?

Re: [Dev] G-reg is not starting

Re: [Dev] [ESB][Nexus] Build fail - synapse-core-tests:jar:2.1.2-wso2v4 not found in nexus repo ?

[Dev] [DEV] [javascript] Generating UUID in javascript

Re: [Dev] [DEV] [javascript] Generating UUID in javascript

Re: [Dev] [DEV] [javascript] Generating UUID in javascript

Re: [Dev] [DEV] [javascript] Generating UUID in javascript

Re: [Dev] [DEV] [javascript] Generating UUID in javascript

Re: [Dev] G-reg is not starting

Re: [Dev] G-reg is not starting

34 matches

Site Navigation

Mail list logo

Footer information