10x, but what I ment was EJB clustering. The web machine needs to activate an
EJB, and the 2 EJB machines should be configured active/passive
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3954352#3954352
Reply to the post :
Hi
I am accessing an EJB running on JBoss 3.2.6 via HTTP Tunneling. I would like
to put an Apache in front of the JBoss, for high availability.
Can I use the modJK for that? The HTTPInvoker does not support AJP. Does that
mean I have to use mod rewrite?
View the original post :
Well it's my mistake - it works fine with AJP. Of course, the application has
to handle by hand crashes in the container, but still, it works.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3951667#3951667
Reply to the post :
How do I configure a JBoss that runs my web application to access only one
server in the cluster, and access another only if the first one fails? I need
the second machine to be idle unless a crash occurs.
View the original post :
Thank you Nimo. I was looking forward for this solution.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3859392#3859392
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859392
Just to make sure, here is the code in the standardjboss.xml file.
| invoker-proxy-binding
| nameManta-message-driven-bean/name
|
invoker-mbeanjboss.mq:service=JMSProvierLoader,name=MantaJMSProvider/invoker-mbean
|
I guessed that. But do you have any tips on checking what JBoss is doing when
registering an MDB on topics?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858774#3858774
Reply to the post :
The bug was closed. However, I still can't connect JBOss to the Manta topics.
I entered the following configuration in the jms-ds.xml file. Anything else I
need to do?
!-- The JMS provider loader --
DefaultJMSProvider
org.jboss.jms.jndi.JNDIProviderAdapter
!-- The
Sorry about that -
| mbean code=org.jboss.jms.jndi.JMSProviderLoader
| name=jboss.mq:service=JMSProviderLoader,name=JMSProvider
| attribute name=ProviderNameDefaultJMSProvider/attribute
| attribute name=ProviderAdapterClass
| org.jboss.jms.jndi.JNDIProviderAdapter
OK. I understood my error right after posting the response. I've updated
standardjboss.xml.
JBoss starts normally now.
However, the MDB does not recieve any messages, and the ejbCreate message does
not run.
Also, JBoss hangs during shutdown (while trying to undeploy the MDB JAR file).
I'm
Is the version still supported and will there be a 3.2.7?
The link is :
https://sourceforge.net/tracker/index.php?func=detailaid=1081962group_id=22866atid=376687
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858292#3858292
Reply to the post :
YOu are of course correct :-)
Anyway, the Manta guys don't have info on the JBoss integration (I checked with
them first). The dump is (pasted from the server.log):
2004-12-09 10:27:15,649 DEBUG [org.jboss.jms.asf.StdServerSession] initializing
(pool, session, xaSession, useLocalTX): [EMAIL
Did that. Is version 3.2.6 still fixed? (I want to run on this version too, not
just JBoss 4.0).
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858277#3858277
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858277
Hi,
I am trying to integrate JBoss with MantaRay (the open source JMS service). I
want a JBoss MDB to listen to a MantaRay queue/topic.
I have updated the required configuration files, but still, I get a
ClassCastException, when JBoss is attempting to cast Destination into a
SpyDestination.
14 matches
Mail list logo
