<< January 2012 | Home | March 2012 >>

RSS | Atom | E-mail

Navigate

Tags | Advanced Search

Tags

Recent Blog Entries

Profiling JRuby with NetBeans
A case study and tutorial on using the NetBeans profiler to profile Ruby code running on the JVM via JRuby. Walks through the steps of configuring NetBeans, launching JRuby with profiling settings, connecting NetBeans to JRuby, and analyzing the ...
Comparing Ruby exceptions to additional stat() test
A common idiom in Ruby code (FileUtils, ActiveSupport, Hike) when dealing with a file or directory that may or may not exist is to go ahead and call a method that expects the file to exist (such as open), and catch the exception raised for nonexistent ...
ActiveRecord connection pool fairness
ActiveRecord maintains a pool of database connections that may be used by multiple threads to perform database work. If many threads are contending for a smaller number of connections, the behavior of the connection pool becomes important. Read ...
Asynchronous responses in Rack
Rack is an interface for Ruby components accepting and responding to HTTP requests synchronously. Though there is not an official Rack spec for asynchronous responses, Rack servers such as Rainbows! and Thin provide an asynchronous interface for ...

Recent Responses

Re: Comparing Ruby exceptions to additional stat() test
Ethan, Thanks, this is an excellent point. I'd personally like to see a lower level file api that returns error codes, or perhaps one that accepts an error handler as a block. I'd been working on a proof-of-concept of such an api, but it is on the far ...
Re: Comparing Ruby exceptions to additional stat() test
The problem with stat-ing a file before you open it is that there may be nonzero time between the two, in which time the file may have been deleted by somebody else. if you stat a file, another process deletes it, and then you open the file, you'll get an ...

Log me in using Google

Deploying Sonar to JBoss AS7

Sonar does not officially support the JBoss AS7 application server / servlet container (or any JBoss version). By default, JBoss's JPA modules notice the persistence.xml file in sonar-core-2.13.1.jar!/META-INF/persistence.xml and attempt to setup JPA (Hibernate). This fails (because Sonar isn't expecting JBoss to be doing anything in the way of setting up Hibernate). One solution is to remove the JPA module from JBoss.

February 2012
Sun	Mon	Tue	Wed	Thu	Fri	Sat
			1	2	3	4
5	6	7	8	9	10	11
12	13	14	15	16	17	18
19	20	21	22	23	24	25
26	27	28	29
Jan \| Today \| Mar

2013	2012 October (2) May (1) April (1) March (1) February (1)
2011	2010 April (1)
2009 February (1)	2008
2007	2006
2005	2004
2003 January (1)	2002 December (1)