[jboss-user] [Clustering/JBoss] - broadcast packet flooding the network

2009-08-05 Thread ywtsang
we are using jboss-4.2.0.GA , internal gigabit network usually we have deployed 3 jboss, all in a cluster, and it works perfectly and recently, we have deployed more jboss, but in a different cluster (i.e. using a different cluster name), and find that the broadcast packets in the network

[jboss-user] [Clustering/JBoss] - Re: broadcast packet flooding the network

2009-08-05 Thread ywtsang
more information we only use the jboss for clustered stateless session bean (ejb3) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4248274#4248274 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4248274

[jboss-user] [EJB/JBoss] - do not auto commit after method is returned

2008-12-21 Thread ywtsang
jboss 4.2 ejb 3 stateless session bean transaction = container managed, REQUIRED using jboss-spring interceptor to inject dependencies (e.g. the hibernate dao) to the session bean we are using ejb 3 stateless session bean to wrap the hibernate codes to do database CRUD (just simple hibernate,

[jboss-user] [EJB/JBoss] - Re: do not auto commit after method is returned

2008-12-21 Thread ywtsang
persistence.xml: | persistence xmlns=http://java.sun.com/xml/ns/persistence; |xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; |xsi:schemaLocation=http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd; |version=1.0 |

[jboss-user] [EJB 3.0] - ejb client cannot reconnect automatically after a network re

2008-10-24 Thread ywtsang
for normal situation, our ejb client (tomcat) can connect to jboss server successfully e.g. we have 3 jboss in clusters, we are using ejb 3 stateless session bean (clustered), when one jboss is down for deployment, and up again, the client can reconnect to this jboss again but if a network

[jboss-user] [EJB 3.0] - ejb 3 stateless bean current transaction lost randomly

2008-07-28 Thread ywtsang
i have a set of ejb 3 stateless session beans, which all methods are marked as Required for the transaction attributes the session beans just wrap the call of hibernate dao the problem happens sometimes that the calling of getCurrentSession from hibernate complains that the Current transaction

[jboss-user] [JNDI/Naming/Network] - updated jndi name can't refer to the hot deployed codes

2008-04-24 Thread ywtsang
let me describe my situation with some simplification: (jboss4.2.0.GA, ejb3) 1 ear (A.ear) with 1 session bean (ProductManagerBean) is deployed jndi name = A.ear/ProductManagerBean 1 tomcat (tomcat 6.0.13) acts as a client and use the session bean remotely now i updated the session bean code

[jboss-user] [JNDI/Naming/Network] - updated jndi name can't refer to the hot deployed codes

2008-04-24 Thread ywtsang
let me describe my situation with some simplification: (jboss4.2.0.GA, ejb3) 1 ear (A.ear) with 1 session bean (ProductManagerBean) is deployed jndi name = A.ear/ProductManagerBean 1 tomcat (tomcat 6.0.13) acts as a client and use the session bean remotely now i updated the session bean code

[jboss-user] [Management, JMX/JBoss] - Re: JBoss Server Response Time

2007-06-11 Thread ywtsang
Is there any answer for this question? As I find that some comerical monitoring software can show the Server Response Time for JBoss, I think it would be possible to get the Server Response Time by ourselves. (In my opinion, the Server Response Time for JBoss can mean the response time for

[jboss-user] [Management, JMX/JBoss] - Re: JBoss Server Response Time

2007-06-11 Thread ywtsang
Is there any documentation/reference about the MBean details under jboss.management.local? I can get the statistics of stateless session bean from your guideline (from the other thread by following the source code of twiddle), but I also want to know the complete reference of the details of

[jboss-user] [Management, JMX/JBoss] - Invocation Statistics of EJB

2007-06-08 Thread ywtsang
From the web-console, I can see the Invocation Statistics of each EJB (session, entity, whatever). The statistics show the mix time/max time/total time/avg time/number of invocation of each method inside the EJB. At that page, it links to the corresponding jmx-console page of that MBean of the