Problem deploying an ear

Question

HI all,
I am trying to deploy a JBoss Seam demo on the server using the command line tool and the deployment fails. The trace says:
#1.5 #C000C0A83E3500010000000300961DFFFFFFFFFFFFFFFFFF#1174439328000#com.sap.engine.deployment.proxy.dc.DeploymentProxyDCImpl##com.sap.engine.deployment.proxy.dc.DeploymentProxyDCImpl#######Thread[Thread-9,5,main]##0#0#Error##Plain###Could not deploy C:
Java
SAP
JP1
JC00
j2ee
deployment
SAP_DM
1174439321546_jboss-seam-booking.ear
jboss-seam-booking.ear with properties {}#
#1.5 #C000C0A83E3500010000000500961DFFFFFFFFFFFFFFFFFF#1174439328015#com.sap.engine.deployment.operations.DistributeOperation##com.sap.engine.deployment.operations.DistributeOperation#######Thread[Thread-9,5,main]##0#0#Error#1#/System/Server/Deployment#Java###Could not distribute
[EXCEPTION]
#2#C:
Java
SAP
JP1
JC00
j2ee
deployment
SAP_DM
1174439321546_jboss-seam-booking.ear
jboss-seam-booking.ear#com.sap.engine.deployment.exceptions.SAPRemoteException
     at com.sap.engine.deployment.proxy.dc.DeploymentProxyDCImpl.distribute(DeploymentProxyDCImpl.java:151)
     at com.sap.engine.deployment.operations.DistributeOperation.run(DistributeOperation.java:111)
     at java.lang.Thread.run(Thread.java:595)
Any idea what the problem could be?
Thank in advance,
Siarhei Dudzin

Answer 1

Thank you very much for the link, it was extremely useful!
I have now defined the datasource as following (btw, is vendor_sql ok for HSQL-DB because other options caused unknown vendor exceptions?):
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE data-sources SYSTEM 'data-sources.dtd'>
<data-sources>
    <data-source>
        <data-source-name>bookingDatasource</data-source-name>
        <driver-name>HSQLDB</driver-name>
        <init-connections>1</init-connections>
          <max-connections>10</max-connections>
          <max-time-to-wait-connection>60</max-time-to-wait-connection>
          <expiration-control>
               <connection-lifetime>600</connection-lifetime>
               <run-cleanup-thread>60</run-cleanup-thread>
          </expiration-control>
          <sql-engine>vendor_sql</sql-engine>
          <jdbc-1.x>
               <driver-class-name>org.hsqldb.jdbcDriver</driver-class-name>
               <url>jdbc:hsqldb:.</url>
               <user-name>sa</user-name>
               <password></password>
          </jdbc-1.x>       
    </data-source>
</data-sources>
I've also defined a driver name HSQLDB via telnet console.
Now I am getting NameNotFoundException:
[EXCEPTION]
#1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 8459050:com.sap.engine.services.orpersistence.container.deploy.ActionException: Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:, the whole lookup name is jdbc/java:/bookingDatasource.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:260)
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:625)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:638)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:209)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:183)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:130)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:78)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:77)
     at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:181)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:233)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:193)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:405)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:259)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:535)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3070)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3043)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:98)
     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.P4Message.process(P4Message.java:253)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:109)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:841)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:125)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:59)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
Any idea why the datasource is suddenly not found? I tried to find jndi tree but without much success. I did however find that HSQLDB and bookingDatasource are registered under "Application Resources" in the web management console...
I understand that I still have to go a long path in porting this example on SAP Netweaver (will have to switch to SAP JPA, etc), but once this is ported the results may be very fruitful