[JBoss Cache] New message: "Re: Jgroups configuration"
by parmod mehta
User development,
A new message was posted in the thread "Jgroups configuration":
http://community.jboss.org/message/532665#532665
Author : parmod mehta
Profile : http://community.jboss.org/people/parmodmehta
Message:
--------------------------------------------------------------
Basically the problem is I have 4 instances of JBoss running on 4 different machines e.g. 100.1.1.1, 100.1.1.2, 100.1.1.3, and 100.1.1.4. When the application loads all I see on 4 servers.
Received new cluster view: [192.168.2.2:58456|0] [192.168.2.2:58456]
This suggest individual instances have not discovered each other. Before I ask sysadmins if the multicast is configured is there anything else I am missing. Here is udp snippet I am using for node discovery
mcast_addr="${jgroups.udp.mcast_addr:228.10.10.10}"
mcast_port="${jgroups.udp.mcast_port:45588}"
thanks
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/532665#532665
16 years, 4 months
[JCA] New message: "Re: HornetQ RA integration"
by Vicky Kak
User development,
A new message was posted in the thread "HornetQ RA integration":
http://community.jboss.org/message/532659#532659
Author : Vicky Kak
Profile : http://community.jboss.org/people/vickyk
Message:
--------------------------------------------------------------
> timfox wrote:
>
> We're discussing this here:
>
> http://community.jboss.org/message/532625#532625
>
> AIUI (Jeff please correct me if I am wrong), the JBoss JCA impl is calling getXAResource() even though no work is being done as part of an XA tx, which seems incorrect to me
>
Yes it does call the getXAReosource() on the MC even if there is not TX propagation. Here is the code which does it
org.jboss.resource.connectionmanager.TxConnectionManager::createConnectionListener()
http://anonsvn.jboss.org/repos/jbossas/trunk/connector/src/main/java/org/...
Also the JCA interacts with the XASession's i.e which I assume are the XAResource via the TM, the TM could interact with the XAResources only when it is enlisted.If the TX is not propagated and JCA getting the XAResource and not making it available(by enlisting it in TX) should not have any effect AFAIU, I don't know how it is affecting TCK.
Yes as per the JCA specs we should not be calling the getXAResource on MC if there is not a TX propagation, this looks a bug to me also.
Jeff, are you able to get things working as it had been done in jboss messaing.
I could try making the changes in JCA but it might need more time for testing etc, I will raise a discussion about it in design forums too so that we hear more from otheres.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/532659#532659
16 years, 4 months
[JBoss Messaging] New message: "MDB reconnect problem after channel restarted"
by Cynthia Wong
User development,
A new message was posted in the thread "MDB reconnect problem after channel restarted":
http://community.jboss.org/message/532652#532652
Author : Cynthia Wong
Profile : http://community.jboss.org/people/cynw
Message:
--------------------------------------------------------------
On my JBoss server which configured to use the IBM Resource Adapter to connect to MQSeries, the Message Driven Bean does not get reconnected after the MQ channel restarted. I need to restart the Jboss server to get it working again. There are no messages shown in the log to indicate any reconnection ever attempts. Even messages were inserted into the queue, nothing is received by the Message Driven Bean, onMessage(), after the channel restored. Not sure what have been missing. I attach the version and configuration details in the attachment. I also posted this on the JCA forum. There is not much documentation around this area. Please help if anyone has IBM Resource Adapter reconnection works before on JBoss Server.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/532652#532652
16 years, 4 months
[jBPM] New message: "Re: jBPM 4.3 and Spring integration - multiple transaction managers"
by Patricia B
User development,
A new message was posted in the thread "jBPM 4.3 and Spring integration - multiple transaction managers":
http://community.jboss.org/message/532650#532650
Author : Patricia B
Profile : http://community.jboss.org/people/patriciab
Message:
--------------------------------------------------------------
Thank you for your reply.
I debugged the issue, and the problem seems to be on the SpringContext.java (line 60 I think), when it loads Spring beans from the context. In my case, there are 2 implementations for transaction manager. So, when running the app, SpringContext finds more than one transaction managers defined on the context, it takes the first one that it comes on the array, but gives me the warning I posted originally.
The fix I see here, is to be able to specify which Spring bean name to load when there are multiple transaction managers defined on the context.
If you have a different solution for this problem, I appreciate it.
Below is a snippet from my context.xml and jbpm.cfg.xml:
<!-- context.xml ---->
<bean id="transactionManager"
class="org.springframework.orm.hibernate3.HibernateTransactionManager"
p:sessionFactory-ref="applicationSessionFactory">
</bean>
<bean id="SisStageTransactionManager"
class="org.springframework.orm.hibernate3.HibernateTransactionManager"
p:sessionFactory-ref="sisStageSessionFactory">
</bean>
<bean id="springHelper" class="org.jbpm.pvm.internal.processengine.SpringHelper">
<property name="jbpmCfg" value="jbpm4/jbpm.cfg.xml"/>
</bean>
<bean id="processEngine" factory-bean="springHelper" factory-method="createProcessEngine" />
<!-- jbpm.cfg.xml ---->
<jbpm-configuration>
<import resource="jbpm.default.cfg.xml" />
<import resource="jbpm.businesscalendar.cfg.xml" />
<import resource="jbpm.tx.spring.cfg.xml" />
<import resource="jbpm.jpdl.cfg.xml" />
<import resource="jbpm.identity.cfg.xml" />
<import resource="jbpm.jobexecutor.cfg.xml" />
<import resource="jbpm.default.scriptmanager.xml" />
</jbpm-configuration>
<!-- context.xml ---->
Thanks,
Patricia
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/532650#532650
16 years, 4 months
[Beginner's Corner] New message: "How to logout & make users re-login"
by Marcelo Cacace
User development,
A new message was posted in the thread "How to logout & make users re-login":
http://community.jboss.org/message/532645#532645
Author : Marcelo Cacace
Profile : http://community.jboss.org/people/mcacace
Message:
--------------------------------------------------------------
Hi,
I'm trying to logout and force users go to in my custom auth-form avoiding access to my webApp.
I have JBoss 5.1.0 with JAAS , jdk1.6.0_17, GWT on clients , IE 7 & FF 3.6
My LoginContext.logout() doesn't throw any exception.
I tried to fix this cleanning credentials and principals,
setting callbackhandler's name/password to null from my subject,
setting DefaultCacheTimeout to zero but I didn't fix this.
I only could destroy cookie jsessionid in IE 7, but I doesn't work on FF 3.6, so it's not a polite way.
Can anyone help me please ?
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/532645#532645
16 years, 4 months