[ https://issues.apache.org/jira/browse/AXIS2-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned AXIS2-4389: -------------------------------------- Assignee: Andreas Veithen > Axis2 1.5 + EclipseLink + Tomcat 6 = Exceptions, but only sometimes > ------------------------------------------------------------------- > > Key: AXIS2-4389 > URL: https://issues.apache.org/jira/browse/AXIS2-4389 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Affects Versions: 1.5 > Environment: Windows XP SP3/Ubuntu 9.04 64bit server, Tomcat 6.0.x, > Eclipse 3.4.2, Axis 1.5 > Reporter: Greg Logan > Assignee: Andreas Veithen > Priority: Blocker > Attachments: catalina.out > > > From the mailing list: > I'm having this weird problem when I try and use certain Axis2 web > services, but not others. What I'm trying to do is make a call, and > have the service return data from the DB using JPA queries via > Eclipselink. Unfortunately Axis appears to be throwing > NullPointerExceptions for some of the calls and I have no idea why. > I've attached the full exception text, but the top few lines are thus: > [ERROR] java.lang.NullPointerException > org.apache.axiom.om.OMException: java.lang.NullPointerException > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:260) > at org.apache.axiom.om.impl.llom.OMNodeImpl.build(OMNodeImpl.java:335) > which is generated in response to the function: > public Act[] getAllScenes(Common common) throws Exception { > //get the entity manager and begin a transaction > EntityManager em = emf.createEntityManager(); > //Find the appropriate video > Episode ep = em.find(Episode.class, common.getVideoid()); > ... > //Get the list of acts in the video > List<Act> results = t.getScenes(); > if (results == null) { > logger.debug("Error: No list of acts found"); > return null; > } > //Sort them into the appropriate order and return > Act[] ary = new Act[results.size()]; > results.toArray(ary); > Arrays.sort(ary); > em.close(); > return ary; > } > I've tried playing the debug-statement game, and I found that the line > throwing the exception is sometime *after* the return statement - > everything else is valid, including the data being pulled from the DB. > On the flip side, I have a very similar function in a different service > (but still the same Eclipse project, persistence unit, build script and > deployed WAR file) which works fine for no apparent reason. > Is there something here that I'm doing wrong, or anything that stands > out? I've been blocked on this for a couple of days now and I would > really like to be able to make some progress again :) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.