Previous     Contents     Index     Next     
iPlanet Market Maker 4.5 Installation Guide



Appendix A       Troubleshooting


This chapter offers installation troubleshooting tips.

The following sections are contained in this chapter:



Installation Error


Error
ClassNotFoundException for RFxDisplayModule on the iPlanet Market Maker login page.


Fix
When bringing up the iPlanet Market Maker login page, the following stack trace is displayed instead:



Cannot include error file (defaultErr.jsp).
Exception in errorFileInclude:
VortexException Stack--------
Unexpected exception chaining .jsp
--------
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.(Compiled Code)
at java.lang.Exception.(Compiled Code)
at com.iplanet.ecommerce.vortex.arch.VortexException.(VortexException.java:52)
at com.iplanet.ecommerce.vortex.arch.VortexException.(VortexException.java:125)
at com.iplanet.ecommerce.vortex.display.util.DispatcherHelper.dispatch(Dispatche Helper.java:118)
at com.iplanet.ecommerce.vortex.display.BaseServlet.errorFileInclude(BaseServlet java:432)
at com.iplanet.ecommerce.vortex.display.BaseServlet.errorForward(BaseServlet.java :166)
at com.iplanet.ecommerce.vortex.display.IMMWrapperPageContext.handlePageException (IMMWrapperPageContext.java:151)
at jsp.APPS.imm40.iMM.imm._jspService(Compiled Code)
at com.iplanet.ecommerce.vortex.display.PlatformServlet.service(PlatformServlet. ava:68)
at com.iplanet.ecommerce.vortex.display.PortalServlet.service(PortalServlet.java 197)
at com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown Source)
at com.netscape.server.servlet.servletrunner.ServletRunner.callJSP(Unknown Source)
at com.netscape.server.servlet.platformhttp.PlatformHttpServletResponse.callJspCo mpiler(Unknown Source)
at com.netscape.server.servlet.platformhttp.PlatformHttpServletResponse.callUri(U nknown Source)
at com.netscape.server.servlet.platformhttp.PlatformHttpServletResponse.callUriRe strictOutput(Unknown Source)
at com.netscape.server.servlet.platformhttp.PlatformRequestDispatcher.forward(Unk nown Source)
at com.netscape.server.servlet.jsp.JSPRunner.service(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown Source)
at com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unknown Source)
at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Compiled Code)
at java.lang.Thread.run(Compiled Code)

and further:

Original exception:
VortexException Stack--------
display profile contained bad data: {0}
--------
display profile contained bad data: {0}
--------
Error decoding xml in display profile: {0}
--------
display profile contained bad data: {0}
--------
java.lang.ClassNotFoundException:
com.iplanet.ecommerce.vortex.rfx.display.RFxDisplayModule
--------
java.lang.ClassNotFoundException:
com.iplanet.ecommerce.vortex.rfx.display.RFxDisplayModule
--------
display profile contained bad data: {0}


The iPlanet Application Server is sensitive to the CLASSPATH environmental variable of the shell from which it is started. Basically, CLASSPATH should not be set in the shell from which you start iAS.

To correct the problem:

  1. Stop iAS.

  2. Either clear CLASSPATH in your current shell, or bring a new shell where CLASSPATH is not set.

  3. Start iAS from the shell where CLASSPATH is not set.



UNIX Error


Error
Word too long when sourcing the mm.cshrc file in the C-shell


Fix
You need to create a symbolic link from your root directory to the iPlanet Market Maker installation directory. The command to create this link is
ln -s <install_dir> <link_name>
. After you create this link, replace all instances of the iPlanet Market Maker installation directory name in your mm.cshrc file with the directory name defined by the symbolic link.



Oracle Errors




Error
Error during creation of interMedia index.


create index CAT_ATR_VALUE_TXT1 on CAT_ATTR

*

ERROR at line 1:

ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine

ORA-20000: interMedia Text error:

DRG-50704: Net8 listener is not running or cannot start external procedures

ORA-28575: unable to open RPC connection to external procedure agent

ORA-06512: at "CTXSYS.DRUE", line 126

ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 54

ORA-06512: at line 1



Possible Cause
Oracle Net Service Name is not configured correctly. Make sure that tnsnames.ora is configured properly.


Fix
Make sure that listener.ora and tnsnames.ora files are configured properly for use with interMedia. There must be an SID entry of "PLSExtProc" in tnsnames.ora and it's corresponding entry in listener.ora. Reconfiguring Net8 using "$ORACLE_HOME/bin/netasst" and "$ORACLE_HOME/bin/netca" may solve the Net 8 configuration problem. Refer to Oracle Net8 Administrator's Guide.

