14 Replies Latest reply on Dec 18, 2013 4:49 AM by jonathan.moore

Fuse Service Works beta is now available

alansantos Oct 28, 2013 12:07 PM

Hey everyone - I'm very pleased to note that beta release of Red Hat JBoss Fuse Service Works is now available. This forum will be monitored by the product team for discussion, questions and feedback about the technology and documentation.

What is Fuse Service Works? Fuse Service Works builds on JBoss Fuse technology to offer a comprehensive service oriented development platform. Beyond out-of-the box support for enterprise messaging and integration patterns with Fuse, developers can also build modular, component based services using Java, BPEL, BPMN2, Business Rules or Apache Camel; Orchestrate Services; Manage service delivery lifecycle across teams with a workflow enabled registry; and finally create and manage service policies and service level agreements with business transaction monitoring.

It does this using 100% open source JBoss and Apache technologies - Apache Camel provides core integration and transformation capabilities; JBoss Switchyard provides the service delivery framework; Governance is provided by JBoss Overlord S-RAMP, DTGov and RTGov. Though the beta only supports HornetQ as a messaging provider the GA will support both HornetQ and JBoss Fuse A-MQ. JBoss Developer Studio integration stack provides eclipse based tools for developers and is conveniently packaged as an update.

The beta download is available on the Red Hat customer portal and here on the JBoss.org website . Be sure to check out the website link for a few brief, introductory videos and installation instructions to get you started. Beta documentation is also available on the customer portal and will be updated throughout the beta program.

Red Hat global support is available for existing customers through the usual channels, including the customer support portal. Everyone is encouraged to post here with questions and comments.

The beta will remain available for download until general availability later this year. Once we've released the GA it will be available here and on the Red Hat customer portal.

1. Re: Fuse Service Works beta is now available

burmanm Oct 31, 2013 11:42 AM (in response to alansantos)

Hi,

Correct link to the documentation seems to be:

https://access.redhat.com/site/documentation/Red_Hat_JBoss_Fuse_Service_Works/

Aside from that, I seriously hope that you will create another beta-candidate at some point. Currently, this release is ridden with bugs. Installer's bugzilla is pretty telling, it's next to impossible to install the beta correctly (and I certainly haven't succeeded in that, yet, and I've reported few bugs, but there seems to be so many that I can never get past some of those). Also, the server seems to die OutOfMemory errors when it's idling over the night (without anything deployed), as well as some components throwing huge amount of stacktraces to the logs (Infinispan, RTGov etc). Maybe these are something the installer doesn't configure properly, hard to tell.

I understand this is a beta and testing is the whole idea, but to get more feedback, more betas should be released with stuff that's been fixed meanwhile. Also, having this community forum shown up in the welcome list would be an ideal start to actually find it. Regarding documentation, how does one install FSW Forge-plugins? They're available on the Maven repo, but the documentation doesn't say anything and the SwitchYard Forge-plugins are old versions (or should I create my own installer by using the community version as a template and then apply these newer jars?).

This post sounds negative, but all I'd want is that the first 6.0.0 would actually be useful, since the product has great ideas. And not that we have to wait until some point releases or 6.1.0 to deploy something useful.
Actions
2. Re: Fuse Service Works beta is now available

jmiguel77 Oct 31, 2013 11:50 AM (in response to alansantos)

hi

i downloaded and installed; in the first run i find this error:

10:41:56,543 ERROR [org.overlord.dtgov.jbpm.util.ApplicationScopedProducer] (ServerService Thread Pool -- 59) Could not find or read the SRAMPPackage
10:41:56,544 ERROR [org.overlord.dtgov.jbpm.util.ApplicationScopedProducer] (ServerService Thread Pool -- 59) Cannot find KieModule: org.overlord.dtgov:dtgov-workflows:1.0.1.Final-redhat-4: java.lang.RuntimeException: Cannot find KieModule: org.overlord.dtgov:dtgov-workflows:1.0.1.Final-redhat-4
at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:84) [drools-compiler-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.overlord.dtgov.jbpm.util.ApplicationScopedProducer.getKieBase(ApplicationScopedProducer.java:116) [classes:]
at org.overlord.dtgov.jbpm.util.ApplicationScopedProducer.produceEnvironment(ApplicationScopedProducer.java:86) [classes:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]
at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstance(MethodInjectionPoint.java:137) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.bean.ProducerMethod$ProducerMethodProducer.produce(ProducerMethod.java:136) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.bean.AbstractProducerBean$AbstractProducer.produce(AbstractProducerBean.java:319) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:307) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:68) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:608) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:635) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:107) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jbpm.runtime.manager.impl.cdi.RuntimeManagerProducer.newSingletonRuntimeManager(RuntimeManagerProducer.java:66) [jbpm-runtime-manager-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]
at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstance(MethodInjectionPoint.java:137) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.bean.ProducerMethod$ProducerMethodProducer.produce(ProducerMethod.java:136) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.bean.AbstractProducerBean$AbstractProducer.produce(AbstractProducerBean.java:319) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:307) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:68) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:608) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:674) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:134) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:763) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:772) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.bean.SessionBean$SessionBeanInjectionTarget$1.proceed(SessionBean.java:179) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.bean.SessionBean$SessionBeanInjectionTarget.inject(SessionBean.java:176) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.as.weld.injection.WeldEEInjection.inject(WeldEEInjection.java:78) [jboss-as-weld-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:60) [jboss-as-weld-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:115) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:104) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ejb3.tx.BMTInterceptor.processInvocation(BMTInterceptor.java:56) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
Actions
3. Re: Fuse Service Works beta is now available

