Re: [GSoC] Adding jmx capabilities to tuscany
Hi, Thank you Raymond. Yes the jmx module activator is activated now.. I'll write a test case to show all the monitoring components on the JConsole
Re: [GSoC] Adding jmx capabilities to tuscany
Hi, Amindri.
Please follow the steps below:
1) cd modules
2) add the dependencies to base-runtime/pom.xml
dependency
groupIdorg.apache.tuscany.sca/groupId
artifactIdtuscany-jmx/artifactId
version${project.version}/version
/dependency
dependency
groupIdorg.apache.tuscany.sca/groupId
artifactIdtuscany-jmx-activator/artifactId
version${project.version}/version
/dependency
3) mvn clean install -fn (under modules)
4) Go to samples/running-tuscany/jse
5) run mvn clean install
I'm seeing started the module jmx activator..
Thanks,
Raymond
Raymond Feng
rf...@apache.org
Apache Tuscany PMC member and committer: tuscany.apache.org
Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
Personal Web Site: www.enjoyjava.com
On Aug 3, 2011, at 10:25 AM, Amindri Udugala wrote:
Hi,
Thanks for the response
I'm trying to understand the project setting for the code you use to test the
JMX integration. Do you have your own maven module or do you reuse an
existing sample module?
Are you trying to run
samples/running-tuscany/jse/src/main/java/launcher/LaunchCalculatorContribution
to see if the JMX is activated?
Yes I'm using
samples/running-tuscany/jse/src/main/java/launcher/LaunchCalculatorContribution
to test JMX integration.
If so, that pom has the following dependency:
dependency
groupIdorg.apache.tuscany.sca/groupId
artifactIdtuscany-base-runtime/artifactId
version2.0-SNAPSHOT/version
/dependency
If you have the jmx modules added to the base-runtime pom, they should be
picked up. You can run mvn dependency:tree under
samples/running-tuscany/jse to confirm.
I added the tuscany-base-runtime dependency to
samples/running-tuscany/pom.xml. Built the project (but stopped half way
through due to the permgen error)
Then executed mvn dependency:tree, and this is the result I get
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ jse ---
[INFO] org.apache.tuscany.sca.samples:jse:jar:2.0-SNAPSHOT
[INFO] +- org.apache.tuscany.sca:tuscany-base-runtime:jar:2.0-SNAPSHOT:compile
[INFO] | +- cglib:cglib:jar:2.2:compile
[INFO] | +- org.apache.ws.commons.schema:XmlSchema:jar:1.4.3:compile
[INFO] | +- asm:asm:jar:3.1:compile
[INFO] | \- wsdl4j:wsdl4j:jar:1.6.2:compile
[INFO] \- junit:junit:jar:4.8.1:test
seems like the two jmx modules are not picked up. (I have added the two jmx
modules to the modules/base-runtime/pom.xml)
Back to the build issue, can you do the following:
1) Send us the error message
2) Use mvn clean install -fae -Dmaven.test.skip=true for the purpose of
compilation and archive.
I still get the permgen error even if I ignore errors using mvn clean
install -fae. Following is end of the log.
[INFO]
[INFO] Building Apache Tuscany SCA iTest WS Contribution WSDL First
2.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4:clean (default-clean) @
itest-ws-contribution-wsdl-first ---
[INFO] Deleting
/home/amindri/tuscany/trunk/testing/itest/ws/contribution-wsdl-first/target
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-plugin-versions) @
itest-ws-contribution-wsdl-first ---
[INFO] The requirePluginVersions rule is currently not compatible with Maven3.
[INFO]
[INFO] --- build-helper-maven-plugin:1.0:add-test-source (add-source) @
itest-ws-contribution-wsdl-first ---
[INFO] Test Source directory:
/home/amindri/tuscany/trunk/testing/itest/ws/contribution-wsdl-first/target/jaxws-source
added.
[INFO]
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @
itest-ws-contribution-wsdl-first ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.2:resources (default-resources) @
itest-ws-contribution-wsdl-first ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 7 resources
[INFO] Copying 0 resource
[INFO] Copying 3 resources
[INFO]
[INFO] --- jaxws-maven-plugin:1.10:wsimport (wsimport2) @
itest-ws-contribution-wsdl-first ---
[INFO] Processing:
/home/amindri/tuscany/trunk/testing/itest/ws/contribution-wsdl-first/target/classes/helloworld-external-service.wsdl
[INFO] jaxws:wsimport args: [-s,
/home/amindri/tuscany/trunk/testing/itest/ws/contribution-wsdl-first/target/jaxws-source,
-d,
/home/amindri/tuscany/trunk/testing/itest/ws/contribution-wsdl-first/target/classes,
-verbose, -p,
org.apache.tuscany.sca.binding.ws.jaxws.external.service.iface, -target, 2.1,
-Xnocompile,
Re: [GSoC] Adding jmx capabilities to tuscany
Hi Raymond, I quite didn't understand what u asked for. Can you please explain what you exactly meant. I'm running the LaunchCalculatorContribution class in the sample module to bootstrap tuscany. On 2 August 2011 23:16, Raymond Feng enjoyj...@gmail.com wrote: Can you point out which sample from svn are you trying to pick up your modules? Thanks, Raymond * Raymond Feng rf...@apache.org Apache Tuscany PMC member and committer: tuscany.apache.org Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com Personal Web Site: www.enjoyjava.com * On Aug 2, 2011, at 9:12 AM, Amindri Udugala wrote: Hi, I tried that out but still could not resolve the memory issue, changed the surefire plugin in trunk/pom.xml as follows configuration argLine-ea -Xmx1024m -Xms756m -XX:MaxPermSize=512m/argLine /configuration I added dependencies to features/all/pom.xml and modules/base-runtime/pom.xml and still the modules are not included to the class path. Is it because I was not able to build the project? On 25 July 2011 19:24, Amindri Udugala amindriudug...@gmail.com wrote: Thanx Raymond I'll try that out. On 26 July 2011 11:24, Raymond Feng enjoyj...@gmail.com wrote: Hi, Amindri. Can you try to add your modules to features/all/pom.xml and modules/base-runtime/pom.xml? It seems that the sample uses base-runtime as the dependency to create the class path. For the memory issue, can you try to change memory setting for the surefire plugin? It is configured in the pom.xml under the plugin element whose artifactid is maven-surefire-plugin. Sent from my iPad On Jul 24, 2011, at 8:11 PM, Amindri Udugala amindriudug...@gmail.com wrote: Hi, Herewith I have listed down the artifacts that I have exposed to JMX connection and the attributes of the artifacts I have exposed. Also I have exposed some of the operations of these artifacts as well to the JMX connection. Please comment if I have missed anything out. Have attached the latest patch with all the latest changes. With this I think I have done with most of my work, but the problem which I'm facing is that I still couldn't get the jmx-activator module activated when Tuscany is bootstrapped. I'm using LaunchCalculatorContribution in the sample module to bootstrap tuscany. I found out that jmx-activator module is not included in the classpath when I'm running the LaunchCalculatorContribution. I guess the reason for this is, that I was never able to build the whole trunk at once, due to lack of perm space. I executed MAVEN_OPTS=-Xmx1024m -Xms512m -XX:MaxPermSize=384m before building the trunk, but still the problem remains. If I can get a solution for this problem, I'll be able to verify the correctness of the code... - Component *Attributes ***getComponents - Lists all runtime Components with following attributes* - Name, URI, AutoWire, Implementation Operations* getComponent(String name) - Lists all the attributes of the specified component- *Name, URI, AutoWire, Implementation, **ExtensionType, AttributeExtensions, Services, References, Properties, RequiredIntents, PolicySets, Extensions* setComponentURI(String currURI, String newURI) setComponentName(String uri, String newName) setComponentAutoWire(String uri, boolean autoWire) setComponentUnresolved(String uri, boolean unresolved) - ComponentService* * * Attributes * getComponentServices - Lists all runtime ComponentServices with following attributes* - Name, CallBackReference, Service Operations* getComponentService(String name) - Lists all attributes of the specified ComponentService - *Name, CallBackReference, Service, **InterfaceContract, Bindings,* *AttributeExtensions, Endpoints, **RequiredIntents, PolicySets , Extensions* setComponentServiceUnresolved(String name, boolean unresolved) setComponentServiceForCallback(String name, boolean forCallBack) setComponentServiceName(String currName, String newName) - Composite * Attributes *getComposites() - Lists all runtime Composites with following attributes - *Name, URI,** ExtensionType, ContributionURI, SpecVersion, Local* * Operations* getComposite(String uri) - Lists all attributes of the specified ComponentService - *Name, URI,** ExtensionType, ContributionURI, SpecVersion , Local, IsAutoWire, Unresolved, Components, Includes, FusedIncludes, **RequiredIntents, Services, references , Operations, Wires, Properties, PolicySets, Extensions,* * AttributeExtensions* setCompositeContributionURI(String uri, String contributionURI) setCompositeURI(String currURI, String
Re: [GSoC] Adding jmx capabilities to tuscany
Hi, I'm trying to understand the project setting for the code you use to test the JMX integration. Do you have your own maven module or do you reuse an existing sample module? Are you trying to run samples/running-tuscany/jse/src/main/java/launcher/LaunchCalculatorContribution to see if the JMX is activated? If so, that pom has the following dependency: dependency groupIdorg.apache.tuscany.sca/groupId artifactIdtuscany-base-runtime/artifactId version2.0-SNAPSHOT/version /dependency If you have the jmx modules added to the base-runtime pom, they should be picked up. You can run mvn dependency:tree under samples/running-tuscany/jse to confirm. Back to the build issue, can you do the following: 1) Send us the error message 2) Use mvn clean install -fae -Dmaven.test.skip=true for the purpose of compilation and archive. Thanks, Raymond Raymond Feng rf...@apache.org Apache Tuscany PMC member and committer: tuscany.apache.org Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com Personal Web Site: www.enjoyjava.com On Aug 3, 2011, at 7:03 AM, Amindri Udugala wrote: Hi Raymond, I quite didn't understand what u asked for. Can you please explain what you exactly meant. I'm running the LaunchCalculatorContribution class in the sample module to bootstrap tuscany. On 2 August 2011 23:16, Raymond Feng enjoyj...@gmail.com wrote: Can you point out which sample from svn are you trying to pick up your modules? Thanks, Raymond Raymond Feng rf...@apache.org Apache Tuscany PMC member and committer: tuscany.apache.org Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com Personal Web Site: www.enjoyjava.com On Aug 2, 2011, at 9:12 AM, Amindri Udugala wrote: Hi, I tried that out but still could not resolve the memory issue, changed the surefire plugin in trunk/pom.xml as follows configuration argLine-ea -Xmx1024m -Xms756m -XX:MaxPermSize=512m/argLine /configuration I added dependencies to features/all/pom.xml and modules/base-runtime/pom.xml and still the modules are not included to the class path. Is it because I was not able to build the project? On 25 July 2011 19:24, Amindri Udugala amindriudug...@gmail.com wrote: Thanx Raymond I'll try that out. On 26 July 2011 11:24, Raymond Feng enjoyj...@gmail.com wrote: Hi, Amindri. Can you try to add your modules to features/all/pom.xml and modules/base-runtime/pom.xml? It seems that the sample uses base-runtime as the dependency to create the class path. For the memory issue, can you try to change memory setting for the surefire plugin? It is configured in the pom.xml under the plugin element whose artifactid is maven-surefire-plugin. Sent from my iPad On Jul 24, 2011, at 8:11 PM, Amindri Udugala amindriudug...@gmail.com wrote: Hi, Herewith I have listed down the artifacts that I have exposed to JMX connection and the attributes of the artifacts I have exposed. Also I have exposed some of the operations of these artifacts as well to the JMX connection. Please comment if I have missed anything out. Have attached the latest patch with all the latest changes. With this I think I have done with most of my work, but the problem which I'm facing is that I still couldn't get the jmx-activator module activated when Tuscany is bootstrapped. I'm using LaunchCalculatorContribution in the sample module to bootstrap tuscany. I found out that jmx-activator module is not included in the classpath when I'm running the LaunchCalculatorContribution. I guess the reason for this is, that I was never able to build the whole trunk at once, due to lack of perm space. I executed MAVEN_OPTS=-Xmx1024m -Xms512m -XX:MaxPermSize=384m before building the trunk, but still the problem remains. If I can get a solution for this problem, I'll be able to verify the correctness of the code... Component Attributes getComponents - Lists all runtime Components with following attributes - Name, URI, AutoWire, Implementation Operations getComponent(String name) - Lists all the attributes of the specified component- Name, URI, AutoWire, Implementation, ExtensionType, AttributeExtensions, Services, References, Properties, RequiredIntents, PolicySets, Extensions setComponentURI(String currURI, String newURI) setComponentName(String uri, String newName) setComponentAutoWire(String uri, boolean autoWire) setComponentUnresolved(String uri, boolean unresolved)
Re: [GSoC] Adding jmx capabilities to tuscany
Hi, Thanks for the response I'm trying to understand the project setting for the code you use to test the JMX integration. Do you have your own maven module or do you reuse an existing sample module? Are you trying to run samples/running-tuscany/jse/src/main/java/launcher/LaunchCalculatorContributionto see if the JMX is activated? Yes I'm using samples/running-tuscany/jse/src/main/java/launcher/LaunchCalculatorContribution to test JMX integration. If so, that pom has the following dependency: dependency groupIdorg.apache.tuscany.sca/groupId artifactIdtuscany-base-runtime/artifactId version2.0-SNAPSHOT/version /dependency If you have the jmx modules added to the base-runtime pom, they should be picked up. You can run mvn dependency:tree under samples/running-tuscany/jse to confirm. I added the tuscany-base-runtime dependency to samples/running-tuscany/pom.xml. Built the project (but stopped half way through due to the permgen error) Then executed mvn dependency:tree, and this is the result I get [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ jse --- [INFO] org.apache.tuscany.sca.samples:jse:jar:2.0-SNAPSHOT [INFO] +- org.apache.tuscany.sca:tuscany-base-runtime:jar:2.0-SNAPSHOT:compile [INFO] | +- cglib:cglib:jar:2.2:compile [INFO] | +- org.apache.ws.commons.schema:XmlSchema:jar:1.4.3:compile [INFO] | +- asm:asm:jar:3.1:compile [INFO] | \- wsdl4j:wsdl4j:jar:1.6.2:compile [INFO] \- junit:junit:jar:4.8.1:test seems like the two jmx modules are not picked up. (I have added the two jmx modules to the modules/base-runtime/pom.xml) Back to the build issue, can you do the following: 1) Send us the error message 2) Use mvn clean install -fae -Dmaven.test.skip=true for the purpose of compilation and archive. I still get the permgen error even if I ignore errors using mvn clean install -fae. Following is end of the log. [INFO] [INFO] Building Apache Tuscany SCA iTest WS Contribution WSDL First 2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4:clean (default-clean) @ itest-ws-contribution-wsdl-first --- [INFO] Deleting /home/amindri/tuscany/trunk/testing/itest/ws/contribution-wsdl-first/target [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-plugin-versions) @ itest-ws-contribution-wsdl-first --- [INFO] The requirePluginVersions rule is currently not compatible with Maven3. [INFO] [INFO] --- build-helper-maven-plugin:1.0:add-test-source (add-source) @ itest-ws-contribution-wsdl-first --- [INFO] Test Source directory: /home/amindri/tuscany/trunk/testing/itest/ws/contribution-wsdl-first/target/jaxws-source added. [INFO] [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ itest-ws-contribution-wsdl-first --- [INFO] [INFO] --- maven-resources-plugin:2.4.2:resources (default-resources) @ itest-ws-contribution-wsdl-first --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 7 resources [INFO] Copying 0 resource [INFO] Copying 3 resources [INFO] [INFO] --- jaxws-maven-plugin:1.10:wsimport (wsimport2) @ itest-ws-contribution-wsdl-first --- [INFO] Processing: /home/amindri/tuscany/trunk/testing/itest/ws/contribution-wsdl-first/target/classes/helloworld-external-service.wsdl [INFO] jaxws:wsimport args: [-s, /home/amindri/tuscany/trunk/testing/itest/ws/contribution-wsdl-first/target/jaxws-source, -d, /home/amindri/tuscany/trunk/testing/itest/ws/contribution-wsdl-first/target/classes, -verbose, -p, org.apache.tuscany.sca.binding.ws.jaxws.external.service.iface, -target, 2.1, -Xnocompile, /home/amindri/tuscany/trunk/testing/itest/ws/contribution-wsdl-first/target/classes/helloworld-external-service.wsdl] --- constituent[0]: file:/opt/maven/lib/sisu-inject-plexus-1.4.3.1.jar constituent[1]: file:/opt/maven/lib/wagon-http-shared-1.0-beta-7.jar constituent[2]: file:/opt/maven/lib/maven-artifact-3.0.2.jar constituent[3]: file:/opt/maven/lib/plexus-utils-2.0.4.jar constituent[4]: file:/opt/maven/lib/maven-repository-metadata-3.0.2.jar constituent[5]: file:/opt/maven/lib/maven-plugin-api-3.0.2.jar constituent[6]: file:/opt/maven/lib/plexus-cipher-1.4.jar constituent[7]: file:/opt/maven/lib/maven-settings-builder-3.0.2.jar constituent[8]: file:/opt/maven/lib/commons-cli-1.2.jar constituent[9]: file:/opt/maven/lib/aether-connector-wagon-1.9.jar constituent[10]: file:/opt/maven/lib/aether-api-1.9.jar constituent[11]: file:/opt/maven/lib/plexus-component-annotations-1.5.5.jar constituent[12]: file:/opt/maven/lib/nekohtml-1.9.6.2.jar constituent[13]: file:/opt/maven/lib/sisu-inject-bean-1.4.3.1.jar constituent[14]: file:/opt/maven/lib/wagon-file-1.0-beta-7.jar constituent[15]: file:/opt/maven/lib/plexus-sec-dispatcher-1.3.jar constituent[16]:
Re: [GSoC] Adding jmx capabilities to tuscany
Hi, I tried that out but still could not resolve the memory issue, changed the surefire plugin in trunk/pom.xml as follows configuration argLine-ea -Xmx1024m -Xms756m -XX:MaxPermSize=512m/argLine /configuration I added dependencies to features/all/pom.xml and modules/base-runtime/pom.xml and still the modules are not included to the class path. Is it because I was not able to build the project? On 25 July 2011 19:24, Amindri Udugala amindriudug...@gmail.com wrote: Thanx Raymond I'll try that out. On 26 July 2011 11:24, Raymond Feng enjoyj...@gmail.com wrote: Hi, Amindri. Can you try to add your modules to features/all/pom.xml and modules/base-runtime/pom.xml? It seems that the sample uses base-runtime as the dependency to create the class path. For the memory issue, can you try to change memory setting for the surefire plugin? It is configured in the pom.xml under the plugin element whose artifactid is maven-surefire-plugin. Sent from my iPad On Jul 24, 2011, at 8:11 PM, Amindri Udugala amindriudug...@gmail.com wrote: Hi, Herewith I have listed down the artifacts that I have exposed to JMX connection and the attributes of the artifacts I have exposed. Also I have exposed some of the operations of these artifacts as well to the JMX connection. Please comment if I have missed anything out. Have attached the latest patch with all the latest changes. With this I think I have done with most of my work, but the problem which I'm facing is that I still couldn't get the jmx-activator module activated when Tuscany is bootstrapped. I'm using LaunchCalculatorContribution in the sample module to bootstrap tuscany. I found out that jmx-activator module is not included in the classpath when I'm running the LaunchCalculatorContribution. I guess the reason for this is, that I was never able to build the whole trunk at once, due to lack of perm space. I executed MAVEN_OPTS=-Xmx1024m -Xms512m -XX:MaxPermSize=384m before building the trunk, but still the problem remains. If I can get a solution for this problem, I'll be able to verify the correctness of the code... - Component *Attributes ***getComponents - Lists all runtime Components with following attributes* - Name, URI, AutoWire, Implementation Operations* getComponent(String name) - Lists all the attributes of the specified component- *Name, URI, AutoWire, Implementation, **ExtensionType, AttributeExtensions, Services, References, Properties, RequiredIntents, PolicySets, Extensions* setComponentURI(String currURI, String newURI) setComponentName(String uri, String newName) setComponentAutoWire(String uri, boolean autoWire) setComponentUnresolved(String uri, boolean unresolved) - ComponentService* * * Attributes * getComponentServices - Lists all runtime ComponentServices with following attributes* - Name, CallBackReference, Service Operations* getComponentService(String name) - Lists all attributes of the specified ComponentService - *Name, CallBackReference, Service, **InterfaceContract, Bindings,* *AttributeExtensions, Endpoints, **RequiredIntents, PolicySets , Extensions* setComponentServiceUnresolved(String name, boolean unresolved) setComponentServiceForCallback(String name, boolean forCallBack) setComponentServiceName(String currName, String newName) - Composite * Attributes *getComposites() - Lists all runtime Composites with following attributes - *Name, URI,** ExtensionType, ContributionURI, SpecVersion, Local* * Operations* getComposite(String uri) - Lists all attributes of the specified ComponentService - *Name, URI,** ExtensionType, ContributionURI, SpecVersion , Local, IsAutoWire, Unresolved, Components, Includes, FusedIncludes, **RequiredIntents, Services, references , Operations, Wires, Properties, PolicySets, Extensions,* * AttributeExtensions* setCompositeContributionURI(String uri, String contributionURI) setCompositeURI(String currURI, String newURI) setCompositeSpecVersion(String uri, String specVersion) setCompositeLocal(String uri, boolean local) setCompositeAutoWire(String uri, boolean autoWire) setCompositeUnresolved(String uri, boolean unresolved) - Endpoint** * Attributes ** *getEndpointView() - Lists all runtime Endpoints with following attributes - *URI, DeployedURI, ExtensionType, Service, Component, Binding , ComponentServiceInterfaceContract, * * Operations** * getEndpoint(String uri) - Lists attributes of the specified Endpoint - *URI, DeployedURI, ExtensionType, Service, Component, Binding ,
Re: [GSoC] Adding jmx capabilities to tuscany
Can you point out which sample from svn are you trying to pick up your modules? Thanks, Raymond Raymond Feng rf...@apache.org Apache Tuscany PMC member and committer: tuscany.apache.org Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com Personal Web Site: www.enjoyjava.com On Aug 2, 2011, at 9:12 AM, Amindri Udugala wrote: Hi, I tried that out but still could not resolve the memory issue, changed the surefire plugin in trunk/pom.xml as follows configuration argLine-ea -Xmx1024m -Xms756m -XX:MaxPermSize=512m/argLine /configuration I added dependencies to features/all/pom.xml and modules/base-runtime/pom.xml and still the modules are not included to the class path. Is it because I was not able to build the project? On 25 July 2011 19:24, Amindri Udugala amindriudug...@gmail.com wrote: Thanx Raymond I'll try that out. On 26 July 2011 11:24, Raymond Feng enjoyj...@gmail.com wrote: Hi, Amindri. Can you try to add your modules to features/all/pom.xml and modules/base-runtime/pom.xml? It seems that the sample uses base-runtime as the dependency to create the class path. For the memory issue, can you try to change memory setting for the surefire plugin? It is configured in the pom.xml under the plugin element whose artifactid is maven-surefire-plugin. Sent from my iPad On Jul 24, 2011, at 8:11 PM, Amindri Udugala amindriudug...@gmail.com wrote: Hi, Herewith I have listed down the artifacts that I have exposed to JMX connection and the attributes of the artifacts I have exposed. Also I have exposed some of the operations of these artifacts as well to the JMX connection. Please comment if I have missed anything out. Have attached the latest patch with all the latest changes. With this I think I have done with most of my work, but the problem which I'm facing is that I still couldn't get the jmx-activator module activated when Tuscany is bootstrapped. I'm using LaunchCalculatorContribution in the sample module to bootstrap tuscany. I found out that jmx-activator module is not included in the classpath when I'm running the LaunchCalculatorContribution. I guess the reason for this is, that I was never able to build the whole trunk at once, due to lack of perm space. I executed MAVEN_OPTS=-Xmx1024m -Xms512m -XX:MaxPermSize=384m before building the trunk, but still the problem remains. If I can get a solution for this problem, I'll be able to verify the correctness of the code... Component Attributes getComponents - Lists all runtime Components with following attributes - Name, URI, AutoWire, Implementation Operations getComponent(String name) - Lists all the attributes of the specified component- Name, URI, AutoWire, Implementation, ExtensionType, AttributeExtensions, Services, References, Properties, RequiredIntents, PolicySets, Extensions setComponentURI(String currURI, String newURI) setComponentName(String uri, String newName) setComponentAutoWire(String uri, boolean autoWire) setComponentUnresolved(String uri, boolean unresolved) ComponentService Attributes getComponentServices - Lists all runtime ComponentServices with following attributes - Name, CallBackReference, Service Operations getComponentService(String name) - Lists all attributes of the specified ComponentService - Name, CallBackReference, Service, InterfaceContract, Bindings, AttributeExtensions, Endpoints, RequiredIntents, PolicySets , Extensions setComponentServiceUnresolved(String name, boolean unresolved) setComponentServiceForCallback(String name, boolean forCallBack) setComponentServiceName(String currName, String newName) Composite Attributes getComposites() - Lists all runtime Composites with following attributes - Name, URI, ExtensionType, ContributionURI, SpecVersion, Local Operations getComposite(String uri) - Lists all attributes of the specified ComponentService - Name, URI, ExtensionType, ContributionURI, SpecVersion , Local, IsAutoWire, Unresolved, Components, Includes, FusedIncludes, RequiredIntents, Services, references , Operations, Wires, Properties, PolicySets, Extensions, AttributeExtensions setCompositeContributionURI(String uri,
Re: [GSoC] Adding jmx capabilities to tuscany
Thanx Raymond I'll try that out. On 26 July 2011 11:24, Raymond Feng enjoyj...@gmail.com wrote: Hi, Amindri. Can you try to add your modules to features/all/pom.xml and modules/base-runtime/pom.xml? It seems that the sample uses base-runtime as the dependency to create the class path. For the memory issue, can you try to change memory setting for the surefire plugin? It is configured in the pom.xml under the plugin element whose artifactid is maven-surefire-plugin. Sent from my iPad On Jul 24, 2011, at 8:11 PM, Amindri Udugala amindriudug...@gmail.com wrote: Hi, Herewith I have listed down the artifacts that I have exposed to JMX connection and the attributes of the artifacts I have exposed. Also I have exposed some of the operations of these artifacts as well to the JMX connection. Please comment if I have missed anything out. Have attached the latest patch with all the latest changes. With this I think I have done with most of my work, but the problem which I'm facing is that I still couldn't get the jmx-activator module activated when Tuscany is bootstrapped. I'm using LaunchCalculatorContribution in the sample module to bootstrap tuscany. I found out that jmx-activator module is not included in the classpath when I'm running the LaunchCalculatorContribution. I guess the reason for this is, that I was never able to build the whole trunk at once, due to lack of perm space. I executed MAVEN_OPTS=-Xmx1024m -Xms512m -XX:MaxPermSize=384m before building the trunk, but still the problem remains. If I can get a solution for this problem, I'll be able to verify the correctness of the code... - Component *Attributes ***getComponents - Lists all runtime Components with following attributes* - Name, URI, AutoWire, Implementation Operations* getComponent(String name) - Lists all the attributes of the specified component- *Name, URI, AutoWire, Implementation, **ExtensionType, AttributeExtensions, Services, References, Properties, RequiredIntents, PolicySets, Extensions* setComponentURI(String currURI, String newURI) setComponentName(String uri, String newName) setComponentAutoWire(String uri, boolean autoWire) setComponentUnresolved(String uri, boolean unresolved) - ComponentService* * * Attributes * getComponentServices - Lists all runtime ComponentServices with following attributes* - Name, CallBackReference, Service Operations* getComponentService(String name) - Lists all attributes of the specified ComponentService - *Name, CallBackReference, Service, **InterfaceContract, Bindings,* *AttributeExtensions, Endpoints, **RequiredIntents, PolicySets , Extensions* setComponentServiceUnresolved(String name, boolean unresolved) setComponentServiceForCallback(String name, boolean forCallBack) setComponentServiceName(String currName, String newName) - Composite * Attributes *getComposites() - Lists all runtime Composites with following attributes - *Name, URI,** ExtensionType, ContributionURI, SpecVersion, Local* * Operations* getComposite(String uri) - Lists all attributes of the specified ComponentService - *Name, URI,** ExtensionType, ContributionURI, SpecVersion , Local, IsAutoWire, Unresolved, Components, Includes, FusedIncludes, **RequiredIntents, Services, references , Operations, Wires, Properties, PolicySets, Extensions,* * AttributeExtensions* setCompositeContributionURI(String uri, String contributionURI) setCompositeURI(String currURI, String newURI) setCompositeSpecVersion(String uri, String specVersion) setCompositeLocal(String uri, boolean local) setCompositeAutoWire(String uri, boolean autoWire) setCompositeUnresolved(String uri, boolean unresolved) - Endpoint** * Attributes ** *getEndpointView() - Lists all runtime Endpoints with following attributes - *URI, DeployedURI, ExtensionType, Service, Component, Binding , ComponentServiceInterfaceContract, * * Operations** * getEndpoint(String uri) - Lists attributes of the specified Endpoint - *URI, DeployedURI, ExtensionType, Service, Component, Binding , ComponentServiceInterfaceContract, AsyncInvocation, Remote, Unresolved, PolicySets, EndpointReferences, RequiredIntents* setEndpointUnresolved(String epURI, boolean unresolved); setEndpointRemote(String epURI, boolean remote); setEndpointURI(String epURI); setEndpointDeployedURI(String epURI, String depURI)* * - EndpointReference * Attributes *getEndpointReferences() - Lists all runtime EndpointReferences with
[GSoC] Adding jmx capabilities to tuscany
Hi, Herewith I have listed down the artifacts that I have exposed to JMX connection and the attributes of the artifacts I have exposed. Also I have exposed some of the operations of these artifacts as well to the JMX connection. Please comment if I have missed anything out. Have attached the latest patch with all the latest changes. With this I think I have done with most of my work, but the problem which I'm facing is that I still couldn't get the jmx-activator module activated when Tuscany is bootstrapped. I'm using LaunchCalculatorContribution in the sample module to bootstrap tuscany. I found out that jmx-activator module is not included in the classpath when I'm running the LaunchCalculatorContribution. I guess the reason for this is, that I was never able to build the whole trunk at once, due to lack of perm space. I executed MAVEN_OPTS=-Xmx1024m -Xms512m -XX:MaxPermSize=384m before building the trunk, but still the problem remains. If I can get a solution for this problem, I'll be able to verify the correctness of the code... - Component *Attributes ***getComponents - Lists all runtime Components with following attributes* - Name, URI, AutoWire, Implementation Operations* getComponent(String name) - Lists all the attributes of the specified component- *Name, URI, AutoWire, Implementation, **ExtensionType, AttributeExtensions, Services, References, Properties, RequiredIntents, PolicySets, Extensions* setComponentURI(String currURI, String newURI) setComponentName(String uri, String newName) setComponentAutoWire(String uri, boolean autoWire) setComponentUnresolved(String uri, boolean unresolved) - ComponentService* * * Attributes * getComponentServices - Lists all runtime ComponentServices with following attributes* - Name, CallBackReference, Service Operations* getComponentService(String name) - Lists all attributes of the specified ComponentService - *Name, CallBackReference, Service, **InterfaceContract, Bindings,* *AttributeExtensions, Endpoints, **RequiredIntents, PolicySets , Extensions* setComponentServiceUnresolved(String name, boolean unresolved) setComponentServiceForCallback(String name, boolean forCallBack) setComponentServiceName(String currName, String newName) - Composite * Attributes *getComposites() - Lists all runtime Composites with following attributes - *Name, URI,** ExtensionType, ContributionURI, SpecVersion, Local* * Operations* getComposite(String uri) - Lists all attributes of the specified ComponentService - *Name, URI,** ExtensionType, ContributionURI, SpecVersion , Local, IsAutoWire, Unresolved, Components, Includes, FusedIncludes, **RequiredIntents, Services, references , Operations, Wires, Properties, PolicySets, Extensions,* *AttributeExtensions * setCompositeContributionURI(String uri, String contributionURI) setCompositeURI(String currURI, String newURI) setCompositeSpecVersion(String uri, String specVersion) setCompositeLocal(String uri, boolean local) setCompositeAutoWire(String uri, boolean autoWire) setCompositeUnresolved(String uri, boolean unresolved) - Endpoint** * Attributes ** *getEndpointView() - Lists all runtime Endpoints with following attributes - *URI, DeployedURI, ExtensionType, Service, Component, Binding , ComponentServiceInterfaceContract, * * Operations** * getEndpoint(String uri) - Lists attributes of the specified Endpoint - *URI, DeployedURI, ExtensionType, Service, Component, Binding , ComponentServiceInterfaceContract, AsyncInvocation, Remote, Unresolved, PolicySets, EndpointReferences, RequiredIntents* setEndpointUnresolved(String epURI, boolean unresolved); setEndpointRemote(String epURI, boolean remote); setEndpointURI(String epURI); setEndpointDeployedURI(String epURI, String depURI)* * - EndpointReference * Attributes *getEndpointReferences() - Lists all runtime EndpointReferences with following attributes - *URI,Status, CallbackEndpoint, TargetEndpoint , Binding, Component, AsyncInvocation* * Operations* getEndpointReference(String epRefUri) - Lists attributes of the specified EndpointReference - *URI,Status, CallbackEndpoint, TargetEndpoint , Binding, Component, AsyncInvocation, ComponentReferenceInterfaceContract, ExtensionType, Reference*, *RequiredIntents, PolicySets* setEndpointReferenceURI(String epRefUri, String uri) setEndpointReferenceUnresolved(String epRefUri, boolean unresolved) setStatus(String epRefUri, String status) -
Re: [GSoC] Adding jmx capabilities to tuscany
Hi, Amindri. Can you try to add your modules to features/all/pom.xml and modules/base-runtime/pom.xml? It seems that the sample uses base-runtime as the dependency to create the class path. For the memory issue, can you try to change memory setting for the surefire plugin? It is configured in the pom.xml under the plugin element whose artifactid is maven-surefire-plugin. Sent from my iPad On Jul 24, 2011, at 8:11 PM, Amindri Udugala amindriudug...@gmail.com wrote: Hi, Herewith I have listed down the artifacts that I have exposed to JMX connection and the attributes of the artifacts I have exposed. Also I have exposed some of the operations of these artifacts as well to the JMX connection. Please comment if I have missed anything out. Have attached the latest patch with all the latest changes. With this I think I have done with most of my work, but the problem which I'm facing is that I still couldn't get the jmx-activator module activated when Tuscany is bootstrapped. I'm using LaunchCalculatorContribution in the sample module to bootstrap tuscany. I found out that jmx-activator module is not included in the classpath when I'm running the LaunchCalculatorContribution. I guess the reason for this is, that I was never able to build the whole trunk at once, due to lack of perm space. I executed MAVEN_OPTS=-Xmx1024m -Xms512m -XX:MaxPermSize=384m before building the trunk, but still the problem remains. If I can get a solution for this problem, I'll be able to verify the correctness of the code... Component Attributes getComponents - Lists all runtime Components with following attributes - Name, URI, AutoWire, Implementation Operations getComponent(String name) - Lists all the attributes of the specified component- Name, URI, AutoWire, Implementation, ExtensionType, AttributeExtensions, Services, References, Properties, RequiredIntents, PolicySets, Extensions setComponentURI(String currURI, String newURI) setComponentName(String uri, String newName) setComponentAutoWire(String uri, boolean autoWire) setComponentUnresolved(String uri, boolean unresolved) ComponentService Attributes getComponentServices - Lists all runtime ComponentServices with following attributes - Name, CallBackReference, Service Operations getComponentService(String name) - Lists all attributes of the specified ComponentService - Name, CallBackReference, Service, InterfaceContract, Bindings, AttributeExtensions, Endpoints, RequiredIntents, PolicySets , Extensions setComponentServiceUnresolved(String name, boolean unresolved) setComponentServiceForCallback(String name, boolean forCallBack) setComponentServiceName(String currName, String newName) Composite Attributes getComposites() - Lists all runtime Composites with following attributes - Name, URI, ExtensionType, ContributionURI, SpecVersion, Local Operations getComposite(String uri) - Lists all attributes of the specified ComponentService - Name, URI, ExtensionType, ContributionURI, SpecVersion , Local, IsAutoWire, Unresolved, Components, Includes, FusedIncludes, RequiredIntents, Services, references , Operations, Wires, Properties, PolicySets, Extensions, AttributeExtensions setCompositeContributionURI(String uri, String contributionURI) setCompositeURI(String currURI, String newURI) setCompositeSpecVersion(String uri, String specVersion) setCompositeLocal(String uri, boolean local) setCompositeAutoWire(String uri, boolean autoWire) setCompositeUnresolved(String uri, boolean unresolved) Endpoint Attributes getEndpointView() - Lists all runtime Endpoints with following attributes - URI, DeployedURI, ExtensionType, Service, Component, Binding , ComponentServiceInterfaceContract, Operations getEndpoint(String uri) - Lists attributes of the specified Endpoint - URI, DeployedURI, ExtensionType, Service, Component, Binding , ComponentServiceInterfaceContract, AsyncInvocation, Remote, Unresolved, PolicySets, EndpointReferences, RequiredIntents setEndpointUnresolved(String epURI, boolean
