1 of 1 people found this helpful
Your client setup is wrong, you can not use the JNP protocol with AS7/EAP6.
You need to change to ejb-client or remote-naming.
I have changed the code n gave proper jar file..
InitialContext ctx =
BookHome home = (BookHome) ctx.lookup(
now m not getting any exception but this message:
12:38:36,052 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-1
12:38:38,194 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-2
12:38:38,460 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting
12:38:45,601 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found BookCatalog.jar in deployment directory. To trigger deployment create a file called BookCatalog.jar.dodeploy
12:38:45,743 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
12:38:45,774 INFO [org.xnio] XNIO Version 3.0.7.GA-redhat-1
12:38:45,790 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1
12:38:45,836 INFO [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1
12:38:46,243 INFO [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin Subsystem
12:38:46,243 INFO [org.jboss.as.security] JBAS013171: Activating Security Subsystem
12:38:46,258 INFO [org.jboss.as.clustering.infinispan] JBAS010280: Activating Infinispan subsystem.
12:38:46,274 INFO [org.jboss.as.osgi] JBAS011906: Activating OSGi Subsystem
12:38:46,430 INFO [org.jboss.as.webservices] JBAS015537: Activating WebServices Extension
12:38:46,477 INFO [org.jboss.as.naming] JBAS011800: Activating Naming Subsystem
12:38:46,477 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
12:38:47,586 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.13.Final-redhat-1)
12:38:47,962 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
12:38:48,041 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
12:38:48,087 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
12:38:49,603 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-localhost/127.0.0.1:8080
12:38:50,933 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
12:38:53,497 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.6.GA-redhat-2
12:38:54,357 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-eap-6.0\standalone\deployments
12:38:54,357 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "BookCatalog.jar"
12:38:54,435 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:4447
12:38:54,435 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:9999
12:38:55,716 INFO [org.jboss.as.osgi] (MSC service thread 1-2) JBAS011907: Register module: Module "deployment.BookCatalog.jar:main" from Service Module Loader
12:38:57,335 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "BookCatalog.jar"
12:38:57,460 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
12:38:57,460 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
12:38:57,460 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 23142ms - Started 157 of 240 services (82 services are passive or on-demand)
12:39:28,273 INFO [org.jboss.as.naming] (Remoting "xin009oaa75197" task-2) JBAS011806: Channel end notification received, closing channel Channel ID 24ad23da (inbound) of Remoting connection 01daca94 to null
can you pls tell me the reason for getting this null value?
your lookup should be "earname/jarname/BeanName!BeanInterface"
as you deploy a jar the ear name can be empty and you start wirh "/BookCatalog/...."
But I don't see that the application (bean) is deployed. Do you deploy a EJB2 Entity with CMP? In that case you need to start with the standalone-full.xml configuration.
No i am not using CMP.. M creating simple ejb n client pgm using ejb 2.1 stateless session bean.
Two xml files i hv created
There is nothing much in project. As i am new to jboss so creating simple application to learn the structure n flow of ejbs on jboss 6.0 eap server.
Can u pls share some learning stuff also with me. how can i deploy ejb 2.1 on jboss 6.0.1 eap?
You might use the quickstarts in JDF and deploy a EJB3 first.
EJB2 SLSB can be deployed in the same way as in older JBoss versions.
But you should see the log messages show the JNDI names.
So the ejb2 app should deploy (but with different JNDI names)
Ok thanks my main task is to migrate ejb2.1 application which contains .ear ( war and 2 ejbs) from weblogic 9.2 to jboss eap 6.0.1
Would u suggest me the steps that i can follow to accomplish my task as soonas possible.
If you start with a working example this will show how the EAP6 behaviour is.
After that I would drop the ejb2 application to the eap6 server and see what happen, the first thing is that you should see the application is deployed and the JNDI names are bound (which is not the case in your log)
So deploy a working example first to see the behaviour.
i tried to run the ejb 3 example using maven and the examples run successfully. But i am not finding any example for ejb 2. Can you pls share or drop ejb 2 application to jboss eap 6.0.
Can you also explain the structure of ejb2 with jboss eap 6. Do ejb 2.0 uses same jboss-ejb3.xml file or there is some other name conventions?
1 of 1 people found this helpful
From what I know there is no EJB2 guide or documentation for JBoss AS7/EAP6. You might search the forms for different issues.
Most important things are
- the DD jboss.xml is not longer evaluated
- some configurations can be done in jboss-ejb3.xml
- use the *full* profile if you have CMP entities
- container configurations of standardjboss.xml (former versions) are not longer supported
As I said befor a simple EJB2 application which is deployable in former AS versions should be work with AS7/EAP6
I read from some documents and forums that in jboss-ejb3.xml <jndi -name> element is no longer supported for session beans. is there any other alterantive for this or jboss itself take care of jndi binding for sessin beans? Do we need to do modifications somewhere else?
No, the JNDI naming is standartisized by the EJB3.1 spec and therefore you need to use the standard name app/module/[distinct]/BeanName!view which is described in the documents that I've linked in a previous comment