Menu
▾
▴
smartfrog-users — Mailing list for SmarFrog
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
(4) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(7) |
Feb
(20) |
Mar
(2) |
Apr
(6) |
May
(10) |
Jun
(1) |
Jul
(2) |
Aug
(3) |
Sep
(7) |
Oct
(1) |
Nov
(4) |
Dec
(2) |
| 2009 |
Jan
(2) |
Feb
|
Mar
(4) |
Apr
|
May
(9) |
Jun
(9) |
Jul
(2) |
Aug
(2) |
Sep
(5) |
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
(3) |
Mar
|
Apr
(7) |
May
(9) |
Jun
(4) |
Jul
(5) |
Aug
|
Sep
(6) |
Oct
(2) |
Nov
(10) |
Dec
(12) |
| 2011 |
Jan
(22) |
Feb
(6) |
Mar
(2) |
Apr
(1) |
May
(7) |
Jun
(2) |
Jul
(1) |
Aug
(4) |
Sep
(1) |
Oct
(2) |
Nov
(2) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
(7) |
Jun
|
Jul
(3) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Aleksandar K. <ako...@re...> - 2012-09-27 18:11:20
|
Hello, I am new to smartfrog and am exploring if it is going to suite my needs. I noticed there is some work for supporting groovy as a language for components. Is this support stable enough? Any documentation/examples for using it? Thank you! |
|
From: Radoslav H. <rh...@re...> - 2012-08-29 16:46:38
|
Hi guys, We have open-sourced our in-house Jenkins SmartFrog plugin. Give it a go if you use Jenkins/Hudson to run SF jobs: https://github.com/jenkinsci/smartfrog-plugin Enjoy, Rado |
|
From: Brian L. <bl...@sg...> - 2012-08-01 23:52:30
|
Hi,<mailto:sma...@li...> Is SmartFrog capable of managing images? For example a chroot environment, linux containers (LXC) or other ways of setting up an image that can later be applied to host(s) ? |
|
From: Radoslav H. <rh...@re...> - 2012-05-28 16:45:59
|
Hi Steve and guys :-)
Am I missing something? When I run sfStart with a hostname that resolves
to IPv6 address then its alright, but when I want to use a specific IPv6
address like this:
[rhusar@vmg ~]$ /tools/opt/smartfrog/smartfrog_debug/bin/sfStart
"2620:52:0:105f:5054:ff:fe84:c43a" "terminate-hook"
"/qa/home/rhusar/hudson-support/hudson-support.sf"
I get:
2012/05/28 12:30:37:132 EDT [ERROR][main] SFCORE_LOG - Error parsing
ACTION_TYPE in:
"terminate-hook":DEPLOY:"/qa/home/rhusar/hudson-support/hudson-support.sf"::2620:52:0:105f:5054:ff:fe84:c43a:(Action
type unknown: 5054) <SmartFrogInitException:: Error parsing ACTION_TYPE
in:
"terminate-hook":DEPLOY:"/qa/home/rhusar/hudson-support/hudson-support.sf"::2620:52:0:105f:5054:ff:fe84:c43a:(Action
type unknown: 5054)
cause: SmartFrogInitException:: Action type unknown: 5054
SmartFrog 3.17.014 (2009-07-28 16:50:31 BST)
SmartFrog 3.17.014 (2009-07-28 16:50:31 BST)>
SmartFrogInitException:: Error parsing ACTION_TYPE in:
"terminate-hook":DEPLOY:"/qa/home/rhusar/hudson-support/hudson-support.sf"::2620:52:0:105f:5054:ff:fe84:c43a:(Action
type unknown: 5054), cause: SmartFrogInitException:: Action type
unknown: 5054, SmartFrog 3.17.014 (2009-07-28 16:50:31 BST),
SmartFrog 3.17.014 (2009-07-28 16:50:31 BST)
at
org.smartfrog.sfcore.common.ConfigurationDescriptor.<init>(ConfigurationDescriptor.java:667)
at org.smartfrog.sfcore.common.OptionSet.<init>(OptionSet.java:168)
at org.smartfrog.SFSystem.execute(SFSystem.java:410)
at org.smartfrog.SFSystem.main(SFSystem.java:379)
Caused by: SmartFrogInitException:: Action type unknown: 5054, SmartFrog
3.17.014 (2009-07-28 16:50:31 BST)
at
org.smartfrog.sfcore.common.ConfigurationDescriptor.setActionType(ConfigurationDescriptor.java:1033)
at
org.smartfrog.sfcore.common.ConfigurationDescriptor.<init>(ConfigurationDescriptor.java:665)
... 3 more
Is this known issue or did I miss something?
PS: We are still using 3.17 :-)
Thanks,
Rado
|
|
From: Guijarro, J. <jul...@hp...> - 2012-05-09 12:19:56
|
Hi Filip, The classloader implementation in the stable release of SF does not allow to unload and reload classes. There is a development branch in SVN where we have integrated OSGi which does (among other things) what you want but it has not been merged into the main branch yet. The mechanism that we have used to reload classes without restarting the daemon is to deploy your components in a sub-daemon (in SF terms a SubProcess). When you want to redeploy your components then you just replace the jars and then restart the subprocess that will load the new classes during start. The thing that you have to be careful with is that the new classes are not referenced in the main (ROOT) daemon so that you do not get API errors. In any case, it is also a good practice to deploy apps/components in subproceses to protect the main daemon from JVM crashes caused by unstable app code. Best regards, Julio Guijarro From: Filip Nguyen [mailto:fn...@re...] Sent: 09 May 2012 09:41 To: sma...@li... Subject: [Smartfrog-users] Dynamic classloading Hi! I have setup dynamic classloading on my nodes but to reaload a class I have to restart the daemon. Is there a way to remedy this? Basically I do not want to restart daemons on every node just because I have modified some components... -- Filip |
|
From: Filip N. <fn...@re...> - 2012-05-09 08:40:40
|
Hi! I have setup dynamic classloading on my nodes but to reaload a class I have to restart the daemon. Is there a way to remedy this? Basically I do not want to restart daemons on every node just because I have modified some components... -- Filip |
|
From: Steve L. <ste...@hp...> - 2011-11-15 10:02:42
|
On 11/11/11 18:21, Nazlie Shahmir wrote: > Hi, > > We are looking for a configuration management tool and I would like to know about your product. Could you please setup a time so we can have a quick chat? > > Thanks, > Nazlie > well, it is open source so you are free to download and play with. If you want to talk more, email me direct and we can discuss a time that suits you and whoever from our group can dial in. We're in the UK, so in GMT time right now |
|
From: Nazlie S. <Naz...@sj...> - 2011-11-11 18:21:57
|
Hi, We are looking for a configuration management tool and I would like to know about your product. Could you please setup a time so we can have a quick chat? Thanks, Nazlie |
|
From: Steve L. <ste...@hp...> - 2011-10-31 15:38:57
|
I'm pleased to announce the release of SmartFrog 3.18.014 The big changes are -asynchronous Jetty startup is now working in the SmartFrog tests and in internal use -the SmartFrog testharness has been reworked to ensure that the failing Jetty test were correctly picked up and other race conditions did not cause deadlocks. We've also upgraded the Groovy distribution to Groovy 1.8.3 As usual, if there are problems, raise them on the mailing list or JIRA. Assuming this release doesn't introduce any major regressions, it will be the last release for 2011. -Steve SmartFrog 3.18.014 ================== This is a new release of SmartFrog, the Java-based, LPGL-licensed distributed deployment framework developed by HP Laboratories. SmartFrog enables applications to be deployed across multiple machines, configuring different aspects of the system so that they are all consistently configured, and managing the life-cycle of the application as a whole. The project's home page is http://smartfrog.org/ The release artifacts are available at https://sourceforge.net/projects/smartfrog/files/development/smartfrog-3.18.014/ Artifacts for use by Ivy and Maven are available under http://smartfrog.sourceforge.net/repository/ This release is 3.18.014; built from revision 8803 of the SVN repository. It was compiled with the Java version set to Java 6 -it will not work on Java1.5 JVMs. This release includes the following items: * The core SmartFrog daemon, including services to manage files, start and stop Java and native programs. * Example components and applications. * Ant support: ant tasks to deploy and terminate applications. * Ant components: the ability to execute ant tasks in a deployment. * Anubis: a partition aware tuple-space that can be used to implement fault tolerant systems. * Database: components to issue database commands, and deploy HSLDB and MySQL databases. * Groovy: the ability to write SmartFrog components using the Groovy language. * JMX: the ability to configure and manage JMX components, and to manage SmartFrog components over JMX. * Logging: integration with Apache commons-logging and Log4J, and the SLF4J framework. * Networking: email, FTP, SSH, DNS support. * Quartz: scheduled operations using Quartz libraries. * RpmTools: components for working with or deploying with RPMs * Scripting: support for BSF-hosted scripting languages * Testing: Distributed JUnit and component testing with SFUnit. * Velocity: generation/transformation of text files during deployment * WWW: deployment of WAR and EAR files to application servers. * Jetty: The Jetty components can configure and deploy individual servlets, eliminating much of the need for WAR files and application servers. * XML: XML support with XOM. * XMPP: Presence and messaging over Jabber. Packaging ========= This release is available as: * RPM files inside a .tar.gz file. * A JAR installer. * The original core smartfrog distribution as .zip and .tar.gz (deprecated). * A .tar.gz file containing everything needed to create a private set of RPM files containing JAR files signed by a private Certification Authority. The RPM installation is for RPM-based Linux systems. The archive contains the following RPM files: smartfrog: The core SmartFrog distribution. smartfrog-daemon: The shell scripts to add the SmartFrog distribution to the path, and to run the daemon on start-up. smartfrog-demo: Example code and documentation. smartfrog-javadocs: Javadocs for the project smartfrog-ant: Ant task and build file execution smartfrog-anubis: Distributed partition-aware tuple space smartfrog-csvfiles: Support for reading/writing CSV Files. smartfrog-database: Database access smartfrog-groovy: Groovy Support smartfrog-jetty: Jetty support smartfrog-jmx: JMX integration though MX4J smartfrog-junit: Junit 3.8.2 test execution smartfrog-logging: Logging through Log4J and commons-logging smartfrog-networking: SSH, SCP, FTP and email smartfrog-quartz: Scheduled operations smartfrog-rpmtools: RPM support tools smartfrog-scripting: Scripted components smartfrog-velocity: Velocity template processing smartfrog-www: Web support: Deployment and liveness pages smartfrog-xml: XML Support smartfrog-xmpp: XMPP/Jabber communications smartfrog-xunit: Distributed testing and reporting All the JAR files are also published to a repository that is compatible with Apache Maven and Ivy. Add http://smartfrog.sourceforge.net/repository/ to your repository list to pull SmartFrog artifacts into your Ivy- or Maven- based build. There are also SmartFrog components to retrieve artifacts from such a repository which can be used for dynamic download of SmartFrog and other artifacts, in /org/smartfrog/services/os/java/library.sf Security warning ================ Unless SmartFrog is configured with security, a running daemon will listen on its configured port for incoming deployment requests, and deploy the applications with the rights of the user running the daemon. When the smartfrog-daemon RPM is installed, that means that a process running as root will be listening on an open port for incoming deployment requests. Do not deploy SmartFrog this way on any untrusted network, not without turning security on. There is a special distribution .tar.gz file that can be used to generate a private set of secure RPM files. Building SmartFrog ================== SmartFrog requires Java 1.6+ and Ant 1.8+ to build. The izpack and source .zip and .tar.gz distributions include a source tree sufficient to build the entire system. To build a later release, please follow the instructions at http://sourceforge.net/svn/?group_id=87384 to check out smartfrog/trunk/core from our repository. This release was built with revision 8803 of the repository, which is available under the SVN branch https://smartfrog.svn.sourceforge.net/svnroot/smartfrog/tags/release3.18.014 We strongly encourage anyone interested in building or extending SmartFrog to get involved in the SmartFrog developer mailing list, which can be found from the sourceforge project page http://sourceforge.net/projects/smartfrog/ Reporting Bugs ============== Please file all bug reports at http://jira.smartfrog.org/ Thank you! The SmartFrog Team http://smartfrog.org/ Changes since last release ========================== ** Bug * [SFOS-1658] - Regression: Xunit AntXMLNestedTestFailing * [SFOS-1659] - Junit testrunner test failing on release VM * [SFOS-1667] - Jetty server not starting up right * [SFOS-1668] - TestCompoundImpl mistakes ForcedShutdown for success * [SFOS-1672] - core/testharness tests failing as ibiblio.org is down * [SFOS-1674] - Jetty tests failing in trunk ** Improvement * [SFOS-1670] - downgrade stack trace warning from warn to log * [SFOS-1675] - WorkerThreadPrimImpl to terminate worker before calling superclass * [SFOS-1677] - move up to groovy 1.8.3 ** New Feature * [SFOS-1673] - add Log4Json to Json package |
|
From: Steve L. <ste...@hp...> - 2011-10-03 09:55:19
|
On 29/09/11 16:28, Steve Loughran wrote: > > I am pleased to announce release 3.18.012 of SmartFrog. One other big change I should mention is > ** Bug > * [SFOS-676] - Jetty component should not block in sfStart/sfDeploy http://jira.smartfrog.org/jira/browse/SFOS-676 Jetty components now start on a separate thread, stopping ping() operations thinking there is a problem when in fact slow-starting servlets are causing it to take a while to come up. While this change is needed, I'm not sure what's gone is complete. -I'm starting to suspect that errors in servlet creation don't propagate up -that's not something I test for yet, so I'll add the test and see what happens. -It may be good to add a switch to say "use blocking startup", though the ping() operation will still be fixed to not worry about slow startup, which was half the problem. If anyone is having problems with Jetty, email the list and I'll have a look. I may well push out a new release at the end of October to deal with any Jetty-related problems, though I need better tests first |
|
From: Steve L. <ste...@hp...> - 2011-09-29 15:28:41
|
I am pleased to announce release 3.18.012 of SmartFrog. The biggest change is the update of the many dependency libraries, and ensuring that everything works with them -get in touch with us if there is any regression. http://jira.smartfrog.org/ is where bugs are filed. One new development is the smartfrog-groovy components. These let you implement SmartFrog components in the groovy language, as well as test your SmartFrog deployments. This is a very nice way to develop and test code, and we are shifting to use Groovy for some of or more recent work, especially the Hadoop components. On the topic of Hadoop, I have been working on those, moving away from in-process management of Hadoop towards one of spawning JVMs configured dynamically. We are doing this with our (unstable) grinstall "Groovy Install" components that are driven by in-filesystem groovy scripts. For Hadoop we take the Apache tar file (currently 0.20.203), untar it, and bring it up with configuration options patched into the various scripts and configuration files. This Hadoop stuff is very unstable and not included in this release. Anyone wishing to explore it will need to check out the source code. -Steve SmartFrog 3.18.012 ================== This is a new release of SmartFrog, the Java-based, LPGL-licensed distributed deployment framework developed by HP Laboratories. SmartFrog enables applications to be deployed across multiple machines, configuring different aspects of the system so that they are all consistently configured, and managing the life-cycle of the application as a whole. The project's home page is http://smartfrog.org/ The release artifacts are available at https://sourceforge.net/projects/smartfrog/files/development/smartfrog-3.18.012/ Artifacts for use by Ivy and Maven are available under http://smartfrog.sourceforge.net/repository/ This release is 3.18.012; built from revision 8753 of the SVN repository. It was compiled with the Java version set to Java 6 -it will not work on Java1.5 JVMs. This release includes the following items: * The core SmartFrog daemon, including services to manage files, start and stop Java and native programs. * Example components and applications. * Ant support: ant tasks to deploy and terminate applications. * Ant components: the ability to execute ant tasks in a deployment. * Anubis: a partition aware tuple-space that can be used to implement fault tolerant systems. * Database: components to issue database commands, and deploy HSLDB and MySQL databases. * Groovy: the ability to write SmartFrog components using the Groovy language. * JMX: the ability to configure and manage JMX components, and to manage SmartFrog components over JMX. * Logging: integration with Apache commons-logging and Log4J, and the SLF4J framework. * Networking: email, FTP, SSH, DNS support. * Quartz: scheduled operations using Quartz libraries. * RpmTools: components for working with or deploying with RPMs * Scripting: support for BSF-hosted scripting languages * Testing: Distributed JUnit and component testing with SFUnit. * Velocity: generation/transformation of text files during deployment * WWW: deployment of WAR and EAR files to application servers. * Jetty: The Jetty components can configure and deploy individual servlets, eliminating much of the need for WAR files and application servers. * XML: XML support with XOM. * XMPP: Presence and messaging over Jabber. Packaging ========= This release is available as: * RPM files inside a .tar.gz file. * A JAR installer. * The original core smartfrog distribution as .zip and .tar.gz * A .tar.gz file containing everything needed to create a private set of RPM files containing JAR files signed by a private Certification Authority. The RPM installation is for RPM-based Linux systems. The archive contains the following RPM files: smartfrog: The core SmartFrog distribution. smartfrog-daemon: The shell scripts to add the SmartFrog distribution to the path, and to run the daemon on start-up. smartfrog-demo: Example code and documentation. smartfrog-javadocs: Javadocs for the project smartfrog-ant: Ant task and build file execution smartfrog-anubis: Distributed partition-aware tuple space smartfrog-csvfiles: Support for reading/writing CSV Files. smartfrog-database: Database access smartfrog-groovy: Groovy Support smartfrog-jetty: Jetty support smartfrog-jmx: JMX integration though MX4J smartfrog-junit: Junit 3.8.2 test execution smartfrog-logging: Logging through Log4J and commons-logging smartfrog-networking: SSH, SCP, FTP and email smartfrog-quartz: Scheduled operations smartfrog-rpmtools: RPM support tools smartfrog-scripting: Scripted components smartfrog-velocity: Velocity template processing smartfrog-www: Web support: Deployment and liveness pages smartfrog-xml: XML Support smartfrog-xmpp: XMPP/Jabber communications smartfrog-xunit: Distributed testing and reporting All the JAR files are also published to a repository that is compatible with Apache Maven and Ivy. Add http://smartfrog.sourceforge.net/repository/ to your repository list to pull SmartFrog artifacts into your Ivy- or Maven- based build. There are also SmartFrog components to retrieve artifacts from such a repository which can be used for dynamic download of SmartFrog and other artifacts, in /org/smartfrog/services/os/java/library.sf Security warning ================ Unless SmartFrog is configured with security, a running daemon will listen on its configured port for incoming deployment requests, and deploy the applications with the rights of the user running the daemon. When the smartfrog-daemon RPM is installed, that means that a process running as root will be listening on an open port for incoming deployment requests. Do not deploy SmartFrog this way on any untrusted network, not without turning security on. There is a special distribution .tar.gz file that can be used to generate a private set of secure RPM files. Building SmartFrog ================== SmartFrog requires Java 1.6+ and Ant 1.8+ to build. The izpack and source .zip and .tar.gz distributions include a source tree sufficient to build the entire system. To build a later release, please follow the instructions at http://sourceforge.net/svn/?group_id=87384 to check out smartfrog/trunk/core from our repository. This release was built with revision 8753 of the repository, which is available under the SVN branch https://smartfrog.svn.sourceforge.net/svnroot/smartfrog/tags/release3.18.012 We strongly encourage anyone interested in building or extending SmartFrog to get involved in the SmartFrog developer mailing list, which can be found from the sourceforge project page http://sourceforge.net/projects/smartfrog/ Reporting Bugs ============== Please file all bug reports at http://jira.smartfrog.org/ Thank you! The SmartFrog Team http://smartfrog.org/ Changes since last release ========================== Release Notes - SmartFrog - Version 3.18.012 ** Bug * [SFOS-205] - Logging services tests are failing * [SFOS-676] - Jetty component should not block in sfStart/sfDeploy * [SFOS-1358] - binding to commons logging appears to not work in sub-processes * [SFOS-1570] - NPE when parsing an SF file outside of an SF daemon * [SFOS-1571] - testrun failing in release build. Dependencies? * [SFOS-1576] - ec2 RPM has a dependency on cloudfarmer RPM that can't be satisfied * [SFOS-1582] - -port option isn't being picked up * [SFOS-1601] - RMI is trying to use IPv6 on Linux * [SFOS-1604] - xunit/junit component tests failing: race conditions? * [SFOS-1613] - <sfrun> not working as expected * [SFOS-1635] - Bug: case insensitive string comparison broken in Assert component * [SFOS-1651] - sfCompleteNameSafe can NPE if there is no process compound (yet?) * [SFOS-1654] - org.smartfrog.services.ant.test.system.AntComplexPropertiesTest failing: no sfhome * [SFOS-1655] - Two TestRunner container tests are failing -but only as part of a larger build- * [SFOS-1660] - TestCompound conditions are evaluated too early * [SFOS-1661] - Restlet tests won't compile (and then are timing out) * [SFOS-1662] - Jetty testWar test failing; startup too long * [SFOS-1663] - grinstall test failing as the remote file being downloaded is gone ** Improvement * [SFOS-1423] - Move Hadoop branch to github, merge in important bugs and then bring components/hadoop up to speed with it * [SFOS-1503] - Move up to Ant 1.8.1 * [SFOS-1561] - Move up to Jetty 6.1.26 * [SFOS-1569] - Move up to JUnit 4.8.2 * [SFOS-1573] - Move SF orch dependencies logic to separate "dependencies" component * [SFOS-1575] - fix formatting in SfComponentDescriptionImpl * [SFOS-1578] - replace uses of *copy* with a constant * [SFOS-1580] - review all code in org.smartfrog.services, clean it up * [SFOS-1581] - Include port number when sfPing fails * [SFOS-1583] - Re-organise Hadoop components * [SFOS-1592] - clean up anubis build files * [SFOS-1593] - Move up to Jetty 6.1.26 * [SFOS-1595] - Review Logging source and docs * [SFOS-1596] - CompoundImpl.sfCreateNewChild can't assume that every Exception has a non-null message * [SFOS-1599] - move up to httpclient 4.1.1 * [SFOS-1600] - include connect time when a test times out connecting to a port * [SFOS-1602] - replace tabs with spaces in the shell scripts * [SFOS-1603] - in logging docs, show how to set log levels on the command line * [SFOS-1609] - make SFGeneralSecurityException part of the SmartFrogException tree * [SFOS-1610] - review logging component code and docs * [SFOS-1611] - clean up SmartFrogLifecycleException source * [SFOS-1616] - Move JarUtil to Java 5 generics * [SFOS-1617] - Review and clean up some of the display code * [SFOS-1618] - Make it possible for Groovy test cases to deploy SmartFrog test runs and work with them * [SFOS-1619] - Make it possible to log files that are #included, so as to detect loops * [SFOS-1626] - stop sfDaemon complaing about duplicate entries in CP when they are the same file * [SFOS-1629] - sf-jetty ivy.xml to drop commons-logging as a dependency of commons-el * [SFOS-1634] - clean up SFSetPropertyImpl * [SFOS-1636] - CompoundImpl to make childCap and childInc static variables final * [SFOS-1637] - make the default sfLivenessFactor and sfLivenessDelay values constants * [SFOS-1647] - review sf-xml source and reformat * [SFOS-1648] - Move to Ant 1.8.2 * [SFOS-1649] - Move to Jackson 1.8.5 * [SFOS-1650] - stop looking for junit.jar when ivy.enabled is not set * [SFOS-1652] - "Try" workflow component to ignore situations where there isn't a child of the specific action to deploy * [SFOS-1653] - Add new deployment operation DEPLOY_WAIT for sfRun.sh to wait for changes ** New Feature * [SFOS-1542] - add rmdir component to delete a directory or files on deployment * [SFOS-1598] - Create grinstall Groovy Installer component * [SFOS-1642] - allow Spinner operation field to be set dynamically ** Task * [SFOS-1612] - move testharness/testcases to testharness/test ** Sub-task * [SFOS-1584] - hadoop refactor: move all the components under the hadoop-components tree * [SFOS-1585] - move hadoop-lifecycle work into its own component, and stop it building * [SFOS-1587] - change release build to include the new hadoop component * [SFOS-1588] - move up to Hadoop 0.21 * [SFOS-1589] - Add Hadoop 0.21 artifacts to the repository * [SFOS-1621] - move grinstall slow operations (download, lifecycle phases) to an async thread * [SFOS-1622] - Groovy Component to add ping task * [SFOS-1623] - Groovy Component to add terminate task * [SFOS-1628] - move log4j-less hadoop-core JAR to a new version to avoid clashes with m2 repo version * [SFOS-1632] - move the HDFS tasks from h-lifecycle to h-ops * [SFOS-1633] - add sf component to bring up MiniDFS cluster |
|
From: Steve L. <ste...@hp...> - 2011-08-31 11:10:23
|
On 23/08/11 16:35, Radoslav Husar wrote: > Hi guys, > > is there any documentation (or examples) for the sf-xml components? I > haven't found anything helpful :-/ > > http://www.smartfrog.org/wiki/display/sf/sf-xml > -Sorry for not replying; I've been on vacation and the others on the team don't seem to be replying either. Sorry. No, there's not much there, is there? I use it primarily as a way of distributing versions of the main XML libraries for other components: xmlapis+ xerces, xalan, jdom, xom The SF components inside were stuff I wrote to work with Xom and generate XML Content. There is a test example of it #include "org/smartfrog/services/xml/components.sf" /** * test a document */ rootDoc extends XmlDocument { root extends XmlElement { textElement ROOT:textElement; } } textElement extends XmlTextNode { text "this is a nested text element"; } sfConfig extends rootDoc ; This isn't that useful. Looking in the code there is a set of attributes which support XML-namespaced qnames, and after building up a tree of them can be saved to an XML file, or, by the look of things, sent over the wire. I don't see anything there to load an XML document, though it looks the kind of thing that I'd do next. The last big stuff I did with XML in SF was working with the "Alpine" SOAP stack, but even that was using Xom, rather than XML-in-SF; I think it depended on sf-xml just for the dependencies and maybe some helper methods. XML should match fairly easily to the SF language, but in practise it doesn't for some reasons you will soon recognise if you spend too much time in XML-land -XML namespaces and the notion of a qualified name on elements and attributes. -the difference between nested elements and simple attributes -the way you can have multiple text elements directly under a node with nested elements in between them. JSON is a far more compatible format, and where we've been drifting to in our use of things recently. If you really want to work with the sf-xml stuff then you can talk to me and we'll see how to improve things - I do think Xom is the best way to work with XML in Java, whereas the DOM APIs are probably the worst. That said, now we've been doing a fair bit of Groovy work that would be even better as I'd be able to inject new methods into every XML node without having to worry about which XML node factory it came from. -steve |
|
From: Radoslav H. <rh...@re...> - 2011-08-23 15:35:18
|
Hi guys, is there any documentation (or examples) for the sf-xml components? I haven't found anything helpful :-/ http://www.smartfrog.org/wiki/display/sf/sf-xml Cheers, Radoslav Husar JBoss QE Czech Republic |
|
From: <dep...@al...> - 2011-08-11 14:03:56
|
Found a solution: set the port number to something large, e.g. 38000 instead of the default 3800. It seems that the firewall blocks ports with low values for some reason (the exact value doesn't matter), but large values are OK. From: dep...@al... [mailto:dep...@al...] Sent: Tuesday, August 09, 2011 5:42 PM To: sma...@li... Cc: Peter Gagarinov; Fiodar Kupchyk (by) Subject: Re: [Smartfrog-users] "Port already in use" exception when starting SmartFrog Further development Re: "java.net.BindException: Address already in use" exception when trying to launch SmartFrog on some Windows Server and Windows 7 machines. The culprit turned out to be the firewall. The daemon can only run when firewall is disabled. We have Microsoft ISA Server firewall on our corporate network. Is there some workaround for this? Quote from our sysadmin: apparently [SmartFrog] wasn't designed with corporate environment in mind... Dmitry Epstein | Developer Allied Testing www.alliedtesting.com<http://www.alliedtesting.com/> We Deliver Quality. From: Dmitry Epstein Sent: Thursday, November 18, 2010 1:45 PM To: sma...@li... Cc: Fiodar Kupchyk (by); Peter Gagarinov Subject: "Port already in use" exception when starting SmartFrog Hi, We are having a problem starting SmartFrog under some accounts. Here is the output that we get when running sfDaemon from Windows command line: ================================================================================== D:\tmp\Externals\Java\smartfrog\bin>sfDaemon SmartFrog 3.18.002 (2010-09-20 04:13:24 EDT) (C) Copyright 1998-2010 Hewlett-Packard Development Company, LP 2010/11/18 12:13:14:859 EET [WARN ][main] SFCORE_LOG - SmartFrog security is NOT active 2010/11/18 12:13:14:866 EET [DEBUG][main] SFCORE_LOG - Security Manager is java. lang.SecurityManager@1a73d3c<mailto:lang.SecurityManager@1a73d3c> 2010/11/18 12:13:14:868 EET [DEBUG][main] SFCORE_LOG - Using java security polic y: =D:\tmp\Externals\Java\smartfrog\private\sf.no.security.policy 2010/11/18 12:13:14:878 EET [WARN ][main] SFCORE_LOG - Possible problem with cla sspath: 3 occurrences for smartfrog- D:\tmp\Externals\Java\smartfrog\lib\smartfrog-src-3.18.002.jar D:\tmp\Externals\Java\smartfrog\lib\smartfrog-jdocs-3.18.002.jar D:\tmp\Externals\Java\smartfrog\lib\smartfrog-3.18.002.jar 2010/11/18 12:13:14:895 EET [DEBUG][main] SFCORE_LOG - Network test localhost: h ostname 'BY0013D4B30637.alliedtesting.com', ip '192.168.198.99', [Successful], 1ms 2010/11/18 12:13:14:902 EET [DEBUG][main] SFCORE_LOG - Command Line args: [] SmartFrogDeploymentException: unnamed component. SmartFrogRuntimeException:: Sma rtFrog daemon could not start because another instance is running, cause: java.r mi.server.ExportException: Port already in use: 3800; nested exception is: java.net.BindException: Address already in use: JVM_Bind, SmartFrog 3.18 .002 (2010-09-20 04:13:24 EDT), cause: SmartFrogRuntimeException:: SmartFrog dae mon could not start because another instance is running, cause: java.rmi.serv er.ExportException: Port already in use: 3800; nested exception is: java.net.BindException: Address already in use: JVM_Bind, SmartFrog 3 .18.002 (2010-09-20 04:13:24 EDT) 2010/11/18 12:13:16:263 EET [DEBUG][main] SFCORE_LOG - SmartFrog System.Exit cod e: 1, v3.18.002 D:\tmp\Externals\Java\smartfrog\bin> ================================================================================== We get the same exception when launching SmartFrog using the test harness. We have checked the port and found that it is not in use at any point and that no SmartFrog daemon instances are running in the background. The most remarkable thing is that in multi-user environments the problem occurs only with certain accounts. When SmartFrog is launched on the same machine from the same location by a different user, we don't see this exception. What is also puzzling is that the problem emerged suddenly and for no apparent reason: we are not aware of any changes to the system that could have occasioned this error. This happens with SmartFrog v. 3.18.002 running on at least three different machines under Windows 7 and Windows Server 2008 R2 Standard with Java SE v. 1.6 runtime environment. The problem account has administrative privileges. Any help would be appreciated. Dmitry |
|
From: <dep...@al...> - 2011-08-09 13:54:54
|
Further development Re: "java.net.BindException: Address already in use" exception when trying to launch SmartFrog on some Windows Server and Windows 7 machines. The culprit turned out to be the firewall. The daemon can only run when firewall is disabled. We have Microsoft ISA Server firewall on our corporate network. Is there some workaround for this? Quote from our sysadmin: apparently [SmartFrog] wasn't designed with corporate environment in mind... Dmitry Epstein | Developer Allied Testing www.alliedtesting.com<http://www.alliedtesting.com/> We Deliver Quality. From: Dmitry Epstein Sent: Thursday, November 18, 2010 1:45 PM To: sma...@li... Cc: Fiodar Kupchyk (by); Peter Gagarinov Subject: "Port already in use" exception when starting SmartFrog Hi, We are having a problem starting SmartFrog under some accounts. Here is the output that we get when running sfDaemon from Windows command line: ================================================================================== D:\tmp\Externals\Java\smartfrog\bin>sfDaemon SmartFrog 3.18.002 (2010-09-20 04:13:24 EDT) (C) Copyright 1998-2010 Hewlett-Packard Development Company, LP 2010/11/18 12:13:14:859 EET [WARN ][main] SFCORE_LOG - SmartFrog security is NOT active 2010/11/18 12:13:14:866 EET [DEBUG][main] SFCORE_LOG - Security Manager is java. lang.SecurityManager@1a73d3c<mailto:lang.SecurityManager@1a73d3c> 2010/11/18 12:13:14:868 EET [DEBUG][main] SFCORE_LOG - Using java security polic y: =D:\tmp\Externals\Java\smartfrog\private\sf.no.security.policy 2010/11/18 12:13:14:878 EET [WARN ][main] SFCORE_LOG - Possible problem with cla sspath: 3 occurrences for smartfrog- D:\tmp\Externals\Java\smartfrog\lib\smartfrog-src-3.18.002.jar D:\tmp\Externals\Java\smartfrog\lib\smartfrog-jdocs-3.18.002.jar D:\tmp\Externals\Java\smartfrog\lib\smartfrog-3.18.002.jar 2010/11/18 12:13:14:895 EET [DEBUG][main] SFCORE_LOG - Network test localhost: h ostname 'BY0013D4B30637.alliedtesting.com', ip '192.168.198.99', [Successful], 1ms 2010/11/18 12:13:14:902 EET [DEBUG][main] SFCORE_LOG - Command Line args: [] SmartFrogDeploymentException: unnamed component. SmartFrogRuntimeException:: Sma rtFrog daemon could not start because another instance is running, cause: java.r mi.server.ExportException: Port already in use: 3800; nested exception is: java.net.BindException: Address already in use: JVM_Bind, SmartFrog 3.18 .002 (2010-09-20 04:13:24 EDT), cause: SmartFrogRuntimeException:: SmartFrog dae mon could not start because another instance is running, cause: java.rmi.serv er.ExportException: Port already in use: 3800; nested exception is: java.net.BindException: Address already in use: JVM_Bind, SmartFrog 3 .18.002 (2010-09-20 04:13:24 EDT) 2010/11/18 12:13:16:263 EET [DEBUG][main] SFCORE_LOG - SmartFrog System.Exit cod e: 1, v3.18.002 D:\tmp\Externals\Java\smartfrog\bin> ================================================================================== We get the same exception when launching SmartFrog using the test harness. We have checked the port and found that it is not in use at any point and that no SmartFrog daemon instances are running in the background. The most remarkable thing is that in multi-user environments the problem occurs only with certain accounts. When SmartFrog is launched on the same machine from the same location by a different user, we don't see this exception. What is also puzzling is that the problem emerged suddenly and for no apparent reason: we are not aware of any changes to the system that could have occasioned this error. This happens with SmartFrog v. 3.18.002 running on at least three different machines under Windows 7 and Windows Server 2008 R2 Standard with Java SE v. 1.6 runtime environment. The problem account has administrative privileges. Any help would be appreciated. Dmitry |
|
From: Fill, N. <Nat...@lg...> - 2011-07-29 11:52:04
|
Hello, I am new user of SmartFrog. So far I managed to install version 3.18.010_all and run some examples. What I really need SmartFrog for is to control JBoss 5.1 deployments. The things I am looking for is to: - Start and stop JBoss servers on various hosts - Deploy and undeploy .ear, .jar, .war files So far I found this link: http://www.mail-archive.com/sma...@li.../msg000 77.html It didn't work for me because distribution of SF that I have got from SourceForge doesn't come with "www" libraries. The following that the script requires are missing from SF distribution: #include "/org/smartfrog/services/www/dbc/components.sf" #include "/org/smartfrog/services/www/webapplication.sf" #include "/org/smartfrog/services/www/livenessPage.sf" Is there any examples of how to get SF configured for JBoss 5.1? If 'www' libraries are needed, where do I get these from? The next question is about SmartFrog and integration with Maven and Hundson. Any help in this direction would be greatly appreciated. I guess the best development tool for SF scripts would be Eclipse. Are there any libraries that I can use to integrate with Eclipse IDE? Kind Regards Natalia This e-mail (and any attachments) may contain privileged and/or confidential information. If you are not the intended recipient please do not disclose, copy, distribute, disseminate or take any action in reliance on it. If you have received this message in error please reply and tell us and then delete it. Should you wish to communicate with us by e-mail we cannot guarantee the security of any data outside our own computer systems. Any information contained in this message may be subject to applicable terms and conditions and must not be construed as giving investment advice within or outside the United Kingdom. Telephone Conversations may be recorded for your protection and to ensure quality of service Legal & General Investment Management Limited (no 2091894), Legal & General Assurance (Pensions Management) Limited (no 1006112), LGV Capital Limited (no 2091268), Legal & General Property Partners (Operator) Limited (no 5522016) and LGIM Corporate Director Limited (no 7105051) are authorised and regulated by the Financial Services Authority. All are registered in England & Wales with a registered office at One Coleman Street, London, EC2R 5AA. Legal & General Property Limited (no 2091897) is authorised and regulated by the Financial Services Authority for insurance mediation activities. It is registered in England & Wales with a registered office at One Coleman Street, London, EC2R 5AA. Legal & General Group PLC, Registered Office One Coleman Street, London, EC2R 5AA. Registered in England no: 1417162 ________________________________________________________________________ **** This email has come from the internet and has been scanned for all viruses and potentially offensive content by Messagelabs on behalf of Legal & General **** |
|
From: Steve L. <ste...@hp...> - 2011-06-27 14:23:45
|
On 21/06/11 01:16, Lavoie, John L wrote: > I found this message in the archives: > > http://sourceforge.net/mailarchive/message.php?msg_id=26211662 > > Has there been any update on it? What about a workaround? Here's a quick update of where we are on this -all problems with spaces in the ant command line (and in the .sf files #includes) have -we believe- been fixed. You can check out the code and try it to see if this is the case -the finishing of the sf-run work is still outstanding; it'll have to wait until Julio comes back from his vacation. Assuming the problem is easy to fix, that would put the release date for a new version of SmartFrog to the week of July 5. There's been some big changes to test running framework recently, to deal with some race conditions, so if anyone is using the TestBlock/TestCompound/xunit code and/or explicitly running deployments from Junit, they are strongly encouraged to check out before the release and make sure that nothing has broken with this: http://jira.smartfrog.org/jira/browse/SFOS-1604 the key change is that unless you set runTests true in these components, the tests will only run if a new method in the TestBlock interface is called to trigger the test run, rather than have them start automatically. This works around a race condition in which the test target would complete its lifecycle before the junit test runner had a chance to bind to it. -Steve |
|
From: Lavoie, J. L <joh...@op...> - 2011-06-21 00:16:18
|
I found this message in the archives: http://sourceforge.net/mailarchive/message.php?msg_id=26211662 Has there been any update on it? What about a workaround? I have a script that is behaving correctly if I call sfrun on the command line. But when I attempt to automate this into my build through ant, it is exiting after the first component completes (the "drop" below). Also, there seems to be a bug where sf-run cannot handle a space in the path to the .sf file. I need to move my .sf file to a temp directory that does not have spaces in order to get it to run through ant. My deployment script contains: #include "org/smartfrog/sfcore/workflow/components.sf" DB_Stuff extends Sequence { drop extends genericSQLCommand { <stuff> } attach extends genericSQLCommand { <stuff> } } sfConfig extends Compound { myDBStuff extends DB_Stuff; } And I am calling sf-run with: <property name="smartfrog.dir" value="${SMARTFROG_HOME}"/> <property name="smartfrog-tasks-jar" value="${smartfrog.dir}/lib/sf-tasks-3.18.010.jar"/> <property name="smartfrog-jar" value="${smartfrog.dir}/lib/smartfrog-3.18.010.jar"/> <property name="security.manager" value="none"/> <taskdef resource="org/smartfrog/tools/ant/tasks.properties"> <classpath> <pathelement location="${smartfrog-tasks-jar}"/> <pathelement location="${smartfrog-jar}"/> </classpath> </taskdef> <target name="Deploy"> <jar destfile="${env.WORKSPACE}\SmartFrogProject/optum-sf.jar" basedir="${env.WORKSPACE}\SmartFrogProject\src"/> <copy file="attach.sf" tofile="C:\temp\attach.sf"/> <path id="smartfrog.classpath"> <fileset dir="${SMARTFROG_HOME}/lib"> <include name="**/*.jar" /> </fileset> <fileset dir="${env.WORKSPACE}\SmartFrogProject\"> <include name="**/*.jar"/> </fileset> </path> <sf-run securityManager="${security.manager}" classpathref="smartfrog.classpath" failonerror="true"> <application name="attachdb" file='C:\temp\attach.sf' /> </sf-run> </target> John Lavoie This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. |
|
From: Steve L. <ste...@hp...> - 2011-05-27 09:45:11
|
On 05/26/2011 10:39 PM, Boivin, Peter wrote: > I may be missing somethng, so I hope someone can assist me. I looked > through the documentation on starting and stopping a daemon. I see how > I can stop a daemon remotely (sfStopDaemon<REMOTEHOST>). How do you > start a daemon remotely? I have started my daemon by logging into the > system and starting it locally on linux we just install the daemon RPM, which sets up the init.d scripts to start and stop SF automatically. > Sometimes it gets in a bad state. When > I am running smartfrog from another server, I would like to be able to > stop and restart the remote daemon to get it into a good state. I have > not seen yet how to do that. We don't have an explicit "log in and start SF" process, because there isn't a daemon there -it's a bit of a vicious cycle. We have hit a similar problem bringing up hosted VMs where the VM boot process actually installs the SF daemon from the RPMS, and starts it, and the remote code needs to block for that to happen, then deploy something. The way this is sone is in the code NodeDeploymentOverSSH - spin until the hostname resolves - spin until port 22 is open - spin until `which sfStart` works - spin until sfStart works the code: http://smartfrog.svn.sourceforge.net/viewvc/smartfrog/trunk/core/components/cloudfarmer/src/org/smartfrog/services/cloudfarmer/server/deployment/NodeDeploymentOverSSH.java?revision=8466&view=markup The nice thing about this is that you don't open any of the ports other than port 22 and whatever application you want to run; nobody can deploy remotely to your daemon. It also works over long-haul networks and handles delays in VM deployment reasonably well, depending on the timeout options. But in the world of VMs, the way to react to any problem in the VM, including sfDaemons not responding, is kill the VM and create a new one. Harsh but predictable. If you are having problems with the sfDaemon getting into a bad state 1. if it's our code, file bugreps: http://jira.smartfrog.org/jira/secure/Dashboard.jspa on linux, a kill -QUIT will get a stack trace of everything to paste in. 2. try starting all your applications in child processes, by setting the sfProcessName attribute of the component you are deploying: appserver extends AppServer { sfProcessName "AppServerSubProc"; }; Once you that the component and its children will get deployed into a new SF process (unless they change their process name) -the processes ping each other for health; if the child doesn't get pinged by its parent, eventually it times out and undeploys its components then terminates -the parent process can detect failure of a child, and depending on the policy of the parent process, choose how to react. There are various parent components in org.smartfrog.sfcore.workflow.combinators that handle failures differently (retry, don't care, etc). -Sometimes (Jetty Startup related), I've turned down the ping frequency: sfLivenessFactor 500; The process name you choose becomes an attribute of the root daemon, so don't give it the same name as anything else you deploy, life gets confusuing. You can deploy different trees of components into the same subprocess, just use the same name. -Steve |
|
From: Boivin, P. <pet...@in...> - 2011-05-26 21:39:41
|
I may be missing somethng, so I hope someone can assist me. I looked through the documentation on starting and stopping a daemon. I see how I can stop a daemon remotely (sfStopDaemon <REMOTEHOST>). How do you start a daemon remotely? I have started my daemon by logging into the system and starting it locally. Sometimes it gets in a bad state. When I am running smartfrog from another server, I would like to be able to stop and restart the remote daemon to get it into a good state. I have not seen yet how to do that. sfDaemon.bat and sfStart have not been successful for me yet. Peter Boivin Senior Java Developer Ingenix 950 Winter Street Waltham, MA 02451-1405 Email: pet...@in... Phone: (781) 419-8643 www.ingenix.com <http://www.ingenix.com/> This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. |
|
From: Steve L. <ste...@hp...> - 2011-05-23 14:40:15
|
One more thing, here is the template I use to define the sf daemon we
run for our tests
<sf-startdaemon
classpathref="tests.run.classpath"
logStackTraces="true"
spawn="true"
securityManager="${security.manager}"
dir="${build.test.dir}"
timeout="0"
serverHostname="${deploy.server.hostname}"
>
<!-- assertions are enabled -->
<assertions refid="sf.assertions"/>
<jvmarg line="${daemon.jvmargs}"/>
<!-- load in a property file if it is present -->
<propertyfile file="${runtime.properties}" optional="true"/>
<!--copy all proxy settings from the running JVM-->
<syspropertyset refid="proxy.settings"/>
<syspropertyset>
<!--copy all properties beginning with test. or run.-->
<propertyref prefix="test."/>
<propertyref prefix="run."/>
<!--SF core options-->
<propertyref prefix="org.smartfrog.sfcore."/>
<!-- RMI options-->
<propertyref prefix="java.rmi."/>
<!-- Log settings for various tools-->
<propertyref prefix="org.mortbay.log."/>
<propertyref prefix="log4j."/>
<propertyref prefix="org.apache.commons.logging."/>
</syspropertyset>
</sf-startdaemon>
With some predefined properties
<property name="security.manager" value="none"/>
<property name="daemon.jvmargs" value=""/>
<!-- set to 127.0.0.1 for local only deployments -->
<property name="deploy.server.hostname" value="127.0.0.1"/
the 127.0.0.1 url means the service only serves loopback addresses,
which is less troublesome when developing on roaming laptops.
|
|
From: Steve L. <ste...@hp...> - 2011-05-23 13:50:36
|
On 17/05/11 11:37, Boivin, Peter wrote:
> Could someone either show me how my code is failing or give me a simple
> ant file that will start a sf-startdaemon and do a sf-deploy? My code
> and error message is below.
>
> <project>
> <property environment="env"/>
> <property name="base" value="${env.SFHOME}"/>
>
> <property name="smartfrog.dir" value="${base}"/>
> <property name="smartfrog-tasks-jar"
> value="${smartfrog.dir}/lib/sf-tasks-3.18.010.jar"/>
>
> <taskdef resource="org/smartfrog/tools/ant/tasks.properties">
> <classpath>
> <pathelement location="${smartfrog-tasks-jar}"/>
> </classpath>
> </taskdef>
>
> <target name="run-test">
> <sf-functionaltest shutdowntime="10" testtimeout="600">
>
> <application>
> <sf-startdaemon />
> </application>
> <probe>
> <socket port="3800" server="localhost"/>
> </probe>
> <teardown>
> <sf-stopdaemon failonerror="false"/>
> </teardown>
> <test>
> <sf-deploy>
> <application name="Counter"
> descriptor="/org/smartfrog/examples/counter/example.sf" />
> </sf-deploy>
> </test>
> </sf-functionaltest>
> </target>
>
> </project>
>
>
> run-test:
> [sf-startdaemon] Error occurred during initialization of VM
> [sf-startdaemon] java.lang.InternalError: Could not create
> SecurityManager: org.smartfrog.sfcore.security.ExitTrappingSecurityMana
> ger
> [sf-startdaemon] at sun.misc.Launcher.<init>(Launcher.java:90)
> [sf-deploy] Error occurred during initialization of VM
> [sf-deploy] java.lang.InternalError: Could not create SecurityManager:
> org.smartfrog.sfcore.security.ExitTrappingSecurityManager
> [sf-startdaemon] at sun.misc.Launcher.<clinit>(Launcher.java:43)
> [sf-startdaemon] at
> java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1338)
> [sf-deploy] at sun.misc.Launcher.<init>(Launcher.java:90)
> [sf-startdaemon] at
> java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1320)
> [sf-startdaemon]
> [sf-deploy] at sun.misc.Launcher.<clinit>(Launcher.java:43)
> [sf-deploy] at
> java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1338)
> [sf-deploy] at
> java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1320)
> [sf-deploy]
> [sf-stopdaemon] Error occurred during initialization of VM
> [sf-stopdaemon] java.lang.InternalError: Could not create
> SecurityManager: org.smartfrog.sfcore.security.ExitTrappingSecurityManag
> er
> [sf-stopdaemon] at sun.misc.Launcher.<init>(Launcher.java:90)
> [sf-stopdaemon] at sun.misc.Launcher.<clinit>(Launcher.java:43)
> [sf-stopdaemon] at
> java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1338)
> [sf-stopdaemon] at
> java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1320)
> [sf-stopdaemon]
> [sf-functionaltest] Application
> Exception:C:\iCollaborate\SmartFrogProject\build.xml:25: Failed to start
> the smartfrog daemon
That's interesting. We're trying to install a security manager that
exists to stop random bits of code calling System.exit() when they feel
like -these get turned into Throwables that get passed up.
http://jira.smartfrog.org/jira/browse/SFOS-1137
http://jira.smartfrog.org/jira/browse/SFOS-1168
it's something that can be tweaked in the shell scripts as an
environment variable, though that wont' change ant.
http://jira.smartfrog.org/jira/browse/SFOS-1187
I think what is possibly happening is that the classpath only contains
the ant tasks jar, and not smartfrog.jar, so the security manager isn't
there. The sfDaemon task sets up the command line to fork a new JVM,
with the security manager, and that happens so early in the boot process
that it's the first sign of failure.
1. Can you do an ant -v of the run, and tell me what you see?
I've created a new JIRA issue, though it's so low-level in the JVM I
don't see any easy way to handle it
http://jira.smartfrog.org/jira/browse/SFOS-1594
What might be good would be if the sfDaemon doesn't start, the code at
the bottom of the run doesn't just say "Failed to start...", it includes
the command line and classpath. That way problems would be easier to
track down.
-Steve
|
|
From: Boivin, P. <pet...@in...> - 2011-05-17 10:37:24
|
Could someone either show me how my code is failing or give me a simple
ant file that will start a sf-startdaemon and do a sf-deploy? My code
and error message is below.
<project>
<property environment="env"/>
<property name="base" value="${env.SFHOME}"/>
<property name="smartfrog.dir" value="${base}"/>
<property name="smartfrog-tasks-jar"
value="${smartfrog.dir}/lib/sf-tasks-3.18.010.jar"/>
<taskdef resource="org/smartfrog/tools/ant/tasks.properties">
<classpath>
<pathelement location="${smartfrog-tasks-jar}"/>
</classpath>
</taskdef>
<target name="run-test">
<sf-functionaltest shutdowntime="10" testtimeout="600">
<application>
<sf-startdaemon />
</application>
<probe>
<socket port="3800" server="localhost"/>
</probe>
<teardown>
<sf-stopdaemon failonerror="false"/>
</teardown>
<test>
<sf-deploy >
<application name="Counter"
descriptor="/org/smartfrog/examples/counter/example.sf" />
</sf-deploy>
</test>
</sf-functionaltest>
</target>
</project>
run-test:
[sf-startdaemon] Error occurred during initialization of VM
[sf-startdaemon] java.lang.InternalError: Could not create
SecurityManager: org.smartfrog.sfcore.security.ExitTrappingSecurityMana
ger
[sf-startdaemon] at sun.misc.Launcher.<init>(Launcher.java:90)
[sf-deploy] Error occurred during initialization of VM
[sf-deploy] java.lang.InternalError: Could not create SecurityManager:
org.smartfrog.sfcore.security.ExitTrappingSecurityManager
[sf-startdaemon] at sun.misc.Launcher.<clinit>(Launcher.java:43)
[sf-startdaemon] at
java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1338)
[sf-deploy] at sun.misc.Launcher.<init>(Launcher.java:90)
[sf-startdaemon] at
java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1320)
[sf-startdaemon]
[sf-deploy] at sun.misc.Launcher.<clinit>(Launcher.java:43)
[sf-deploy] at
java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1338)
[sf-deploy] at
java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1320)
[sf-deploy]
[sf-stopdaemon] Error occurred during initialization of VM
[sf-stopdaemon] java.lang.InternalError: Could not create
SecurityManager: org.smartfrog.sfcore.security.ExitTrappingSecurityManag
er
[sf-stopdaemon] at sun.misc.Launcher.<init>(Launcher.java:90)
[sf-stopdaemon] at sun.misc.Launcher.<clinit>(Launcher.java:43)
[sf-stopdaemon] at
java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1338)
[sf-stopdaemon] at
java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1320)
[sf-stopdaemon]
[sf-functionaltest] Application
Exception:C:\iCollaborate\SmartFrogProject\build.xml:25: Failed to start
the smartfrog daemon
Peter Boivin
Senior Java Developer
Ingenix
950 Winter Street
Waltham, MA 02451-1405
Email: pet...@in...
Phone: (781) 419-8643
www.ingenix.com <http://www.ingenix.com/>
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
|
|
From: Boivin, P. <pet...@in...> - 2011-05-12 15:34:35
|
I am having problems downloading a zip file through a system that has
proxy settings. My general code is below. Could someone suggest how I
might fix this issue?
#include "org/smartfrog/services/os/download/components.sf"
sfConfig extends Compound {
download extends Downloader {
url
"https://<dowmain_address>.uhc.com/jenkins/job/Impact%20Collaborate%20Da
tabase/lastSuccessfulBuild/artifact/ImpactCollaborate_mdf.zip
<https://<dowmain_address>.uhc.com/jenkins/job/Impact%20Collaborate%20Da
tabase/lastSuccessfulBuild/artifact/ImpactCollaborate_mdf.zip> ";
toLocalFile "C:/SRC/svn/iCollaborate 1.x/tmp";
}
}
Peter Boivin
Senior Java Developer
Ingenix
950 Winter Street
Waltham, MA 02451-1405
Email: pet...@in...
Phone: (781) 419-8643
www.ingenix.com <http://www.ingenix.com/>
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
|
|
From: Steve L. <ste...@hp...> - 2011-05-05 16:11:22
|
We've discovered a regression in SF in the 3.18.010 release, namely you can't specify which port to ping or deploy to via the -p or -port option on the command line http://jira.smartfrog.org/jira/browse/SFOS-1582 You can do it by editing default.ini and changing the port there. I'm not sure if this is enough to merit pushing out a new release -there haven't been that many tangible changes, the only two that are likely to matter being http://jira.smartfrog.org/jira/browse/SFOS-1570: NPE when parsing an SF file outside of an SF daemon and http://jira.smartfrog.org/jira/browse/SFOS-1542 : add rmdir component to delete a directory or files on deployment I'll plan for a may/june release; I want to move the Hadoop code around (split the stuff that needs a modified hadoop version off from the stuff that can work with apache distributions of hadoop. ) |
