Jasper server 6.0.1 Deployment error with SOA 5

Solution Unverified - Updated -

Environment

  • RedHat JBoss SOA
    • 5.x

Issue

  • The Jasper server 6.0.1 cannot be deploy with with JBoss SOA 5 and throwing below error.
DEPLOYMENTS IN ERROR:
  Deployment "vfsfile:/abc/esb531/jboss-as/server/production/deploy/jasperserver.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/abc/esb531/jboss-as/server/production/deploy/jasperserver.war/ deployment failed

Resolution

  • The error looks like it is trying to load "/abc/esb531/jboss-as/server/production/deploy/jasperserver.war/WEB-INF/lib/jasperserver-api-engine-impl-6.0.1.jar/com/jaspersoft/jasperserver/api/engine/jasperreports/service/impl" as a jar, and may be caused by it instead being an exploded directory. It does not look like the application packages the "Snowdrop" components which are requires to make Spring correctly handle JBoss' vfs: URLs, so it may be the case that the URL is "vfs:/abc/esb531/jboss-as/server/production/deploy/jasperserver.war/WEB-INF/lib/jasperserver-api-engine-impl-6.0.1.jar/com/jaspersoft/jasperserver/api/engine/jasperreports/service/impl", and it is stripping off the URL scheme and acting as if the rest was a file path (which it is not usually).

  • The error looks to be a problem with the application and/or the version of Spring packaged, which is trying to load the file incorrectly. If you do have support from Jasper,try to consult with them. Adding the Snowdrop components may be the solution, but if the application is certified on EAP 5, then it should work.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments