[Clustering/JBoss] - Re: JGroups Multiple Registrations
by bstansberry@jboss.com
"kvbisme" wrote : What is confusing to me is that Machine1 is the first machine in the cluster so I am confused what would cause Machine1 to become unresponsive to itself?
It isn't unresponsive to itself, it's unresponsive to other members in the cluster. They decide to remove Machine1 from the group.
anonymous wrote : Is there a particular fix I can point to in JGroups for justification of this upgrade to the boss?
Can't recall anything specific, no. I have an (admittedly vague) memory of a similar issue coming up sometime in the past and moving off of JGroups 2.2.7 helped.
In general, using JGroups 2.4 is recommended. 2.2.7 is very old. We were forced for policy reasons to leave it in all the 4.0.x releases (so for example a 4.0.5 server could interoperate with a 4.0.2). But if it weren't for that requirement, we would have used a much later JGroups release in AS 4.0.5.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137922#4137922
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137922
18 years, 1 month
[JBossWS] - ServiceEndpointInvoker rethrows runtimeexception, headers th
by zach.mabe@cox.com
In version 2.0.3.GA, I am seeing an issue where the org.jboss.ws.core.server.ServiceEndpointInvoker is catching a runtimeexception thrown from within a handler, calling the handleFault operations of the handlers but then rethrowing the exception.
Since this is a runtimeexception, it ends up being passed back out to org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(...) where a new SOAP Fault message is created because (I think) the requesthandlerimpl doesn't repeek the messagecontextstack for a fresh context.
Is this a bug or am I not understanding how it is supposed to work.
The main problem with this is my custom handler throws a WebServiceException when the request isn't valid. I see that the WSAddressingServerHandling is putting the correct ws-addressing stuff in the response. But that response isn't what ends up being sent to the client. The client then complains because the response is missing the action header.
Thanks
Zach Mabe
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137911#4137911
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137911
18 years, 1 month
[Installation, Configuration & DEPLOYMENT] - Re: connection pool configuration ?
by patzerbud
anonymous wrote : Are you saying that after 5 minutes the number of connections falls below 10?
Perhaps, and No. Let me try to clarify what I was trying to say in my previous post:
It only takes about five minutes for all existing connections to the database to be closed and replaced with new ones (the PIDs on the db server verify this). What I suspect is happening is this: connection #10 of 10 (the LRU) has exceeded idle-timeout-minutes so it gets closed leaving only 9 connections in the pool. A different thread notices the number of connections has fallen below the min-pool-size and creates a new one.
This was supposed to be my first question: Why doesn't one hand no what the other is doing? Why have one thread close an "idle" connection if that will cause the number of connections to fall below the specified min-pool-size? The quote in my original post referenced the - to me - confusing section of the documentation that led me to question this. To me the documentation implies that this is what is going on.
Secondly, in my environment ALL connections get closed & replaced and this only takes about 5 minutes. We have approx. 300 simultaneous users accessing the system w/ an auto-refresh configured to take place every 3 minutes. In other words we see about 100 hits per minute. With this kind of activity - why would we see the top n connections get recycled? Shouldn't some of the connections be used over & over and not be idle? This is based on my understanding of the MRU strategy used to dole out connections from the pool.
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137910#4137910
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137910
18 years, 1 month
[Persistence, JBoss/CMP, Hibernate, Database] - Re: could not insert exception in JBOSS 4.2.2 GA ...
by sajhak
thanks to u , i got it right this time ...
and thought of describing the method i followed for the help of any other , who might need this in the future..
what i did was i add the following property to persistence.xml
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect" />
also , as u said ,
<property name="hibernate.hbm2ddl.auto" value="update"/>
too..
so this works fine.Even i restart the JBOSS server , the table is persistent in the database..
But , if i used
<property name="hibernate.hbm2ddl.auto" value="create-drop"/>
instead. ( which i tested by using it earlier ) and , when the JBOSS restarted the table will be created from the beginning , when the JBOSS is shutdown , the table is vanished.
regds
Saji
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137893#4137893
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137893
18 years, 1 month