If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

HELP!!! can't run C8 on WAS

Started by vip2cool, 28 Nov 2008 01:01:14 PM

Previous topic - Next topic

vip2cool

here's the server log, any ideas? greatly appreciated!

Runtime Exception stack trace:
java.lang.ExceptionInInitializerError
   at java.lang.J9VMInternals.initialize(J9VMInternals.java:216)
   at org.apache.derby.jdbc.ClientDriver.<clinit>(Unknown Source)
   at java.lang.J9VMInternals.initializeImpl(Native Method)
   at java.lang.J9VMInternals.initialize(J9VMInternals.java:194)
   at java.lang.Class.forNameImpl(Native Method)
   at java.lang.Class.forName(Class.java:130)
   at com.cognos.cm.dbstore.CMDbStoreFactory.getInitialConnection(CMDbStoreFactory.java:1906)
   at com.cognos.cm.dbstore.CMDbStoreFactory.initContentIndependentBeforeLock(CMDbStoreFactory.java:2042)
   at com.cognos.cm.dbstore.CMDbStore.initializeContentIndependentBeforeLock(CMDbStore.java:4873)
   at com.cognos.cm.server.CMServlet.initializeContentStoreContentIndependentBeforeLock(CMServlet.java:2351)
   at com.cognos.cm.server.CMServlet.init(CMServlet.java:2072)
   at com.cognos.cm.server.ContentManager.start(ContentManager.java:296)
   at com.cognos.cm.server.ContentManagerLifecycleHandler.start(ContentManagerLifecycleHandler.java:68)
   at com.cognos.pogo.services.DefaultHandlerService.start(DefaultHandlerService.java:101)
   at com.cognos.pogo.services.DispatcherServices.startInititalServices(DispatcherServices.java:416)
   at com.cognos.pogo.transport.PogoServlet$PogoStartup.run(PogoServlet.java:654)
   at java.lang.Thread.run(Thread.java:810)
Caused by: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info: already loaded
   at java.net.URLClassLoader.defineClass(URLClassLoader.java:535)
   at java.net.URLClassLoader.access$400(URLClassLoader.java:123)
   at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1034)
   at java.security.AccessController.doPrivileged(AccessController.java:279)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:491)
   at com.cognos.pogo.isolation.ParanoidClassLoader.loadClass(ParanoidClassLoader.java:119)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:597)
   at org.apache.derby.client.am.Configuration$1.run(Unknown Source)
   at java.security.AccessController.doPrivileged(AccessController.java:246)
   at org.apache.derby.client.am.Configuration.buildProductVersionHolder(Unknown Source)
   at org.apache.derby.client.am.Configuration.loadProductVersionHolder(Unknown Source)
   at org.apache.derby.client.am.Configuration.<clinit>(Unknown Source)
   at java.lang.J9VMInternals.initializeImpl(Native Method)
   at java.lang.J9VMInternals.initialize(J9VMInternals.java:194)
   ... 16 more

kolonell

Your C8 instance is trying to load the derby JDBC driver but WAS has one loaded already. Check if you can remove the one from ear/war file and redo the deployment or go through  the JVM options specified by WAS and remove the
Derby JDBC reference.

vip2cool

Thanks

but i'm not exactly sure what you mean.

1. Check if you can remove the one from ear/war file and redo the deployment. (what do you mean by the one?)
2. go through the JVM options specified by WAS and remove the Derby JDBC reference.

here's the server.xml, is this where to set jvm options?:
<jvmEntries xmi:id="JavaVirtualMachine_1228131560937" verboseModeClass="true" verboseModeGarbageCollection="false" verboseModeJNI="false" initialHeapSize="512" maximumHeapSize="1024" runHProf="false" hprofArguments="" debugMode="false" debugArgs="-Djava.compiler=NONE -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=15050" genericJvmArguments="">
<systemProperties xmi:id="Property_1228132750718" name="com.ibm.tivoli.reporting.installdir" value="C:/IBM/tivoli/tip/products/tcr" description="Tivoli Common Reporting Home" required="false"/>
</jvmEntries>

not sure where to look for Derby JDBC reference.

do you mind going into step by step detail about how to go about fixing the issue? greatly appreciated!