Error on loadjava with log4j

Hi.
I have a problem loading jar file: oracle 9.2.0.7.0 on unix server with jvm 1.3.1
Using sqlplus I didn't receive any error (PL/SQL procedure successfully completed.) on loading log4j-1.2.14.jar with the following command 6 java class (org/apache/log4j/jmx/...)are invalid:
call dbms_java.loadjava(' -r -v -schema NameOfSchema /orabkp/java/log4j-1.2.14.jar');
Executing the same command from unix command line
loadjava -r -v -u user/password@database -schema NameOfSchema /orabkp/java/log4j-1.2.14.jar
i received the following errors:
For class AbstractDynamicMBean (org/apache/log4j/jmx/)
errors : class NameOfSchema.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
same error for the following java class:
org/apache/log4j/jmx/Agent
org/apache/log4j/jmx/AppenderDynamicMBean
org/apache/log4j/jmx/HierarchyDynamicMBean
org/apache/log4j/jmx/LayoutDynamicMBean
org/apache/log4j/jmx/LoggerDynamicMBean
If I didn't insert -r (resolve) option, I will have a list of 50/60 java class invalid
Much appreciated, any help to understand why on sqlplus I didn't receive any message and a help to solve ORA error.
Thanks.

Hi Paolo:
These classes are part of JDK1.5 stack for JMX services, for example:
http://java.sun.com/j2se/1.5.0/docs/api/javax/management/MBeanInfo.html
If log4j.jar includes these classes may be is compiled with jdk 1.5, check if the essential classes of log4j do not returns invalid class format error.
JMX classes are not required if you use FileAppender or ConsoleAppender loggers.
Best regards, Marcelo.
PD: If you get invalid class format error you must to compile log4j sources using a JDK 1.3 compiler which is the JDK included into 9.x databases.

Similar Messages

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.

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

Error creating bean with name 'org.springframework.dao.annotation.Persisten

Hello
I am using Hibernate 4, Spring 3 , JSF 2.0 and Weblogic 10.3.6
When I start weblogic server and server starts successfully, however whenever it starts publishing application, I am getting the following exception.
Error creating bean with name
'org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor#0'
defined in ServletContext resource [/WEB-INF/applicationContext.xml]:
Initialization of bean failed; nested exception is
org.springframework.beans.factory.BeanCreationException:
 Caused By: org.springframework.beans.factory.BeanCreationException: Error creating
 bean with name 'entityManagerFactory'defined in ServletContext resource
 [/WEB-INF/applicationContext.xml]: Invocation of init method failed;
 nested exception is java.lang.NoSuchMethodError:
 javax.persistence.spi.PersistenceUnitInfo.getSharedCacheMode()Ljavax/persistence/
 SharedCacheMode;
