Déploiement des composants de petals esb 4.1

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

Déploiement des composants de petals esb 4.1

theirman
Bonjour,

  Je tente de déployer les composants sur un bus Petals d'une machine de production, chose que j'avais réussi à faire sur une machine de test, mais j'obtiens des messages d'erreur pour presque chacun des composants (sauf SL, BC-SOAP et BC-JMS)
  - le plus courant : javax.jbi.JBIException: Bootstrap failure on INSTALL
  - autre : org.ow2.petals.admin.api.exception.ArtifactAdministrationException: Impossible to set parameters for this component (no installer configuration MBean)


petals-cli@localhost:7700>deploy -u /home/petals-user/petals-soa-suite/Components/ServicesEngines/petals-se-validation-1.1.3.zip 
ERROR on command 'deploy': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: org.ow2.petals.jmx.exception.PerformActionRemoteErrorException: javax.jbi.JBIException: Bootstrap failure on INSTALL

petals-cli@localhost:7700>undeploy -u /home/petals-user/petals-soa-suite/Components/ServicesEngines/petals-se-validation-1.1.3.zip 
ATTENTION: The component is not installed but loaded, it will be automatically unloaded.

petals-cli@localhost:7700>deploy -u /home/petals-user/petals-soa-suite/Components/ServicesEngines/petals-se-rmi-1.1.1.zip 
ERROR on command 'deploy': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: Impossible to set parameters for this component (no installer configuration MBean)

petals-cli@localhost:7700>undeploy -u /home/petals-user/petals-soa-suite/Components/ServicesEngines/petals-se-rmi-1.1.1.zip 
ATTENTION: The component is not installed but loaded, it will be automatically unloaded.

petals-cli@localhost:7700>deploy -u /home/petals-user/petals-soa-suite/Components/ServicesEngines/petals-se-notification-1.0.3.zip 
ERROR on command 'deploy': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: org.ow2.petals.jmx.exception.PerformActionRemoteErrorException: javax.jbi.JBIException: Bootstrap failure on INSTALL

petals-cli@localhost:7700>undeploy -u /home/petals-user/petals-soa-suite/Components/ServicesEngines/petals-se-notification-1.0.3.zip  
ATTENTION: The component is not installed but loaded, it will be automatically unloaded.

petals-cli@localhost:7700>deploy -u /home/petals-user/petals-soa-suite/Components/ServicesEngines/petals-se-quartz-1.1.2.zip 
ERROR on command 'deploy': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: org.ow2.petals.jmx.exception.PerformActionRemoteErrorException: javax.jbi.JBIException: Bootstrap failure on INSTALL

petals-cli@localhost:7700>undeploy -u /home/petals-user/petals-soa-suite/Components/ServicesEngines/petals-se-quartz-1.1.2.zip 
ATTENTION: The component is not installed but loaded, it will be automatically unloaded.

petals-cli@localhost:7700>deploy -u /home/petals-user/petals-soa-suite/Components/BindingComponents/petals-bc-sftp-1.2.1.zip 
ERROR on command 'deploy': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: org.ow2.petals.jmx.exception.PerformActionRemoteErrorException: javax.jbi.JBIException: Bootstrap failure on INSTALL

petals-cli@localhost:7700>undeploy -u /home/petals-user/petals-soa-suite/Components/BindingComponents/petals-bc-sftp-1.2.1.zip 
ATTENTION: The component is not installed but loaded, it will be automatically unloaded.

petals-cli@localhost:7700>deploy -u /home/petals-user/petals-soa-suite/Components/BindingComponents/petals-bc-ftp-3.3.1.zip 
ERROR on command 'deploy': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: org.ow2.petals.jmx.exception.PerformActionRemoteErrorException: javax.jbi.JBIException: Bootstrap failure on INSTALL

petals-cli@localhost:7700>undeploy -u /home/petals-user/petals-soa-suite/Components/BindingComponents/petals-bc-ftp-3.3.1.zip 
ATTENTION: The component is not installed but loaded, it will be automatically unloaded.

petals-cli@localhost:7700>deploy -u /home/petals-user/petals-soa-suite/Components/BindingComponents/petals-bc-filetransfer-2.4.4.zip 
ERROR on command 'deploy': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: org.ow2.petals.jmx.exception.PerformActionRemoteErrorException: javax.jbi.JBIException: Bootstrap failure on INSTALL

petals-cli@localhost:7700>undeploy -u /home/petals-user/petals-soa-suite/Components/BindingComponents/petals-bc-filetransfer-2.4.4.zip 
ATTENTION: The component is not installed but loaded, it will be automatically unloaded.

petals-cli@localhost:7700>deploy -u /home/petals-user/petals-soa-suite/Components/BindingComponents/petals-bc-ejb-1.3.zip 
ERROR on command 'deploy': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: org.ow2.petals.jmx.exception.PerformActionRemoteErrorException: javax.jbi.JBIException: Bootstrap failure on INSTALL

petals-cli@localhost:7700>deploy -u /home/petals-user/petals-soa-suite/Components/BindingComponents/petals-bc-ftp-3.3.1.zip 
ERROR on command 'deploy': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: org.ow2.petals.jmx.exception.PerformActionRemoteErrorException: javax.jbi.JBIException: Bootstrap failure on INSTALL

petals-cli@localhost:7700>deploy -u /home/petals-user/petals-soa-suite/Components/BindingComponents/petals-bc-soap-4.1.0.zip 

petals-cli@localhost:7700>deploy -u /home/petals-user/petals-soa-suite/Components/BindingComponents/petals-bc-jms-3.1.1.zip 


