Re: [Resin-interest] 4.0.24 configuration notes
I hope so. Since it's new, this is a great time for feedback For the first time, Resin 4.0.24 doesn't work out of the box when added to Eclipse as a new server. I go through this process pain free for each new release, but now immediately see the message 'default' is an unknown server in the configuration file and the server doesn't start. To recreate, use Servers | New | Server | Resin 4.0 | (Create runtime specifying the new Resin home) | Next | Finish (add apps as necessary) | try to start the server. In fact the 4.0.23 server is still present which I'm sticking with for now. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] 4.0.24 configuration notes
I hope so. Since it's new, this is a great time for feedback For the first time, Resin 4.0.24 doesn't work out of the box when added to Eclipse as a new server. I go through this process pain free for each new release, but now immediately see the message 'default' is an unknown server in the configuration file and the server doesn't start. To recreate, use Servers | New | Server | Resin 4.0 | (Create runtime specifying the new Resin home) | Next | Finish (add apps as necessary) | try to start the server. In fact the 4.0.23 server is still present which I'm sticking with for now. I had a similar issue with 4.0.23 (though it was my fault), and by switching out: -conf ${resin.configuration.file} with: -conf /path/to/resin.xml it went away. I have always set that explicitly though and have never tried to figure out how ${resin.configuration.file} gets set. Not sure that helps much, but thought I would throw it out there as something to try. Aaron ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] 4.0.24 configuration notes
On 22-Nov-2011 09:43, Aaron Freeman wrote: I hope so. Since it's new, this is a great time for feedback For the first time, Resin 4.0.24 doesn't work out of the box when added to Eclipse as a new server. I go through this process pain free for each new release, but now immediately see the message 'default' is an unknown server in the configuration file and the server doesn't start. To recreate, use Servers | New | Server | Resin 4.0 | (Create runtime specifying the new Resin home) | Next | Finish (add apps as necessary) | try to start the server. In fact the 4.0.23 server is still present which I'm sticking with for now. I had a similar issue with 4.0.23 (though it was my fault), and by switching out: -conf ${resin.configuration.file} with: -conf /path/to/resin.xml it went away. I have always set that explicitly though and have never tried to figure out how ${resin.configuration.file} gets set. Not sure that helps much, but thought I would throw it out there as something to try. Thanks. Still not right - the path was fully qualified anyway - but on a hunch I copied the 4 files from the 4.0.23-config (admin-users.xml, app-default.xml, resin.xml and health.xml) over the new ones and resin started. Theres something wrong in the newly generated config files themselves. I notice health.xml doesn't appear in the new set. Aaron ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] 4.0.24 configuration notes
On 11/22/2011 02:57 AM, Stargazer wrote: On 22-Nov-2011 09:43, Aaron Freeman wrote: I hope so. Since it's new, this is a great time for feedback For the first time, Resin 4.0.24 doesn't work out of the box when added to Eclipse as a new server. I go through this process pain free for each new release, but now immediately see the message 'default' is an unknown server in the configuration file and the server doesn't start. To recreate, use Servers | New | Server | Resin 4.0 | (Create runtime specifying the new Resin home) | Next | Finish (add apps as necessary) | try to start the server. In fact the 4.0.23 server is still present which I'm sticking with for now. I had a similar issue with 4.0.23 (though it was my fault), and by switching out: -conf ${resin.configuration.file} with: -conf /path/to/resin.xml it went away. I have always set that explicitly though and have never tried to figure out how ${resin.configuration.file} gets set. Not sure that helps much, but thought I would throw it out there as something to try. Thanks. Still not right - the path was fully qualified anyway - but on a hunch I copied the 4 files from the 4.0.23-config (admin-users.xml, app-default.xml, resin.xml and health.xml) over the new ones and resin started. Theres something wrong in the newly generated config files themselves. I notice health.xml doesn't appear in the new set. You can also just add a server id= .../ to the resin.xml. This is an issue we're working on. The health.xml has been moved to local.d in the distribution. -- Scott Aaron ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] 4.0.24 configuration notes
As part of our work on simplifying the Resin configuration to make dynamic/cloud servers easier to deploy, 4.0.24 now has rpm support two new configuration tags resin:properties and server-multi a new EL function rvar() two new CLI commands start-all and generate-password and a new command-line script resinctl all to help make the cluster/cloud deployment easier (and also help simplify /resin-admin setup). Our goal is to make a new dynamic server require very little in specific configuration to attach to the triad and start working. If the small specific configuration can fit in an Amazon-style user-data, that would be perfect (we're not quite there yet, but 4.0.24 is a good step forward.) The start-all is used in the updated /etc/init.d/resin to start all servers that are configured on the local IP addresses of the current machine, avoiding the earlier requirement of specifying the -server. With 4.0.24, the /etc/init.d/resin can be left as-is. If you look at the new default resin.xml, it has a resin:properties path=${__DIR__}/resin.properties and several uses of rvar like http port=${rvar('http')}/. The resin:properties is similar to the resin:import, but loads a properties file and saves the values in EL expressions which are then available to the resin.xml. Basically, this means that many sites will only need to change the resin.properties and may never need to touch the resin.xml. The new server-multi works with the resin.properties to make it easier to define the triad or the entire cluster. Instead of creating on server entry for each server, you can use the server-multi and set its address-list attribute to list all of the servers in the resin.properties like: app_tier : 192.168.1.10 192.168.1.11 192.168.1.12 and server-multi id-prefix=app- address-list=${rvar('app_tier')} port=6800/ Together with the CLI start-all, this lets you configure the app-tier cluster without modifying either the resin.xml or the /etc/init.d/resin. The resin.xml also includes a resin:import fileset=${__DIR__}/local.d/*.xml/ which will let you add configuration such as database tags in a separate *.xml without needing to modify the standard one. resinctl is now placed in /usr/bin for the make install, the rpm, and the deb. So it's always available. It's similar to bin/httpd.sh, but has the default installed locations build-in. In other words, on a Linux system, it already knows about /etc/resin, /var/log/resin, /var/www, and /usr/local/share/resin. -- Scott ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] 4.0.24 configuration notes
-Original Message- If you look at the new default resin.xml, it has a resin:properties path=${__DIR__}/resin.properties and several uses of rvar like http port=${rvar('http')}/. The resin:properties is similar to the resin:import, but loads a properties file and saves the values in EL expressions which are then available to the resin.xml. Basically, this means that many sites will only need to change the resin.properties and may never need to touch the resin.xml. This could be awesome! Will modifying the resin.properties force your resin instance to restart? The resin.xml also includes a resin:import fileset=${__DIR__}/local.d/*.xml/ which will let you add configuration such as database tags in a separate *.xml without needing to modify the standard one. Same question as above, will modifying the *.xml files force your resin instance to restart? Thanks, Aaron ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] 4.0.24 configuration notes
On 11/21/2011 11:08 AM, Aaron Freeman wrote: -Original Message- If you look at the new default resin.xml, it has a resin:properties path=${__DIR__}/resin.properties and several uses of rvar likehttp port=${rvar('http')}/. The resin:properties is similar to the resin:import, but loads a properties file and saves the values in EL expressions which are then available to the resin.xml. Basically, this means that many sites will only need to change the resin.properties and may never need to touch the resin.xml. This could be awesome! I hope so. Since it's new, this is a great time for feedback Will modifying the resin.properties force your resin instance to restart? Yes. It's the same mechanism as modifying resin.xml causing a restart. The resin.xml also includes a resin:import fileset=${__DIR__}/local.d/*.xml/ which will let you add configuration such asdatabase tags in a separate *.xml without needing to modify the standard one. Same question as above, will modifying the *.xml files force your resin instance to restart? Yep. -- Scott ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest