Oracle.jsp.logger.JspMessages warningAnnotationTagNotFound logging message

Hi,
I'm getting this message in my embedded OC4J log in JDeveloper 10.1.3.1.0
Nov 13, 2006 4:13:25 AM oracle.jsp.logger.JspMessages warningAnnotationTagNotFound
INFO: Unable to load class oracle.jsp.webutil.personalization.tagext.RecordRatingTag while scanning for annotated JSP tags.
Nov 13, 2006 4:13:25 AM oracle.jsp.logger.JspMessages warningAnnotationTagNotFound
INFO: Unable to load class oracle.jsp.webutil.personalization.tagext.RemoveNavigationRecordTag while scanning for annotated JSP tags.
Nov 13, 2006 4:13:25 AM oracle.jsp.logger.JspMessages warningAnnotationTagNotFound
INFO: Unable to load class oracle.jsp.webutil.personalization.tagext.XSellRecsTag while scanning for annotated JSP tags.
Nov 13, 2006 4:13:25 AM oracle.jsp.logger.JspMessages warningAnnotationTagNotFound
INFO: Unable to load class oracle.jsp.webutil.personalization.tagext.RecordPurchaseTag while scanning for annotated JSP tags.
Nov 13, 2006 4:13:25 AM oracle.jsp.logger.JspMessages warningAnnotationTagNotFound
I don't know why it is trying to load the oracle.jsp.webutil.personalization classes b/c I am just working on a basic web application.
Thanks,
Richard

Looks like its off to the OA Framework Forum (hint, hint) for you.
John

