| 15:15:51,330 INFO [JmxKernelAbstraction] creating wrapper delegate for:
org.jboss.ejb3.entity.PersistenceUnitDeployment
| 15:15:51,345 INFO [JmxKernelAbstraction] installing MBean:
Hi, I am having a problem when I try to deploy an ear that conatins stateless
session beans exposed as web services on JBoss 4.2.3. The problem only arises
however if I attempt to inject an entity manager or entity manager factory into
the session bean, or if I inject anything that has a
Ok, sorry for the delay in posting this reply. This issue turned out to be a
configuration error in the ra.xml. I had the wrong value in the
messagelistener-type value. Once that was fixed everything deployed fine. I
was even able to include the data source in the ear and have everything
I have a project that uses an inbound resource connector and an message driven
bean. I am trying to deploy these on jboss 4.2.3. The app has the following
layout :
| app.ear
|lib/logic.jar
|ejb.jar
|ra.rar
|
The ra.rar just contains the ra.xml and the manifest
Just a bit more information, in case it is pertinent and not obvious. The rar
is an inbound resource adapter that sends its messages to the MDB in the
ejb.jar. It looks like the rar is not completely deployed (in that the
classloader hasn't been set up) by the time the ejb.jar starts it's
The MDB is packaged in the ejb.jar. It is done with annotations, so there is
no ejb-jar.xml.
For the deployment issue, I read all of the posts about fixing the code for
deployment ordering and then added the module-orderstrict/module-order to
the jboss-app.xml. And the modules are listed in
Ok, then that is a problem I am running into as well.
You have an xml file somewhere that is getting read by JBoss that has the DTD
or schema specification in it. JBoss is supposed to validate against local
files but it doesn't appear to (again, this is with 5.0), instead it tries to
pull
I have seen this problem. It is happening because JBoss cannot get out to
validate an xml file. If you are behnd a firewall this can cause it.
I got past this by passing the following parameters to JBoss 5.
-Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort=
where x.x.x.x is the hostname of
I am tring to create a new JMS provider using the standard jboss provider. I
created a custom myds-ds.xml that contains the following :
| mbean code=org.jboss.jms.jndi.JMSProviderLoader
| name=jboss.mq:service=JMSProviderLoader,name=myJMSProvider
| attribute
