Problems with Log4j/commonslogging

I'm having some weird problems with log4j or commons/logging. I'm not at all
excluding that they may be my own fault, but I can't get to the actual
problem. Hope someone can help me out. I'm getting an exception at startup
of the VM. The exception is below. The problem seems to be version related I
think, but I can't figure it out exactly, since the versions of both logging
and log4j I have in my path seem to be exactly equal to those in my 2.5 RC1
distrib.
Hope you can help out,
Martin van Dijken
PS: This isn't the entire excep, hope it's enough
1652 ERROR [main] kodo.Runtime -
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:org.apache.commons.logg
ing.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:org.apache.commons.logg
ing.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja
va:555)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja
va:289)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:409)
at
com.solarmetric.modules.tools.compiler.MetaDataParser.<init>(MetaDataParser.
java:32)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.<init>(CFMetaDataPar
ser.java:39)
at
com.solarmetric.kodo.meta.JDOMetaDataParser.<init>(JDOMetaDataParser.java:61
at
com.solarmetric.kodo.meta.ClassMetaData.getInstance(ClassMetaData.java:223)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClassIn
ternal(JDBCPersistenceManagerFactory.java:444)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClass(J
DBCPersistenceManagerFactory.java:334)
at
com.solarmetric.kodo.impl.jdbc.RegisterListener.registerClass(RegisterListen
er.java:53)
at javax.jdo.spi.JDOImplHelper.registerClass(JDOImplHelper.java:269)
at
com.madocke.mirakel.forum.ForumMessage.<clinit>(ForumMessage.java)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:217)
at
com.solarmetric.kodo.util.MultiLoaderClassResolver.resolveClass(MultiLoaderC
lassResolver.java:85)
at
com.solarmetric.kodo.util.MultiLoaderClassResolver.canResolveClass(MultiLoad
erClassResolver.java:143)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.classForName(CFMetaD
ataParser.java:231)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.classForName(CFMetaD
ataParser.java:180)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.classForName(CFMetaD
ataParser.java:165)
at
com.solarmetric.kodo.meta.JDOMetaDataParser.startClass(JDOMetaDataParser.jav
a:122)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.startElement(CFMetaD
ataParser.java:53)
at
com.solarmetric.modules.tools.compiler.MetaDataParser.startElement(MetaDataP
arser.java:238)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unkno
wn Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc
her.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

What is probably happening is a class loader issue... I would put
jakarta's logging jar in the same place as log4j and be sure that they
aren't extraneously in the classpath (such as in an EAR or WAR). Java
can be pretty funky about classloaders and interfaces.
On Fri, 16 May 2003 11:02:40 -0400, Alex Roytman wrote:
Are you running it standalone or under lets say tomcat 4?
"Martin van Dijken" <[email protected]> wrote in message
news:[email protected]...
I'm having some weird problems with log4j or commons/logging. I'm not atall
excluding that they may be my own fault, but I can't get to the actual
problem. Hope someone can help me out. I'm getting an exception at startup
of the VM. The exception is below. The problem seems to be version relatedI
think, but I can't figure it out exactly, since the versions of bothlogging
and log4j I have in my path seem to be exactly equal to those in my 2.5RC1
distrib.
Hope you can help out,
Martin van Dijken
PS: This isn't the entire excep, hope it's enough
1652 ERROR [main] kodo.Runtime -
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:org.apache.commons.logg
ing.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:org.apache.commons.logg
ing.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja
va:555)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja
va:289)
atorg.apache.commons.logging.LogFactory.getLog(LogFactory.java:409)
at
com.solarmetric.modules.tools.compiler.MetaDataParser.<init>(MetaDataParser.
java:32)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.<init>(CFMetaDataPar
ser.java:39)
at
com.solarmetric.kodo.meta.JDOMetaDataParser.<init>(JDOMetaDataParser.java:61
at
com.solarmetric.kodo.meta.ClassMetaData.getInstance(ClassMetaData.java:223)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClassIn
ternal(JDBCPersistenceManagerFactory.java:444)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClass(J
DBCPersistenceManagerFactory.java:334)
at
com.solarmetric.kodo.impl.jdbc.RegisterListener.registerClass(RegisterListen
er.java:53)
atjavax.jdo.spi.JDOImplHelper.registerClass(JDOImplHelper.java:269)
at
com.madocke.mirakel.forum.ForumMessage.<clinit>(ForumMessage.java)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:217)
at
com.solarmetric.kodo.util.MultiLoaderClassResolver.resolveClass(MultiLoaderC
lassResolver.java:85)
at
com.solarmetric.kodo.util.MultiLoaderClassResolver.canResolveClass(MultiLoad
erClassResolver.java:143)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.classForName(CFMetaD
ataParser.java:231)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.classForName(CFMetaD
ataParser.java:180)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.classForName(CFMetaD
ataParser.java:165)
at
com.solarmetric.kodo.meta.JDOMetaDataParser.startClass(JDOMetaDataParser.jav
a:122)
at
com.solarmetric.modules.tools.compiler.CFMetaDataParser.startElement(CFMetaD
ataParser.java:53)
at
com.solarmetric.modules.tools.compiler.MetaDataParser.startElement(MetaDataP
arser.java:238)
atorg.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unkno
wn Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc
her.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(UnknownSource)
at org.apache.xerces.parsers.DTDConfiguration.parse(UnknownSource)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(UnknownSource)
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com

