September 2006 - jboss-user - Jboss List Archives

[Clustering/JBoss] - Re: ejb proxies only contain nodes at deploy time

by bstansberry＠jboss.com

OK, thanks for the details. I was hoping you'd tell me something that would tell me where you're going wrong, but you've basically got a regular client that does JNDI lookups of clustered EJBs. Shouldn't matter whether you do a lookup in local JNDI or HA-JNDI, either way you should get a proxy that tracks changes in the cluster topology. A simple explanation would be that the servers aren't clustering properly, but in some cases you are getting proxies that can communicate with both servers, so that tells me that there is communication. And once a server knows about another, if the communication is cut off the surviving server should detect that and update its proxies. And you're not seeing that either. I'll have to think a bit about this to try to come up with an approach to diagnosing the issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971319#3971319 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971319

19 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Seam in production (Tomcat, JSF RI, Hibernate, Tomahawk,

by gavin.king＠jboss.com

This combination should work fine, after a bit of hacking with configurations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971318#3971318 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971318

19 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Binding to existing conversation

by gavin.king＠jboss.com

Also remember to provide the conversation id as a request parameter. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971317#3971317 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971317

19 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: No active application scope in long running process

by gavin.king＠jboss.com

Sure, you just won't be able to use all Seam functionality from the asyn thread. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971316#3971316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971316

19 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: multi portlet setup

by gavin.king＠jboss.com

I don't understand the question. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971315#3971315 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971315

19 years, 7 months

1
0
0 / 0

[Remoting] - Re: Timeout parameter - can I specify timeout per request?

by tom.elrod＠jboss.com

There is no way to do this currently wihtin remoting. However, can add config on client side so that can pass timeout desired per invocation. Have created a jira issue for this to be added in remoting 2.2.0 release - http://jira.jboss.com/jira/browse/JBREM-598 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971314#3971314 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971314

19 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: TROUBLE RUNNING BOOKING EXAMPLE ON TOMCAT

by gavin.king＠jboss.com

OK, something's WRONG in the 1.0.1 GA distribution This is extremely difficult to believe. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971313#3971313 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971313

19 years, 7 months

1
0
0 / 0

[Clustering/JBoss] - Re: Farm deployement problem

by bstansberry＠jboss.com

What AS version? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971311#3971311 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971311

19 years, 7 months

1
0
0 / 0

[Clustering/JBoss] - Re: Jgroups jboss cache deadlock

by bstansberry＠jboss.com

In general, you don't want to synchronize on the cache to do a put. I don't know your use case in enough detail (i.e. who's putting what where when) to absolutely say you shouldn't, but JBC already provides concurrency control at the individual Node level. I don't know what your isCacheActive() call does; perhaps some synchronization is needed there. Blocking in the GroupRequest for a while during cache replication is perfectly normal. The caller thread sends the RPC call out to the cluster, and then blocks waiting for responses that come in separately from each cluster node. Seeing a thread blocking there in a thread dump means nothing. Seeing the thread continually blocking there for a long time over more than one thread dump tells you that for some reason it's taking a while for responses to come back. The issue then is why it's taking a long time to get responses, which could be all sorts of reasons. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971310#3971310 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971310

19 years, 7 months

1
0
0 / 0

[JBoss Seam] - Re: Pageflow - ClassCastException: org.jbpm.graph.node.Start

by gavin.king＠jboss.com

Perhaps you need to use <start-page> instead of <start-state> in your process definition. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971309#3971309 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971309

19 years, 7 months

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 September 2006