J2EE Engine Doesn't Start (exitcode=-11113)

Attempt to start the J2EE engine fails with an exit code -11113 (check dev_* trace file). The exit code -11113 means that a mandatory service has failed to start. You need to check the std_* trace file to determine which service has failed.


Sample Error 1: Core service p4 failed. J2EE Engine cannot be started.

Solution: Check bindHost property using Config Tool.

Navigate to configtool -> Instance -> dispatcher -> services -> p4 -> bindHost
Make sure that a correct value is maintained there. Remove any additional IP(backup IP) maintained.


Sample Error 2: Core service file failed. J2EE Engine cannot be started.

Caused by: org.omg.CORBA.INITIALIZE: cannot instantiate com.sap.engine.system.PortableRemoteObject vmcid: 0x0 minor code: 0 completed: No

Solution: In this example, one of the Java parameters is set incorrectly. The parameter should have been com.sap.engine.system.PortableRemoteObjectProxy instead of com.sap.engine.system.PortableRemoteObject.
Navigate to  configtool -> Instance, Java Parameters and correct it.
In this case, the property should have been -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy


Sample Error 3: Core service security failed. J2EE Engine cannot be started.

Caused by: com.sap.security.api.NoSuchUserAccountException: 
USER_AUTH_FAILED: User account for logonid "j2ee_guest" not found!

Solution: You are likely to face these problems if you have made changes to the user at the data source or changed the data source itself. Example: You have deleted the user; if using dual stack changed to some other client number; changed the data source to LDAP.

Follow these instructions:
http://wiki.sdn.sap.com/wiki/display/JSTSG/(SIM)Q0111

If you see "Io exception: There is no process to read data written to a pipe" in the default trace files, take java thread dumps. See if you find java.net.Inet6AddressImpl in the thread dumps. The JDK is configured to use IPv6. If the network environment is not configured to use IPv6, the threads that are showing the java.net.Inet6AddressImpl* classes are hanging. add "-Djava.net.preferIPv4Stack=true" to the JVM setting using config tool and restart the cluster.

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are created i
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,
Read more