Caused By: java.lang.NoSuchMethodError:
javax.persistence.spi.PersistenceUnitInfo.getSharedCacheMode()
Ljavax/persistence /SharedCacheMode; at
org.hibernate.ejb.util.LogHelper.logPersistenceUnitInfo(LogHelper.java:38) at
org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:525)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72) at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManager I have the following in applicationContext.xml
<beans xmlns="http://www.springframework.org/schema/beans"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tx="http://www.springframework.org/schema/tx"
 xmlns:context="http://www.springframework.org/schema/context"
 xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd">
 <context:component-scan base-package="net.test" />
 
 <bean id="DataSource" class="com.mchange.v2.c3p0.ComboPooledDataSource"
 destroy-method="close">
 <property name="driverClass" value="oracle.jdbc" />
 <property name="jdbcUrl" value="jdbc:oracle:thin:@server:1521:DB" />
 <property name="user" value="scott" />
 <property name="password" value="tiger" />
 <property name="maxPoolSize" value="10" />
 <property name="maxStatements" value="0" />
 <property name="minPoolSize" value="5" />
 </bean>
 <bean
 class="org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor" />
 
 <bean id="entityManagerFactory"
 class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
 <property name="dataSource" ref="DataSource" />
 <property name="packagesToScan" value="net.test.entity" />
 <property name="jpaVendorAdapter">
 <bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter">
 <property name="showSql" value="true" />
 <property name="generateDdl" value="false" />
 <property name="databasePlatform" value="${jdbc.dialectClass}" />
 </bean>
 </property>
 </bean>
 <bean id="defaultLobHandler" class="org.springframework.jdbc.support.lob.DefaultLobHandler" />
 
 <bean id="SessionFactory"
 class="org.springframework.orm.hibernate4.LocalSessionFactoryBean">
 <property name="dataSource" ref="DataSource" />
 <property name="annotatedClasses">
 <list>
 <value>net.test.entity.Department</value>
 <value>net.test.entity.Employees</value>
 </list>
 </property>
 <property name="hibernateProperties">
 <props>
 <prop key="hibernate.dialect">org.hibernate.dialect.Oracle10gDialect</prop>
 <prop key="hibernate.show_sql">true</prop>
 <prop key="hibernate.query.factory_class">org.hibernate.hql.internal.classic.ClassicQueryTranslatorFactory
 </prop>
 </props>
 </property>
 </bean>
 
 <tx:annotation-driven transaction-manager="txManager" />
 <tx:annotation-driven transaction-manager="transactionManager" />
 
 <bean id="txManager"
 class="org.springframework.orm.hibernate4.HibernateTransactionManager">
 <property name="sessionFactory" ref="SessionFactory" />
 </bean>
 <bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager">
 <property name="entityManagerFactory" ref="entityManagerFactory" />
 </bean>
 <context:annotation-config />
 <bean id="hibernateStatisticsMBean" class="org.hibernate.jmx.StatisticsService">
 <property name="statisticsEnabled" value="true" />
 <property name="sessionFactory" value="#{entityManagerFactory.sessionFactory}" />
 </bean>
 <bean name="ehCacheManagerMBean"
 class="org.springframework.cache.ehcache.EhCacheManagerFactoryBean" />
 <bean id="mbeanServer" class="org.springframework.jmx.support.MBeanServerFactoryBean">
 <property name="locateExistingServerIfPossible" value="true" />
 </bean>
 <bean id="jmxExporter" class="org.springframework.jmx.export.MBeanExporter"
 lazy-init="false">
 <property name="server" ref="mbeanServer" />
 <property name="registrationBehaviorName" value="REGISTRATION_REPLACE_EXISTING" />
 <property name="beans">
 <map>
 <entry key="SpringBeans:name=hibernateStatisticsMBean"
 value-ref="hibernateStatisticsMBean" />
 <entry key="SpringBeans:name=ehCacheManagerMBean" value-ref="ehCacheManagerMBean" />
 </map>
 </property>
 </bean>
