ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 6364ms - Started 142 of 227 services (6 services failed or missing dependencies, 74 services are passive or on-demand)
kelevratf Oct 22, 2012 9:25 AMHello all. I have those ERROR during deploying . What can couse this??
ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 6364ms - Started 142 of 227 services (6 services failed or missing dependencies, 74 services are passive or on-demand)
And full log:
16:16:21,957 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
16:16:22,027 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
16:16:21,986 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
16:16:21,981 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
16:16:21,979 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
16:16:22,276 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
16:16:22,277 INFO [org.jboss.as.security] (MSC service thread 1-7) JBAS013100: Current PicketBox version=4.0.7.Final
16:16:22,295 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
16:16:22,636 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
16:16:22,641 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
16:16:22,790 TRACE [org.jboss.security.jacc.DelegatingPolicy] (MSC service thread 1-7) Loaded JACC permissions: true
16:16:22,790 TRACE [org.jboss.security.jacc.DelegatingPolicy] (MSC service thread 1-7) loaded policy context classclass javax.security.jacc.PolicyContext
16:16:23,147 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:16:23,197 TRACE [org.jboss.security.authentication.JBossCachedAuthenticationManager] (MSC service thread 1-8) CallbackHandler: org.jboss.security.auth.callback.JBossCallbackHandler@12b8501d
16:16:23,198 TRACE [org.jboss.security.authentication.JBossCachedAuthenticationManager] (MSC service thread 1-2) CallbackHandler: org.jboss.security.auth.callback.JBossCallbackHandler@75157f77
16:16:23,198 TRACE [org.jboss.security.authentication.JBossCachedAuthenticationManager] (MSC service thread 1-3) CallbackHandler: org.jboss.security.auth.callback.JBossCallbackHandler@47662250
16:16:23,198 TRACE [org.jboss.security.authentication.JBossCachedAuthenticationManager] (MSC service thread 1-7) CallbackHandler: org.jboss.security.auth.callback.JBossCallbackHandler@2c5e5c15
16:16:23,208 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.2.GA
16:16:23,479 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.0)
16:16:24,014 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
16:16:24,101 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
16:16:24,102 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/rq]
16:16:24,215 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory /opt/jboss-as-7.1.1.Final/standalone/deployments
16:16:24,221 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /127.0.0.1:9999
16:16:24,221 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:4447
16:16:24,967 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.jdbc-driver.oracle (missing) dependents: [service jboss.data-source.java:jboss/datasources/rq1, service jboss.data-source.java:jboss/datasources/ttkDatasource, service jboss.data-source.java:jboss/datasources/ttkTicketsDatasource]
16:16:25,069 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
16:16:25,070 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 6364ms - Started 142 of 227 services (6 services failed or missing dependencies, 74 services are passive or on-demand)
16:16:25,306 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "RQ.war"
16:16:27,338 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry activation.jar in "/content/RQ.war/WEB-INF/lib/mail-1.4.jar" does not point to a valid jar for a Class-Path reference.
16:16:27,683 INFO [org.jboss.as.jpa] (MSC service thread 1-6) JBAS011401: Read persistence.xml for TTKTickets
16:16:27,985 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016002: Processing weld deployment RQ.war
16:16:28,043 INFO [org.hibernate.search.Version] (MSC service thread 1-6) HSEARCH000034: Hibernate Search 4.1.0.Beta2
16:16:28,044 INFO [org.jboss.seam.persistence.HibernatePersistenceProvider] (MSC service thread 1-6) Hibernate Search is available
16:16:28,050 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named RoleService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/RoleService!com.kmware.ttk.service.RoleService
java:app/RQ/RoleService!com.kmware.ttk.service.RoleService
java:module/RoleService!com.kmware.ttk.service.RoleService
java:global/RQ/RoleService
java:app/RQ/RoleService
java:module/RoleService
16:16:28,051 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SubtopicService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/SubtopicService!com.kmware.ttk.service.SubtopicService
java:app/RQ/SubtopicService!com.kmware.ttk.service.SubtopicService
java:module/SubtopicService!com.kmware.ttk.service.SubtopicService
java:global/RQ/SubtopicService
java:app/RQ/SubtopicService
java:module/SubtopicService
16:16:28,052 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named KladrService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/KladrService!com.kmware.ttk.service.KladrService
java:app/RQ/KladrService!com.kmware.ttk.service.KladrService
java:module/KladrService!com.kmware.ttk.service.KladrService
java:global/RQ/KladrService
java:app/RQ/KladrService
java:module/KladrService
16:16:28,052 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named StatusTransitionService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/StatusTransitionService!com.kmware.ttk.service.StatusTransitionService
java:app/RQ/StatusTransitionService!com.kmware.ttk.service.StatusTransitionService
java:module/StatusTransitionService!com.kmware.ttk.service.StatusTransitionService
java:global/RQ/StatusTransitionService
java:app/RQ/StatusTransitionService
java:module/StatusTransitionService
16:16:28,053 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SubsidiaryService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/SubsidiaryService!com.kmware.ttk.service.SubsidiaryService
java:app/RQ/SubsidiaryService!com.kmware.ttk.service.SubsidiaryService
java:module/SubsidiaryService!com.kmware.ttk.service.SubsidiaryService
java:global/RQ/SubsidiaryService
java:app/RQ/SubsidiaryService
java:module/SubsidiaryService
16:16:28,054 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named ConnectionTypeWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,054 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SourceService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/SourceService!com.kmware.ttk.service.SourceService
java:app/RQ/SourceService!com.kmware.ttk.service.SourceService
java:module/SourceService!com.kmware.ttk.service.SourceService
java:global/RQ/SourceService
java:app/RQ/SourceService
java:module/SourceService
16:16:28,055 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named CurrentUserManager in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/CurrentUserManager!com.kmware.ttk.tickets.account.CurrentUserManager
java:app/RQ/CurrentUserManager!com.kmware.ttk.tickets.account.CurrentUserManager
java:module/CurrentUserManager!com.kmware.ttk.tickets.account.CurrentUserManager
java:global/RQ/CurrentUserManager
java:app/RQ/CurrentUserManager
java:module/CurrentUserManager
16:16:28,056 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named AuthWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,056 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named DocumentChangesHistoryService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/DocumentChangesHistoryService!com.kmware.ttk.service.DocumentChangesHistoryService
java:app/RQ/DocumentChangesHistoryService!com.kmware.ttk.service.DocumentChangesHistoryService
java:module/DocumentChangesHistoryService!com.kmware.ttk.service.DocumentChangesHistoryService
java:global/RQ/DocumentChangesHistoryService
java:app/RQ/DocumentChangesHistoryService
java:module/DocumentChangesHistoryService
16:16:28,057 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SupportTicketDocumentCreator in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/SupportTicketDocumentCreator!com.kmware.ttk.webservices.creators.SupportTicketDocumentCreator
java:app/RQ/SupportTicketDocumentCreator!com.kmware.ttk.webservices.creators.SupportTicketDocumentCreator
java:module/SupportTicketDocumentCreator!com.kmware.ttk.webservices.creators.SupportTicketDocumentCreator
java:global/RQ/SupportTicketDocumentCreator
java:app/RQ/SupportTicketDocumentCreator
java:module/SupportTicketDocumentCreator
16:16:28,058 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named AddressWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,059 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SupportTicketDocumentWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,059 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named RequestDocumentWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,059 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SupportTicketCommentService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/SupportTicketCommentService!com.kmware.ttk.service.SupportTicketCommentService
java:app/RQ/SupportTicketCommentService!com.kmware.ttk.service.SupportTicketCommentService
java:module/SupportTicketCommentService!com.kmware.ttk.service.SupportTicketCommentService
java:global/RQ/SupportTicketCommentService
java:app/RQ/SupportTicketCommentService
java:module/SupportTicketCommentService
16:16:28,060 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named PromotionWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,061 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SupportTicketDocumentService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/SupportTicketDocumentService!com.kmware.ttk.service.SupportTicketDocumentService
java:app/RQ/SupportTicketDocumentService!com.kmware.ttk.service.SupportTicketDocumentService
java:module/SupportTicketDocumentService!com.kmware.ttk.service.SupportTicketDocumentService
java:global/RQ/SupportTicketDocumentService
java:app/RQ/SupportTicketDocumentService
java:module/SupportTicketDocumentService
16:16:28,061 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named KladrUpdateSettingsService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/KladrUpdateSettingsService!com.kmware.ttk.service.KladrUpdateSettingsService
java:app/RQ/KladrUpdateSettingsService!com.kmware.ttk.service.KladrUpdateSettingsService
java:module/KladrUpdateSettingsService!com.kmware.ttk.service.KladrUpdateSettingsService
java:global/RQ/KladrUpdateSettingsService
java:app/RQ/KladrUpdateSettingsService
java:module/KladrUpdateSettingsService
16:16:28,062 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named RolePermissionService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/RolePermissionService!com.kmware.ttk.service.RolePermissionService
java:app/RQ/RolePermissionService!com.kmware.ttk.service.RolePermissionService
java:module/RolePermissionService!com.kmware.ttk.service.RolePermissionService
java:global/RQ/RolePermissionService
java:app/RQ/RolePermissionService
java:module/RolePermissionService
16:16:28,063 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named RoleRolePermissionService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/RoleRolePermissionService!com.kmware.ttk.service.RoleRolePermissionService
java:app/RQ/RoleRolePermissionService!com.kmware.ttk.service.RoleRolePermissionService
java:module/RoleRolePermissionService!com.kmware.ttk.service.RoleRolePermissionService
java:global/RQ/RoleRolePermissionService
java:app/RQ/RoleRolePermissionService
java:module/RoleRolePermissionService
16:16:28,064 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named TicketsAuthenticator in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/TicketsAuthenticator!org.jboss.seam.security.Authenticator
java:app/RQ/TicketsAuthenticator!org.jboss.seam.security.Authenticator
java:module/TicketsAuthenticator!org.jboss.seam.security.Authenticator
java:global/RQ/TicketsAuthenticator
java:app/RQ/TicketsAuthenticator
java:module/TicketsAuthenticator
16:16:28,065 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named ServiceWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,065 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named ApplicationDocumentService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/ApplicationDocumentService!com.kmware.ttk.service.ApplicationDocumentService
java:app/RQ/ApplicationDocumentService!com.kmware.ttk.service.ApplicationDocumentService
java:module/ApplicationDocumentService!com.kmware.ttk.service.ApplicationDocumentService
java:global/RQ/ApplicationDocumentService
java:app/RQ/ApplicationDocumentService
java:module/ApplicationDocumentService
16:16:28,066 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SourceWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,066 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named KladrStreetShorteningService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/KladrStreetShorteningService!com.kmware.ttk.service.KladrStreetShorteningService
java:app/RQ/KladrStreetShorteningService!com.kmware.ttk.service.KladrStreetShorteningService
java:module/KladrStreetShorteningService!com.kmware.ttk.service.KladrStreetShorteningService
java:global/RQ/KladrStreetShorteningService
java:app/RQ/KladrStreetShorteningService
java:module/KladrStreetShorteningService
16:16:28,067 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named TopicService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/TopicService!com.kmware.ttk.service.TopicService
java:app/RQ/TopicService!com.kmware.ttk.service.TopicService
java:module/TopicService!com.kmware.ttk.service.TopicService
java:global/RQ/TopicService
java:app/RQ/TopicService
java:module/TopicService
16:16:28,068 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named PromotionService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/PromotionService!com.kmware.ttk.service.PromotionService
java:app/RQ/PromotionService!com.kmware.ttk.service.PromotionService
java:module/PromotionService!com.kmware.ttk.service.PromotionService
java:global/RQ/PromotionService
java:app/RQ/PromotionService
java:module/PromotionService
16:16:28,068 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named CityService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/CityService!com.kmware.ttk.service.CityService
java:app/RQ/CityService!com.kmware.ttk.service.CityService
java:module/CityService!com.kmware.ttk.service.CityService
java:global/RQ/CityService
java:app/RQ/CityService
java:module/CityService
16:16:28,069 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named ConnectionTypeService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/ConnectionTypeService!com.kmware.ttk.service.ConnectionTypeService
java:app/RQ/ConnectionTypeService!com.kmware.ttk.service.ConnectionTypeService
java:module/ConnectionTypeService!com.kmware.ttk.service.ConnectionTypeService
java:global/RQ/ConnectionTypeService
java:app/RQ/ConnectionTypeService
java:module/ConnectionTypeService
16:16:28,070 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named RequestDocumentService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/RequestDocumentService!com.kmware.ttk.service.RequestDocumentService
java:app/RQ/RequestDocumentService!com.kmware.ttk.service.RequestDocumentService
java:module/RequestDocumentService!com.kmware.ttk.service.RequestDocumentService
java:global/RQ/RequestDocumentService
java:app/RQ/RequestDocumentService
java:module/RequestDocumentService
16:16:28,070 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named DomService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/DomService!com.kmware.ttk.service.DomService
java:app/RQ/DomService!com.kmware.ttk.service.DomService
java:module/DomService!com.kmware.ttk.service.DomService
java:global/RQ/DomService
java:app/RQ/DomService
java:module/DomService
16:16:28,071 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named ServiceService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/ServiceService!com.kmware.ttk.service.ServiceService
java:app/RQ/ServiceService!com.kmware.ttk.service.ServiceService
java:module/ServiceService!com.kmware.ttk.service.ServiceService
java:global/RQ/ServiceService
java:app/RQ/ServiceService
java:module/ServiceService
16:16:28,072 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named TopicWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,072 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named CityWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,073 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SubsidiaryWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,073 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SubtopicConverter in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/SubtopicConverter!javax.faces.convert.Converter
java:app/RQ/SubtopicConverter!javax.faces.convert.Converter
java:module/SubtopicConverter!javax.faces.convert.Converter
java:global/RQ/SubtopicConverter
java:app/RQ/SubtopicConverter
java:module/SubtopicConverter
16:16:28,074 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named StreetService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/StreetService!com.kmware.ttk.service.StreetService
java:app/RQ/StreetService!com.kmware.ttk.service.StreetService
java:module/StreetService!com.kmware.ttk.service.StreetService
java:global/RQ/StreetService
java:app/RQ/StreetService
java:module/StreetService
16:16:28,074 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named ApplicationDocumentWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,075 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named RequestDocumentCreator in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/RequestDocumentCreator!com.kmware.ttk.webservices.creators.RequestDocumentCreator
java:app/RQ/RequestDocumentCreator!com.kmware.ttk.webservices.creators.RequestDocumentCreator
java:module/RequestDocumentCreator!com.kmware.ttk.webservices.creators.RequestDocumentCreator
java:global/RQ/RequestDocumentCreator
java:app/RQ/RequestDocumentCreator
java:module/RequestDocumentCreator
16:16:28,075 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named UserService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/UserService!com.kmware.ttk.service.UserService
java:app/RQ/UserService!com.kmware.ttk.service.UserService
java:module/UserService!com.kmware.ttk.service.UserService
java:global/RQ/UserService
java:app/RQ/UserService
java:module/UserService
16:16:28,076 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named StatusService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/StatusService!com.kmware.ttk.service.StatusService
java:app/RQ/StatusService!com.kmware.ttk.service.StatusService
java:module/StatusService!com.kmware.ttk.service.StatusService
java:global/RQ/StatusService
java:app/RQ/StatusService
java:module/StatusService
16:16:28,077 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named GroupService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/GroupService!com.kmware.ttk.service.GroupService
java:app/RQ/GroupService!com.kmware.ttk.service.GroupService
java:module/GroupService!com.kmware.ttk.service.GroupService
java:global/RQ/GroupService
java:app/RQ/GroupService
java:module/GroupService
16:16:28,077 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named PasswordManager in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/PasswordManager!com.kmware.ttk.tickets.account.PasswordManager
java:app/RQ/PasswordManager!com.kmware.ttk.tickets.account.PasswordManager
java:module/PasswordManager!com.kmware.ttk.tickets.account.PasswordManager
java:global/RQ/PasswordManager
java:app/RQ/PasswordManager
java:module/PasswordManager
16:16:28,078 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named SubtopicWebservice in deployment unit deployment "RQ.war" are as follows:
16:16:28,079 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named DocumentService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/DocumentService!com.kmware.ttk.service.DocumentService
java:app/RQ/DocumentService!com.kmware.ttk.service.DocumentService
java:module/DocumentService!com.kmware.ttk.service.DocumentService
java:global/RQ/DocumentService
java:app/RQ/DocumentService
java:module/DocumentService
16:16:28,079 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named ReportService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/ReportService!com.kmware.ttk.service.ReportService
java:app/RQ/ReportService!com.kmware.ttk.service.ReportService
java:module/ReportService!com.kmware.ttk.service.ReportService
java:global/RQ/ReportService
java:app/RQ/ReportService
java:module/ReportService
16:16:28,080 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named ApplicationDocumentCreator in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/ApplicationDocumentCreator!com.kmware.ttk.webservices.creators.ApplicationDocumentCreator
java:app/RQ/ApplicationDocumentCreator!com.kmware.ttk.webservices.creators.ApplicationDocumentCreator
java:module/ApplicationDocumentCreator!com.kmware.ttk.webservices.creators.ApplicationDocumentCreator
java:global/RQ/ApplicationDocumentCreator
java:app/RQ/ApplicationDocumentCreator
java:module/ApplicationDocumentCreator
16:16:28,081 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named MistakeService in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/MistakeService!com.kmware.ttk.service.MistakeService
java:app/RQ/MistakeService!com.kmware.ttk.service.MistakeService
java:module/MistakeService!com.kmware.ttk.service.MistakeService
java:global/RQ/MistakeService
java:app/RQ/MistakeService
java:module/MistakeService
16:16:28,081 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named Registrar in deployment unit deployment "RQ.war" are as follows:
java:global/RQ/Registrar!com.kmware.ttk.tickets.account.Registrar
java:app/RQ/Registrar!com.kmware.ttk.tickets.account.Registrar
java:module/Registrar!com.kmware.ttk.tickets.account.Registrar
java:global/RQ/Registrar
java:app/RQ/Registrar
java:module/Registrar
16:16:28,706 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016005: Starting Services for CDI deployment: RQ.war
16:16:28,730 INFO [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900 1.1.5 (AS71)
16:16:28,820 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=CityWebservice
address=http://localhost:8080/RQ/services/CityWebservice
implementor=com.kmware.ttk.webservices.CityWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}CityWebserviceService
portName={http://webservices.ttk.kmware.com/}CityWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.CityWebservice.VIEW."com.kmware.ttk.webservices.CityWebservice".SERVICE_ENDPOINT]
16:16:28,821 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=SourceWebservice
address=http://localhost:8080/RQ/services/SourceWebservice
implementor=com.kmware.ttk.webservices.SourceWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}SourceWebserviceService
portName={http://webservices.ttk.kmware.com/}SourceWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.SourceWebservice.VIEW."com.kmware.ttk.webservices.SourceWebservice".SERVICE_ENDPOINT]
16:16:28,822 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=ApplicationDocumentWebservice
address=http://localhost:8080/RQ/services/ApplicationDocumentWebservice
implementor=com.kmware.ttk.webservices.ApplicationDocumentWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}ApplicationDocumentWebserviceService
portName={http://webservices.ttk.kmware.com/}ApplicationDocumentWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.ApplicationDocumentWebservice.VIEW."com.kmware.ttk.webservices.ApplicationDocumentWebservice".SERVICE_ENDPOINT]
16:16:28,823 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=AddressWebservice
address=http://localhost:8080/RQ/services/AddressWebservice
implementor=com.kmware.ttk.webservices.AddressWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}AddressWebserviceService
portName={http://webservices.ttk.kmware.com/}AddressWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.AddressWebservice.VIEW."com.kmware.ttk.webservices.AddressWebservice".SERVICE_ENDPOINT]
16:16:28,824 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=ServiceWebservice
address=http://localhost:8080/RQ/services/ServiceWebservice
implementor=com.kmware.ttk.webservices.ServiceWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}ServiceWebserviceService
portName={http://webservices.ttk.kmware.com/}ServiceWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.ServiceWebservice.VIEW."com.kmware.ttk.webservices.ServiceWebservice".SERVICE_ENDPOINT]
16:16:28,825 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=RequestDocumentWebservice
address=http://localhost:8080/RQ/services/RequestDocumentWebservice
implementor=com.kmware.ttk.webservices.RequestDocumentWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}RequestDocumentWebserviceService
portName={http://webservices.ttk.kmware.com/}RequestDocumentWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.RequestDocumentWebservice.VIEW."com.kmware.ttk.webservices.RequestDocumentWebservice".SERVICE_ENDPOINT]
16:16:28,826 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=SubsidiaryWebservice
address=http://localhost:8080/RQ/services/SubsidiaryWebservice
implementor=com.kmware.ttk.webservices.SubsidiaryWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}SubsidiaryWebserviceService
portName={http://webservices.ttk.kmware.com/}SubsidiaryWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.SubsidiaryWebservice.VIEW."com.kmware.ttk.webservices.SubsidiaryWebservice".SERVICE_ENDPOINT]
16:16:28,827 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=SupportTicketDocumentWebservice
address=http://localhost:8080/RQ/services/SupportTicketDocumentWebservice
implementor=com.kmware.ttk.webservices.SupportTicketDocumentWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}SupportTicketDocumentWebserviceService
portName={http://webservices.ttk.kmware.com/}SupportTicketDocumentWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.SupportTicketDocumentWebservice.VIEW."com.kmware.ttk.webservices.SupportTicketDocumentWebservice".SERVICE_ENDPOINT]
16:16:28,828 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=TopicWebservice
address=http://localhost:8080/RQ/services/TopicWebservice
implementor=com.kmware.ttk.webservices.TopicWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}TopicWebserviceService
portName={http://webservices.ttk.kmware.com/}TopicWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.TopicWebservice.VIEW."com.kmware.ttk.webservices.TopicWebservice".SERVICE_ENDPOINT]
16:16:28,829 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=PromotionWebservice
address=http://localhost:8080/RQ/services/PromotionWebservice
implementor=com.kmware.ttk.webservices.PromotionWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}PromotionWebserviceService
portName={http://webservices.ttk.kmware.com/}PromotionWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.PromotionWebservice.VIEW."com.kmware.ttk.webservices.PromotionWebservice".SERVICE_ENDPOINT]
16:16:28,830 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=AuthWebservice
address=http://localhost:8080/RQ/services/AuthWebservice
implementor=com.kmware.ttk.webservices.AuthWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}AuthWebserviceService
portName={http://webservices.ttk.kmware.com/}AuthWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.AuthWebservice.VIEW."com.kmware.ttk.webservices.AuthWebservice".SERVICE_ENDPOINT]
16:16:28,831 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=SubtopicWebservice
address=http://localhost:8080/RQ/services/SubtopicWebservice
implementor=com.kmware.ttk.webservices.SubtopicWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}SubtopicWebserviceService
portName={http://webservices.ttk.kmware.com/}SubtopicWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.SubtopicWebservice.VIEW."com.kmware.ttk.webservices.SubtopicWebservice".SERVICE_ENDPOINT]
16:16:28,832 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service
id=ConnectionTypeWebservice
address=http://localhost:8080/RQ/services/ConnectionTypeWebservice
implementor=com.kmware.ttk.webservices.ConnectionTypeWebservice
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://webservices.ttk.kmware.com/}ConnectionTypeWebserviceService
portName={http://webservices.ttk.kmware.com/}ConnectionTypeWebservicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.unit."RQ.war".component.ConnectionTypeWebservice.VIEW."com.kmware.ttk.webservices.ConnectionTypeWebservice".SERVICE_ENDPOINT]
16:16:29,085 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}CityWebserviceService from class com.kmware.ttk.webservices.CityWebservice
16:16:29,600 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/CityWebservice
16:16:29,734 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/CityWebserviceService.wsdl
16:16:29,737 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}SourceWebserviceService from class com.kmware.ttk.webservices.SourceWebservice
16:16:29,767 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/SourceWebservice
16:16:29,778 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/SourceWebserviceService.wsdl
16:16:29,779 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}ApplicationDocumentWebserviceService from class com.kmware.ttk.webservices.ApplicationDocumentWebservice
16:16:29,881 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/ApplicationDocumentWebservice
16:16:29,898 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/ApplicationDocumentWebserviceService.wsdl
16:16:29,900 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}AddressWebserviceService from class com.kmware.ttk.webservices.AddressWebservice
16:16:29,936 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/AddressWebservice
16:16:29,946 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/AddressWebserviceService.wsdl
16:16:29,947 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}ServiceWebserviceService from class com.kmware.ttk.webservices.ServiceWebservice
16:16:29,969 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/ServiceWebservice
16:16:29,976 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/ServiceWebserviceService.wsdl
16:16:29,977 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}RequestDocumentWebserviceService from class com.kmware.ttk.webservices.RequestDocumentWebservice
16:16:30,033 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/RequestDocumentWebservice
16:16:30,041 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/RequestDocumentWebserviceService.wsdl
16:16:30,043 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}SubsidiaryWebserviceService from class com.kmware.ttk.webservices.SubsidiaryWebservice
16:16:30,064 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/SubsidiaryWebservice
16:16:30,070 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/SubsidiaryWebserviceService.wsdl
16:16:30,071 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}SupportTicketDocumentWebserviceService from class com.kmware.ttk.webservices.SupportTicketDocumentWebservice
16:16:30,464 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/SupportTicketDocumentWebservice
16:16:30,879 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/SupportTicketDocumentWebserviceService.wsdl
16:16:30,880 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}TopicWebserviceService from class com.kmware.ttk.webservices.TopicWebservice
16:16:30,899 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/TopicWebservice
16:16:30,904 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/TopicWebserviceService.wsdl
16:16:30,905 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}PromotionWebserviceService from class com.kmware.ttk.webservices.PromotionWebservice
16:16:30,922 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/PromotionWebservice
16:16:30,927 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/PromotionWebserviceService.wsdl
16:16:30,927 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}AuthWebserviceService from class com.kmware.ttk.webservices.AuthWebservice
16:16:30,951 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/AuthWebservice
16:16:30,956 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/AuthWebserviceService.wsdl
16:16:30,957 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}SubtopicWebserviceService from class com.kmware.ttk.webservices.SubtopicWebservice
16:16:31,235 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/SubtopicWebservice
16:16:31,241 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/SubtopicWebserviceService.wsdl
16:16:31,242 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://webservices.ttk.kmware.com/}ConnectionTypeWebserviceService from class com.kmware.ttk.webservices.ConnectionTypeWebservice
16:16:31,259 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/RQ/services/ConnectionTypeWebservice
16:16:31,263 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/opt/jboss-as-7.1.1.Final/standalone/data/wsdl/RQ.war/ConnectionTypeWebserviceService.wsdl
16:16:31,266 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015539: Starting service jboss.ws.port-component-link
16:16:31,279 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".CityWebservice
16:16:31,281 INFO [org.jboss.as.webservices] (MSC service thread 1-7) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".ServiceWebservice
16:16:31,282 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-7) register: jboss.ws:context=RQ,endpoint=ServiceWebservice
16:16:31,282 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-3) register: jboss.ws:context=RQ,endpoint=CityWebservice
16:16:31,289 INFO [org.jboss.as.webservices] (MSC service thread 1-6) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".ConnectionTypeWebservice
16:16:31,290 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".AuthWebservice
16:16:31,290 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) register: jboss.ws:context=RQ,endpoint=AuthWebservice
16:16:31,291 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".ApplicationDocumentWebservice
16:16:31,291 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) register: jboss.ws:context=RQ,endpoint=ApplicationDocumentWebservice
16:16:31,291 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".AddressWebservice
16:16:31,292 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) register: jboss.ws:context=RQ,endpoint=AddressWebservice
16:16:31,292 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".SourceWebservice
16:16:31,292 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) register: jboss.ws:context=RQ,endpoint=SourceWebservice
16:16:31,293 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".SubsidiaryWebservice
16:16:31,293 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) register: jboss.ws:context=RQ,endpoint=SubsidiaryWebservice
16:16:31,294 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".SupportTicketDocumentWebservice
16:16:31,294 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) register: jboss.ws:context=RQ,endpoint=SupportTicketDocumentWebservice
16:16:31,299 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".PromotionWebservice
16:16:31,295 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-6) register: jboss.ws:context=RQ,endpoint=ConnectionTypeWebservice
16:16:31,300 INFO [org.jboss.as.webservices] (MSC service thread 1-6) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".RequestDocumentWebservice
16:16:31,295 INFO [org.jboss.as.webservices] (MSC service thread 1-8) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".SubtopicWebservice
16:16:31,295 INFO [org.jboss.as.webservices] (MSC service thread 1-5) JBAS015539: Starting service jboss.ws.endpoint."RQ.war".TopicWebservice
16:16:31,302 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-8) register: jboss.ws:context=RQ,endpoint=SubtopicWebservice
16:16:31,301 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-3) register: jboss.ws:context=RQ,endpoint=PromotionWebservice
16:16:31,302 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-5) register: jboss.ws:context=RQ,endpoint=TopicWebservice
16:16:31,303 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-6) register: jboss.ws:context=RQ,endpoint=RequestDocumentWebservice
16:16:31,306 TRACE [org.jboss.security.util.state.StateMachine] (MSC service thread 1-1) nextState(getPolicyConfiguration) = State(name=open
on: addToExcludedPolicy go to: open
on: inService go to: open
on: getContextID go to: open
on: removeExcludedPolicy go to: open
on: commit go to: inService
on: removeRole go to: open
on: addToUncheckedPolicy go to: open
on: delete go to: deleted
on: getPolicyConfiguration go to: open
on: addToRole go to: open
on: linkConfiguration go to: open
on: removeUncheckedPolicy go to: open)
16:16:31,307 TRACE [org.jboss.security.jacc.JBossPolicyConfiguration] (MSC service thread 1-1) ctor, contextID=RQ.war
16:16:31,310 TRACE [org.jboss.security.util.state.StateMachine] (MSC service thread 1-1) nextState(getPolicyConfiguration) = State(name=open
on: addToExcludedPolicy go to: open
on: inService go to: open
on: getContextID go to: open
on: removeExcludedPolicy go to: open
on: commit go to: inService
on: removeRole go to: open
on: addToUncheckedPolicy go to: open
on: delete go to: deleted
on: getPolicyConfiguration go to: open
on: addToRole go to: open
on: linkConfiguration go to: open
on: removeUncheckedPolicy go to: open)
16:16:31,316 TRACE [org.jboss.security.jacc.JBossPolicyConfiguration] (MSC service thread 1-1) commit:RQ.war
16:16:31,325 TRACE [org.jboss.security.util.state.StateMachine] (MSC service thread 1-1) nextState(commit) = State(name=inService
on: getContextID go to: inService
on: inService go to: inService
on: delete go to: deleted
on: getPolicyConfiguration go to: open)
16:16:31,612 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS015870: Deploy of deployment "RQ.war" was rolled back with failure message JBAS014750: Operation handler failed to complete
16:16:31,659 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".ServiceWebservice
16:16:31,659 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=RQ,endpoint=ServiceWebservice
16:16:31,660 INFO [org.jboss.as.webservices] (MSC service thread 1-7) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".ApplicationDocumentWebservice
16:16:31,660 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-7) remove: jboss.ws:context=RQ,endpoint=ApplicationDocumentWebservice
16:16:31,660 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".AddressWebservice
16:16:31,660 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-4) remove: jboss.ws:context=RQ,endpoint=AddressWebservice
16:16:31,659 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".CityWebservice
16:16:31,668 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-3) remove: jboss.ws:context=RQ,endpoint=CityWebservice
16:16:31,668 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".SourceWebservice
16:16:31,668 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-3) remove: jboss.ws:context=RQ,endpoint=SourceWebservice
16:16:31,669 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".SubsidiaryWebservice
16:16:31,669 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) remove: jboss.ws:context=RQ,endpoint=SubsidiaryWebservice
16:16:31,671 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".PromotionWebservice
16:16:31,671 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-3) remove: jboss.ws:context=RQ,endpoint=PromotionWebservice
16:16:31,669 TRACE [org.jboss.security.util.state.StateMachine] (MSC service thread 1-6) nextState(getPolicyConfiguration) = State(name=open
on: addToExcludedPolicy go to: open
on: inService go to: open
on: getContextID go to: open
on: removeExcludedPolicy go to: open
on: commit go to: inService
on: removeRole go to: open
on: addToUncheckedPolicy go to: open
on: delete go to: deleted
on: getPolicyConfiguration go to: open
on: addToRole go to: open
on: linkConfiguration go to: open
on: removeUncheckedPolicy go to: open)
16:16:31,659 INFO [org.jboss.as.webservices] (MSC service thread 1-8) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".AuthWebservice
16:16:31,659 INFO [org.jboss.as.webservices] (MSC service thread 1-5) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".ConnectionTypeWebservice
16:16:31,679 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-5) remove: jboss.ws:context=RQ,endpoint=ConnectionTypeWebservice
16:16:31,674 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-8) remove: jboss.ws:context=RQ,endpoint=AuthWebservice
16:16:31,672 TRACE [org.jboss.security.jacc.JBossPolicyConfiguration] (MSC service thread 1-6) delete:RQ.war
16:16:31,671 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".RequestDocumentWebservice
16:16:31,680 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) remove: jboss.ws:context=RQ,endpoint=RequestDocumentWebservice
16:16:31,669 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".SubtopicWebservice
16:16:31,669 INFO [org.jboss.as.webservices] (MSC service thread 1-7) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".TopicWebservice
16:16:31,669 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."RQ.war".SupportTicketDocumentWebservice
16:16:31,681 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-7) remove: jboss.ws:context=RQ,endpoint=TopicWebservice
16:16:31,681 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-4) remove: jboss.ws:context=RQ,endpoint=SubtopicWebservice
16:16:31,680 TRACE [org.jboss.security.util.state.StateMachine] (MSC service thread 1-6) nextState(delete) = State(name=deleted
on: inService go to: deleted
on: getContextID go to: deleted
on: delete go to: deleted
on: getPolicyConfiguration go to: open)
16:16:31,681 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=RQ,endpoint=SupportTicketDocumentWebservice
16:16:31,692 INFO [org.jboss.as.webservices] (MSC service thread 1-7) JBAS015540: Stopping service jboss.ws.port-component-link
16:16:31,859 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment RQ.war in 247ms