Open GoogleCodeExporter opened 9 years ago
Another error is observed as well in page.rb,
325905813 eyedpt TRACE [http-bio-80-exec-107] openjpa.jdbc.SQL - <t
24472531, conn 15750363> [0 ms] spent
NativeException: org.apache.openjpa.persistence.PersistenceException: Multiple
concurrent threads attempted to access a single broker. By default brokers are
not thread safe; if you require and/or intend a broker to be accessed by more
than one thread, set the openjpa.Multithreaded property to true to override the
default behavior.
result at (erb):28
eval at org/jruby/RubyKernel.java:1093
result at file:/E:/opt/Tomcat 7.0/webapps/seeeye/WEB-INF/lib/jruby-complete-1.6.5.jar!/META-INF/jruby.home/lib/ruby/1.9/erb.rb:753
show_home_bulletin at page.rb:97
call at org/jruby/RubyMethod.java:121
_execute_ at WEB-INF/ruby/lib/startup.rb:16
Original comment by shen.bin...@gmail.com
on 3 Jan 2013 at 1:06
As suggested in the error message, I set openjpa.Multithreaded property to true
as a workaround. But this may slow down the site speed according to the OpenJPA
manual.
>> excerpted from OpenJPA manual:
OpenJPA respects the openjpa.Multithreaded option in that it does not impose as
much synchronization
overhead for applications that do not set this value to true. If your
application is guaranteed
to only use single-threaded access to OpenJPA resources and persistent objects,
leaving this option
as false will reduce synchronization overhead, and may result in a modest
performance increase.
Original comment by shen.bin...@gmail.com
on 3 Jan 2013 at 1:08
Original comment by shen.bin...@gmail.com
on 3 Jan 2013 at 1:11
Original issue reported on code.google.com by
shen.bin...@gmail.com
on 3 Jan 2013 at 1:05