[JBoss Portal] - Integration of jBPM, drools, JBoss ESB with JBoss portal
by niravn
Hi,
We have a BPM application running from 2-3 years. We are using jBPM, Drools, Liferay tomcat portal as a server, Orbeon xForms as UI, Hibernate, Quartz schedular, Axis ws, MULE as an ESB.
We are starting newer version of this application and focusing JBoss portal for its base.
Now my question is, Does JBoss portal come with internal jBPM and Drools engine?
If not then is it possible to integrate both of them seperately?
Regards,
Nirav.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209868#4209868
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209868
17 years, 3 months
[JBoss Messaging] - Re: MySQL in Cluster question
by jbabad
I'm labouring this one a bit more, I know... but having seen this in the server.log... I'm trying my luck...
|
| 2009-02-13 10:45:14,913 DEBUG [org.jboss.messaging.core.impl.FailoverWaiter] (WorkerThread#6[192.168.8.125:47389]) org.jboss.messaging.core.impl.FailoverWaiter@128b200 blocking on the failover lock, waiting for failover to start
| 2009-02-13 10:45:15,750 DEBUG [org.jgroups.protocols.MERGE2] (Timer-4,192.168.8.117:7900) 192.168.8.117:7900 is looking for merge candidates, found initial_mbrs=[[own_addr=192.168.8.118:7900, coord_addr=192.168.8.117:7900, is_server=true], [own_addr=192.168.8.117:7900, coord_addr=192.168.8.117:7900, is_server=true]]
| 2009-02-13 10:45:16,360 DEBUG [org.jgroups.protocols.MERGE2] (Timer-9,192.168.8.117:49704) 192.168.8.117:49704 is looking for merge candidates, found initial_mbrs=[[own_addr=192.168.8.118:56013, coord_addr=192.168.8.117:49704, is_server=true], [own_addr=192.168.8.117:49704, coord_addr=192.168.8.117:49704, is_server=true]]
|
Then later on....
|
| 2009-02-13 10:46:14,914 DEBUG [org.jboss.messaging.core.impl.FailoverWaiter] (WorkerThread#6[192.168.8.125:47389]) org.jboss.messaging.core.impl.FailoverWaiter@128b200 releasing the failover lock, checking again whether failover started ...
| 2009-02-13 10:46:14,914 DEBUG [org.jboss.messaging.core.impl.FailoverWaiter] (WorkerThread#6[192.168.8.125:47389]) Timed out waiting for failover to start
| 2009-02-13 10:46:14,915 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (WorkerThread#4[192.168.8.125:47391]) removing callback handler ServerInvokerCallbackHandler[5c4o83h-nlkeqt-fr4rzxwx-1-fr4sagqo-s2g+5c4o83h-nlkeqt-fr4rzxwx-1-fr4sagr5-s2l]
| 2009-02-13 10:46:14,915 DEBUG [org.jboss.remoting.InvokerRegistry] (WorkerThread#4[192.168.8.125:47391]) removed SocketClientInvoker[11aed12, bisocket://192.168.8.125:342501498] from registry
| 2009-02-13 10:46:14,917 DEBUG [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] (WorkerThread#4[192.168.8.125:47391]) SocketClientInvoker[11aed12, bisocket://192.168.8.125:342501498] disconnecting ...
| 2009-02-13 10:46:14,919 DEBUG [org.jboss.jms.server.remoting.ServerSocketWrapper] (WorkerThread#4[192.168.8.125:47391]) wrote CLOSING byte
This has happened, but my client apps still continue to send/receive messages after this. So I assume that it just picked up the same JMS connection and continued?
Thanks again.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209864#4209864
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209864
17 years, 3 months
[EJB/JBoss] - Re: JBoss Messenger upgrade to 1.4.2. GA - MDBs suddenly wan
by mhoennig
I can hardly post all my JBoss configuration. The point is: It DID WORK with JBoss Messenger 1.4.0 and I just upgraded to 1.4.2. I have not changed my other config at all.
But anyway: Here my annotations (... is just a placeholder):
@MessageDriven(activationConfig=
{
@ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination", propertyValue="queue/...Status"),
@ActivationConfigProperty(propertyName="acknowledgeMode", propertyValue="Auto-acknowledge")
} )
public class QueueStatusReceiver
implements javax.jms.MessageListener
Here the relevant part of boss-messaging.sar/destinations-service.xml:
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=...Status"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer
jboss.messaging:service=PostOffice
Which other of the vast amount of configs would you need? As I said, there is not a single word of MQ in any config file. Not a single! And yet, some JBoss part suddenly is asking for it.
Maybe one hint: I am using sslbisocket, but I also used it with 1.4.0 and it did work (just not with PostgreSQL 8.3 anymore - but that's a different problem).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209858#4209858
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209858
17 years, 3 months
[Installation, Configuration & DEPLOYMENT] - Re: War file produces org.apache.commons.logging.LogConfigur
by gauravnsj
Thanks for the reply Peter.
I tried looking in the server log but could not find any thing there.When I am trying your suggested solution browser is showing 404 error but nothing could be seen in console or log.
I tried looking in the jboss console but no error could be seen even there.
What i did is i took the commons.logging jar of my application and jboss 4.0.4 commons logging and found that jar is similar and application is running perfectly fine.
Then I took commons.logging of my application and commons.logging of jboss 4.2.2 and I could make that there is lot of difference between the two and that is the cause I think , and on running the application the error pasted in my first post is comming up.
When I am removing the commons.logging of jboss4.2.2 the server is showing error in starting and when I am removing the commons.logging of my application then this 404 error is comming.I think this commons.logging is must for my application as when I am removing this jar from my application and then running the application in jboss4.0.4 then also this 404 error is comming up.
Could you guide me how can I overcome this problem.
any help would be highly appreciated.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209855#4209855
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209855
17 years, 3 months