A new linux script to launch petals
|
View:
New views
2 Messages
—
Rating Filter:
Alert me
|
 |
A new linux script to launch petals
by Frederic Gardes - eBM Websourcing
::
Rate this Message:
new way to administrate the container is on development. Why?
->To get a robust action to stop petals (call the java stop then, if needed, call the terminate signal and then, if needed, call the kill signal+clean all the environnement to be ready to start again) ->to clarify the actions : a stop stops the container (components and service assemblies uninstalled/undeployed), and a suspend ... suspends the container (all the component installations and the service assembly deployments are kept). ->to provide a real linux daemon: you can put it into crontabs without problems, insert it into the update-rc.d (to suspend/start petals with your system,...), you don't have any output on the screen (it's forbidden by the init.d manager),... ->to provide a real "status" command , on a pid file at the execution ->to provide one dot per 3 seconds to says "hey i'am starting, no problem". Goodies sometimes aren't just goodies... The option "console" always allows to keep the output on the console (the log trace aren't blocked). What we need at this time? Just the "debbug" option (as soon as possible). With it and the update of the documentaition, the actual startup.sh, stop.sh environnement.sh and debbug.sh will be deprecated for me. Have you got any suggestion? A little sample (we already use it for clients), with a JAVA_HOME but without a PETALS_HOME: fgardes@ebm-25:~$ /home/logica/petals-platform-3.0-SNAPSHOT-3/bin/petals-esb start The PETALS_HOME variable is wrong. We are going to try a default path: /home/logica/petals-platform-3.0-SNAPSHOT-3 Starting petals-esb: .........OK fgardes@ebm-25:~$ /home/logica/petals-platform-3.0-SNAPSHOT-3/bin/petals-esb status The PETALS_HOME variable is wrong. We are going to try a default path: /home/logica/petals-platform-3.0-SNAPSHOT-3 petals-esb is RUNNING (pid 29765) fgardes@ebm-25:~$ /home/logica/petals-platform-3.0-SNAPSHOT-3/bin/petals-esb stop The PETALS_HOME variable is wrong. We are going to try a default path: /home/logica/petals-platform-3.0-SNAPSHOT-3 Stopping petals-esb: ..OK fgardes@ebm-25:~$ /home/logica/petals-platform-3.0-SNAPSHOT-3/bin/petals-esb console The PETALS_HOME variable is wrong. We are going to try a default path: /home/logica/petals-platform-3.0-SNAPSHOT-3 ----------------------------------------------------------- | | | OW2 PEtALS Enterprise Service Bus | | http://petals.ow2.org | | | ----------------------------------------------------------- PEtALS ESB is starting... [Petals.Communication.RMIConnectorImpl]-INFO 2009-09-10 13:26:06,436 JMX RMI server started at : service:jmx:rmi:///jndi/rmi://localhost:7700/jmxRmiConnector 2009-09-10 13:26:08,088 INFO transport.cxf.CXFMessageReceiver Start receiving on http://localhost:7900/services/RegistryService 2009-09-10 13:26:08,088 INFO transport.cxf.CXFMessageReceiver Start receiving on http://localhost:7900/services/RegistryService [Petals.JBI-Messaging.EndpointRegistryImpl]-INFO 2009-09-10 13:26:09,889 The registry is ready process requests on http://localhost:7900 [Petals.Transporter.NioTransportProtocol.NioServerAgent]-INFO 2009-09-10 13:26:10,594 The NIO transporter server is ready to process request on port 7800 [Petals.Tools.WebServiceManagerImpl]-INFO 2009-09-10 13:26:10,674 Kernel Web service 'JBIArtefactsService' has been added and is available at 'http://localhost:9001/petals/ws/JBIArtefactsService' [Petals.Tools.WebServiceManagerImpl]-INFO 2009-09-10 13:26:10,726 Kernel Web service 'ArtifactRepositoryService' has been added and is available at 'http://localhost:9001/petals/ws/ArtifactRepositoryService' [Petals.Tools.WebServiceManagerImpl]-INFO 2009-09-10 13:26:10,753 Kernel Web service 'RuntimeService' has been added and is available at 'http://localhost:9001/petals/ws/RuntimeService' [Petals.Tools.WebServiceManagerImpl]-INFO 2009-09-10 13:26:10,801 Kernel Web service 'EndpointService' has been added and is available at 'http://localhost:9001/petals/ws/EndpointService' [Petals.Tools.WebServiceManagerImpl]-INFO 2009-09-10 13:26:10,821 Kernel Web service 'TopologyService' has been added and is available at 'http://localhost:9001/petals/ws/TopologyService' [Petals.Tools.WebServiceManagerImpl]-INFO 2009-09-10 13:26:10,853 Kernel Web service 'InformationService' has been added and is available at 'http://localhost:9001/petals/ws/InformationService' PEtALS ESB platform distribution successfully started - 10/09/09 13:26 System Information : Petals JBI Container - version: 3.0-SNAPSHOT PEtALS prompt. Tape 'help' for help. petals@localhost:/> q [Petals.PetalsAdminServiceImpl]-INFO 2009-09-10 13:26:17,832 PEtALS is stopping... [Petals.Transporter.NioTransportProtocol.NioServerAgent]-INFO 2009-09-10 13:26:17,840 The NIO Server agent is stopped. 2009-09-10 13:26:17,907 INFO transport.cxf.CXFMessageReceiver Stop receiving on http://localhost:7900/services/RegistryService 2009-09-10 13:26:17,907 INFO transport.cxf.CXFMessageReceiver Stop receiving on http://localhost:7900/services/RegistryService PEtALS ESB platform distribution is stopped - 10/09/09 13:26 fgardes@ebm-25:~$ -- You receive this message as a subscriber of the petals-users@... mailing list. To unsubscribe: mailto:petals-users-unsubscribe@... For general help: mailto:sympa@...?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
|
|
Re: A new linux script to launch petals
by Christophe Hamerling
::
Rate this Message:
Should be sent to the petals-dev list to discuss such things
Le 10 sept. 09 à 13:47, Frederic Gardes - eBM Websourcing a écrit : > new way to administrate the container is on development. Why? > ->To get a robust action to stop petals (call the java stop then, if > needed, call the terminate signal and then, if needed, call the kill > signal+clean all the environnement to be ready to start again) > ->to clarify the actions : a stop stops the container (components > and service assemblies uninstalled/undeployed), and a suspend ... > suspends the container (all the component installations and the > service assembly deployments are kept). > ->to provide a real linux daemon: you can put it into crontabs > without problems, insert it into the update-rc.d (to suspend/start > petals with your system,...), you don't have any output on the > screen (it's forbidden by the init.d manager),... > ->to provide a real "status" command , on a pid file at the execution > ->to provide one dot per 3 seconds to says "hey i'am starting, no > problem". Goodies sometimes aren't just goodies... > > The option "console" always allows to keep the output on the console > (the log trace aren't blocked). > What we need at this time? Just the "debbug" option (as soon as > possible). With it and the update of the documentaition, the actual > startup.sh, stop.sh environnement.sh and debbug.sh will be > deprecated for me. > Have you got any suggestion? > A little sample (we already use it for clients), with a JAVA_HOME > but without a PETALS_HOME: > > fgardes@ebm-25:~$ /home/logica/petals-platform-3.0-SNAPSHOT-3/bin/ > petals-esb start > The PETALS_HOME variable is wrong. We are going to try a default > path: /home/logica/petals-platform-3.0-SNAPSHOT-3 > Starting petals-esb: .........OK > fgardes@ebm-25:~$ /home/logica/petals-platform-3.0-SNAPSHOT-3/bin/ > petals-esb status > The PETALS_HOME variable is wrong. We are going to try a default > path: /home/logica/petals-platform-3.0-SNAPSHOT-3 > petals-esb is RUNNING (pid 29765) > fgardes@ebm-25:~$ /home/logica/petals-platform-3.0-SNAPSHOT-3/bin/ > petals-esb stop > The PETALS_HOME variable is wrong. We are going to try a default > path: /home/logica/petals-platform-3.0-SNAPSHOT-3 > Stopping petals-esb: ..OK > fgardes@ebm-25:~$ /home/logica/petals-platform-3.0-SNAPSHOT-3/bin/ > petals-esb console > The PETALS_HOME variable is wrong. We are going to try a default > path: /home/logica/petals-platform-3.0-SNAPSHOT-3 > > ----------------------------------------------------------- > | | > | OW2 PEtALS Enterprise Service Bus | > | http://petals.ow2.org | > | | > ----------------------------------------------------------- > > PEtALS ESB is starting... > [Petals.Communication.RMIConnectorImpl]-INFO 2009-09-10 13:26:06,436 > JMX RMI server started at : service:jmx:rmi:///jndi/rmi://localhost: > 7700/jmxRmiConnector > 2009-09-10 13:26:08,088 INFO transport.cxf.CXFMessageReceiver Start > receiving on http://localhost:7900/services/RegistryService > 2009-09-10 13:26:08,088 INFO transport.cxf.CXFMessageReceiver Start > receiving on http://localhost:7900/services/RegistryService > [Petals.JBI-Messaging.EndpointRegistryImpl]-INFO 2009-09-10 > 13:26:09,889 The registry is ready process requests on http://localhost:7900 > [Petals.Transporter.NioTransportProtocol.NioServerAgent]-INFO > 2009-09-10 13:26:10,594 The NIO transporter server is ready to > process request on port 7800 > [Petals.Tools.WebServiceManagerImpl]-INFO 2009-09-10 13:26:10,674 > Kernel Web service 'JBIArtefactsService' has been added and is > available at 'http://localhost:9001/petals/ws/JBIArtefactsService' > [Petals.Tools.WebServiceManagerImpl]-INFO 2009-09-10 13:26:10,726 > Kernel Web service 'ArtifactRepositoryService' has been added and is > available at 'http://localhost:9001/petals/ws/ArtifactRepositoryService' > [Petals.Tools.WebServiceManagerImpl]-INFO 2009-09-10 13:26:10,753 > Kernel Web service 'RuntimeService' has been added and is available > at 'http://localhost:9001/petals/ws/RuntimeService' > [Petals.Tools.WebServiceManagerImpl]-INFO 2009-09-10 13:26:10,801 > Kernel Web service 'EndpointService' has been added and is available > at 'http://localhost:9001/petals/ws/EndpointService' > [Petals.Tools.WebServiceManagerImpl]-INFO 2009-09-10 13:26:10,821 > Kernel Web service 'TopologyService' has been added and is available > at 'http://localhost:9001/petals/ws/TopologyService' > [Petals.Tools.WebServiceManagerImpl]-INFO 2009-09-10 13:26:10,853 > Kernel Web service 'InformationService' has been added and is > available at 'http://localhost:9001/petals/ws/InformationService' > > PEtALS ESB platform distribution successfully started - 10/09/09 13:26 > System Information : Petals JBI Container - version: 3.0-SNAPSHOT > PEtALS prompt. Tape 'help' for help. > > petals@localhost:/> q > [Petals.PetalsAdminServiceImpl]-INFO 2009-09-10 13:26:17,832 PEtALS > is stopping... > [Petals.Transporter.NioTransportProtocol.NioServerAgent]-INFO > 2009-09-10 13:26:17,840 The NIO Server agent is stopped. > 2009-09-10 13:26:17,907 INFO transport.cxf.CXFMessageReceiver Stop > receiving on http://localhost:7900/services/RegistryService > 2009-09-10 13:26:17,907 INFO transport.cxf.CXFMessageReceiver Stop > receiving on http://localhost:7900/services/RegistryService > PEtALS ESB platform distribution is stopped - 10/09/09 13:26 > fgardes@ebm-25:~$ > > -- > You receive this message as a subscriber of the petals-users@... > mailing list. > To unsubscribe: mailto:petals-users-unsubscribe@... > For general help: mailto:sympa@...?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws SOA Research Engineer - OW2 PEtALS ESB Comitter 4 rue Amélie FR-31000 Toulouse Skype : christophe.hamerling -- You receive this message as a subscriber of the petals-users@... mailing list. To unsubscribe: mailto:petals-users-unsubscribe@... For general help: mailto:sympa@...?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
| Free embeddable forum powered by Nabble | Forum Help |
