Hi,
I tried to move to atom based strategy, but having the following issue on the
GREG 3.6.0 side now after db restart when esb fetch resource from greg:
2011-03-12 13:21:52,527] ERROR
{org.wso2.carbon.registry.core.session.UserRegistry} - Failed in getting the
user realm for the tenant id: 0
{org.wso2.carbon.registry.core.session.UserRegistry}
[2011-03-12 13:22:12,398] FATAL
{org.wso2.carbon.registry.core.session.UserRegistry} - Failed to add the root
collection to the coreRegistry.
{org.wso2.carbon.registry.core.session.UserRegistry}
java.lang.NullPointerException
at
org.wso2.carbon.registry.core.jdbc.dao.JDBCPathCache.getPathID(JDBCPathCache.java:239)
at
org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.getResourceID(JDBCResourceDAO.java:57)
at
org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.resourceExists(JDBCResourceDAO.java:140)
at
org.wso2.carbon.registry.core.session.UserRegistry.addRootCollection(UserRegistry.java:357)
at
org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:288)
at
org.wso2.carbon.registry.core.session.UserRegistry.<init>(UserRegistry.java:209)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getUserRegistry(EmbeddedRegistryService.java:425)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:290)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getGovernanceSystemRegistry(EmbeddedRegistryService.java:515)
at
org.wso2.carbon.core.internal.permission.update.PermissionUpdater.needsUpdating(PermissionUpdater.java:121)
at
org.wso2.carbon.core.internal.permission.update.PermissionUpdateTask.updateSuperTenantPermissions(PermissionUpdateTask.java:83)
at
org.wso2.carbon.core.internal.permission.update.PermissionUpdateTask.run(PermissionUpdateTask.java:72)
I found the same issue at https://wso2.org/jira/browse/CARBON-8148
So is it fixed or not in GREG 3.6.0? Maybe this only happens when ESB 3.0.1
with outdated registry code communicates with GREG 3.6.0?
Also I tried to apply org.wso2.carbon.registry.core-3.1.0.jar to ESB 3.0.1,
however code changes are significant (newer vesion of CarbonUtils is used) and
completely incompatible with ESB 3.0.1.
ANY thoughts about how to get ESB 3.0.1 handle properly governance registry
database restart with JDBC or Atom based strategy???
From: [email protected] [mailto:[email protected]] On
Behalf Of Hodchenkov, Paul
Sent: Friday, March 11, 2011 2:22 PM
To: [email protected]
Subject: [Carbon-dev] Database reconnect and validation query
Hi folks,
I am using MS SQL database for registry. I am trying to figure out why esb
3.0.1 does not reconnect successfully to db when MSSQL was restarted.
I had created test resource in registry which is accessible by
http://localhost:9763/registry/resource/_system/governance/test
The problem is that ESB 3.0.1(governance folder is mounted using JDBC model)
can access this resource only after 4-5 attempt after database is restarted.
However GREG 3.6.0 (using the same MSSQL database at the same time) can access
this resource successfully from first attempt after database restart. It seems
that ESB 3.0.1 does not respect validationQuery property in registry.xml . As I
remember I had the same issue with GREG 3.5.1, however in 3.6.0 it was fixed.
Does ESB 3.0.1 share the source code for embedded registry from GREG 3.5.1
which prevents graceful reconnect? If yes, should I switch to ATOM based model
at ESB to workaround this(however in this case I will have single point of
failure)?
Also why user-mgt.xml does not support validationQuery property? I looked to
sources of JDBCUserStoreManager and it does not use validationQuery property.
Best Regards,
Paul Hodchenkov
Java developer, Oxagile
Skype: paul.hodchenkov
Email: mailto:[email protected]
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
