Running a simple EJB3 project in Websphere 7

Greenhorn

Posts: 2

posted 13 years ago

Number of slices to send:

Optional 'thank-you' note:

Send

Hello,

I'm trying to develop and deploy a simple EJB Hello-world-kind-of application in Websphere 7. Currently, I am in the state that it runs fine in Tomcat with OpenEJB, but not in Websphere. I wonder what I'm doing wrong.

Overall, I just create an EJB, pack it into a JAR, and then try to use it in a servlet page.

This is the content of my ejb-package:

Interface:

Implementation:

This comes into a jar and is then used in my servlet:

Of course, in the web.xml nothing spectacular happens, I just map the servlet to a path, and that'd it. If I deploy this in Tomcat 5.5.27, I get the expected output on the servlet page:

This is my stateless session-EJB: Hello World!

But if I deploy this in Websphere 7, I get the output:

Error 500: java.lang.NullPointerException

In the SystemOut.log, I get:

[16.07.10 17:28:55:190 CEST] 00000017 webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet-Fehler]-[MeinServletName]: java.lang.NullPointerException
at myservletpkg.MyServlet.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:718)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1655)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:937)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:500)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3810)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:183)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:455)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:384)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:272)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)

Does Websphere expect something which I didn't do? I also tried to deploy with a WAR inside of an EAR, but that didn't change anything.

Klaus Kroener

Greenhorn

Posts: 2

posted 13 years ago

Number of slices to send:

Optional 'thank-you' note:

Send

The problem was not where I searched it. It was in the web.xml where I defined my servlet. The tag didn't have any attributes, but it needs to have the attribute "version", thus looking like , and the value of this attribute needs to be at least 2.4 .

eat bricks! HA! And here's another one! And a tiny ad!

a bit of art, as a gift, that will fit in a stocking

https://gardener-gift.com