I did build the ESB and getting the WARN messages as hiranya pointed out. But my UI response times are normal.
Thanks, Supun.. On Fri, Apr 15, 2011 at 11:10 AM, Senaka Fernando <[email protected]> wrote: > Hi Hiranya, > > Is there a stable build of ESB (on Builder) that I can have a look into > this? Or did you add some bundles to get this to work? > > I'd like to take a look into the Event component and see what causes these > delays. From what I understand, this delay is directly linked to recent > migration of the registry eventing implementation into the new event > component which uses Qpid. > > Thanks, > Senaka. > > On Fri, Apr 15, 2011 at 10:51 AM, Hiranya Jayathilaka <[email protected]> > wrote: >> >> Hi Danushka, >> When I add the latest Qpid components to the product, the registry >> exceptions do not occur anymore. However the performance is still >> unacceptable. It takes about 10 seconds to add a simple pass through proxy. >> Here's the logs generated during the process: >> [2011-04-15 10:47:21,694] INFO >> {org.apache.synapse.core.axis2.ProxyService} - Building Axis service for >> Proxy service : FooProxy >> [2011-04-15 10:47:21,695] INFO >> {org.apache.synapse.core.axis2.ProxyService} - Adding service FooProxy to >> the Axis2 configuration >> [2011-04-15 10:47:22,384] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:23,006] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"bc6ecdc9-f463-409c-9247-d7b86d9b29c4"] >> [2011-04-15 10:47:23,109] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:23,252] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"04620ba1-e32f-49ca-ab23-711c943b608a"] >> [2011-04-15 10:47:23,352] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:23,464] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"d656fca4-f6a8-4414-8263-d9cbf89d3aff"] >> [2011-04-15 10:47:23,612] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:23,818] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"bc59b9d2-81f9-4a34-9780-237976b4c8a7"] >> [2011-04-15 10:47:23,824] INFO >> {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2 >> service: FooProxy {super-tenant} >> [2011-04-15 10:47:23,906] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:24,082] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"5dae5acb-e36c-48aa-87a1-4ea3cf01cc3c"] >> [2011-04-15 10:47:24,135] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:24,274] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"c402d60a-6945-4e80-b30e-9a55575f8456"] >> [2011-04-15 10:47:24,322] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:24,431] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"fbe59adf-cbf0-4432-ad84-ac0cb681a0af"] >> [2011-04-15 10:47:24,483] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:24,604] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"a817ddaf-9d94-480a-a0fa-6b3ba584e9de"] >> [2011-04-15 10:47:24,687] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:24,798] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"e64d7667-3a15-43bf-b46b-bc547bfb4001"] >> [2011-04-15 10:47:24,900] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:25,043] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"a7d02482-dc84-41d8-966e-a59aadb76ebd"] >> [2011-04-15 10:47:25,103] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:25,228] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"1d59fc14-2d0e-41b3-8972-6bf576d3373b"] >> [2011-04-15 10:47:25,292] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:25,462] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"fd37495e-79d1-4349-8f0d-84233b5be980"] >> [2011-04-15 10:47:25,519] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:25,624] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"673646a2-ec61-44de-875a-4a0f9110bace"] >> [2011-04-15 10:47:25,763] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:25,958] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"e5926dbb-6e33-4254-b9cd-062fbff5a4b4"] >> [2011-04-15 10:47:26,009] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:26,111] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"c5e666f7-4b95-4c6f-b7a2-d9be4155cdcb"] >> [2011-04-15 10:47:26,176] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:26,378] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"b4240b70-0e17-4fb0-807d-03d90eec4e5b"] >> [2011-04-15 10:47:26,448] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:26,609] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"3dec65cf-cf7f-4b5d-8df6-ec6c87dafede"] >> [2011-04-15 10:47:26,697] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:26,857] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"69a1ac1c-f27a-4647-9110-48a1ad101459"] >> [2011-04-15 10:47:26,908] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:27,115] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"627e18db-fa5c-4ea9-8e32-8efd78c5867a"] >> [2011-04-15 10:47:27,208] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:27,339] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"40129e06-2bdb-4ada-9f30-2d4e1b129c21"] >> [2011-04-15 10:47:27,403] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:27,575] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"65235bfb-f23f-4676-ac6d-0a473266ae7d"] >> [2011-04-15 10:47:27,656] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:27,833] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"86236b90-16a8-4b20-93f9-69fa9c798e3b"] >> [2011-04-15 10:47:27,904] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:28,039] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"be1ef9b3-c56e-4ae2-9be1-272b130701cf"] >> [2011-04-15 10:47:28,112] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:28,243] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"0bd2334e-6028-479d-accf-d89061831184"] >> [2011-04-15 10:47:28,288] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:28,399] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"34e856d2-ce4a-4128-8158-0ea199905b87"] >> [2011-04-15 10:47:28,455] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:28,674] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"5c57f9c3-674c-44c0-854f-1705fcc271a1"] >> [2011-04-15 10:47:28,744] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:28,851] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"5ca5f460-7c6c-475f-8d2b-5cbc902b0304"] >> [2011-04-15 10:47:28,908] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:29,095] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"f6370114-f429-4149-8e70-ffe4579e2aeb"] >> [2011-04-15 10:47:29,159] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:29,438] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"98d1ff13-4d28-489d-b59c-0679f93ff239"] >> [2011-04-15 10:47:29,508] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:29,776] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"a663d5e2-adc0-484c-b668-9df8eedefdd5"] >> [2011-04-15 10:47:29,828] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:30,008] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"fa812b49-92cb-4b27-ab3b-1c66ff5be3fc"] >> [2011-04-15 10:47:30,078] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:30,214] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"16a683f9-f458-44bd-ba24-8e5bb870bbdb"] >> [2011-04-15 10:47:30,280] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:30,448] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"7abc7964-89dd-43b9-a799-4541ea26bd2c"] >> [2011-04-15 10:47:30,511] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:30,679] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"695500bf-797a-4cf4-8cd7-f946e2c5c71e"] >> [2011-04-15 10:47:30,744] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:30,964] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"bb5dba44-531e-4500-9426-b0a5461b2202"] >> [2011-04-15 10:47:31,028] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:31,201] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"d5472a3e-f65f-4887-90ce-bd462a785f7b"] >> [2011-04-15 10:47:31,272] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:31,396] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"fd17ef89-196c-4131-9964-ccec28399dd0"] >> [2011-04-15 10:47:31,460] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:31,604] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"71776df2-4dc0-4a7d-a71e-003cc7597a7e"] >> [2011-04-15 10:47:31,683] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:31,846] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"e623c694-4275-4bb5-8fb7-dbae9963ae05"] >> [2011-04-15 10:47:31,911] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:32,092] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"508116a3-138d-4403-8f4a-611cf73ddf03"] >> [2011-04-15 10:47:32,176] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:32,351] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"796b23b0-5463-4d09-977c-d740a2683504"] >> [2011-04-15 10:47:32,416] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:32,553] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"7b440f1e-8563-4178-a9ef-d5c0672688c6"] >> [2011-04-15 10:47:32,617] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:32,712] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"a3bfa359-19e1-44c7-9ec1-cebe4e4f00c7"] >> [2011-04-15 10:47:32,773] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:32,910] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"ae827231-a8e9-4830-a364-46391ac86ba9"] >> [2011-04-15 10:47:32,976] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:33,070] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"cfe36cbc-c506-4922-b91d-8a2733715f76"] >> [2011-04-15 10:47:33,136] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:33,258] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"97f1f4b4-dd1f-44ea-b7e4-8c362e995ecc"] >> [2011-04-15 10:47:33,312] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:33,494] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"f88e1e3d-dc35-4f07-a8c4-823934ec4a3b"] >> [2011-04-15 10:47:33,544] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:33,650] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"8bc2afec-3b00-4a55-9b4a-6663fdb1a8fc"] >> [2011-04-15 10:47:33,700] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:33,837] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"2e72575e-a2fe-4516-afb7-1dda15646317"] >> [2011-04-15 10:47:33,915] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:33,978] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"73be5229-52e6-425c-b56a-d61b69701534"] >> [2011-04-15 10:47:34,045] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:34,217] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"1e290b2a-2292-45d6-8ef4-d223c51c6b69"] >> [2011-04-15 10:47:34,280] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:34,509] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"617770d2-d011-498a-86bf-6351b0edddfb"] >> [2011-04-15 10:47:34,535] INFO >> {org.apache.synapse.core.axis2.ProxyService} - Successfully created the >> Axis2 service for Proxy service : FooProxy >> [2011-04-15 10:47:35,367] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:35,433] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"c296203d-f23f-4d52-bedf-87e421e8d3a5"] >> [2011-04-15 10:47:35,479] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:35,676] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"f13cf693-9862-4c24-bffe-c3c64ccabe5c"] >> [2011-04-15 10:47:35,799] WARN {org.apache.qpid.transport.ClientDelegate} >> - Ignoring the idle timeout 120 set by the connection, using the brokers >> max value 0 >> [2011-04-15 10:47:35,936] WARN >> {org.apache.qpid.transport.SessionDelegate} - CLOSED: >> [ssn:"135b8c33-c528-47c4-9b96-3b42a8e53765"] >> Thanks, >> Hiranya >> On Fri, Apr 15, 2011 at 10:16 AM, Danushka Menikkumbura >> <[email protected]> wrote: >>> >>> Qpid no longer uses UserRegistry to get the user realm. Please update and >>> build components/qpid. This was fixed just before the vacation. >>> >>> Danushka >>> >>> On Thu, Apr 14, 2011 at 4:13 PM, Hiranya Jayathilaka <[email protected]> >>> wrote: >>>> >>>> Folks, >>>> Have we found a way to fix this issue? As it stands now, ESB UI is >>>> completely unusable due to this. It takes about 2 minutes to complete a >>>> simple proxy service creation operation. Also it throws out exceptions >>>> almost continuously: >>>> [2011-04-14 16:08:47,032] ERROR >>>> {org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin} - >>>> Error while retrieving UserRegistry : Failed to add the root collection to >>>> the coreRegistry. >>>> [2011-04-14 16:08:49,053] ERROR >>>> {org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO} - Failed to get >>>> the resource at path /_system/config. Timeout trying to lock table >>>> "REG_RESOURCE"; SQL statement: >>>> SELECT REG_MEDIA_TYPE, REG_CREATOR, REG_CREATED_TIME, REG_LAST_UPDATOR, >>>> REG_LAST_UPDATED_TIME, REG_VERSION, REG_DESCRIPTION, REG_CONTENT_ID FROM >>>> REG_RESOURCE WHERE REG_PATH_ID=? AND REG_NAME IS NULL AND REG_TENANT_ID=? >>>> [50200-140] >>>> org.h2.jdbc.JdbcSQLException: Timeout trying to lock table >>>> "REG_RESOURCE"; SQL statement: >>>> SELECT REG_MEDIA_TYPE, REG_CREATOR, REG_CREATED_TIME, REG_LAST_UPDATOR, >>>> REG_LAST_UPDATED_TIME, REG_VERSION, REG_DESCRIPTION, REG_CONTENT_ID FROM >>>> REG_RESOURCE WHERE REG_PATH_ID=? AND REG_NAME IS NULL AND REG_TENANT_ID=? >>>> [50200-140] >>>> at org.h2.message.DbException.getJdbcSQLException(DbException.java:327) >>>> at org.h2.message.DbException.get(DbException.java:167) >>>> at org.h2.message.DbException.get(DbException.java:144) >>>> at org.h2.table.RegularTable.doLock(RegularTable.java:466) >>>> at org.h2.table.RegularTable.lock(RegularTable.java:404) >>>> at org.h2.table.TableFilter.lock(TableFilter.java:139) >>>> at org.h2.command.dml.Select.queryWithoutCache(Select.java:554) >>>> at org.h2.command.dml.Query.query(Query.java:241) >>>> at org.h2.command.CommandContainer.query(CommandContainer.java:80) >>>> at org.h2.command.Command.executeQuery(Command.java:132) >>>> at >>>> org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:96) >>>> at >>>> org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) >>>> at >>>> org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) >>>> at >>>> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.getResourceMetaData(JDBCResourceDAO.java:1112) >>>> at >>>> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.getResource(JDBCResourceDAO.java:1172) >>>> at >>>> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.get(JDBCResourceDAO.java:229) >>>> at >>>> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.get(JDBCResourceDAO.java:225) >>>> at >>>> org.wso2.carbon.registry.core.session.UserRegistry.addRootCollection(UserRegistry.java:353) >>>> at >>>> org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:262) >>>> at >>>> org.wso2.carbon.registry.core.session.UserRegistry.<init>(UserRegistry.java:199) >>>> at >>>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getUserRegistry(EmbeddedRegistryService.java:426) >>>> at >>>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getRegistry(EmbeddedRegistryService.java:446) >>>> at >>>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getConfigUserRegistry(EmbeddedRegistryService.java:493) >>>> at >>>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getConfigUserRegistry(EmbeddedRegistryService.java:507) >>>> at >>>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getConfigUserRegistry(EmbeddedRegistryService.java:503) >>>> at >>>> org.wso2.carbon.qpid.authorization.service.qpid.QpidAuthorizationPlugin.authorise(QpidAuthorizationPlugin.java:137) >>>> at >>>> org.apache.qpid.server.security.SecurityManager$11.allowed(SecurityManager.java:390) >>>> at >>>> org.apache.qpid.server.security.SecurityManager.checkAllPlugins(SecurityManager.java:245) >>>> at >>>> org.apache.qpid.server.security.SecurityManager.authorisePublish(SecurityManager.java:386) >>>> at >>>> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:307) >>>> at >>>> org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96) >>>> at >>>> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) >>>> at >>>> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50) >>>> at >>>> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:112) >>>> at >>>> org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96) >>>> at org.apache.qpid.transport.Method.delegate(Method.java:159) >>>> at org.apache.qpid.transport.Session.received(Session.java:500) >>>> at org.apache.qpid.transport.Connection.dispatch(Connection.java:404) >>>> at >>>> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64) >>>> at >>>> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40) >>>> at >>>> org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113) >>>> at >>>> org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:108) >>>> at >>>> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54) >>>> at >>>> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40) >>>> at org.apache.qpid.transport.Method.delegate(Method.java:159) >>>> at org.apache.qpid.transport.Connection.received(Connection.java:369) >>>> at >>>> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:195) >>>> at >>>> org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:52) >>>> at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95) >>>> at >>>> org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:217) >>>> at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129) >>>> at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133) >>>> at >>>> org.apache.qpid.transport.network.Assembler.received(Assembler.java:100) >>>> at >>>> org.apache.qpid.transport.network.Assembler.received(Assembler.java:42) >>>> at >>>> org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187) >>>> at >>>> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103) >>>> at >>>> org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:42) >>>> at >>>> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:102) >>>> at >>>> org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:36) >>>> at >>>> org.apache.qpid.transport.network.mina.MINANetworkDriver.messageReceived(MINANetworkDriver.java:337) >>>> at >>>> org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived(AbstractIoFilterChain.java:703) >>>> at >>>> org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:362) >>>> at >>>> org.apache.mina.common.support.AbstractIoFilterChain.access$1200(AbstractIoFilterChain.java:54) >>>> at >>>> org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:800) >>>> at >>>> org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:243) >>>> at >>>> org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:305) >>>> at >>>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) >>>> at >>>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) >>>> at java.lang.Thread.run(Thread.java:619) >>>> Thanks, >>>> Hiranya >>>> >>>> On Fri, Apr 8, 2011 at 4:36 PM, Amila Suriarachchi <[email protected]> >>>> wrote: >>>>> >>>>> >>>>> On Thu, Apr 7, 2011 at 6:19 PM, Senaka Fernando <[email protected]> >>>>> wrote: >>>>>> >>>>>> >>>>>> On Thu, Apr 7, 2011 at 5:26 PM, Supun Kamburugamuva <[email protected]> >>>>>> wrote: >>>>>>> >>>>>>> On Thu, Apr 7, 2011 at 5:25 PM, Amila Suriarachchi <[email protected]> >>>>>>> wrote: >>>>>>> > >>>>>>> > >>>>>>> > On Thu, Apr 7, 2011 at 12:19 PM, Senaka Fernando <[email protected]> >>>>>>> > wrote: >>>>>>> >> >>>>>>> >> Hi Danushka, >>>>>>> >> >>>>>>> >> On Thu, Apr 7, 2011 at 7:18 AM, Danushka Menikkumbura >>>>>>> >> <[email protected]> >>>>>>> >> wrote: >>>>>>> >>> >>>>>>> >>> Also if this particular call is costly we can optimise some of >>>>>>> >>> them. But >>>>>>> >>> I think it is supposed to be used quite often. Isn't it? >>>>>>> >> >>>>>>> >> Yes. IMHO, the optimization could be done at the event-component >>>>>>> >> level >>>>>>> >> right, to avoid an unwanted call to Qpid. The publishers would >>>>>>> >> generate >>>>>>> >> events whenever some thing interesting happens and forward it to >>>>>>> >> the broker. >>>>>>> >> These go through the event component which manages the brokering, >>>>>>> >> and then >>>>>>> >> comes into Qpid for routing. So, if we could make the event >>>>>>> >> component a bit >>>>>>> >> more intelligent to only forward messages to Qpid if needed (some >>>>>>> >> form of >>>>>>> >> caching is needed), we should be able to avoid this right? >>>>>>> > >>>>>>> > The root cause of this problem is registry publishes some >>>>>>> > unnecessary >>>>>>> > events. i.e. registry can keep an attribute of each resource that >>>>>>> > whether >>>>>>> > some one has subscribes to that resource or not since users >>>>>>> > subscribe to the >>>>>>> > registry events using registry UI. Then fire events only for >>>>>>> > resources where >>>>>>> > there is a subscriber already. >>>>>>> >>>>>>> +1 >>>>>> >>>>>> I'm -0. IMHO, I don't like this suggestion. >>>>>> >>>>>> If the registry can do this, why would we ever need the event broker? >>>>>> >>>>>> Also, we were using eventing so far, and we did not have such >>>>>> bottlenecks. The new eventing implementation does not properly address >>>>>> this, >>>>>> which is what needs to be fixed. >>>>>> >>>>>> If we go about making changes to the registry eventing implementation >>>>>> to keep track of subscribers, I see no point of having a separate event >>>>>> broker. >>>>> >>>>> I mean to keep some property whether some one has subscribed or not. >>>>> yes it is a separate thing to decide whether it is correct to publish >>>>> event >>>>> for each and every registry resource change. Any way we need to fix any >>>>> event broker performance issues. >>>>> >>>>> Actually there is hardly any advantage using a separate broker with >>>>> registry since both subscription and message sending parts handle by the >>>>> registry itself. But some one can take the advantage of features like >>>>> hierarchical subscriptions and ability to subscribe using JMS Api etc .. >>>>> >>>>> thanks, >>>>> Amila. >>>>> >>>>>> >>>>>> Thanks, >>>>>> Senaka. >>>>>> >>>>>>> >>>>>>> Supun.. >>>>>>> >>>>>>> > >>>>>>> > thanks, >>>>>>> > Amila. >>>>>>> >> >>>>>>> >> WDYT? >>>>>>> >> >>>>>>> >> Thanks, >>>>>>> >> Senaka. >>>>>>> >>> >>>>>>> >>> Danushka >>>>>>> >>> >>>>>>> >>> On Thu, Apr 7, 2011 at 6:41 AM, Danushka Menikkumbura >>>>>>> >>> <[email protected]> >>>>>>> >>> wrote: >>>>>>> >>>>> >>>>>>> >>>>> Why 'registryService.getConfigUserRegistry().getUserRealm();' >>>>>>> >>>>> getting >>>>>>> >>>>> too long to respond? This is a widely used statement available >>>>>>> >>>>> on unit >>>>>>> >>>>> tests. Are those failing as well? If not, why is this happening >>>>>>> >>>>> during >>>>>>> >>>>> runtime only? >>>>>>> >>>> >>>>>>> >>>> Yes. Senaka I think this is the issue that we need to address as >>>>>>> >>>> I can >>>>>>> >>>> see. >>>>>>> >>>> >>>>>>> >>>> Danushka >>>>>>> >>>> >>>>>>> >>> >>>>>>> >>> >>>>>>> >>> _______________________________________________ >>>>>>> >>> Carbon-dev mailing list >>>>>>> >>> [email protected] >>>>>>> >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>>> >>> >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> >> -- >>>>>>> >> Senaka Fernando >>>>>>> >> Product Manager - WSO2 Governance Registry; >>>>>>> >> Associate Technical Lead; WSO2, Inc.; http://wso2.com >>>>>>> >> Member; Apache Software Foundation; http://apache.org >>>>>>> >> >>>>>>> >> E-mail: senaka AT wso2.com >>>>>>> >> P: +1 408 754 7388; ext: 51736; M: +94 77 322 1818 >>>>>>> >> Linked-In: http://www.linkedin.com/in/senakafernando >>>>>>> >> >>>>>>> >> Lean . Enterprise . Middleware >>>>>>> >> >>>>>>> >> >>>>>>> >> _______________________________________________ >>>>>>> >> Carbon-dev mailing list >>>>>>> >> [email protected] >>>>>>> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>>> >> >>>>>>> > >>>>>>> > >>>>>>> > _______________________________________________ >>>>>>> > Carbon-dev mailing list >>>>>>> > [email protected] >>>>>>> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>>> > >>>>>>> > >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Supun Kamburugamuva >>>>>>> Technical Lead & Product Manager, WSO2 Inc.; http://wso2.com >>>>>>> Member, Apache Software Foundation; http://www.apache.org >>>>>>> WSO2 Inc.; http://wso2.org >>>>>>> E-mail: [email protected]; Mobile: +94 77 431 3585 >>>>>>> Blog: http://supunk.blogspot.com >>>>>>> _______________________________________________ >>>>>>> Carbon-dev mailing list >>>>>>> [email protected] >>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Senaka Fernando >>>>>> Product Manager - WSO2 Governance Registry; >>>>>> Associate Technical Lead; WSO2, Inc.; http://wso2.com >>>>>> Member; Apache Software Foundation; http://apache.org >>>>>> >>>>>> E-mail: senaka AT wso2.com >>>>>> P: +1 408 754 7388; ext: 51736; M: +94 77 322 1818 >>>>>> Linked-In: http://www.linkedin.com/in/senakafernando >>>>>> >>>>>> Lean . Enterprise . Middleware >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Carbon-dev mailing list >>>>>> [email protected] >>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Carbon-dev mailing list >>>>> [email protected] >>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Hiranya Jayathilaka >>>> Senior Software Engineer; >>>> WSO2 Inc.; http://wso2.org >>>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>>> Blog: http://techfeast-hiranya.blogspot.com >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>> >> >> >> >> -- >> Hiranya Jayathilaka >> Senior Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: [email protected]; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > > -- > Senaka Fernando > Product Manager - WSO2 Governance Registry; > Associate Technical Lead; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > P: +1 408 754 7388; ext: 51736; M: +94 77 322 1818 > Linked-In: http://www.linkedin.com/in/senakafernando > > Lean . Enterprise . Middleware > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Supun Kamburugamuva Technical Lead & Product Manager, WSO2 Inc.; http://wso2.com Member, Apache Software Foundation; http://www.apache.org WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 431 3585 Blog: http://supunk.blogspot.com _______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
