cancel
Showing results for 
Search instead for 
Did you mean: 

Simple EJB file giving error while deployment in NW 7.3 EHP 1

raktim_banerjee
Participant
0 Kudos

Hi All,

I have following EJB code :

package com.lex;

import javax.ejb.Stateless;

/**

* Session Bean implementation class TestEJB

*/

@Stateless

public class TestEJB implements TestEJBLocal {

    /**

     * Default constructor.

     */

    public TestEJB() {

        // TODO Auto-generated constructor stub

    }

   

}

This is giving message in developertrace:

#2.0 #2012 09 11 05:10:55:993#+00#Error#com.sap.engine.services.deploy.server.TransactionManager#

com.sap.ASJ.dpl_ds.002038##com.lexmark/home~eartest#C0009DB8AB4031C20000001F00001188#102280550000000038##com.sap.engine.services.deploy.server.TransactionManager#rabanerj#3942##2D593C9C02AD100080A3C71CA3A69259#2d593c9c02ad100080a3c71ca3a69259#2d593c9c02ad100080a3c71ca3a69259#0#Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]#Plain##

Global [startInitiallyApp] operation of application [com.lexmark/home~eartest] failed with errors on server process [102280550].#

#2.0 #2012 09 11 05:10:55:993#+00#Error#com.sap.engine.services.deploy.server.TransactionManager#

com.sap.ASJ.dpl_ds.0020380##com.lexmark/home~eartest#C0009DB8AB4031C20000002000001188#102280550000000038##com.sap.engine.services.deploy.server.TransactionManager#rabanerj#3942##2D593C9C02AD100080A3C71CA3A69259#2d593c9c02ad100080a3c71ca3a69259#2d593c9c02ad100080a3c71ca3a69259#0#Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]#Plain##

Global [startInitiallyApp] operation of application [com.lexmark/home~eartest] finished with errors for [164] ms on server process [102280550] [

>>> without errors <<<] [

>>> without warnings <<<].#

Any idea whats wrong?

Thanks

Raktim

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

There is already a thread for this topic http://scn.sap.com/thread/3172995 without providing a solution.

Since this message occurs here to but the application is working perfectly, I assume the message is not related to the application. There might exist some malconfiguration of the application server.

regards