[jboss-user] [Performance Tuning] - Re: Increase jboss Memory

Eelshereif, Try out with this: JAVA_OPTS=$JAVA_OPTS -Xms4096m -Xmx4096m -XX:+UseParallelGC -XX:ParallelGCThreads=5 -verbose:gc Daniel View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4214029#4214029 Reply to the post :

[jboss-user] [Performance Tuning] - Re: Datasource Recovery

Sambit, Rigth now you can do a re-deploy of you datasource from jmx-console. And could be interesting for you this open source product: http://www.jboss.org/jopr/ take a look! Regards, Daniel View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4212945#4212945

[jboss-user] [Performance Tuning] - Re: Datasource Recovery

Hi Sambit, When DB is running again then just make a touch to datasource file. This will redeploy all mbean related with datasource and restart conection pool. After this touch your system will work fine again. Daniel View the original post :

[jboss-user] [EJB/JBoss] - Re: Java 6 corrupted stream - help needed

Mark, If you can't migrate JBoss AS version then keep using Java 5. Precisely the problem is with javaws, this services is incompatible with Java 6. Regards, Daniel View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4212742#4212742 Reply to the post :

[jboss-user] [EJB/JBoss] - Re: Java 6 corrupted stream - help needed

JBoss 4.0.4 not support Java 6. Migrate to a newer JBoss version. Daniel View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4212451#4212451 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4212451

[jboss-user] [EJB/JBoss] - Re: EJBs in a Load Balanced Environment

It really easy!. 1) Make your EJB clusterized -- Add Annotation @Clustered on any EJB 2) copy cluster-service.xml from all to default 3) copy ejb3-clustered-sfsbcache-service.xml from all to default (if you have SFSB) 4) and finally modify you jndi.properties change port from 1099 to 1100. (on

[jboss-user] [EJB/JBoss] - Re: EJBs in a Load Balanced Environment

Check this link: http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Clustering_Guide/beta422/html/index.html Daniel View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4194136#4194136 Reply to the post :

[jboss-user] [Performance Tuning] - Re: JBoss 4.3 start up time information

We have same problem with a Sun T2000. We're lost with it. If you found a solution let me know. tks. Daniel View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4192665#4192665 Reply to the post :

[jboss-user] [EJB/JBoss] - Re: EJB with infinite loop does not timeout

1) thinks in JMS for decouple APPs. 2) SLSB not support @Remove. Remove is a SFSB event. regards, DC View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4097016#4097016 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4097016

[jboss-user] [EJB/JBoss] - Problems using Extended Persistence Context

I'm using EXTENDED Persistence Context with a SFSB, expecting that the lifecycle of the persistence context is binded to the lifecycle of the Stateful Session Bean but this dont work. I'm get org.hibernate.LazyInitializationException in the second lap, this is the same method invocation with

[jboss-user] [EJB/JBoss] - Re: Problems using Extended Persistence Context

waynebaylor: that for you help! But see my method grabar(), this is annotated with @Remove, for flush every modification, then the original bean is detroyed and I need new one. The SFSB make the work of keep a conversation (like seam do). View the original post :

[jboss-user] [EJB/JBoss] - Re: Problems using Extended Persistence Context

ummm... @Remove not is a callback method, like PreDestroy, etc. @Remove is the only one called by code, not by container. Thanks any way, Daniel View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4091708#4091708 Reply to the post :