[ http://issues.apache.org/jira/browse/TUSCANY-298?page=comments#action_12378104 ]
Jim Marino commented on TUSCANY-298: ------------------------------------ The current architecture doesn't support restart semantics; users need to new up a new TuscanyRuntime which shouldn't be a burden. I fixed the hang and added a thrown exception with an informative message if they try a restart. After the milestone, we can track an ehnacement request for restart > Cannot start Tuscany runtime - Timeout waiting for Tuscany runtime to > initialize > -------------------------------------------------------------------------------- > > Key: TUSCANY-298 > URL: http://issues.apache.org/jira/browse/TUSCANY-298 > Project: Tuscany > Type: Bug > Components: Java SCA Core > Versions: M1 > Reporter: Jean-Sebastien Delfino > Assignee: Jim Marino > Fix For: M1 > Attachments: > org.apache.tuscany.samples.helloworldmc.HelloWorldServiceComponentTestCase.txt, > testcase.zip > > In your Tuscany client code do the following: > TuscanyRuntime tuscany = new TuscanyRuntime("test", null); > tuscany.start(); > > tuscany.stop(); > > tuscany.start(); > Looks like stop() is not working. You will get the following exception: > org.osoa.sca.ServiceRuntimeException: > org.apache.tuscany.core.context.ContextInitException: Timeout waiting for > module context to initialize > at > org.apache.tuscany.core.client.TuscanyRuntime.start(TuscanyRuntime.java:122) > at > org.apache.tuscany.samples.helloworldmc.HelloWorldServiceComponentTestCase.testGeetings(HelloWorldServiceComponentTestCase.java:33) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) > Caused by: org.apache.tuscany.core.context.ContextInitException: Timeout > waiting for module context to initialize > at > org.apache.tuscany.core.context.impl.AbstractCompositeContext.checkInit(AbstractCompositeContext.java:548) > at > org.apache.tuscany.core.context.impl.AbstractCompositeContext.publish(AbstractCompositeContext.java:494) > at > org.apache.tuscany.core.client.TuscanyRuntime.start(TuscanyRuntime.java:114) > ... 16 more > To reproduce use the attached test case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