Similar Messages

  • Problem with log4j

    I want to load the jar file for my program into oracle.
    The program depends on log4j.
    I am using loadjava command.
    loadjava -user schema/password@database -oci8 -resolve so.jar lib\*.jar config\*.properties
    but i get this error
    errors : class org/apache/log4j/jmx/AbstractDynamicMBean
    ORA-29521: referenced name javax/management/RuntimeOperationsException could not be found
    ORA-29521: referenced name javax/management/AttributeList could not be found
    ORA-29521: referenced name javax/management/Attribute could not be found
    ORA-29521: referenced name javax/management/DynamicMBean could not be found
    ORA-29521: referenced name javax/management/MBeanRegistration could not be found
    ORA-29521: referenced name javax/management/MBeanException could not be found
    ORA-29521: referenced name javax/management/ReflectionException could not be found
    ORA-29521: referenced name javax/management/AttributeNotFoundException could not be found
    ORA-29521: referenced name javax/management/InvalidAttributeValueException could not be found
    ORA-29521: referenced name javax/management/MBeanServer could not be found
    ORA-29521: referenced name javax/management/ObjectName could not be found
    ORA-29521: referenced name javax/management/MBeanInfo could not be found
    what i could figure out is that the jvm on oracle server is 1.4 and hence this class has problems there. Is there a way to make this work without sacrificing log4j?
    null

    Hi,
    The tomcat service is still running fine.
    I have implemented a rotation(once a day) for the log4j log files
    Usually the file size is at about 400KB - 1.5MB the most a day for the log43j log files, and for catalina.out i do not have any rotation implemented.
    Sometimes, i just restarted the tomcat, and the catalina.out is cleared. The catalina.out log, sometimes, it becomes slow and stops logging after a few hours yet the tomcat service is still running because i am getting log on the http post and etc.
    So basically i am having problem with the logger, both log4j and the catalina.out
    Any ideas ?
    (on certain occurance, the log starts again after a while (maybe 1-2 hours later), yet there is a http post request during this period and its not logged)
    below is the log4j properties
    log4j.rootCategory=info,S,R
    log4j.rootLogger=debug, S,R
    log4j.appender.R=org.apache.log4j.DailyRollingFileAppender
    log4j.appender.S=org.apache.log4j.ConsoleAppender
    log4j.appender.R.File=/home/server/tomcatlogs/http_my.log
    log4j.appender.R.DatePattern=-yyyy-MM-dd
    log4j.appender.R.layout=org.apache.log4j.PatternLayout
    log4j.appender.S.layout=org.apache.log4j.PatternLayout
    log4j.appender.R.layout.ConversionPattern=%d{dd MMM yyyy HH:mm:ss} - %p %m%n
    log4j.appender.S.layout.ConversionPattern=%d{dd MMM yyyy HH:mm:ss} - %p %m%n
    log4j.category.org.apache.axis=OFF
    log4j.logger.org.apache.commons.httpclient=OFF
    everything is to be working normally, until a weird sudden death.
    So my main problems are:
    1) catalina.out
    2) log4j
    Both seems to die a slow and painful death :)
    appreciate ur help on this
    cheers,
    Edited by: sankai on Aug 14, 2008 3:58 AM

  • Problems with log4j in jboss please help

    Please i need help because i can't anywhere else.
    Below is the log4j properties file
    # initialise root logger with level INFO and call it
    log4j.rootLogger=INFO, BLAH
    # add a Appender to the logger BLAH
    log4j.appender.BLAH=org.apache.log4j.RollingFileAppender
    # set the layout
    log4j.appender.BLAH.layout=org.apache.log4j.PatternLayout
    #log4j.appender.BLAH.layout.ConversionPattern=%p %c - %m%n
    log4j.appender.BLAH.layout.ConversionPattern=%d{dd-MMM-yyyy HH:mm:ss:SSS}: %m%n
    log4j.appender.BLAH.File=c:/testing.log
    log4j.appender.BLAH.MaxFileSize=10000KB
    # Keep one backup file
    log4j.appender.BLAH.MaxBackupIndex=10
    Below is the code in which i am using log4j logging
    import javax.servlet.*;
    import javax.servlet.http.*;
    import java.io.PrintWriter;
    import java.io.IOException;
    import org.apache.log4j.Logger;
    import org.apache.log4j.PropertyConfigurator;
    public class rectest extends HttpServlet
    private static final String CONTENT_TYPE = "text/html; charset=windows-1252";
    public void init(ServletConfig config) throws ServletException
    super.init(config);
    String prefix = "D:/jdkwork/work/App/testing";
    String file = getInitParameter("log4j-init-file");
    // if the log4j-init-file is not set, then no point in trying
    if(file != null) {
    PropertyConfigurator.configure(prefix+file);
    private static Logger log =Logger.getLogger(rectest.class);
    public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException
    doPost(request,response);
    public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException
    response.setContentType(CONTENT_TYPE);
    PrintWriter out = response.getWriter();
    out.println("<html>");
    out.println("<head><title>rectest</title></head>");
    out.println("<body>");
    log.info("this is a test");
    out.println("<p>The servlet has received a POST. This is the reply.</p>");
    out.println("</body></html>");
    out.close();
    I deploy the war file in jboss4 and run it. It runs smoothly and when deploys the war file, all the info messages in the console are then logged to the log file of my application which is deployed in it. i am new to log4j and couldn't find solution for that. please help

    should i assume that there will be no help for this or there is no solution for which is offcourse not possible.

  • Problem with log4j.properties and level DEBUG

    Hi,
    I need some log4j help.
    I create 2 different appenders in the log4j.properties file
    and it works.
    This is my complete log4j.properties:
    log4j.logger.log1=DEBUG, log1
    log4j.logger.log2=DEBUG, log2
    log4j.appender.log1=org.apache.log4j.DailyRollingFileAppender
    log4j.appender.log1.File=${StandardLogPath}
    log4j.appender.log1.DatePattern='.'yyyy-MM-dd
    log4j.appender.log1.Append=true
    #log4j.appender.log1.Threshold=DEBUG
    log4j.appender.log1.layout=org.apache.log4j.PatternLayout
    log4j.appender.log1.layout.ConversionPattern=%d{dd MMM yyyy HH:mm:ss} [%-5p] %-25c{1} %m%n
    log4j.appender.log2=org.apache.log4j.DailyRollingFileAppender
    log4j.appender.log2.File=${StandardLogQueryPath}
    log4j.appender.log2.DatePattern='.'yyyy-MM-dd
    log4j.appender.log2.Append=true
    log4j.appender.log2.layout=org.apache.log4j.PatternLayout
    log4j.appender.log2.layout.ConversionPattern=%d{dd MMM yyyy HH:mm:ss} [%-5p] %-25c{1} %m%nAnd here's my logging code:
    import org.apache.log4j.Logger;
    Logger log = Logger.getLogger("log1");
    Logger logQuery = Logger.getLogger("log2");
    log.debug("loggerDebug");
    logQuery.debug("loggerDebug");
    log.info("loggerInfo");
    logQuery.info("loggerInfo");The problem is that "loggerDebug" is not written to all appenders (only "loggerInfo").
    In fact if I print:
    System.out.println( log.getEffectiveLevel().toString() );result that the level is INFO and I known that if level is INFO then DEBUG is disable.
    But why the level is INFO????
    Someone can suggest me a solution?
    Thank you very much

    You're so over-sensitive you: when an OP doesn't respond anymore
    to your last reply it implies that you've solved the problem and
    (implicitly) that the OP is very grateful to you. Why do you always
    have to be so explicit about matters? ;-)
    Because I'm not one of those Dutch people ;-)Yes, that's us, the Dutch: mysteriously smiling and keeping silent all the
    time. That's why they call us the Asians of Western Europe ;-)
    ps. There are nice exception to the rule sometimes though.
    Yes, and unfortunately they do seem to be the exception rather than
    the rule. It would be nice to catch one a bit more often.True; that's the internet generation: grab all the information that you can
    and don't give a f*ck about the guy who supplied the information. It's sad
    indeed.
    Maybe we should start a support group where we could thank each
    other now and then 'on behalf' of those little spoiled brats and complain
    about all those bad manners nowadays ;-)
    kind regards,
    Jos

  • Problem with LOG4J with NETWEAVER

    Hi All,
    I have one web project and one EJB project ,when i m trying to build my application its throwing me an error saying Class not found like :
    java.lang.NoClassDefFoundError: org/apache/log4j/Category
    Why its looking for category class ?? I have already set the log4j.jar in my WEB-INF/lib folder and log4j.properties in WEB-INF/classes .please let know how to solve this

    > seems you posted in the wrong section...this here is
    > migration stuff (changing operating system and/or
    > database system)
    I'm sorry but this section is originaly a pure Java/J2EE application migration forum, introduced with the release of the J2EE Migration Kit.
    So strictly speaking postings regarding how to migrate a specific SAP release to NetWeaver or DB migration issues are wrong here.
    Best regards
    Halil

  • Need help:  Problem with log4j

    Hi I am working on jsp ,ejb in my project, i am trying to run jsp file using oc4j , here below error is coming
    java.lang.nosuchmethoderror.org.apache.log4j.level org.apache.log4j.spi.loggingevent.getLevel()
    please give me sollution.

    Looks like you hav a jar loading issue.
    Look in the container directory for "log4j-*.jar" to see if there is use of multiple log4j instances

  • Getting error with Log4j

    Hi,
    Not sure if this is the right place to post this as it is a problem with log4j really and not java. Let me know if this needs moving.
    Here goes:
    I have a servlet in tomcat that uses log4j to log details, this works fine on all the systems at home and work, but I get the following error when it is run on our customers site:
    log4j: No appenders could be found for category (some.category.name).
    log4j: Please initialize the log4j system properly.
    I have looked this up on log4j's website, they give the following advice:
    Log4j does not have a default logging target. It is the user's responsibility to ensure that all categories can inherit an appender. This can be easily achieved by attaching an appender to the root category.
    This works fine off site? I have the following log4j.properties in the WEB-INF/classes dir in tomcat:
    log4j.rootCategory=DEBUG, dest1
    log4j.appender.dest1=org.apache.log4j.FileAppender
    log4j.appender.dest1.file=/rmx.log
    log4j.appender.dest1.layout=org.apache.log4j.PatternLayout
    log4j.appender.dest1.layout.ConversionPattern=%-5p %l %x: %m%nAny ideas?
    Thanks in advance.
    Phil Maskell

    I have added code similar to what you suggested,
    being deployed on Tomcat I get the following:
    java.class.path=C:\Program Files\Apache Group\Tomcat
    5.5\bin\bootstrap.jar
    Is this what I should get? This is on my working
    system.That was probably not a good test (in hindsight). Tomcat's classpath is evidently not where its servlet classloader looks for classes.
    My log4j code uses a logFactory, in a final class,
    will this have any effect on the class path?The fact that the class is final will have no effect on any classloading. I doubt whether a logfactory will either, but I don't know what that is.
    P.S I could post my Logger.java, but stupid thing is
    it works fine on all my systems, just not on the
    customers :(I put my log4j.properties in the web app's WEB-INF/classes directory, just like you did. If your customer's system is not working the same as yours then you are probably wasting your time looking at Java code. The two systems are not configured the same and you need to find the difference.

  • Log4j problem with JRockit

    When I use JRockit 8.1 SP2 with Log4j 1.2.8, it appears that JRockit handles reflection differently than the Sun JVM, because the log4j messages come back wrong under JRockit and work fine with Hotspot.
    I think if you do the following you will reproduce the issue:
    Set your ConversionPattern layout in Log4j to include Method lookup (%M) - for example:
    log4j.appender.stdout.layout.ConversionPattern=[%d{HH:mm:ss.SSS}] %5p %x %c.%M() line %L - %m%nGet some code to log a log4j message. Run it under the different JVMs and the log4j messages will give you different results.
    For example, under Sun's JVM, the method name is properly returned in the log message:
    [15:39:21.549] DEBUG  COMMON.com.mycompany.common.security.ldap.LdapManager.findGroupsSelectedAttributes() line 696 - <exit
    [15:39:21.948]  WARN  COMMON.com.mycompany.common.dao.DAOFactory.reset() line 244 - Resetting DAO cacheUnder JRockit, you get what appears to be the return type of the method. Sometimes it's instead of the method name, sometimes it's in addition to it:
    [16:12:45.014] DEBUG  COMMON.com.mycompany.common.security.ldap.LdapManager.List;() line 696 - <exit
    [16:12:45.034]  WARN  COMMON.com.mycompany.common.dao.DAOFactory.reset()V() line 244 - Resetting DAO cache

    We have seen this problem with JRockit before and it seems to be a compatability issue with log4j.
    Quoting Jim Brown of BEA:
    "The underlying problem appears to be that log4j is ignorant of the extended method argument and type data returned by JRockit."
    At this point, we have not changed anything in JRockit to avoid this.
    Kind regards, Cecilia Borg
    BEA WebLogic JRockit

  • Problem With MF 2727 nj

    We have just bught and installed Hp MF 2727nf
    while giving multiple copie sof signle document instea dof printing it on more than 1 paper its printing it in duplex mode on the same paper ....
    how can i make it print on single paper withotu duplex and second copy fo new page instead of printing same matter 2nd copy of back side of the same page ( duplex)

    Must have been a momentary abberation. I haven't been able to reproduce it. It might have been a problem with the way I included the source files the first time. The second time, I destroyed the old project and created a new one, copied the source files in, rebuilt, and didn't get the problem with missing the main class.
    However, I did have a problem with using SAXParser and log4j. Although they both work in the IDE, when I tried to run the .jar from the command line, Java couldn't find SAXParser or log4j.Logger classes. I ended up taking log4j completely out and changing to com.sun.org.apache.xerces.internal.parsers.SAXParser, then it worked fine. That happened with both JSE and Eclipse; so it might be a classpath problem. Frustrating in any case.
    Thanks for the help.
    Brian

  • Problem with deploying SPLService (CC&B2.2.0) on OAS

    Hi,
    I have a problem with installation CC&B 2.2.0.
    I have this error during the deploying it on Oracle Application Server:
    09/01/28 08:23:22 Start process
    09/01/28 08:23:30 Oracle Containers for J2EE 10g (10.1.3.1.0) initialized
    - 08:25:46,009 [DeployerRunnable Thread for SPLService] INFO (service.impl.ServiceBeanContext) Initializing Service Bean
    - 08:25:46,025 [DeployerRunnable Thread for SPLService] INFO (shared.environ.ApplicationProperties) loaded properties from resource spl.properties: {spl.runtime.service.extraInstallationServices=CILTINCP, spl.runtime.cobol.remote.jvmcommand=C:/PFiles/Java/jdk1.5.0_09/bin/java.exe, spl.tools.loaded.applications=base,ccb,cm, spl.runtime.cobol.remote.jvmcount=2, spl.runtime.socket.file.dir=C:/spl/ccb/runtime, spl.runtime.cobol.sql.fetchSize=50, spl.runtime.cobol.cobrcall=false, spl.runtime.cobol.encoding=UTF8, spl.runtime.cobol.sql.disableQueryCache=false, com.splwg.grid.online.enabled=true, spl.runtime.utf8Database=true, spl.runtime.cobol.remote.jvmoptions=-Xmx512m -server -Dfile.encoding=ISO8859_1 -cp C:/spl/ccb/splapp/standalone/config;C:/spl/ccb/splapp/standalone/lib/activation_api-1.1.jar;C:/spl/ccb/splapp/standalone/lib/commons-beanutils-core-1.7.0.jar;C:/spl/ccb/splapp/standalone/lib/commons-codec-1.3.jar;C:/spl/ccb/splapp/standalone/lib/commons-collections-2.1.1.jar;C:/spl/ccb/splapp/standalone/lib/commons-fileupload-1.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-httpclient-2.0.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-io-1.3.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-lang-2.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-logging-1.0.4.jar;C:/spl/ccb/splapp/standalone/lib/concurrent-1.3.4.jar;C:/spl/ccb/splapp/standalone/lib/dom4j-1.6.1.jar;C:/spl/ccb/splapp/standalone/lib/hibernate-3.2.5.ga.jar;C:/spl/ccb/splapp/standalone/lib/icu4j-3.6.1.jar;C:/spl/ccb/splapp/standalone/lib/jaxen-1.1.1.jar;C:/spl/ccb/splapp/standalone/lib/jcip-annotations.jar;C:/spl/ccb/splapp/standalone/lib/jta.jar;C:/spl/ccb/splapp/standalone/lib/jtds-1.2.jar;C:/spl/ccb/splapp/standalone/lib/log4j-1.2.15.jar;C:/spl/ccb/splapp/standalone/lib/mail_api-1.4.jar;C:/spl/ccb/splapp/standalone/lib/mfcobol.jar;C:/spl/ccb/splapp/standalone/lib/ojdbc5-11.1.0.6.0.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-collation.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-mapping.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-utility.jar;C:/spl/ccb/splapp/standalone/lib/orai18n.jar;C:/spl/ccb/splapp/standalone/lib/serializer-2.7.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-base-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-ccb-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-servicebeaninterface-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-serviceclient-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-shared-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-web-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-xai-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/xalan-2.7.0.jar;C:/spl/ccb/splapp/standalone/lib/xmlparserv2.jar;C:/spl/ccb/splapp/standalone/lib/xquery.jar;C:/spl/ccb/splapp/standalone/lib/xstream-1.2.1.jar;C:/spl/ccb/splapp/standalone/lib/yjp-controller-api-redist.jar, spl.runtime.environ.init.dir=C:/spl/ccb/etc, com.splwg.grid.distThreadPool.threads.DEFAULT=5, spl.runtime.cobol.sql.cache.maxTotalEntries=1000, spl.runtime.oracle.statementCacheSize=300, spl.runtime.cobol.remote.rmiStartPort=6503, spl.runtime.cobol.sql.cursoredCache.maxRows=10, spl.runtime.cobol.remote.jvm=true, com.splwg.batch.scheduler.daemon=true, spl.runtime.sql.highValue=}
    - 08:25:46,025 [DeployerRunnable Thread for SPLService] INFO (shared.context.ApplicationMode) Application set to production mode
    - 08:25:46,041 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Creating default context
    - 08:25:47,697 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Loading lookups for runtime discovery of implemented lookups in application
    - 08:25:48,228 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Done loading lookups for discovery, time 526,639 ms
    - 08:25:51,259 [DeployerRunnable Thread for SPLService] INFO (shared.context.ContextLoader) Discovering lookups for base
    - 08:25:51,525 [DeployerRunnable Thread for SPLService] INFO (shared.context.ContextLoader) Done discovering base lookups (generated=203, manual=23), time 263,781 ms
    - 08:25:54,869 [DeployerRunnable Thread for SPLService] INFO (shared.context.ContextLoader) Discovering lookups for ccb
    - 08:25:55,134 [DeployerRunnable Thread for SPLService] INFO (shared.context.ContextLoader) Done discovering ccb lookups (generated=439, manual=81), time 257,230 ms
    - 08:25:55,197 [DeployerRunnable Thread for SPLService] WARN (shared.environ.ContextManagedObjectSet) Could not load resource com/splwg/cm/domain/contextManagedObjects.xml on classpath. This may be harmless but could mean a problem with the classpath. Please verify that the classpath for application cm is correctly configured.
    - 08:26:07,415 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering lookups
    - 08:26:07,900 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 613 lookups registered, time 483,437 ms
    - 08:26:07,900 [DeployerRunnable Thread for SPLService] INFO (support.context.ComponentContainerLookupHelper) Initializing constants on 642 lookup interface classes
    - 08:26:08,759 [DeployerRunnable Thread for SPLService] INFO (support.context.ComponentContainerLookupHelper) Done initializing lookup constants, time 862,978 ms
    - 08:26:08,759 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering Entities
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 857 entities registered, time 2 621,264 ms
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering Code Description queries
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 50 code/description queries registered, time 0,085 ms
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering algorithm spots
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 183 algorithm spots registered, time 0,382 ms
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering algorithm components
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 68 algorithm components registered, time 0,087 ms
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering batch jobs
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 21 batch jobs registered, time 0,052 ms
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering Components
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 489 components registered, time 4,287 ms
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering Change Handlers
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 237 handlers registered, time 0,913 ms
    - 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering Services
    - 08:26:11,399 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 460 services registered, time 13,970 ms
    - 08:26:11,399 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering cobol programs
    - 08:26:11,696 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 351 cobol copybooks registered, time 293,026 ms
    - 08:26:11,696 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering cobol programs
    - 08:26:11,696 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 105 cobol programs registered, time 0,094 ms
    - 08:26:11,696 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Building hibernate configuration
    - 08:26:11,696 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Adding 857 hibernate mappings
    - 08:26:13,603 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 100 mappings
    - 08:26:14,321 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 200 mappings
    - 08:26:15,056 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 300 mappings
    - 08:26:15,759 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 400 mappings
    - 08:26:16,462 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 500 mappings
    - 08:26:17,118 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 600 mappings
    - 08:26:17,759 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 700 mappings
    - 08:26:18,415 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 800 mappings
    - 08:26:18,790 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 857 mappings
    - 08:26:18,790 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Done building hibernate configuration, time 7 095,676 ms
    - 08:26:18,790 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Building hibernate session factory
    - 08:26:20,165 [DeployerRunnable Thread for SPLService] INFO (hibernate.connection.ConnectionProviderFactory) Initializing connection provider: org.hibernate.connection.C3P0ConnectionProvider
    - 08:26:20,165 [DeployerRunnable Thread for SPLService] INFO (hibernate.connection.C3P0ConnectionProvider) C3P0 using driver: oracle.jdbc.driver.OracleDriver at URL: jdbc:oracle:thin:@localhost:1521:ccb
    - 08:26:20,165 [DeployerRunnable Thread for SPLService] INFO (hibernate.connection.C3P0ConnectionProvider) Connection properties: {user=cisuser, password=****}
    - 08:26:20,165 [DeployerRunnable Thread for SPLService] INFO (hibernate.connection.C3P0ConnectionProvider) autocommit mode: false
    - 08:26:20,181 [DeployerRunnable Thread for SPLService] INFO (v2.log.MLog) MLog clients using log4j logging.
    - 08:26:20,259 [DeployerRunnable Thread for SPLService] INFO (v2.c3p0.C3P0Registry) jdk1.5 management interfaces unavailable... JMX support disabled.
    java.lang.SecurityException: Unauthorized access from application: SPLService to MBean: java.lang:type=ClassLoading
         at oracle.oc4j.admin.jmx.shared.UserMBeanServer.checkRegisterAccess(UserMBeanServer.java:873)
         at oracle.oc4j.admin.jmx.shared.UserMBeanServer.registerMBean(UserMBeanServer.java:400)
         at oracle.oc4j.admin.jmx.server.state.LocalizationFilterMBeanServer.registerMBean(LocalizationFilterMBeanServer.java:348)
         at sun.management.ManagementFactory$1.run(ManagementFactory.java:240)
         at java.security.AccessController.doPrivileged(Native Method)
         at sun.management.ManagementFactory.addMBean(ManagementFactory.java:235)
         at sun.management.ManagementFactory.addMBean(ManagementFactory.java:223)
         at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:266)
         at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:512)
         at com.mchange.v2.c3p0.management.ActiveManagementCoordinator.<init>(ActiveManagementCoordinator.java:42)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
         at java.lang.Class.newInstance0(Class.java:350)
         at java.lang.Class.newInstance(Class.java:303)
         at com.mchange.v2.c3p0.C3P0Registry.<clinit>(C3P0Registry.java:134)
         at com.mchange.v2.c3p0.impl.DriverManagerDataSourceBase.<init>(DriverManagerDataSourceBase.java:206)
         at com.mchange.v2.c3p0.DriverManagerDataSource.<init>(DriverManagerDataSource.java:60)
         at com.mchange.v2.c3p0.DriverManagerDataSource.<init>(DriverManagerDataSource.java:56)
         at com.mchange.v2.c3p0.DataSources.unpooledDataSource(DataSources.java:152)
         at org.hibernate.connection.C3P0ConnectionProvider.configure(C3P0ConnectionProvider.java:154)
         at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124)
         at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:56)
         at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:414)
         at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:62)
         at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009)
         at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292)
         at com.splwg.base.support.context.ApplicationContext.buildSessionFactory(ApplicationContext.java:152)
         at com.splwg.base.support.context.ContextFactory.buildContext(ContextFactory.java:114)
         at com.splwg.base.support.context.ContextFactory.buildContext(ContextFactory.java:88)
         at com.splwg.base.support.context.ContextFactory.createDefaultContext(ContextFactory.java:497)
         at com.splwg.ejb.service.impl.ServiceBeanContext.initializeApplicationContext(ServiceBeanContext.java:79)
         at com.splwg.ejb.service.impl.ServiceBeanContext.initialize(ServiceBeanContext.java:27)
         at com.splwg.ejb.service.impl.ServiceBean.<clinit>(ServiceBean.java:43)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:242)
         at com.evermind.server.ejb.deployment.BeanDescriptor.initialize(BeanDescriptor.java:288)
         at com.evermind.server.ejb.deployment.ExposableBeanDescriptor.initialize(ExposableBeanDescriptor.java:173)
         at com.evermind.server.ejb.deployment.SessionBeanDescriptor.initialize(SessionBeanDescriptor.java:225)
         at com.evermind.server.ejb.deployment.EJBPackage.initialize(EJBPackage.java:999)
         at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:852)
         at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:217)
         at com.evermind.server.Application.setConfig(Application.java:413)
         at com.evermind.server.Application.setConfig(Application.java:314)
         at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1853)
         at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:512)
         at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:196)
         at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
         at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
         at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
         at java.lang.Thread.run(Thread.java:595)
    Can anyone help me to resolve this?
    Thanks - Michael

    Yes, SYSUSER is defined and it is a member of cisusers group.
    on another forum I found a solution for "Unauthorized access exc...". I added "-Doc4j.jmx.security.proxy.off=true" to "Start-parameters: Java Options". Now I don't have this error, but I have another:
    - 09:17:53,725 [DeployerRunnable Thread for SPLService] INFO (cobol.host.CobolHostStartup) Using provided java command for remote cobol execution: C:/PFiles/Java/jdk1.5.0_09/bin/java.exe
    - 09:17:53,725 [DeployerRunnable Thread for SPLService] INFO (cobol.host.CobolHostStartup) Using provided java command options for remote cobol execution: -Xmx512m -server -Dfile.encoding=ISO8859_1 -cp C:/spl/ccb/splapp/standalone/config;C:/spl/ccb/splapp/standalone/lib/activation_api-1.1.jar;C:/spl/ccb/splapp/standalone/lib/commons-beanutils-core-1.7.0.jar;C:/spl/ccb/splapp/standalone/lib/commons-codec-1.3.jar;C:/spl/ccb/splapp/standalone/lib/commons-collections-2.1.1.jar;C:/spl/ccb/splapp/standalone/lib/commons-fileupload-1.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-httpclient-2.0.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-io-1.3.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-lang-2.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-logging-1.0.4.jar;C:/spl/ccb/splapp/standalone/lib/concurrent-1.3.4.jar;C:/spl/ccb/splapp/standalone/lib/dom4j-1.6.1.jar;C:/spl/ccb/splapp/standalone/lib/hibernate-3.2.5.ga.jar;C:/spl/ccb/splapp/standalone/lib/icu4j-3.6.1.jar;C:/spl/ccb/splapp/standalone/lib/jaxen-1.1.1.jar;C:/spl/ccb/splapp/standalone/lib/jcip-annotations.jar;C:/spl/ccb/splapp/standalone/lib/jta.jar;C:/spl/ccb/splapp/standalone/lib/jtds-1.2.jar;C:/spl/ccb/splapp/standalone/lib/log4j-1.2.15.jar;C:/spl/ccb/splapp/standalone/lib/mail_api-1.4.jar;C:/spl/ccb/splapp/standalone/lib/mfcobol.jar;C:/spl/ccb/splapp/standalone/lib/ojdbc5-11.1.0.6.0.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-collation.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-mapping.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-utility.jar;C:/spl/ccb/splapp/standalone/lib/orai18n.jar;C:/spl/ccb/splapp/standalone/lib/serializer-2.7.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-base-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-ccb-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-servicebeaninterface-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-serviceclient-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-shared-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-web-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-xai-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/xalan-2.7.0.jar;C:/spl/ccb/splapp/standalone/lib/xmlparserv2.jar;C:/spl/ccb/splapp/standalone/lib/xquery.jar;C:/spl/ccb/splapp/standalone/lib/xstream-1.2.1.jar;C:/spl/ccb/splapp/standalone/lib/yjp-controller-api-redist.jar
    - 09:17:53,725 [DeployerRunnable Thread for SPLService] INFO (cobol.host.CobolHostStartup) Using starting port number 6503 for remote cobol execution.
    - 09:17:53,740 [DeployerRunnable Thread for SPLService] INFO (cobol.host.SocketStrategy) Socket strategy set to com.splwg.base.support.cobol.host.sockets.WindowsPipeSocketStrategy
    - 09:17:53,756 [DeployerRunnable Thread for SPLService] DEBUG (host.sockets.WindowsPipeSocket) Creating client socket for named pipe remoteJvmPipe6504
    - 09:17:53,787 [JVM Socket Listener] DEBUG (support.context.ThreadlocalStorage) Added entry to ThreadlocalStorage global map, current size: 3
    - 09:17:53,787 [JVM Socket Listener] DEBUG (host.sockets.WindowsPipeSocket) Creating server socket for named pipe remoteJvmPipe6504
    - 09:17:53,787 [DeployerRunnable Thread for SPLService] INFO (cobol.host.CobolHostStartup) Using active JVM count of 2 for remote cobol execution.
    - 09:17:53,803 [DeployerRunnable Thread for SPLService] DEBUG (host.sockets.WindowsPipeSocket) Creating client socket for named pipe remoteJvmPipe6506
    - 09:17:53,803 [DeployerRunnable Thread for SPLService] DEBUG (cobol.host.RemoteJVMFactoryImpl) Command line used to launch child JVM: C:/PFiles/Java/jdk1.5.0_09/bin/java.exe -Xmx512m -server -Dfile.encoding=ISO8859_1 -cp C:/spl/ccb/splapp/standalone/config;C:/spl/ccb/splapp/standalone/lib/activation_api-1.1.jar;C:/spl/ccb/splapp/standalone/lib/commons-beanutils-core-1.7.0.jar;C:/spl/ccb/splapp/standalone/lib/commons-codec-1.3.jar;C:/spl/ccb/splapp/standalone/lib/commons-collections-2.1.1.jar;C:/spl/ccb/splapp/standalone/lib/commons-fileupload-1.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-httpclient-2.0.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-io-1.3.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-lang-2.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-logging-1.0.4.jar;C:/spl/ccb/splapp/standalone/lib/concurrent-1.3.4.jar;C:/spl/ccb/splapp/standalone/lib/dom4j-1.6.1.jar;C:/spl/ccb/splapp/standalone/lib/hibernate-3.2.5.ga.jar;C:/spl/ccb/splapp/standalone/lib/icu4j-3.6.1.jar;C:/spl/ccb/splapp/standalone/lib/jaxen-1.1.1.jar;C:/spl/ccb/splapp/standalone/lib/jcip-annotations.jar;C:/spl/ccb/splapp/standalone/lib/jta.jar;C:/spl/ccb/splapp/standalone/lib/jtds-1.2.jar;C:/spl/ccb/splapp/standalone/lib/log4j-1.2.15.jar;C:/spl/ccb/splapp/standalone/lib/mail_api-1.4.jar;C:/spl/ccb/splapp/standalone/lib/mfcobol.jar;C:/spl/ccb/splapp/standalone/lib/ojdbc5-11.1.0.6.0.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-collation.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-mapping.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-utility.jar;C:/spl/ccb/splapp/standalone/lib/orai18n.jar;C:/spl/ccb/splapp/standalone/lib/serializer-2.7.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-base-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-ccb-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-servicebeaninterface-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-serviceclient-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-shared-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-web-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-xai-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/xalan-2.7.0.jar;C:/spl/ccb/splapp/standalone/lib/xmlparserv2.jar;C:/spl/ccb/splapp/standalone/lib/xquery.jar;C:/spl/ccb/splapp/standalone/lib/xstream-1.2.1.jar;C:/spl/ccb/splapp/standalone/lib/yjp-controller-api-redist.jar com.splwg.base.support.cobol.host.RemoteJVM 1 6505 6506 2
    - 09:17:53,834 [DeployerRunnable Thread for SPLService] DEBUG (cobol.host.RemoteRequestTimer) Request made:RegisterServerExecuterCommand for connection 5040264954652086151
    - 09:17:53,834 [DeployerRunnable Thread for SPLService] DEBUG (cobol.host.RemoteRunnerImpl) Invoking command: RegisterServerExecuterCommand
    - 09:17:53,850 [DeployerRunnable Thread for SPLService] DEBUG (cobol.host.SocketStrategy) Attempting to create socket on port 6506
    - 09:17:53,850 [DeployerRunnable Thread for SPLService] DEBUG (host.sockets.WindowsPipeSocket) Creating client socket for named pipe remoteJvmPipe6506
    - 09:17:53,850 [DeployerRunnable Thread for SPLService] WARN (cobol.host.SocketStrategy) Unable to create socket on port 6506
    java.net.ConnectException: Error: Could not open pipe
    caused by system error: cannot find the file specified.
         at com.splwg.base.support.cobol.host.sockets.WindowsPipeSocket.connectToPipe(Native Method)
         at com.splwg.base.support.cobol.host.sockets.WindowsPipeSocket.<init>(WindowsPipeSocket.java:64)
         at com.splwg.base.support.cobol.host.sockets.WindowsPipeSocket.createSocket(WindowsPipeSocket.java:100)
         at com.splwg.base.support.cobol.host.sockets.WindowsPipeSocket.connect(WindowsPipeSocket.java:96)
         at com.splwg.base.support.cobol.host.sockets.WindowsPipeSocketStrategy.openSocket(WindowsPipeSocketStrategy.java:32)
         at com.splwg.base.support.cobol.host.SocketStrategy.unsafeOpen(SocketStrategy.java:119)
         at com.splwg.base.support.cobol.host.SocketStrategy.open(SocketStrategy.java:104)
         at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.createNewHolder(OptimizedRemoteExecuterStub.java:162)
         at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.getStreamHolder(OptimizedRemoteExecuterStub.java:125)
         at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.invoke(OptimizedRemoteExecuterStub.java:46)
         at com.splwg.base.support.cobol.host.RemoteRunnerImpl.invoke(RemoteRunnerImpl.java:89)
         at com.splwg.base.support.cobol.host.RemoteJVMConnectionImpl.createRemoteRunner(RemoteJVMConnectionImpl.java:148)
         at com.splwg.base.support.cobol.host.RemoteJVMConnectionImpl.<init>(RemoteJVMConnectionImpl.java:67)
         at com.splwg.base.support.cobol.host.RemoteJVMFactoryImpl.addConnection(RemoteJVMFactoryImpl.java:92)
         at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider.addNewConnection(RotatingCommandRunnerProvider.java:135)
         at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider.addNecessaryConnections(RotatingCommandRunnerProvider.java:121)
         at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider.access$800(RotatingCommandRunnerProvider.java:30)
         at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.performPollingActions(RotatingCommandRunnerProvider.java:257)
         at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.performRunLoop(RotatingCommandRunnerProvider.java:239)
         at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.run(RotatingCommandRunnerProvider.java:230)
         at java.lang.Thread.run(Thread.java:595)
    other processes don't use port 6506, java.exe opens this port few secounds after starting genoasdeploy.cmd
    Edited by: user4630304 on 2009-02-03 02:29

  • Problems with JUnit

    Hello,
    I'm using KODO 2.4.3 and JUnit 3.8.1 and log4j 1.2.8.
    I have a problem when executing TestCases with JUnit! I think it have to
    do with log4j.
    The Error is:
    javax.jdo.JDOFatalUserException: Exception thrown by
    getPersistenceManagerFactory(Properties)
    Caused by: org.apache.commons.logging.LogConfigurationException: Class
    org.apache.commons.logging.impl.Log4JCategoryLog does not implement Log
         at
    org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:416)
    I regret, but JUnit doesnt show the complete output of the eexception and
    you also can't copy and paste it! But it must have to do with the
    log4j-Framework (which makes alyways problems with JUnit?)...
    If I start JUnit without "-Dlog4j.ignoreTCL=true" then Errors occur with
    log4j already before KODO is called...
    Thanks for any idea.
    Best wishes
    BERND

    Bernd-
    Hmmm ... I really think that this problem is because you have another
    version of log4j somewhere in your CLASSPATH (or else the classpath that
    ant is using). Do you get this exception if you try to use the junit
    test cases stand-alone (by using the junit TestRunner class)?
    Can you scour your classpath and any classpath that is being used by
    ant to ensure that you do not have another log4j or commons-logging jar
    anywhere?
    In article <[email protected]>, Michael wrote:
    I'm using 1.2.8 so I doubt it's the version. It's possible to have two
    versions of the apache commons logging jar files, since they've renamed it
    from commons-logging to jakarta-commons-logging a while back.
    "Marc Prudhommeaux" <[email protected]> wrote in message
    news:[email protected]...
    Bernd-
    Do you have a different version of log4j in your CLASSPATH (perhaps
    being used by ant)? You might want to try log4j 1.2.6, which does not
    exhibit any problems for us.
    In article <[email protected]>, Bernd Ruecker wrote:
    Yes, I have both...
    Michael wrote:
    Do you have both log4j & commons-logging jar files in your classpath??
    "Bernd Ruecker" <[email protected]> wrote in message
    news:[email protected]...
    Hello,
    I'm using KODO 2.4.3 and JUnit 3.8.1 and log4j 1.2.8.
    I have a problem when executing TestCases with JUnit! I think it have
    to
    do with log4j.
    The Error is:
    javax.jdo.JDOFatalUserException: Exception thrown by
    getPersistenceManagerFactory(Properties)
    Caused by: org.apache.commons.logging.LogConfigurationException:Class
    org.apache.commons.logging.impl.Log4JCategoryLog does not implementLog
    at
    org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryI
    mpl.java:416)
    I regret, but JUnit doesnt show the complete output of the eexception
    and
    you also can't copy and paste it! But it must have to do with the
    log4j-Framework (which makes alyways problems with JUnit?)...
    If I start JUnit without "-Dlog4j.ignoreTCL=true" then Errors occurwith
    log4j already before KODO is called...
    Thanks for any idea.
    Best wishes
    BERND
    Marc Prud'hommeaux [email protected]
    SolarMetric Inc. http://www.solarmetric.com

  • Weird Goings on with Log4J on Linux

    Hi there,
    I'm using the Log4J package to output logging statements to catalina.out from my webapp. After a while the logging statements seem to begin to duplicate exponentially. Each statement is printed out multiple times from the same thread. I know Log4J is thread safe, and this doesnt happen on windows, Im running Mandrake 10.1
    Anyone seen this before, Is this a problem with Mandrake rather than Log4J.
    John.

    I don't use any auto-syncing at all - it's all manual.
    You indicate you are not using auto-sync, which is most likely the root of your problem.
    When using auto-sync, if you rate a track on the iPod... the rating will be be maintained and sync back to your iTunes library.
    If you are not using auto-sync, this will not happen and you are likely to get undesireable results upon your next manual iTunes sync.

  • Problems with passing arguments to app

    Hi.
    I have a litle problem with passing arguments. I create a dynamic jnlp file using jsp. This is my code:
    <%
    response.setContentType("application/x-java-jnlp-file");
    String l = request.getParameter("login");
    String p = request.getParameter("pass");
    out.println("<?xml version=\"1.0\" encoding=\"UTF-8\"?>");
    out.println("<jnlp spec=\"1.0+\" codebase=\"http://212.244.104.27:8080/PzP_INSTALL/\" href=\"pzp.jsp\">");
    out.println("<information>");
    out.println("<title>xxx</title>");
    out.println("<vendor>xxxx</vendor>");
    out.println("<homepage href=\"main.jsp\"/>");
    out.println("<description>text</description>");
    out.println("<offline-allowed/>");
    out.println("</information>");
    out.println("<security>");
    out.println("<all-permissions/>");
    out.println("</security>");
    out.println("<resources>");
    out.println("<j2se version=\"1.4+\"/>");
    out.println("<jar href=\"jars/pzp.jar\" main=\"true\" download=\"eager\"/>");
    out.println("<jar href=\"jars/config.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jars/commons-beanutils.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jars/commons-collections.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jars/commons-digester.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jars/commons-logging.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jars/commons-validator.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jars/easclient.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jars/easj2ee.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jars/jakarta-oro-2.0.7.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jars/jbcl.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jars/log4j-1.2.7.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jars/jdom.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jars/xercesImpl.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<property name =\"javaws.login \"  " + "value=" + "\"" + l + "\"" + "/>");
    out.println("<property name =\"javaws.pass \"  " + "value=" + "\"" + p + "\"" + "/>");
    out.println("</resources>");
    out.println("<application-desc main-class=\"aaa.bbb.ccc.MyClass\"/>");
    out.println("</jnlp>");
    %>My problem is when i have the href tag filled, the arguments that i passed equlas null, when i remove the href everything is ok besides that the app doesnt show in application manager and doesnt create an icon on the desktop.
    out.println("<jnlp spec=\"1.0+\" codebase=\"http://62.89.104.27:8080/PzP_INSTALL/\" href=\"pzp.jsp\">");
    Any help would be appreciated.

    Hello again.
    Thanks for your replay but unfortunetly it doesnt work too :-(
    I've tried to use the out.println statemants in the servlet instead of using a jsp page but the error is the same. Please look at my code and tell me if you can what could be wrong.
    This is the error message:
    An error occurred while launching/running the application.
    Title: PZP
    Vendor: SPEED
    Category: Download Error
    Unable to load resource: http://212.89.104.27:8080/PzP_INSTALL/ServletPZP
    Servlet code.
    package pzp_install;
    import javax.servlet.*;
    import javax.servlet.http.*;
    import java.io.*;
    import java.util.*;
    import pzp_install.LoginBean;
    import javax.swing.JOptionPane;
    public class ServletPZP extends HttpServlet {
      public void init(ServletConfig config) throws ServletException {
      super.init(config);
      config.getServletContext().setAttribute("ServletPZP", this);
      public void doPost(HttpServletRequest request, HttpServletResponse resp)
      throws IOException {
      PrintWriter out = resp.getWriter();
    // Get the value of the request parameter
      String login = request.getParameter("login");
      String pass = request.getParameter("pass");
    resp.setContentType("application/x-java-jnlp-file");
    out.println("<?xml version=\"1.0\" encoding=\"UTF-8\"?>");
    out.println("<jnlp spec=\"1.0+\" codebase=\"http://212.89.104.27:8080/PzP_INSTALL/\" href=\"/servletpzp\">");
    out.println("<information>");
    out.println("<title>PZP</title>");
    out.println("<vendor>SPEED</vendor>");
    out.println("<homepage href=\"main.jsp\"/>");
    out.println("<description>Aplikacja wspomagajaca zarzadzanie zleceniami</description>");
    out.println("<offline-allowed/>");
    out.println("</information>");
    out.println("<security>");
    out.println("<all-permissions/>");
    out.println("</security>");
    out.println("<resources>");
    out.println("<j2se version=\"1.4+\"/>");
    out.println("<jar href=\"pzp.jar\" main=\"true\" download=\"eager\"/>");
    out.println("<jar href=\"config.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"commons-beanutils.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"commons-collections.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"commons-digester.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"commons-logging.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"commons-validator.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"easclient.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"easj2ee.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jakarta-oro-2.0.7.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jbcl.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"log4j-1.2.7.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"jdom.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<jar href=\"xercesImpl.jar\" main=\"false\" download=\"eager\"/>");
    out.println("<property name =\"javaws.login \"  " + "value=" + "\"" + login + "\"" + "/>");
    out.println("<property name =\"javaws.pass \"  " + "value=" + "\"" + pass + "\"" + "/>");
    out.println("</resources>");
    out.println("<application-desc main-class=\"pl.speednet.pzp.PzP\"/>");
    out.println("</jnlp>");
      public void destroy() {
      super.destroy();
    This is the brief of code which starts the servlet
    <form action="http://212.89.104.27:8080/PzP_INSTALL/servletpzp" method="post">
      <input type="hide" name="login" value=<%=l%>>
      <input type="hide" name="pass" value=<%=p%>>
      <input type=submit value=Start PZP>
    </form>
    This is the web.xml file code.
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
    <web-app>
      <servlet>
        <servlet-name>ServletPZP</servlet-name>
        <servlet-class>pzp_install.ServletPZP</servlet-class>
      </servlet>
      <servlet-mapping>
        <servlet-name>ServletPZP</servlet-name>
        <url-pattern>/servletpzp</url-pattern>
      </servlet-mapping>
      <mime-mapping>
        <extension>jar</extension>
        <mime-type>application/x-java-archive</mime-type>
      </mime-mapping>
      <mime-mapping>
        <extension>jnlp</extension>
        <mime-type>application/x-java-jnlp-file</mime-type>
      </mime-mapping>
    </web-app>

  • Not sure how to configure Weblogic with log4j.xml

    I tried something VERY similar to this. I wasn't sure where to put this code below. I figured in a Servlet environment, it should probably go in a Listener. I found an existing class inside of Spring that does exactly that: org.springframework.web.util.Log4jConfigListener
    I put my log4j configuration file into an entry in the classpath and configured web.xml as follows:
    <!-- Spring log4j parameters -->
            <context-param>
                <param-name>log4jConfigLocation</param-name>
                <param-value>classpath:gov/pa/dep/formu/resources/log4j.properties</param-value>
            </context-param>
            <context-param>
                <param-name>log4jRefreshInterval</param-name>
                <param-value>30000</param-value>
            </context-param>
            <!-- Spring Log4j config listener -->
         <listener>
              <listener-class>org.springframework.web.util.Log4jConfigListener</listener-class>
         </listener>The server admin placed the actual log4j.properties file into an AppFileOverrides folder instead of under WEB-INF\classes. I don't know if this caused the problem or not. Since I also was using the DailyRollingFileAppender and running into problems LOSING my log entries each day because he file didn't get renamed, I followed Metalink BUG# 8459807, and used the datedFileAppender available at http://minaret.biz/tips/datedFileAppender.html.
    When the application started, the server log showed that log4j was being configured but none of my logging statements were going into the logs. It wasn't until the server admin placed a copy of log4j.properties (a different log4j.properties with a rolling file appender) that the log statements started going into the file that was configured based on web.xml.
    Surely, things can't be this difficult with log4j, and commons logging under WebLogic.
    All I want is APPLICATION LEVEL LOGS that are specific to the day.
    Can someone else elaborate on how they got this working?
    thanks a bunch,
    Eric

    Hi,
    The configuration wizard (config.sh) lets you create a WebLogic Domain, however and depending on others "Oracle Middleware" products installed on the same "Oracle Home" (directory where weblogic has been installed) the configuration wizard allows you create the new weblogic domain to support the others middleware products such as WebCenter.
    When I say support It means that Configuration Wizard allows you to create the weblogic resources like JDBC connections, JMS services, and deploys all applications that integrates another product such as WebCenter.
    I suggest create your domain with support for WebCenter and then from Admin Console create the JDBC resource to connect to other database such as JD Edwards database.
    I hope this help.

  • Logging with log4j in a Web app that uses TopLink

    The deployment engineer in my company is reporting problems with our first Web app that uses both log4j and TopLink. Apparently TopLink is failing to initialize correctly when log4j-1.2.8.jar is deployed to the WEB-INF/classes directory within the Web app.
    I know that 9iAS's Enterprise Manager uses an older version of log4j and I wonder if TopLink uses an older version too.
    Are there any known problems when using log4j 1.2.8 with TopLink 9.0.3?
    Thanks,
    Al Margheim

    Unfortunately, when I asked the deployment engineer for more information on the problem, he couldn't provide any, and since he moved the log4j library out of the application's WEB-INF\classes directory he can't reproduce the problem (whatever it was).
    Based on a variety of factors (including your response) I suspect that the people who encountered the problem misinterpreted the cause.
    If I can get him to put the log4j library back in WEB-INF\classes and get more specific information about the problem, and it still looks like a conflict between TopLink and log4j, I'll post the errors here.
    Thanks,
    Al Margheim

Maybe you are looking for

  • HOW DO I MERGE FILES FROM EMAC TO MACBOOK W/O having 2 logins?

    I used transfer manager to move files from old eMac to new MacBook ...now it is like I have two computers....I have to log off from the MACBOOK "side " and log in like I was on my old eBook to get to those files??? At a minimum I want my iPhotos and

  • Error in installing 9i on suse8.2

    Hi: I install oracle database 9i(9.2.0.1) for linux on SuSE8.2. It report error as follows(in make.log): gcc -o ctxhx -L/home/oracle/ora/OraHome1/ctx/lib/ -L/home/oracle/ora/OraHome1/lib/ -L/home/oracle/ora/OraHome1/lib/stubs/ /home/oracle/ora/OraHom

  • How to search case insensitive ?

    Is there any way to search case insensitive ? Because we use Remedy application, we can't change query like to use 'UPPER' or 'LOWER' functions. For example, SQL> desc test1 Name Null? Type A VARCHAR2(20) SQL> select * from test1; A TEST test SQL> se

  • Within SQL*Plus, get error code of host command

    Hello everyone, I am currently writing an SQL*Plus (Oracle 10g) that has a big logic and somewhere in the middle, I have to call a host command, which is an C++ function. I call it using SQL> HOST cd SQL> HOST cd bins SQL> HOST ./my_procedureBut, I n

  • No Oracle HTTP server service

    Hi, I have installed the Oracle Databse XE, I try to start Htmldb and I receive a message that it doesn't find the page. I tried with http://127.0.0.1:8080/htmldb, http://127.0.0.1:8087/htmldb and http://127.0.0.1:7777/htmldb, also replacing 127.0.0.