[jira] [Created] (TUSCANY-3870) Invocations fail on a node which stopped/started a composite on a remote node
Invocations fail on a node which stopped/started a composite on a remote node - Key: TUSCANY-3870 URL: https://issues.apache.org/jira/browse/TUSCANY-3870 Project: Tuscany Issue Type: Bug Reporter: ant elder Fix For: Java-SCA-2.0 Invocations fail on a node which stopped/started a composite on a remote node. Say there are two nodes, nodeA and nodeB, and nodeA is running helloworld.composite with a HellowordComponent. if nodeB stops and starts helloworld.composite on nodeA and then the service is tried to be invoked from a proxy got from nodeB.getService it fails with an NPE. Something seems like its not cleaned up or something after the restart. See the itest testing/itests/nodes/remote-stop-start which demonstrates the issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TUSCANY-3867) Confirm that framework/extension/composite starts and stops all happen in the right places
[ https://issues.apache.org/jira/browse/TUSCANY-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046419#comment-13046419 ] Simon Laws commented on TUSCANY-3867: - This is the way I think it should work... Tuscany will start a composite when requested and, assuming that there are no errors at this stage, will mark all components as started, see RuntimeComponent.isStarted(). A component being started doesn't necessarily mean that implementation instances will exist but it does mean that it's implementation and binding providers will have been started. If an error is detected during start the runtime will stop any providers it's already started for the failing component and then return an exception. It's the Node's (or whatever calls the activator) responsibility to call stop on the activator to stop any other components that have been started. Component instances themselves are created in different ways depending on component scope and other configuration. Here are the combinations. COMPOSITE/@EagerInit - one instance is created at component start time COMPOSITE - One instance is created at the time the first message arrives STATELESS - A new instance is created for each message These different configurations have an impact on how errors are handled and hence how shutdown operates. The general rule of thumb is that if an exception is detected while the composite is being started (the COMPOSITE/@EagerInit case) then the Node will trap the error and use the underlying SPI to shut down all the components in the composite before throwing the exception to the code that called start. If the exception is detected on receipt of a message then just the implementation instance is removed and the component remains in the started state until the code that called the node calls node.stop Confirm that framework/extension/composite starts and stops all happen in the right places -- Key: TUSCANY-3867 URL: https://issues.apache.org/jira/browse/TUSCANY-3867 Project: Tuscany Issue Type: Bug Components: SCA Java Runtime Reporter: Simon Laws Assignee: Simon Laws Priority: Minor Fix For: Java-SCA-2.0 Looking at some of the tests I'm not sure that we catch all of the start/stop situations. It's not clear though so I'm raising this JIRA and I'll write a test to track what's going on. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TUSCANY-3852) SOAP Envelope is not available from the response message context in PolicyInterceptor.invoke() after getNext().invoke() returns.
[ https://issues.apache.org/jira/browse/TUSCANY-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-3852: --- Assignee: Simon Laws SOAP Envelope is not available from the response message context in PolicyInterceptor.invoke() after getNext().invoke() returns. Key: TUSCANY-3852 URL: https://issues.apache.org/jira/browse/TUSCANY-3852 Project: Tuscany Issue Type: Improvement Components: Java SCA Policy Affects Versions: Java-SCA-2.0-Beta1 Environment: Windows 2003 using Tuscany 2.0-Beta2 for Java Reporter: Gang Yang Assignee: Simon Laws Fix For: Java-SCA-2.0 Attachments: TS3Policy2.zip In a policy extension written for binding.ws using Axis2 provider, when PolicyInterceptor.invoke() is called, the response message returned by the getNext().invoke() does not contain the response SOAP envelope. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TUSCANY-3855) We need to be able to pass context through a component implementation
[ https://issues.apache.org/jira/browse/TUSCANY-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-3855: --- Assignee: Simon Laws We need to be able to pass context through a component implementation --- Key: TUSCANY-3855 URL: https://issues.apache.org/jira/browse/TUSCANY-3855 Project: Tuscany Issue Type: New Feature Reporter: Gang Yang Assignee: Simon Laws Fix For: Java-SCA-2.0 See the discussion for more details: http://mail-archives.apache.org/mod_mbox/tuscany-dev/201102.mbox/%3cAANLkTikg1FFgFCcoDfudahrbXYkik76MhQhc5z=nf...@mail.gmail.com%3e -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TUSCANY-3853) PolicyProvider.configureBinding() is called with a configuration object that does not contain Axis2's ConfigurationContext on client/reference side.
[ https://issues.apache.org/jira/browse/TUSCANY-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-3853: --- Assignee: Simon Laws PolicyProvider.configureBinding() is called with a configuration object that does not contain Axis2's ConfigurationContext on client/reference side. Key: TUSCANY-3853 URL: https://issues.apache.org/jira/browse/TUSCANY-3853 Project: Tuscany Issue Type: Bug Components: Java SCA Policy Affects Versions: Java-SCA-2.0-Beta1 Environment: Windows 2003 using Tuscany 2.0-Beta2 for Java Reporter: Gang Yang Assignee: Simon Laws Fix For: Java-SCA-2.0 In a policy extension written for binding.ws with the intent to access Axis2 ConfigurationContext in order to add Axis2 handlers, the PolicyProvider.configureBinding() is called with the Axis2BaseBindingProvider object that returns null for getAxisConfigurationContext(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: EndpointRegistry / DomainRegistry
On Thu, May 26, 2011 at 12:41 PM, ant elder ant.el...@gmail.com wrote: On Fri, May 20, 2011 at 10:16 AM, ant elder ant.el...@gmail.com wrote: This is where i've got to so far, I think there is refactoring that could be done but this is the current state. It seems like there are now several types of things in the domain registry, theres info about installed contributions, there's info about the distributed domain - eg what composites are running where, and there is info about the active endpoints. I wonder if those should be three separate things? One of the refactorings could be to separate out the things like the contribution information from the runtime information, so perhaps have something like a ContributionRepository which holds the ContributionDescriptions and provides access to the actual contribution contents. ...ant Looking at the DomainRegistryFactory there are operations... DomainRegistry getEndpointRegistry(String endpointRegistryURI, String domainURI); CollectionDomainRegistry getEndpointRegistries(); Any reason I can't change these to getDomainRegistry etc. or was this left in case the idea of having a ContributionRepository takes hold? Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: svn commit: r1133713 - in /tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime: ./ src/main/java/org/apache/tuscany/sca/binding/comet/runtime/ src/main/java/org/apache/tuscany/sca/binding/com
Hi Ant,
I've noticed your commit the other day and was going to ask you what's the
purpose and what should I do now. Thanks for pointing this out.
I've made the necessary adjustments to the LICENSE file and I'm trying to
run the test again which doesn't seem to work... Do I have to start a full
build?
Florian
On Thu, Jun 9, 2011 at 4:46 PM, ant elder ant.el...@gmail.com wrote:
Just as an FYI as you don't know its there - there is an itest that
checks that all the dependency jars in the distribution are mentioned
in the LICENSE file, so when versions get changed the distribution
LICENSE file also needs to be updated or else the itest fails -
https://builds.apache.org/job/Tuscany-2x/org.apache.tuscany.sca$itest-distribution-legal-checks/239/console
The distribution LICENSE file is at
https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/distribution/all/src/main/release/bin/LICENSE
...ant
On Thu, Jun 9, 2011 at 9:35 AM, fm...@apache.org wrote:
Author: fmoga
Date: Thu Jun 9 08:35:42 2011
New Revision: 1133713
URL: http://svn.apache.org/viewvc?rev=1133713view=rev
Log:
Use the BroadcasterLifeCyclePolicy and new callback mechanism from
Atmosphere to improve resource cleanup. Move to Atmosphere 0.8-SNAPSHOT.
Modified:
tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/pom.xml
tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/src/main/java/org/apache/tuscany/sca/binding/comet/runtime/CometCallbackInvoker.java
tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/src/main/java/org/apache/tuscany/sca/binding/comet/runtime/ServletFactory.java
tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/src/main/java/org/apache/tuscany/sca/binding/comet/runtime/handler/CometBindingHandler.java
Modified:
tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/pom.xml
URL:
http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/pom.xml?rev=1133713r1=1133712r2=1133713view=diff
==
--- tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/pom.xml
(original)
+++ tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/pom.xml Thu
Jun 9 08:35:42 2011
@@ -61,7 +61,7 @@
dependency
groupIdorg.atmosphere/groupId
artifactIdatmosphere-jersey/artifactId
- version0.7.1/version
+ version0.8-SNAPSHOT/version
scopecompile/scope
/dependency
/dependencies
@@ -78,14 +78,12 @@
/releases
/repository
repository
- idoss-sonatype-repository/id
+ idsonatype-releases/id
url
https://oss.sonatype.org/content/repositories/releases//url
- snapshots
- enabledtrue/enabled
- /snapshots
- releases
- enabledtrue/enabled
- /releases
+ /repository
+ repository
+ idsonatype-snapshots/id
+ url
https://oss.sonatype.org/content/repositories/snapshots//url
/repository
/repositories
Modified:
tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/src/main/java/org/apache/tuscany/sca/binding/comet/runtime/CometCallbackInvoker.java
URL:
http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/src/main/java/org/apache/tuscany/sca/binding/comet/runtime/CometCallbackInvoker.java?rev=1133713r1=1133712r2=1133713view=diff
==
---
tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/src/main/java/org/apache/tuscany/sca/binding/comet/runtime/CometCallbackInvoker.java
(original)
+++
tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/src/main/java/org/apache/tuscany/sca/binding/comet/runtime/CometCallbackInvoker.java
Thu Jun 9 08:35:42 2011
@@ -65,9 +65,6 @@ public class CometCallbackInvoker implem
Message response = new MessageImpl();
if (broadcaster == null) {
response.setBody(Status.CLIENT_DISCONNECTED);
-} else if (broadcaster.getAtmosphereResources().isEmpty()) {
-CometSessionManager.remove(sessionId);
-response.setBody(Status.CLIENT_DISCONNECTED);
} else {
String callbackMethod = msg.getTo().getURI();
Object[] body = msg.getBody();
Modified:
tuscany/sca-java-2.x/trunk/modules/binding-comet-runtime/src/main/java/org/apache/tuscany/sca/binding/comet/runtime/ServletFactory.java
URL:
