You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Waxter <ml...@intecna.es> on 2007/02/20 12:35:01 UTC
Re: ServiceMix+Jboss - Unable to run BPEL project created using
netbeans
I have installed both components (com.sun.httpsoapbc and com.sun.bpelse) in
Servicemix and deployed SynchronousSample Application:
java version "1.5.0_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b03)
Java HotSpot(TM) Client VM (build 1.5.0_09-b03, mixed mode)
Starting Apache ServiceMix ESB: 3.1-incubating
Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
INFO - ConnectorServerFactoryBean - JMX connector available at:
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
INFO - JBIContainer - ServiceMix 3.1-incubating JBI
Container (ServiceMix) is starting
INFO - JBIContainer - For help or more informations
please see: http://incubator.apache.org/servicemix/
INFO - ComponentMBeanImpl - Initializing component:
#SubscriptionManager#
20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEBootstrap init
INFO: Calling init method
20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
setDB_JNDIName
INFO: setting jndiname jdbc/__default
20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
setDB_Type
INFO: setting type 4
20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
setDB_URL
INFO: setting dburl jdbc:derby://localhost:1527/derbyDB
20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
setDB_Password
INFO: setting password pass2
20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
setDB_UserName
INFO: setting user usr2
20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
setPersistenceEnabled
INFO: setting PersistenceEnabled flag false
20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEBootstrap init
INFO: init method has been called
20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEBootstrap
getExtensionMBeanName
INFO: retrieving installation configuration mbean
20-feb-2007 12:24:00
com.sun.jbi.httpsoapbc.bootstrap.HttpSoapBindingBootstrap init
INFO: Registered MBean
org.apache.servicemix:ContainerName=ServiceMix,Type=Component,Name=com.sun.httpsoapbc-1.0-2,SubType=BootstrapExtension
INFO - DeploymentService - Restoring service assemblies
INFO - ComponentMBeanImpl - Setting running state for
Component: com.sun.bpelse-1.0-2 to Started
INFO - ComponentMBeanImpl - Initializing component:
com.sun.bpelse-1.0-2
20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
INFO: Started BPEL service engine in-out thread
20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
INFO: Started BPEL service engine in-out thread
20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
INFO: Started BPEL service engine in-out thread
20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
INFO: Started BPEL service engine in-out thread
20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
INFO: Started BPEL service engine in-out thread
20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
INFO: Started BPEL service engine in-out thread
20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
INFO: Started BPEL service engine in-out thread
20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
INFO: Started BPEL service engine in-out thread
20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
INFO: Started BPEL service engine in-out thread
20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSELifeCycle start
INFO: BPEL service engine started
20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
INFO: Started BPEL service engine in-out thread
INFO - ComponentMBeanImpl - Setting running state for
Component: com.sun.httpsoapbc-1.0-2 to Started
INFO - ComponentMBeanImpl - Initializing component:
com.sun.httpsoapbc-1.0-2
20-feb-2007 12:24:03 com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle start
INFO: HTTP SOAP binding started.
20-feb-2007 12:24:03 com.sun.jbi.httpsoapbc.OutboundReceiver run
INFO: Started receiver
INFO - ComponentMBeanImpl - Setting running state for
Component: JavaEEServiceEngine to Shutdown
INFO - ServiceAssemblyLifeCycle - Starting service assembly:
SynchronousSample1Application
INFO - ServiceUnitLifeCycle - Initializing service unit:
SynchronousSample1Application-SynchronousSample1
20-feb-2007 12:24:03 com.sun.jbi.engine.bpel.BPELSEDeployer init
INFO: Starting BPELSE deploy process
20-feb-2007 12:24:05 com.sun.jbi.engine.bpel.EngineHelper deploy
INFO: Loaded bpel processes to engine
20-feb-2007 12:24:06 com.sun.jbi.engine.bpel.BPELSEDeployer init
INFO: Activated an endpoint. Service name
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}SynchronousSample,
endpoint name partnerlinktyperole1_myRole
20-feb-2007 12:24:06 com.sun.jbi.engine.bpel.BPELSEDeployer init
INFO: BPELSE deploy process finished
INFO - ServiceUnitLifeCycle - Initializing service unit:
SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer init
INFO: Initializing service unit :
SynchronousSample1Application-com.sun.httpsoapbc-1.0-2 from
/opt/apache-servicemix-3.1-incubating/data/smx/service-assemblies/SynchronousSample1Application/version_1/sus/com.sun.httpsoapbc-1.0-2/SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
Retrieving document at
'/opt/apache-servicemix-3.1-incubating/data/smx/service-assemblies/SynchronousSample1Application/version_1/sus/com.sun.httpsoapbc-1.0-2/SynchronousSample1Application-com.sun.httpsoapbc-1.0-2/SynchronousSample.wsdl'.
Retrieving schema at 'SynchronousSample.xsd', relative to
'file:/opt/apache-servicemix-3.1-incubating/data/smx/service-assemblies/SynchronousSample1Application/version_1/sus/com.sun.httpsoapbc-1.0-2/SynchronousSample1Application-com.sun.httpsoapbc-1.0-2/SynchronousSample.wsdl'.
20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapEndpoint init
ADVERTENCIA: soap action is null
20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapEndpoint init
INFO: using soap action () as hints for operation operation1
20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer init
INFO: Service unit SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
was initialized successfully
INFO - ServiceUnitLifeCycle - Starting service unit:
SynchronousSample1Application-SynchronousSample1
INFO - ServiceUnitLifeCycle - Starting service unit:
SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer start
INFO: Starting suId : SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
20-feb-2007 12:24:06
com.sun.jbi.httpsoapbc.embedded.EmbeddedServerController startServer
INFO: Attempt to create Grizzly connector at 18.181
20-feb-2007 12:24:07 org.apache.coyote.tomcat5.CoyoteConnector start
INFO: Cannot register MBean for the Protocol
20-feb-2007 12:24:07
com.sun.enterprise.web.connector.grizzly.GrizzlyHttpProtocol start
INFO: grizzlyHttpProtocol.selectorRegisterProtocol
20-feb-2007 12:24:07
com.sun.enterprise.web.connector.grizzly.GrizzlyHttpProtocol start
INFO: grizzlyHttpProtocol.start
20-feb-2007 12:24:07
com.sun.jbi.httpsoapbc.embedded.EmbeddedServerController startServer
INFO: Grizzly connector created at 18.181
20-feb-2007 12:24:07 com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle
endpointActivated
INFO: Prepared inbound endpoint
{http://localhost/SynchronousSample/SynchronousSample}service1,port1,inbound
mapped to context /SynchronousSample
20-feb-2007 12:24:07 com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer start
INFO: Started : SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
INFO - JBIContainer - ServiceMix JBI Container
(ServiceMix) started
INFO - JDBCAdapterFactory - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
INFO - LogTask - log4j system reconfigured
At this point I think runs ok. The problem comes when I run a TestCase with
Netbeans. Output is never returned and in Servicemix I get the following
errors:
20-feb-2007 12:32:16 com.sun.jbi.httpsoapbc.util.DebugLog debugLog
INFO: sending normalized msg to component:
<?xml version="1.0" encoding="UTF-8"?><jbi:message
xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"
xmlns:msgns="http://localhost/SynchronousSample/SynchronousSample"
name="input1" type="msgns:requestMessage" version="1.0"><jbi:part><syn:typeA
xmlns:syn="http://xml.netbeans.org/schema/SynchronousSample">
<syn:paramA>Input</syn:paramA>
</syn:typeA></jbi:part></jbi:message>
WARN - DeliveryChannelImpl - Error calling listener: null
java.lang.NullPointerException
at
org.apache.servicemix.jbi.view.DotViewFlowListener.exchangeSent(DotViewFlowListener.java:159)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:364)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:417)
at
com.sun.jbi.httpsoapbc.InboundMessageProcessor.sendInOut(InboundMessageProcessor.java:314)
at
com.sun.jbi.httpsoapbc.InboundMessageProcessor.execute(InboundMessageProcessor.java:253)
at
com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.processAsynchRequest(GrizzlyRequestProcessor.java:236)
at
com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.service(GrizzlyRequestProcessor.java:195)
at
com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
at
com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:91)
at
com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:143)
at
com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:132)
at
com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:81)
at
com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at
com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
20-feb-2007 12:32:17 com.sun.jbi.httpsoapbc.OutboundReceiver run
INFO: Got a message in SOAP binding ID:localhost-57437-1171970639424-3:0
20-feb-2007 12:32:17 com.sun.jbi.httpsoapbc.OutboundAction run
GRAVE: Unexpected exception in processing outbound message
java.lang.NullPointerException
at
com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:206)
at
com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:180)
at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:57)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Is this a servicemix bug or should I post this message in Sun Java forums?
Thanks
gnodet wrote:
>
> In my previous mail, i said that you will find them in the open esb
> distribution.
> https://open-esb.dev.java.net/
> But dropping them inside ServiceMix won' t work (i' ve tried).
> You will need to solve CNFEs and put jars in ServiceMix sar
> or jboss classpath until it works.
> Note that the end result is uncertain ... up to you ;)
>
> On 8/24/06, Sat <Sa...@cognizant.com> wrote:
>>
>>
>>
>> I think i got it...So you mean to install the two components from Open
>> ESB
>> distribution into ServiceMix JBI container. Am i right? If thats the
>> case,
>> can you please let me know in which jar files these JBI components will
>> be
>> there and is it enough if i copy those files and drop it in deploy
>> directory? If there any other configurations required. Sorry for buzzing
>> again.
>>
>> Thanks, Sat
>>
>>
>> gnodet wrote:
>> >
>> > Not sure to understand your question,
>> > but the container is just, well, the container.
>> > You should be able to deploy any jbi compliant
>> > components on it.
>> > But if you want to deploy the SA that you have created,
>> > it depends on the openesb jbi components. It' s not
>> > a problem by itself, you just need to tweak ServiceMix
>> > sar or jboss classpath to include stuff needed by
>> > these components (if ever possible).
>> >
>> > On 8/24/06, Sat <Sa...@cognizant.com> wrote:
>> >>
>> >>
>> >> Gnodet,
>> >>
>> >> Correct me if i am wrong! If downloading Open ESB distribution and
>> >> deploying
>> >> it in Jboss, does it make as my ServiceMix ESB replacement? Tell me if
>> we
>> >> are just going to use JBI container of ServiceMix ESB for routing and
>> >> transformations and use Open ESB for webservices/BPEL processing?
>> >>
>> >> Thanks, Sat
>> >>
>> >>
>> >> gnodet wrote:
>> >> >
>> >> > Mmh, I guess you misunderstood me.
>> >> > Before trying to deploy this service assembly, you need to install
>> >> > the needed JBI components which are:
>> >> > * com.sun.bpelse-1.0-2
>> >> > * com.sun.httpsoapbc-1.0-2
>> >> > The jars SynchronousSampleApplication.zip are service units targeted
>> to
>> >> > these components. You need to find the JBI components installers
>> for
>> >> > these components, but I' m not sure where you can find them.
>> >> > Try to look for these files in your glassfish distribution or in
>> >> openesb
>> >> > one
>> >> > ...
>> >> >
>> >> > On 8/24/06, Sat <Sa...@cognizant.com> wrote:
>> >> >>
>> >> >>
>> >> >> Yes it does have the JBI descriptors. I have uploaded the files at
>> >> >> http://www.esnips.com/web/TechDoubts
>> >> http://www.esnips.com/web/TechDoubts
>> >> >> for your review. Please let me know your comments. The same zip
>> file
>> >> was
>> >> >> used to deploy in Sun Application Server and it worked.
>> >> >>
>> >> >> Thanks, Sat
>> >> >>
>> >> >>
>> >> >> gnodet wrote:
>> >> >> >
>> >> >> > Could you check if the httpsoapbc and bpelse jars have a jbi
>> >> descriptor
>> >> >> > in METAF-INF/jbi.xml ?
>> >> >> >
>> >> >> > I can not download the jar :(
>> >> >> > Do you have any url where i could download them without having to
>> >> >> download
>> >> >> > the
>> >> >> > full glashfish server ?
>> >> >> >
>> >> >> > On 8/24/06, Sat <Sa...@cognizant.com> wrote:
>> >> >> >>
>> >> >> >>
>> >> >> >> Thanks Gnodet for your quick reply.
>> >> >> >>
>> >> >> >> Actually i guess the JBI container was able to recognize my zip
>> >> file,
>> >> >> was
>> >> >> >> parsing for information on the zip file and was able to locate
>> the
>> >> >> files
>> >> >> >> inside the zip, i guess thats why it was able to print a INFO
>> >> message
>> >> >> of
>> >> >> >> "....com.sun.httpsoapbc-1.0-2, com.sun.bpelse-1.0-2 are not
>> >> installed
>> >> >> yet
>> >> >> >> -
>> >> >> >> > adding ServiceAssembly SynchronousSampleTestApplication to
>> >> pending
>> >> >> >> > list..." with the two filenames.
>> >> >> >>
>> >> >> >> Anyway i tried dropping those two jar files inside deploy
>> directory
>> >> >> and
>> >> >> >> restarted the server. Still the same :( No changes. Can you see
>> >> >> whether
>> >> >> >> somethingelse is wrong with the attached files.
>> >> >> >>
>> >> >> >> Thanks, Sat
>> >> >> >>
>> >> >> >>
>> >> >> >> gnodet wrote:
>> >> >> >> >
>> >> >> >> > Maybe i missed your points, but I think you have the solution.
>> >> >> >> > The "INFO
>> >> >> >> > [org.apache.servicemix.jbi
>> >> >> >> >>
>> >> >> >> >> .framework.AutoDeploymentService] Components
>> >> >> >> >> com.sun.httpsoapbc-1.0-2, com.sun.bpelse-1.0-2 are not
>> installed
>> >> >> yet
>> >> >> -
>> >> >> >> >> adding ServiceAssembly SynchronousSampleTestApplication to
>> >> pending
>> >> >> >> list".
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > message is the important one.
>> >> >> >> > If you want to deploy a Service Assembly to a JBI container,
>> the
>> >> >> >> > requirement
>> >> >> >> > is
>> >> >> >> > that the needed JBI components are previously installed.
>> >> >> >> > It seems this is not the case here as the log statement
>> >> indicates.
>> >> >> >> >
>> >> >> >> > You need to find the components zips for the two listed
>> >> components
>> >> >> and
>> >> >> >> > *try* to install them in ServiceMix (just drop them in the
>> deploy
>> >> >> dir
>> >> >> >> of
>> >> >> >> > jboss).
>> >> >> >> > If you are lucky it will work. Well, there' s no luck here.
>> It
>> >> will
>> >> >> >> work
>> >> >> >> > if
>> >> >> >> > the
>> >> >> >> > components are not tied to openesb.
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On 8/23/06, Sat <Sa...@cognizant.com>
>> wrote:
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> Hi,
>> >> >> >> >>
>> >> >> >> >> Have followed the bewlo steps in creating my BPEL project
>> >> >> >> >>
>> >> >> >> >> 1. Installed JDK 1.5.0_07
>> >> >> >> >> 2. Installed JBoss 4.0.4.GA AS
>> >> >> >> >> 3. Integrated the ServiceMix 3.0 M2 with JBoss AS by using
>> >> >> >> >> jboss-deployer-3.0-incubating-SNAPSHOT.sar and server starts
>> >> with
>> >> >> no
>> >> >> >> >> errors.
>> >> >> >> >> That means i can see the the message in my logs as
>> "ServiceMix
>> >> JBI
>> >> >> >> >> Container
>> >> >> >> >> (http://servicemix.org/) name: ServiceMix running version:
>> >> >> >> >> 3.0-incubating-SNAPSHOT"
>> >> >> >> >> 4. Now i followed the link
>> >> >> >> >> http://www.netbeans.org/kb/55/synchronousample.html
>> >> >> >> >> http://www.netbeans.org/kb/55/synchronousample.html and
>> created
>> >> >> the
>> >> >> >> >> simple
>> >> >> >> >> synchronous BPEL Process using the NetBeans IDE 5.5 beta
>> >> >> (enterprise
>> >> >> >> >> pack).
>> >> >> >> >> 5. I tried deploying into Sun Application Server and it
>> worked.
>> >> But
>> >> >> >> when
>> >> >> >> >> i
>> >> >> >> >> tried to deploy the BPEL process created to my JBoss AS
>> through
>> >> the
>> >> >> >> IDE,
>> >> >> >> >> i
>> >> >> >> >> got the error stating "Retrieving settings from C:\Documents
>> and
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> Settings\sdeenadayalan.354100952JEB1\.netbeans\5.5beta2/config/J2EE/InstalledServers/.nbattrs
>> >> >> >> >> /n java.lang.NumberFormatException: For input string:
>> >> >> >> "\jboss-4.0.4.GA"
>> >> >> >> >> "
>> >> >> >> >> 6. I thought it would be some configuration problem, so tried
>> to
>> >> >> copy
>> >> >> >> the
>> >> >> >> >> dist\SynchronousSampleApplication.zip
>> >> >> >> >> file created as part of the build process and deployed to the
>> >> >> deploy
>> >> >> >> >> directory of JBoss.
>> >> >> >> >> 7. Restarted the JBoss and there was no errors except that i
>> >> could
>> >> >> >> find
>> >> >> >> a
>> >> >> >> >> INFO message saying that "INFO
>> >> >> >> >> [org.apache.servicemix.jbi.framework.AutoDeploymentService]
>> >> >> Components
>> >> >> >> >> com.sun.httpsoapbc-1.0-2, com.sun.bpelse-1.0-2 are not
>> installed
>> >> >> yet
>> >> >> -
>> >> >> >> >> adding ServiceAssembly SynchronousSampleTestApplication to
>> >> pending
>> >> >> >> list".
>> >> >> >> >> 8. I understand that the file that i dropped was picked up by
>> >> the
>> >> >> JBI
>> >> >> >> >> container by "INFO
>> >> [org.servicemix.jboss.deployment.JBIDeployer]
>> >> >> >> >> ServiceMix
>> >> >> >> >> deployer passing deployment to JBI container
>> >> >> >> >> [file:/C:/jboss-
>> >> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> 4.0.4.GA/server/default/tmp/deploy/tmp61422SynchronousSampleApplication.zip-contents/com.sun.httpsoapbc-1.0-2.jar
>> >> >> >> ]
>> >> >> >> >> ",
>> >> >> >> >> But later for some reasons it was not able to deploy.
>> >> >> >> >> 9. I have attached a zip file containing the following items
>> for
>> >> >> your
>> >> >> >> >> review.
>> >> >> >> >>
>> >> >> >> >> SynchronousSampleApplication.zip - Application Sample
>> generated
>> >> >> >> through
>> >> >> >> >> NetBeans
>> >> >> >> >> Jboss_SM_NB.txt - containing the snippet of the
>> server.logfile
>> >> >> after
>> >> >> >> >> JBoss
>> >> >> >> >> starts.
>> >> >> >> >>
>> >> >> >> >> It would be great help and would appreciate if i can get a
>> >> solution
>> >> >> >> for
>> >> >> >> >> this.
>> >> >> >> >>
>> >> >> >> >> Thanks, Sat
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/user-files/235730/BPEL_Analysis.zipBPEL_Analysis.zip
>> >> >> >> >> --
>> >> >> >> >> View this message in context:
>> >> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5953389
>> >> >> >> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Cheers,
>> >> >> >> > Guillaume Nodet
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >> --
>> >> >> >> View this message in context:
>> >> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5953860
>> >> >> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Cheers,
>> >> >> > Guillaume Nodet
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5954364
>> >> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > Cheers,
>> >> > Guillaume Nodet
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5963885
>> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5965058
>> Sent from the ServiceMix - User forum at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context: http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124s12049.html#a9060063
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix+Jboss - Unable to run BPEL project created using
netbeans
Posted by Waxter <ml...@intecna.es>.
The another thread is about the Warning related to the listeners. But this is
not the relevant problem in this case, since the bpel invocation continues
ignoring this warning.
The part of the log I'm interested to resolve is:
20-feb-2007 18:13:07 com.sun.jbi.httpsoapbc.OutboundReceiver run
INFO: Got a message in SOAP binding ID:localhost-47983-1171989709539-3:4
20-feb-2007 18:13:07 com.sun.jbi.httpsoapbc.OutboundAction run
GRAVE: Unexpected exception in processing outbound message
java.lang.NullPointerException
at
com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:206)
at
com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:180)
at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:57)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
To run the test I use this Input soap-message using sendsoap.sh command-line
tool
<soapenv:Envelope
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:syn="http://xml.netbeans.org/schema/SynchronousSample">
<soapenv:Body>
<syn:typeA>
<syn:paramA>Input</syn:paramA>
</syn:typeA>
</soapenv:Body>
</soapenv:Envelope
root@localhost:/opt/ode/bin$ ./sendsoap.sh
http://localhost:18181/SynchronousSample client.test
..... but no response is given... :(
gnodet wrote:
>
> There is another thread about that.
> I have just fixed this NPE, but in the mean time,
> you should be able to remove the
> <sm:dotViewService />
> element in the main configuration.
>
> On 2/20/07, Waxter <ml...@intecna.es> wrote:
>>
>> I have installed both components (com.sun.httpsoapbc and com.sun.bpelse)
>> in
>> Servicemix and deployed SynchronousSample Application:
>>
>>
>> java version "1.5.0_09"
>> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b03)
>> Java HotSpot(TM) Client VM (build 1.5.0_09-b03, mixed mode)
>>
>> Starting Apache ServiceMix ESB: 3.1-incubating
>>
>> Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
>> INFO - ConnectorServerFactoryBean - JMX connector available at:
>> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
>> INFO - JBIContainer - ServiceMix 3.1-incubating JBI
>> Container (ServiceMix) is starting
>> INFO - JBIContainer - For help or more informations
>> please see: http://incubator.apache.org/servicemix/
>> INFO - ComponentMBeanImpl - Initializing component:
>> #SubscriptionManager#
>> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEBootstrap init
>> INFO: Calling init method
>> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
>> setDB_JNDIName
>> INFO: setting jndiname jdbc/__default
>> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
>> setDB_Type
>> INFO: setting type 4
>> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
>> setDB_URL
>> INFO: setting dburl jdbc:derby://localhost:1527/derbyDB
>> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
>> setDB_Password
>> INFO: setting password pass2
>> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
>> setDB_UserName
>> INFO: setting user usr2
>> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
>> setPersistenceEnabled
>> INFO: setting PersistenceEnabled flag false
>> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEBootstrap init
>> INFO: init method has been called
>> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEBootstrap
>> getExtensionMBeanName
>> INFO: retrieving installation configuration mbean
>> 20-feb-2007 12:24:00
>> com.sun.jbi.httpsoapbc.bootstrap.HttpSoapBindingBootstrap init
>> INFO: Registered MBean
>> org.apache.servicemix:ContainerName=ServiceMix,Type=Component,Name=com.sun.httpsoapbc-1.0-2,SubType=BootstrapExtension
>> INFO - DeploymentService - Restoring service assemblies
>> INFO - ComponentMBeanImpl - Setting running state for
>> Component: com.sun.bpelse-1.0-2 to Started
>> INFO - ComponentMBeanImpl - Initializing component:
>> com.sun.bpelse-1.0-2
>> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
>> INFO: Started BPEL service engine in-out thread
>> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
>> INFO: Started BPEL service engine in-out thread
>> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
>> INFO: Started BPEL service engine in-out thread
>> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
>> INFO: Started BPEL service engine in-out thread
>> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
>> INFO: Started BPEL service engine in-out thread
>> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
>> INFO: Started BPEL service engine in-out thread
>> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
>> INFO: Started BPEL service engine in-out thread
>> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
>> INFO: Started BPEL service engine in-out thread
>> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
>> INFO: Started BPEL service engine in-out thread
>> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSELifeCycle start
>> INFO: BPEL service engine started
>> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
>> INFO: Started BPEL service engine in-out thread
>> INFO - ComponentMBeanImpl - Setting running state for
>> Component: com.sun.httpsoapbc-1.0-2 to Started
>> INFO - ComponentMBeanImpl - Initializing component:
>> com.sun.httpsoapbc-1.0-2
>> 20-feb-2007 12:24:03 com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle
>> start
>> INFO: HTTP SOAP binding started.
>> 20-feb-2007 12:24:03 com.sun.jbi.httpsoapbc.OutboundReceiver run
>> INFO: Started receiver
>> INFO - ComponentMBeanImpl - Setting running state for
>> Component: JavaEEServiceEngine to Shutdown
>> INFO - ServiceAssemblyLifeCycle - Starting service assembly:
>> SynchronousSample1Application
>> INFO - ServiceUnitLifeCycle - Initializing service unit:
>> SynchronousSample1Application-SynchronousSample1
>> 20-feb-2007 12:24:03 com.sun.jbi.engine.bpel.BPELSEDeployer init
>> INFO: Starting BPELSE deploy process
>> 20-feb-2007 12:24:05 com.sun.jbi.engine.bpel.EngineHelper deploy
>> INFO: Loaded bpel processes to engine
>> 20-feb-2007 12:24:06 com.sun.jbi.engine.bpel.BPELSEDeployer init
>> INFO: Activated an endpoint. Service name
>> {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}SynchronousSample,
>> endpoint name partnerlinktyperole1_myRole
>> 20-feb-2007 12:24:06 com.sun.jbi.engine.bpel.BPELSEDeployer init
>> INFO: BPELSE deploy process finished
>> INFO - ServiceUnitLifeCycle - Initializing service unit:
>> SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
>> 20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer init
>> INFO: Initializing service unit :
>> SynchronousSample1Application-com.sun.httpsoapbc-1.0-2 from
>> /opt/apache-servicemix-3.1-incubating/data/smx/service-assemblies/SynchronousSample1Application/version_1/sus/com.sun.httpsoapbc-1.0-2/SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
>> Retrieving document at
>> '/opt/apache-servicemix-3.1-incubating/data/smx/service-assemblies/SynchronousSample1Application/version_1/sus/com.sun.httpsoapbc-1.0-2/SynchronousSample1Application-com.sun.httpsoapbc-1.0-2/SynchronousSample.wsdl'.
>> Retrieving schema at 'SynchronousSample.xsd', relative to
>> 'file:/opt/apache-servicemix-3.1-incubating/data/smx/service-assemblies/SynchronousSample1Application/version_1/sus/com.sun.httpsoapbc-1.0-2/SynchronousSample1Application-com.sun.httpsoapbc-1.0-2/SynchronousSample.wsdl'.
>> 20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapEndpoint init
>> ADVERTENCIA: soap action is null
>> 20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapEndpoint init
>> INFO: using soap action () as hints for operation operation1
>> 20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer init
>> INFO: Service unit SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
>> was initialized successfully
>> INFO - ServiceUnitLifeCycle - Starting service unit:
>> SynchronousSample1Application-SynchronousSample1
>> INFO - ServiceUnitLifeCycle - Starting service unit:
>> SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
>> 20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer start
>> INFO: Starting suId :
>> SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
>> 20-feb-2007 12:24:06
>> com.sun.jbi.httpsoapbc.embedded.EmbeddedServerController startServer
>> INFO: Attempt to create Grizzly connector at 18.181
>> 20-feb-2007 12:24:07 org.apache.coyote.tomcat5.CoyoteConnector start
>> INFO: Cannot register MBean for the Protocol
>> 20-feb-2007 12:24:07
>> com.sun.enterprise.web.connector.grizzly.GrizzlyHttpProtocol start
>> INFO: grizzlyHttpProtocol.selectorRegisterProtocol
>> 20-feb-2007 12:24:07
>> com.sun.enterprise.web.connector.grizzly.GrizzlyHttpProtocol start
>> INFO: grizzlyHttpProtocol.start
>> 20-feb-2007 12:24:07
>> com.sun.jbi.httpsoapbc.embedded.EmbeddedServerController startServer
>> INFO: Grizzly connector created at 18.181
>> 20-feb-2007 12:24:07 com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle
>> endpointActivated
>> INFO: Prepared inbound endpoint
>> {http://localhost/SynchronousSample/SynchronousSample}service1,port1,inbound
>> mapped to context /SynchronousSample
>> 20-feb-2007 12:24:07 com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer start
>> INFO: Started : SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
>> INFO - JBIContainer - ServiceMix JBI Container
>> (ServiceMix) started
>> INFO - JDBCAdapterFactory - Database driver recognized:
>> [apache_derby_embedded_jdbc_driver]
>> INFO - LogTask - log4j system reconfigured
>>
>> At this point I think runs ok. The problem comes when I run a TestCase
>> with
>> Netbeans. Output is never returned and in Servicemix I get the following
>> errors:
>>
>> 20-feb-2007 12:32:16 com.sun.jbi.httpsoapbc.util.DebugLog debugLog
>> INFO: sending normalized msg to component:
>> <?xml version="1.0" encoding="UTF-8"?><jbi:message
>> xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"
>> xmlns:msgns="http://localhost/SynchronousSample/SynchronousSample"
>> name="input1" type="msgns:requestMessage"
>> version="1.0"><jbi:part><syn:typeA
>> xmlns:syn="http://xml.netbeans.org/schema/SynchronousSample">
>> <syn:paramA>Input</syn:paramA>
>> </syn:typeA></jbi:part></jbi:message>
>> WARN - DeliveryChannelImpl - Error calling listener: null
>> java.lang.NullPointerException
>> at
>> org.apache.servicemix.jbi.view.DotViewFlowListener.exchangeSent(DotViewFlowListener.java:159)
>> at
>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:364)
>> at
>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:417)
>> at
>> com.sun.jbi.httpsoapbc.InboundMessageProcessor.sendInOut(InboundMessageProcessor.java:314)
>> at
>> com.sun.jbi.httpsoapbc.InboundMessageProcessor.execute(InboundMessageProcessor.java:253)
>> at
>> com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.processAsynchRequest(GrizzlyRequestProcessor.java:236)
>> at
>> com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.service(GrizzlyRequestProcessor.java:195)
>> at
>> com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
>> at
>> com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:91)
>> at
>> com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:143)
>> at
>> com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:132)
>> at
>> com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:81)
>> at
>> com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
>> at
>> com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
>> 20-feb-2007 12:32:17 com.sun.jbi.httpsoapbc.OutboundReceiver run
>> INFO: Got a message in SOAP binding ID:localhost-57437-1171970639424-3:0
>> 20-feb-2007 12:32:17 com.sun.jbi.httpsoapbc.OutboundAction run
>> GRAVE: Unexpected exception in processing outbound message
>> java.lang.NullPointerException
>> at
>> com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:206)
>> at
>> com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:180)
>> at
>> com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:57)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>> at java.lang.Thread.run(Thread.java:595)
>>
>> Is this a servicemix bug or should I post this message in Sun Java
>> forums?
>>
>> Thanks
>>
>>
>>
>>
>>
>> gnodet wrote:
>> >
>> > In my previous mail, i said that you will find them in the open esb
>> > distribution.
>> > https://open-esb.dev.java.net/
>> > But dropping them inside ServiceMix won' t work (i' ve tried).
>> > You will need to solve CNFEs and put jars in ServiceMix sar
>> > or jboss classpath until it works.
>> > Note that the end result is uncertain ... up to you ;)
>> >
>> > On 8/24/06, Sat <Sa...@cognizant.com> wrote:
>> >>
>> >>
>> >>
>> >> I think i got it...So you mean to install the two components from Open
>> >> ESB
>> >> distribution into ServiceMix JBI container. Am i right? If thats the
>> >> case,
>> >> can you please let me know in which jar files these JBI components
>> will
>> >> be
>> >> there and is it enough if i copy those files and drop it in deploy
>> >> directory? If there any other configurations required. Sorry for
>> buzzing
>> >> again.
>> >>
>> >> Thanks, Sat
>> >>
>> >>
>> >> gnodet wrote:
>> >> >
>> >> > Not sure to understand your question,
>> >> > but the container is just, well, the container.
>> >> > You should be able to deploy any jbi compliant
>> >> > components on it.
>> >> > But if you want to deploy the SA that you have created,
>> >> > it depends on the openesb jbi components. It' s not
>> >> > a problem by itself, you just need to tweak ServiceMix
>> >> > sar or jboss classpath to include stuff needed by
>> >> > these components (if ever possible).
>> >> >
>> >> > On 8/24/06, Sat <Sa...@cognizant.com> wrote:
>> >> >>
>> >> >>
>> >> >> Gnodet,
>> >> >>
>> >> >> Correct me if i am wrong! If downloading Open ESB distribution and
>> >> >> deploying
>> >> >> it in Jboss, does it make as my ServiceMix ESB replacement? Tell me
>> if
>> >> we
>> >> >> are just going to use JBI container of ServiceMix ESB for routing
>> and
>> >> >> transformations and use Open ESB for webservices/BPEL processing?
>> >> >>
>> >> >> Thanks, Sat
>> >> >>
>> >> >>
>> >> >> gnodet wrote:
>> >> >> >
>> >> >> > Mmh, I guess you misunderstood me.
>> >> >> > Before trying to deploy this service assembly, you need to
>> install
>> >> >> > the needed JBI components which are:
>> >> >> > * com.sun.bpelse-1.0-2
>> >> >> > * com.sun.httpsoapbc-1.0-2
>> >> >> > The jars SynchronousSampleApplication.zip are service units
>> targeted
>> >> to
>> >> >> > these components. You need to find the JBI components installers
>> >> for
>> >> >> > these components, but I' m not sure where you can find them.
>> >> >> > Try to look for these files in your glassfish distribution or in
>> >> >> openesb
>> >> >> > one
>> >> >> > ...
>> >> >> >
>> >> >> > On 8/24/06, Sat <Sa...@cognizant.com> wrote:
>> >> >> >>
>> >> >> >>
>> >> >> >> Yes it does have the JBI descriptors. I have uploaded the files
>> at
>> >> >> >> http://www.esnips.com/web/TechDoubts
>> >> >> http://www.esnips.com/web/TechDoubts
>> >> >> >> for your review. Please let me know your comments. The same zip
>> >> file
>> >> >> was
>> >> >> >> used to deploy in Sun Application Server and it worked.
>> >> >> >>
>> >> >> >> Thanks, Sat
>> >> >> >>
>> >> >> >>
>> >> >> >> gnodet wrote:
>> >> >> >> >
>> >> >> >> > Could you check if the httpsoapbc and bpelse jars have a jbi
>> >> >> descriptor
>> >> >> >> > in METAF-INF/jbi.xml ?
>> >> >> >> >
>> >> >> >> > I can not download the jar :(
>> >> >> >> > Do you have any url where i could download them without having
>> to
>> >> >> >> download
>> >> >> >> > the
>> >> >> >> > full glashfish server ?
>> >> >> >> >
>> >> >> >> > On 8/24/06, Sat <Sa...@cognizant.com>
>> wrote:
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> Thanks Gnodet for your quick reply.
>> >> >> >> >>
>> >> >> >> >> Actually i guess the JBI container was able to recognize my
>> zip
>> >> >> file,
>> >> >> >> was
>> >> >> >> >> parsing for information on the zip file and was able to
>> locate
>> >> the
>> >> >> >> files
>> >> >> >> >> inside the zip, i guess thats why it was able to print a INFO
>> >> >> message
>> >> >> >> of
>> >> >> >> >> "....com.sun.httpsoapbc-1.0-2, com.sun.bpelse-1.0-2 are not
>> >> >> installed
>> >> >> >> yet
>> >> >> >> >> -
>> >> >> >> >> > adding ServiceAssembly SynchronousSampleTestApplication to
>> >> >> pending
>> >> >> >> >> > list..." with the two filenames.
>> >> >> >> >>
>> >> >> >> >> Anyway i tried dropping those two jar files inside deploy
>> >> directory
>> >> >> >> and
>> >> >> >> >> restarted the server. Still the same :( No changes. Can you
>> see
>> >> >> >> whether
>> >> >> >> >> somethingelse is wrong with the attached files.
>> >> >> >> >>
>> >> >> >> >> Thanks, Sat
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> gnodet wrote:
>> >> >> >> >> >
>> >> >> >> >> > Maybe i missed your points, but I think you have the
>> solution.
>> >> >> >> >> > The "INFO
>> >> >> >> >> > [org.apache.servicemix.jbi
>> >> >> >> >> >>
>> >> >> >> >> >> .framework.AutoDeploymentService] Components
>> >> >> >> >> >> com.sun.httpsoapbc-1.0-2, com.sun.bpelse-1.0-2 are not
>> >> installed
>> >> >> >> yet
>> >> >> >> -
>> >> >> >> >> >> adding ServiceAssembly SynchronousSampleTestApplication to
>> >> >> pending
>> >> >> >> >> list".
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > message is the important one.
>> >> >> >> >> > If you want to deploy a Service Assembly to a JBI
>> container,
>> >> the
>> >> >> >> >> > requirement
>> >> >> >> >> > is
>> >> >> >> >> > that the needed JBI components are previously installed.
>> >> >> >> >> > It seems this is not the case here as the log statement
>> >> >> indicates.
>> >> >> >> >> >
>> >> >> >> >> > You need to find the components zips for the two listed
>> >> >> components
>> >> >> >> and
>> >> >> >> >> > *try* to install them in ServiceMix (just drop them in the
>> >> deploy
>> >> >> >> dir
>> >> >> >> >> of
>> >> >> >> >> > jboss).
>> >> >> >> >> > If you are lucky it will work. Well, there' s no luck
>> here.
>> >> It
>> >> >> will
>> >> >> >> >> work
>> >> >> >> >> > if
>> >> >> >> >> > the
>> >> >> >> >> > components are not tied to openesb.
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > On 8/23/06, Sat <Sa...@cognizant.com>
>> >> wrote:
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> Hi,
>> >> >> >> >> >>
>> >> >> >> >> >> Have followed the bewlo steps in creating my BPEL project
>> >> >> >> >> >>
>> >> >> >> >> >> 1. Installed JDK 1.5.0_07
>> >> >> >> >> >> 2. Installed JBoss 4.0.4.GA AS
>> >> >> >> >> >> 3. Integrated the ServiceMix 3.0 M2 with JBoss AS by using
>> >> >> >> >> >> jboss-deployer-3.0-incubating-SNAPSHOT.sar and server
>> starts
>> >> >> with
>> >> >> >> no
>> >> >> >> >> >> errors.
>> >> >> >> >> >> That means i can see the the message in my logs as
>> >> "ServiceMix
>> >> >> JBI
>> >> >> >> >> >> Container
>> >> >> >> >> >> (http://servicemix.org/) name: ServiceMix running version:
>> >> >> >> >> >> 3.0-incubating-SNAPSHOT"
>> >> >> >> >> >> 4. Now i followed the link
>> >> >> >> >> >> http://www.netbeans.org/kb/55/synchronousample.html
>> >> >> >> >> >> http://www.netbeans.org/kb/55/synchronousample.html and
>> >> created
>> >> >> >> the
>> >> >> >> >> >> simple
>> >> >> >> >> >> synchronous BPEL Process using the NetBeans IDE 5.5 beta
>> >> >> >> (enterprise
>> >> >> >> >> >> pack).
>> >> >> >> >> >> 5. I tried deploying into Sun Application Server and it
>> >> worked.
>> >> >> But
>> >> >> >> >> when
>> >> >> >> >> >> i
>> >> >> >> >> >> tried to deploy the BPEL process created to my JBoss AS
>> >> through
>> >> >> the
>> >> >> >> >> IDE,
>> >> >> >> >> >> i
>> >> >> >> >> >> got the error stating "Retrieving settings from
>> C:\Documents
>> >> and
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> Settings\sdeenadayalan.354100952JEB1\.netbeans\5.5beta2/config/J2EE/InstalledServers/.nbattrs
>> >> >> >> >> >> /n java.lang.NumberFormatException: For input string:
>> >> >> >> >> "\jboss-4.0.4.GA"
>> >> >> >> >> >> "
>> >> >> >> >> >> 6. I thought it would be some configuration problem, so
>> tried
>> >> to
>> >> >> >> copy
>> >> >> >> >> the
>> >> >> >> >> >> dist\SynchronousSampleApplication.zip
>> >> >> >> >> >> file created as part of the build process and deployed to
>> the
>> >> >> >> deploy
>> >> >> >> >> >> directory of JBoss.
>> >> >> >> >> >> 7. Restarted the JBoss and there was no errors except that
>> i
>> >> >> could
>> >> >> >> >> find
>> >> >> >> >> a
>> >> >> >> >> >> INFO message saying that "INFO
>> >> >> >> >> >>
>> [org.apache.servicemix.jbi.framework.AutoDeploymentService]
>> >> >> >> Components
>> >> >> >> >> >> com.sun.httpsoapbc-1.0-2, com.sun.bpelse-1.0-2 are not
>> >> installed
>> >> >> >> yet
>> >> >> >> -
>> >> >> >> >> >> adding ServiceAssembly SynchronousSampleTestApplication to
>> >> >> pending
>> >> >> >> >> list".
>> >> >> >> >> >> 8. I understand that the file that i dropped was picked up
>> by
>> >> >> the
>> >> >> >> JBI
>> >> >> >> >> >> container by "INFO
>> >> >> [org.servicemix.jboss.deployment.JBIDeployer]
>> >> >> >> >> >> ServiceMix
>> >> >> >> >> >> deployer passing deployment to JBI container
>> >> >> >> >> >> [file:/C:/jboss-
>> >> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> 4.0.4.GA/server/default/tmp/deploy/tmp61422SynchronousSampleApplication.zip-contents/com.sun.httpsoapbc-1.0-2.jar
>> >> >> >> >> ]
>> >> >> >> >> >> ",
>> >> >> >> >> >> But later for some reasons it was not able to deploy.
>> >> >> >> >> >> 9. I have attached a zip file containing the following
>> items
>> >> for
>> >> >> >> your
>> >> >> >> >> >> review.
>> >> >> >> >> >>
>> >> >> >> >> >> SynchronousSampleApplication.zip - Application Sample
>> >> generated
>> >> >> >> >> through
>> >> >> >> >> >> NetBeans
>> >> >> >> >> >> Jboss_SM_NB.txt - containing the snippet of the
>> >> server.logfile
>> >> >> >> after
>> >> >> >> >> >> JBoss
>> >> >> >> >> >> starts.
>> >> >> >> >> >>
>> >> >> >> >> >> It would be great help and would appreciate if i can get a
>> >> >> solution
>> >> >> >> >> for
>> >> >> >> >> >> this.
>> >> >> >> >> >>
>> >> >> >> >> >> Thanks, Sat
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/user-files/235730/BPEL_Analysis.zipBPEL_Analysis.zip
>> >> >> >> >> >> --
>> >> >> >> >> >> View this message in context:
>> >> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5953389
>> >> >> >> >> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > --
>> >> >> >> >> > Cheers,
>> >> >> >> >> > Guillaume Nodet
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> View this message in context:
>> >> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5953860
>> >> >> >> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Cheers,
>> >> >> >> > Guillaume Nodet
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >> --
>> >> >> >> View this message in context:
>> >> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5954364
>> >> >> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Cheers,
>> >> >> > Guillaume Nodet
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5963885
>> >> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > Cheers,
>> >> > Guillaume Nodet
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5965058
>> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124s12049.html#a9060063
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/
>
>
--
View this message in context: http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124s12049.html#a9066203
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix+Jboss - Unable to run BPEL project created using netbeans
Posted by Guillaume Nodet <gn...@gmail.com>.
There is another thread about that.
I have just fixed this NPE, but in the mean time,
you should be able to remove the
<sm:dotViewService />
element in the main configuration.
On 2/20/07, Waxter <ml...@intecna.es> wrote:
>
> I have installed both components (com.sun.httpsoapbc and com.sun.bpelse) in
> Servicemix and deployed SynchronousSample Application:
>
>
> java version "1.5.0_09"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_09-b03, mixed mode)
>
> Starting Apache ServiceMix ESB: 3.1-incubating
>
> Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
> INFO - ConnectorServerFactoryBean - JMX connector available at:
> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> INFO - JBIContainer - ServiceMix 3.1-incubating JBI
> Container (ServiceMix) is starting
> INFO - JBIContainer - For help or more informations
> please see: http://incubator.apache.org/servicemix/
> INFO - ComponentMBeanImpl - Initializing component:
> #SubscriptionManager#
> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEBootstrap init
> INFO: Calling init method
> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
> setDB_JNDIName
> INFO: setting jndiname jdbc/__default
> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
> setDB_Type
> INFO: setting type 4
> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
> setDB_URL
> INFO: setting dburl jdbc:derby://localhost:1527/derbyDB
> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
> setDB_Password
> INFO: setting password pass2
> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
> setDB_UserName
> INFO: setting user usr2
> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEInstallerConfiguration
> setPersistenceEnabled
> INFO: setting PersistenceEnabled flag false
> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEBootstrap init
> INFO: init method has been called
> 20-feb-2007 12:24:00 com.sun.jbi.engine.bpel.BPELSEBootstrap
> getExtensionMBeanName
> INFO: retrieving installation configuration mbean
> 20-feb-2007 12:24:00
> com.sun.jbi.httpsoapbc.bootstrap.HttpSoapBindingBootstrap init
> INFO: Registered MBean
> org.apache.servicemix:ContainerName=ServiceMix,Type=Component,Name=com.sun.httpsoapbc-1.0-2,SubType=BootstrapExtension
> INFO - DeploymentService - Restoring service assemblies
> INFO - ComponentMBeanImpl - Setting running state for
> Component: com.sun.bpelse-1.0-2 to Started
> INFO - ComponentMBeanImpl - Initializing component:
> com.sun.bpelse-1.0-2
> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
> INFO: Started BPEL service engine in-out thread
> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
> INFO: Started BPEL service engine in-out thread
> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
> INFO: Started BPEL service engine in-out thread
> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
> INFO: Started BPEL service engine in-out thread
> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
> INFO: Started BPEL service engine in-out thread
> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
> INFO: Started BPEL service engine in-out thread
> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
> INFO: Started BPEL service engine in-out thread
> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
> INFO: Started BPEL service engine in-out thread
> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
> INFO: Started BPEL service engine in-out thread
> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSELifeCycle start
> INFO: BPEL service engine started
> 20-feb-2007 12:24:02 com.sun.jbi.engine.bpel.BPELSEInOutThread run
> INFO: Started BPEL service engine in-out thread
> INFO - ComponentMBeanImpl - Setting running state for
> Component: com.sun.httpsoapbc-1.0-2 to Started
> INFO - ComponentMBeanImpl - Initializing component:
> com.sun.httpsoapbc-1.0-2
> 20-feb-2007 12:24:03 com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle start
> INFO: HTTP SOAP binding started.
> 20-feb-2007 12:24:03 com.sun.jbi.httpsoapbc.OutboundReceiver run
> INFO: Started receiver
> INFO - ComponentMBeanImpl - Setting running state for
> Component: JavaEEServiceEngine to Shutdown
> INFO - ServiceAssemblyLifeCycle - Starting service assembly:
> SynchronousSample1Application
> INFO - ServiceUnitLifeCycle - Initializing service unit:
> SynchronousSample1Application-SynchronousSample1
> 20-feb-2007 12:24:03 com.sun.jbi.engine.bpel.BPELSEDeployer init
> INFO: Starting BPELSE deploy process
> 20-feb-2007 12:24:05 com.sun.jbi.engine.bpel.EngineHelper deploy
> INFO: Loaded bpel processes to engine
> 20-feb-2007 12:24:06 com.sun.jbi.engine.bpel.BPELSEDeployer init
> INFO: Activated an endpoint. Service name
> {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}SynchronousSample,
> endpoint name partnerlinktyperole1_myRole
> 20-feb-2007 12:24:06 com.sun.jbi.engine.bpel.BPELSEDeployer init
> INFO: BPELSE deploy process finished
> INFO - ServiceUnitLifeCycle - Initializing service unit:
> SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
> 20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer init
> INFO: Initializing service unit :
> SynchronousSample1Application-com.sun.httpsoapbc-1.0-2 from
> /opt/apache-servicemix-3.1-incubating/data/smx/service-assemblies/SynchronousSample1Application/version_1/sus/com.sun.httpsoapbc-1.0-2/SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
> Retrieving document at
> '/opt/apache-servicemix-3.1-incubating/data/smx/service-assemblies/SynchronousSample1Application/version_1/sus/com.sun.httpsoapbc-1.0-2/SynchronousSample1Application-com.sun.httpsoapbc-1.0-2/SynchronousSample.wsdl'.
> Retrieving schema at 'SynchronousSample.xsd', relative to
> 'file:/opt/apache-servicemix-3.1-incubating/data/smx/service-assemblies/SynchronousSample1Application/version_1/sus/com.sun.httpsoapbc-1.0-2/SynchronousSample1Application-com.sun.httpsoapbc-1.0-2/SynchronousSample.wsdl'.
> 20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapEndpoint init
> ADVERTENCIA: soap action is null
> 20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapEndpoint init
> INFO: using soap action () as hints for operation operation1
> 20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer init
> INFO: Service unit SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
> was initialized successfully
> INFO - ServiceUnitLifeCycle - Starting service unit:
> SynchronousSample1Application-SynchronousSample1
> INFO - ServiceUnitLifeCycle - Starting service unit:
> SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
> 20-feb-2007 12:24:06 com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer start
> INFO: Starting suId : SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
> 20-feb-2007 12:24:06
> com.sun.jbi.httpsoapbc.embedded.EmbeddedServerController startServer
> INFO: Attempt to create Grizzly connector at 18.181
> 20-feb-2007 12:24:07 org.apache.coyote.tomcat5.CoyoteConnector start
> INFO: Cannot register MBean for the Protocol
> 20-feb-2007 12:24:07
> com.sun.enterprise.web.connector.grizzly.GrizzlyHttpProtocol start
> INFO: grizzlyHttpProtocol.selectorRegisterProtocol
> 20-feb-2007 12:24:07
> com.sun.enterprise.web.connector.grizzly.GrizzlyHttpProtocol start
> INFO: grizzlyHttpProtocol.start
> 20-feb-2007 12:24:07
> com.sun.jbi.httpsoapbc.embedded.EmbeddedServerController startServer
> INFO: Grizzly connector created at 18.181
> 20-feb-2007 12:24:07 com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle
> endpointActivated
> INFO: Prepared inbound endpoint
> {http://localhost/SynchronousSample/SynchronousSample}service1,port1,inbound
> mapped to context /SynchronousSample
> 20-feb-2007 12:24:07 com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer start
> INFO: Started : SynchronousSample1Application-com.sun.httpsoapbc-1.0-2
> INFO - JBIContainer - ServiceMix JBI Container
> (ServiceMix) started
> INFO - JDBCAdapterFactory - Database driver recognized:
> [apache_derby_embedded_jdbc_driver]
> INFO - LogTask - log4j system reconfigured
>
> At this point I think runs ok. The problem comes when I run a TestCase with
> Netbeans. Output is never returned and in Servicemix I get the following
> errors:
>
> 20-feb-2007 12:32:16 com.sun.jbi.httpsoapbc.util.DebugLog debugLog
> INFO: sending normalized msg to component:
> <?xml version="1.0" encoding="UTF-8"?><jbi:message
> xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"
> xmlns:msgns="http://localhost/SynchronousSample/SynchronousSample"
> name="input1" type="msgns:requestMessage" version="1.0"><jbi:part><syn:typeA
> xmlns:syn="http://xml.netbeans.org/schema/SynchronousSample">
> <syn:paramA>Input</syn:paramA>
> </syn:typeA></jbi:part></jbi:message>
> WARN - DeliveryChannelImpl - Error calling listener: null
> java.lang.NullPointerException
> at
> org.apache.servicemix.jbi.view.DotViewFlowListener.exchangeSent(DotViewFlowListener.java:159)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:364)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:417)
> at
> com.sun.jbi.httpsoapbc.InboundMessageProcessor.sendInOut(InboundMessageProcessor.java:314)
> at
> com.sun.jbi.httpsoapbc.InboundMessageProcessor.execute(InboundMessageProcessor.java:253)
> at
> com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.processAsynchRequest(GrizzlyRequestProcessor.java:236)
> at
> com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.service(GrizzlyRequestProcessor.java:195)
> at
> com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
> at
> com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:91)
> at
> com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:143)
> at
> com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:132)
> at
> com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:81)
> at
> com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
> at
> com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
> 20-feb-2007 12:32:17 com.sun.jbi.httpsoapbc.OutboundReceiver run
> INFO: Got a message in SOAP binding ID:localhost-57437-1171970639424-3:0
> 20-feb-2007 12:32:17 com.sun.jbi.httpsoapbc.OutboundAction run
> GRAVE: Unexpected exception in processing outbound message
> java.lang.NullPointerException
> at
> com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyInbound(OutboundMessageProcessor.java:206)
> at
> com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:180)
> at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:57)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:595)
>
> Is this a servicemix bug or should I post this message in Sun Java forums?
>
> Thanks
>
>
>
>
>
> gnodet wrote:
> >
> > In my previous mail, i said that you will find them in the open esb
> > distribution.
> > https://open-esb.dev.java.net/
> > But dropping them inside ServiceMix won' t work (i' ve tried).
> > You will need to solve CNFEs and put jars in ServiceMix sar
> > or jboss classpath until it works.
> > Note that the end result is uncertain ... up to you ;)
> >
> > On 8/24/06, Sat <Sa...@cognizant.com> wrote:
> >>
> >>
> >>
> >> I think i got it...So you mean to install the two components from Open
> >> ESB
> >> distribution into ServiceMix JBI container. Am i right? If thats the
> >> case,
> >> can you please let me know in which jar files these JBI components will
> >> be
> >> there and is it enough if i copy those files and drop it in deploy
> >> directory? If there any other configurations required. Sorry for buzzing
> >> again.
> >>
> >> Thanks, Sat
> >>
> >>
> >> gnodet wrote:
> >> >
> >> > Not sure to understand your question,
> >> > but the container is just, well, the container.
> >> > You should be able to deploy any jbi compliant
> >> > components on it.
> >> > But if you want to deploy the SA that you have created,
> >> > it depends on the openesb jbi components. It' s not
> >> > a problem by itself, you just need to tweak ServiceMix
> >> > sar or jboss classpath to include stuff needed by
> >> > these components (if ever possible).
> >> >
> >> > On 8/24/06, Sat <Sa...@cognizant.com> wrote:
> >> >>
> >> >>
> >> >> Gnodet,
> >> >>
> >> >> Correct me if i am wrong! If downloading Open ESB distribution and
> >> >> deploying
> >> >> it in Jboss, does it make as my ServiceMix ESB replacement? Tell me if
> >> we
> >> >> are just going to use JBI container of ServiceMix ESB for routing and
> >> >> transformations and use Open ESB for webservices/BPEL processing?
> >> >>
> >> >> Thanks, Sat
> >> >>
> >> >>
> >> >> gnodet wrote:
> >> >> >
> >> >> > Mmh, I guess you misunderstood me.
> >> >> > Before trying to deploy this service assembly, you need to install
> >> >> > the needed JBI components which are:
> >> >> > * com.sun.bpelse-1.0-2
> >> >> > * com.sun.httpsoapbc-1.0-2
> >> >> > The jars SynchronousSampleApplication.zip are service units targeted
> >> to
> >> >> > these components. You need to find the JBI components installers
> >> for
> >> >> > these components, but I' m not sure where you can find them.
> >> >> > Try to look for these files in your glassfish distribution or in
> >> >> openesb
> >> >> > one
> >> >> > ...
> >> >> >
> >> >> > On 8/24/06, Sat <Sa...@cognizant.com> wrote:
> >> >> >>
> >> >> >>
> >> >> >> Yes it does have the JBI descriptors. I have uploaded the files at
> >> >> >> http://www.esnips.com/web/TechDoubts
> >> >> http://www.esnips.com/web/TechDoubts
> >> >> >> for your review. Please let me know your comments. The same zip
> >> file
> >> >> was
> >> >> >> used to deploy in Sun Application Server and it worked.
> >> >> >>
> >> >> >> Thanks, Sat
> >> >> >>
> >> >> >>
> >> >> >> gnodet wrote:
> >> >> >> >
> >> >> >> > Could you check if the httpsoapbc and bpelse jars have a jbi
> >> >> descriptor
> >> >> >> > in METAF-INF/jbi.xml ?
> >> >> >> >
> >> >> >> > I can not download the jar :(
> >> >> >> > Do you have any url where i could download them without having to
> >> >> >> download
> >> >> >> > the
> >> >> >> > full glashfish server ?
> >> >> >> >
> >> >> >> > On 8/24/06, Sat <Sa...@cognizant.com> wrote:
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> Thanks Gnodet for your quick reply.
> >> >> >> >>
> >> >> >> >> Actually i guess the JBI container was able to recognize my zip
> >> >> file,
> >> >> >> was
> >> >> >> >> parsing for information on the zip file and was able to locate
> >> the
> >> >> >> files
> >> >> >> >> inside the zip, i guess thats why it was able to print a INFO
> >> >> message
> >> >> >> of
> >> >> >> >> "....com.sun.httpsoapbc-1.0-2, com.sun.bpelse-1.0-2 are not
> >> >> installed
> >> >> >> yet
> >> >> >> >> -
> >> >> >> >> > adding ServiceAssembly SynchronousSampleTestApplication to
> >> >> pending
> >> >> >> >> > list..." with the two filenames.
> >> >> >> >>
> >> >> >> >> Anyway i tried dropping those two jar files inside deploy
> >> directory
> >> >> >> and
> >> >> >> >> restarted the server. Still the same :( No changes. Can you see
> >> >> >> whether
> >> >> >> >> somethingelse is wrong with the attached files.
> >> >> >> >>
> >> >> >> >> Thanks, Sat
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> gnodet wrote:
> >> >> >> >> >
> >> >> >> >> > Maybe i missed your points, but I think you have the solution.
> >> >> >> >> > The "INFO
> >> >> >> >> > [org.apache.servicemix.jbi
> >> >> >> >> >>
> >> >> >> >> >> .framework.AutoDeploymentService] Components
> >> >> >> >> >> com.sun.httpsoapbc-1.0-2, com.sun.bpelse-1.0-2 are not
> >> installed
> >> >> >> yet
> >> >> >> -
> >> >> >> >> >> adding ServiceAssembly SynchronousSampleTestApplication to
> >> >> pending
> >> >> >> >> list".
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > message is the important one.
> >> >> >> >> > If you want to deploy a Service Assembly to a JBI container,
> >> the
> >> >> >> >> > requirement
> >> >> >> >> > is
> >> >> >> >> > that the needed JBI components are previously installed.
> >> >> >> >> > It seems this is not the case here as the log statement
> >> >> indicates.
> >> >> >> >> >
> >> >> >> >> > You need to find the components zips for the two listed
> >> >> components
> >> >> >> and
> >> >> >> >> > *try* to install them in ServiceMix (just drop them in the
> >> deploy
> >> >> >> dir
> >> >> >> >> of
> >> >> >> >> > jboss).
> >> >> >> >> > If you are lucky it will work. Well, there' s no luck here.
> >> It
> >> >> will
> >> >> >> >> work
> >> >> >> >> > if
> >> >> >> >> > the
> >> >> >> >> > components are not tied to openesb.
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > On 8/23/06, Sat <Sa...@cognizant.com>
> >> wrote:
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> Hi,
> >> >> >> >> >>
> >> >> >> >> >> Have followed the bewlo steps in creating my BPEL project
> >> >> >> >> >>
> >> >> >> >> >> 1. Installed JDK 1.5.0_07
> >> >> >> >> >> 2. Installed JBoss 4.0.4.GA AS
> >> >> >> >> >> 3. Integrated the ServiceMix 3.0 M2 with JBoss AS by using
> >> >> >> >> >> jboss-deployer-3.0-incubating-SNAPSHOT.sar and server starts
> >> >> with
> >> >> >> no
> >> >> >> >> >> errors.
> >> >> >> >> >> That means i can see the the message in my logs as
> >> "ServiceMix
> >> >> JBI
> >> >> >> >> >> Container
> >> >> >> >> >> (http://servicemix.org/) name: ServiceMix running version:
> >> >> >> >> >> 3.0-incubating-SNAPSHOT"
> >> >> >> >> >> 4. Now i followed the link
> >> >> >> >> >> http://www.netbeans.org/kb/55/synchronousample.html
> >> >> >> >> >> http://www.netbeans.org/kb/55/synchronousample.html and
> >> created
> >> >> >> the
> >> >> >> >> >> simple
> >> >> >> >> >> synchronous BPEL Process using the NetBeans IDE 5.5 beta
> >> >> >> (enterprise
> >> >> >> >> >> pack).
> >> >> >> >> >> 5. I tried deploying into Sun Application Server and it
> >> worked.
> >> >> But
> >> >> >> >> when
> >> >> >> >> >> i
> >> >> >> >> >> tried to deploy the BPEL process created to my JBoss AS
> >> through
> >> >> the
> >> >> >> >> IDE,
> >> >> >> >> >> i
> >> >> >> >> >> got the error stating "Retrieving settings from C:\Documents
> >> and
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >>
> >> Settings\sdeenadayalan.354100952JEB1\.netbeans\5.5beta2/config/J2EE/InstalledServers/.nbattrs
> >> >> >> >> >> /n java.lang.NumberFormatException: For input string:
> >> >> >> >> "\jboss-4.0.4.GA"
> >> >> >> >> >> "
> >> >> >> >> >> 6. I thought it would be some configuration problem, so tried
> >> to
> >> >> >> copy
> >> >> >> >> the
> >> >> >> >> >> dist\SynchronousSampleApplication.zip
> >> >> >> >> >> file created as part of the build process and deployed to the
> >> >> >> deploy
> >> >> >> >> >> directory of JBoss.
> >> >> >> >> >> 7. Restarted the JBoss and there was no errors except that i
> >> >> could
> >> >> >> >> find
> >> >> >> >> a
> >> >> >> >> >> INFO message saying that "INFO
> >> >> >> >> >> [org.apache.servicemix.jbi.framework.AutoDeploymentService]
> >> >> >> Components
> >> >> >> >> >> com.sun.httpsoapbc-1.0-2, com.sun.bpelse-1.0-2 are not
> >> installed
> >> >> >> yet
> >> >> >> -
> >> >> >> >> >> adding ServiceAssembly SynchronousSampleTestApplication to
> >> >> pending
> >> >> >> >> list".
> >> >> >> >> >> 8. I understand that the file that i dropped was picked up by
> >> >> the
> >> >> >> JBI
> >> >> >> >> >> container by "INFO
> >> >> [org.servicemix.jboss.deployment.JBIDeployer]
> >> >> >> >> >> ServiceMix
> >> >> >> >> >> deployer passing deployment to JBI container
> >> >> >> >> >> [file:/C:/jboss-
> >> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >>
> >> 4.0.4.GA/server/default/tmp/deploy/tmp61422SynchronousSampleApplication.zip-contents/com.sun.httpsoapbc-1.0-2.jar
> >> >> >> >> ]
> >> >> >> >> >> ",
> >> >> >> >> >> But later for some reasons it was not able to deploy.
> >> >> >> >> >> 9. I have attached a zip file containing the following items
> >> for
> >> >> >> your
> >> >> >> >> >> review.
> >> >> >> >> >>
> >> >> >> >> >> SynchronousSampleApplication.zip - Application Sample
> >> generated
> >> >> >> >> through
> >> >> >> >> >> NetBeans
> >> >> >> >> >> Jboss_SM_NB.txt - containing the snippet of the
> >> server.logfile
> >> >> >> after
> >> >> >> >> >> JBoss
> >> >> >> >> >> starts.
> >> >> >> >> >>
> >> >> >> >> >> It would be great help and would appreciate if i can get a
> >> >> solution
> >> >> >> >> for
> >> >> >> >> >> this.
> >> >> >> >> >>
> >> >> >> >> >> Thanks, Sat
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >>
> >> http://www.nabble.com/user-files/235730/BPEL_Analysis.zipBPEL_Analysis.zip
> >> >> >> >> >> --
> >> >> >> >> >> View this message in context:
> >> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >>
> >> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5953389
> >> >> >> >> >> Sent from the ServiceMix - User forum at Nabble.com.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > --
> >> >> >> >> > Cheers,
> >> >> >> >> > Guillaume Nodet
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> View this message in context:
> >> >> >> >>
> >> >> >>
> >> >>
> >> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5953860
> >> >> >> >> Sent from the ServiceMix - User forum at Nabble.com.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > Cheers,
> >> >> >> > Guillaume Nodet
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >> --
> >> >> >> View this message in context:
> >> >> >>
> >> >>
> >> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5954364
> >> >> >> Sent from the ServiceMix - User forum at Nabble.com.
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Cheers,
> >> >> > Guillaume Nodet
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5963885
> >> >> Sent from the ServiceMix - User forum at Nabble.com.
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > Cheers,
> >> > Guillaume Nodet
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124.html#a5965058
> >> Sent from the ServiceMix - User forum at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
> >
>
> --
> View this message in context: http://www.nabble.com/ServiceMix%2BJboss---Unable-to-run-BPEL-project-created-using-netbeans-tf2155124s12049.html#a9060063
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/