These errors indicate that there is something wrong with external procedures.


Verification Method 1
Installation of Context objects did not succeed.

Check:

  1. Whether user CTXSYS exists in database:

    SQL>select username from dba_users where username = 'CTXSYS';

    which should return:

    CTXSYS

  2. If yes, check whether user CTXSYS is the owner of the required libraries:

    SQL>select LIBRARY_NAME, FILE_SPEC, STATUS from user_libraries;

    which should return:



    DR$LIB  

     

    VALID  

    DR$LIBX  

    <$ORACLE_HOME>/ctx/lib/libctxx8.s0  

    VALID  

At least one of the two queries above should show something else other than expected. If yes, you need to reinstall Context objects.

Explanation:

Installation of Context Objects failed. You need to reinstall them.


Verification Method 2
Make sure you have configured your listener.ora and tnsnames.ora correctly as shown below. You can ping the extproc alias.

LISTENER ORA:



LISTENER =

 (DESCRIPTION_LIST =

  (DESCRIPTION =

   (ADDRESS_LIST =

    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))

   )

   (ADDRESS_LIST =

    (ADDRESS = (PROTOCOL = TCP)(HOST = vortex-pls3)(PORT = 1521))

   )

  )

  (DESCRIPTION =

   (PROTOCOL_STACK =

    (PRESENTATION = GIOP)

    (SESSION = RAW)

   )

   (ADDRESS = (PROTOCOL = TCP)(HOST = vortex-pls3)(PORT = 2481))

  )

 )

SID_LIST_LISTENER =

 (SID_LIST =

  (SID_DESC =

   (SID_NAME = PLSExtProc)

   (ORACLE_HOME = /home/app/oracle/product/8.1.7)

   (PROGRAM = extproc)

  )

  (SID_DESC =

   (GLOBAL_DBNAME = VORTEX.red.iplanet.com)

   (ORACLE_HOME = /home/app/oracle/product/8.1.7)

   (SID_NAME = VORTEX)

  )

 )


SQLNET.ORA



NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)

#NAMES.DEFAULT_DOMAIN = red.iplanet.com

Note: Comment out the parameter NAMES.DEFAULT_DOMAIN


TNSNAMES.ORA



EXTPROC_CONNECTION_DATA =

 (DESCRIPTION =

  -(ADDRESS_LIST =

    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))

   )

   (CONNECT_DATA =

    (SID = PLSExtProc)

    (PRESENTATION = RO)

   )

  )

 

VORTEX =

 (DESCRIPTION =

  (ADDRESS_LIST =

   (ADDRESS = (PROTOCOL = TCP)(HOST = vortex-pls3)(PORT = 1521))

  )

  (CONNECT_DATA =

   (SERVICE_NAME = VORTEX.red.iplanet.com)

  )

 )


If you have configured as shown above and still receive an error, the problem is that you have not set up your environment variables correctly. As documented in the interMedia release notes:

Ensure that $ORACLE_HOME/ctx/lib is included in the appropriate environment variables to allow the system to locate the Inso shared libraries (DLLs).

For example, Solaris:


add $ORACLE_HOME/ctx/lib to your LD_LIBRARY_PATH environment variable




Note This path MUST be added to both variables.





Sizing iMQBroker



iMQ should be started with at least 128MB. If not, it uses the default of 16MB, which is too low.

If there is not enough memory for iMQBroker, you might see the following error in the imm.log file:


Error
java.lang.OutOfMemoryError in imm.log


Possible Cause
iMM router (used in the Exchange module) could be causing the error.


Fix
If an out of memory error results from the router process, the imm/bin/ExchangeRouter.bash should be modified to increase the amount of maximum memory (the default value is -Xmx128M). The router should then be stopped and restarted.


Error
java.lang.OutOfMemoryError in iMQ logs directory


Possible Cause
This error can come from imqbroker because maximum memory setting on imqbroker is too low.


Possible Fix
Increase the maximum memory used by imqbroker as follows:

To increase maximum memory used by imqbroker, use the following settings:

jmqbroker - vmargs -Xmx128Mb

To set the minimum and the maximum settings simultaneously, use the following settings:

jmqbroker -vmargs -Xmx128Mb - Xms64MB


Previous     Contents     Index     Next     
Copyright © 2002 Sun Microsystems, Inc. All rights reserved.

Last Updated April 08, 2002