I'm getting this error while trying out session serialization across app
server instances.
The changes you made seem simple enough that maybe the problem lies
elsewhere ...
[#|2007-04-17T19:03:15.667-0700|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=26;_ThreadName=httpSSLWorkerThread-1110-1;_RequestID=eb6f2940-bc95-44b0-bd58-fd002b9aa24a;|Unexpected
end of stream
/abc/gf-cluster/glassfish/nodeagents/cluster1-nodeagent/instance-ONE/generated/jsp/j2ee-modules/depot_l3/loader/builtin/rails-integration/session/java_servlet_store.rb:21:in
`load'
/abc/gf-cluster/glassfish/nodeagents/cluster1-nodeagent/instance-ONE/generated/jsp/j2ee-modules/depot_l3/loader/builtin/rails-integration/session/java_servlet_store.rb:21:in
`restore'
/home/ashish/.jruby/lib/ruby/1.8/cgi/session.rb:304:in `[]'
/abc/gf-cluster/glassfish/nodeagents/cluster1-nodeagent/instance-ONE/applications/j2ee-modules/depot_l3/WEB-INF/gems/gems/actionpack-1.13.2/lib/action_controller/cgi_process.rb:126:in
`session'
/abc/gf-cluster/glassfish/nodeagents/cluster1-nodeagent/instance-ONE/applications/j2ee-modules/depot_l3/WEB-INF/gems/gems/actionpack-1.13.2/lib/action_controller/base.rb:1053:in
`stale_session_check!'
/abc/gf-cluster/glassfish/nodeagents/cluster1-nodeagent/instance-ONE/applications/j2ee-modules/depot_l3/WEB-INF/gems/gems/actionpack-1.13.2/lib/action_controller/cgi_process.rb:127:in
`session'
/abc/gf-cluster/glassfish/nodeagents/cluster1-nodeagent/instance-ONE/applications/j2ee-modules/depot_l3/WEB-INF/gems/gems/actionpack-1.13.2/lib/action_controller/base.rb:1053:in
`assign_shortcuts'
/abc/gf-cluster/glassfish/nodeagents/cluster1-nodeagent/instance-ONE/applications/j2ee-modules/depot_l3/WEB-INF/gems/gems/actionpack-1.13.2/lib/action_controller/flash.rb:140:in
`assign_shortcuts_with_flash'
/abc/gf-cluster/glassfish/nodeagents/cluster1-nodeagent/instance-ONE/applications/j2ee-modules/depot_l3/WEB-INF/gems/gems/actionpack-1.13.2/lib/action_controller/base.rb:424:in
`process'
/abc/gf-cluster/glassfish/nodeagents/cluster1-nodeagent/instance-ONE/applications/j2ee-modules/depot_l3/WEB-INF/gems/gems/actionpack-1.13.2/lib/action_controller/filters.rb:624:in
`process_with_filters'
/abc/gf-cluster/glassfish/nodeagents/cluster1-nodeagent/instance-ONE/applications/j2ee-modules/depot_l3/WEB-INF/gems/gems/actionpack-1.13.2/lib/action_controller/session_management.rb:114:in
`process_with_session_management_support'
/abc/gf-cluster/glassfish/nodeagents/cluster1-nodeagent/instance-ONE/applications/j2ee-modules/depot_l3/WEB-INF/gems/gems/actionpack-1.13.2/lib/action_controller/base.rb:330:in
`process'
/abc/gf-cluster/glassfish/nodeagents/cluster1-nodeagent/instance-ONE/applications/j2ee-modules/depot_l3/WEB-INF/gems/gems/rails-1.2.2/lib/dispatcher.rb:41:in
`dispatch'
<script>:0
|#]
Thanks
Ashish
Ola Bini wrote:
Fausto Lelli wrote:
Hi,
a stupid question.
I've always taken for granted that the "ruby session" was difficult to
marshall because it is bound to the runtime.
Am I missing something here ? :)
Fausto.
Yes, you are. =) The Ruby session is not difficult at all to Marshal
(that's the way Rails always does it). The things that's hard is to
Serialize it; but that can also be done by serializing a marshalled
representation of the RubyObject, and that's basically the fix I committed.
Cheers
_______________________________________________
Jruby-extras-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/jruby-extras-devel
