March 2008 - jboss-user - Jboss List Archives

[JBoss jBPM] - Re: BPEL beta2 - JBOSS 4.0.4 - JWSDP?

by alex.guizar＠jboss.com

If the warnings become annoying, you can filter them out in the log4j config file. Look for it under jboss-home/server/default/conf/log4j.xml. Add the following category: <category name="org.hibernate.engine.StatefulPersistenceContext.ProxyWarnLog"> | <priority value="ERROR"/> | </category> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134446#4134446 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134446

18 years, 1 month

1
0
0 / 0

[JBoss jBPM] - Re: BPEL beta2 - JBOSS 4.0.4 - JWSDP?

by alex.guizar＠jboss.com

Yogesh, which problem are you referring to? If it is the ProxyWarnLog messages, just ignore them. They do not interfere with the operation of the product. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134445#4134445 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134445

18 years, 1 month

1
0
0 / 0

[JBoss jBPM] - Re: jBPM BPEL 1.1 GA - should bpel2 samples work?

by alex.guizar＠jboss.com

As mentioned in the user guide, wstools has a number of limitations. Use wscompile instead. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134444#4134444 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134444

18 years, 1 month

1
0
0 / 0

[JBoss jBPM] - Re: Help in Excecuting Hello World BPEL Example

by alex.guizar＠jboss.com

Yogesh, please do not cross post. It makes tracking an issue very hard. I've already replied to your question in your other post. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134443#4134443 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134443

18 years, 1 month

1
0
0 / 0

[JBoss jBPM] - Re: problem in invoking of a web service

by alex.guizar＠jboss.com

I don't see a closing </ definitions> tag in Process1Artifact.wsdl. Plus, your imports seem quite messy. One of them does not have the location attribute, and other references the parent directory (../). Make sure all your imports have a location attribute, and verify the location is either an absolute URL or a relative path from the process document inside the process archive. I doubt Goodbye.wsdl is being included in the process archive, hence it will not inaccessible to the BPEL reader. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134442#4134442 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134442

18 years, 1 month

1
0
0 / 0

[JBoss jBPM] - Re: Please help~~problem when invoking bpel process~~

by alex.guizar＠jboss.com

Why are you running wscompile yourself? The deployment module in the jBPM BPEL console does that for you on the server side. Is it to create the artifacts for the client side? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134440#4134440 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134440

18 years, 1 month

1
0
0 / 0

[JBoss jBPM] - Re: Problem in Running JBPEL Client Component

by alex.guizar＠jboss.com

Did you deploy the J2EE application client on the server (xxx-client.jar) ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134439#4134439 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134439

18 years, 1 month

1
0
0 / 0

[JBoss jBPM] - Re: BPEL2 --> Error in examples

by alex.guizar＠jboss.com

jbpm-bpel-1.1.GA was upgraded to support the final BPEL 2.0 standard not long before its release date. Due to time limitations, however, the examples were not upgraded as well. We have fixed them and the corrected versions are available from CVS. http://fisheye.jboss.com/browse/JBPM/jbpm.3/bpel/examples Note that you do not need to check out the entire repository, just the files in the bpel2 directories. Then overwrite the corresponding files in the distribution. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134438#4134438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134438

18 years, 1 month

1
0
0 / 0

[JBoss Messaging] - Re: MDBs not getting messages after long run

by mpr_prabhu