</beans>
pom.xml
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
 http://maven.apache.org/maven-v4_0_0.xsd">
 <modelVersion>4.0.0</modelVersion>
 <groupId>net.test</groupId>
 <artifactId>myappp</artifactId>
 <packaging>war</packaging>
 <version>1.0-SNAPSHOT</version>
 <name>myappp</name>
 <url>http://maven.apache.org</url>
 <repositories>
 <repository>
 <id>prime-repo</id>
 <name>PrimeFaces Maven Repository</name>
 <url>http://repository.primefaces.org</url>
 <layout>default</layout>
 </repository>
 </repositories>
 <properties>
 <spring.version>3.1.1.RELEASE</spring.version>
 </properties>
 <dependencies>
 
 <dependency>
 <groupId>org.springframework</groupId>
 <artifactId>spring-core</artifactId>
 <version>${spring.version}</version>
 </dependency>
 <dependency>
 <groupId>org.springframework</groupId>
 <artifactId>spring-context</artifactId>
 <version>${spring.version}</version>
 </dependency>
 <dependency>
 <groupId>org.springframework</groupId>
 <artifactId>spring-web</artifactId>
 <version>${spring.version}</version>
 </dependency>
 <dependency>
 <groupId>org.springframework</groupId>
 <artifactId>spring-tx</artifactId>
 <version>${spring.version}</version>
 </dependency>
 <dependency>
 <groupId>org.springframework</groupId>
 <artifactId>spring-orm</artifactId>
 <version>${spring.version}</version>
 </dependency>
 <dependency>
 <groupId>org.springframework</groupId>
 <artifactId>spring-test</artifactId>
 <version>${spring.version}</version>
 </dependency>
 
 <dependency>
 <groupId>com.sun.faces</groupId>
 <artifactId>jsf-api</artifactId>
 <version>2.1.6</version>
 </dependency>
 <dependency>
 <groupId>com.sun.faces</groupId>
 <artifactId>jsf-impl</artifactId>
 <version>2.1.6</version>
 </dependency>
 <dependency>
 <groupId>javax.servlet</groupId>
 <artifactId>jstl</artifactId>
 <version>1.2</version>
 </dependency>
 
 <dependency>
 <groupId>org.primefaces</groupId>
 <artifactId>primefaces</artifactId>
 <version>3.4.2</version>
 </dependency>
 <dependency>
 <groupId>org.primefaces.themes</groupId>
 <artifactId>afterwork</artifactId>
 <version>1.0.8</version>
 </dependency>
 
 <dependency>
 <groupId>org.hibernate</groupId>
 <artifactId>hibernate-core</artifactId>
 <version>4.1.0.Final</version>
 </dependency>
 <dependency>
 <groupId>javassist</groupId>
 <artifactId>javassist</artifactId>
 <version>3.12.1.GA</version>
 </dependency>
 <dependency>
 <groupId>javax.inject</groupId>
 <artifactId>javax.inject</artifactId>
 <version>1</version>
 </dependency>
 
 <dependency>
 <groupId>com.oracle</groupId>
 <artifactId>ojdbc6</artifactId>
 <version>11.2.0.3</version>
 </dependency>
 <dependency>
 <groupId>c3p0</groupId>
 <artifactId>c3p0</artifactId>
 <version>0.9.1.2</version>
 </dependency>
 
 <dependency>
 <groupId>log4j</groupId>
 <artifactId>log4j</artifactId>
 <version>1.2.16</version>
 </dependency>
 <dependency>
 <groupId>org.testng</groupId>
 <artifactId>testng</artifactId>
 <version>6.4</version>
 </dependency>
 <dependency>
 <groupId>org.hibernate</groupId>
 <artifactId>hibernate-jpamodelgen</artifactId>
 <version>1.2.0.Final</version>
 </dependency>
 <dependency>
 <groupId>org.hibernate</groupId>
 <artifactId>hibernate-entitymanager</artifactId>
 <version>4.1.0.Final</version>
 </dependency>
 <dependency>
 <groupId>org.hibernate.javax.persistence</groupId>
 <artifactId>hibernate-jpa-2.0-api</artifactId>
 <version>1.0.1.Final</version>
 </dependency>
 <dependency>
 <groupId>org.apache.myfaces.extensions.cdi.core</groupId>
 <artifactId>myfaces-extcdi-core-api</artifactId>
 <version>1.0.5</version>
 <scope>compile</scope>
</dependency>
 <dependency>
 <groupId>org.hibernate</groupId>
 <artifactId>hibernate-ehcache</artifactId>
 <version>4.0.1.Final</version>
 </dependency>
 </dependencies>
 <build>
 <resources>
 <resource>
 <directory>src/main/resources</directory>
 </resource>
 </resources>
 <plugins>
 <plugin>
 <groupId>org.apache.maven.plugins</groupId>
 <artifactId>maven-compiler-plugin</artifactId>
 <configuration>
 <source>1.6</source>
 <target>1.6</target>
 <compilerArgument>-proc:none</compilerArgument>
 </configuration>
 </plugin>
 <plugin>
 <groupId>org.bsc.maven</groupId>
 <artifactId>maven-processor-plugin</artifactId>
 <version>2.0.6</version>
 <executions>
 <execution>
 <id>process</id>
 <goals>
 <goal>process</goal>
 </goals>
 <phase>generate-sources</phase>
 <configuration>
 
 <outputDirectory>target/metamodel</outputDirectory>
 </configuration>
 </execution>
 </executions>
 </plugin>
 </plugins>
 </build>
