[starksm64]

"elkner" wrote:
Wondering, what those "j2ee rules" are ... ;-)

That you cannot include future specifications.

[starksm64]

The only problem I have with the EJB3Trail.ear is this Type javax.ejb.PreDestroy not present exception:

http://jira.jboss.com/jira/browse/JBDOCS-181

[joel.rosi-schwartz]

The only problem I have with the EJB3Trail.ear is this Type javax.ejb.PreDestroy not present exception:

http://jira.jboss.com/jira/browse/JBDOCS-181

What version of ejb3 are you trying this with. I downloaded EJB3 RC5, built it successfully and used the one in ./build/EJB3Trail/EJB3/build/jar/EJB3Trail.ear. This was run against the JBoss 4.0.4 manual install which had been fixed up as described in the original post. I get the exception as described.

I have a feeling that there are too many configurations being discussed here and if we are not specific it is easy to go off on wild goose chases.

[joel.rosi-schwartz]

The only problem I have with the EJB3Trail.ear is this Type javax.ejb.PreDestroy not present exception:

http://jira.jboss.com/jira/browse/JBDOCS-181

I tried this again, this time using the copy of 4.0.4 that I intalled via the installer and having selected "ejb3" configuration. In this config EJB3Trail does deploy fine.

This brings me full circle to where my investigations started earlier today. There is a change in (or a problem with) the packaging of EJB3 in 4.0.4 that breaks the JBossIDE. please see my earlier post http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934762#3934762

[astronox]

This set of instructions was written originally for the manual install, because it did not come with the EJB 3.0 module. If you tried this on the installer version, I have no guarantee of what will happen.

Honestly, I have tested the default server configuration together with the EJB 3.0 RC5 module and it works fine for me, even up to now. No problems at all. I admit I did not really test the one for the all configuration but I can give you my guarantee that the instructions for the default configuration works. In fact, I had followed that set of instructions and deployed the EJB3Trail.ear successfully without any exceptions before posting this. In general you do not need the all configuration unless you are doing clustering.

You cannot use the installer in Bash because it has no windowing system unless you install X. Well, unless the jar is smart enough to provide a console install if there is no windowing system. This I wouldn't know because I did not try the installer myself in Bash.

[joel.rosi-schwartz]

"AstroNox" wrote:
This set of instructions was written originally for the manual install, because it did not come with the EJB 3.0 module. If you tried this on the installer version, I have no guarantee of what will happen.

Yes, I finally figured this out :-)

"AstroNox" wrote:
Honestly, I have tested the default server configuration together with the EJB 3.0 RC5 module and it works fine for me, even up to now. No problems at all. I admit I did not really test the one for the all configuration but I can give you my guarantee that the instructions for the default configuration works. In fact, I had followed that set of instructions and deployed the EJB3Trail.ear successfully without any exceptions before posting this. In general you do not need the all configuration unless you are doing clustering.

Well then, it is a mystery for me as it does not work here. My guess is that when/we figure it out it will be a slight difference in our setups or procedure. I do not have the bandwidth to be chasing it right now though.

"AstroNox" wrote:
You cannot use the installer in Bash because it has no windowing system unless you install X. Well, unless the jar is smart enough to provide a console install if there is no windowing system. This I wouldn't know because I did not try the installer myself in Bash.

Oh, sorry, it has been a long time since I've worked on Unix box without X, so I did not even consider it.

Thanks for your input, it is truly appreciated!

[aro1976]

I tried 4.0.4.CR2 but didn't have time to figure it out the issues below:
a) after installing using installer I figured out that using the clustered and unclustered version, it didn't come with jboss-srp.jar in the lib, because both EJB3 install options are apparently based on standard and not on all.

I'd like to know if there is a easier way to have srp working or if I should have to install by unziping the standard jboss-4.0.4.CR2, and procedding with EJB3 installation instructions above.

b) even when chosen the clustered install, EJB3 deployer/hibernate comes configured to use hashtable cache instead of jboss-cache.

I'd like to know whether jboss-cache is a better cache for single and clustered deployments, and if it is why it's not enabled by default.

just my thoughts,

thanks in advance!

Alessandro Oliveira
Brazil

[robby80]

FYI:
Finally the manual install of 4.0.4.CR2 with EJB3.0 RC5 works for me when I use the all configuration but still not with default which shows at startup:

...
12:15:51,781 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
12:15:53,765 ERROR [MainDeployer] Could not create deployment: file:/F:/server/jboss/4.0.4.CR2/server/default/deploy/ejb3-clustered-sfsbcache-service.xml
org.jboss.deployment.DeploymentException: Unexpected error during load of: org.jboss.ejb3.cache.tree.PassivationTreeCache, msg=org/jboss/cache/TreeCache; - nested throwable: (java.lang.ClassNotFoundException: Unexpected error during load of: org.jboss.ejb3.cache.tree.PassivationTreeCache, msg=org/jboss/cache/TreeCache)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
...
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassNotFoundException: Unexpected error during load of: org.jboss.ejb3.cache.tree.PassivationTreeCache, msg=org/jboss/cache/TreeCache
at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:527)
...
12:16:04,062 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
12:16:04,421 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@f4688465 { url=file:/F:/server/jboss/4.0.4.CR2/server/default/deploy/ejb3-clustered-sfsbcache-service.xml }
deployer: org.jboss.deployment.SARDeployer@1f7708
status: Deployment FAILED reason: Unexpected error during load of: org.jboss.ejb3.cache.tree.PassivationTreeCache, msg=org/jboss/cache/TreeCache; - nested throwable: (java.lang.ClassNotFoundException: Unexpected error during load of: org.jboss.ejb3.cache.tree.PassivationTreeCache, msg=org/jboss/cache/TreeCache)
state: FAILED
watch: file:/F:/server/jboss/4.0.4.CR2/server/default/deploy/ejb3-clustered-sfsbcache-service.xml
altDD: null
lastDeployed: 1144232153671
lastModified: 1144232153656
mbeans:


12:16:04,750 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
...

As my sample business app works for me I can finally focus on JBossWS. :)

[greening]

"robby80" wrote:

I followed the instruction by AstroNox as given above and when deploying the EJB3.0 TrailBlazer I get

WARN [ServiceController] Problem creating service jboss.j2ee:module=beans.jar,uid=22359683,service=EJB3
java.lang.RuntimeException: No container configured with name 'Stateful Bean''
 at org.jboss.ejb3.Ejb3AnnotationHandler.getStatefulContainer(Ejb3AnnotationHandler.java:198)

For what it's worth, I am long experienced with JBoss and I'm pretty decent with EJB3. I followed both the instructions listed at the top of this thread, for the "default" configuration, and the instructions supplied in jboss-EJB-3.0_RC6-PFD.zip. I get this same error message. No container configured with name 'Stateful Bean''.

I'd prefer not to use the "all" configuration, because it takes forever to boot when I am testing.

What am I doing wrong?

[greening]

I don't need an answer now. I looked at the differences between the manual install version and the installer.jar, and they are pretty significant. I too have moved to the installer.jar file method instead of the manual method. We use ant/maven to deploy JBoss, so I just repackaging the results in a "re-manualized" zip file. It works.

Mentioning this so others don't have to repeat my steps.