[
https://issues.apache.org/activemq/browse/SM-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38653
]
Jamie Goodyear commented on SM-564:
-----------------------------------
Hi All,
Reviewing this report it appears that the SA Deployment error with
whitespaces in
jbi.xml <artifacts-zip> value is already resolved but the JIRA entry has not
been
updated to reflect change of status.
I tested this issue using the loan-broker example by adding leading
whitespaces to
Artifacts-zip tag, the starting servicemix without recieving the described
error. Could
we mark this issue as resolved-fixed?
Note: used servicemix-core-3.2-incubating-SNAPSHOT jar with 3.1 kit -- added
extra
logging to jar to see that whitespaces in name were picked up.
Cheers,
Jamie.
For testing this issue the jbi file
INSTALL_DIR\examples\loan-broker\src\sa\META-INF\jbi.xml
was modified to the following:
<jbi xmlns="http://java.sun.com/xml/ns/jbi"; version="1.0">
<service-assembly>
<identification>
<name>loanbroker</name>
<description>LoanBroker Service Assembly</description>
</identification>
<service-unit>
<identification>
<name>loanbroker</name>
<description>LoanBroker Service Unit</description>
</identification>
<target>
<artifacts-zip> loanbroker-su.zip</artifacts-zip>
<component-name>servicemix-lwcontainer</component-name>
</target>
</service-unit>
</service-assembly>
</jbi>
ServiceMix Startup Logging:
C:\Apache\kit\examples\loan-broker>C:\Apache\kit\bin\servicemix servicemix.xml
Starting Apache ServiceMix ESB: 3.2-incubating-SNAPSHOT
Loading Apache ServiceMix from file: servicemix.xml
INFO - JBIContainer - ServiceMix 3.2-incubating-SNAPSHOT JBI
Container
(ServiceMix) is starting
INFO - JBIContainer - For help or more informations please
see:
http://incubator.apache.org/servicemix/
INFO - ConnectorServerFactoryBean - JMX connector available at:
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
INFO - ComponentMBeanImpl - Initializing component:
#SubscriptionManager#
INFO - DeploymentService - Restoring service assemblies
INFO - ComponentMBeanImpl - Setting running state for Component:
servicemix-lwcontainer
to Started
INFO - ComponentMBeanImpl - Initializing component:
servicemix-lwcontainer
INFO - ServiceAssemblyLifeCycle - Starting service assembly: loanbroker
INFO - ServiceUnitLifeCycle - Initializing service unit: loanbroker
INFO - ServiceUnitLifeCycle - Starting service unit: loanbroker
INFO - ComponentMBeanImpl - Initializing component:
loanBrokerJmsBinding
INFO - ComponentMBeanImpl - Starting component:
loanBrokerJmsBinding
INFO - ComponentMBeanImpl - Initializing component: loanBroker
INFO - ComponentMBeanImpl - Starting component: loanBroker
INFO - ComponentMBeanImpl - Initializing component: creditAgency
INFO - ComponentMBeanImpl - Starting component: creditAgency
INFO - ComponentMBeanImpl - Initializing component: lenderGateway
INFO - ComponentMBeanImpl - Starting component: lenderGateway
INFO - ComponentMBeanImpl - Initializing component: bank1
INFO - ComponentMBeanImpl - Starting component: bank1
INFO - ComponentMBeanImpl - Initializing component: bank2
INFO - ComponentMBeanImpl - Starting component: bank2
INFO - ComponentMBeanImpl - Initializing component: bank3
INFO - ComponentMBeanImpl - Starting component: bank3
INFO - ComponentMBeanImpl - Initializing component: bank4
INFO - ComponentMBeanImpl - Starting component: bank4
INFO - ComponentMBeanImpl - Initializing component: bank5
INFO - ComponentMBeanImpl - Starting component: bank5
INFO - JBIContainer - ServiceMix JBI Container (ServiceMix)
started
> SA deployment error with whitespace in jbi.xml <artifacts-zip> value
> --------------------------------------------------------------------
>
> Key: SM-564
> URL: https://issues.apache.org/activemq/browse/SM-564
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: 3.0-M2
> Environment: Apache ServiceMix ESB: 3.0-M2-incubating
> windows SP2
> Reporter: fred smith
> Priority: Minor
>
> I reformatted my Service Assembly's jbi.xml file and the SA failed to deploy.
> Logging shows the following error:
> java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
> <jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message";
> version="1.0">
> <jbi-task-result>
> <frmwk-task-result>
> <frmwk-task-result-details>
> <task-result-details>
> <task-id>deploy</task-id>
> <task-result>FAILED</task-result>
> <message-type>ERROR</message-type>
> <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Artifact gestalt-jbi-pingpong-ws-lw-su-HEAD.zip not found
> for service unit pingpong-lw-su</loc-message>
> </msg-loc-info>
> </task-status-msg>
> </task-result-details>
> </frmwk-task-result-details>
> </frmwk-task-result>
> </jbi-task-result>
> </jbi-task>
> The problem can be recreated with whitespace after the <artifacts-zip> tag
> value (shown below). If the whitespace is removed then the SA is deployed
> correctly.
> ===== incorrect =====
> <service-unit>
> <identification>
> <name>pingpong-lw-su</name>
> <description>Contains the binding for the lwcontainer SE</description>
> </identification>
> <target>
> <artifacts-zip> gestalt-jbi-pingpong-ws-lw-su-HEAD.zip</artifacts-zip>
> <component-name>servicemix-lwcontainer</component-name>
> </target>
> </service-unit>
> ===== correct =====
> <artifacts-zip>gestalt-jbi-pingpong-ws-lw-su-HEAD.zip</artifacts-zip>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
