I have added a feature to 4.2 whereby if the first attempt to acquire a connection fails, no more attempts will be made, that particular connection destroyed and a new one created right away. This is to address complaints in regards to how we handle validation wherein a large pool with lots of connections will take substantial time to fail through the entire pool before a new connection created.
While timeouts and background validation may help, this option seems to be a decent feature request. This behavior can be turned on/off and is off by default.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004375#4004375
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004375
Hmmm, this:
| Can not make remoting client invocation due to not being connected to server.
| at org.jboss.remoting.Client.invoke(Client.java:639)
| at org.jboss.remoting.Client.invoke(Client.java:627)
| at org.jboss.jms.client.delegate.DelegateSupport.invoke(DelegateSupport.java:118)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_N5002091796089334799.invokeNext(ClientSessionDelegate$createConsumerDelegate_N5002091796089334799.java)
| at org.jboss.jms.client.container.StateCreationAspect.handleCreateConsumerDelegate(StateCreationAspect.java:153)
| at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect17.invoke(StateCreationAspect17.java)
| at
|
Looks very much like another remoting bug I have replicated here:
http://jira.jboss.com/jira/browse/JBMESSAGING-765
I believe it is a bug in the way remoting handles reference counts for invokers.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004356#4004356
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004356
Cool. Again, you can set that system property to get the desired behavior in the 4.0.5 stuff, but I think the approach is at best pretty weak, and downright f*!@ed up at the worst. If you wanted to do this, you would have to add the following to your run.sh or run.conf script
-Dorg.jboss.asf.jms.useold=true
Again, not the best approach and it was added in haste. I would prefer that it died a quick and swift death.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004352#4004352
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004352
Clebert-
I just tried to deploy the scoped sar in JBAS and it fails, complaining that it cannot find a property editor for ConnectionFactory::setLoadBalancingFactory.
Looking at the code, the method setLoadBalancingFactory() takes a LoadBalancingFactory, but the MBean method takes a String.
I have fixed this, so I can get on with my work. You may want to review my fix since it was very quick.
This tells me one thing, you added an MBean attribute without adding a corresponding test for it.
All new functionality needs to have unit tests, so please could you add a test.
Cheers.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004347#4004347
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004347
First of all thank you for quick responses and for your help!
I need to implement the following layout strategy:
Assume we have some region, containing several portlets with different orders.
Portlets can be only of 2 states: "minimized" and "normal";
Only 1 portlet in reagion can be in "normal" state at a time;
If portlet with order X becomes minimized, portlet with order X+1 must be "normilized"; if X = N; then first-order portlet must be normilized;
If portlet with order X becomes normal, previous normal portlet must be minimized;
By default, portlet with order 0 must be in normal state;
thanks in advance!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004335#4004335
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004335