:in const_missing' WEB-INF/gems/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:453 WEB-INF/gems/gems/actionpack-2.0.2/lib/action_view/base.rb:316:in WEB-INF/gems/gems/actionpack-2.0.2/lib/action_view/base.rb:365:in der' fault_render' in perform_action_with_benchmark’
bstract/query_cache.rb:33:in cache'
WEB-INF/gems/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:126:i
To unsubscribe from this list, please visit:
The problem is this application is working fine in windows OS, Even it
is working fine in solaris OS.
The problem is in solarise OS this application is not that stable. We
use same war file and working sometime and after few hours it start to
give above exception.
Can you please let me know what is the reason it’s working fine some
time and after some time it is failing.
This seems to be the case; it’s cleaving threads in half because it’s
not including appropriate headers…
Someone should report that to them
Thanks for you replay. Can you please let me know To whom I need to
report.
I am also feeling that it is some threading issue. I also observer when
we remove browser cache then I can access the application using same
code Other thing I observer is it’s giving error because of cache or due
to reading session variable.(process_with_session_management_support)
This seems to be the case; it’s cleaving threads in half because it’s
not including appropriate headers…
Someone should report that to them
Thanks for you replay. Can you please let me know To whom I need to
report.
Sorry, I was referring to the ruby-forum gateway splitting email
threads in half
I am also feeling that it is some threading issue. I also observer when
we remove browser cache then I can access the application using same
code Other thing I observer is it’s giving error because of cache or due
to reading session variable.(process_with_session_management_support)
Taking a closer look at your original email…
I would strongly recommend that you not use JRuby 1.1RC3. It’s now
over two years old, and was an RC after all. Can you provide more
information about how you’re building your WAR file? I think you’re
picking up a really old JRuby somewhere.
If you have absolutely no choice but to stay with 1.1RC3, our ability
to help you will be very limited
I hate to say it, but this list of gems is really old. I’m not sure
AR-JDBC will even work properly with a recent JRuby version.
I wish it were possible to be more helpful, but this app seems to have
decayed quite a bit. What was that error again?
Charlie
Hi,
This application we started to develop 1.5 year ago and this application
is working in production since last 1 year but in QA environment this
application is giving that kind of exception from last 4 month. This
application is deployed in solarise since first day of deployment and it
is working fine in solaris OS as well earlier. The environment is also
same but I don’t know the did some solarise update in between.
This seems to be the case; it’s cleaving threads in half because it’s
not including appropriate headers…
Someone should report that to them
Thanks for you replay. Can you please let me know To whom I need to
report.
Sorry, I was referring to the ruby-forum gateway splitting email
threads in half
I am also feeling that it is some threading issue. I also observer when
we remove browser cache then I can access the application using same
code Other thing I observer is it’s giving error because of cache or due
to reading session variable.(process_with_session_management_support)
Taking a closer look at your original email…
I would strongly recommend that you not use JRuby 1.1RC3. It’s now
over two years old, and was an RC after all. Can you provide more
information about how you’re building your WAR file? I think you’re
picking up a really old JRuby somewhere.
If you have absolutely no choice but to stay with 1.1RC3, our ability
to help you will be very limited
I also recommend upgrading since we have fixed several concurrency
bugs since then as well as hundreds/thousands of others. It may take
a little work, but I will lay money that you won’t have this error
anymore once you are done.
If you cannot upgrade easily you can try disabling the JIT to see if
the errror goes away:
-J-Djruby.compile.mode=OFF
We did have a concurrency error back then when replacing the default
interpreted version of the method with the JIT’d one. If you change
this and it does not work then you are tripping on something else.
Like I said we have fixed multiple concurrency bugs since then.
same but I don’t know the did some solarise update in between.
to define Login for login
WEB-INF/gems/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:260:in const_missing' app/views/login/login.html.erb:3:in render’ perform_action' perform_action_with_rescue’
WEB-INF/gems/gems/actionpack-2.0.2/lib/action_controller/filters.rb:685:in
`dispatch_cgi’
To unsubscribe from this list, please visit:
I hate to say it, but this list of gems is really old. I’m not sure
AR-JDBC will even work properly with a recent JRuby version.
I wish it were possible to be more helpful, but this app seems to have
decayed quite a bit. What was that error again?
Charlie
Hi,
This application we started to develop 1.5 year ago and this application
is working in production since last 1 year but in QA environment this
application is giving that kind of exception from last 4 month. This
application is deployed in solarise since first day of deployment and it
is working fine in solaris OS as well earlier. The environment is also
same but I don’t know the did some solarise update in between.
-Sam
Hi ,
I am receiving below exception While rendering first page of the
application.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
rescuing exception globally - Expected
/opt/wlpdomain/servers/stAppServer02/tmp/_WL_user/LoginApp/qkatyo/war/app/models/login.rb
to define Login for login
printing stack trace now…"
In shared/navigation_bar.html.erb
I also recommend upgrading since we have fixed several concurrency
bugs since then as well as hundreds/thousands of others. It may take
a little work, but I will lay money that you won’t have this error
anymore once you are done.
If you cannot upgrade easily you can try disabling the JIT to see if
the errror goes away:
-J-Djruby.compile.mode=OFF
We did have a concurrency error back then when replacing the default
interpreted version of the method with the JIT’d one. If you change
this and it does not work then you are tripping on something else.
Like I said we have fixed multiple concurrency bugs since then.
same but I don’t know the did some solarise update in between.
to define Login for login
� �WEB-INF/gems/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:260:in const_missing' � �app/views/login/login.html.erb:3:in render’ perform_action' perform_action_with_rescue’
� �WEB-INF/gems/gems/actionpack-2.0.2/lib/action_controller/filters.rb:685:in
`dispatch_cgi’
To unsubscribe from this list, please visit:
Remove the -J and then supply this -D java property setting to your
Java application server. How this is done varies per app server so
you may need to figure out how to do this.
We fix that issue after deleting connection pool and creating new
connection pool with the same name. Looks like the connection pool is
not responding at some stage.
I tried to do today using warble war and it is working in one solaris
box and does not working in another solaris box. It is giving “The
server is currently overload please try again” from last 30 min.
please advice.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
