Well, a component has already activated this endpoint.
See the error:
 service {urn:imocha:soa:login}LoginService and endpoint loginBroker

If both your bpel are the same, they will try to activate the same endpoints
when the bpel has an receive action.  You need to specify two different
service names
or endpoint names.

On 8/7/06, azwan <[EMAIL PROTECTED]> wrote:


Hi,
I've tried that but got error during startup.  Any idea?

<sm:activationSpec>
                                <sm:component>
                                        <bpws:component
bpelResource="classpath:processA.bpel" />
                                </sm:component>
                        </sm:activationSpec>

                        <sm:activationSpec>
                                <sm:component>
                                        <bpws:component
bpelResource="classpath:ProcessB.bpel" />
                                </sm:component>
                        </sm:activationSpec>

Caught: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'jbi' defined in file
[/home/azwan/tmp/servicemix-3.0-M2/apache-servicemix-3.0-M2-incubating
/examples/mytest/mytest/epf/servicemix.xml]:
Invocation of init method failed; nested exception is
javax.jbi.JBIException: An internal endpoint for service
{urn:imocha:soa:login}LoginService and endpoint loginBroker is already
registered
org.springframework.beans.factory.BeanCreationException: Error creating
bean
with name 'jbi' defined in file
[/home/azwan/tmp/servicemix-3.0-M2/apache-servicemix-3.0-M2-incubating
/examples/mytest/mytest/epf/servicemix.xml]:
Invocation of init method failed; nested exception is
javax.jbi.JBIException: An internal endpoint for service
{urn:imocha:soa:login}LoginService and endpoint loginBroker is already
registered
Caused by: javax.jbi.JBIException: An internal endpoint for service
{urn:imocha:soa:processB}ProcessBService and endpoint processBBroker is
already registered
        at

org.apache.servicemix.jbi.framework.EndpointRegistry.registerInternalEndpoint
(EndpointRegistry.java:157)
        at
org.apache.servicemix.jbi.framework.Registry.activateEndpoint(
Registry.java:179)
        at
org.apache.servicemix.jbi.framework.ComponentContextImpl.activateEndpoint(
ComponentContextImpl.java:135)
        at
org.apache.servicemix.bpe.BPEEndpoint.activate(BPEEndpoint.java:74)
        at
org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:49)
        at
org.apache.servicemix.bpe.BPESpringComponent$LifeCycle.doStart(
BPESpringComponent.java:61)
        at
org.apache.servicemix.common.AsyncBaseLifeCycle.start(
AsyncBaseLifeCycle.java:198)
        at
org.apache.servicemix.jbi.framework.ComponentMBeanImpl.doStart(
ComponentMBeanImpl.java:285)
        at

org.apache.servicemix.jbi.framework.ComponentRegistry.setInitialRunningStateFromStart
(ComponentRegistry.java:155)
        at
org.apache.servicemix.jbi.framework.ComponentRegistry.start(
ComponentRegistry.java:72)

--
View this message in context:
http://www.nabble.com/2-bpel-component-in-1-servicemix-instance-tf2061589.html#a5680811
Sent from the ServiceMix - User forum at Nabble.com.




--
Cheers,
Guillaume Nodet

Reply via email to