... and then if you restart the server your list of undeployed services is huge and seems to be caused by an earlier error when the server is starting up:
2006-07-17 16:08:46,251 ERROR [org.jboss.deployment.MainDeployer - 961] Could not create deployment: file:/C:/APPS/jboss-4.0.4.GA/server/all/deployJBoss/jbossweb-tomcat55.sar/jboss-service.xml org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.system:service=ThreadPool
It is hard when one wants to go from one release to another. Please helpt me! I am running JBoss from JBoss Eclipse IDE 1.6. Could this interfere?
The second error is my own wrong doing...
I forgot to remove some old configuration from the build script. But the first deployment-waiting is still a mysteri...
I don't think that the par extension is valid any more for persistence archives. Rename it to concept.jar.
Thanx! After looking a bit on the trailblazer, it confirmed your story.
But still... What am I doing wrong...
To deploy the entity beans in an application, you can just package their class files in a JAR file. The EJB 3.0 specification also requires a persistence.xml file in the META-INF directory of the JAR file. The persistence.xml file defines which database is used with those entity beans and specifies the default behavior of the EntityManager.
In my deploy nothing happens. The server do not react to concept.jar being copied to the deploy folder. The jar has a META-INF folder and has a MANIFEST.FS and a persistence.xml there. But nothing... Ideas?
JBoss is giving the reply that it is starting the J2EE application if you deploy them within an ear, but I am unable to use them with an ejb (previously deployed in a ejb3-archive) and the exception is NameNotFoundException: 'bean' not bound.
I suspect this is because JBoss is trying to deploy the EJBs before it has deployed the entity manager (the persistent beans) and is therefore unable to deploy the EJB. I had the same problem on the 4.0.3, but solved this by deploying the par archive outside the ear archive, but this is not a solution anymore since jboss won't deploy a simple jar.
How do I make a deployment to wait untill anoter deployment is done? Do I have to deploy this as 2 different ear archives?
Anyone. Please help!
And where does all the logging go? On the 4.0.3, Hibernate logged a lot when persitent beans where deployed and some other components where logging quite a bit when EJBs where deployed, but know I only get this:
2006-07-19 09:18:03,347 INFO [org.jboss.deployment.EARDeployer - 129] Init J2EE application: file:/C:/APPS/jboss-4.0.4.GA/server/accenture/deploy/concept.ear 2006-07-19 09:18:03,397 INFO [org.jboss.deployment.EARDeployer - 318] Started J2EE application: file:/C:/APPS/jboss-4.0.4.GA/server/accenture/deploy/concept.ear
Is this just another way of telling me that the EJBs are not deployed?
I found the reason for the non-deployment, and I know hope to get some tips on how to fix it.
According to the trailblazer:
All the EJB 3.0 libraries and server-wide configuration files are located in the [server_installation]/server/default/deploy directory...
* The ejb3.deployer/META-INF/persistence.properties file configures the default database for all entity beans and EntityManager in this server. The default is the server's embedded HSQLDB database.
* The ejb3-clustered-sfsbcache-service.xml file contains the MBean configuration for the JBoss Cache service that replicates stateful session beans in a cluster.
* The ejb3-entity-cache-service.xml file contains the MBean configuration for the JBoss Cache service that caches and replicates entity bean objects in a cluster.
When you run the 'all' configuration on the installer, this is not a part of the deployment. I get the ejb3.deployer if I run the ejb configuration on top of the all configuration, but then there is error logging of components allready beeing deployed... I do not need the cluster service and the caching is not necessary, but could be an asset. How do get the all configuration working with ejb3 but with the all configuration?
This is a failure that should not be present and should not be hard for a jboss employee to fix. I also tried to download the zip-file, but this is also without the ejb3.deployer and xml-files...
EJB 3.0 RC6 already comes with JBoss 4.0.4CR2
Where do I download 4.0.4RC2?
Important Note for JBoss 4.0.4 CR2+: You have to use the installer to install EJB 3.0 support in your server. The ZIP installation file of the server does not provide EJB3 support.
Is the JBoss 4.0.4 GA a releace which is later than CR2? If so; how do you provide EJB3 support from the installer?
I have been going through lots of documents on EJB3 and discovered that EJB3 has evolved quite a bit since the 4.0.3SP1 release.
I still need to know how to get jboss 4.0.4.GA to run with EJB3 embedded. How?
Since the implementation of EJB3 has changed, where can I dowload the latest jar files needed?