Et la commande list me renvoie :
petals-cli@localhost:7700>list
petals-sl-activemq-5.3.0 SL
petals-sl-easybeans-1.0.2 SL
petals-sl-hsql-1.8.0.10 SL
petals-sl-jboss-4.0.2 SL
petals-sl-jonas-5.0-M1 SL
petals-sl-joram-5.2.6 SL
petals-sl-mysql-5.1.10 SL
petals-bc-soap STARTED BC
petals-bc-jms STARTED SE

Franchement, je ne vois pas d'où peut venir l'erreur. Dans l'immédiat, je n'ai besoin que de BC-SOAP (installé) et SE-RMI (en erreur) pour la webconsole. Mais si qqn a une idée, je suis preneur.

Cordialement
TH
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

theirman
Je me suis réjouis un peu trop vite pour le BC-SOAP. Il ne résiste pas à un redemarrage du serveur :

Initializing server ...
Starting server ...
0 2013/03/01 17:33:40,473 GMT+0100 INFO [Petals.Communication.RMIConnector] : JMX RMI server started at : service:jmx:rmi:///jndi/rmi://localhost:7700/jmxRmiConnector
0 2013/03/01 17:33:42,490 GMT+0100 INFO [Petals.JBI-Messaging.EndpointRegistry] : The registry is ready process requests on http://localhost:7900
0 2013/03/01 17:33:42,819 GMT+0100 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : The NIO transporter server is ready to process request on port 7800
0 2013/03/01 17:33:42,896 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'ArtifactRepositoryService' has been added and is available at 'http://localhost:7600/petals/ws/ArtifactRepositoryService'
0 2013/03/01 17:33:42,943 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'DeploymentService' has been added and is available at 'http://localhost:7600/petals/ws/DeploymentService'
0 2013/03/01 17:33:42,973 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'InstallationService' has been added and is available at 'http://localhost:7600/petals/ws/InstallationService'
0 2013/03/01 17:33:43,131 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'TopologyService' has been added and is available at 'http://localhost:7600/petals/ws/TopologyService'
0 2013/03/01 17:33:43,167 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'EndpointService' has been added and is available at 'http://localhost:7600/petals/ws/EndpointService'
0 2013/03/01 17:33:43,223 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'JBIArtefactsService' has been added and is available at 'http://localhost:7600/petals/ws/JBIArtefactsService'
0 2013/03/01 17:33:43,358 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'ExecutionEnvironmentManager' has been added and is available at 'http://localhost:7600/petals/ws/ExecutionEnvironmentManager'
0 2013/03/01 17:33:43,393 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'ServiceAssemblyStateService' has been added and is available at 'http://localhost:7600/petals/ws/ServiceAssemblyStateService'
0 2013/03/01 17:33:43,418 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'RuntimeService' has been added and is available at 'http://localhost:7600/petals/ws/RuntimeService'
0 2013/03/01 17:33:43,442 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'InformationService' has been added and is available at 'http://localhost:7600/petals/ws/InformationService'
0 2013/03/01 17:33:43,634 GMT+0100 SEVERE [Petals.JBI-Management.SystemRecoveryService] : org.ow2.petals.jbi.management.ManagementException: A component consistency is corrupted: petals-bc-soap
Caused by: JBI descriptor entry was not found in repository for JBI artefact 'petals-bc-soap'
Its state changes to UNKNOWN
Please check the repository consistency.
java.util.concurrent.ExecutionException: org.ow2.petals.jbi.management.ManagementException: A component consistency is corrupted: petals-bc-soap
Caused by: JBI descriptor entry was not found in repository for JBI artefact 'petals-bc-soap'
Its state changes to UNKNOWN
Please check the repository consistency.
	at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
	at java.util.concurrent.FutureTask.get(FutureTask.java:83)
	at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl.recoverAllComponent(SystemRecoveryServiceImpl.java:252)
	at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl.recoverAllEntities(SystemRecoveryServiceImpl.java:166)
	at org.objectweb.fractal.julia.generated.C290d4ec8_0.recoverAllEntities(INTERCEPTOR[SystemRecoveryService])
	at org.objectweb.fractal.julia.generated.Ca30db3f3_0.recoverAllEntities(INTERFACE[SystemRecoveryService])
	at org.ow2.petals.kernel.server.PetalsServerImpl.recoverSystem(PetalsServerImpl.java:533)
	at org.ow2.petals.kernel.server.PetalsServerImpl.start(PetalsServerImpl.java:195)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.ow2.petals.launcher.PetalsLauncher.launchPetalsServer(PetalsLauncher.java:106)
	at org.ow2.petals.launcher.PetalsLauncher.main(PetalsLauncher.java:202)
Caused by: org.ow2.petals.jbi.management.ManagementException: A component consistency is corrupted: petals-bc-soap
Caused by: JBI descriptor entry was not found in repository for JBI artefact 'petals-bc-soap'
Its state changes to UNKNOWN
Please check the repository consistency.
	at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl$1.call(SystemRecoveryServiceImpl.java:229)
	at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl$1.call(SystemRecoveryServiceImpl.java:1)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
0 2013/03/01 17:33:43,636 GMT+0100 SEVERE [Petals.JBI-Management.SystemRecoveryService] : org.ow2.petals.jbi.management.ManagementException: A component consistency is corrupted: petals-se-rmi
Caused by: JBI descriptor entry was not found in repository for JBI artefact 'petals-se-rmi'
Its state changes to UNKNOWN
Please check the repository consistency.
java.util.concurrent.ExecutionException: org.ow2.petals.jbi.management.ManagementException: A component consistency is corrupted: petals-se-rmi
Caused by: JBI descriptor entry was not found in repository for JBI artefact 'petals-se-rmi'
Its state changes to UNKNOWN
Please check the repository consistency.
	at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
	at java.util.concurrent.FutureTask.get(FutureTask.java:83)
	at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl.recoverAllComponent(SystemRecoveryServiceImpl.java:252)
	at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl.recoverAllEntities(SystemRecoveryServiceImpl.java:166)
	at org.objectweb.fractal.julia.generated.C290d4ec8_0.recoverAllEntities(INTERCEPTOR[SystemRecoveryService])
	at org.objectweb.fractal.julia.generated.Ca30db3f3_0.recoverAllEntities(INTERFACE[SystemRecoveryService])
	at org.ow2.petals.kernel.server.PetalsServerImpl.recoverSystem(PetalsServerImpl.java:533)
	at org.ow2.petals.kernel.server.PetalsServerImpl.start(PetalsServerImpl.java:195)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.ow2.petals.launcher.PetalsLauncher.launchPetalsServer(PetalsLauncher.java:106)
	at org.ow2.petals.launcher.PetalsLauncher.main(PetalsLauncher.java:202)
