I'm not sure if it does work correctly.  I saw that there were two bpel
examples so I tried that one as well.
 
Here's the messages when servicemix starts up:

Loading Apache ServiceMix from file: servicemix.xml
WARN - MulticastDiscoveryAgent.start(206) | brokerName not set
INFO - ComponentMBeanImpl.init(184) | Initializing component:
#SubscriptionManager#
INFO - DeploymentService.buildState(683) | Restoring service
assemblies
INFO - JBIContainer.init(508) | ServiceMix JBI Container
(http://servicemix.org/) name: ServiceMix running version: 3.0-
SNAPSHOT
 
and then I go over to the client and run ant
run:
     [echo] Running exsample client
     [java] Connecting to JMS server.
     [java] Sending request.
     [java] javax.jms.JMSException:
EDU.oswego.cs.dl.util.concurrent.TimeoutException
     [java]     at
org.logicblaze.lingo.jms.impl.MultiplexingRequestor.createJMSException(MultiplexingRequestor.java:155
)
     [java]     at
org.logicblaze.lingo.jms.impl.MultiplexingRequestor.request(MultiplexingRequestor.java:107)
     [java]     at
org.logicblaze.lingo.jms.impl.MultiplexingRequestor.request(MultiplexingRequestor.java:82)
     [java]     at JMSClient.run(JMSClient.java:102)
     [java]     at JMSClient.main(JMSClient.java:59)
     [java] Closing.
 
so it looks like its not connecting to the service correctly.
 
Brian
>>> [EMAIL PROTECTED] 03/30/06 3:21 PM >>>

Have you tried the bpel-bpe demo that ships with the distribution ?
It works fine.  The bpe component has some limitations but works fine.
Btw, the 3.0M1 has never been release officially...

Some people have succesfully deployed PXE in ServiceMix, but they had
to hack on PXE dependencies and installer...
I hope someone will soon have time to rework on this integration.

Cheers,
Guillaume Nodet

On 3/31/06, Luan La <[EMAIL PROTECTED]> wrote:
> I think the PXE Component that is bundled with servicemix has a bug
with the
> service unit deployment. It simply doesn't register the endpoint with
the
> container. I have successfully run the examples in PXE standalone.
However,
> the current PXE release has a problem with the JBI component, so
servicemix
> doesn't even deploy it. I am running around in circles chasing my
tail
> really...
>
> Does anyone know what is the status of service-bpe? It isn't bundled
with
> the 3.0 M1 release. I have successfully built it from trunk but it
seems to
> have the same problem with PXE. i.e, the service-bpe component is
deployed
> successfully in the container, but it doesn't deploy the service
units
> properly, and hence an endpoint is never registered.
>
> Anyone else know about the status of Apache ode? The SVN repository
shows
> nothing in trunk or branches. There is something in scratched
however...hmmm
>
> Keep this discussion going. There's not a lot out there as far as
working
> open source BPEL Engines.
>
> Cheers,
> Luan
>
> -----Original Message-----
> From: Brian Rook [mailto:[EMAIL PROTECTED]
> Sent: Friday, 31 March 2006 7:30 AM
> To: [email protected]
> Subject: Re: BPEL Example
>
>
> I'm having the same problem as well.
>
> On start, I get a message that says
> WARN - MulticastDiscoveryAgent.start(206) | brokerName not set
>
> then when I run the ant task for the client I get this:
> WARN - DeliveryChannelImpl.createExchangeFactory(196) | Could not
find
> destination endpoint for myComponent service({uri
> :fivesight.com/examples/AsyncProcessJBI}ProcessSVC) with
endpointName
> ProcessPORT
> WARN - Broker.resolveAddress(355) | ServiceName
> ({uri:fivesight.com/examples/AsyncProcessJBI}ProcessSVC) specified
for
> r
> outing, but can't find it registered
>
> Brian
>
> >>> [EMAIL PROTECTED] 03/28/06 3:25 PM >>>
>
> I have seen the same problem, but I have no idea where it comes from
> at the moment...
>
> Cheers,
> Guillaume Nodet
>
> On 3/29/06, Luan La <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > Just wondering if anyone has successfully run the BPEL example?
For
> some
> > reason I always get one of two exceptions:
> >
> > Thanks,
> > Luan
> >
> > 1.
> >
> > javax.jbi.messaging.MessagingException: Failed to resolve
endpoint:
> > org.apache.servicemix.jbi.NoServiceAvailableException: Cannot find
> an
> > instance of the service:
> > {uri:fivesight.com/examples/AsyncProcessJBI}ProcessSVC
> >         at
> >
org.apache.servicemix.jbi.nmr.Broker.resolveAddress(Broker.java:358)
> >         at
> >
>
org.apache.servicemix.jbi.nmr.Broker.sendExchangePacket(Broker.java:278)
> >         at
> >
>
org.apache.servicemix.jbi.container.JBIContainer.sendExchange(JBIContainer.j
> > ava:586)
> >         at
> >
>
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChann
> > elImpl.java:346)
> >         at
> >
>
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.sendSync(DeliveryCha
> > nnelImpl.java:420)
> >         at
> >
>
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.sendSync(DeliveryCha
> > nnelImpl.java:397)
> >         at
> >
>
org.apache.servicemix.components.jms.JmsServiceComponent.onMessage(JmsServic
> > eComponent.java:213)
> >         at
> >
>
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer
> > .java:716)
> >         at
> >
>
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor
> > .java:93)
> >         at
> >
>
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.
> > java:146)
> >         at
> >
>
org.apache.activemq.thread.SimpleTaskRunner.runTask(SimpleTaskRunner.java:11
> > 0)
> >         at
> >
>
org.apache.activemq.thread.SimpleTaskRunner.access$100(SimpleTaskRunner.java
> > :25)
> >         at
> >
>
org.apache.activemq.thread.SimpleTaskRunner$1.run(SimpleTaskRunner.java:43)
> >         at
> >
>
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> > Task(ThreadPoolExecutor.java:643)
> >         at
> >
>
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> > (ThreadPoolExecutor.java:668)
> >         at java.lang.Thread.run(Thread.java:595)
> > Caused by: org.apache.servicemix.jbi.NoServiceAvailableException:
> Cannot
> > find an instance of the service:
> > {uri:fivesight.com/examples/AsyncProcessJBI}ProcessSVC
> >         at
> >
>
org.apache.servicemix.jbi.resolver.ServiceAndEndpointNameResolver.createServ
> > iceUnavailableException(ServiceAndEndpointNameResolver.java:75)
> >         at
> >
>
org.apache.servicemix.jbi.resolver.EndpointResolverSupport.resolveEndpoint(E
> > ndpointResolverSupport.java:39)
> >         at
> >
org.apache.servicemix.jbi.nmr.Broker.resolveAddress(Broker.java:355)
> >         ... 15 more
> >
> > or
> >
> > 2.
> >
> > ERROR - AutoDeploymentService.updateArchive(258) | Failed to
update
> Service
> > Assembly: AsyncProcessSA
> > javax.jbi.management.DeploymentException: PXE Deployment Error.
> >         at
com.fs.pxe.jbi.PxeSUManager.deploy(PxeSUManager.java:124)
> >         at
> >
>
org.apache.servicemix.jbi.framework.DeploymentService.deployServiceUnit(Depl
> > oymentService.java:403)
> >         at
> >
>
org.apache.servicemix.jbi.framework.DeploymentService.deploy(DeploymentServi
> > ce.java:141)
> >         at
> >
>
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(Auto
> > DeploymentService.java:245)
> >         at
> >
>
org.apache.servicemix.jbi.framework.AutoDeploymentService$2.run(AutoDeployme
> > ntService.java:517)
> >         at
> >
>
org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:291)
> >         at
> > EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
> Source)
> >         at java.lang.Thread.run(Thread.java:595)
> > Caused by: javax.management.RuntimeMBeanException:
RuntimeException
> thrown
> > by the invoke method of the Dynamic MBean
> >         at
> >
>
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:
> > 227)
> >         at
> > com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
> >         at
> >
>
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanSer
> > verInterceptor.java:815)
> >         at
> >
>
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
> >         at
> >
>
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHa
> > ndler.java:201)
> >         at $Proxy4.deploySystem(Unknown Source)
> >         at
com.fs.pxe.jbi.PxeSUManager.deploy(PxeSUManager.java:121)
> >         ... 7 more
> > Caused by: java.lang.NullPointerException
> >         at
> >
>
edu.emory.mathcs.backport.java.util.Collections$ReverseComparator.compare(Co
> > llections.java:772)
> >         at
> >
>
edu.emory.mathcs.backport.java.util.TreeMap.compare(TreeMap.java:873)
> >         at
> edu.emory.mathcs.backport.java.util.TreeMap.put(TreeMap.java:98)
> >         at
> edu.emory.mathcs.backport.java.util.TreeSet.add(TreeSet.java:143)
> >         at
> >
>
com.fs.utils.fs.TempFileManager._registerTemporaryFile(TempFileManager.java:
> > 191)
> >         at
> >
>
com.fs.utils.fs.TempFileManager.registerTemporaryFile(TempFileManager.java:1
> > 87)
> >         at
> >
>
com.fs.utils.fs.TempFileManager.getTemporaryFile(TempFileManager.java:159)
> >         at
> >
>
com.fs.utils.fs.TempFileManager.getTemporaryDirectory(TempFileManager.java:1
> > 77)
> >         at
> >
>
com.fs.utils.fs.TempFileManager.getTemporaryDirectory(TempFileManager.java:1
> > 73)
> >         at
> >
>
com.fs.pxe.sfwk.impl.DomainNodeImpl.expandSAR(DomainNodeImpl.java:1301)
> >         at
> >
com.fs.pxe.sfwk.impl.DomainNodeImpl.deploy(DomainNodeImpl.java:1045)
> >         at
> >
>
com.fs.pxe.sfwk.impl.DomainAdminMBeanImpl.deploySystem(DomainAdminMBeanImpl.
> > java:65)
> >         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:585)
> >         at
> >
>
com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.jav
> > a:414)
> >         at
> javax.management.StandardMBean.invoke(StandardMBean.java:323)
> >         at
> >
>
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:
> > 213)
> >         ... 13 more
> >
> >
> >
> >
>
>
>

Reply via email to