[ 
https://issues.apache.org/jira/browse/UNOMI-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392995#comment-16392995
 ] 

Serge Huber commented on UNOMI-170:
-----------------------------------

Hello Mitesh, 

Ok now I understand where the Outofmemory is coming from. In this test we 
create 3000 threads and it seems that this is hitting some kind of OS limit. 
Depending on your operating system, you should probably change the limits using 
the "ulimit" variable. 

Otherwise you could also download a generated snapshot from here:

[https://repository.apache.org/service/local/repo_groups/snapshots-group/content/org/apache/unomi/unomi/1.3.0-incubating-SNAPSHOT/unomi-1.3.0-incubating-20180308.141228-134.tar.gz]

Regards,

  Serge... 

> UNOMI CORS Issue is coming when trying to fetch RULES
> -----------------------------------------------------
>
>                 Key: UNOMI-170
>                 URL: https://issues.apache.org/jira/browse/UNOMI-170
>             Project: Apache Unomi
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2.0-incubating, 1.3.0-incubating
>         Environment: Mac OS
>            Reporter: Mitesh Jain
>            Priority: Major
>              Labels: security
>         Attachments: Screen Shot 2018-03-07 at 11.35.27 AM.png
>
>
> Hi,
> My Name is Mitesh Jain,
> I am new to Unomi.
> All installations are done according to this link:
> [http://unomi.incubator.apache.org/]
> When I am trying to access the rest api cxs to fetch all the rules, it is 
> showing properly in browser when I browse,
> [https://localhost:9443/cxs/rules]
> but when I am trying to access the same using my Angular application to fetch 
> rules using above url, 
> [https://localhost:9443/cxs/rules|https://localhost:9443/cxs/rules/] it will 
> make a OPTIONS call and I am getting the error as "No 
> 'Access-Control-Allow-Origin' header is present on the requested resource."
> Please Let me know how to fix this CORS issue.
> Mitesh Jain
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to