Jump to content

jdlh

Members
  • Posts

    10
  • Joined

  • Last visited

jdlh's Achievements

Apprentice

Apprentice (3/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Collaborator Rare

Recent Badges

0

Reputation

  1. Oesina, thank you for your suggestions. I have successfully connected from JasperReports Server and from iReport. The last step for iReport was to find out from my admin that we are using a non-standard port number on our SQL Server database server. I added the instance name and corrected the port, and iReport was able to connect. To make JasperReports Server work, I first fixed the port number in the JDBC URL. Then, I found the Tomcat error logs in the directory: <js-install>\apache-tomcat\logs\ . The file that helped me was the most recent one, named in my case stderr_20120813.log. The error message I found there was: Aug 13, 2012 12:40:59 PM com.microsoft.sqlserver.jdbc.SQLServerConnection <init>SEVERE: Java Runtime Environment (JRE) version 1.6 is not supported by this driver. Use the sqljdbc4.jar class library, which provides support for JDBC 4.0. By this point I had four sqljdbc*.jar files each in my apache-tomcat\lib and apache-tomcat\webapps\jasperserver-pro\WEB-INF\lib directories: sqljdbc.jar, sqljdbc4.jar, sqljdbc-1.5.jar, sqljdbc-1.6.jar. I got rid of all except sqldbc.jar, from each lib directory. On stopping and restarting the JasperReports Server service, I found that my SQL Server data source, now passed when I used the "Test Connection" button in the connection definition dialog box. I wonder why I didn't see this error message before. I speculate that this message comes from the Microsoft-developed sqljdbc.jar, and that there was some contention between sqljdbc4.jar (which seems to work) and the other sqljdbc*.jar files. So, I speculate that it's better to put in just one driver file, and to be sure it's the right one.
  2. Thank you, oesina, for this insight. I agree, the Installation Guide doesn't say much about iReport. It would be nice if it did. When I use Tools... Options... iReport... Classpath... Add jar to point to sqljdbc-1.6.jar, then sure enough, the connection name MS SQL Server 2005 appears in black, and I no longer get the ClassNotFoundException. Progress! Now I'm getting connection refused and timeout errors from iReport, and I'll talk to my administrator to be sure I have the system coordinates correct. All this helps iReport only; JasperServer is still not connecting to my SQL Server database. Thanks again for your help.
  3. > I'm running Microsoft Windows XP SP3, if that makes a difference. FYI, I've also reproduced the problem with JasperServer 4.7 eval version, Windows x64, running on a VM with Windows Server 2008 R2 as guest OS. The only Java VM I see on this system is the one installed with JasperServer: C:\Users\Administrator>"c:\Program Files\jasperreports-server-4.7\java\bin\java.exe" -versionjava version "1.6.0_18"Java(TM) SE Runtime Environment (build 1.6.0_18-b07)Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)
  4. Hi, I've been trying to use the JasperServer 4.7 eval edition, and connect to our existing SQL Server database. It hasn't worked for me, despite trying several workarounds mentioned in various forum posts. Perhaps some of you can point out what I'm missing. I created a data source in JasperServer as the user jasperadmin. The parameters are: JDBC Driver: MS SQLServer (2005) (com.microsoft.sqlserver.jdbc.SQLServerDriver) JDBC URL: jdbc:sqlserver://myserver\myinstance:1433;databaseName=mydatabase When I push the Test Connection button in the JasperServer "Edit Data Source" page, I get a brief glimpse of a yellow bar saying, "Connection Failed", with no visible way to diagnose the problem. When I run iReport 4.7, I see this data source in a pulldown menu of datasources at centre of the top toolbar. When I push the "Report Datasources" button, and then select my data source from the dialog "Connections / Datasources", and push the "Modify" button, I get a "Database JDBC Connection" dialog. When I press the "Test" button in the JDBC connection dialog, I get the following error message: ExceptionMessage: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriverLevel: SEVEREStack Trace:com.microsoft.sqlserver.jdbc.SQLServerDriver com.jaspersoft.ireport.designer.connection.JDBCConnection.loadDriver(JDBCConnection.java:63) com.jaspersoft.ireport.designer.connection.JDBCConnection.getConnection(JDBCConnection.java:126) com.jaspersoft.ireport.designer.connection.JDBCConnection.test(JDBCConnection.java:447)...[snip]... This seems to be saying that iReport can't find the JDBC driver for SQL Server. Or more precisely, the class com.microsoft.sqlserver.jdbc.SQLServerDriver which is provided by the driver. Is SQL Server installed with the JasperReports 4.7 eval edition for Windows, by default? The installation guide doesn't explicitly say. Given that there's no instructions on "how to add SQL Server support to the default installation", the implicit message is that such support is part of the default install. The sentence, "The installer provides the JDBC drivers for all databases listed in the following table except MySQL." (JasperReports Server Install Guide 4.7 p.59) also implies this. But maybe not. So, following hints in a couple of forum posts, I copied <js-install>/buildomatic/conf_source/db/sqlserver/jdbc/sqljdbc-1.6.jar to <js-install>/apache-tomcat/webapps/jasperserver-pro/WEB-INF/lib/ and to <js-install>/apache-tomcat/lib/ . I stopped and restarted the JasperServer service and the iReports application. No change to the symptoms. I downloaded the latest Microsoft JDBC driver from http://msdn.microsoft.com/en-us/data/aa937724.aspx , and copied their sqljdbc.jar and sqljdbc4.jar to the same two lib directories. Stopped and restarted. No change. I see that, after installing Java 1.7 from Oracle, and JasperServer 4.7, I still had no classpath set. I added an environment variable CLASSPATH to Windows, with a value of C:\Program Files\jasperreports-server-4.7\buildomatic\conf_source\db\sqlserver\j dbc . No change. According to "jar tf", the archive sqljdbc-1.6.jar has a file named com\microsoft\sqlserver\jdbc\SQLServerDriver.class . So, after providing Tomcat and JasperServer all these different files which appear to have class SQLServerDriver, how come iReport is giving a java.lang.ClassNotFoundException of com.microsoft.sqlserver.jdbc.SQLServerDriver? And, to get to my underlying question, how can I use my existing SQL Server database in the JasperServer 4.7 eval edition? I'm running Microsoft Windows XP SP3, if that makes a difference. Thanks in advance for any insight you can offer.
  5. Hi, folks: I have a suspicion that the JasperServer 4.7 eval package requires that the target installation directory be on an NTFS volume. It's not clear to me if this is a JasperServer requirement, or just a Postgresql installer requirement. In any case, if there is such a limitation, it would be good to make this clear in the installer and the Installation Guide. The installer could perhaps check if the install destination is suitable, and put up an error message if it isn't. The Installation Guide could perhaps document the file system type in the system requirements section. I tried installing the JasperServer 4.7 eval package, Windows x86 (32-bit) version. When it asked for an install location, I pointed it to a server-hosted directory on my Y:\ drive. This directory was implemented by the VMWare Fusion product, because my installation target Windows machine is a VMWare Fusion guest OS hosted on a Mac OS X machine. When I ran the installation, it failed with the message, [14:52:30] Running cacls Executing cacls "Y:\@@ Overdudu-Overdue shared\Jaspersoft BI test\jasperpro-4.7/postgresql/data" /e /c /t /p SomeUser:c Script exit code: 1Script output: The Cacls command can be run only on disk drives that use the NTFS file system. Script stderr: Program ended with an error exit code Error running cacls "Y:\@@Overdudu-Overdue shared\Jaspersoft BI test\jasperpro-4.7/postgresql/data" /e /c /t /p SomeUser:c : Program ended with an error exit code CACLS is a Windows tool to change Access Control Lists (ACLs): http://technet.microsoft.com/en-us/library/cc732245%28v=ws.10%29 . This line appears to be trying to grant user “SomeUser” write permission. The tool refuses to do this, or to give up and continue, when run on a non-NTFS file system. As a consequence, the entire install fails. From the evidence, it's not clear if JasperServer itself only runs from an NTFS volume. But it certainly seems that the Postgresql installer will only succeed on an NTFS volume. It would be nice if this restriction could be relaxed. But if it can't, then it would be nice if the Installer and the Installation Guide would document this. It looks like someone else on the forums had this problem: http://community.jaspersoft.com/questions/542315/jasperreports-server-installing-error-plz-help-me . By the way, when the Postgresql install fails, a cascade of cleanup results in no postgresql directory at all remaining. This makes it hard to fix the ACLs manually and continue the installation. My workaround was to free up some space on my C:\ drive, which is NTFS formatted, and then accept the default installation target. I hope this report is helpful for others.
  6. > It does not take a rocket scientist to figure it out. > > It is a JAVA error saying that the classes revision you tried to install do not match the JVM revision. Heh. I suppose it matters whether one considers installing the JasperServer eval package to be a system administration exercise, or a Java software development exercise. I believe it's in JasperSoft's interest, and perhaps in the community's interest, that installing it be more of a system administration exercise. And that means clearer error messages. A Java developer probably already knows that "java.lang.UnsupportedClassVersionError: Bad version number" means "the classes revision you tried to install do not match the JVM revision." And I'm probably revealling how little I know about Java software development and the JasperServer codebase, but I don't find it immediately intuitive that an error thrown by a file named "buildomatic/bin/db-common.xml" would be a Java runtime error. I do think it would be clearer if the package installer checked the JVM revision, and if the answer weren't satisfactory, would given an error message like, This package requires a JVM of version Y or higher. Your JVM is X. Installation cannot continue. From this other symptoms, I'm guessing that the underlying issue is that Mac OS X 10.5.8 supports a JVM which claims to be JavaSE 1.6, but it's not the kind of JavaSE 1.6 which satisfies parts of JasperServer. And hence JasperServer doesn't work on Mac OS X 10.5.8. It would be clearer also if the installation guide would either say 10.5.8 isn't supported, or give instructions for how to make it work.
  7. I found some useful logs, in <js-install> /apache-tomcat/logs/*, esp catalina.out . It looks like Jasperserver is failing to start because my Java environment isn't sufficient. The trigger for the failure appears to be class com.jaspersoft.ji.adhoc.service.AdhocTempARUKiller . For what it's worth, my machine has Apple's JDK 1.6 installed: % java -version java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-9M3425) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode) But, this 1.6 applies only to 64-bit Java code. 32-bit Java code is given Java SE 1.5, not 1.6. The 4.7 Installation Guide says, "1.2 Java Version Supported JasperReports Server supports Java 1.6 and 1.7. Versions earlier than Java 1.6 are not supported." So this might be my problem. Here's the contents of catalina.out: Jul 17, 2012 9:22:56 AM org.apache.catalina.core.AprLifecycleListener initINFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /Applications/jasperreports-server-4.7/postgresql/lib:/Applications/jasperreports-server-4.7/common/lib::.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/javaJul 17, 2012 9:23:26 AM org.apache.coyote.http11.Http11Protocol initINFO: Initializing Coyote HTTP/1.1 on http-8080Jul 17, 2012 9:23:26 AM org.apache.catalina.startup.Catalina loadINFO: Initialization processed in 31231 msJul 17, 2012 9:23:27 AM org.apache.catalina.core.StandardService startINFO: Starting service CatalinaJul 17, 2012 9:23:27 AM org.apache.catalina.core.StandardEngine startINFO: Starting Servlet Engine: Apache Tomcat/6.0.26Jul 17, 2012 9:23:27 AM org.apache.catalina.startup.HostConfig deployDescriptorINFO: Deploying configuration descriptor host-manager.xmlJul 17, 2012 9:23:27 AM org.apache.catalina.startup.HostConfig deployDescriptorINFO: Deploying configuration descriptor jasperserver-pro.xmlJul 17, 2012 9:23:30 AM org.apache.tomcat.util.modeler.Registry registerComponentSEVERE: Null component Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/jasperserver-pro,J2EEApplication=none,J2EEServer=noneJul 17, 2012 9:23:30 AM org.apache.catalina.startup.HostConfig deployDescriptorSEVERE: Error deploying configuration descriptor jasperserver-pro.xmljava.lang.UnsupportedClassVersionError: Bad version number in .class file (unable to load class com.jaspersoft.ji.adhoc.service.AdhocTempARUKiller) at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:2531) at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1010) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1483) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1361) at org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation(WebAnnotationSet.java:145) at org.apache.catalina.startup.WebAnnotationSet.loadApplicationListenerAnnotations(WebAnnotationSet.java:73) at org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(WebAnnotationSet.java:56) at org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(ContextConfig.java:297) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1074) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:261) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4377) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:637) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:563) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:498) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:785) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:519) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:581) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)Jul 17, 2012 9:23:30 AM org.apache.catalina.startup.HostConfig deployDescriptorINFO: Deploying configuration descriptor manager.xmlJul 17, 2012 9:23:30 AM org.apache.catalina.startup.HostConfig deployDirectoryINFO: Deploying web application directory docsJul 17, 2012 9:23:30 AM org.apache.catalina.startup.HostConfig deployDirectoryINFO: Deploying web application directory examplesJul 17, 2012 9:23:31 AM org.apache.catalina.startup.HostConfig deployDirectoryINFO: Deploying web application directory jasperserver-proJul 17, 2012 9:23:31 AM org.apache.tomcat.util.modeler.Registry registerComponentSEVERE: Null component Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/jasperserver-pro,J2EEApplication=none,J2EEServer=noneJul 17, 2012 9:23:31 AM org.apache.catalina.startup.HostConfig deployDirectorySEVERE: Error deploying web application directory jasperserver-projava.lang.UnsupportedClassVersionError: Bad version number in .class file (unable to load class com.jaspersoft.ji.adhoc.service.AdhocTempARUKiller) at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:2531) at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1010) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1483) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1361) at org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation(WebAnnotationSet.java:145) at org.apache.catalina.startup.WebAnnotationSet.loadApplicationListenerAnnotations(WebAnnotationSet.java:73) at org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(WebAnnotationSet.java:56) at org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(ContextConfig.java:297) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1074) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:261) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4377) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964) Next step, see if I can find the code for class com.jaspersoft.ji.adhoc.service.AdhocTempARUKiller, and see what JDK it's asking for.
  8. Hi, folks, I'm installing the JasperServer Pro 4.7 evaluation edition onto my Mac OS X 10.5.8 machine, and with both the x86 and x64 installers, I see the following error message. My interpretation (which could well be wrong) is that the sample report builder is failing, and perhaps the problem is that Java language utilities are failing to find the JDK version they seek. Any suggestions for what to do about this error? Has anyone else seen it? Contents of error log: [00:43:36] Log: jasperserver-sample-data:[00:43:36] About to import Sample Data[00:43:36] jasperserver_install_sampledata=1[00:43:36] note: sample data import has both minimal and sample data[00:43:36] -DimportFile=/Applications/jasperreports-server-4.7/buildomatic/install_resources/export/js-catalog[00:43:36] Loading sample data resources. This may take a moment.Executing /Applications/jasperreports-server-4.7/apache-ant/bin/ant import -DimportFile=install_resources/export/js-catalogScript exit code: 1Script output: Buildfile: /Applications/jasperreports-server-4.7/buildomatic/build.xml [echo] Filtering properties (cleaning out blank spaces) [echo] creating /Applications/jasperreports-server-4.7/buildomatic/build_conf/default [mkdir] Created dir: /Applications/jasperreports-server-4.7/buildomatic/build_conf/default [copy] Copying 1 file to /Applications/jasperreports-server-4.7/buildomatic/build_conf/default [copy] Copying 1 file to /Applications/jasperreports-server-4.7/buildomatic/build_conf/default [copy] Copying 1 file to /Applications/jasperreports-server-4.7/buildomatic/build_conf/default [copy] Copying 1 file to /Applications/jasperreports-server-4.7/buildomatic/build_conf/default [copy] Copying 1 file to /Applications/jasperreports-server-4.7/buildomatic/build_conf/default [copy] Copying 25 files to /Applications/jasperreports-server-4.7/buildomatic/build_conf/default [copy] Copying 1 file to /Applications/jasperreports-server-4.7/buildomatic/build_conf/default/webapp/WEB-INFScript stderr: BUILD FAILED/Applications/jasperreports-server-4.7/buildomatic/build.xml:63: The following error occurred while executing this line:/Applications/jasperreports-server-4.7/buildomatic/bin/install.xml:44: The following error occurred while executing this line:/Applications/jasperreports-server-4.7/buildomatic/conf_source/db/postgresql/db.xml:3: The following error occurred while executing this line:/Applications/jasperreports-server-4.7/buildomatic/bin/db-common.xml:37: java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:676) at org.apache.tools.ant.AntClassLoader.defineClassFromData(AntClassLoader.java:1124) at org.apache.tools.ant.AntClassLoader.getClassFromStream(AntClassLoader.java:1295) at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1351) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1311) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1064) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:375) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at org.apache.tools.ant.taskdefs.Definer.addDefinition(Definer.java:594) at org.apache.tools.ant.taskdefs.Definer.loadProperties(Definer.java:423) at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:279) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:168) at org.apache.tools.ant.taskdefs.ImportTask.importResource(ImportTask.java:216) at org.apache.tools.ant.taskdefs.ImportTask.execute(ImportTask.java:162) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:168) at org.apache.tools.ant.taskdefs.ImportTask.importResource(ImportTask.java:216) at org.apache.tools.ant.taskdefs.ImportTask.execute(ImportTask.java:162) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68) at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197) at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:154) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:168) at org.apache.tools.ant.taskdefs.ImportTask.importResource(ImportTask.java:216) at org.apache.tools.ant.taskdefs.ImportTask.execute(ImportTask.java:162) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:179) at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:82) at org.apache.tools.ant.Main.runBuild(Main.java:786) at org.apache.tools.ant.Main.startAnt(Main.java:218) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)Total time: 1 secondError running /Applications/jasperreports-server-4.7/apache-ant/bin/ant import -DimportFile=install_resources/export/js-catalog : BUILD FAILED/Applications/jasperreports-server-4.7/buildomatic/build.xml:63: The following error occurred while executing this line:/Applications/jasperreports-server-4.7/buildomatic/bin/install.xml:44: The following error occurred while executing this line:/Applications/jasperreports-server-4.7/buildomatic/conf_source/db/postgresql/db.xml:3: The following error occurred while executing this line:/Applications/jasperreports-server-4.7/buildomatic/bin/db-common.xml:37: java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:676) at org.apache.tools.ant.AntClassLoader.defineClassFromData(AntClassLoader.java:1124) at org.apache.tools.ant.AntClassLoader.getClassFromStream(AntClassLoader.java:1295) at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1351) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1311) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1064) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:375) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at org.apache.tools.ant.taskdefs.Definer.addDefinition(Definer.java:594) at org.apache.tools.ant.taskdefs.Definer.loadProperties(Definer.java:423) at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:279) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:168) at org.apache.tools.ant.taskdefs.ImportTask.importResource(ImportTask.java:216) at org.apache.tools.ant.taskdefs.ImportTask.execute(ImportTask.java:162) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:168) at org.apache.tools.ant.taskdefs.ImportTask.importResource(ImportTask.java:216) at org.apache.tools.ant.taskdefs.ImportTask.execute(ImportTask.java:162) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68) at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197) at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:154) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:168) at org.apache.tools.ant.taskdefs.ImportTask.importResource(ImportTask.java:216) at org.apache.tools.ant.taskdefs.ImportTask.execute(ImportTask.java:162) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:179) at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:82) at org.apache.tools.ant.Main.runBuild(Main.java:786) at org.apache.tools.ant.Main.startAnt(Main.java:218) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)Total time: 1 secondProblem running post-install step. Installation may not complete correctly Error running /Applications/jasperreports-server-4.7/apache-ant/bin/ant import -DimportFile=install_resources/export/js-catalog : BUILD FAILED/Applications/jasperreports-server-4.7/buildomatic/build.xml:63: The following error occurred while executing this line:/Applications/jasperreports-server-4.7/buildomatic/bin/install.xml:44: The following error occurred while executing this line:/Applications/jasperreports-server-4.7/buildomatic/conf_source/db/postgresql/db.xml:3: The following error occurred while executing this line:/Applications/jasperreports-server-4.7/buildomatic/bin/db-common.xml:37: java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:676) at org.apache.tools.ant.AntClassLoader.defineClassFromData(AntClassLoader.java:1124) at org.apache.tools.ant.AntClassLoader.getClassFromStream(AntClassLoader.java:1295) at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1351) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1311) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1064) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:375) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at org.apache.tools.ant.taskdefs.Definer.addDefinition(Definer.java:594) at org.apache.tools.ant.taskdefs.Definer.loadProperties(Definer.java:423) at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:279) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:168) at org.apache.tools.ant.taskdefs.ImportTask.importResource(ImportTask.java:216) at org.apache.tools.ant.taskdefs.ImportTask.execute(ImportTask.java:162) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:168) at org.apache.tools.ant.taskdefs.ImportTask.importResource(ImportTask.java:216) at org.apache.tools.ant.taskdefs.ImportTask.execute(ImportTask.java:162) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68) at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197) at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:154) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:168) at org.apache.tools.ant.taskdefs.ImportTask.importResource(ImportTask.java:216) at org.apache.tools.ant.taskdefs.ImportTask.execute(ImportTask.java:162) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:179) at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:82) at org.apache.tools.ant.Main.runBuild(Main.java:786) at org.apache.tools.ant.Main.startAnt(Main.java:218) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)Total time: 1 second
  9. Hi, folks: I'm looking at Jaspersoft's evaluation packages for JasperReports Server 4.7: jasperreports-server-4.7-osx-x86-installer.app.zip jasperreports-server-4.7-osx-x64-installer.app.zip Which should I install on my Mac OS X 10.5.8 machine? I get that x86 refers to 32-bit intel architecture code, and x64 refers to 64-bit intel architecture code. I understand that Mac OS X 10.5.8 is generally considered 32-bit. The big deal about Mac OS X 10.6 is that many parts of the system are implemented in 64-bits. I'm not sure if this should affect my choice of Jasperreports code, though. Apple supplies an implementation of the JDK 1.6, but only in 64-bit. The 32-bit implementation of the JDK is 1.5. I've already had an experience with Eclipse (the software development tool) where I had to use the 64-bit version of Eclipse in order to invoke JDK 1.6; the 32-bit version of Eclipse could only invoke JDK 1.6. I don't see anything in the Install Guide (JasperReports-Server-Install-Guide-4.7.pdf) which gives guidance on whether to choose the x86 or the x64 installer, for any platform. The closest hint is an afterthought at the end of section 2.2 "Starting the Installer", which says that it's OK to use the x86 installer on a 64-bit OS. I've tried installing the x86, then the x64 versions on my Mac OS X 10.5.8. Both fail to work, with identical symptoms. If anyone could offer any guidance, I'd appreciate it. --Jim DeLaHunt, Vancouver, Canada.
  10. I've tried installing the JasperSoft commercial trial version of JasperServer on my Mac OS X 10.5.8 machine. Each time, the install appears to complete, and Tomcat is running, but the page at the JasperServer Pro URL, http://localhost:8080/jasperserver-pro/ , displays a page complaining about an HTTP Status 503 "This application is not currently available". The URL above, http://localhost:8080/, shows a Tomcat page which appears to indicate Tomcat is running. Any suggestions for how to diagnose this problem? The JasperServer Installation Guide for 4.7 isn't much help. It talks about manually deleting the catalina.pid file in order to allow Tomcat to start. However, I think Tomcat is starting. It's JasperServer that is not starting. I think. Thanks in advance for any tips. --Jim DeLaHunt, Vancouver BC
×
×
  • Create New...