jboss5.x

As part of an upgrade from JBoss 4.0.4 to 5.1, I am trying to get a WAR to deploy after an EAR is successfully deployed. JBoss 5.x does not support PrefixDeploymentSorter like 4.x did, which means that I have to use <depends> in the WAR's jboss-web.xml. It seems I cannot depend on the EAR itself, so I pick the last deployed EJB instead. This EJB provides a JNDI entry that the WAR needs. Here's the EJB as it deploys when the WAR is absent from the deploy directory: 2010-03-25 10:47:30,348 INFO [org.jboss.ejb3.session.SessionSpecContainer] (main) Starting jboss.j2ee:ear=my-ear.ear,jar=mypackage

jboss-6.0.0.Final doesn't seem to have jboss-log4j.xml which was used to configure log4j settings in jboss5 (i.e. under server/default/conf/jboss-log4j.xml) Apparently the name and location changed since release 6: In the releases 4.x and 5.x it's located here:JBoss_HOME\server\default\conf\jboss-log4j.xml Since the release 6.0.0 M1 it's located in the deploy folder: JBOSS_HOME\server\default\deploy\jboss-logging.xml Source: http://www.mastertheboss.com/jboss-application-server/251-jboss-log4j-configuration.html if you are using axis2.war the log4j.properties is there in axis2.war/WEB-INF

I am trying to get the instance of a service class bound in jboss-service.xml using MBean. JBoss-Service.xml has defined a BasicThreadPool which we want to use it in our code. This is what it is in JBOSS-Service.xml . <mbean code="org.jboss.util.threadpool.BasicThreadPool" name="jboss.system:service=ThreadPool"> <attribute name="Name">JBoss System Threads</attribute> <attribute name="ThreadGroupName">System Threads</attribute> <attribute name="KeepAliveTime">60000</attribute> <attribute name="MaximumPoolSize">10</attribute> <attribute name="MaximumQueueSize">1000</attribute> <!-- The behavior

I am using Hibernate on a JBoss server. I get the error below. The error happens when I try to connect to the database for the second time in the same sesssion. Also I get the error "Closing connection for you. Please close your connection". 14:28:37,869 ERROR [HibernateUtil] HibernateException occurred in executeQuery method in HibernateUtil class org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java

I use jaxws 2.2.3 and Jboss 5.1 with JDK 6. When calling ws client, I get java.util.ServiceConfigurationError: javax.xml.ws.spi.Provider: Provider org.jboss.ws.core.jaxws.spi.ProviderImpl not found (see full stack trace below) When I remove libs jbossws-native-*.jar from jboss/lib/endorsed everthing works fine. But they must be there. I tried to tell jboss to use com.sun.xml.ws.spi.ProviderImpl: META-INF/services/javax.xml.ws.spi.Provider -Djavax.xml.ws.spi.Provider to read first my libs WEB-INF/jboss-classloading.xml <classloading xmlns="urn:jboss:classloading:1.0" parent-first="false" domain

I've got two questions to ask regarding JBoss 5.1. We are in process of migrating from JBoss 4.2 to JBoss 5.1. We are also using Java 1.6 and JPA 2.0 with Hibernate 3.6 as the provider. My questions are: Is it possible to use Hibernate 3.6+ with JBoss 5.1. If yes, then how? What about JPA 2.0? I know that JBoss 5.1 comes with JPA 1.0 compatibility. Can we use JPA2? And as we can not do any kind of configuration to the JBoss installation, all the fixes need to be done in our application only. Thanks in advance, JassB Do this: 1) Add jboss-classloading.xml to /src/main/webapp (I am using Maven):

Right now in my application,at certain points we are logging some heavy stuff into the log files. Basically only for logging we are creating JSON of the data available and then logging into Log files.This is business requirement to log data in JSON format . Now creating JSON from the data available and then logging to FILE takes lot of time and impacts the original request return time. Now idea is to improve the sitation . One of the things that we have discussed is to create a thread pool using Executors.newSingleThreadExecutor() in our code and then submitting the task to it which does the