Caused by: org.ow2.petals.jbi.management.ManagementException: A component consistency is corrupted: petals-se-rmi
Caused by: JBI descriptor entry was not found in repository for JBI artefact 'petals-se-rmi'
Its state changes to UNKNOWN
Please check the repository consistency.
	at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl$1.call(SystemRecoveryServiceImpl.java:229)
	at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl$1.call(SystemRecoveryServiceImpl.java:1)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Server STARTED
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

Vincent Zurczak
In reply to this post by theirman
Bonjour,

Est-ce qu'il n'y a pas de plus amples informations dans le fichier de log de CLI ?
Il faudra peut-être activer un niveau plus fin d'ailleurs (FINEST).

J'ai une petite idée sur le sujet, mais je vais attendre d'en savoir un peu plus avant de m'avancer.
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

theirman
Je viens de passer le niveau de détails des composants à FINEST dans logger.properties
 - Petals.Container.Components.level=FINEST

Puis je retente toutes les opérations, en utilisant le répertoire install/ d'auto-déploiement :
  - démarrage du bus vierge de tous composants [OK]
  - ajout de SE-RMI [OK]
  - ajout de BC-SOAP [OK]
  - arret du bus [OK]
  - démarrage du bus contenant SE-RMI et BC-SOAP [OK]
  - ajout de BC-SFTP [ERROR]
  - suppression de BC-SFTP [OK]

