You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ted Ross (JIRA)" <qp...@incubator.apache.org> on 2009/03/27 21:47:50 UTC
[jira] Resolved: (QPID-1702) Method invocation timeout causes odd
stack trace
[ https://issues.apache.org/jira/browse/QPID-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross resolved QPID-1702.
----------------------------
Resolution: Fixed
> Method invocation timeout causes odd stack trace
> ------------------------------------------------
>
> Key: QPID-1702
> URL: https://issues.apache.org/jira/browse/QPID-1702
> Project: Qpid
> Issue Type: Bug
> Components: Qpid Managment Framework
> Affects Versions: M4
> Environment: Fedora 10
> qmf-0.4.738618-3.fc10.x86_64
> Reporter: Ian Main
> Assignee: Ted Ross
> Fix For: 0.5
>
>
> I'm making a method call into libvirt-qpid and get an error:
> Task action processing failed: RuntimeError: Type Object has no attribute 'seq'
> /usr/lib/ruby/site_ruby/1.8/qpid/qmf.rb:1052:in `method_missing'
> /usr/lib/ruby/site_ruby/1.8/qpid/qmf.rb:1094:in `invoke'
> /usr/lib/ruby/site_ruby/1.8/qpid/qmf.rb:1035:in `method_missing'
> ./task_storage.rb:154:in `connect'
> ./taskomatic.rb:590:in `task_refresh_pool'
> ./taskomatic.rb:835:in `mainloop'
> ./taskomatic.rb:809:in `each'
> ./taskomatic.rb:809:in `mainloop'
> ./taskomatic.rb:785:in `loop'
> ./taskomatic.rb:785:in `mainloop'
> ./taskomatic.rb:874
> I think this is happening because it's timed out, but the error path has a bug in it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org