1 Reply Latest reply on Feb 3, 2006 2:26 PM by zoo

    "FROM not found" EJB-QL errors when deploying to JB4(jdk1.4)

    zoo Newbie

      I'm using JBoss 4.0.3SP1, JDK1.4.2_10 (and EJB2.1) and I'm seeing these errors during deployment of my .ear file to JB4.
      I checked my ejb finders methods for empty queries but they're fine.
      Also, the same "LiveView" code runs just fine when deployed to JBoss3.2.7.
      Any ideas on how to solve this problem ???

      16:15:39,854 INFO [ProxyFactory] Bound EJB Home 'LiveView' to jndi 'ejb/echelon/LiveView'
      16:15:40,776 INFO [STDOUT] org.jboss.ejb.plugins.cmp.ejbql.ParseException: FROM not found
      16:15:40,776 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.parse(EJBQLParser.java:39)
      16:15:40,776 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.compileEJBQL(JDBCEJBQLCompiler.java:153) :
      :
      :
      16:15:40,932 WARN [ServiceController] Problem starting service jboss.j2ee:jndiName=ejb/echelon/LiveView,service=EJB
      org.jboss.deployment.DeploymentException: Error compiling EJB-QL statement ''; - nested throwable: (org.jboss.ejb.plugins.cmp.ejbql.ParseException: FROM not found) at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.(JDBCEJBQLQuery.java:52) at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createEJBQLQuery(JDBCCommandFactory.java:60)
      :
      :
      :
      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.j2ee:jndiName=ejb/echelon/LiveView,service=EJB
      State: FAILED
      Reason: org.jboss.deployment.DeploymentException: Error compiling EJB-QL statement ''; - nested throwable: (org.jboss.ejb.plugins.cmp.ejbq
      l.ParseException: FROM not found)


        • 1. Re: "FROM NOT FOUND" errors
          zoo Newbie

          Eventually figured out what was happening:

          I had several "findAll()" ejb finder methods empty. This works fine under JB3.2.7 but for some reason, JB4 did not implement them for me.

          Had to go through each EJB and manually flesh out the SQL queries for each one.