Voici le log de petals ESB :
0 2013/03/04 11:11:54,233 GMT+0100 INFO [Petals.Communication.RMIConnector] : JMX RMI server started at : service:jmx:rmi:///jndi/rmi://localhost:7700/jmxRmiConnector
0 2013/03/04 11:11:56,328 GMT+0100 INFO [Petals.JBI-Messaging.EndpointRegistry] : The registry is ready process requests on http://localhost:7900
0 2013/03/04 11:11:56,686 GMT+0100 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : The NIO transporter server is ready to process request on port 7800
0 2013/03/04 11:11:56,772 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'ArtifactRepositoryService' has been added and is available at 'http://localhost:7600/petals/ws/ArtifactRepositoryService'
0 2013/03/04 11:11:56,818 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'DeploymentService' has been added and is available at 'http://localhost:7600/petals/ws/DeploymentService'
0 2013/03/04 11:11:56,853 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'InstallationService' has been added and is available at 'http://localhost:7600/petals/ws/InstallationService'
0 2013/03/04 11:11:57,020 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'TopologyService' has been added and is available at 'http://localhost:7600/petals/ws/TopologyService'
0 2013/03/04 11:11:57,054 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'EndpointService' has been added and is available at 'http://localhost:7600/petals/ws/EndpointService'
0 2013/03/04 11:11:57,127 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'JBIArtefactsService' has been added and is available at 'http://localhost:7600/petals/ws/JBIArtefactsService'
0 2013/03/04 11:11:57,309 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'ExecutionEnvironmentManager' has been added and is available at 'http://localhost:7600/petals/ws/ExecutionEnvironmentManager'
0 2013/03/04 11:11:57,347 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'ServiceAssemblyStateService' has been added and is available at 'http://localhost:7600/petals/ws/ServiceAssemblyStateService'
0 2013/03/04 11:11:57,368 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'RuntimeService' has been added and is available at 'http://localhost:7600/petals/ws/RuntimeService'
0 2013/03/04 11:11:57,392 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'InformationService' has been added and is available at 'http://localhost:7600/petals/ws/InformationService'
0 2013/03/04 11:12:36,528 GMT+0100 INFO [Petals.JBI-Management.InstallationService] : A new installer for the component 'petals-bc-soap' is loaded
0 2013/03/04 11:12:36,535 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.bootstrap.petals-bc-soap] : Install component [Name : petals-bc-soap, Version : 4.1.0]
0 2013/03/04 11:12:36,656 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-bc-soap' installed
0 2013/03/04 11:12:36,657 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Init component...
0 2013/03/04 11:12:37,692 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : The JMS transport layer configuration is not complete. It is disabled.
0 2013/03/04 11:12:37,703 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Component initialized
0 2013/03/04 11:12:37,704 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Start component...
0 2013/03/04 11:12:37,816 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : Starting Jetty server...
0 2013/03/04 11:12:37,817 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : Hosts : 127.0.0.1 (localhost) / 138.102.xx.xx (xxxxxxxx.inra.fr) - HTTP Port : 8084 - HTTPS Port : 0 - Jetty Max poolsize : 50 - Jetty Min poolsize : 2 - Jetty Acceptors size : 4
0 2013/03/04 11:12:37,818 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : jetty-6.1.9
0 2013/03/04 11:12:37,850 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : ServicesListServlet: init
0 2013/03/04 11:12:37,850 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : SoapServlet: init
0 2013/03/04 11:12:37,875 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : WelcomeServlet: init
0 2013/03/04 11:12:37,892 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : Started {}
0 2013/03/04 11:12:37,894 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Component Information is available at http://138.102.xx.xx:8084/
0 2013/03/04 11:12:37,895 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Component started
0 2013/03/04 11:13:26,585 GMT+0100 INFO [Petals.JBI-Management.InstallationService] : A new installer for the component 'petals-se-rmi' is loaded
0 2013/03/04 11:13:26,612 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-se-rmi' installed
0 2013/03/04 11:13:26,617 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] : INIT RMI engine
0 2013/03/04 11:13:26,634 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] : Starting RMI Service Engine...
0 2013/03/04 11:13:26,635 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] :  - RMI Port : 1099
0 2013/03/04 11:13:26,635 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] :  - Embedded : true
0 2013/03/04 11:13:26,636 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] :  - Component Context Name : RMIComponentContext
0 2013/03/04 11:13:36,923 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] : Stopping Service Engine...
0 2013/03/04 11:13:45,294 GMT+0100 INFO [Petals.Communication.RMIConnector] : JMX RMI server started at : service:jmx:rmi:///jndi/rmi://localhost:7700/jmxRmiConnector
0 2013/03/04 11:13:47,374 GMT+0100 INFO [Petals.JBI-Messaging.EndpointRegistry] : The registry is ready process requests on http://localhost:7900
0 2013/03/04 11:13:47,667 GMT+0100 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : The NIO transporter server is ready to process request on port 7800
0 2013/03/04 11:13:47,741 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'ArtifactRepositoryService' has been added and is available at 'http://localhost:7600/petals/ws/ArtifactRepositoryService'
0 2013/03/04 11:13:47,787 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'DeploymentService' has been added and is available at 'http://localhost:7600/petals/ws/DeploymentService'
0 2013/03/04 11:13:47,822 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'InstallationService' has been added and is available at 'http://localhost:7600/petals/ws/InstallationService'
0 2013/03/04 11:13:48,001 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'TopologyService' has been added and is available at 'http://localhost:7600/petals/ws/TopologyService'
0 2013/03/04 11:13:48,058 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'EndpointService' has been added and is available at 'http://localhost:7600/petals/ws/EndpointService'
0 2013/03/04 11:13:48,127 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'JBIArtefactsService' has been added and is available at 'http://localhost:7600/petals/ws/JBIArtefactsService'
0 2013/03/04 11:13:48,325 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'ExecutionEnvironmentManager' has been added and is available at 'http://localhost:7600/petals/ws/ExecutionEnvironmentManager'
0 2013/03/04 11:13:48,391 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'ServiceAssemblyStateService' has been added and is available at 'http://localhost:7600/petals/ws/ServiceAssemblyStateService'
0 2013/03/04 11:13:48,416 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'RuntimeService' has been added and is available at 'http://localhost:7600/petals/ws/RuntimeService'
0 2013/03/04 11:13:48,444 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'InformationService' has been added and is available at 'http://localhost:7600/petals/ws/InformationService'
0 2013/03/04 11:13:48,962 GMT+0100 INFO [Petals.JBI-Management.SystemRecoveryService] : Installer of the component 'petals-se-rmi' loaded
0 2013/03/04 11:13:49,083 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-se-rmi' installed
0 2013/03/04 11:13:49,089 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] : INIT RMI engine
0 2013/03/04 11:13:49,137 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] : Starting RMI Service Engine...
0 2013/03/04 11:13:49,137 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] :  - RMI Port : 1099
0 2013/03/04 11:13:49,138 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] :  - Embedded : true
0 2013/03/04 11:13:49,138 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] :  - Component Context Name : RMIComponentContext
0 2013/03/04 11:13:49,774 GMT+0100 INFO [Petals.JBI-Management.SystemRecoveryService] : Installer of the component 'petals-bc-soap' loaded
0 2013/03/04 11:13:49,778 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.bootstrap.petals-bc-soap] : Install component [Name : petals-bc-soap, Version : 4.1.0]
0 2013/03/04 11:13:49,934 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-bc-soap' installed
0 2013/03/04 11:13:49,935 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Init component...
0 2013/03/04 11:13:51,022 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : The JMS transport layer configuration is not complete. It is disabled.
0 2013/03/04 11:13:51,036 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Component initialized
0 2013/03/04 11:13:51,036 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Start component...
0 2013/03/04 11:13:51,155 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : Starting Jetty server...
0 2013/03/04 11:13:51,156 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : Hosts : 127.0.0.1 (localhost) / 138.102.xx.xx (xxxxxxxx.inra.fr) - HTTP Port : 8084 - HTTPS Port : 0 - Jetty Max poolsize : 50 - Jetty Min poolsize : 2 - Jetty Acceptors size : 4
0 2013/03/04 11:13:51,156 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : jetty-6.1.9
0 2013/03/04 11:14:07,024 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : ServicesListServlet: init
0 2013/03/04 11:14:07,024 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : SoapServlet: init
0 2013/03/04 11:14:07,052 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : WelcomeServlet: init
0 2013/03/04 11:14:07,068 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : Started {}
0 2013/03/04 11:14:07,071 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Component Information is available at http://138.102.xx.xx:8084/
0 2013/03/04 11:14:07,071 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Component started
0 2013/03/04 11:14:54,211 GMT+0100 INFO [Petals.JBI-Management.InstallationService] : A new installer for the component 'petals-bc-sftp' is loaded
0 2013/03/04 11:14:54,216 GMT+0100 INFO [Petals.Container.Components.petals-bc-sftp.bootstrap.petals-bc-sftp] : Install component [Name : petals-bc-sftp, Version : 1.2.1]
0 2013/03/04 11:14:54,236 GMT+0100 SEVERE [Petals.Container.Lifecycle.Installer] : Bootstrap failure on INSTALL
javax.jbi.JBIException: Bootstrap failure on INSTALL
	at org.ow2.petals.container.thread.BootstrapThread.doTask(BootstrapThread.java:116)
	at org.ow2.petals.container.thread.AbstractThread.run(AbstractThread.java:109)