We had the same problem occur few times today. When the problem occurred we just stopped the delivery on the MDB MBean and started delivery again. Everything started working again. Also when the problem occurred we took a ThreadCPUUtilization to see what threads were doing any work and found a daemon thread which was the only one using CPU cycles. The thread dump (before we started re-delivery of messages to MDBs again) of this thread during this period showed Few times we caught the thread doing this Thread: Thread-78 : priority:5, demon:true, threadId:328, threadState:RUNNABLE, lockName:nulljava.net.SocketInputStream.socketRead0(Native Method)java.net.SocketInputStream.read(SocketInputStream.java:129)java.io.BufferedInputStream.fill(BufferedInputStream.java:218)java.io.BufferedInputStream.read(BufferedInputStream.java:235)java.io.FilterInputStream.read(FilterInputStream.java:66)org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)org.jboss.remoting.Client.invoke(Client.java:1634)org.jboss.remoting.Client.invoke(Client.java:548)org.jboss.remoting.Client.invoke(Client.java:536)org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:187)org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:158)org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$acknowledgeDeliveries$aop(ClientSessionDelegate.java:175)org.jboss.jms.client.delegate.ClientSessionDelegate$acknowledgeDeliveries_1767561430588382789.invokeNext(ClientSessionDelegate$acknowledgeDeliveries_1767561430588382789.java)org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)org.jboss.jms.client.delegate.ClientSessionDelegate$acknowledgeDeliveries_1767561430588382789.invokeNext(ClientSessionDelegate$acknowledgeDeliveries_1767561430588382789.java)org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)org.jboss.jms.client.delegate.ClientSessionDelegate$acknowledgeDeliveries_1767561430588382789.invokeNext(ClientSessionDelegate$acknowledgeDeliveries_1767561430588382789.java)org.jboss.jms.client.delegate.ClientSessionDelegate.acknowledgeDeliveries(ClientSessionDelegate.java)org.jboss.jms.client.container.SessionAspect.acknowledgeDeliveries(SessionAspect.java:908)org.jboss.jms.client.container.SessionAspect.handleAcknowledgeAll(SessionAspect.java:399)org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect20.invoke(SessionAspect20.java)org.jboss.jms.client.delegate.ClientSessionDelegate$acknowledgeAll_3428828241771477154.invokeNext(ClientSessionDelegate$acknowledgeAll_3428828241771477154.java)org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)org.jboss.jms.client.delegate.ClientSessionDelegate$acknowledgeAll_3428828241771477154.invokeNext(ClientSessionDelegate$acknowledgeAll_3428828241771477154.java)org.jboss.jms.client.delegate.ClientSessionDelegate.acknowledgeAll(ClientSessionDelegate.java)org.jboss.jms.message.MessageProxy.acknowledge(MessageProxy.java:426)org.jboss.messaging.core.impl.clusterconnection.MessageSucker.onMessage(MessageSucker.java:300)org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:157)org.jboss.jms.client.container.ClientConsumer$ListenerRunner.run(ClientConsumer.java:965)EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)java.lang.Thread.run(Thread.java:595) Once the thread was doing Thread: Thread-78 : priority:5, demon:true, threadId:328, threadState:RUNNABLE, lockName:nulljava.net.SocketInputStream.socketRead0(Native Method)java.net.SocketInputStream.read(SocketInputStream.java:129)java.io.BufferedInputStream.fill(BufferedInputStream.java:218)java.io.BufferedInputStream.read(BufferedInputStream.java:235)java.io.FilterInputStream.read(FilterInputStream.java:66)org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)org.jboss.remoting.Client.invoke(Client.java:1634)org.jboss.remoting.Client.invoke(Client.java:548)org.jboss.remoting.Client.invoke(Client.java:536)org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:187)org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:158)org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$cancelDelivery$aop(ClientSessionDelegate.java:493)org.jboss.jms.client.delegate.ClientSessionDelegate$cancelDelivery_2980985335510575813.invokeNext(ClientSessionDelegate$cancelDelivery_2980985335510575813.java)org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)org.jboss.jms.client.delegate.ClientSessionDelegate$cancelDelivery_2980985335510575813.invokeNext(ClientSessionDelegate$cancelDelivery_2980985335510575813.java)org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)org.jboss.jms.client.delegate.ClientSessionDelegate$cancelDelivery_2980985335510575813.invokeNext(ClientSessionDelegate$cancelDelivery_2980985335510575813.java)org.jboss.jms.client.delegate.ClientSessionDelegate.cancelDelivery(ClientSessionDelegate.java)org.jboss.jms.client.container.ClientConsumer.checkExpiredOrReachedMaxdeliveries(ClientConsumer.java:103)org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:132)org.jboss.jms.client.container.ClientConsumer$ListenerRunner.run(ClientConsumer.java:965)EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)java.lang.Thread.run(Thread.java:595) Any idea what is going on? We use DUPS_OK_ACKNOWLEDGE mode for the MDBs. Does this have anything to do with these or something going on with the clustering? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134437#4134437 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134437

18 years, 1 month

1
0
0 / 0

[JBoss jBPM] - Re: Differentiating partner Services in JBPM BPEL

by alex.guizar＠jboss.com

You will need to declare two different partner links and assign an endpoint reference to each. Endpoint references can be assigned in either the process document itself or the bpel-deployment.xml descriptor. Let me know which way do you want to go and I'll tell you how to do it. Also specify the BPEL version you are working on. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134436#4134436 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134436

18 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user March 2008