kconner Oct 31, 2013 12:25 PM (in response to burmanm)

We haven't come across any OOM errors in our testing, could you please send in a log and a heap dump if possible?

You should be able to generate a heap dump by adding '-XX:+HeapDumpOnOutOfMemoryError' to the options within bin/standalone.conf.

Thanks very much
Actions
4. Re: Fuse Service Works beta is now available

kconner Oct 31, 2013 12:34 PM (in response to jmiguel77)

There is a workflow process that is associated with the Design Time Governance capabilities, allowing you to control the lifecycle of the artifacts that are uploaded, however it is not installed by default. The exception, the handling of which has been improved for final, is indicating that the workflow has not yet been installed and is being generated by the jBPM codebase.

We ship an example workflow but do not install it by default as we believe that customers will create their own version to match their productisation processes. Take a look at the example under jboss-eap-6.1/quickstarts/overlord/dtgov/dtgov-demos-switchyard and follow the directions in the README.asciidoc file, this will guide you through the installation process.
Actions
5. Re: Fuse Service Works beta is now available

kconner Oct 31, 2013 5:16 PM (in response to kconner)

Sorry, the workflow you are looking for is actually located under jboss-eap-6.1/data
Actions
6. Re: Fuse Service Works beta is now available

jmiguel77 Oct 31, 2013 7:25 PM (in response to kconner)

hi
i tried to deploy the dtgov-demos-switchyard with this command:

mvn -Pdemo -Dsramp.auth.username=admin -Dsramp.auth.password=[passwd] clean deploy

