I suppose that you are using EJB2.1, right?
Normally there is no message printed during startup, also the container might not create the bean unless a message is in the queue.
Do you see an activity if you send a message to the queue by client?
Yes, I am using EJB 2.1 .
This same application when it was deployed in weblogic 9.2 server, the startup messages were printed.
Now, we are migrating the application to JBoss 4.3 EAP.
since now the startup messages are not printed, i got worried whether the bean instance is created or not.
Yep, migrating is a difficult and special thing with EJB2.
So you will find a lot of issues where two app server are different if you are a bit beside the spec or where the spec is not very clear.
Where do you log the 'startup' message?
Does the bean is created and handle the message if you fill the queue?
Do you have EAP support? Or just evaluate the EAP version?
I would prefer EAP 5.1. Also you might raise a support ticket if you have a support subscription.
My issue got resolved for the MDB, regarding it's creation.
What is said is right. When we put a message in queue and tested and commented all the logger messages, the message-driven bean instance is created.
Now, the problem is with log4j.properties file.
The properties file is not being picked up by the EJB application .
I tried many ways to put the properties file in all paths, but with no success.
Kindly tell me , where should i put my properties file , so that the application can pick up that.
good to hear that the issue is solved.
For the log4j I use the JBoss configuration conf/jboss-log4j.xml because this is picked up during runtime.
I know that the configuration can packed with the application but I never tried that. You might search for answers in the community
mark this thread as 'answered' and start a new one with the correct subject
My issues are resolved now. Migrated my application successfully to JBoss 5.1 EAP from weblogic 9.2.
Sincere thanks to Wolf-Dieter Fink.
Some points here which may be useful for anyone.
Regarding log4j.properties file, i kept it under the root of the app. The logpath whatever i mention like 'www/mylog/' was being created inside the bin folder of the linux server.
When the logpath starts with forward slash , then it is taking the absolute root path of the server.
I didn't made any changes in the jboss-log4j.xml file.