Views having odd timeout issues on some clusters

Mark Nunberg added a comment - 18/Dec/12 9:55 PM Just try to do this with a simple java script (i.e. connect and query the view)

Deepti Dawar added a comment - 20/Dec/12 4:20 AM This issue persists when the view retrieval is ran from standalone java program as well. I tried this on both the VMs - 10.3.3.203, 10.3.3.209.

Deepti Dawar added a comment - 20/Dec/12 5:35 AM - edited Its working fine for server deployed on localhost.

Matt Ingenthron added a comment - 02/Jan/13 4:51 PM Michael: found out today that this is a large issue for SDKQE. Can you have a quick look at this in the next day? You may find the underlying issue.

Michael Nitschinger added a comment - 03/Jan/13 9:57 AM Please pass me the script as commented and then (or if you can't) please assign it back to me! Thanks

Michael Nitschinger added a comment - 18/Jan/13 2:39 AM According to the posted logs, it looks like debugging was not turned on. Can you please run this again with debugging turned on? To get the full logs to STDOUT, use this before initializing the CouchbaseClient in The App:       // Tell spy to use the SunLogger         Properties systemProperties = System.getProperties();         systemProperties.put("net.spy.log.LoggerImpl", "net.spy.memcached.compat.log.SunLogger");         System.setProperties(systemProperties);         Logger.getLogger("com.couchbase.client").setLevel(Level.FINEST);         //get the top Logger         Logger topLogger = java.util.logging.Logger.getLogger("");         // Handler for console (reuse it if it already exists)         Handler consoleHandler = null;         //see if there is already a console handler         for (Handler handler : topLogger.getHandlers()) {             if (handler instanceof ConsoleHandler) {                 //found the console handler                 consoleHandler = handler;                 break;             }         }         if (consoleHandler == null) {             //there was no console handler found, create a new one             consoleHandler = new ConsoleHandler();             topLogger.addHandler(consoleHandler);         }         //set the console handler to fine:         consoleHandler.setLevel(java.util.logging.Level.FINEST); Would be great if we can get all the output so we can investigate where the timeouts come from. I'm sure with a debug log it will be much easier. Thanks!

Mark Nunberg added a comment - 23/Jan/13 8:28 PM So this bug isn't such an "unknown" anymore, and has exposed itself in 1.1.0 as well as 1.1.1 and isn't limited to particular clusters - (it just seems that some clusters are more likely than others to trigger this bug). However this still needs a lot of care and analysis

Michael Nitschinger added a comment - 01/Feb/13 6:26 AM This is "kinda" blocker.