markmaslow

If 3.7.1 works, I guess it must be a 3.7.0 problem. I'll look into upgrading. Thanks.

Apparently, it's a bug - if you turn on auditing to audit logins to the server, you can't connect to the server from iReport - all you get is the cryptic message cited.

We're running JasperServer-pro 3.7 and using iReport Professional 3.7.0. We've been connecting successfully for quite some time. Starting yesterday, any attempts to connect to the server from iReport yield: Error: ; nested exception is org.xml.sax.SAXException: Bad envelope tag: html This occurs from two different client machines running iReport, attempting to connect to two different installations of JasperServer. I opened a case with tech support last night, but don't seem to be getting any helpful responses from them so far. At this point, we are unable to modify or deploy any reports that are served up by Jasper server using iReport. Does anyone have any clues as to what might be causing this?

If the server is not accessed for a period of time, it seems to loose its connection to the repository. Messages in log: org.springframework.transaction.CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is org.hibernate.TransactionException: JDBC begin failed: com.mysql.jdbc.CommunicationsException: The last packet successfully received from the server was 62,798,203 milliseconds ago. The last packet sent successfully to the server was 62,798,203 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. At this point, it seems that the only way to get rid of the message is to restart the Tomcat service. What is the recommended solution to this problem?

OK - I finally figured it out. The file that needs to have the JNDI resource defined is: Tomcat\conf\Catalina\localhost\jasperserver-pro.xml The META-INF/web.xml seems to be ignored in favor of that one.

I am deploying to Tomcat 6. I tried cloning one of the existing jndi datasources, but that didn't work either. In the META-INF/context.xml, I have the following 2 entries: <Resource name="jdbc/foodmart" auth="Container" type="javax.sql.DataSource" maxActive="100" maxIdle="30" maxWait="10000" username="jasperdb" password="password" driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://127.0.0.1:3306/foodmart"/> <Resource name="jdbc/testfoodmart" auth="Container" type="javax.sql.DataSource" maxActive="100" maxIdle="30" maxWait="10000" username="jasperdb" password="password" driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://127.0.0.1:3306/foodmart"/> In thet WEB-INF/web.xml, I have the following 2 entries: <resource-ref> <description>Foodmart database</description> <res-ref-name>jdbc/foodmart</res-ref-name> <res-type>javax.sql.DataSource</res-type> <res-auth>Container</res-auth> </resource-ref> <resource-ref> <description>Test Foodmart database</description> <res-ref-name>jdbc/testfoodmart</res-ref-name> <res-type>javax.sql.DataSource</res-type> <res-auth>Container</res-auth> </resource-ref> I can successfully connect to the jdbc/foodmart datasource, but the test on the jdbc/testfoodmart datasource fails. Very mysterious.

Yes, I want to use a JNDI connection in order to take advantage of connection pooling. Connecting to the DB is a relatively high overhead operation, so it is more efficient to reuse connections than to open a new one every time a report is run. I have a JNDI datasource defined in the GlobalNamingResources section of the server.xml file for the tomcat server. I know that it works, because another web app on the same server uses it. I copied the resource from server.xml into context.xml in the META-INF folder of the jasperserver application directory. Stopped and restarted the server, but still get "Test failed" when pressing the "Test connection" button after trying to set up a datasource that uses it. The server must be able to find the driver, since I can set up a regular JDBC connection with that driver. Unfortunately, there seems to be no information whatsoever available to give me any clues as to what the cause of the problem might be, and I have run out of ideas. If anyone has any ideas as to things to try, I would greatly appreciate hearing them.

I am unable to create a JNDI database connection in JasperServer. The following is in the Tomcat server.xml file, inside the GlobalNamingResources section: <Resource name="jdbc/ClubOnBarbeau" auth="Container" type="javax.sql.DataSource" driverClassName="com.sybase.jdbc3.jdbc.SybDriver" url="jdbc:sybase:Tds:10.1.1.xx:xx/xxxx" username="*****" password="*****" maxActive="20" maxIdle="10" maxWait="20000" /> I am able to connect to this datasource in another web application. In the web.xml for that application, I put the following: <ResourceLink name="jdbc/ClubOnBarbeau" global="jdbc/ClubOnBarbeau" type="javax.sql.DataSource" /> The application connects without problem. But if I try creating a new JNDI datasource in JasperServer, using the following Service Name: jdbc/ClubOnBarbeau When I press "Test connection", I get "Test failed". No other information seems to be available. Am I missing something?