You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jürgen Schumacher (JIRA)" <tu...@ws.apache.org> on 2008/04/04 09:23:24 UTC
[jira] Created: (TUSCANY-2197) Conversations with OSGi services
expire immediately
Conversations with OSGi services expire immediately
---------------------------------------------------
Key: TUSCANY-2197
URL: https://issues.apache.org/jira/browse/TUSCANY-2197
Project: Tuscany
Issue Type: Bug
Components: Java SCA OSGi Integration
Affects Versions: Java-SCA-1.2
Environment: Windows XP, Eclipse 3.3.2
Reporter: Jürgen Schumacher
Attachments: tuscany-implosgi-osgiannotation.patch
This occurred with current revision from sca-java-1.2 branch.
I use the Tuscany OSGi bundles created by itests/osgi-tuscany in Eclipse Equinox, the SCA domain is started in a BundleActivator of my test projects. When I use implementation.osgi for a conversational service, the first method call after the init method throws a org.osoa.sca.ConversationEndedException: Conversation 44c36d6c-68af-4ba9-a9ba-354ccc5dd9d0 has expired. I debugged this and it seems that is caused by org.apache.tuscany.sca.implementation.osgi.context.OSGiAnnotations, which uses Long.MAX_VALUE as the default values for maxAge and maxIdleTime which in turn causes an overflow in the initializeConversationAttributes() of org.apache.tuscany.sca.core.conversation.ExtendedConversationImpl. This results in a negative expirationTime which is of course always smaller than the current time. When I change the default values to -1 (as in org.apache.tuscany.sca.implementation.java.impl.JavaImplementationImpl), it works. See attached patch for modules/implementation-osgi. I'm not sure if this is the best or correct solution, but it may be a hint to someone with more knowledge about this code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-2197) Conversations with OSGi services
expire immediately
Posted by "Jürgen Schumacher (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jürgen Schumacher updated TUSCANY-2197:
---------------------------------------
Attachment: tuscany-implosgi-osgiannotation.patch
> Conversations with OSGi services expire immediately
> ---------------------------------------------------
>
> Key: TUSCANY-2197
> URL: https://issues.apache.org/jira/browse/TUSCANY-2197
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA OSGi Integration
> Affects Versions: Java-SCA-1.2
> Environment: Windows XP, Eclipse 3.3.2
> Reporter: Jürgen Schumacher
> Attachments: tuscany-implosgi-osgiannotation.patch
>
>
> This occurred with current revision from sca-java-1.2 branch.
> I use the Tuscany OSGi bundles created by itests/osgi-tuscany in Eclipse Equinox, the SCA domain is started in a BundleActivator of my test projects. When I use implementation.osgi for a conversational service, the first method call after the init method throws a org.osoa.sca.ConversationEndedException: Conversation 44c36d6c-68af-4ba9-a9ba-354ccc5dd9d0 has expired. I debugged this and it seems that is caused by org.apache.tuscany.sca.implementation.osgi.context.OSGiAnnotations, which uses Long.MAX_VALUE as the default values for maxAge and maxIdleTime which in turn causes an overflow in the initializeConversationAttributes() of org.apache.tuscany.sca.core.conversation.ExtendedConversationImpl. This results in a negative expirationTime which is of course always smaller than the current time. When I change the default values to -1 (as in org.apache.tuscany.sca.implementation.java.impl.JavaImplementationImpl), it works. See attached patch for modules/implementation-osgi. I'm not sure if this is the best or correct solution, but it may be a hint to someone with more knowledge about this code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-2197) Conversations with OSGi services
expire immediately
Posted by "Rajini Sivaram (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586173#action_12586173 ]
Rajini Sivaram commented on TUSCANY-2197:
-----------------------------------------
Patch applied under revision 645290. Thank you for the patch, Juergen.
> Conversations with OSGi services expire immediately
> ---------------------------------------------------
>
> Key: TUSCANY-2197
> URL: https://issues.apache.org/jira/browse/TUSCANY-2197
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA OSGi Integration
> Affects Versions: Java-SCA-1.2
> Environment: Windows XP, Eclipse 3.3.2
> Reporter: Jürgen Schumacher
> Attachments: tuscany-implosgi-osgiannotation.patch
>
>
> This occurred with current revision from sca-java-1.2 branch.
> I use the Tuscany OSGi bundles created by itests/osgi-tuscany in Eclipse Equinox, the SCA domain is started in a BundleActivator of my test projects. When I use implementation.osgi for a conversational service, the first method call after the init method throws a org.osoa.sca.ConversationEndedException: Conversation 44c36d6c-68af-4ba9-a9ba-354ccc5dd9d0 has expired. I debugged this and it seems that is caused by org.apache.tuscany.sca.implementation.osgi.context.OSGiAnnotations, which uses Long.MAX_VALUE as the default values for maxAge and maxIdleTime which in turn causes an overflow in the initializeConversationAttributes() of org.apache.tuscany.sca.core.conversation.ExtendedConversationImpl. This results in a negative expirationTime which is of course always smaller than the current time. When I change the default values to -1 (as in org.apache.tuscany.sca.implementation.java.impl.JavaImplementationImpl), it works. See attached patch for modules/implementation-osgi. I'm not sure if this is the best or correct solution, but it may be a hint to someone with more knowledge about this code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Resolved: (TUSCANY-2197) Conversations with OSGi services
expire immediately
Posted by "Simon Laws (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws resolved TUSCANY-2197.
---------------------------------
Resolution: Fixed
Hi Jurgen. I'm marking this as resolved as Rajini applied the patch.
> Conversations with OSGi services expire immediately
> ---------------------------------------------------
>
> Key: TUSCANY-2197
> URL: https://issues.apache.org/jira/browse/TUSCANY-2197
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA OSGi Integration
> Affects Versions: Java-SCA-1.2
> Environment: Windows XP, Eclipse 3.3.2
> Reporter: Jürgen Schumacher
> Attachments: tuscany-implosgi-osgiannotation.patch
>
>
> This occurred with current revision from sca-java-1.2 branch.
> I use the Tuscany OSGi bundles created by itests/osgi-tuscany in Eclipse Equinox, the SCA domain is started in a BundleActivator of my test projects. When I use implementation.osgi for a conversational service, the first method call after the init method throws a org.osoa.sca.ConversationEndedException: Conversation 44c36d6c-68af-4ba9-a9ba-354ccc5dd9d0 has expired. I debugged this and it seems that is caused by org.apache.tuscany.sca.implementation.osgi.context.OSGiAnnotations, which uses Long.MAX_VALUE as the default values for maxAge and maxIdleTime which in turn causes an overflow in the initializeConversationAttributes() of org.apache.tuscany.sca.core.conversation.ExtendedConversationImpl. This results in a negative expirationTime which is of course always smaller than the current time. When I change the default values to -1 (as in org.apache.tuscany.sca.implementation.java.impl.JavaImplementationImpl), it works. See attached patch for modules/implementation-osgi. I'm not sure if this is the best or correct solution, but it may be a hint to someone with more knowledge about this code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org