</project>In Weblogic 10.3.6 I have enabled JPA2 support by adding the following in commEnv.cmd
@rem Enable JPA 2.0 functionality on WebLogic Server
set PRE_CLASSPATH=%BEA_HOME%\modules\javax.persistence_1.1.0.0_2-0.jar;
%BEA_HOME%\modules\com.oracle.jpa2support_1.0.0.0_2-1.jarApplication which works on WLS 10.3.6 is http://download.oracle.com/otn/nt/middleware/11g/wls/1036/wls1036_dev.zip and the one which is not working is
http://download.oracle.com/otn/nt/middleware/11g/wls/1036/wls1036_win32.exe.
How can I resolve these errors and exceptions? Any help is highly appreciable.
Thanks

Looks like you might have a spelling error in your spring config, or are trying to set a read-only property. BdasInterfaceManagerImpl has been configured as having a method called setBdasInterfaceJdbcDao() : does it?
By the way, we now know that you're writing code for JP Morgan - there's a slight risk that this could bite you in the @ss at some point (there are some malicious people around) you might want to take that into consideration next time!

Getting empty log files with log4j and WebLogic 10.0

Hi!
I get empty log files with log4j 1.2.13 and WebLogic 10.0. If I don't run the application in the application server, then the logging works fine.
The properties file is located in a jar in the LIB folder of the deployed project. If I change the name of the log file name in the properties file, it just creates a new empty file.
What could be wrong?
Thanks!

I assume that when you change the name of the expected log file in the properties file, the new empty file is that name, correct?
That means you're at least getting that properties file loaded by log4j, which is a good sign.
As the file ends up empty, it appears that no logger statements are being executed at a debug level high enough for the current debug level. Can you throw in a logger.error() call at a point you're certain is executed?

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

Need help with log4j logging tool (org.apache.log4j.*) to log into database