Similar Messages

  • Log Messages from Transaction Event Logger

    I have 4 instances of MII v12.1 and within a transaction I want to add a message to the log when the transaction runs so I can view it through the message logger. All 4 MII instances were installed by the same consultant a few years ago so there "should" be no differences in the log configs. On 3 of the instances this is working fine - I have created a very simple transaction with one Event Logger action configured with a message "Test Message" and when I execute the transaction I see the correct entry in the log viewer. On the fourth however, although the transaction executes without error I am not seeing anything in the viewer for this event. I am using the standard "last 24 hours" log viewer with no filters and no specific log locations selected, and no customisations. I am seeing other system generated messages. I found some documentation about logging and the viewer and I found the Netweaver log config but as far as I can see it looks consistent between the instance which is working and the one which is not working. Is there some other config which needs to be done to enable Event Logging from transactions? My user has the same access across all instances. Any guidance would be appreciated. I attach a screen shot of what I am expecting to see (taken from one of the instances which is working).

    Hi Partha
    Many thanks for your reply. I have tried this and unfortunately it makes no difference. I also checked on the other instances and found they have their tracing levels all set to error, not Info. I have also noticed that on the instance which is working, in the System Configuration section at the bottom of the Log Config page - for Applications and all sub categories I see the entry .\log\applications_00.log in the Pattern column. On the instance which is not working I see that entry for the Applications root but not for any of the sub categories (even after selecting Copy to subtree). I cannot see where I can set this value (there is no modify function available, even under Administrator login).
    Also, when I look at the log messages which have generated when setting the Event Type to Error on the instance which is not working, it shows one entry and the Category and Location columns show <com.sap.xmii.bls.executables.action.logging.LoggingActions>. When I generate an event with type Error on the instance which is working I get 2 log messages, one with the Category and Location <com.sap.xmii.bls.executables.action.logging.LoggingActions> and the other with Category /Applications/XMII/Xacute/Event and Location <com.sap.xmii.bls.executables.action.logging.LoggingActions>.
    I guess that the .\log\applications_00.log should be showing for all subtree items under Applications and because it is not then the messages are not going into any application log. Not sure how to fix this however.
    I have also reset to the default configuration and it does not change the above.
    Best Rgds
    Richard

  • Logger doesn't log fine() messages

    I setup the Logger like so
    try {
         FileHandler handler = new FileHandler("JEL.log");
         handler.setFormatter(new SimpleFormatter());
         gLogger = Logger.getLogger("com.sidkwakkel.jel");
         gLogger.addHandler(handler);
         // The logging level can be set from the application options file
         if(mOptions.getProperty("Logger_level").equalsIgnoreCase("all")) {
              gLogger.getHandlers()[0].setLevel(Level.ALL);
              gLogger.setLevel(Level.ALL);
         } else if(mOptions.getProperty("Logger_level").equalsIgnoreCase("debug")) {
              gLogger.getHandlers()[0].setLevel(Level.INFO);
              gLogger.setLevel(Level.INFO);
         } else if(mOptions.getProperty("Logger_level").equalsIgnoreCase("warnings")) {
              gLogger.getHandlers()[0].setLevel(Level.WARNING);
              gLogger.setLevel(Level.WARNING);
         } else if(mOptions.getProperty("Logger_level").equalsIgnoreCase("off")) {
              gLogger.getHandlers()[0].setLevel(Level.OFF);
              gLogger.setLevel(Level.OFF);
         gLogger.info("test info");
         gLogger.fine("test fine");
    }catch(IOException e) {}If I set my option file to
    Logger_level               :     allit still only captures messages that are made using info(). All of my messages that use fine() are ignored. Any ideas?

    Following up after further investigation.
    It's not just .exiting() that is failing to log the class/method names.
    All methods on Logger fail to log the supplied class/method names.
    Even manually creating a LogRecord and explicitly calling setSourceClassName()
    and setSourceMethodName() fails to log the names.
    Presumably this is because the supplied names are being ignored.
    Anyone have any idea why this would happen?/
    Thanks, Alan
    PS. All this refers to java.util.logging.Logger

  • Using GenericPortlet sublcass .. cannot get any log messages to come out.

    Hi all ..
    I'm having a lot of problems getting any exceptions or log messages dumped from my portlet to help me debug.
    I'm currently using subclass of javax.portlet.GenericPortlet and not a sublcass of com.sun.portal.providers.jsp.JSPProvider. Does that matter? Anyone know if there are issues that I might be running into here?
    More details ..
    I've tried making nice PortletException wrappers around all sorts of other exceptions .. and even using the API call:
    GenericPortlet.getPortletContext().log(<msg>,<throwable> )
    I've tweaked every debug/log/show exception config setting I can find .. including setting logger.log.level=ALL in:
    /etc/opt/SUNWps/portlet/PDConfig.properties
    It'll mostly fail with nada .. zilch .. zero. No hint or reason why. Occasionally I'll get something useful and I'll see an exception I made .. but the other 95% of the time I get no hint.
    I've a script that searches for any file touched in /opt/SUNW*, /var/opt/SUNW* and /etc/opt/SUNW*. I regularly get the following files touched:
    /var/opt/SUNWam/debug/portletcontainer.log
    /var/opt/SUNWam/debug/<myportlet>.log
    /var/opt/SUNWam/debug/desktop.debug
    Can anyone tell me where I should expect to see PortletExceptions logged? How do I turn that feature on .. just in case I've missed the config I need to change? Has anyone had any luck using the PortletContext.log(<msg>,<throwable) API calls? Is there some config that controls where that goes? (I would've assumed it all goes in the <myportlet>.log file .. but not for me.)
    Many thanks for your time ..
    Curtis.
    p.s. Below is an example of some of the messages I do see.
    One instance I get "ERROR: Content not available" .. I get a series of
    rather unhelpful internal exceptions that (for example) complain the portlet threw an exception of some sort. If only the root cause had been printed out it would be possible to nail exactly what's going on in my code that's the issue. Unfortunately this style of "black box" debugging is taking me 10 times (literally .. honestly!) longer than it should. I have to comment out stuff and slowly add it back in again .. if only I could've seen the exception.
    (NOTE: I modifed PrefPortlet.java example .. still called the same at the minute :-) )
    From log file /var/opt/SUNWam/debug/desktop.debug ..
    06/09/2004 09:25:08:066 PM PDT: Thread[Thread-76,5,main]
    ERROR: ProviderCaller.run(): exception thrown from PrefPortlet
    com.sun.portal.providers.ProviderException: PortletWindowProvider.getContent():container exc
    eptioncom.sun.portal.container.ContainerException: PortletContainer.getMarkup():getting cont
    ent com.sun.portal.container.ContentException: PortletContainer.getMarkup(): Cannot get cont
    ent
    at com.sun.portal.providers.portletwindow.PortletWindowProvider.getContent(PortletWi
    ndowProvider.java:284)
    at com.sun.portal.desktop.context.ReusableProviderCaller.run(ReusableProviderCaller.
    java:158)
    com.sun.portal.container.ContainerException: PortletContainer.getMarkup():getting content co
    m.sun.portal.container.ContentException: PortletContainer.getMarkup(): Cannot get content
    at com.sun.portal.container.portlet.impl.PortletContainer.getMarkup(PortletContainer
    .java:201)
    [snip]
    (not much help really)
    From the file /var/opt/SUNWam/debug/<myportlet>.log (my specific portlet log) ..
    2004/06/09 21:25:08.058 PDT | Curtis First Port | SEVERE | Thread-76 | Portle
    tAppEngineServlet.HandleError()() - Error: null | LifecycleManagerImpl.getPortlet(),
    can not get portlet.
    x -----------------------------------------------------------------------------
    X javax.portlet.PortletException: LifecycleManagerImpl.getPortlet(), can not get por
    tlet.
    X at com.sun.portal.portletappengine.impl.LifecycleManagerImpl.getPortlet(Life
    cycleManagerImpl.java:163)
    X at com.sun.portal.portletappengine.PortletAppEngineServlet.service(PortletAp
    pEngineServlet.java:187)
    X at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    [snip]
    (still not much help)
    Note .. i sometimes get useful exceptions dumped to that last file .. but
    it's rare .. I just can't seem to spot the pattern when they will and won't
    get printed.
    From file /var/opt/SUNWam/debug/portletcontainer.log
    2004/06/09 21:25:07.414 PDT | null | INFO | Thread-76 | Portle
    tContainer.invokePAE(): invoking:
    app name /<myportlet>
    portlet name PrefPortlet
    action RENDER | -
    2004/06/09 21:25:08.063 PDT | null | SEVERE | Thread-76 | Portle
    tContainer:executeAction(): Exception thrown from render() of <myportlet>|PrefPortlet
    |PrefPortlet | -
    [snip]
    (the least helpful of all!!)
    When I simply comment out the new code I added, recompile, and view the portlet again .. it works fine. If I could only see the root cause exception!!

    Ok .. weirder and weirder ...
    I left this for a while .. and then went back to my xterms where I was working .. and one of them I saw this:
    # Jun 9 21:55:14 troy server1 appservd[7440]: [ID 702911 daemon.alert] SEVERE ( 7440): hefalump - Problem setting up PAL array!
    Jun 9 21:55:14 troy java.io.FileNotFoundException: http://pie1.some.thing.com/portal/arraylist.xml
    Jun 9 21:55:14 troy at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:789)
    Jun 9 21:55:14 troy at java.net.URL.openStream(URL.java:913)
    Jun 9 21:55:14 troy at com.tarantella.portal.bell.test.WebtopHostFinder.<init>(WebtopHostFinder.java:42)
    Jun 9 21:55:14 troy at com.some.portal.test.PrefPortlet.init(PrefPortlet.java:72)
    Jun 9 21:55:14 troy at com.sun.portal.portletappengine.impl.LifecycleManagerImpl.createPortlets(LifecycleManagerImpl.java:329)
    Jun 9 21:55:14 troy at com.sun.portal.portletappengine.impl.LifecycleManagerContextListenerImpl.contextInitialized(LifecycleManagerContextListenerImpl.java:13)
    Jun 9 21:55:14 troy at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3255)
    Jun 9 21:55:14 troy at org.apache.catalina.core.StandardContext.reload(StandardContext.java:2525
    Jun 9 21:55:14 troy at com.sun.portal.portletappengine.impl.LifecycleManagerImpl.init(LifecycleManagerImpl.java:109)
    That is exactly the information I'm looking for!!!
    I've no idea how it got there .. I think the appservd process just dumped it there .. after I saw this I grep'ed the entire set of files in /opt/SUNW* /var/opt/SUNW* /etc/opt/SUNW* for "hefalump" (my unique 'log' key) and it's not in any log file.
    Anyone know what's going on?
    Curtis.

  • ERROR messages in /var/log/messages

    Hi,
    I encountered a error messages in /var/log/messages please find below
    Dec 9 04:03:08 drs syslogd 1.4.1: restart (remote reception).
    Dec 9 04:03:18 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:03:18 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:03:18 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:03:18 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:03:18 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:03:18 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:03:18 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:03:18 drs init: Id "h1" respawning too fast: disabled for 5 minutes
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs init: Id "h1" respawning too fast: disabled for 5 minutes
    Dec 9 04:10:46 drs rpc.mountd: authenticated unmount request from 10.3.141.26:651 for /opt/backup_log/srv (/opt/backup_log)
    Dec 9 04:10:47 drs rpc.mountd: authenticated mount request from 10.3.141.26:657 for /opt/backup_log/websrv (/opt/backup_log)
    Dec 9 04:10:47 drs rpc.mountd: authenticated unmount request from 10.3.141.26:672 for /opt/backup_log/websrv (/opt/backup_log)
    Dec 9 04:10:47 drs rpc.mountd: authenticated mount request from 10.3.141.26:677 for /opt/backup_log/ws (/opt/backup_log)
    Dec 9 04:12:01 drs rpc.mountd: authenticated unmount request from 10.3.141.26:849 for /opt/backup_log/ws (/opt/backup_log)
    Dec 9 04:13:20 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    and database (oracle 10g) is running fine, but i cant figure out what could be the problem, can anyone just help me out on this.
    Jafar

    Hi,
    #h1:35:respawn:/etc/init.d/init.cssd run >/dev/null 2>&1 </dev/null
    by commenting above line in initttab file would stop messaging, is this would have any adverse affect on the database. As its a production server, so i am really taking time to resolve it. Your suggestions are welcome. If there is no harm in commenting the above line then i would go forward to comment that line.
    Thanks
    Jafar>

  • Log4j not logging messages out to weblogic console for custom automatplugin

    Hi,
    We have a custom automation plugin for the OSM application build 381 in our environment(HP-UX Itanium platform). The plugins are bundled in a single ear application "A.ear" which is a mixed bag of pre-defined automation plugins of type XsltSender, XsltAutomator(both InternalReciever as well ExternalReceiver) as well other custom automators(java). For logging of messages in order to aid debugging of custom automators, we are using a logger "com.xyz.osm.plugin" which is also declared in log4j.xml file that is within omslogging.jar. You must already be aware that the build scripts of assembling, deploying ansd registering plugins also includes omslogging.jar are part of the application ear.
    <category name="com.mtsa.osm.plugin">
    <priority value="debug"/>
    </category>
    Below java code snippet is taken from our custom automation plugin classes indicating how the above logger is being used for printing messages.
    //Declaration
    private static Log log = LogFactory.getLog("com.mtsa.osm.plugin");
    mthod1(){
    log.info("xyz");
    In addition to the above logger, the pre-defined automators XsltSender, XsltReceiver also enable logging from xsl files by making the "log" parameter available. Thus we have lines such as the one below in our xsl files that should print messages to the weblogic console.
    <xsl:variable name="addLog1" select="java:info($log, 'transformSiebelActivationRequest: ***** Starting *****')"/>
    The logger that allows printing of these lines is "com.mslv.oms.automation".
    <category name="com.mslv.oms.automation">
    <priority value="info"/>
    </category>
    These configurations should have ideally allowed one to see messages such as one below getting printed out to weblogic console:
    <16-Mar-2012 8:59:36,931 CDT PM> <INFO> <plugin.XSLTReceiver> <ExecuteThread: '19' for queue: 'oms.automation'> <transformSiebelActivationRequest: ***** Starting *****>
    Unfotunately after having done all the above configuration, we are still unable to see any such log messages in the console apart from those emitting from SOP and from <xsl:message> inserted in java & xsl files respectively.
    I also checked if the log4j sub-system is able to correctly initialize after parsing the log4j.xml. It does and one can confirm it by setting system property log4j.debug=true in setDomainEnv.sh file.
    $$$$$$$$ log4j initialization by application classloader for oms.ear application $$$$$$$$$$$$$$$$$$
    log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1592141 finder: weblogic.utils.classloaders.CodeGenClassFinder@1112e85 annotation: oms@.
    log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/oms/amuube/omslogging.jar!/log4j.xml] for automatic log4j configuration.
    log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
    log4j: System property is :null
    log4j: Standard DocumentBuilderFactory search succeded.
    log4j: DocumentBuilderFactory is: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
    $$$$$$$$ log4j initialization by application classloader for custom automation plugin xyz.ear application $$$$$$$$$$$$$$$$$$
    log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1b7a8c5 finder: weblogic.utils.classloaders.CodeGenClassFinder@10bc849 annotation: xyz.ear@.
    log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/xyz.ear/ah0eeq/omslogging.jar!/log4j.xml] for automatic log4j configuration.
    log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
    log4j: System property is :null
    log4j: Standard DocumentBuilderFactory search succeded.
    log4j: DocumentBuilderFactory is: weblogic.xml.jaxp.RegistryDocumentBuilderFactory
    log4j: debug attribute= "false".
    Ironically, logging levels for loggers defined in log4j.xml of oms.ear could be dynamically changed from log4jAdmin.jsp page and the results are immediately visible. However for some reason, loggers defined in log4j.xml of custom plugin application were completely getting ignored. I don't see any warnings or erro messages in the logs indicating that log4j configuration failed for custom application failed. We want to refrain using SOP and <xsl:message> but I am afraid we have no option other than filling up our sources files with them.
    Bottomline, how do we get application B(which in our case is the custom plugin) to log messaged the console just like that done by application A(oms.ear).
    I am sure OSM developers would like to leverage log4j bundled with OSM SDK to log messages that would aid in trouble-shooting during development cycles. Both application ear files have commons-logging-1.1.jar,log4j-1.2.13.jar, omslogging.jar available in their classpaths. In other words, META-INF/MANIFEST.MF file of oms.war(web module within oms.ear) and xyz.jar(ejb module within xyz.ear) has references to these jars.
    Appreciate if one can reply and let me know if they could get log messages to print from custom plugin.
    Thanks
    Edited by: user3693508 on Mar 18, 2012 11:38 AM

    Hi,
    We have a custom automation plugin for the OSM application build 381 in our environment(HP-UX Itanium platform). The plugins are bundled in a single ear application "A.ear" which is a mixed bag of pre-defined automation plugins of type XsltSender, XsltAutomator(both InternalReciever as well ExternalReceiver) as well other custom automators(java). For logging of messages in order to aid debugging of custom automators, we are using a logger "com.xyz.osm.plugin" which is also declared in log4j.xml file that is within omslogging.jar. You must already be aware that the build scripts of assembling, deploying ansd registering plugins also includes omslogging.jar are part of the application ear.
    <category name="com.mtsa.osm.plugin">
    <priority value="debug"/>
    </category>
    Below java code snippet is taken from our custom automation plugin classes indicating how the above logger is being used for printing messages.
    //Declaration
    private static Log log = LogFactory.getLog("com.mtsa.osm.plugin");
    mthod1(){
    log.info("xyz");
    In addition to the above logger, the pre-defined automators XsltSender, XsltReceiver also enable logging from xsl files by making the "log" parameter available. Thus we have lines such as the one below in our xsl files that should print messages to the weblogic console.
    <xsl:variable name="addLog1" select="java:info($log, 'transformSiebelActivationRequest: ***** Starting *****')"/>
    The logger that allows printing of these lines is "com.mslv.oms.automation".
    <category name="com.mslv.oms.automation">
    <priority value="info"/>
    </category>
    These configurations should have ideally allowed one to see messages such as one below getting printed out to weblogic console:
    <16-Mar-2012 8:59:36,931 CDT PM> <INFO> <plugin.XSLTReceiver> <ExecuteThread: '19' for queue: 'oms.automation'> <transformSiebelActivationRequest: ***** Starting *****>
    Unfotunately after having done all the above configuration, we are still unable to see any such log messages in the console apart from those emitting from SOP and from <xsl:message> inserted in java & xsl files respectively.
    I also checked if the log4j sub-system is able to correctly initialize after parsing the log4j.xml. It does and one can confirm it by setting system property log4j.debug=true in setDomainEnv.sh file.
    $$$$$$$$ log4j initialization by application classloader for oms.ear application $$$$$$$$$$$$$$$$$$
    log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1592141 finder: weblogic.utils.classloaders.CodeGenClassFinder@1112e85 annotation: oms@.
    log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/oms/amuube/omslogging.jar!/log4j.xml] for automatic log4j configuration.
    log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
    log4j: System property is :null
    log4j: Standard DocumentBuilderFactory search succeded.
    log4j: DocumentBuilderFactory is: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
    $$$$$$$$ log4j initialization by application classloader for custom automation plugin xyz.ear application $$$$$$$$$$$$$$$$$$
    log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1b7a8c5 finder: weblogic.utils.classloaders.CodeGenClassFinder@10bc849 annotation: xyz.ear@.
    log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/xyz.ear/ah0eeq/omslogging.jar!/log4j.xml] for automatic log4j configuration.
    log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
    log4j: System property is :null
    log4j: Standard DocumentBuilderFactory search succeded.
    log4j: DocumentBuilderFactory is: weblogic.xml.jaxp.RegistryDocumentBuilderFactory
    log4j: debug attribute= "false".
    Ironically, logging levels for loggers defined in log4j.xml of oms.ear could be dynamically changed from log4jAdmin.jsp page and the results are immediately visible. However for some reason, loggers defined in log4j.xml of custom plugin application were completely getting ignored. I don't see any warnings or erro messages in the logs indicating that log4j configuration failed for custom application failed. We want to refrain using SOP and <xsl:message> but I am afraid we have no option other than filling up our sources files with them.
    Bottomline, how do we get application B(which in our case is the custom plugin) to log messaged the console just like that done by application A(oms.ear).
    I am sure OSM developers would like to leverage log4j bundled with OSM SDK to log messages that would aid in trouble-shooting during development cycles. Both application ear files have commons-logging-1.1.jar,log4j-1.2.13.jar, omslogging.jar available in their classpaths. In other words, META-INF/MANIFEST.MF file of oms.war(web module within oms.ear) and xyz.jar(ejb module within xyz.ear) has references to these jars.
    Appreciate if one can reply and let me know if they could get log messages to print from custom plugin.
    Thanks
    Edited by: user3693508 on Mar 18, 2012 11:38 AM

  • Oracle.jsp.JspServlet

    Hello!
    I receive the next error message from jserv.log when I try to run a JSP demo page.
    (ERROR) ajp12: Servlet Error: ClassNotFoundException: oracle.jsp.JspServlet
    THX.
    null

    Jayaprakash,
    I am unable to Solution Becon Oracle apps 11i , When I tried to connect I am getting the message like this
    "The requested URL /oa_servlets/oracle.jsp.JspServlet was not found on this server"
    Please guide me and help me.We do not maintain this instance so please contact Solution Beacon support for help.
    Thanks,
    Hussein

  • Exception:oracle.jsp.parse.JspParseException

    hi,
    I deploy my bibeans application via jdeveloper in to application server and copy my lib file named bibeans.jar in web-inf/lib. after I try to view my jsp page which view my graph my browser show internal server error message (error 500 in IE)and following error in my log file :
    04/12/14 11:00:31 Started
    04/12/14 11:00:33 webapp: jsp: init
    04/12/14 11:00:33 webapp: uix: init
    04/12/14 11:00:33 webapp: 9.0.4.0.0 Started
    04/12/14 11:02:42 webapp: JspServlet: unable to dispatch to requested page: Exception:oracle.jsp.parse.JspParseException: Line # 1, <%@ taglib uri="http://xmlns.oracle.com/bibeans" prefix="orabi" %>
    Error: Unable to load taghandler class: http://xmlns.oracle.com/bibeans
    04/12/14 11:04:22 webapp: JspServlet: unable to dispatch to requested page: Exception:oracle.jsp.parse.JspParseException: Line # 1, <%@ taglib uri="http://xmlns.oracle.com/bibeans" prefix="orabi" %>
    Error: Unable to load taghandler class: http://xmlns.oracle.com/bibeans
    what should I do ???
    thanks in advance,
    shima

    To the web.xml file add a taglib element.
    <taglib>
      <taglib-uri>http://xmlns.oracle.com/bibeans/</taglib-uri>
      <taglib-location>/WEB-INF/BITags.tld</taglib-location>
    </taglib>

  • What's best practice for logging messages in pageflow?

    What's best practice for logging messages in pageflow?
    Workshop complains when I try to use a Log4J logger by saying it's not serializable. Is there a context similar to JWSContext that you can get a logger from?
    There seems to be a big hole in the documentation on debug logging in workflows and JSP pages.
    thanks,
    Rodger...

    Make the configuration change in setDomainEnv.cmd. Find where the following variable is set:
    LOG4J_CONFIG_FILE
    and change it to your desired path.
    In your Global.app class, instantiate a static Logger like this:
    transient static Logger logger = Logger.getLogger(Global.class);
    You should be logging now as long as you have the categories and appenders configured properly in your log4j.xml file.

  • Debug mode for Oracle JSP compiler?

    I deploy a web application in an EAR file to Oracle 9iAS 9.0.3 through Oracle Enterprise Manager. Now during the deployment of the EAR file I get an error:
    404 Not Found
    OracleJSP: java.io.FileNotFoundException:
    Set the init-param debug_mode to "true" to see the complete exception message.
    But I already added this parameter manually to the "oracle.jsp.runtimev2.JspServlet" in "global-web-application.xml" (as suggested by http://otn.oracle.com/tech/java/oc4j/doc_library/902/jsp/getstart.htm#1005625). Also, when I check out the "JSP Container Attributes" in the "Administration" settings of my OC4J, "Debug Mode:" is set to "Yes" as well.
    So how do I need to configure my OC4J to print the full JSP compilation error message?

    Please try Oracle9iAS Release 2 Containers for J2EE - Logging and Debugging at http://otn.oracle.com/tech/java/oc4j/htdocs/oc4j-logging-debugging-technote.html.
    Hope that helps.

  • Error Mesages in /var/log/messages

    Hi,
    Dec 9 04:03:08 drs syslogd 1.4.1: restart (remote reception).
    Dec 9 04:03:18 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:03:18 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:03:18 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:03:18 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:03:18 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:03:18 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:03:18 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:03:18 drs init: Id "h1" respawning too fast: disabled for 5 minutes
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs init: Id "h1" respawning too fast: disabled for 5 minutes
    Dec 9 04:10:46 drs rpc.mountd: authenticated unmount request from 10.3.141.26:651 for /opt/backup_log/srv (/opt/backup_log)
    Dec 9 04:10:47 drs rpc.mountd: authenticated mount request from 10.3.141.26:657 for /opt/backup_log/websrv (/opt/backup_log)
    Dec 9 04:10:47 drs rpc.mountd: authenticated unmount request from 10.3.141.26:672 for /opt/backup_log/websrv (/opt/backup_log)
    Dec 9 04:10:47 drs rpc.mountd: authenticated mount request from 10.3.141.26:677 for /opt/backup_log/ws (/opt/backup_log)
    Dec 9 04:12:01 drs rpc.mountd: authenticated unmount request from 10.3.141.26:849 for /opt/backup_log/ws (/opt/backup_log)
    Dec 9 04:13:20 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    I observed above mesages in /var/log/messages, can anyone tell what does it mean
    Version - oracle 10g
    Platform - Linux.
    Thanks
    Jafar

    Hi,
    #h1:35:respawn:/etc/init.d/init.cssd run >/dev/null 2>&1 </dev/null
    by commenting above line in initttab file would stop messaging, is this would have any adverse affect on the database. As its a production server, so i am really taking time to resolve it. Your suggestions are welcome. If there is no harm in commenting the above line then i would go forward to comment that line.
    Thanks
    Jafar

  • How to add log messages in the sever/webui objects?

    Hi,
    I am new to the OA Framework.
    Can any one share any information in how to add log messages in the sever/webui objects?
    What are the beans I need to use to show in the diagnostic page?
    Can I get sample code for this log staments?
    Thanks in advance,
    Padma

    Hello. This forum is for reporting problems with the published Oracle documentation. You have a better change of getting a reply if you post your question on the Database - General forum.
    Regards,
    Diana

  • Error while accessing OIM UI - OracleJSP error: oracle.jsp.parse.JspParseException

    We have 3 nodes of OIM servers in our clustered production environment. While accessing OIM server on first node, following error is coming in the browser window -
    OracleJSP error: oracle.jsp.parse.JspParseException:
    /oracle/iam/ui/main/signin.jspx: Line # 5, &amp;amp;amp;lt;af:document id="d1" initialFocusId="pt1:_pt_it1" theme="light" title="#{uiBundle['IDENTITY_SELF_SERVICE_TITLE']}"&amp;amp;amp;gt;
    Error: Encountered deferred syntax #{ in template text. If intended as a literal, escape it or set directive deferredSyntaxAllowedAsLiteral
    The OIM UI is accessible on the other 2 nodes. There are no changes made in the environment. I have also attached the OIM diagnostic logs for your analysis.
    Please let us know the steps to resolve this issue in production environment.

    No..
    I have followed the way to add JSF libray,
    1)Right click the projet->project properties->javadoc->JSP taglibraries
    2)Inside the Distributed Library i have selected the JSTL core 1.2 and click on add.
    3) Then a new dialogue box of Choose tablibraries came.inside that only struts bean,struts Html etc are seeing.
    What i need to select?..Do i am following the right way?
    Please help..

  • PL/SQL log messages are not printing from Java concurrent program

    Hi,
    I have a strange issue while submitting the Java concurrent program through PL/SQL.
    I have a PL/SQL concurrent program which will invoke the Java concurrent program inside the package by use of "FND_GLOBAL.SUBMIT_REQUEST". It worked and submitted successfully. From that Java concurrent program we are calling some other PL/SQL packages and printing some log messages over there. But problem here is the request is only printing the Java log messages in view log but not the PL/SQL log messages.  But if I submit the Java concurrent program directly from SRS form at that it is printing both Java and PL/SQL log messages.
    I am just wondering how the log messages has not printed. Please provide your inputs to solve this problem.
    Thanks
    Suriya

    I'm adding log messages in the package body , but these messages are not printing after completion of concurrent prog.
    Any suggestions.
    FND_FILE.PUT_LINE(FND_FILE.LOG,'Data Test :');Do you have COMMIT in your code?
    https://forums.oracle.com/forums/search.jspa?threadID=&q=%27FND_FILE.PUT_LINE%27+AND+commit&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
    Thanks,
    Hussein

  • Log messages from multiple instances in single file.

    Hi!
    I have a requirement that i need to log messages from muliple instances of the same object in a file. The new file will be created every day. Likewise, multiple objects might have various instances each.
    One class
    ->multiple instances
    -> log message stored in single file.
    Note :
    I am using the Message driven bean. I need to log from the bean class. JDK 1.3
    If u could help me out that would be great.

    As long as they are all from the same OS program (a single Java VM), that's OK - you can use Log4j, and use a rotating file logger.
    If you point two different virtual machine processes at the same file, one may have it open when the other is trying to rotate it, and your rotation may fail (at best) and/or you may lose the old log (the worst case).
    If you need to collect log messages from multiple processes (or even multiple machines), use a syslog-based logger (Log4j has a SyslogAppender) or use Log4j's SocketAppender to write to a log4j-builtin log listener (SocketNode).

