Win a copy of Secure Financial Transactions with Ansible, Terraform, and OpenSCAP this week in the Cloud/Virtualization forum!

Hardik Mehta

+ Follow
since Jul 31, 2006
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Hardik Mehta


I am trying to deploy an ear file to JBOSS AS (defalut server). The application is the mavenised version of examples of SeamInAction book.

When I copy the file to $JBOSS_HOME/server/default/deploy, I don't get any exception but the application doesn't respond, after some time trying to access the application from the browser gives following in the log...

While deploying with admin-console (http://localhost:8080/admin-console) I get following error messgae:

PS: After this Jboss gets into unusable state. I cannot even access admin-console. I just have to kill it.

ErrorMessage in admin-console:

Error Logs:

11 years ago

While deploying a mavenized application consisting of a parent project, ejb jar project and a web project I have following stack trace in Jboss As ,5.1.0.GA.

I checked that I have the dependency for jboss-el-1.0_02.CR4.jar and the library also contains the class org/jboss/el/util/ReflectionUtil.

Any ideas ? If required, I will also post the pom files of all the projects. They are based on the seam-refimpl project mentioned in the seam FAQ section.

Here the link


Thanks Manuel, for the the explanation.

What I forgot to mention in my first post (which I thought would be assumed, my fault) is that I also deploy the client in the container with the bean. This means and it is also written in the book, that it is deployed in the container (Application Client Container) and DI should be available for that client. I followed this documentation to deploy on glassfish.

Following the similar documentation for JBOSS here, I could get the same client working.

Why shouldn't DI work for stateful beans ? On glassfish forums I was told, may be it is due to the following bug...
Here the contents:

I am using glassfish V3 container.

I have deployed a very simple stateful EJB which is accessible by a client which uses global jndi lookup. But it is not accessible using the @EJB (DI) method.

Also the commandline described in glassfish documentation and other books is also not working for running the client in the ACC (Application client container).

Here the Client code:

The bean is code is like following:

After deploying the bean in the container. I tried following commandlines to run the client.

1. This is described in glassfish documentation and other online material.

2. This works for me when I run the jndi lookup client.

Am I making some mistake ?
Thanks Lalit,

I sorted out this problem. It was a missing jars problem indeed and I ended up with following in my class path:
All the libs are from jboss/client

But after the client started running properly, I got following exception in my server.log

And on client side it looks like following:

Just for info: I installed jboss from

thanks & regards.
11 years ago
I have a simple hello-world EJB3 successfully deployed as web service. I can check it with url: http://localhost:8080/jbossws/services

Following is the client which works for Glassfish but doesn't work for JBOSS

Here is how I execute the client and the error I get:

Do I need to generate something ? Am I missing some jar file(s) ?

11 years ago
Thanks Jaikiran,

I did exactly what the tutorial said, but I get the following error while deploying..

org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/hardik/apps/jboss-5.1.0.GA/server/default/deploy/count-bean.ear/count-bean.jar/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(
at org.jboss.deployment.JBossEjbParsingDeployer.createMetaData(
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(
at org.jboss.dependency.plugins.AbstractControllerContext.install(
at org.jboss.dependency.plugins.AbstractController.install(
at org.jboss.dependency.plugins.AbstractController.incrementState(
at org.jboss.dependency.plugins.AbstractController.resolveContexts(
at org.jboss.dependency.plugins.AbstractController.resolveContexts(
at org.jboss.dependency.plugins.AbstractController.change(
at org.jboss.dependency.plugins.AbstractController.change(
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(
at java.util.concurrent.Executors$
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(
at java.util.concurrent.FutureTask.runAndReset(
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(
at java.util.concurrent.ScheduledThreadPoolExecutor$
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
at java.util.concurrent.ThreadPoolExecutor$
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: aop-domain-name cannot appear in this position. Expected content of session is unordered_sequence: port-component? call-by-value? configuration-name? security-proxy? clustered? home-jndi-name? method-attributes? cluster-config? security-identity? local-jndi-name? ejb-name? local-home-jndi-name? timer-persistence? security-domain? ior-security-config? exception-on-rollback? jndi-name? ejb-timeout-identity? depends* invoker-bindings? {all descriptionGroup}? {unordered_sequence jndiEnvironmentRefsGroup}?

My META-INF/jboss.xml looks like this:

and the META-INF/mydomain-aop.xml like this:

The bean class is the same as posted before, without annotations regarding cacheconfig.

Am I making any mistakes ?

I figured this out after searching.

Here is the documentation link.

I have to use the @CacheConfig annotation.

I am still searching for the way to configure this with xml without using any annotations. Can any body suggest how ?

My bean class looks like this..


I want to check if my stateful bean get passivated/activated as expected and the callbacks are called.

Is it possible in GlassFish, JBOSS to restrict the number of instances created in the pool ?

If yes how ?

thanks & regards.

Thanks Jaikiran,

Exactly this was the problem, I was missing namespace information in the ejb-jar.xml.

Now I changed it according to your link..

Now it works as expected.

Hi thanks for the quick reply.

I checked the deployment logs, and I found something like this...

Look the part after Global JNDI: is empty.


I am following the MasteringEJB4thEdition book, which I downloaded from The Server Site website.

There is a simple example of HelloBean, which works perfectly with GlassFish V3 app server. The same example when deployed on JBOSS fails because of JNDI name lookup.

Is there any rule how the JNDI lookup names in JBOSS are decided if we don't provide any ? I found while googling that it is "<ear-file-name>/<Bean-class-name>/remote" but it doesn't work for me.

Here is the bean

Here is the client I am using:

Here is the error I get while executing the client

Hi Henry,

the expression ,

means that here I am expecting a group (A 1234) or (A ) or the whole group may be absent. But in case, the group is present, I want to extract it as group no. 6.

I think now this makes sense.

Now you are right about qualifying and this solved my problem. Following pattern,

works well and I have correct value for V or group 5.

But still, I wonder how the same pattern works for R or group 4 but not for V or group 5. I think this is because of the weird group A.

But anyway, this has solved my problem and I thank you all who took pain to answer me.

14 years ago