You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Arjun Roy (JIRA)" <qp...@incubator.apache.org> on 2009/07/07 21:54:14 UTC
[jira] Created: (QPID-1973) Calling session.objects fails to return
objects in certain cases
Calling session.objects fails to return objects in certain cases
----------------------------------------------------------------
Key: QPID-1973
URL: https://issues.apache.org/jira/browse/QPID-1973
Project: Qpid
Issue Type: Bug
Components: Ruby Client
Environment: Fedora 11, Qpid svn trunk revision 787286
Reporter: Arjun Roy
Suppose we have a simple schema consisting of class A and class B, where A is the parent of class B.
Suppose also that we have a simple ruby console program that, upon having the obj_props callback called by the broker, ignores all objects not of class A. For any objects of class A, it prints out the instance (of class A) and all corresponding child instances (of class B).
In the case where managed_connections is enabled in the session, if the agent connected to the broker before the console, then the session.objects method fails to return any objects. The agent can be running for a large length of time before the console connects, and other consoles that connected can see all the published qmf objects, but the console that connected after the agent cannot see the objects.
Finally, I tried writing a simple console that extended debug console that queried for objects on user input to try debugging when session.objects() fails. It appears that the console picks up the qmf objects in the schema written by the user before picking up any of the org.apache.* schemas, and that after the console picks up the org.apache.* schemas, then session.objects() works normally.
--
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
[jira] Assigned: (QPID-1973) Calling session.objects fails to
return objects in certain cases
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross reassigned QPID-1973:
------------------------------
Assignee: Ted Ross
> Calling session.objects fails to return objects in certain cases
> ----------------------------------------------------------------
>
> Key: QPID-1973
> URL: https://issues.apache.org/jira/browse/QPID-1973
> Project: Qpid
> Issue Type: Bug
> Components: Ruby Client
> Environment: Fedora 11, Qpid svn trunk revision 787286
> Reporter: Arjun Roy
> Assignee: Ted Ross
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Suppose we have a simple schema consisting of class A and class B, where A is the parent of class B.
> Suppose also that we have a simple ruby console program that, upon having the obj_props callback called by the broker, ignores all objects not of class A. For any objects of class A, it prints out the instance (of class A) and all corresponding child instances (of class B).
> In the case where managed_connections is enabled in the session, if the agent connected to the broker before the console, then the session.objects method fails to return any objects. The agent can be running for a large length of time before the console connects, and other consoles that connected can see all the published qmf objects, but the console that connected after the agent cannot see the objects.
> Finally, I tried writing a simple console that extended debug console that queried for objects on user input to try debugging when session.objects() fails. It appears that the console picks up the qmf objects in the schema written by the user before picking up any of the org.apache.* schemas, and that after the console picks up the org.apache.* schemas, then session.objects() works normally.
--
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
[jira] Resolved: (QPID-1973) Calling session.objects fails to
return objects in certain cases
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross resolved QPID-1973.
----------------------------
Resolution: Fixed
Fix Version/s: 0.6
> Calling session.objects fails to return objects in certain cases
> ----------------------------------------------------------------
>
> Key: QPID-1973
> URL: https://issues.apache.org/jira/browse/QPID-1973
> Project: Qpid
> Issue Type: Bug
> Components: Ruby Client
> Environment: Fedora 11, Qpid svn trunk revision 787286
> Reporter: Arjun Roy
> Assignee: Ted Ross
> Fix For: 0.6
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Suppose we have a simple schema consisting of class A and class B, where A is the parent of class B.
> Suppose also that we have a simple ruby console program that, upon having the obj_props callback called by the broker, ignores all objects not of class A. For any objects of class A, it prints out the instance (of class A) and all corresponding child instances (of class B).
> In the case where managed_connections is enabled in the session, if the agent connected to the broker before the console, then the session.objects method fails to return any objects. The agent can be running for a large length of time before the console connects, and other consoles that connected can see all the published qmf objects, but the console that connected after the agent cannot see the objects.
> Finally, I tried writing a simple console that extended debug console that queried for objects on user input to try debugging when session.objects() fails. It appears that the console picks up the qmf objects in the schema written by the user before picking up any of the org.apache.* schemas, and that after the console picks up the org.apache.* schemas, then session.objects() works normally.
--
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