Maybe you are looking for

  • Sound system not working for multiple programs at same time.

    So first off I have an HP Envy m6 Notebook Windows 8 laptop with an AMD10 processor, no added in cards or anything. I am using headphones and the first program I run after starting up my computer (WoW, itunes, winamp, youtube video, etc) is the only

  • Reformatted, need to restore Mail.app from external USB drive

    I just reformatted my Macbook, and I'd like to restore my Mail.app to its former glory without having to reinstall every single email account (I've got 7). If I copy ~/Library/Mail on my backup into the same directory on my Macbook, will Mail.app jus

  • View/Controller best practices

    Hello, A coworker and I are in charge of creating the standards for Web Dynpro development at our company.  We've been able to agree on most topics, but we're stuck on one issue.  Should ALL logic be in the controller or is it ok to perform some logi

  • Disabling Field Disables the Entire Form

    I am trying to disable fields in the 'User Library.xml' form depending on who logs in; unfortunately the code below disables the whole form. Any pointers on how to get out of this logjam? <Field name='global.login_desc'> <Display class='Text'> <Prope

  • IDVD Themepak installation issue

    I purchased third party themes from ThemePaks and when I try to install the software, I get to the part that ask's "What volume that I want to install this on and when I choose the destination I get an error that says "you are not allowed to install