Caused by: javax.xml.transform.TransformerFactoryConfigurationError: Provider net.sf.saxon.TransformerFactoryImpl not found
	at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:108)
	at org.ow2.petals.component.framework.util.XSLTUtilImpl.<init>(XSLTUtilImpl.java:75)
	at org.ow2.petals.component.framework.util.UtilFactory.<clinit>(UtilFactory.java:55)
	at org.ow2.petals.component.framework.DefaultBootstrap.processNotificationResource(DefaultBootstrap.java:238)
	at org.ow2.petals.component.framework.DefaultBootstrap.onInstall(DefaultBootstrap.java:130)
	at org.ow2.petals.container.thread.BootstrapThread.doTask(BootstrapThread.java:101)
	... 1 more
0 2013/03/04 11:14:54,237 GMT+0100 SEVERE [Petals.AutoLoaderService] : Error during the auto- installation of a component
javax.management.MBeanException: Exception thrown in RequiredModelMBean while trying to invoke operation install
	at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1101)
	at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:955)
	at mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(InvokerMBeanServerInterceptor.java:221)
	at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
	at mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(SecurityMBeanServerInterceptor.java:84)
	at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
	at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
	at mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.invoke(ContextClassLoaderMBeanServerInterceptor.java:203)
	at mx4j.server.MX4JMBeanServer.invoke(MX4JMBeanServer.java:1043)
	at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performInstallComponent(AutoLoaderServiceImpl.java:469)
	at org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.install(AutoLoaderServiceImpl.java:148)
	at org.ow2.petals.jbi.management.autoload.InstallDirectoryScanner.run(InstallDirectoryScanner.java:82)
	at java.util.TimerThread.mainLoop(Timer.java:512)
	at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.jbi.JBIException: Bootstrap failure on INSTALL
	at org.ow2.petals.container.thread.BootstrapThread.doTask(BootstrapThread.java:116)
	at org.ow2.petals.container.thread.AbstractThread.run(AbstractThread.java:109)
Caused by: javax.xml.transform.TransformerFactoryConfigurationError: Provider net.sf.saxon.TransformerFactoryImpl not found
	at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:108)
	at org.ow2.petals.component.framework.util.XSLTUtilImpl.<init>(XSLTUtilImpl.java:75)
	at org.ow2.petals.component.framework.util.UtilFactory.<clinit>(UtilFactory.java:55)
	at org.ow2.petals.component.framework.DefaultBootstrap.processNotificationResource(DefaultBootstrap.java:238)
	at org.ow2.petals.component.framework.DefaultBootstrap.onInstall(DefaultBootstrap.java:130)
	at org.ow2.petals.container.thread.BootstrapThread.doTask(BootstrapThread.java:101)
	... 1 more
0 2013/03/04 11:15:21,341 GMT+0100 INFO [Petals.JBI-Management.InstallationService] : Installer of the component 'petals-bc-sftp' succesfully unloaded

Notes supplémentaires :
  - petals-cli ne me sort aucun log (???)
  - petals-cli : quand je fais un deploy -u <url>, depuis que je suis en FINEST, ne me répond que "ERROR: .."
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

Christophe DENEUX
Administrator
This post has NOT been accepted by the mailing list yet.
Quelle version du BC SFTP utilise tu ?
Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

