remote JSON hangs for ~30 seconds with 6.0.4

I was unable to duplicate this on v6.0.3 and eventually hit the rate limit on the github API from my testing. :-(

Changed Status from New to Assigned

Changed Assigned User from - to @mrabbi

---

Hi I tried to reproduce on Mac OS X. Unfortunately I was not able. See my screencast: http://screencast.com/t/QRUfrh8TRgFilling time could indicate that there is something JR related, but it seems strange since all timing info were fine.I will give it a try into a Windows VM. Regards,Massimo.

Thanks for taking the time to reproduce.. I can certainly reproduce it with ease over here, even when connecting to a JSON resource on localhost. The delay is always ~30 seconds. I'll try and do a screen cast as well to show you the issue.

Here is a screen cast. I suspect its something related to the actual fetching of the resource via HTTP. Local source on disk does not cause this. The 30 seconds is also a bit too perfect of a time, almost some type of timeout.

 

 

(sorry about QT and large size, not sure how else to make it just yet)..

 

http://www.screencast.com/t/zbsPCzczWYs

 

 

Here is another screen cast (with JING this time) which shows the issue happening even in the data adapter. I can fetch this same resource from browser without an issue. I suspect it is something JVM related when fetching the resource. Where can I find the code which actually does the fetch? I'd like to break that out into a standalone app outside of eclipse using the bundled JVM and try and reproduce?

 

http://screencast.com/t/o9ngfZAxjjE

Changed Status from Assigned to Feedback Requested

---

Please first give it a try to this JRXML sample I created and use the attached exported DA. The URL from which I'm taking data is this: http://jsonplaceholder.typicode.com/commentsTry to see if the 30s delay occurs also with this and let me know.

Changed Resolution from Open to Unable to Reproduce

Changed Status from Feedback Requested to Closed

---

Hi,you can try to enable logging for org.apache.http and maybe use packet sniffer to detect possible problems at network level.For enabling this kind of logging in JSS create a log.properties (i.e: /tmp/log.properties) file like this: # Log Handlershandlers = java.util.logging.FileHandler, java.util.logging.ConsoleHandler# Handlers log level.level = INFOjava.util.logging.FileHandler.level = ALLjava.util.logging.ConsoleHandler.level = ALL# Log level for the HTTP stufforg.apache.http.level = FINEST# Default file formatterjava.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter# Specify the location and name of the log filejava.util.logging.FileHandler.pattern = /tmp/studio-common.logPlus in your Jaspersoft Studio.ini file add to the end of file the following config line:-Djava.util.logging.config.file=/tmp/log.propertiesI will close the bug for now since we are not able to reproduce at all.Just in case re-open it if you find something interesting.Regards,Massimo.