Hi All,
Getting same when login to APIM Store(2.0.0) as a tenant user, on Greg5.0.0
Beta testing. Attached the log here with. Is there any proper way to
overcome this?
*TID: [1] [] [2015-08-28 10:07:54,516] @tenant1.com http://tenant1.com
[1] [Greg]ERROR
For me this Error got disappeared when the tenant got unloaded.
*Dhanuka Ranasinghe*
Senior Software Engineer
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 715381915
On Wed, Aug 12, 2015 at 10:00 PM, Evanthika Amarasiri evanth...@wso2.com
wrote:
We have missed this
Hi,
Did we get these logs? We'd like to have a look at it.
Thanks
On Thu, Jun 18, 2015 at 6:21 AM, Evanthika Amarasiri evanth...@wso2.com
wrote:
Hello Senaka,
On Thursday, June 18, 2015, Senaka Fernando sen...@wso2.com wrote:
Hi Evanthika,
Oh! after all these years, :). I believe we can
We have missed this email. Sorry about it. We will provide logs tomorrow
after trying out the scenario once again.
Regards,
Evanthika Amarasiri
Senior Technical Lead - Quality Assurance
Mobile: +94773125935
Blog: evanthika.blogspot.com
wso2.com lean.enterprise.middleware
On Wed, Aug 12, 2015
Observed the same issue with AM 1.9.0 packs today when the local DBs were
pointed to H2 (with absolute paths). Any reason why this is happening?
Regards,
Evanthika
On Wed, Jun 17, 2015 at 3:41 PM, Asanthi Kulasinghe asan...@wso2.com
wrote:
Hi,
The same error could be reproduced on the ESB
Hi Evanthika,
Oh! after all these years, :). I believe we can forget about this and
you'll not get it for the next 2 years? :).
Anyway lets see what can be done here. Can you'll please do a favor? Can
you'll turn on the JDBC logs (with the log4jdbc driver) and then share
those log files please?
Hello Senaka,
On Thursday, June 18, 2015, Senaka Fernando sen...@wso2.com wrote:
Hi Evanthika,
Oh! after all these years, :). I believe we can forget about this and
you'll not get it for the next 2 years? :).
I doubt it :)
Anyway lets see what can be done here. Can you'll please do a
Hi,
The same error could be reproduced on the ESB 4.9.0 Test setup (1 Manager
and 2 worker nodes fronted by Nginx, DB - Oracle ) when invoking a proxy
service.
When the issue was reproduced
1. The local registry was pointed to the default H2 DB
2. Database URL was defined with the absolute path
Hi all,
Now that's a convincing issue as to H2 not having proper stability. If this
is consistently reproducible, we should probably get in contact with the H2
folks and get their feedback and see how to resolve this, but we should
also make it a point to update the production guidelines.
On Sun, Sep 8, 2013 at 7:44 PM, Senaka Fernando sen...@wso2.com wrote:
Hi Amila,
Configuration looks good. Got a few questions regarding the worker's setup.
1. Did you first create the tenant on the manager and then setup the
worker?
Tenant was created after setting up both the worker and
Hi Amila,
Could you please try using mysql database (another database) replacing H2
and try. We have seen this behavior with H2 database in some setups and did
not appear when moved to mysql. (So we can be sure that this is not a
problem of H2)
Thanks
On Sun, Sep 8, 2013 at 8:57 PM, Amila De
Hi Shelan, Amila,
Well it might be H2, but it also might be the sequence of steps that lead
to this. We probably can ensure all DBs are cleaned or try the same in a
similar setup with no data in any DB (UM, Remote Registry DB and Local
Registry DB).
Thanks,
Senaka.
On Sun, Sep 8, 2013 at 9:58
We've seen this as well with H2. See [1]. Once we moved to mySQL, we did
not encounter the same.
[1] - https://wso2.org/jira/browse/CARBON-14224
Evanthika Amarasiri
Senior Technical Lead - Quality Assurance
Mobile: +94773125935
*
*
wso2.com Lean Enterprise Middleware
On Sun, Sep 8, 2013 at
Hi Amila,
This is most probably a result of improper mounting configurations. Can you
please explain how the mounts were setup and how the registry databases
were configured?
Thanks,
Senaka.
On Sat, Sep 7, 2013 at 12:40 AM, Amila De Silva ami...@wso2.com wrote:
Hi,
I'm getting the following
It seems there is a registry write happening during API invocation.
If this is related to erroneous mounting configuration goes away after
that, then no issue. If not, we need to check why a write operation is
happening for an API invocation.
Amila, pls note.
On Sat, Sep 7, 2013 at 10:07 PM,
Hi,
I'm getting the following exception when invoking an API in a distributed
APIM setup. In the deployment, we have two gateway nodes, one serving as a
manager and the other as the worker. Published APIs are first deployed on
the manager node and then propagated to the worker node through the
16 matches
Mail list logo