Christophe DENEUX
Administrator
This post has NOT been accepted by the mailing list yet.
D'après les logs de ton premier post, tu utiliserais le BC SFTP 1.2.1. Cette version n'est pas operationnelle sur Petals ESB 4.1, il faut utiliser la version 1.4.0 de la distribution (cf. les details du pack Petals ESB 4.1: http://download.petalslink.com/petals-esb.html)
Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

theirman
Effectivement Christophe, j'utilisais des composants plus anciens que j'avais sur une clé (ceux fournis avec petals-4.0 en fait)

Pour ma curiosité personnelle, quelles différences y-a-t-il entre les composants de la version 4.0 et ceux de la 4.1 ? pourquoi ne sont-ils pas compatibles ?


Pour info:
theirman@eowyn:/apps/petals/petals-esb-4.1$ sudo -u petals-user bin/petals-esb.sh
[sudo] password for theirman: 
     ___   ____ __   ___    __    ____   ____ ____ ___  
    / _ \ / __// /_ / _ |  / /   / __/  / __// __// _ ) 
   / ___// _/ / __// __ | / /__ _\ \   / _/ _\ \ / _  | 
  /_/   /___/ \__//_/ |_|/____//___/  /___//___//____/  

Initializing server ...
Starting server ...
0 2013/03/04 14:55:17,926 GMT+0100 INFO [Petals.Communication.RMIConnector] : JMX RMI server started at : service:jmx:rmi:///jndi/rmi://localhost:7700/jmxRmiConnector
0 2013/03/04 14:55:20,519 GMT+0100 INFO [Petals.JBI-Messaging.EndpointRegistry] : The registry is ready process requests on http://localhost:7900
0 2013/03/04 14:55:20,863 GMT+0100 INFO [Petals.Transporter.NioTransportProtocol.NioServerAgent] : The NIO transporter server is ready to process request on port 7800
0 2013/03/04 14:55:20,941 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'ArtifactRepositoryService' has been added and is available at 'http://localhost:7600/petals/ws/ArtifactRepositoryService'
0 2013/03/04 14:55:20,988 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'DeploymentService' has been added and is available at 'http://localhost:7600/petals/ws/DeploymentService'
0 2013/03/04 14:55:21,021 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'InstallationService' has been added and is available at 'http://localhost:7600/petals/ws/InstallationService'
0 2013/03/04 14:55:21,196 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'TopologyService' has been added and is available at 'http://localhost:7600/petals/ws/TopologyService'
0 2013/03/04 14:55:21,233 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'EndpointService' has been added and is available at 'http://localhost:7600/petals/ws/EndpointService'
0 2013/03/04 14:55:21,275 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'JBIArtefactsService' has been added and is available at 'http://localhost:7600/petals/ws/JBIArtefactsService'
0 2013/03/04 14:55:21,397 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'ExecutionEnvironmentManager' has been added and is available at 'http://localhost:7600/petals/ws/ExecutionEnvironmentManager'
0 2013/03/04 14:55:21,437 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'ServiceAssemblyStateService' has been added and is available at 'http://localhost:7600/petals/ws/ServiceAssemblyStateService'
0 2013/03/04 14:55:21,461 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'RuntimeService' has been added and is available at 'http://localhost:7600/petals/ws/RuntimeService'
0 2013/03/04 14:55:21,498 GMT+0100 INFO [Petals.Tools.WebServiceManager] : Kernel Web service 'InformationService' has been added and is available at 'http://localhost:7600/petals/ws/InformationService'
0 2013/03/04 14:55:22,220 GMT+0100 INFO [Petals.JBI-Management.SystemRecoveryService] : Installer of the component 'petals-se-rmi' loaded
0 2013/03/04 14:55:22,356 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-se-rmi' installed
0 2013/03/04 14:55:22,395 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] : INIT RMI engine
0 2013/03/04 14:55:22,484 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] : Starting RMI Service Engine...
0 2013/03/04 14:55:22,484 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] :  - RMI Port : 1099
0 2013/03/04 14:55:22,485 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] :  - Embedded : true
0 2013/03/04 14:55:22,485 GMT+0100 INFO [Petals.Container.Components.petals-se-rmi] :  - Component Context Name : RMIComponentContext
0 2013/03/04 14:55:23,713 GMT+0100 INFO [Petals.JBI-Management.SystemRecoveryService] : Installer of the component 'petals-bc-sql' loaded
0 2013/03/04 14:55:23,732 GMT+0100 INFO [Petals.Container.Components.petals-bc-sql.bootstrap.petals-bc-sql] : Install component [Name : petals-bc-sql, Version : 1.4.0]
0 2013/03/04 14:55:23,741 GMT+0100 INFO [Petals.JBI-Management.SystemRecoveryService] : Installer of the component 'petals-bc-sftp' loaded
0 2013/03/04 14:55:23,764 GMT+0100 INFO [Petals.Container.Components.petals-bc-sftp.bootstrap.petals-bc-sftp] : Install component [Name : petals-bc-sftp, Version : 1.4.0]
0 2013/03/04 14:55:23,868 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-bc-sql' installed
0 2013/03/04 14:55:23,873 GMT+0100 INFO [Petals.JBI-Management.SystemRecoveryService] : Installer of the component 'petals-bc-filetransfer' loaded
0 2013/03/04 14:55:23,876 GMT+0100 INFO [Petals.Container.Components.petals-bc-sql] : Init component...
0 2013/03/04 14:55:23,886 GMT+0100 INFO [Petals.Container.Components.petals-bc-filetransfer.bootstrap.petals-bc-filetransfer] : Install component [Name : petals-bc-filetransfer, Version : 3.1.0]
0 2013/03/04 14:55:23,891 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-bc-sftp' installed
0 2013/03/04 14:55:23,906 GMT+0100 INFO [Petals.Container.Components.petals-bc-sftp] : Init component...
0 2013/03/04 14:55:24,054 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-bc-filetransfer' installed
0 2013/03/04 14:55:24,072 GMT+0100 INFO [Petals.Container.Components.petals-bc-filetransfer] : Init component...
0 2013/03/04 14:55:24,207 GMT+0100 INFO [Petals.JBI-Management.SystemRecoveryService] : Installer of the component 'petals-se-validation' loaded
0 2013/03/04 14:55:24,215 GMT+0100 INFO [Petals.Container.Components.petals-se-validation.bootstrap.petals-se-validation] : Install component [Name : petals-se-validation, Version : 1.3.0]
0 2013/03/04 14:55:24,345 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-se-validation' installed
0 2013/03/04 14:55:24,367 GMT+0100 INFO [Petals.Container.Components.petals-se-validation] : Init component...
0 2013/03/04 14:55:25,444 GMT+0100 INFO [Petals.Container.Components.petals-bc-sql] : Component initialized
0 2013/03/04 14:55:25,444 GMT+0100 INFO [Petals.Container.Components.petals-bc-sql] : Start component...
0 2013/03/04 14:55:25,578 GMT+0100 INFO [Petals.Container.Components.petals-bc-filetransfer] : Component initialized
0 2013/03/04 14:55:25,583 GMT+0100 INFO [Petals.Container.Components.petals-bc-filetransfer] : Start component...
0 2013/03/04 14:55:25,681 GMT+0100 INFO [Petals.Container.Components.petals-bc-sql] : Component started
0 2013/03/04 14:55:26,081 GMT+0100 INFO [Petals.JBI-Management.SystemRecoveryService] : Installer of the component 'petals-bc-soap' loaded
0 2013/03/04 14:55:26,114 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.bootstrap.petals-bc-soap] : Install component [Name : petals-bc-soap, Version : 4.2.0]
0 2013/03/04 14:55:26,157 GMT+0100 INFO [Petals.Container.Components.petals-bc-filetransfer] : Component started
0 2013/03/04 14:55:26,240 GMT+0100 INFO [Petals.Container.Components.petals-se-validation] : Component initialized
0 2013/03/04 14:55:26,240 GMT+0100 INFO [Petals.Container.Components.petals-se-validation] : Start component...
0 2013/03/04 14:55:26,361 GMT+0100 INFO [Petals.Container.Components.petals-se-validation] : Component started
0 2013/03/04 14:55:26,411 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-bc-soap' installed
0 2013/03/04 14:55:26,416 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Init component...
0 2013/03/04 14:55:27,440 GMT+0100 INFO [Petals.JBI-Management.SystemRecoveryService] : Installer of the component 'petals-se-quartz' loaded
0 2013/03/04 14:55:27,454 GMT+0100 INFO [Petals.Container.Components.petals-se-quartz.bootstrap.petals-se-quartz] : Install component [Name : petals-se-quartz, Version : 1.3.0]
0 2013/03/04 14:55:27,607 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-se-quartz' installed
0 2013/03/04 14:55:27,616 GMT+0100 INFO [Petals.Container.Components.petals-se-quartz] : Init component...
0 2013/03/04 14:55:28,099 GMT+0100 INFO [Petals.JBI-Management.SystemRecoveryService] : Installer of the component 'petals-se-jsr181' loaded
0 2013/03/04 14:55:28,105 GMT+0100 INFO [Petals.Container.Components.petals-se-jsr181.bootstrap.petals-se-jsr181] : Install component [Name : petals-se-jsr181, Version : 1.3.0]
0 2013/03/04 14:55:28,302 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-se-jsr181' installed
0 2013/03/04 14:55:28,304 GMT+0100 INFO [Petals.Container.Components.petals-se-jsr181] : Init component...
0 2013/03/04 14:55:28,414 GMT+0100 INFO [Petals.JBI-Management.SystemRecoveryService] : Installer of the component 'petals-se-eip' loaded
0 2013/03/04 14:55:28,437 GMT+0100 INFO [Petals.Container.Components.petals-se-eip.bootstrap.petals-se-eip] : Install component [Name : petals-se-eip, Version : 2.7.0]
0 2013/03/04 14:55:28,617 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-se-eip' installed
0 2013/03/04 14:55:28,628 GMT+0100 INFO [Petals.Container.Components.petals-se-eip] : Init component...
0 2013/03/04 14:55:29,375 GMT+0100 INFO [Petals.Container.Components.petals-se-quartz] : Component initialized
0 2013/03/04 14:55:29,379 GMT+0100 INFO [Petals.Container.Components.petals-se-quartz] : Start component...
0 2013/03/04 14:55:29,659 GMT+0100 INFO [Petals.Container.Components.petals-se-quartz] : Component started
0 2013/03/04 14:55:30,474 GMT+0100 INFO [Petals.Container.Components.petals-se-eip] : Initialize the EIP Service Engine.
0 2013/03/04 14:55:30,540 GMT+0100 INFO [Petals.Container.Components.petals-se-eip] : Component initialized
0 2013/03/04 14:55:30,540 GMT+0100 INFO [Petals.Container.Components.petals-se-eip] : Start component...
0 2013/03/04 14:55:30,551 GMT+0100 INFO [Petals.Container.Components.petals-bc-sftp] : Component initialized
0 2013/03/04 14:55:30,552 GMT+0100 INFO [Petals.Container.Components.petals-bc-sftp] : Start component...
0 2013/03/04 14:55:30,916 GMT+0100 INFO [Petals.Container.Components.petals-se-eip] : Component started
0 2013/03/04 14:55:31,298 GMT+0100 INFO [Petals.JBI-Management.SystemRecoveryService] : Installer of the component 'petals-se-xslt' loaded
0 2013/03/04 14:55:31,302 GMT+0100 INFO [Petals.Container.Components.petals-se-xslt.bootstrap.petals-se-xslt] : Install component [Name : petals-se-xslt, Version : 2.6.0]
0 2013/03/04 14:55:31,476 GMT+0100 INFO [Petals.Container.Lifecycle.Installer] : Component 'petals-se-xslt' installed
0 2013/03/04 14:55:31,477 GMT+0100 INFO [Petals.Container.Components.petals-se-xslt] : Init component...
0 2013/03/04 14:55:32,184 GMT+0100 INFO [Petals.Container.Components.petals-se-jsr181] : Component initialized
0 2013/03/04 14:55:32,185 GMT+0100 INFO [Petals.Container.Components.petals-se-jsr181] : Start component...
0 2013/03/04 14:55:32,232 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : The JMS transport layer configuration is not complete. It is disabled.
0 2013/03/04 14:55:32,288 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Component initialized
0 2013/03/04 14:55:32,289 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Start component...
0 2013/03/04 14:55:32,449 GMT+0100 INFO [Petals.Container.Components.petals-se-jsr181] : Component started
0 2013/03/04 14:55:32,592 GMT+0100 INFO [Petals.Container.Components.petals-se-xslt] : Component initialized
0 2013/03/04 14:55:32,600 GMT+0100 INFO [Petals.Container.Components.petals-se-xslt] : Start component...
0 2013/03/04 14:55:32,753 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : Starting HTTP(S)/SOAP server...
0 2013/03/04 14:55:32,754 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : Hosts : 127.0.0.1 (localhost) / 138.102.xx.xx (xxxxxxxx.inra.fr) - HTTP Port : 8084 - HTTPS Port : 0 - HTTP(S) server max poolsize : 50 - HTTP(S) server min poolsize : 2 - HTTP(S) server acceptors size : 4
0 2013/03/04 14:55:32,754 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : jetty-6.1.9
0 2013/03/04 14:55:32,833 GMT+0100 INFO [Petals.Container.Components.petals-se-xslt] : Component started
0 2013/03/04 14:55:32,873 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : ServicesListServlet: init
0 2013/03/04 14:55:32,874 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : SoapServlet: init
0 2013/03/04 14:55:32,958 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : WelcomeServlet: init
0 2013/03/04 14:55:33,008 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap.jetty] : Started {}
0 2013/03/04 14:55:33,011 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Component Information is available at http://138.102.xx.xx:8084/
0 2013/03/04 14:55:33,011 GMT+0100 INFO [Petals.Container.Components.petals-bc-soap] : Component started
0 2013/03/04 14:55:34,605 GMT+0100 INFO [Petals.Container.Components.petals-bc-sftp] : Component started
Server STARTED
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

