My team is using BIRT to handle our clients business logic. Every so often we get an exception in our our logs:
18-Dec-2012 11:25:39.163 INFO
org.eclipse.birt.report.data.oda.jdbc.JndiDataSource.getDriverJndiPropertyFile
getDriverJndiPropertyFile() java.io.IOException: Unable to locate the installation path of
the ODA extension (org.eclipse.birt.runtime). The ODA consumer application must specify a
ResourceIdentifiers in the appContext to resolve the path.
We're not sure what causes this error and it seems to be working fine. We have a jdbc connection so we're not sure what would cause this. Any tips or info that we could use to help troubleshoot this issue would be greatly appreciated.
Copy
mysql-connector-java-5.0.8-bin.jar
to
WEB-INF\platform\plugins\org.eclipse.birt.report.data.oda.jdbc_INSTALLED_VERSION\drivers
folder.
Related
I have been trying to create a DataSource on my development machine using Weblogic 12.2.1.3.0 developer install using the admin console and I am getting an exception that I have not encountered before. I have verified that all of the connection information is correct and I can connect to the Oracle Database (v12.1.2) using SQL Developer and an IDE connection but the Weblogic server is not cooperating.
This is the exception that I am getting:
I have also tried creating a DataSource when the EAR file is deployed using descriptors and the DS is created and deployed but the connection pool for the DS cannot be created and the only exception that I am seeing is this:
Connection test failed with the following exception: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection for datasource 'StipDS'. The DBMS driver exception was: null
Anyone have any ideas?
Oracle has not been much help at all so far.
check your jdbc connection url, i guess something is missing there. make sure the jdbc driver is present inside lib folder.
I was facing the same issue and able to resolve by replacing the ojdbc6.jar with ojdbc6-2.0.jar from "C:\Oracle\Middleware\wlserver_10.3\server\lib"
Downloaded the jar file from https://jar-download.com/?search_box=ojdbc6++jar
Error log:
Caused By: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: null
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:283)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1310)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1227)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:250)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1329)
i suggest reverting any network changes that might have taken place.
example DNS change in the resolve.conf file
I am trying to use JMeter to work with IBM MQ.
As per the article I created the JNDI Bindings.
Now I am trying to connect JMeter using the JNDI Bindings. I give the QCF (Queue Connection Factory), but it is throwing an error
"Response message: java.lang.IllegalStateException: QueueConnectionFactory expected, but got javax.naming.Reference"
I searched around a lot, but didnt find anything. I looked at source code for Sampler and it looks like it is not able to find the Connection Factory from the JNDI.
Any idea what could i be missing? I Didnt know if the Configuration details would help, if it would i can provide that.
Thanks in Advance!
I was able to resolve this by copying all the MQ Jars (that comes with a complete Websphere MQ installation) and placing them into JMeter/Lib.
Now it works fine.
Thanks for anyone who viewed this. Hope my answer may provide some light to others who may encounter the same problem.
When i am running my application it give me this exception:-
Exception sending context initialized event to listener instance of class
org.springframework.web.util.Log4jConfigListener
java.lang.ExceptionInInitializerError
But this problem is not permanent. If i remove the log4j entries from web.xml and restart p.c and then again add log4j entries and start the server, then the application works fine.
I noticed that when the application is deployed and when i undeploy and again deploy the same application, this problem emerge.
Please help me ........ i am facing this problem from 3 months...
I just investigated it a little and have found the similar issue:
It causes when multiple jar file for log4j is available to application.
From web/application server and from build path(Included from other
path rather than web/application server)
You can see the entire thread here:
http://www.coderanch.com/t/551933/Spring/Exception-sending-context-initialized-event
looks like this is your problem.
I'm running into an issue with the Spring IDE release 2.6.0 under Eclipse 3.6 SR 1
Error occured processing XML 'Could not instantiate bean class
[org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$ToolingFriendlyBeanDefinitionDocumentReader]:
Constructor threw exception; nested exception is
org.apache.commons.logging.LogConfigurationException: User-specified log class
'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable.'.
See Error Log for more details
I dumped my entire eclipse environment and re-installed to see if it would fix it and it didn't. Not sure if this is a classpath problem or something specifically related to the SpringIDE configuration.
Any help would be appreciated.
you're hitting a bug in Spring IDE. See the following JIRA for more details:
https://issuetracker.springsource.com/browse/STS-1691
We are going to publish a patch for this issue soon. Check the JIRA for when it is available. Alternatively install an upcoming nightly build.
Regards, Christian
I'm trying to deploy a couple of jar files in a code module for an event action in FileNet P8 4.0 (the FileNet server runs on WebSphere 6.1). One of these jars is my custom code, and the other jar is the thin driver for Oracle called ojdbc14.jar (I also tried with ojdbc15.jar), the custom code uses the oracle jar in order to connect to a data source and get a connection using the JNDI name.
When the event action is executed (after a subscription is invoked) the code in my custom module is called OK, the problem occurs when my code needs to load classes from the Oracle jar, I get this cause:
ERROR - Mon Sep 21 16:42:17 UTC 2009 - com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.reflect.InvocationTargetException]
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:1000)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:705)
at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:2093)
...
Caused by: java.lang.NoClassDefFoundError: oracle.jdbc.driver.OracleLog
at com.ibm.ws.rsadapter.dbutils.impl.OracleUtilityImpl.setLogVolume(OracleUtilityImpl.java:85)
at com.ibm.ws.rsadapter.spi.InternalOracleDataStoreHelper.setProperties(InternalOracleDataStoreHelper.java:142)
at com.ibm.ws.rsadapter.spi.WSRdbDataSource.(WSRdbDataSource.java:846)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.setDataSourceProperties(WSManagedConnectionFactoryImpl.java:1947)
... 43 more
...
Caused by: java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleLog
at java.net.URLClassLoader.findClass(URLClassLoader.java:496)
at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:132)
at java.lang.ClassLoader.loadClass(ClassLoader.java:631)
at com.ibm.ws.bootstrap.ExtClassLoader.loadClass(ExtClassLoader.java:87)
at java.lang.ClassLoader.loadClass(ClassLoader.java:597)
... 48 more
Since I'm deploying the oracle jar with the code module, shouldn't FileNet should be able to find the class? Do you think I need to configure something else?
Thanks in advance.
Is it possible for your application to use WebSphere's own JDBC connection pools? When you set up a pool for a particulr database you get all the vendor-specific drivers installed there.
Generally, all manner of classpath and classloader confisions ensue when you try to place infrastructure code in your own applications. I don't know for certain that this is the case for your situation, but I do find taht staying on the known path in WebSphere tends to give the smoothest results.
I found the problem... somehow the ojdbc14.jar file got corrupted, so even when the classpath was correct and no matter what I tried to fix the problem, the problem was always there.
Thanks for the comments!