but i get an error everytime:

Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5-redhat-1:deploy (default-deploy) on project dtgov-demos-switchyard: Failed to deploy artifacts: Could not transfer artifact org.overlord.dtgov.demos.switchyard:dtgov-demos-switchyard:jar:1.0.1.Final-redhat-4 from/to local-sramp-repo (sramp://localhost:8080/s-ramp-server/?artifactType=SwitchYardApplication): Failed to connect to the S-RAMP repository. Authentication failure while attempting to access the S-RAMP repository

but i am sure the credentials are the same ones that appear in the file overlord-idp-users.properties
Actions
7. Re: Fuse Service Works beta is now available

kconner Oct 31, 2013 8:28 PM (in response to jmiguel77)

Try adding the following section to your settings.xml file, substituting your username/password.

<servers>
    <server>
      <id>local-sramp-repo</id>
      <username>XXX</username>
      <password>YYY</password>
    </server>
</servers>
Actions
8. Re: Fuse Service Works beta is now available

alansantos Nov 1, 2013 9:51 AM (in response to burmanm)

Michael, Jose - Thanks very much for the feedback.

First we've updated the beta release notes to note the missing workflow problem, the supported databases for beta and a few others. We don't believe there are any issues that Red Hat traditionally considers to be sev - 0, i.e. corrupt data, bugs affecting core capabilities w/out a workaround, etc..

There are no plans for an additional beta release, but let's see how things move ahead and what sort of issues are uncovered. If we can reproduce significant issues - like your OOM - we're much more likely to have additional builds or patches. To be clear, please don't take that as a promise for either of those during beta; it's only a promise that we're willing to re-evaluate plans as we move ahead based on user feedback and we understand that a beta is only useful if it's usable.
Actions
9. Re: Fuse Service Works beta is now available

jmiguel77 Nov 1, 2013 3:33 PM (in response to kconner)

i added the server to my settings and the quickstart is able to deploy, but in the deployment process it gives me this error:

13:22:36,758 INFO [org.overlord.sramp.governance.QueryExecutor] (EJB default - 2) Starting workflow overlord.demo.SimpleReleaseProcess for artifact 453ab586-9a7c-4500-a5ba-add099d3940a
13:22:36,788 WARN [org.drools.persistence.SingleSessionCommandService] (EJB default - 2) Could not commit session: java.lang.IllegalArgumentException: Unknown process ID: overlord.demo.SimpleReleaseProcess
...
...
...
Caused by: java.lang.IllegalArgumentException: Unknown process ID: overlord.demo.SimpleReleaseProcess
at org.jbpm.process.instance.ProcessRuntimeImpl.createProcessInstance(ProcessRuntimeImpl.java:217) [jbpm-flow-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.jbpm.process.instance.ProcessRuntimeImpl.createProcessInstance(ProcessRuntimeImpl.java:178) [jbpm-flow-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:168) [jbpm-flow-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.drools.core.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1577) [drools-core-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.drools.core.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:343) [drools-core-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.drools.core.command.runtime.process.StartProcessCommand.execute(StartProcessCommand.java:121) [drools-core-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.drools.core.command.runtime.process.StartProcessCommand.execute(StartProcessCommand.java:40) [drools-core-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.drools.core.command.impl.DefaultCommandService.execute(DefaultCommandService.java:36) [drools-core-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.drools.core.command.impl.AbstractInterceptor.executeNext(AbstractInterceptor.java:41) [drools-core-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.drools.persistence.SingleSessionCommandService$TransactionInterceptor.execute(SingleSessionCommandService.java:564) [drools-persistence-jpa-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.drools.core.command.impl.AbstractInterceptor.executeNext(AbstractInterceptor.java:41) [drools-core-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.drools.persistence.jpa.OptimisticLockRetryInterceptor.execute(OptimisticLockRetryInterceptor.java:71) [drools-persistence-jpa-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.drools.persistence.SingleSessionCommandService.execute(SingleSessionCommandService.java:388) [drools-persistence-jpa-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.drools.core.command.impl.CommandBasedStatefulKnowledgeSession.startProcess(CommandBasedStatefulKnowledgeSession.java:230) [drools-core-6.0.0-redhat-4.jar:6.0.0-redhat-4]
at org.overlord.dtgov.jbpm.ejb.ProcessBean.startProcess(ProcessBean.java:81) [classes:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:374) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:129) [jboss-as-weld-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:137) [jboss-as-weld-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:374) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.concurrency.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:104) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:104) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
... 91 more
Actions
10. Re: Fuse Service Works beta is now available

jcordes Nov 2, 2013 4:42 AM (in response to burmanm)

Hi Michael,

The link has changed because of re-branding. I would be quite interested in the issues you have found, I have seen [SWITCHYARD-231] SmooksExceptions should be checked - JBoss Issue Tracker so far.

Where did you report the other issues? Red Hat's bugzilla (https://bugzilla.redhat.com/) would be the preferred ticket system. What method did you choose for installation? I'm on a FSW project ATM and therefore would like to share my experience with others.

About the plugins for Forge we have to be aware that Forge is a community project and therefore you have to rely on the community to keep up-to-date, however it could be worth to mention it in the Red Hat documentation (as we do with Arquillian, for example)

Kind regards,

Jochen
Actions
11. Re: Fuse Service Works beta is now available

jonathan.moore Dec 16, 2013 9:15 AM (in response to alansantos)

Falling at an early hurdle.

The instructions and the video at http://www.jboss.org/products/fsw both refer to an update site at https://devstudio.jboss.com/updates/7.0-development/integration-stack/ and say to select "JBoss SOA Development".

There is no "JBoss SOA Development" category listed for that update site (there are no categories at all), and I've no idea which, if any, of the components listed are the ones I need, or if I should be using a different update site altogether. I've tried a few variations of URL without any success, and Google's not helping either.

Can you please clarify what I need to do to install the developer studio plugins for FSW? (And preferably update the published documentation.)

(All components freshly downloaded on 16/12/2013).
Actions
12. Re: Fuse Service Works beta is now available

rcernich Dec 16, 2013 9:19 AM (in response to jonathan.moore)

I think the category has since been renamed to: JBoss Integration and SOA Development
Actions
13. Re: Fuse Service Works beta is now available

jonathan.moore Dec 16, 2013 10:19 AM (in response to rcernich)

Thanks, but where is it? I can't find any plugins or categories with 'Integration' or 'SOA' in the name at all.
Actions
14. Re: Fuse Service Works beta is now available

jonathan.moore Dec 18, 2013 4:49 AM (in response to jonathan.moore)

The content on the update site has changed over the last couple of days and the SOA and Integration category is now there. If someone fixed it in response to this thread, then thank you.
Actions

Go to original post