Jar File Not Found On Linux Tomcat

Hi, 
 
First, my setup: 
 
BiRT Runtime: 3.7.2. 
OS: Ubuntu 10.04 
Tomcat 6 
Sun Java 1.6.0 
 
I have a jar file I want to deploy onto a Tomcat server so it is usable by the rntime, so after reading <a class='bbc_url' href='http://wiki.eclipse.org/BIRT/FAQ/Scripting#Q:_Where_do_I_have_to_put_my_classes_in_order_to_access_them_by_JavaScript.3F'>this</a> I placed the jar file in /var/lib/tomcat6/webapps/birt/WEB-INF/lib. 
 
But the jar file is not accessible by the report that is trying to call it. In the BiRT logs I see: 
<pre class='_prettyXprint _lang-auto _linenums:0'>Error evaluating Javascript expression. Script engine error: ReferenceError: "DynDSinfo" is not defined. (/report/data-sources/oda-data-source[@id="54"]/method[@name="beforeOpen"]#20)
Script source: /report/data-sources/oda-data-source[@id="54"]/method[@name="beforeOpen"], line: 0, text:
__bm_beforeOpen()
org.eclipse.birt.data.engine.core.DataException: Fail to execute script in function __bm_beforeOpen(). Source:</pre>
 
And now for the kicker... this works fine on Tomcat6 on Windows 7. So is there some additional configuration or some environmental variable that needs to be set, or something different on the Linux platform? 
 
I have struggled with this for hours as it should just work.. but no. 
 
All help or ideas gratefully received, 
 
Stephen

Find more posts tagged with

Comments

CBR

Are you using the BIRt Webviewer application or some home brewn app to generate your reports?
If you aure using the Webviewer you should not put your jar files into the lib folder but in the scriptlib subfolder. The Webviewer will take care that all jar files located in the scriptlib folder are accessible for all rhino expressions within your reports.
the reason for the jar files beeing accessible if you put them in the lib folder is that everybody in that folder is accessible for all java classes anyways. But depending on your specific configuration they can be hidden for some subclasses anyways.
So to keep it short: If you need some classes for scripting compile them to a jar and put it into the scriptlib folder! The Webviewer will take care that these jars are accessible in the reports.
This is not true for jdbc jar files these jar files need to be in the lib folder! The reason for that is that the jdbc jars need to be visible to the oda driver which is not related to rhino

zax

Thank you for your reply. I am indeed trying to call a JAR from scripting and I have tried placing the JAR file in /var/lib/tomcat6/webapps/birt/scriptlib, but no dice. I get the same error. I have started trying to get this to work with a very simple JAR that contains a class that will just return a string. But I still get: 
 
<pre class='_prettyXprint _lang-auto _linenums:0'>ReferenceError: "BirtClass" is not defined. (/report/method[@name="initialize"]#3)</pre>
 
when I try to initialize the class. The /var/lib/tomcat6/webapps/birt/scriptlib looks like this: 
<pre class='_prettyXprint _lang-auto _linenums:0'>-rwxr-xr-x 1 tomcat6 tomcat6 917 2012-06-28 09:46 BIRTdummy.jar
</pre>
 
This is all very strange as there must be lots of people who have successfully used JARs with BiRT on Ubuntu. As far as I can remember this is a standard installation of Tomcat6 (from the repository), BiRT was deployed using the WAR file and I have not changed any settings or config. 
 
Can you think of any other things I could try? 
 
Thanks again, 
Stephen

CBR

Can you design a simple report using a dummy java class and upload both over here?
I need to try it myself.

zax

OK thanks, in the zip file is the simple JAR and the report trying to use a class in the JAR. I forgot to mention I have been seeing the error in the ReportEngine log in /var/lib/tomcat6/webapps/birt/logs.

zax

This epic continues... I have now got a Windows server giving the same error as the Ubuntu server and desktop. So now I will investigate Java versions and configuration.

Either people who do this have struck it lucky, or not many people add JARs to BiRT reports, or I am doing some silly mistake. This assumption is based on the low number of hits on Google when I have searched for solutions or common experiences.

Stephen

zax

OK, solved. I discovered that the Windows PC that worked was running Java 1.7 and Tomcat 7. Apart from the operating system, this was the only difference. 
 
So after trying many combinations: 
 
Java 1.6 and Tomcat 7 
Java 1.7 and Tomcat 6 
 
It was only Java 1.7 and Tomcat 7 that worked... so why this is I can only guess. 
For people's future reference, as things stand at the moment you cannot get Oracle Java from the Ubuntu repositories, so I used a ppa to get Java: 
 
<pre class='_prettyXprint _lang-auto _linenums:0'>
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
</pre>
 
And downloaded Tomcat directly from <a class='bbc_url' href='http://apache.hoxt.com/tomcat/tomcat-7/'>here</a> and installed it by unpacking the tar file and starting the service using startup.sh. 
 
I then deployed BiRT using the WAR file (using the Tomcat Manager Web Application), placed the JAR in /var/lib/tomcat7/webapps/birt/scriptlib and put the report file in the usual place, and it worked! 
 
It feels a bit like using a sledgehammer to crack a nut, but I don't have the knowledge to go digging around the JRE and Tomcat. 
 
Stephen

CBR

Makes sense. I m assuming that you compiled your custom java classes using Java 7. This will cause the java class not to run on any version lower then 7.
Go back to your java sources and have a look for compiler level that is configured for these java sources. Try to built your sources using Java6 or Java5 (depending on which version you want to use on your Prod server).

EDIT: From all i can see in your upload the compliance level is Java7. This is most likely the reason for the jar file not running with any version lower then 7.

zax

Yes that does make sense. The JAR was handed to me to integrate into BiRT. I really don't want upgrade the development, test and production environments. If it is possible to re-compile the JAR using Java 6 and avoid that, it would be great.

CBR

Yes, just tell the dev team to compile the java classes using Java6 or Java5 (you should define a target jre that everybody working on that project has to use to avoid such problems in the future)
Let me know if it solves the issue.