[JBoss Transactions Development] - Re: Transactional MSC
by Tom Jenkinson
Tom Jenkinson [https://community.jboss.org/people/tomjenkinson] created the discussion
"Re: Transactional MSC"
To view the discussion, visit: https://community.jboss.org/message/828591#828591
--------------------------------------------------------------
I think this:
[Q] Does it matter if the object store contains transaction logs for both Transacional MSC and applications?
Should be:
[Q] Can the ObjectStore that the application user configures be used by the MSC?
[Q] Must the transaction/recovery manager allow separate object stores to be configured?
[Q] When using the CLI to browse the object store to resolve transactions manually, must the MSC and application txs both be visible?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/828591#828591]
Start a new discussion in JBoss Transactions Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
- 1
- 0
[JBoss Transactions Development] - Transactional MSC
by Paul Robinson
Paul Robinson [https://community.jboss.org/people/paul.robinson] created the discussion
"Transactional MSC"
To view the discussion, visit: https://community.jboss.org/message/828391#828391
--------------------------------------------------------------
WARNING: THIS IS NOT READY FOR REVIEW YET!!
I WILL REMOVE THIS TEXT AND SEND ROUND AN EMAIL, WHEN IT IS READY.
h1. Introduction
This discussion covers the "Transactional MSC" feature scheduled for a future release of WildFly. Although the feature is discussed in general, the focus of this document is to establish the requirements from Narayana and to discuss implementation details.
h1. What is "Transactional MSC"?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/828391#828391]
Start a new discussion in JBoss Transactions Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
- 1
- 0
[JBoss Web Services Development] - HANDLER_RAISED_RUNTIME_EXCEPTION: java.lang.NullPointerException
by Anu Raj
Anu Raj [https://community.jboss.org/people/mpag1980] created the discussion
"HANDLER_RAISED_RUNTIME_EXCEPTION: java.lang.NullPointerException"
To view the discussion, visit: https://community.jboss.org/message/828310#828310
--------------------------------------------------------------
WARNING [org.apache.cxf.jaxws.handler.HandlerChainInvoker] (http-/127.0.0.1:7080-1) HANDLER_RAISED_RUNTIME_EXCEPTION: java.lang.NullPointerException
g.picketlink.identity.federation.core.wstrust.handlers.STSSecurityHandler.createSTSClient(STSSecurityHandler.java:311) [picketlink-core-2.1.5-2012Sep04.jar:2.1.5-2012Sep04]
g.picketlink.identity.federation.core.wstrust.handlers.STSSecurityHandler.handleMessage(STSSecurityHandler.java:189) [picketlink-core-2.1.5-2012Sep04.jar:2.1.5-2012Sep04]
g.picketlink.identity.federation.core.wstrust.handlers.STSSecurityHandler.handleMessage(STSSecurityHandler.java:120) [picketlink-core-2.1.5-2012Sep04.jar:2.1.5-2012Sep04]
g.apache.cxf.jaxws.handler.HandlerChainInvoker.invokeHandleMessage(HandlerChainInvoker.java:335) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.jaxws.handler.HandlerChainInvoker.invokeHandlerChain(HandlerChainInvoker.java:253) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.jaxws.handler.HandlerChainInvoker.invokeProtocolHandlers(HandlerChainInvoker.java:131) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessageInternal(SOAPHandlerInterceptor.java:168) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:123) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:70) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:207) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:209) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:191) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:114) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:185) [cxf-2.4.6.jar:2.4.6]
g.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:108) [cxf-2.4.6.jar:2.4.6]
vax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
g.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:164) [cxf-2.4.6.jar:2.4.6]
g.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
g.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
g.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
g.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
g.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
g.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
g.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
g.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
g.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
g.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
g.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
g.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
va.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
I am trying to access my service hosted in Jboss EAP 6.1 and I am getting the above exception. I am using handlerchain annotation at the service level.
In one of the forum, I saw this issue occurs due to apache CXF SAAJ version and Jboss SAAJ version does not match.
I am using Apache CXF 2.7.5 stack.
Can anybody help me out.
Thanks,
Abarna
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/828310#828310]
Start a new discussion in JBoss Web Services Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
- 1
- 0
[JBoss Web Services Development] - Upgrade jbossws-common spec api dependencies to latest version ?
by Lin Gao
Lin Gao [https://community.jboss.org/people/gaol] created the discussion
"Upgrade jbossws-common spec api dependencies to latest version ?"
To view the discussion, visit: https://community.jboss.org/message/828146#828146
--------------------------------------------------------------
There are several dependencies in jbossws-common project, which has some JavaEE spec api dependencies that is NOT latest version:
1. jboss-ejb-api_3.1_spec
<ejb.api.version>1.0.0.CR2</ejb.api.version>
<dependency>
<groupId>org.jboss.spec.javax.ejb</groupId>
<artifactId>jboss-ejb-api_3.1_spec</artifactId>
<version>${ejb.api.version}</version>
<scope>provided</scope>
</dependency>
The latest version of this spec api is: 1.0.2.Final
2. jboss-jms-api_1.1_spec
<jms.api.version>1.0.0.Final</jms.api.version>
<dependency>
<groupId>org.jboss.spec.javax.jms</groupId>
<artifactId>jboss-jms-api_1.1_spec</artifactId>
<version>${jms.api.version}</version>
<scope>provided</scope>
</dependency>
The latest version of this spec api is: 1.0.1.Final
3. jboss-servlet-api_3.0_spec
<servlet.api.version>1.0.0.Final</servlet.api.version>
<dependency>
<groupId>org.jboss.spec.javax.servlet</groupId>
<artifactId>jboss-servlet-api_3.0_spec</artifactId>
<version>${servlet.api.version}</version>
<scope>provided</scope>
</dependency>
The latest version of this spec api is: 1.0.2.Final
4. jboss-jaxws-api_2.2_spec
<jaxws.api.version>1.0.0.Final</jaxws.api.version>
<dependency>
<groupId>org.jboss.spec.javax.xml.ws</groupId>
<artifactId>jboss-jaxws-api_2.2_spec</artifactId>
<version>${jaxws.api.version}</version>
</dependency>
The latest version of this spec api is: 2.0.1.Final
Upgrades these spec dependency versions can align the version with jboss as dependencies and unique scope definition of the JavaEE spec api dependencies, which uses 'provided'.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/828146#828146]
Start a new discussion in JBoss Web Services Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
- 2
- 1
[JBoss AS 7 Development] - security interceptor no access to ejb
by ich selbst
ich selbst [https://community.jboss.org/people/gris12] created the discussion
"security interceptor no access to ejb"
To view the discussion, visit: https://community.jboss.org/message/828132#828132
--------------------------------------------------------------
Hi
i'm currently new to Jboss development. I have implemented some REST services and now I want to secure them. I have implemented a SecurityInterceptor, but my problem is, I can't access my EJB's in this class.
Here ist the code of the interceptor:
@EJB
KryptoManager kryptoManager;
@Override
public boolean accept(Class c, Method method) {
if (c == null || method == null) return false;
//class implementing rest service
return method.getName().equals("restService");
}
@Override
public ServerResponse preProcess(HttpRequest request, ResourceMethod method)
throws Failure, WebApplicationException {
ServerResponse response = null;
String key = kryptoManager.getKryptoInformation();
...
if (error) {
response = new ServerResponse(LOGINURL, 403, new Headers<Object>());
}
return response;
}
The kryptoManager always is null. I also used this method to access bean Information in a servlet and a REST service, were it is working fine. The bean access the database info and delivers them to the controlers, but in securityinterceptor this is not working, why?
Here is the rest my classes:
The KryptoManager looks like:
@Stateless
public class KryptoManager {
@EJB
private KryptoDAO kryptoDAO;
public KryptoBean getKryptoInformation() {
return kryptoDAO.getKryptoInformation();
}
}
@Stateless
public class KryptoDAO {
@PersistenceContext(unitName = "adb", type = PersistenceContextType.TRANSACTION)
private EntityManager entityManager;
public KryptoBean getKryptoInformation() {
Query query = entityManager.createQuery("SELECT k FROM KryptoBean k");
return (KryptoBean) query.getResultList().get(0);
}
}
And the Bean Class looks like:
@XmlRootElement
@Table(name = "krypto")
@Entity(name = "KryptoBean")
public class KryptoBean {
@Id
@Column(name = "idkrypto")
private int idkrypto;
@Column (name = "hmackey")
private String hmackey;
public int getIdkrypto() {
return idkrypto;
}
public void setIdkrypto(int idkrypto) {
this.idkrypto = idkrypto;
}
public String getHmackey() {
return hmackey;
}
public void setHmackey(String hmackey) {
this.hmackey = hmackey;
}
}
And the JaxRsActivator looks like:
@ApplicationPath( "/rest" )
public class JaxRsActivator extends Application
{
@Override
public Set<Class<?>> getClasses() {
// TODO Auto-generated method stub
return super.getClasses();
}
@Override
public Set<Object> getSingletons() {
// TODO Auto-generated method stub
return super.getSingletons();
}
}
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/828132#828132]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
- 1
- 0
[JBoss AS 7 Development] - Re: Issue using RESTeasy 3.0.1 in JBoss AS 7.1.1
by Tomaz Cerar
Tomaz Cerar [https://community.jboss.org/people/ctomc] created the discussion
"Re: Issue using RESTeasy 3.0.1 in JBoss AS 7.1.1"
To view the discussion, visit: https://community.jboss.org/message/827539#827539
--------------------------------------------------------------
You can try with WildFly 8 alpha2 which has RESTEasy 3.0.1 already bundled.
Oterwise did you folow docs about upgrading RestEasy in AS7 http://docs.jboss.org/resteasy/docs/3.0.1.Final/userguide/html_single/ind... http://docs.jboss.org/resteasy/docs/3.0.1.Final/userguide/html_single/ind...
there are modules provided in distribution that you should put in your AS7 modules directory...
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/827539#827539]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
- 2
- 2
[JBoss AS 7 Development] - JBoss 7.1.1 Deployment Failure on Bizagi BPM Suite
by Morty S
Morty S [https://community.jboss.org/people/boogiejack] created the discussion
"JBoss 7.1.1 Deployment Failure on Bizagi BPM Suite"
To view the discussion, visit: https://community.jboss.org/message/827490#827490
--------------------------------------------------------------
Good day
I'd appreciate any help or leads to solve this problem.
I am trying to publish a process using Bizagi (a BPM Suite), which comes bundled with JBoss 7.1.1. Under the deployment folder there is a +*BizAgi-ear-JBoss.ear*+ file that I suppose should be deployed. When I publish the process from within Bizagi, the .ear file is also deployed, but ends up as *+BizAgi-ear-JBoss.ear.failed+* , and displays the following message:*+
+*
And the log from the Server is:
10:42:43,663 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final
10:42:44,443 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
10:42:44,646 INFO [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
10:42:44,880 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]
10:42:46,580 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 3.0)
10:42:46,627 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--0.0.0.0-8080
10:42:48,203 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 11.1)
10:42:48,827 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) JBAS010403: Deploying JDBC-compliant driver class bizagi.jdbc.BizAgiDriver (version 1.0)
10:42:50,075 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingjournal,bindingsDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messaginglargemessages,pagingDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingpaging)
10:42:51,136 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:61613 for STOMP protocol
10:42:51,151 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5455 for CORE protocol
10:42:51,167 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5445 for CORE protocol
10:42:51,198 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) Server is now live
10:42:51,198 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [cdb8d2aa-e9aa-11e2-90a4-001d92219e28]) started
10:42:51,229 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) trying to deploy queue jms.queue.testQueue
10:42:51,715 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
10:42:51,840 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/queue/test
10:42:52,027 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
10:42:52,043 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
10:42:52,043 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/AsyncControllerFactory
10:42:52,059 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) trying to deploy queue jms.topic.testTopic
10:42:52,199 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/topic/test
10:42:52,230 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) trying to deploy queue jms.queue.AsyncController
10:42:52,230 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/jms/AsyncController
10:42:52,339 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:/BizAgiJava]
10:42:52,339 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA
10:42:52,371 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-2) HornetQ resource adaptor started
10:42:52,371 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra
10:42:52,386 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
10:42:52,885 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\deployments
10:42:52,917 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /0.0.0.0:9999
10:42:52,901 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment BizAgi-ear-JBoss.ear
10:42:52,917 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 0.0.0.0/0.0.0.0:4447
10:42:53,815 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "BizAgi-ear-JBoss.ear"
10:43:52,971 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
10:43:52,971 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "BizAgi-ear-JBoss.ear" was rolled back with failure message Operation cancelled
10:44:09,289 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "BizAgi-ejb.jar"
10:44:09,289 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "BizAgiScheduler-9.0.8.jar"
10:44:09,305 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "BizAgi-war.war"
10:44:09,305 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry Generated.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-ejb.jar" does not point to a valid jar for a Class-Path reference.
10:44:12,627 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BizAgi-ejb.jar in 3323ms
10:44:12,659 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry Generated.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,659 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry opensaml-1.0.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,659 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry wsdl4j-1.6.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,659 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry wss4j-1.5.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,674 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-digester-1.6.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,674 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-beanutils-1.8.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,674 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-collections-2.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,690 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-discovery-0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,690 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry axis-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,690 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry servlet-api-2.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,690 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry build-tools-1.0.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,705 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry velocity-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,705 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry velocity-dep-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,705 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry tomahawk-1.1.9.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,705 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-validator-1.3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,705 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-el-1.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,721 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry oro-2.0.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,721 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-lang-2.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,721 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry batik-awt-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,721 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry batik-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,721 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry batik-gui-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,737 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry batik-ext-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,737 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry itext-1.4.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,737 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry WorkPortalServices-9.1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,737 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jmimemagic-0.1.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,737 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry xmlParserAPIs-2.0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,752 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jersey-server-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,752 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry asm-3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,752 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jersey-core-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,752 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jsr311-api-1.1.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,768 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jersey-multipart-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,768 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry mimepull-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,768 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jersey-client-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:44:12,815 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment BizAgiScheduler-9.0.8.jar in 3516ms
10:44:19,023 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BizAgi-war.war in 9727ms
10:44:19,195 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BizAgi-ear-JBoss.ear in 26220ms
10:48:07,190 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:/queue/test
10:48:07,208 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011605: Unbound messaging object to jndi name java:/RemoteConnectionFactory
10:48:07,211 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011942: Stopping OSGi Framework
10:48:07,215 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory
10:48:07,218 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011605: Unbound messaging object to jndi name java:/AsyncControllerFactory
10:48:26,386 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
10:48:26,574 INFO [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
10:48:26,835 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.2.GA
10:48:27,355 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 3.0)
10:48:27,368 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
10:48:27,834 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-0.0.0.0-0.0.0.0-8080
10:48:28,030 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 11.1)
10:48:28,051 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class bizagi.jdbc.BizAgiDriver (version 1.0)
10:48:28,505 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\deployments
10:48:28,684 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 0.0.0.0/0.0.0.0:4447
10:48:28,699 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /0.0.0.0:9999
10:48:28,892 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/BizAgiJava]
10:48:28,963 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingjournal,bindingsDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messaginglargemessages,pagingDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingpaging)
10:48:29,208 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-3) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:61613 for STOMP protocol
10:48:29,217 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-3) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5445 for CORE protocol
10:48:29,226 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-3) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5455 for CORE protocol
10:48:29,232 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) Server is now live
10:48:29,235 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [a8525f7d-ea06-11e2-8bd6-001d92219e28]) started
10:48:29,244 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) trying to deploy queue jms.queue.testQueue
10:48:29,383 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/queue/test
10:48:29,415 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/AsyncControllerFactory
10:48:29,419 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) trying to deploy queue jms.topic.testTopic
10:48:29,478 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/topic/test
10:48:29,483 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
10:48:29,488 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
10:48:29,491 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) trying to deploy queue jms.queue.AsyncController
10:48:29,499 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/jms/AsyncController
10:48:29,593 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA
10:48:29,626 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-1) HornetQ resource adaptor started
10:48:29,629 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra
10:48:29,635 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
10:48:29,915 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
10:48:29,919 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 10236ms - Started 157 of 234 services (76 services are passive or on-demand)
10:48:33,608 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015009: Scan found incompletely copied file content for deployment C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\deployments\BizAgi-ear-JBoss.ear. Deployment changes will not be processed until all content is complete.
10:48:35,220 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "BizAgi-ear-JBoss.ear"
10:49:35,047 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
10:49:35,048 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "BizAgi-ear-JBoss.ear" was rolled back with failure message Operation cancelled
10:49:39,124 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "BizAgi-ejb.jar"
10:49:39,127 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "BizAgiScheduler-9.0.8.jar"
10:49:39,128 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "BizAgi-war.war"
10:49:39,169 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment BizAgiScheduler-9.0.8.jar in 21ms
10:49:42,348 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BizAgi-ejb.jar in 3219ms
10:49:44,384 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry opensaml-1.0.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,392 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry wsdl4j-1.6.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,399 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry wss4j-1.5.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,404 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-digester-1.6.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,409 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-beanutils-1.8.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,414 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-collections-2.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,419 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-discovery-0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,424 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry axis-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,429 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry servlet-api-2.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,435 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry build-tools-1.0.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,440 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry velocity-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,445 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry velocity-dep-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,450 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry tomahawk-1.1.9.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,455 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-validator-1.3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,461 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-el-1.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry oro-2.0.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,470 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry commons-lang-2.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,475 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry batik-awt-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,480 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry batik-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,485 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry batik-gui-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,491 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry batik-ext-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,496 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry itext-1.4.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,501 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry WorkPortalServices-9.1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,506 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jmimemagic-0.1.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,511 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xmlParserAPIs-2.0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,516 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jersey-server-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,521 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry asm-3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,526 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jersey-core-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,531 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jsr311-api-1.1.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,537 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jersey-multipart-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,542 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry mimepull-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:44,547 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jersey-client-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:49:55,978 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011605: Unbound messaging object to jndi name java:/queue/test
10:49:56,073 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/RemoteConnectionFactory
10:49:56,083 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory
10:49:56,087 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/AsyncControllerFactory
10:50:11,751 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
10:50:11,889 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
10:50:12,481 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.7.Final
10:50:12,766 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 3.0)
10:50:13,228 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 11.1)
10:50:13,248 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class bizagi.jdbc.BizAgiDriver (version 1.0)
10:50:13,626 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
10:50:13,792 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--0.0.0.0-8080
10:50:14,783 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:/BizAgiJava]
10:50:14,877 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\deployments
10:50:14,930 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 0.0.0.0/0.0.0.0:4447
10:50:14,930 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /0.0.0.0:9999
10:50:14,990 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingjournal,bindingsDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messaginglargemessages,pagingDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingpaging)
10:50:15,330 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5455 for CORE protocol
10:50:15,336 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5445 for CORE protocol
10:50:15,346 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:61613 for STOMP protocol
10:50:15,353 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) Server is now live
10:50:15,360 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [e786cb0a-ea06-11e2-8e59-001d92219e28]) started
10:50:15,373 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) trying to deploy queue jms.queue.AsyncController
10:50:15,502 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/jms/AsyncController
10:50:15,539 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
10:50:15,544 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/AsyncControllerFactory
10:50:15,548 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) trying to deploy queue jms.queue.testQueue
10:50:15,566 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/queue/test
10:50:15,572 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
10:50:15,585 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) trying to deploy queue jms.topic.testTopic
10:50:15,712 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-3) JBAS010406: Registered connection factory java:/JmsXA
10:50:15,757 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/topic/test
10:50:15,769 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-3) HornetQ resource adaptor started
10:50:15,781 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatorhornetq-ra
10:50:15,788 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-3) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
10:50:16,094 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
10:50:16,097 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 11046ms - Started 157 of 234 services (76 services are passive or on-demand)
10:50:20,528 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "BizAgi-ear-JBoss.ear"
10:51:13,401 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "BizAgi-war.war"
10:51:13,404 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "BizAgi-ejb.jar"
10:51:13,409 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "BizAgiScheduler-9.0.8.jar"
10:51:17,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry opensaml-1.0.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,471 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry wsdl4j-1.6.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,476 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry wss4j-1.5.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,481 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-digester-1.6.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,486 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-beanutils-1.8.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,491 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-collections-2.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,496 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-discovery-0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,502 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry axis-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,506 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry servlet-api-2.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,511 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry build-tools-1.0.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,516 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry velocity-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,521 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry velocity-dep-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,526 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry tomahawk-1.1.9.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,532 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-validator-1.3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,537 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-el-1.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,544 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry oro-2.0.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,549 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-lang-2.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,554 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry batik-awt-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,559 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry batik-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,564 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry batik-gui-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,569 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry batik-ext-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,574 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry itext-1.4.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,579 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry WorkPortalServices-9.1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,584 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jmimemagic-0.1.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,589 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xmlParserAPIs-2.0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,594 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jersey-server-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,599 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry asm-3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,604 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jersey-core-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,609 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jsr311-api-1.1.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,614 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jersey-multipart-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,619 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry mimepull-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:17,624 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jersey-client-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:51:18,557 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,563 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,570 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,576 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,582 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,588 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,593 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,599 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,611 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,635 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,680 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,685 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,690 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,695 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,700 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
10:51:18,707 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
10:51:18,732 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'
10:51:18,740 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
10:51:18,741 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
10:51:18,741 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'
10:51:18,741 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
10:51:18,756 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'
10:51:18,756 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'
10:51:18,756 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'
10:51:18,772 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for service type 'javax.ws.rs.ext.MessageBodyWriter'
10:51:18,803 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromStringEnum' for service type 'com.sun.jersey.spi.StringReaderProvider'
10:51:18,834 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeValueOf' for service type 'com.sun.jersey.spi.StringReaderProvider'
10:51:18,834 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromString' for service type 'com.sun.jersey.spi.StringReaderProvider'
10:51:18,850 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$StringConstructor' for service type 'com.sun.jersey.spi.StringReaderProvider'
10:51:18,850 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$DateProvider' for service type 'com.sun.jersey.spi.StringReaderProvider'
10:51:18,850 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.JAXBStringReaderProviders$RootElementProvider' for service type 'com.sun.jersey.spi.StringReaderProvider'
10:51:18,819 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
10:51:18,912 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
10:51:18,975 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for BizAgi.RenderPU
10:51:18,975 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for BizAgi.EntitiesPU
10:51:20,503 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "BizAgi-ear-JBoss.ear" was rolled back with failure message Operation cancelled
10:51:20,503 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
10:51:20,909 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BizAgi-ejb.jar in 156ms
10:51:20,909 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment BizAgiScheduler-9.0.8.jar in 160ms
10:51:32,609 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment BizAgi-war.war in 11864ms
10:51:32,937 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment BizAgi-ear-JBoss.ear in 12192ms
10:51:34,200 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:/RemoteConnectionFactory
10:51:34,200 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011942: Stopping OSGi Framework
10:51:34,200 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory
10:51:34,216 WARN [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
10:51:34,216 WARN [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
10:51:34,216 WARN [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
10:51:34,216 WARN [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
10:51:34,231 WARN [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
10:51:34,231 WARN [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
10:51:34,231 WARN [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
10:51:34,231 WARN [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
10:51:34,247 WARN [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
10:51:34,247 WARN [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
10:51:34,247 WARN [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
10:51:34,247 WARN [org.jboss.remoting.remote] (Remoting "microteckbpm-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
10:51:34,263 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011605: Unbound messaging object to jndi name java:/jms/AsyncController
10:51:34,278 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011605: Unbound messaging object to jndi name java:/topic/test
10:51:34,294 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/queue/test
10:51:34,309 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:/AsyncControllerFactory
10:51:48,583 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
10:51:48,537 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final
10:51:49,223 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
10:51:50,253 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 3.0)
10:51:50,721 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 11.1)
10:51:50,736 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class bizagi.jdbc.BizAgiDriver (version 1.0)
10:51:50,752 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
10:51:51,516 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-0.0.0.0-0.0.0.0-8080
10:51:51,672 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingjournal,bindingsDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messaginglargemessages,pagingDirectory=C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\data\messagingpaging)
10:51:52,281 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5445 for CORE protocol
10:51:52,327 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:5455 for CORE protocol
10:51:52,327 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:61613 for STOMP protocol
10:51:52,327 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) Server is now live
10:51:52,343 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [21248c49-ea07-11e2-916d-001d92219e28]) started
10:51:52,374 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/BizAgiJava]
10:51:52,437 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
10:51:52,483 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/AsyncControllerFactory
10:51:52,499 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) trying to deploy queue jms.queue.AsyncController
10:51:52,686 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/jms/AsyncController
10:51:52,686 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
10:51:52,717 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) trying to deploy queue jms.queue.testQueue
10:51:52,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/queue/test
10:51:52,764 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-2) trying to deploy queue jms.topic.testTopic
10:51:52,780 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory C:\BizagiJEE\jboss-as-7.1.1.Final\standalone\deployments
10:51:52,827 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:/topic/test
10:51:52,858 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA
10:51:52,920 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /0.0.0.0:9999
10:51:52,920 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-1) HornetQ resource adaptor started
10:51:52,920 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 0.0.0.0/0.0.0.0:4447
10:51:52,920 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra
10:51:52,936 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
10:51:53,263 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
10:51:53,263 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 10857ms - Started 157 of 234 services (76 services are passive or on-demand)
10:51:57,850 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "BizAgi-ear-JBoss.ear"
10:52:57,827 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
10:52:57,852 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "BizAgi-ear-JBoss.ear" was rolled back with failure message Operation cancelled
10:53:12,248 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "BizAgi-war.war"
10:53:12,252 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "BizAgi-ejb.jar"
10:53:12,253 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "BizAgiScheduler-9.0.8.jar"
10:53:15,931 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment BizAgi-ejb.jar in 3670ms
10:53:15,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment BizAgiScheduler-9.0.8.jar in 3681ms
10:53:16,667 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry opensaml-1.0.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,672 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry wsdl4j-1.6.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,678 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry wss4j-1.5.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,683 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-digester-1.6.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,689 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-beanutils-1.8.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,695 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-collections-2.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,701 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-discovery-0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry axis-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,715 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry servlet-api-2.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,720 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry build-tools-1.0.5.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,726 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry velocity-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,731 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry velocity-dep-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,736 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry tomahawk-1.1.9.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,741 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-validator-1.3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,747 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-el-1.0.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,752 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry oro-2.0.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,757 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry commons-lang-2.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry batik-awt-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,767 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry batik-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,772 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry batik-gui-util-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,777 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry batik-ext-1.6-1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,783 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry itext-1.4.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,788 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry WorkPortalServices-9.1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,793 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jmimemagic-0.1.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,798 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry xmlParserAPIs-2.0.2.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,803 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jersey-server-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,808 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry asm-3.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,813 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jersey-core-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,818 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jsr311-api-1.1.1.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,823 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jersey-multipart-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,828 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry mimepull-1.4.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:16,833 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jersey-client-1.8.jar in "/C:/BizagiJEE/jboss-as-7.1.1.Final/bin/content/BizAgi-ear-JBoss.ear/BizAgi-war.war" does not point to a valid jar for a Class-Path reference.
10:53:22,629 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment BizAgi-war.war in 10370ms
10:53:22,787 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BizAgi-ear-JBoss.ear in 24927ms
Can someone please guide me on what possible problems could be, I am not an expert in JBoss...
Further information:
I am running the latest Java version 7, update 25, on a Windows 7 Enterprise machine.
Thanks in advance
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/827490#827490]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
- 2
- 1
[jBPM Development] - How to stop NioProcessor-2 logging. [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
by uvijayreddy657
uvijayreddy657 [https://community.jboss.org/people/uvijayreddy657] created the discussion
"How to stop NioProcessor-2 logging. [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE"
To view the discussion, visit: https://community.jboss.org/message/715135#715135
--------------------------------------------------------------
In JBoss server always for every second the below is scrolling continuously. Because of this *server.log size is increasing till 400MB to 500MB*. Getting disk out of space error and also getting *java.net.SocketException : Too many open files.*
*How to stop this LoggingFilter.* Please suggest and advice.
2012-02-08 11:59:13,309 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:13,309 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:14,262 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:14,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:15,277 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,262 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,280 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,280 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,280 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:22,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:22,264 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:23,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:23,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:25,266 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:25,283 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:25,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/715135#715135]
Start a new discussion in jBPM Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
- 3
- 2
[JBoss AS 7 Development] - Re: No suitable driver found for jdbc:mysql://localhost:3306/test
by Mario Torre
Mario Torre [https://community.jboss.org/people/mtorre] created the discussion
"Re: No suitable driver found for jdbc:mysql://localhost:3306/test"
To view the discussion, visit: https://community.jboss.org/message/827797#827797
--------------------------------------------------------------
Hi, I have exactly the same issue. Any help will be apreciated.
Mario Torre
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/827797#827797]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
- 2
- 2
[JBoss AS 7 Development] - Question about having Multiple EAR Files in a single deployment
by ronorato
ronorato [https://community.jboss.org/people/ronorato] created the discussion
"Question about having Multiple EAR Files in a single deployment"
To view the discussion, visit: https://community.jboss.org/message/827819#827819
--------------------------------------------------------------
I Have an application that I am deploying on a server running a single instance of JBoss AS 7 (will be moving to 6.1). I have broken the application up into multiple EAR files. I have two EAR files that contain just application code (POJO) and some EJBs but no related items. Then I have multiple EAR files that contain application code (POJOs), EJBs and Web (packaged in a WAR file). I am using JNDI to communicate between modules (internal and exernal to the EAR) and I am using JPA for my database access. So I have a few questions about all of this.
First (this is probaly more of option oriented question, but figured I ask it here) is this a good way to group and deploy functionality? I am grouping items into EAR files based on the functionality offered. I was doing this to allow functionality to be distributed over mulitple severs where one set of servers may provide core functionality and another set functionality related to feature x.
The second question really has to do with how to set the root context so that it points to pages in my company home application. I have tried updating the application.xml within that EAR but that did not work. Everytime I go to the root context "localhost:8080" I ended up with a JBoss AS page. I am not sure where this page is being set from.
Another question along the same lines as the one above. Is it possible to have multiple domains pointing to the same JBoss instance with each one having its one root context or do I need to build up routes (similar to how it is done in MVC 3 & 4)?
Thank you in advance,
Richard O
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/827819#827819]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 9 months
- 1
- 0