With multiple consumers on a queue, messages are load balanced between the consumers. As you have some time consuming the message, you should disable buffering by setting consumer-window-size. On hornetQ there’s an example on the distribution, about how to disable client buffering and give a better support for slow consumers. (a slow consumer is a … Read more
This problems are thrown cause of different version of Resteasy Client implementation between your app and Jboss EAP modules. You are using the newest version of jaxrs-client, but JBoss EAP 6.3.0 use very old version (resteasy-jaxrs-2.3.8.Final-redhat-3). Just download latest pack of JBoss Resteasy implementation (sometking like this: resteasy-jboss-modules-3.0.9.Final.zip) and unzip into EAP Modules folder replacing … Read more
Hibernate logging has to be also enabled in hibernate configuration. Add lines hibernate.show_sql=true hibernate.format_sql=true either to server\default\deployers\ejb3.deployer\META-INF\jpa-deployers-jboss-beans.xml or to application’s persistence.xml in <persistence-unit><properties> tag. Anyway hibernate logging won’t include (in useful form) info on actual prepared statements’ parameters. There is an alternative way of using log4jdbc for any kind of sql logging. The above answer … Read more
This is a sign of classpath pollution. JBoss already ships with JSF bundled. This exception can occur if you bundle JSF in your WAR as well. It’ll only collide. There are 2 solutions: Get rid of jsf-api and jsf-impl JARs in your WAR (i.e. they should not end up in /WEB-INF/lib after build/deploy. Tell JBoss … Read more
This is not Mojarra specific. This is Tomcat specific (JBoss uses Tomcat as servletcontainer). Add the following VM argument to startup options. -Dorg.apache.el.parser.COERCE_TO_ZERO=false To my experience, this one should actually only apply on Number properties (int, long, etc), however since a certain late Tomcat 6.0.x version (at least after 6.0.20) it seems to be broken … Read more
NoSuchMethodError usually means you are having two different versions of the class on your classpath. As the javax.ws.rs.core.Application class does have the getProperties() method in its JAX-RS 2 version, but not in JAX-RS 1.x, I would guess that somehow you are combining the old 1.x Jersey (or old REST api) with the current (2.3.1) one. … Read more