Hi,
I need help with log4j logging tool (org.apache.log4j.*) to log into database using JDBCAppender. Have look at my logger code and corresponding log4j.properties file stated below. I'm running this program using Eclipse IDE and it's giving me the following error (highlighted in red) at the end:
log4j: Parsing for [root] with value=[debug, stdout, Roll, CRSDBAPPENDER].
log4j: Level token is [debug].
log4j: Category root set to DEBUG
log4j: Parsing appender named "stdout".
log4j: Parsing layout options for "stdout".
log4j: Setting property [conversionPattern] to [%x %d{HH:mm:ss,SSS} %5p [%t] (%c:%-4L %M) - %m%n].
log4j: End of parsing for "stdout".
log4j: Parsed "stdout" options.
log4j: Parsing appender named "Roll".
log4j: Parsing layout options for "Roll".
log4j: Setting property [conversionPattern] to [%x %d{yyyy.MM.dd HH:mm:ss,SSS} %5p [%t] (%c:%-4L %M) - %m%n].
log4j: End of parsing for "Roll".
log4j: Setting property [file] to [HelloWorld.log].
log4j: Setting property [maxBackupIndex] to [10].
log4j: Setting property [maxFileSize] to [20KB].
log4j: setFile called: HelloWorld.log, true
log4j: setFile ended
log4j: Parsed "Roll" options.
log4j: Parsing appender named "CRSDBAPPENDER".
{color:#ff0000}
Can't find class HelloWorld{color}
import org.apache.log4j.*;
public class HelloWorld {
static Logger log = Logger.getLogger(HelloWorld.class.getName());
public static void main(String[] args) {
try{
// Now, try a few logging methods
MDC.put("myComputerName", "Ravinder");
MDC.put("crsServerName", "ARNDEV01");
log.debug("Start of main()");
log.info("Just testing a log message with priority set to INFO");
log.warn("Just testing a log message with priority set to WARN");
log.error("Just testing a log message with priority set to ERROR");
log.fatal("Just testing a log message with priority set to FATAL");
catch(Exception e){
e.printStackTrace();
------------------------- log4j.properties file ------------------------------
#### Use three appenders - log to console, file and database
log4j.rootCategory=debug, stdout, Roll, CRSDBAPPENDER
log4j.debug=true
# Print only messages of priority WARN or higher for your category
# log4j.category.your.category.name=WARN
# Specifically inherit the priority level
# log4j.category.your.category.name=INHERITED
#### stdout - First appender writes to console
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%x %d{HH:mm:ss,SSS} %5p [%t] (%c:%-4L %M) - %m%n
#### Roll - Second appender writes to a file
log4j.appender.Roll=org.apache.log4j.RollingFileAppender
##log4j.appender.Roll.File=${InstanceName}.log
log4j.appender.Roll.File=HelloWorld.log
log4j.appender.Roll.MaxFileSize=20KB
log4j.appender.Roll.MaxBackupIndex=10
log4j.appender.Roll.layout=org.apache.log4j.PatternLayout
log4j.appender.Roll.layout.ConversionPattern=%x %d{yyyy.MM.dd HH:mm:ss,SSS} %5p [%t] (%c:%-4L %M) - %m%n
#### CRSDBAPPENDER - third appender writes to the database
log4j.appender.CRSDBAPPENDER=org.apache.log4j.jdbc.JDBCAppender
log4j.appender.CRSDBAPPENDER.Driver=net.sourceforge.jtds.jdbc.Driver
log4j.appender.CRSDBAPPENDER.URL=jdbc:jtds:sqlserver:/arncorp15:1433;DatabaseName=LOG
log4j.appender.CRSDBAPPENDER.USER=sa
log4j.appender.CRSDBAPPENDER.PASSWORD=p8ss3doff
log4j.appender.CRSDBAPPENDER.layout=org.apache.log4j.PatternLayout
log4j.appender.CRSDBAPPENDER.sql=INSERT INTO LOG (computername, crsservername, logtime, loglevel, threadname, filename, linenumber, logtext) VALUES ('%X{myComputerName}', '%X{crsServerName}', '%d{dd MMM yyyy HH:mm:ss,SSS}', '%p', '%t', '%F', '%L', '%m')
#log4j.appender.CRSDBAPPENDER.sql=INSERT INTO LOG(COMPUTERNAME,CRSSERVERNAME,LOGTIME,LOGLEVEL,THREADNAME,FILENAME,LINENUMBER,LOGTEXT) select host_name(),'${CRSServerName}${InstanceName}','%d','%5p','%t','%F','%L','%m%n'
#log4j.appender.CRSDBAPPENDER.sql=INSERT INTO LOG (computername, crsservername, logtime, loglevel, threadname, filename, linenumber, logtext) VALUES ("%X{myComputerName}", "%X{crsServerName}", "%d{dd MMM yyyy HH:mm:ss,SSS}", "%p", "%t", "%F", "%L", "%m")
------------------------------- end of log4j.properties file ------------------------------
Here is the directory structure of my program. My log4j.properties file and HelloWorld.class file are residing in folder HelloWorld\bin.
HelloWorld\bin
HelloWorld\lib
HelloWorld\src
Please note - The same program works fine for console and file appender when I comment the database appender part in my properties file.
Thanks
Ravinder

try this :
log4j.appender.PROJECT.Append=false

Load data error: Database selection with invalid cursor (sm21)

hi experts,
when I execute processchar, it occur some system error:
"Database selection with invalid cursor ",
"Documentation for system log message BY 7 :
The database interface was called by a cursor (in a FETCH or CLOSE
cursor operation) that is not flagged as opened. This can occur if a
COMMIT or ROLLBACK was executed within a SELECT loop (which closes all
opened cursors), followed by another attempt to access the cursor (for
example, the next time the loop is executed). "
the error msg occur when apply bw support package19.
data from DSO to CUBE, Transferred Recodes is not zero, but Added Recodes is zero.
Request status always yellow, process is running.
current sys info: BI7 and BW19, BASIS17,PI_BASIS17, the database is oracle10g R2.
thanks for your help.

I have solved this issue, The Oracle checkpoint not complete.
thanks,
xwu.

Processchar occur error: Database selection with invalid cursor (sm21)

hi,
when I execute processchar, it occur some system error:
"Database selection with invalid cursor ",
"Documentation for system log message BY 7 :
The database interface was called by a cursor (in a FETCH or CLOSE
cursor operation) that is not flagged as opened. This can occur if a
COMMIT or ROLLBACK was executed within a SELECT loop (which closes all
opened cursors), followed by another attempt to access the cursor (for
example, the next time the loop is executed). "
the error msg occur when apply bw support package19.
data from DSO to CUBE, Transferred Recodes is not zero, but Added Recodes is zero.
Request status always yellow, process is running.
current sys info: BI7 and BW19, BASIS17,PI_BASIS17, the database is oracle10g R2.
thanks for your help.

I have solved this issue , The Oracle checkpoint is not complete.
thanks,
xwu.

When I try to sign in to my account on iTunes, I get the above error message, along with "Please review your account information". When I then click on "Review"

When I try to sign in to my account on iTunes, I get the above error message, along with"Please review your account information".
When I then click on "Review", it comesup with the page "Create an Apple Account for the iTunes Store"and presents me with the Terms Of Service.
When I click "Agree", It is disabled.
Can anyone tell me why this has happened and how to resolve it?
Please, please, please help.

Count me in as having the same problem. I have been leaving messages in the iTunes for Mac forum where others in there also are having problems. I have been unable to access my account since 11/7/2007. E-mails with Apple have not worked and now I haven't heard back from them since Saturday. I have tried both on a Mac and Windows machine and keep receiving the same error message that:
This Apple ID has not yet been used with iTunes.
I last purchased music with this account on 10/30/2007. I even tried resetting my password, changing my account info, trying on a computer with iTunes 7.4, etc. I have money in that account and 150 songs and 5-6 tv shows that I cannot access. I also just purchased a new computer and cannot sync my iPod with this computer since these songs will not transfer.
Apple really needs a phone number for technical support. Having to deal with e-mails back and forth (and waiting a day for each e-mail) is not a good business practice. Hopefully they will have a phone number in the future.
Either way, count me in on getting annoyed that a week later, this issue has not been fixed.

Error in access with Essbase Studio Console

We get error to connect with Essbase Studio Console.
"children for Root. Reason: Unknown package name 'drillthrough'.Line = 1."
It is a new installation.
EPM 11.1.2.2

Hi,
During the installation of Essbase Studio only, ess_es_server.jar and ess_japi.jar are missing. If you install both Essbase and Studio, they are not missing.
This is due to unpublished bug 14232814 - DURING THE INSTALLATION ONLY STUDIO SOME .JAR FILES NOT INSTALLED
Try the following:
Stop Essbase Studio
copy files into EPMSystem11R1\common\EssbaseJavaAPI\11.1.2.0\lib
ess_es_server.jar
ess_japi.jar
If folder does not exist create it.
1. Stop essbase Studio.
2. Drop tables from relational database
3. Recreate tables.
4. Start Essbase Studio.
Scripts for dropping & recreating catalog located under
oracle\middleware\EPMSystem11R1\products\Essbase\EssbaseStudio\Server\database\common\db_name
Hope it helps....
KosuruS
PS: If the above information is helpful, mark it :)

Error in WebDynpro with WebServices

Hi all,
Im getting some errors using applications deployed in WEB AS SP9 that runs as a WebDynpro IView in EP.
Running the application as standalone (out of EP) this works fine.
NetWeaver Developer Studio 2.0.9
WebDynpro application using WebServices that access Oracle 8i database in the follow sequence:
WebServices -> Session Bean stateless -> Entity Bean CMP (manage connections; generate sql code, etc.)
In WebDynpro application we import WebService Model by the follow sequence:
New Model - Import Web Service Model - Local Server for WSDL Source - <WebService deployed>
In each WebServices we have created these methods:
findByID(ID);
getAll();
insert(parameters);
remove(ID);
update(parameters);
We guess that the error is generated in Entity Bean because all WebServices generate these errors.
Error 1 - Application with WebServices Model
Error stacktrace:
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Repository Object br.com.xxx.fluxo.Fluxo/ComponentInterface:FluxoInterface/InterfaceViews:CadastroSituacaoFluxoInterfaceView/InboundPlugs:Default associated via relation RepositoryObjectRelation(br.com.xxx.fluxo.application.CadastroSituacaoFluxoApp, StartupPlug) does not exist.
 at com.sap.tc.webdynpro.repository.RelationToOne.resolveTargets(RelationToOne.java:124)
 at com.sap.tc.webdynpro.repository.RelationToOne.mergeTargets(RelationToOne.java:108)
 at com.sap.tc.webdynpro.repository.RelationToOne.mergeTargets(RelationToOne.java:72)
 at com.sap.tc.webdynpro.repository.RelationToOne.getTarget(RelationToOne.java:174)
 at com.sap.tc.webdynpro.repository.RepositoryObject.getRelatedModelObject(RepositoryObject.java:349)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getStartupPlugInternal(IWDApplicationInfo.java:319)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:355)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
-- end --
Error 2 - Application with WebServices Model
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Hide details
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-19:21:48:59[UTC], changelist=290362, host=PWDFM026)
Web Dynpro code generators of DC local/Apontamentos:
SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:31:53[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:36:19[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:00[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:25:03[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:01[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:29:01[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:11[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:33[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: (unknown)
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
6.40 patchlevel 87037.313
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_06-b03, vendor: Sun Microsystems Inc.
Operating system:
Windows 2000, version: 5.0, architecture: x86
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller NotProductiveEventController
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.createCustomController(DelegatingComponent.java:55)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:428)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Error 3 - Application with RFC Model
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Hide details
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-19:21:48:59[UTC], changelist=290362, host=PWDFM026)
Web Dynpro code generators of DC local/Apontamentos:
SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:31:53[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:36:19[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:00[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:54:34[UTC], changelist=290362, host=PWDFM026)
SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:25:03[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:01[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:29:01[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:26:11[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-10-18:21:41:33[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: (unknown)
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
6.40 patchlevel 87037.313
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_06-b03, vendor: Sun Microsystems Inc.
Operating system:
Windows 2000, version: 5.0, architecture: x86
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Did not find repository information for controller ZMANPP012Controller
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.createCustomController(DelegatingComponent.java:55)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:428)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

Hi,
I feel this error is nothing to do with webservice model.
Please check your application properties like startupPlug,Interface View etc. Set the properties correctly and deploy once again.
Regards, VIP

Error in Communicating with DCA Server

Hi,
I have Cisco LMS 2.6 and next modules:
1. CiscoWorks Common Services 3.0.6
2. Campus Manager 4.0.13
3. CiscoView 6.1.5
4. Device Fault Manager 2.0.13
5. Internetwork Performance Monitor 2.6.0
6. Integration Utility 1.6.0
7. Resource Manager Essentials 4.0.6
Windows Server 2003 SE SP2
I have some problems:
1)
When I try enter to Device and Credentials I get message "Error in communicating with DCA Server.
DCA Server may be down. Please start the DCA Server and then refresh the page."
I try to restart CiscoWorks Daemon Manager over Services.
I cannot get information a lot of time from command "pdshow". Only black screen on the window CMD.
Or I get error
C:\Documents and Settings\zykov>pdshow
ERROR: GetReply failed:
ERROR: Daemon Manager startup in progress. Please wait.
dcr.log
[ Чт фев 18 16:51:28 YEKT 2010 ] [Ajp13Processor[9009][4]] FATAL com.cisco.nm.dcr.DCRProxy - Error in Communication to DCRServer , Reason :DCRException ID - -202 : CSTM Error Code [-1] CSTM Comm Type [0] - Unknown exception before invocation
[ Чт фев 18 20:32:35 YEKT 2010 ] [Ajp13Processor[9009][3]] FATAL com.cisco.nm.dcr.DCRDatabaseAccess - Severe error in DCRDatabaseAccess initialization - JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s). 0 JZ00L
[ Чт фев 18 20:32:35 YEKT 2010 ] [Ajp13Processor[9009][3]] FATAL com.cisco.nm.dcr.DCRSystem - Unable to Instantiate DCRDataManagement ObjectJZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s).
java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s).
DCRServer.log
[ Thu Feb 18 21:10:41 YEKT 2010 ] Starting DCR Server...
[ Thu Feb 18 21:10:43 YEKT 2010 ] No restore has happened
dcrclient.log
[ Чт фев 18 20:50:49 YEKT 2010 ] [Ajp13Processor[9009][5]] FATAL com.cisco.nm.dcr.DCRProxy - Error in Communication to DCRServer , Reason :DCRException ID - -202 : CSTM Error Code [-1] CSTM Comm Type [0] - Unknown exception before invocation
2) When I run Alerts and Activites I get error "An exception occurred. Please check the AAD.log file for further details."
AAD.log
18-фев-2010|21:30:10.291|ERROR|AAD|Ajp13Processor[9009][3]|AFDLaunchAction|perform|.|Error in calling getPartitionNamePMServercom.cisco.nm.xms.ctm.common.CTMException: Read timed out/Error in received response Connection reset
3) On the window Home of Common Services I have message "JRM server is down or inaccessible for this user"
I try reinstall last modules Campus Manager 4.0.13,
Device Fault Manager 2.0.13,
CiscoWorks Common Services 3.0.6.
But it cannot help me.
I think that this problems related. Yesterday all works correctly.
Thank you for your help.

You are right the problem was related with antivirus.
After removal antivirus DCA Server started successfully.
Remains the question as to be without an antivirus program?
Also remains a problem in the window Alerts and Activites.
When I click on the Device Name field (for some devices) does not open Detailed Device View.
The window closes immediately after opening.

Error in communicating with DCR

Preliminary question:
     For LMS 3.2 on Windows, which is better 2003 or 2008?
Primary issue:
     Background: new install of LMS 3.2 on Windows 2008 sp2 Virtual Machine.
          Upgraded Campus to 5.2.1
          Upgraded RME to 4.3.1
          when updating device packages, services started extremely slow with anidbeng taking 2hrs. portal showed service unavailable.
          had to restart crmdmgtd to be able to login.
          most links in CS return the following:   Error in communicating with DCR server. DCR server may be down. Please start the DCR server           and then refresh the page.   The DCR server shows running normal.
          tried restarting crmdmgtd
          attached DCR.log
         tried CSCtd07131 .. no success

Windows 2008 offers more scalability so I would go with that although LMS has been tested on both (you will have a longer life of support as well).
When applying the CSCtd07131 patch, you need to be sure it is the right patch for the right CS version as there are multiple versions out there. However, this is fixed in LMS 3.2.1 so you should just upgrade there.
An often overlooked matter when installing LMS are the steps mentioned here:
https://supportforums.cisco.com/docs/DOC-9132
I see constant TAC cases due to installation problems because the above steps are not met or are half-met. Services starting slowly are usually an after-effect of something blocking ports (anti-virus or such) or possible database corruption. Setting DEP and anti-virus as specified above might help here, but if you did not follow these steps to the letter during this new install, I would suggest to cleanup this server and re-install properly; then move all the way to LMS 3.2.1.

Error in communicating with DCR server (Operations Manager 8.5)

Hi,
I just installed Operations Manager 8.5 on a new server. And, although I'm able to login to the OM, I'm unable to add any devices to the DCR. When attempting to add the device the following error is returned:
"Error in communicating with DCR Server
DCR Server may be down. Please start DCR server and then refresh the page. "
The same error is returned when an attempt is made toaccess the screen to change the mode (standalone/master/slave.) However, according to pdshow output DCRServer is up and running:
Process= DCRServer
State = Running normally
Pid    = 9220
RC     = 0
Signo = 0
Start = 7/29/2011 2:46:33 PM
Stop   = Not applicable
Core   = Not applicable
Info   = DCRServer is up and running
I've browsed the site and tried all suggestions for LMS since I didn't see any for OM. No success.
Any/all suggestions are much appreciated.
Kind regards,
Bart

It appears the answer is rather simple. According to a trusted source who works for a Cisco training partner, one must wait before even attempting a login into OM.
Apparently, it takes about 25 to 30 minutes for all the services to start. Any attempt to login to the OM may corrupt the database. This is based on CiscoWorks. When command "net stop crmdmgtd" is issued it takes about 5 minutes to stop the service and a confirmaiton that the service was stopped is displayed. However, when starting the service with "net start crmdmgtd" there is no confirmation that it started successfully. One may look into ":\ program Files\CSCOpx\objects\dmgt\ready" directory for a _lock file." As long as the lock file is present one shouldn't use the browser to login. However, I was advised the best approach is to restart the service and give it 30 minutes.
It worked for me
Kind regards,
Bart.

Error on loadjava with log4j

Similar Messages

Maybe you are looking for