cancel
Showing results for 
Search instead for 
Did you mean: 

Deploying an Application written for SAPWebAS 7.0 on CE 7.1

Former Member
0 Kudos

Hi,

we are facing a problem when trying to deploy an application which runs successfully on the SAP Web Application Server 7.0 on the SAP CE 7.1 Application Server.

The error reads like this:

Exception has been returned while the 'msg.de/msg.eVB' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is: 
	com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 7484250:com.sap.engine.services.deploy.container.DeploymentException: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect QL query: SELECT OBJECT(p) FROM PlausiCustomizingBean AS p
          select object(p) from PlausiCustomizingBean as pselect
                    object(p) from PlausiCustomizingBean p, errors: line 2: unexpected token: select
          select object(p) from PlausiCustomizingBean as pselect
          ^
.
	at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:893)
	at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.makeStartInitially(ContainerInterfaceImpl.java:771)
	at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:184)
	at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:145)
	at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
	at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
	at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
	at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
	at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
	at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
	at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
	at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
	at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
	at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
	at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
	at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
	at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
	at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
	at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
	at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
	at com.sap.engine.services.dc.lcm.impl.RemoteLCMImpl.start(RemoteLCMImpl.java:45)
	at com.sap.engine.services.dc.lcm.impl.RemoteLCMImplp4_Skel.dispatch(RemoteLCMImplp4_Skel.java:233)
	at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
	at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
	at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
	at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
	at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
	at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
	at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
	at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
	at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: com.sap.engine.services.ejb3.container.ActionException: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect QL query: SELECT OBJECT(p) FROM PlausiCustomizingBean AS p
          select object(p) from PlausiCustomizingBean as pselect
                    object(p) from PlausiCustomizingBean p, errors: line 2: unexpected token: select
          select object(p) from PlausiCustomizingBean as pselect
          ^
.
	at com.sap.engine.services.ejb.adapter.DeploymentActions$EntityModuleDeployer.deploySingleJar(DeploymentActions.java:325)
	at com.sap.engine.services.ejb.adapter.DeploymentActions$EntityModuleDeployer.perform(DeploymentActions.java:182)
	at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
	at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
	at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
	at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:887)
	... 30 more
Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect QL query: SELECT OBJECT(p) FROM PlausiCustomizingBean AS p
          select object(p) from PlausiCustomizingBean as pselect
                    object(p) from PlausiCustomizingBean p, errors: line 2: unexpected token: select
          select object(p) from PlausiCustomizingBean as pselect
          ^
.
	at com.sap.engine.services.ejb.deploy.ejbql.QLTranslator.prepareQLContext(QLTranslator.java:162)
	at com.sap.engine.services.ejb.deploy.ejbql.QLTranslator.translateQuery(QLTranslator.java:69)
	at com.sap.engine.services.ejb.deploy.xml.XMLPmGenerator.generateFinderOrSelect2x(XMLPmGenerator.java:527)
	at com.sap.engine.services.ejb.deploy.xml.XMLPmGenerator.generateFinders2x(XMLPmGenerator.java:514)
	at com.sap.engine.services.ejb.deploy.xml.XMLPmGenerator.generateFindMethods(XMLPmGenerator.java:484)
	at com.sap.engine.services.ejb.deploy.xml.XMLPmGenerator.generateXml(XMLPmGenerator.java:169)
	at com.sap.engine.services.ejb.adapter.DeploymentActions$EntityModuleDeployer.deploySingleJar(DeploymentActions.java:313)
	... 35 more

Is the CE 7.1 not backward-compatible to 7.0?

Yours sincerely

Florian

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Florian!

It seems that the EJBQL query is incorrect.

select object(p) from PlausiCustomizingBean as pselect

The object-keyword's parameter must be a valid indentification variable. In you case it should be pselect and not p. Please try the following query:

select object(pselect) from PlausiCustomizingBean as pselect

Best Regards,

Robin

Former Member
0 Kudos

Hi Robin,

you are right, but in the application (ejb-jar.xml) i already wrote:

select object(p) from PlausiCustomizingBean as p

So the error occures when deploying to CE 7.1. It seems it changes the query to:

select object(p) from PlausiCustomizingBean as pselect

Thats the reason for the error. But why, and how can i avoid it?

Greets

Florian

Edited by: Florian Kandlinger on Apr 14, 2008 11:21 AM

Edited by: Florian Kandlinger on Apr 14, 2008 11:22 AM

Former Member
0 Kudos

Sorry, I have no idea why the server would try to change a EJBQL query in a ejb-jar.xml during deployment. I will try to forward your question to one of our EJB-container colleagues.

Best Regards,

Robin

Former Member
0 Kudos

Hi Florian!

Maybe it will be helpful for analyzing the problem if you post the content of your ejb-jar.xml file. However, if you have access to SAP Service Marketplace it would be the best approach to open a trouble ticket on the component BC-JAS-EJB.

Best Regards,

Robin

Former Member
0 Kudos

Hi Robin, here is the relevant content of the ejb-jar.xml:

<entity>
      <ejb-name>PlausiCustomizingBean</ejb-name>
      <local-home>de.msg.evb.ejb.PlausiCustomizingLocalHome</local-home>
      <local>de.msg.evb.ejb.PlausiCustomizingLocal</local>
      <ejb-class>de.msg.evb.ejb.PlausiCustomizingBean</ejb-class>
      <persistence-type>Container</persistence-type>
      <prim-key-class>de.msg.evb.ejb.PlausiCustomizingPK</prim-key-class>
      <reentrant>False</reentrant>
      <cmp-version>2.x</cmp-version>
      <abstract-schema-name>PlausiCustomizingBean</abstract-schema-name>
      <cmp-field>
        <field-name>mandt</field-name>
      </cmp-field>
      <cmp-field>
        <field-name>dtoClassName</field-name>
      </cmp-field>
      <cmp-field>
        <field-name>plausiClassName</field-name>
      </cmp-field>
      <cmp-field>
        <field-name>nsp</field-name>
      </cmp-field>
      <query>
        <query-method>
          <method-name>findByMandt</method-name>
          <method-params>
            <method-param>java.lang.Short</method-param>
          </method-params>
        </query-method>
        <ejb-ql>select object(p) from PlausiCustomizingBean as p
                    where p.mandt = ?1</ejb-ql>
      </query>
      <query>
        <query-method>
          <method-name>findAll</method-name>
          <method-params/>
        </query-method>
        <ejb-ql>select object(p) from PlausiCustomizingBean as p
          <![CDATA[select object(p) from PlausiCustomizingBean as pselect
                    object(p) from PlausiCustomizingBean p
      
      
        
          findByNsp
          
            java.lang.String
          
        
        select object(p) from PlausiCustomizingBean as p
                    where p.nsp = ?1
      
    ]]>

Thanks for your help.

Edited by: Florian Kandlinger on Apr 16, 2008 7:25 AM

Now i saw the error by myself. It seems that the Developer Studio destroyed the xml-file by inserting:

<![CDATA[select object(p) from PlausiCustomizingBean as pselect
                    object(p) from PlausiCustomizingBean p]]>

Strange is also, that the "old" application server has no problem with this.

Ok, problem solved, thanks for your tips Robin.

Answers (1)

Answers (1)

Former Member
0 Kudos

<PRE>

Hi Florian!

Even i am getting the same exception, please advice.

Thanks

Hari Krishna

</PRE>