[Resin-interest] resin 3.1.6 startup options, no -pid ?
I'm upgrading from resin 3.1.1 to 3.1.6 which is, I believe, the current stable version. I tried my existing startup script and got this error: [EMAIL PROTECTED] local]# /etc/init.d/resin start unknown argument '-pid' usage: java -jar resin.jar [-options] [status | start | stop | restart | kill | shutdown] where options include: -conf file : select a configuration file -log-directory dir : select a logging directory -resin-home dir : select a resin home directory -root-directory dir : select a root directory -server id : select a server to run -watchdog-port port : override the watchdog-port -verbose : print verbose starting information The relevant bit of the startup script is: su $USER -c $HTTPD start -verbose -J-server -J-Xms1024m -J-Xmx1024m \ -Djava.awt.headless=true -pid $PID -jvm-log $JVMLOG \ -stdout $STDOUT -stderr $STDERR $* where the $VARIABLES have reasonable values. I checked the resin docs and the wiki but could not find any information on the -pid option. I'd like to retain it as the stop script uses it as a backup shutdown method. Can anyone point me to documentation on this? Thanks, Rachel ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] resin 3.1.6 startup options, no -pid ?
On Oct 6, 2008, at 12:49 PM, Rachel McConnell wrote: I'm upgrading from resin 3.1.1 to 3.1.6 which is, I believe, the current stable version. I tried my existing startup script and got this error: [EMAIL PROTECTED] local]# /etc/init.d/resin start unknown argument '-pid' usage: java -jar resin.jar [-options] [status | start | stop | restart | kill | shutdown] where options include: -conf file : select a configuration file -log-directory dir : select a logging directory -resin-home dir : select a resin home directory -root-directory dir : select a root directory -server id : select a server to run -watchdog-port port : override the watchdog-port -verbose : print verbose starting information The relevant bit of the startup script is: su $USER -c $HTTPD start -verbose -J-server -J-Xms1024m -J-Xmx1024m \ -Djava.awt.headless=true -pid $PID -jvm-log $JVMLOG \ -stdout $STDOUT -stderr $STDERR $* where the $VARIABLES have reasonable values. I checked the resin docs and the wiki but could not find any information on the -pid option. I'd like to retain it as the stop script uses it as a backup shutdown method. Can anyone point me to documentation on this? The -pid doesn't exist in 3.1.x because of the switch to the watchdog mechanism. The watchdog keeps track of the pids internally. -- Scott Thanks, Rachel ___ 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] resin 3.1.6 startup options, no -pid ?
Thanks Scott. Can the watchdog handle multiple resin instances on the same machine, where each is started up with a different resin.conf script from the same resin home? Our webapps are the same for each, and the resin install is the same, but the server configuration is different so we use different startup scripts. We do not use resin's built-in clustering. Rachel On Mon, Oct 6, 2008 at 5:24 PM, Scott Ferguson [EMAIL PROTECTED] wrote: On Oct 6, 2008, at 12:49 PM, Rachel McConnell wrote: I'm upgrading from resin 3.1.1 to 3.1.6 which is, I believe, the current stable version. I tried my existing startup script and got this error: [EMAIL PROTECTED] local]# /etc/init.d/resin start unknown argument '-pid' usage: java -jar resin.jar [-options] [status | start | stop | restart | kill | shutdown] where options include: -conf file : select a configuration file -log-directory dir : select a logging directory -resin-home dir : select a resin home directory -root-directory dir : select a root directory -server id : select a server to run -watchdog-port port : override the watchdog-port -verbose : print verbose starting information The relevant bit of the startup script is: su $USER -c $HTTPD start -verbose -J-server -J-Xms1024m -J-Xmx1024m \ -Djava.awt.headless=true -pid $PID -jvm-log $JVMLOG \ -stdout $STDOUT -stderr $STDERR $* where the $VARIABLES have reasonable values. I checked the resin docs and the wiki but could not find any information on the -pid option. I'd like to retain it as the stop script uses it as a backup shutdown method. Can anyone point me to documentation on this? The -pid doesn't exist in 3.1.x because of the switch to the watchdog mechanism. The watchdog keeps track of the pids internally. -- Scott Thanks, Rachel ___ 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
Re: [Resin-interest] Resin 3.1.6
On May 7, 2008, at 12:50 PM, Alex Sharaz wrote: Scott, Just upgraded 1 test server to 3.1.6. Am using a watchdog conf file with the following in it Thanks, it's http://bugs.caucho.com/view.php?id=2652 The fix will be in the snapshot. -- Scott watchdog id=commswiki resin-conf/var/web/conf/commswiki.conf/resin-conf !-- resin-root/var/web/resin-root -- open-port address=150.237.47.46 port=80/ jvm-arg-Xmx256m/jvm-arg Had to comment out the resin-root... Config entry as it generated an error when I started it Alex On 06/05/2008 23:32, Scott Ferguson [EMAIL PROTECTED] wrote: Resin 3.1.6 is now available. The 3.1.x tree is now the stable version and will contain only bug fixes. New development will go into the 3.2.x tree. The release notes are at http://caucho.com/resin/changes/resin-3.1.6.xtp The detailed changelog is at http://caucho.com/resin/changes/changes.xtp 1. Resin JSF Resin's JSF implementation has been promoted to the 3.1.6 release. The JSF implementation includes a large number of bug fixes and compatibility testing. Resin's JSF includes to important enhancements: direct JSP implementation and Hessian serialization, both of which improve performance and reduce session size. 2. Quercus (PHP) A large number of bug fixes are included in the Quercus release. We've moved our focus to a killer app strategy, where the first priority of Quercus is keeping up to date with new killer app versions. The killer apps are currently: Mediawiki 1.12 (wikipedia) Drupal 6.0 phpBB3 Typo3 Wordpress 2.5.1 3. HMTP (Hessian Message Transport Protocol) http://caucho.com/resin/doc/hmtp.xtp HMTP is all about putting the interactive in RIA (rich interactive applications.) It's a high-performance, bidirectional, asynchronous messaging system based on Hessian and XMPP (Jabber IM). The current implementations are in Java and Flash. The underlying model is a Brokered Agent Messaging (bam), which is the XMPP model. Essentially, it's a hub-and-spoke messaging model with dynamic services. Agents are things like a chat login, or a chat room nickname, or a game's player. We think HMTP is the next step in web interactivity, leapfrogging over the interim Ajax/Comet techniques. 4. scheduled-task http://caucho.com/resin/doc/resources.xtp scheduled-task is a nice convenience bean for scheduling cron jobs. The full cron syntax is supported. scheduled-task can start Runnable beans automatically, or invoke an EL method expression, or execute a URL (convenient for PHP cron scripts.) 5. administration/reliability http://caucho.com/resin/doc/resin-admin.xtp For Resin-Pro, the administration task now checks CPU usage every 60 seconds, either logging the results, or logging a thread dump if the cpu is excessive. It's possible to configure the admin to restart Resin if the CPU usage it too high as wel. 6. logging http://caucho.com/resin/doc/config-log.xtp We've cleaned up the logging a bit, making it easier to configure custom logging Handlers and Formatting tools. In addition, we've split out log-handler as a separate configuration item, which configures the log handlers directly. logger configures the Loggers. (The older log is now discouraged since it combines both and is a bit confusing.) The logging has some new handlers: event:, jms:, and hmtp: which lets you publish logging messages to WebBeans events, JMS, and HMTP respectively. share and enjoy! -- Scott ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest * To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html * ___ 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] Resin 3.1.6
Scott, Just upgraded 1 test server to 3.1.6. Am using a watchdog conf file with the following in it watchdog id=commswiki resin-conf/var/web/conf/commswiki.conf/resin-conf !-- resin-root/var/web/resin-root -- open-port address=150.237.47.46 port=80/ jvm-arg-Xmx256m/jvm-arg Had to comment out the resin-root... Config entry as it generated an error when I started it Alex On 06/05/2008 23:32, Scott Ferguson [EMAIL PROTECTED] wrote: Resin 3.1.6 is now available. The 3.1.x tree is now the stable version and will contain only bug fixes. New development will go into the 3.2.x tree. The release notes are at http://caucho.com/resin/changes/resin-3.1.6.xtp The detailed changelog is at http://caucho.com/resin/changes/changes.xtp 1. Resin JSF Resin's JSF implementation has been promoted to the 3.1.6 release. The JSF implementation includes a large number of bug fixes and compatibility testing. Resin's JSF includes to important enhancements: direct JSP implementation and Hessian serialization, both of which improve performance and reduce session size. 2. Quercus (PHP) A large number of bug fixes are included in the Quercus release. We've moved our focus to a killer app strategy, where the first priority of Quercus is keeping up to date with new killer app versions. The killer apps are currently: Mediawiki 1.12 (wikipedia) Drupal 6.0 phpBB3 Typo3 Wordpress 2.5.1 3. HMTP (Hessian Message Transport Protocol) http://caucho.com/resin/doc/hmtp.xtp HMTP is all about putting the interactive in RIA (rich interactive applications.) It's a high-performance, bidirectional, asynchronous messaging system based on Hessian and XMPP (Jabber IM). The current implementations are in Java and Flash. The underlying model is a Brokered Agent Messaging (bam), which is the XMPP model. Essentially, it's a hub-and-spoke messaging model with dynamic services. Agents are things like a chat login, or a chat room nickname, or a game's player. We think HMTP is the next step in web interactivity, leapfrogging over the interim Ajax/Comet techniques. 4. scheduled-task http://caucho.com/resin/doc/resources.xtp scheduled-task is a nice convenience bean for scheduling cron jobs. The full cron syntax is supported. scheduled-task can start Runnable beans automatically, or invoke an EL method expression, or execute a URL (convenient for PHP cron scripts.) 5. administration/reliability http://caucho.com/resin/doc/resin-admin.xtp For Resin-Pro, the administration task now checks CPU usage every 60 seconds, either logging the results, or logging a thread dump if the cpu is excessive. It's possible to configure the admin to restart Resin if the CPU usage it too high as wel. 6. logging http://caucho.com/resin/doc/config-log.xtp We've cleaned up the logging a bit, making it easier to configure custom logging Handlers and Formatting tools. In addition, we've split out log-handler as a separate configuration item, which configures the log handlers directly. logger configures the Loggers. (The older log is now discouraged since it combines both and is a bit confusing.) The logging has some new handlers: event:, jms:, and hmtp: which lets you publish logging messages to WebBeans events, JMS, and HMTP respectively. share and enjoy! -- Scott ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest * To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html * ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Resin 3.1.6
Resin 3.1.6 is now available. The 3.1.x tree is now the stable version and will contain only bug fixes. New development will go into the 3.2.x tree. The release notes are at http://caucho.com/resin/changes/resin-3.1.6.xtp The detailed changelog is at http://caucho.com/resin/changes/changes.xtp 1. Resin JSF Resin's JSF implementation has been promoted to the 3.1.6 release. The JSF implementation includes a large number of bug fixes and compatibility testing. Resin's JSF includes to important enhancements: direct JSP implementation and Hessian serialization, both of which improve performance and reduce session size. 2. Quercus (PHP) A large number of bug fixes are included in the Quercus release. We've moved our focus to a killer app strategy, where the first priority of Quercus is keeping up to date with new killer app versions. The killer apps are currently: Mediawiki 1.12 (wikipedia) Drupal 6.0 phpBB3 Typo3 Wordpress 2.5.1 3. HMTP (Hessian Message Transport Protocol) http://caucho.com/resin/doc/hmtp.xtp HMTP is all about putting the interactive in RIA (rich interactive applications.) It's a high-performance, bidirectional, asynchronous messaging system based on Hessian and XMPP (Jabber IM). The current implementations are in Java and Flash. The underlying model is a Brokered Agent Messaging (bam), which is the XMPP model. Essentially, it's a hub-and-spoke messaging model with dynamic services. Agents are things like a chat login, or a chat room nickname, or a game's player. We think HMTP is the next step in web interactivity, leapfrogging over the interim Ajax/Comet techniques. 4. scheduled-task http://caucho.com/resin/doc/resources.xtp scheduled-task is a nice convenience bean for scheduling cron jobs. The full cron syntax is supported. scheduled-task can start Runnable beans automatically, or invoke an EL method expression, or execute a URL (convenient for PHP cron scripts.) 5. administration/reliability http://caucho.com/resin/doc/resin-admin.xtp For Resin-Pro, the administration task now checks CPU usage every 60 seconds, either logging the results, or logging a thread dump if the cpu is excessive. It's possible to configure the admin to restart Resin if the CPU usage it too high as wel. 6. logging http://caucho.com/resin/doc/config-log.xtp We've cleaned up the logging a bit, making it easier to configure custom logging Handlers and Formatting tools. In addition, we've split out log-handler as a separate configuration item, which configures the log handlers directly. logger configures the Loggers. (The older log is now discouraged since it combines both and is a bit confusing.) The logging has some new handlers: event:, jms:, and hmtp: which lets you publish logging messages to WebBeans events, JMS, and HMTP respectively. share and enjoy! -- Scott ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
