Jump to content
Changes to the Jaspersoft community edition download ×

dana.gray

Members
  • Posts

    8
  • Joined

  • Last visited

dana.gray's Achievements

Rookie

Rookie (2/14)

  • Week One Done
  • One Month Later
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. I know there are instructions on how to install Jasper Report Server on Wildfly. But these instructions just demonstrate how to install it in Standup Mode only. I need to install JRS onto Wildfly in domain mode or domain controller. I've tried installing it in Standup mode and then creating a war file that I then deploy in Wildfly domain but it throws the following exception stack. What is the proper way to deploy JRS in Wildfly on the domain profile? Please advise. 2023-11-01 14:05:45,124 DEBUG [org.jboss.as.config] (MSC service thread 1-7) VM Arguments: -D[server:server-one] -XX:PermSize=1028m -XX:MaxPermSize=1028m -Xms2560m -Xmx10240m -Djava.net.preferIPv4Stack=true -Djboss.home.dir=C:wildfly-8.1.0.Final -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.log.dir=C:wildfly-8.1.0.Finaldomainserversserver-onelog -Djboss.server.temp.dir=C:wildfly-8.1.0.Finaldomainserversserver-onetmp -Djboss.server.data.dir=C:wildfly-8.1.0.Finaldomainserversserver-onedata -Dlogging.configuration=file:C:wildfly-8.1.0.Finaldomainserversserver-onedatalogging.properties 2023-11-01 14:05:45,249 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.2.2.Final 2023-11-01 14:05:45,264 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.2.2.Final 2023-11-01 14:05:45,351 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 4.0.3.Final 2023-11-01 14:05:50,751 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 31) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique. 2023-11-01 14:05:50,751 INFO [org.jboss.as.security] (ServerService Thread Pool -- 32) JBAS013171: Activating Security Subsystem 2023-11-01 14:05:50,767 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 29) JBAS015537: Activating WebServices Extension 2023-11-01 14:05:50,782 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem 2023-11-01 14:05:50,782 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) JBAS010280: Activating Infinispan subsystem. 2023-11-01 14:05:50,782 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.21.Beta1 2023-11-01 14:05:50,798 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 49) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors 2023-11-01 14:05:50,798 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 52) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 2023-11-01 14:05:50,814 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 47) JBAS016300: Activating JacORB Subsystem 2023-11-01 14:05:50,970 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 41) JBAS012615: Activated the following JSF Implementations: [main] 2023-11-01 14:05:50,970 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017502: Undertow 1.0.15.Final starting 2023-11-01 14:05:50,970 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 30) JBAS017502: Undertow 1.0.15.Final starting 2023-11-01 14:05:51,111 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service 2023-11-01 14:05:51,111 INFO [org.jboss.as.connector.logging] (MSC service thread 1-5) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.5.Final) 2023-11-01 14:05:51,111 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default] 2023-11-01 14:05:51,126 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = h2 2023-11-01 14:05:51,251 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 30) JBAS017527: Creating file handler for path C:wildfly-8.1.0.Final/welcome-content 2023-11-01 14:05:51,657 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017525: Started server default-server. 2023-11-01 14:05:51,673 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017531: Host default-host starting 2023-11-01 14:05:51,782 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 2023-11-01 14:05:51,907 WARN [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal 2023-11-01 14:05:51,907 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "jasperserver-pro.war" (runtime-name: "jasperserver-pro.war") 2023-11-01 14:05:51,907 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "TIsqlserver-5.14.1.jar" (runtime-name: "TIsqlserver-5.14.1.jar") 2023-11-01 14:05:52,048 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 2023-11-01 14:05:52,048 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:wildfly-8.1.0.Finaldomainserversserver-onedatamessagingjournal,bindingsDirectory=C:wildfly-8.1.0.Finaldomainserversserver-onedatamessagingbindings,largeMessagesDirectory=C:wildfly-8.1.0.Finaldomainserversserver-onedatamessaginglargemessages,pagingDirectory=C:wildfly-8.1.0.Finaldomainserversserver-onedatamessagingpaging) 2023-11-01 14:05:52,064 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221006: Waiting to obtain live lock 2023-11-01 14:05:52,157 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221013: Using NIO Journal 2023-11-01 14:05:52,204 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 54) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability. 2023-11-01 14:05:52,329 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221043: Adding protocol support CORE 2023-11-01 14:05:52,329 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221043: Adding protocol support AMQP 2023-11-01 14:05:52,345 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221043: Adding protocol support STOMP 2023-11-01 14:05:52,492 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221034: Waiting to obtain live lock 2023-11-01 14:05:52,492 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221035: Live Server Obtained live lock 2023-11-01 14:05:52,649 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.4.Final 2023-11-01 14:05:52,758 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010403: Deploying JDBC-compliant driver class tibcosoftware.jdbc.sqlserver.SQLServerDriver (version 5.1) 2023-11-01 14:05:52,789 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = TIsqlserver-5.14.1.jar 2023-11-01 14:05:52,836 INFO [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor 2023-11-01 14:05:52,836 INFO [org.jboss.messaging] (MSC service thread 1-5) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor 2023-11-01 14:05:52,961 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221007: Server is now live 2023-11-01 14:05:52,961 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [c7910a6a-781d-11ee-a168-719ebcdbeb4b] 2023-11-01 14:05:53,039 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 54) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory 2023-11-01 14:05:53,039 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 57) HQ221003: trying to deploy queue jms.queue.DLQ 2023-11-01 14:05:53,071 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ 2023-11-01 14:05:53,071 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221003: trying to deploy queue jms.queue.ExpiryQueue 2023-11-01 14:05:53,071 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue 2023-11-01 14:05:53,071 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 55) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 2023-11-01 14:05:53,133 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010406: Registered connection factory java:/JmsXA 2023-11-01 14:05:53,196 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started 2023-11-01 14:05:53,196 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra 2023-11-01 14:05:53,196 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] 2023-11-01 14:05:53,196 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory 2023-11-01 14:06:46,997 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015959: Additional resource root /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/mariadb-java-client-1.1.2.jar added via jboss-deployment-structure.xml does not exist 2023-11-01 14:06:47,106 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry avalon-framework-4.2.0.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry batik-all-1.7.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry commons-io-1.3.1.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry commons-logging-1.0.4.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry serializer-2.7.0.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry servlet-2.2.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xalan-2.7.0.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xercesImpl-2.7.1.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xml-apis-1.3.04.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xml-apis-ext-1.3.04.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xmlgraphics-commons-1.3.1.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry fop-hyph.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry jai_codec.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry jai_core.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry jai_imageio.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry jimi-1.0.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xmlunit1.0.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/fop-0.95.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,153 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $hk2-utils.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,153 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $javax.inject.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,153 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $hk2-api.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,153 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $aopalliance-repackaged.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,153 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $config-types.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,153 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $hk2-core.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,153 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $hk2-config.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,168 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $tiger-types.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,168 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $hibernate-validator.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,168 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $validation-api.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,168 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $jboss-logging.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,168 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $classmate.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,168 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $hk2-locator.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,168 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $javax.inject.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,168 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $javassist.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,168 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $hk2-runlevel.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,168 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $class-model.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,168 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry $asm-all-repackaged.$jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/hk2-2.5.0-b32.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,262 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry jaxb-api.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/jaxb-impl-2.1.5.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,278 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry activation.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/jaxb-impl-2.1.5.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,278 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry jsr173_1.0_api.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/jaxb-impl-2.1.5.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,278 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry jaxb1-impl.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/jaxb-impl-2.1.5.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,293 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry activation.jar in /C:/wildfly-8.1.0.Final/content/jasperserver-pro.war/WEB-INF/lib/mail-1.4.jar does not point to a valid jar for a Class-Path reference. 2023-11-01 14:06:47,996 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."jasperserver-pro.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jasperserver-pro.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "jasperserver-pro.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.1.0.Final.jar:8.1.0.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_382] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_382] at java.lang.Thread.run(Thread.java:750) [rt.jar:1.8.0_382] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011666: Could not parse file C:wildfly-8.1.0.Finaldomainserversserver-onetmpvfstemptemp97584868c3133263content-91a4ebf0859ad950WEB-INFapplicationContext-jms.xml at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:99) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.1.0.Final.jar:8.1.0.Final] ... 5 more Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011666: Could not parse file C:wildfly-8.1.0.Finaldomainserversserver-onetmpvfstemptemp97584868c3133263content-91a4ebf0859ad950WEB-INFapplicationContext-jms.xml at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:96) ... 6 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[11,107] Message: Unexpected element '{http://www.springframework.org/schema/beans}beans' at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:90) ... 6 more 2023-11-01 14:06:47,996 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "jacorb")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.jacorb.orb-service is missing [jboss.binding.jacorb-ssl, jboss.binding.jacorb]"]} 2023-11-01 14:06:47,996 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "jasperserver-pro.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit."jasperserver-pro.war".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit."jasperserver-pro.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "jasperserver-pro.war" Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011666: Could not parse file C:\wildfly-8.1.0.Final\domain\servers\server-one\tmp\vfs\temp\temp97584868c3133263\content-91a4ebf0859ad950\WEB-INF\applicationContext-jms.xml Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011666: Could not parse file C:\wildfly-8.1.0.Final\domain\servers\server-one\tmp\vfs\temp\temp97584868c3133263\content-91a4ebf0859ad950\WEB-INF\applicationContext-jms.xml Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[11,107] Message: Unexpected element '{http://www.springframework.org/schema/beans}beans'"}} 2023-11-01 14:06:48,043 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "TIsqlserver-5.14.1.jar" (runtime-name : "TIsqlserver-5.14.1.jar") 2023-11-01 14:06:48,043 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "jasperserver-pro.war" (runtime-name : "jasperserver-pro.war") 2023-11-01 14:06:48,043 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.binding.jacorb (missing) dependents: [service jboss.jacorb.orb-service] service jboss.binding.jacorb-ssl (missing) dependents: [service jboss.jacorb.orb-service] JBAS014777: Services which failed to start: service jboss.deployment.unit."jasperserver-pro.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jasperserver-pro.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "jasperserver-pro.war" 2023-11-01 14:06:48,043 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 63817ms - Started 233 of 294 services (6 services failed or missing dependencies, 94 services are lazy, passive or on-demand)
  2. It looks like the Role Properties only lists the first 20 users (in alphabetical order). How do I configure this to show ALL users assigned to a role?
  3. Swapnil, thank you for your reply. I did mention in the original post that the user, role and the administrator account conducting the searches are all members of the same org. We only have one org so there's no issue with an MT.
  4. I haven't received an answer to this question. Can someone please assist me with this?
  5. We have a user account that isn't showing in the Role Properties User list. The account can be manually searched for and found and the Role shows in the Users properties but the account doesn't show natively when the Role Properties is selected. Both the user, role and administrator account conducting the searches belong to the same (and only) organization. See screenshots below. Any reason why this account doesn't show with the rest of the users within this role?
  6. I've discovered that the escape characters needed for the domainusername account to be pushed to SQL Server are two additional backslashes. In other words, the dbUsername in the default_master.properties file should look like domain\username. This will result in the correct username of domainusername when Jasper attempts to connect to SQL Server. I'm now having an issue with the TIBCO SQL Server driver in that even with this correct username it's throwing the following error. Generic connection failure: [[TibcoSoftware][sqlServer JDBC Driver][sqlServer]Login failed for user 'STATExxxxxx'.]. Treating problem with JDBC connection as unrecoverable. I'm able to log in using a SQL Server Authentication account but not a Windows Authentication using this same driver. Any ideas as to what the issue might be?
  7. Hello Paul, Our SQL Server is setup to utilize Windows Authentication instead of SQL Server Authentication so the usernames include the Active Directory domain name. Example: stateaccountname. When I add this to the default_master.properties file for the "dbUsername=" the js-export.bat script removes the backslash before presenting it to the SQL Server for authentication. This results in a failed connection which in turn crashes the script. I guess the question is, can a username include special characters such as a backslash ''?
  8. I'm trying to upgrade our Jasper Server Application utilizing SQL Server. When I provide my username which includes the domain (domainusername) in the default_master.properties file, the js-export.bat script omits the '' when attempting to connect to the SQL Server. This results in the script not connecting to the server and crashing the repository database export. I've attempted using the \ escape for the backspace character but this hasn't seemed to work. What can I do to get this script (and ultimately the upgrade or install scripts) to work with my domainusername dbUserName? Please advise.
×
×
  • Create New...