theirman
Et bien sûr, encore une fois, un grand merci à toi Christophe
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

Christophe DENEUX
Administrator
This post has NOT been accepted by the mailing list yet.
De mémoire, et en ce qui concerne ton problème, depuis la version 4 de Petals ESB, Saxon est utilisé comme moteur de transformation. Comme les composants fonctionnent dans leur propre classloader, il faut qu'ils embarquent une instance de Saxon que tu ne devais pas avoir dans ta version.
Certes cela consomme un peu plus de mémoire, mais aujourd'hui ce n'est pas un problème, vu les avantages d'indépendance. D'un autre coté, on n'aurait pu etre un peu plus malin pour ne pas définir Saxon via une propriété sur la ligne de commande mais plutôt via le système de SPI Java.
Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

theirman
Merci pour cette réponse explicative :)

Christophe DENEUX wrote
De mémoire, et en ce qui concerne ton problème, depuis la version 4 de Petals ESB, Saxon est utilisé comme moteur de transformation. Comme les composants fonctionnent dans leur propre classloader, il faut qu'ils embarquent une instance de Saxon que tu ne devais pas avoir dans ta version.
Encore et toujours les saxons !! ;)
Plus sérieusement, les composants que j'utilisais et qui se mettaient en erreur sur le bus en version 4.1 marchaient sur la version 4.0 que j'utilisais dans ma phase de test. La différence se fait donc non pas entre la 3 et la 4 mais bien entre la 4.0 et la 4.1


Christophe DENEUX wrote
Certes cela consomme un peu plus de mémoire, mais aujourd'hui ce n'est pas un problème, vu les avantages d'indépendance. D'un autre coté, on n'aurait pu etre un peu plus malin pour ne pas définir Saxon via une propriété sur la ligne de commande mais plutôt via le système de SPI Java.
Effectivement, aujourd'hui avec des serveurs multi processeurs, multi coeurs, on a ce qu'il faut en terme de puissance.
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

theirman
Nouvelle petite question au sujet du composant BC-SOAP :

Il expose de manière ostentatoire la liste des services disponibles sur la page http://url_de_la_machine:8084/petals/services/listServices/  J'ai vu dans le JBI.xml du composant qu'il y'a un port sécurisé 8083. Mais comment déployer les services sur le BC-SOAP de manière à ce qu'il utilise de préférence ce port sécurisé ?

J'ai essayé d'atteindre, via mon navigateur, cette page (localhost:8083) mais elle ne passe pas !!
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

Christophe DENEUX
Administrator
This post has NOT been accepted by the mailing list yet.
C'est le port par défaut pour une exposition SSL des services. Voir la documentation du BC SOAP pour voir comment activer tout ça.
Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

theirman
OK, j'ai vu ce qu'il faut configurer. J'ai également trouvé où se trouve le répertoire HTTPS contenant les certificats HTTPS de la bus PETALS, par contre, dans la config ci-dessous, je ne connais pas les passwords des fichiers keystore.
(désolé, je ne suis pas habitué à utiliser des certificats et des clés SSL  )


	<!-- HTTPS SUPPORT -->
        <soap:https-enabled xmlns:soap="http://petals.ow2.org/components/soap/version-4" xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5" xmlns:jbi="http://java.sun.com/xml/ns/jbi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">true</soap:https-enabled>
        <soap:https-port xmlns:soap="http://petals.ow2.org/components/soap/version-4" xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5" xmlns:jbi="http://java.sun.com/xml/ns/jbi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">8083</soap:https-port>
        <soap:https-keystore-type xmlns:soap="http://petals.ow2.org/components/soap/version-4" xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5" xmlns:jbi="http://java.sun.com/xml/ns/jbi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">JKS</soap:https-keystore-type>
        <soap:https-keystore-file xmlns:soap="http://petals.ow2.org/components/soap/version-4" xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5" xmlns:jbi="http://java.sun.com/xml/ns/jbi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">/apps/petals/petals-esb-4.1/https/keystore-srv.jks</soap:https-keystore-file>
        <soap:https-keystore-password xmlns:soap="http://petals.ow2.org/components/soap/version-4" xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5" xmlns:jbi="http://java.sun.com/xml/ns/jbi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">????????</soap:https-keystore-password>
        <soap:https-key-password xmlns:soap="http://petals.ow2.org/components/soap/version-4" xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5" xmlns:jbi="http://java.sun.com/xml/ns/jbi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">????????</soap:https-key-password>
        <soap:https-truststore-type xmlns:soap="http://petals.ow2.org/components/soap/version-4" xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5" xmlns:jbi="http://java.sun.com/xml/ns/jbi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">JKS</soap:https-truststore-type>
        <soap:https-truststore-file xmlns:soap="http://petals.ow2.org/components/soap/version-4" xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5" xmlns:jbi="http://java.sun.com/xml/ns/jbi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">/apps/petals/petals-esb-4.1/https/keystore-srv-ssl.jks</soap:https-truststore-file>
        <soap:https-truststore-password xmlns:soap="http://petals.ow2.org/components/soap/version-4" xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5" xmlns:jbi="http://java.sun.com/xml/ns/jbi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">????????</soap:https-truststore-password>
Reply | Threaded
Open this post in threaded view
|

Re: Déploiement des composants de petals esb 4.1

Christophe DENEUX
Administrator
This post has NOT been accepted by the mailing list yet.
Stp, peux-tu créer une autre discussion à propos de SSL pour ne pas mélanger les sujets ?

Merci
Christophe DENEUX
Petals ESB Architect
Linagora
Twitter: @ChrisDENEUX