[JBoss AS 7 Development] - HornetQ live-Backup failover on JBoss AS 7
by Celia Wang
Celia Wang [http://community.jboss.org/people/hsichuan] created the discussion
"HornetQ live-Backup failover on JBoss AS 7"
To view the discussion, visit: http://community.jboss.org/message/645871#645871
--------------------------------------------------------------
Hello everyone, I am not a native English speaker and I'm new to here. I really need some help, please help me~thanks.
I had spent a lot of time on the HornetQ User Manual but it seems like that there are some problems happened.
What I want to do is that live server can failover to backup server when client is sending messages.
My problem is: when I killed the live server, my backup server could not take over and become live.
I have 4 servers -
A: HornetQ Live Server on JBoss AS7 (jboss-as-7.0.1.Final)
deploy mdb-ear-1.0.0.ear (andytaylor-HornetQ-AS7-examples-1a5935b , it's a mdb example)
B: HornetQ Backup Server on JBoss AS7
deploy mdb-ear-1.0.0.ear , but backup server is lock, this deployment will not be active until backup server become live
C: a client running MDB example, send 2000 of messages to live server (andytaylor-HornetQ-AS7-examples-1a5935b/mdb/mdb-client)
D: shared store - NFS, to store A&B's message journal
The method of executing server:
A: ./standalone.sh --server-config=standalone-preview-ha-live.xml
B: ./standalone.sh --server-config=standalone-preview-ha-back.xml
C: mvn -Pclient test
Here is the configurations changed on A & B
standalone-preview-ha-live.xml & standalone-preview-ha-back.xml are modified from standalone-preview-ha.xml
where the font color is red is my modified for configurations, others are the same as standalone-preview-ha.xml
*A: live server -*
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<!-- Default journal file size is 10Mb, reduced here to 100k for faster first boot -->
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<!-- disable messaging persistence -->
<persistence-enabled>false</persistence-enabled>
<!--add hornetq-configuration set live here-->
<clustered>true</clustered>
<failover-on-shutdown>false</failover-on-shutdown>
<shared-store>true</shared-store>
<!--end here-->
---
skip
---
<jms-destinations>
<jms-queue name="testQueue">
<entry name="queue/test"/>
</jms-queue>
<jms-queue name="mdbQueue">
<entry name="queue/mdbQueue"/>
</jms-queue>
<jms-queue name="mdbReplyQueue">
<entry name="queue/mdbReplyQueue"/>
</jms-queue>
<jms-topic name="testTopic">
<entry name="topic/test"/>
</jms-topic>
</jms-destinations>
---
skip
---
<interfaces>
<interface name="management">
<inet-address value="140.XXX.XX.231"/>
</interface>
<interface name="public">
<inet-address value="140.XXX.XX.231"/>
</interface>
</interfaces>
*B: backup server -*
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<!-- Default journal file size is 10Mb, reduced here to 100k for faster first boot -->
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<!-- disable messaging persistence -->
<persistence-enabled>false</persistence-enabled>
<!--add hornetq-configuration set backup here -->
<clustered>true</clustered>
<failover-on-shutdown>false</failover-on-shutdown>
<backup>true</backup>
<shared-store>true</shared-store>
<!--end here-->
<connectors>
<netty-connector name="netty" socket-binding="messaging" />
<netty-connector name="netty-throughput" socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0" />
</connectors>
---
skip
---
<jms-destinations>
<jms-queue name="testQueue">
<entry name="queue/test"/>
</jms-queue>
<jms-queue name="mdbQueue">
<entry name="queue/mdbQueue"/>
</jms-queue>
<jms-queue name="mdbReplyQueue">
<entry name="queue/mdbReplyQueue"/>
</jms-queue>
<jms-topic name="testTopic">
<entry name="topic/test"/>
</jms-topic>
</jms-destinations>
---
skip
---
<interfaces>
<interface name="management">
<inet-address value="140.XXX.XX.232"/>
</interface>
<interface name="public">
<inet-address value="140.XXX.XX.232"/>
</interface>
</interfaces>
*C: I modified "MDBClient.java", in order to send messages to the live server.*
final int numMessages = 2000;
HashMap map = new HashMap();
map.put("host", "140.XXX.XX.231");
map.put("port", 5445);
TransportConfiguration transportConfiguration = new TransportConfiguration(NettyConnectorFactory.class.getName(),map);
---skip---
TextMessage message=null;
//Step 7. Create a Text Message
for (int i = 0; i < numMessages; i++)
{
message = session.createTextMessage("This is a text message"+ i);
//Step 8. Send the Message
producer.send(message);
System.out.println("Sent message: " + message.getText());
}
*D: shared store - NFS*
The NFS directory is /home/user/jboss-as-7.0.1.Final/standalone/data
==================================
Now, after live & backup server is started, I executed "MDBClient.java", sending 2000 messages to the live server.
Then, I went to the live server and killed its process id.
jps
kill XXXXX
My backup server did not become live, but after some minutes, there are a lot of WARN on live server's boot.log & backup server's server.log
WARN [com.arjuna.ats.jta] ARJUNA16038: No XAResource to recover < formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffff8c7452e7:7386542f:4f0d2d17:ebf, node_name=1, branch_uid=0:ffff8c7452e7:7386542f:4f0d2d17:ec0, eis_name=unknown eis name >
*Here is the server.log on live server.*
14:32:55,668 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-4) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /opt/jdk1.6.0_24/jre/lib/amd64/server:/opt/jdk1.6.0_24/jre/lib/amd64:/opt/jdk1.6.0_24/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
14:32:55,701 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1) Starting remote JMX connector
14:32:55,707 INFO [org.jboss.as.remoting] (MSC service thread 1-7) Listening on /140.XXX.XX.231:9999
14:32:55,738 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
14:32:55,742 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-5) Starting Coyote HTTP/1.1 on http-WMC-Cloud-A-140.XXX.XX.231-8080
14:32:55,751 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.0.Beta3
14:32:55,889 INFO [org.jboss.as.modcluster] (MSC service thread 1-4) Mod_cluster uses default load balancer provider
14:32:55,963 INFO [org.jboss.modcluster.ModClusterService] (MSC service thread 1-4) Initializing mod_cluster 1.1.3.Final
14:32:55,982 INFO [org.jboss.as.connector] (MSC service thread 1-2) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
14:32:55,986 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-4) Listening to proxy advertisements on 224.0.1.105:23364
14:32:56,045 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) Bound data source [java:jboss/datasources/ExampleDS]
14:32:56,056 INFO [org.jboss.as.jacorb] (MSC service thread 1-3) CORBA ORB Service Started
14:32:56,126 \u8cc7\u8a0a [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=/home/wmc/jboss-as-7.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/home/wmc/jboss-as-7.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/home/wmc/jboss-as-7.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/home/wmc/jboss-as-7.0.1.Final/standalone/data/messagingpaging)
14:32:56,161 \u8b66\u544a [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.
14:32:56,172 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) Registered connection factory java:/JmsXA
14:32:56,193 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-1) HornetQ resource adaptor started
14:32:56,193 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra
14:32:56,209 INFO [org.jboss.as.jacorb] (MSC service thread 1-3) CORBA Naming Service Started
14:32:56,304 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-5) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} WMC-Cloud-A:5455 for CORE protocol
14:32:56,305 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-5) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} WMC-Cloud-A:5445 for CORE protocol
14:32:56,306 \u8cc7\u8a0a [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) Server is now live
14:32:56,306 \u8cc7\u8a0a [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [b4c2c38f-3c18-11e1-8dd2-e41f13246ff6] started
14:32:56,308 \u8cc7\u8a0a [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) trying to deploy queue jms.topic.testTopic
14:32:56,384 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-8) Bound messaging object to jndi name java:/topic/test
14:32:56,395 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-2) Bound messaging object to jndi name java:/RemoteConnectionFactory
14:32:56,397 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-1) Bound messaging object to jndi name java:/ConnectionFactory
14:32:56,397 \u8cc7\u8a0a [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) trying to deploy queue jms.queue.mdbQueue
14:32:56,421 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-5) Bound messaging object to jndi name java:/queue/mdbQueue
14:32:56,422 \u8cc7\u8a0a [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) trying to deploy queue jms.queue.testQueue
14:32:56,435 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-7) Bound messaging object to jndi name java:/queue/test
14:32:56,435 \u8cc7\u8a0a [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) trying to deploy queue jms.queue.mdbReplyQueue
14:32:56,446 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-4) Bound messaging object to jndi name java:/queue/mdbReplyQueue
14:32:56,623 INFO [org.jboss.as.deployment] (MSC service thread 1-4) Started FileSystemDeploymentService for directory /home/wmc/jboss-as-7.0.1.Final/standalone/deployments
14:32:56,641 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 2665ms - Started 128 of 208 services (80 services are passive or on-demand)
14:32:56,652 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "my-webapp.war"
14:32:56,652 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) Starting deployment of "mdb-ear-1.0.0.ear"
14:32:56,692 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "mdb-jar-1.0.0.jar"
14:32:56,717 INFO [org.jboss.as.jpa] (MSC service thread 1-3) added javax.persistence.api dependency to my-webapp.war
14:32:56,720 INFO [org.jboss.as.jpa] (MSC service thread 1-5) added javax.persistence.api dependency to mdb-ear-1.0.0.ear
14:32:56,723 INFO [org.jboss.as.jpa] (MSC service thread 1-5) added javax.persistence.api dependency to mdb-jar-1.0.0.jar
14:32:56,875 INFO [org.jboss.web] (MSC service thread 1-4) registering web context: /my-webapp
14:32:56,923 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "mdb-ear-1.0.0.ear"
14:32:56,923 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "my-webapp.war"
14:33:05,921 INFO [org.jboss.modcluster.ModClusterService] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Engine [jboss.web] will use jvmRoute: d883de1f-fe17-3214-8442-4e4880a8781a
---after client send messages---
14:34:10,802 INFO [stdout] (Thread-3 (group:HornetQ-client-global-threads-2000502626)) message This is a text message2
14:34:10,805 INFO [stdout] (Thread-3 (group:HornetQ-client-global-threads-2000502626)) connection created
14:34:10,815 INFO [stdout] (Thread-9 (group:HornetQ-client-global-threads-2000502626)) message This is a text message8
14:34:10,815 INFO [stdout] (Thread-9 (group:HornetQ-client-global-threads-2000502626)) connection created
14:34:10,815 INFO [stdout] (Thread-2 (group:HornetQ-client-global-threads-2000502626)) message This is a text message1
14:34:10,816 INFO [stdout] (Thread-2 (group:HornetQ-client-global-threads-2000502626)) connection created
---skip---kill the live server
14:36:32,377 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-5) Stopping Coyote HTTP/1.1 on http-WMC-Cloud-A-140.116.82.231-8080
14:36:32,378 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-7) Unbound messaging object from jndi name java:/RemoteConnectionFactory
14:36:32,380 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-6) Unbound messaging object from jndi name java:/topic/test
*boot.log on live server (because live server is shutdown)*
14:32:55,322 INFO [org.jboss.as.logging] Removing bootstrap log handlers
The followings are the WARNs and ERRORs after the live server killed.
14:36:32,398 INFO [org.jboss.as.logging] Restored bootstrap log handlers
14:36:32,415 INFO [org.jboss.modcluster.ModClusterService] All active sessions drained from context [/my-webapp] in 0 seconds
14:36:32,421 INFO [org.jboss.as.jmx.JMXConnectorService] JMX remote connector stopped
14:36:32,423 INFO [stdout] message This is a text message415
14:36:32,423 INFO [stdout] connection created
14:36:32,426 INFO [org.jboss.modcluster.ModClusterService] All active sessions drained from context [/my-webapp] in 0 seconds
14:36:32,429 INFO [stdout] session created
14:36:32,430 ERROR [stderr] javax.jms.InvalidDestinationException: Destination mdbReplyQueue does not exist
14:36:32,430 ERROR [stderr] at org.hornetq.jms.client.HornetQSession.createProducer(HornetQSession.java:337)
14:36:32,430 ERROR [stderr] at org.hornetq.ra.HornetQRASession.createProducer(HornetQRASession.java:1163)
14:36:32,430 ERROR [stderr] at org.hornetq.example.MDBSendExample.onMessage(MDBSendExample.java:77)
--skip--
14:36:32,608 \u8cc7\u8a0a [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [b4c2c38f-3c18-11e1-8dd2-e41f13246ff6] stopped
14:37:02,575 WARN [com.arjuna.ats.jta] ARJUNA16086: TransactionImple.enlistResource setTransactionTimeout on XAResource < formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffff8c7452e7:7386542f:4f0d2d17:ee7, node_name=1, branch_uid=0:ffff8c7452e7:7386542f:4f0d2d17:ee8, eis_name=unknown eis name > threw: XAException.XAER_RMERR: javax.transaction.xa.XAException
--skip
14:37:02,599 ERROR [org.hornetq.core.client.impl.ClientSessionImpl] Caught jmsexecptione : HornetQException[errorCode=3 message=Timed out waiting for response when sending packet 52]
--skip
14:37:02,605 WARN [com.arjuna.ats.jta] ARJUNA16041: prepare on < formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffff8c7452e7:7386542f:4f0d2d17:edf, node_name=1, branch_uid=0:ffff8c7452e7:7386542f:4f0d2d17:ee0, eis_name=unknown eis name > (org.hornetq.core.client.impl.DelegatingSession@4aa594e1) failed with exception XAException.XAER_RMERR: javax.transaction.xa.XAException
--skip
14:37:02,610 WARN [com.arjuna.ats.arjuna] ARJUNA12073: BasicAction.End() - prepare phase of action-id 0:ffff8c7452e7:7386542f:4f0d2d17:edf failed.
14:37:02,610 WARN [com.arjuna.ats.arjuna] ARJUNA12075: Action Aborting
14:37:02,633 WARN [org.hornetq.core.client.impl.ClientSessionImpl] failover occured during commit throwing XAException.XA_RETRY
14:37:02,634 WARN [com.arjuna.ats.jta] ARJUNA16036: commit on < formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffff8c7452e7:7386542f:4f0d2d17:eb7, node_name=1, branch_uid=0:ffff8c7452e7:7386542f:4f0d2d17:eb8, eis_name=unknown eis name > (org.hornetq.core.client.impl.DelegatingSession@58fe210a) failed with exception $XAException.XA_RETRY: javax.transaction.xa.XAException
*Here is the server.log on backup server.*
14:35:36,363 \u8cc7\u8a0a [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) backup server is starting with configuration HornetQ Configuration (clustered=true,backup=true,sharedStore=true,journalDirectory=/home/wmc/jboss-as-7.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/home/wmc/jboss-as-7.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/home/wmc/jboss-as-7.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/home/wmc/jboss-as-7.0.1.Final/standalone/data/messagingpaging)
14:35:36,365 \u8cc7\u8a0a [org.hornetq.jms.server.impl.JMSServerManagerImpl] (MSC service thread 1-5) Caching command for createQueue for mdbReplyQueue since the JMS Server is not active yet
14:35:36,367 \u8cc7\u8a0a [org.hornetq.jms.server.impl.JMSServerManagerImpl] (MSC service thread 1-5) Caching command for createConnectionFactory for RemoteConnectionFactory since the JMS Server is not active yet
14:35:36,367 \u8cc7\u8a0a [org.hornetq.jms.server.impl.JMSServerManagerImpl] (MSC service thread 1-5) Caching command for createQueue for testQueue since the JMS Server is not active yet
14:35:36,367 \u8cc7\u8a0a [org.hornetq.jms.server.impl.JMSServerManagerImpl] (MSC service thread 1-5) Caching command for createQueue for mdbQueue since the JMS Server is not active yet
14:35:36,368 \u8cc7\u8a0a [org.hornetq.jms.server.impl.JMSServerManagerImpl] (MSC service thread 1-6) Caching command for createConnectionFactory for InVmConnectionFactory since the JMS Server is not active yet
14:35:36,368 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (Thread-18) Waiting to become backup node
14:35:36,368 \u8cc7\u8a0a [org.hornetq.jms.server.impl.JMSServerManagerImpl] (MSC service thread 1-2) Caching command for createTopic for testTopic since the JMS Server is not active yet
14:35:36,396 INFO [org.jboss.as.jacorb] (MSC service thread 1-1) CORBA Naming Service Started
14:35:36,401 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) Registered connection factory java:/JmsXA
14:35:36,407 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-3) HornetQ resource adaptor started
14:35:36,408 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatorhornetq-ra
14:35:36,427 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (Thread-18) ** got backup lock
14:35:36,443 \u8b66\u544a [org.hornetq.core.server.impl.HornetQServerImpl] (Thread-18) Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.
14:35:36,487 \u8cc7\u8a0a [org.hornetq.core.server.impl.HornetQServerImpl] (Thread-18) HornetQ Backup Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [b4c2c38f-3c18-11e1-8dd2-e41f13246ff6] started, waiting live to fail before it gets active
14:35:36,843 INFO [org.jboss.as.deployment] (MSC service thread 1-5) Started FileSystemDeploymentService for directory /home/wmc/jboss-as-7.0.1.Final/standalone/deployments
14:35:36,860 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 2572ms - Started 128 of 208 services (80 services are passive or on-demand)
14:35:46,162 INFO [org.jboss.modcluster.ModClusterService] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Engine [jboss.web] will use jvmRoute: a8c846d5-8c74-327b-ba50-723177f332e2
--the following are the WARNs after live server killed,
14:37:56,286 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA16037: Could not find new XAResource to use for recovering non-serializable XAResource XAResourceRecord < resource:null, txid:< formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffff8c7452e7:7386542f:4f0d2d17:ed7, node_name=1, branch_uid=0:ffff8c7452e7:7386542f:4f0d2d17:ed8, eis_name=unknown eis name >, heuristic: TwoPhaseOutcome.FINISH_OK com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@78221c75 >
14:37:56,287 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA16037: Could not find new XAResource to use for recovering non-serializable XAResource XAResourceRecord < resource:null, txid:< formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffff8c7452e7:7386542f:4f0d2d17:ed7, node_name=1, branch_uid=0:ffff8c7452e7:7386542f:4f0d2d17:edc, eis_name=unknown eis name >, heuristic: TwoPhaseOutcome.FINISH_OK com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@5271b383 >
14:37:56,288 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA16038: No XAResource to recover < formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffff8c7452e7:7386542f:4f0d2d17:ed7, node_name=1, branch_uid=0:ffff8c7452e7:7386542f:4f0d2d17:ed8, eis_name=unknown eis name >
14:37:56,288 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA16038: No XAResource to recover < formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffff8c7452e7:7386542f:4f0d2d17:ed7, node_name=1, branch_uid=0:ffff8c7452e7:7386542f:4f0d2d17:edc, eis_name=unknown eis name >
--it will receive the same WARN repeately---
=================================
The live & backup server will always receive the same WARNs repeately, it seems like a deadlock.
However, the backup server did not become live.
Do I miss any other configurations on live & backup server?
Does anyone knows how to successfully set live & backup server failover?
I'm sorry about that I post a long description of my problem, if there is any question about my problem, just ask.
Thanks for your help!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/645871#645871]
Start a new discussion in JBoss AS 7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years
[jBPM Development] - After modifying jbpm-gwt-console.war file, I got Runtime Exceptins at deploying jbpm-gwt-console.war file in running jboss instance.
by Mark P
Mark P [http://community.jboss.org/people/jbpm_mark] created the discussion
"After modifying jbpm-gwt-console.war file, I got Runtime Exceptins at deploying jbpm-gwt-console.war file in running jboss instance."
To view the discussion, visit: http://community.jboss.org/message/645292#645292
--------------------------------------------------------------
Hi Guys,
I got some runtime Exceptions while followed the below steps. Help me in solving this issue.
1) Downloaded the source code(zip file) from https://github.com/bpmc/bpm-console https://github.com/bpmc/bpm-console.
2) Extracted in a folder (bpmc-bpm-console-1cf8710).
3) I run "mvn clean install" from the bpmc-bpm-console-1cf8710 folder.
4) I run "mvn package" from the bpmc-bpm-console-1cf8710 folder
5) After that the war file(gwt-console.war) was generated in target folder(bpmc-bpm-console-1cf8710/gui/war/target)
6) I renamed the war file(gwt-console.war) to "jbpm-gwt-console.war" file and i deployed the "jbpm-gwt-console.war" file in running jboss instance (jboss/server/default/deploy),
i got some errors which i posted here.
2012-01-05 17:42:44,779 ERROR [org.reflections.Reflections] (HDScanner) could not create Vfs.Dir from url. ignoring the exception and continuing
org.reflections.ReflectionsException: could not create Dir using org.jboss.errai.bus.server.service.metadata.VFSUrlType from url vfszip:/D:/jbpm5.1_BKP/jbpm-installer/jboss-5.1.0.GA/server/default/deploy/jbpm-gwt-console.war/WEB-INF/classes/
at org.reflections.vfs.Vfs.fromURL(Vfs.java:99)
at org.reflections.vfs.Vfs.fromURL(Vfs.java:89)
at org.reflections.Reflections.scan(Reflections.java:136)
at org.jboss.errai.bus.server.service.metadata.MetaDataScanner.<init>(MetaDataScanner.java:83)
at org.jboss.errai.bus.server.service.metadata.MetaDataScanner.createInstance(MetaDataScanner.java:95)
at org.jboss.errai.bus.server.service.metadata.MetaDataScanner.createInstance(MetaDataScanner.java:87)
at org.jboss.errai.bus.server.service.ErraiServiceConfiguratorImpl.<init>(ErraiServiceConfiguratorImpl.java:58)
at org.jboss.errai.bus.server.service.ErraiServiceConfiguratorImpl$$FastClassByGuice$$b6139751.newInstance(<generated>)
at com.google.inject.internal.cglib.reflect.FastConstructor.newInstance(FastConstructor.java:40)
at com.google.inject.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60)
at com.google.inject.ConstructorInjector.construct(ConstructorInjector.java:85)
at com.google.inject.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:111)
at com.google.inject.FactoryProxy.get(FactoryProxy.java:56)
at com.google.inject.SingleParameterInjector.inject(SingleParameterInjector.java:42)
at com.google.inject.SingleParameterInjector.getAll(SingleParameterInjector.java:66)
at com.google.inject.ConstructorInjector.construct(ConstructorInjector.java:84)
at com.google.inject.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:111)
at com.google.inject.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:45)
at com.google.inject.InjectorImpl.callInContext(InjectorImpl.java:811)
at com.google.inject.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:42)
at com.google.inject.Scopes$1$1.get(Scopes.java:54)
at com.google.inject.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:48)
at com.google.inject.FactoryProxy.get(FactoryProxy.java:56)
at com.google.inject.InjectorImpl$4$1.call(InjectorImpl.java:758)
at com.google.inject.InjectorImpl.callInContext(InjectorImpl.java:804)
at com.google.inject.InjectorImpl$4.get(InjectorImpl.java:754)
at com.google.inject.InjectorImpl.getInstance(InjectorImpl.java:793)
at org.jboss.errai.bus.server.servlet.AbstractErraiServlet.buildService(AbstractErraiServlet.java:133)
at org.jboss.errai.bus.server.servlet.AbstractErraiServlet.init(AbstractErraiServlet.java:104)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:950)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4122)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4421)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142)
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
at org.jboss.web.deployers.WebModule.start(WebModule.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
at $Proxy38.start(Unknown Source)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.start(ServiceController.java:460)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
2012-01-05 17:42:44,905 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (HDScanner) Bootstrap Errai
2012-01-05 17:42:44,917 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (HDScanner) using dispatcher implementation: org.jboss.errai.bus.server.AsyncDispatcher
2012-01-05 17:42:44,924 INFO [org.jboss.errai.bus.server.WorkerFactory] (HDScanner) initializing async worker pools (poolSize: 5; workerTimeout: 5000)
2012-01-05 17:42:44,926 INFO [org.jboss.errai.bus.server.WorkerFactory] (HDScanner) starting worker pool.
2012-01-05 17:42:44,930 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (HDScanner) using session provider implementation: org.jboss.errai.bus.server.HttpSessionProvider
2012-01-05 17:42:44,938 INFO [org.jboss.errai.bus.server.service.bootstrap.LoadExtensions] (HDScanner) beging searching for Errai extensions ...
2012-01-05 17:42:44,984 INFO [org.jboss.errai.bus.server.service.bootstrap.LoadExtensions] (HDScanner) added extension binding: org.jboss.errai.bus.client.framework.ModelAdapter
2012-01-05 17:42:44,984 INFO [org.jboss.errai.bus.server.service.bootstrap.LoadExtensions] (HDScanner) total extension binding: 1
2012-01-05 17:42:45,025 INFO [org.jboss.errai.bus.server.service.bootstrap.BootstrapContext] (HDScanner) Running deferred bootstrap tasks ...
2012-01-05 17:42:45,025 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (HDScanner) Bootstrap complete. Ready to rumble!
Thanks
Mark
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/645292#645292]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years
[JBoss AS 7 Development] - Command Line Interface
by Alexey Loubyansky
Alexey Loubyansky [http://community.jboss.org/people/aloubyansky] modified the document:
"Command Line Interface"
To view the document, visit: http://community.jboss.org/docs/DOC-16581
--------------------------------------------------------------
The AS7 Command Line Interface (CLI) is a command line management tool for the AS 7 domain or a standalone server. It allows a user to connect to the AS7 domain controller or a standalone server and execute management operations available through the http://community.jboss.org/docs/DOC-16317 AS7 detyped management model. Depending on the operation system, the CLI is launched using jboss-admin.sh or jboss-admin.bat located in the AS7 bin directory.
h2. Features
The CLI features include:
* connect to the specific controller or server instance by specifying the host and the port;
* send operation requests (providing the managed component's address, attribute or operation name and parameters) following the http://community.jboss.org/docs/DOC-16317 AS7 detyped management model;
* view the available managed components, their attributes and operations;
* tab-completion for commands and operation requests;
* history of the executed commands and operation requests;
* http://community.jboss.org/docs/DOC-16769 deploy and undeploy packages at runtime in standalone and domain modes;
* http://community.jboss.org/docs/DOC-16728 batch mode;
* http://community.jboss.org/docs/DOC-17041 non-interactive mode;
* http://community.jboss.org/docs/DOC-16981 generic resource type commands;
* http://community.jboss.org/docs/DOC-17457 GUI mode.
h2. Commands
There are commands and operations. They are different. Operations are considered a low level but comprehensive way to manage the AS controller, i.e. if it can't be done with operations it can't be done in any other way.
Commands, on the other hand, are more user-friendly in syntax, although most of them still translate into operation requests and some of them even into a few operation requests, i.e. commands also simplify some management operations from the user's point of view.
To see all the list of all the supported commands enter command +help --commands+. Another way to list all the supported commands is to press the tab key at the command line prompt which will trigger the tab-completion for the commands. The list of the available commands depends on the current context, i.e. it may change since some of the commands may require an established connection to the AS controller, or the presence of a certain node address in the domain management model, etc. For example, if the server configuration doesn't include messaging subsystem then the CLI will not expose messaging related commands.
To see a detailed description of a specific command, execute the command with +--help+ as the argument.
h3. Connection
The first thing to do after the CLI has started is to connect to a managed AS7 instance. This is done using the command +connect+, e.g.
+connect+
which is equivalent to
+connect localhost:9999+
localhost:9999 is the default host and port combination for the AS7 model controller client. Both, the host and the port, are optional parameters and can be specified together or separately.
h3. Quit
To terminate the session type +quit+.
h2. Operation requests
The format for the operation requests is
[node-type=node-name (,node-type=node-name)*] : operation-name [( [parameter-name=parameter-value (,parameter-name=parameter-value)*] )]
e.g.
/profile=default/subsystem=logging/console-handler=CONSOLE:read-attribute(name=level)
It's a lot of typing but tab-completion is supported for all the composing parts, i.e. node-types and node-names, operation names and parameter names. We are also looking into adding custom commands/aliases that would be less verbose for the user but would translate into the corresponding operation requests on the background.
Whitespaces between the separators in the operation request strings are not significant.
Operation requests might not always have the address part or the parameters. E.g.
+:read-resource+
which will list all the node types for the current node.
To syntactically disambiguate between the commands and operations, operations require one of the following prefixes:
* +:+ - to execute an operation against the current node, e.g.
+[subsystem=web] :read-resource(recursive="true")+
+
+
* +./+ - to execute an operation against a child node of the current node, e.g.
+[subsystem=web] ./connector=http:read-resource+
i.e. the full address of the operation will be +subsystem=web,connector=http+.
* +/+ - to execute an operation against the root node, e.g.
+[subsystem=web] /:read-resource+
or its child, e.g.
+[subsystem=web] /subsystem=logging:read-resource+
h3. How the tab-completion works
Suppose, the cursor is positioned at the beginning of an empty line. If you type in +'./'+ and press the tab key, you will get a list of all the available node types. After selecting the node type you want and adding '=', pressing the tab key again will result in a list of all the node names available for the chosen node type. If, after selecting the node name from the list, you want to continue with the node path then add ',' after the selected node name and press the tab key again. This will print all the available node types for the previously select node.
After you are done with the node path, adding ':' at the end of the node path and pressing the tab key will print all the available operation names for the selected node.
To see all the parameters of the operation, add '(' after the operation name and press the tab key. Choose the parameter you want and specify its value after '='. Tab-completion for parameter values is not supported (yet?). If you want to add more parameters, add ',' and press the tab key to see the rest of the available parameter names.
Finally, when all the parameters have been specified, add ')' and press enter.
In the node path you can use the following strings for navigations:
* .. - parent node, e.g.
+[/] ./subsystem=web/../subsystem=transactions+
is equivalent to
+[/] ./subsystem=transactions+
* +.type+ - the type of the current node, e.g.
+[/] ./subsystem=web/.type/transactions+
is equivalent to the same
+[/] ./subsystem=transactions+
h2. Current node path and navigation
The current node path is indicated in the command line prompt. The default value is '/', i.e. the root node. All the operation requests that don't contain the address part will be executed against the current node path.
h4. Change node command (cn or cd)
+cn+, or +cd+, command allows you to change the current node path, e.g.
+[host:port /] cd subsystem=web+
After that the command line prompt will change to
+[host:port /subsystem=web]+
and every operation entered w/o the node path will be executed against the node subsystem=web. If you do specify a node path for the operation, it will be considered relative to subsystem=web.
The node path might not necessarily end on a node name. It might be just
+[host:port /] cd subsystem+
+[host:port /subsystem]+
Then to execute an operation against the logging subsystem you would type in
+[host:port /subsystem] logging:read-resource+
To go back to the root node, type in
+[host:port /subsystem] cd /+
+[host:port /]+
You can also navigate to the parent node
+[++host:port /++subsystem=web,connector=http] cd ..+
+[++host:port /++subsystem=web]+
or the node type
+[++host:port /++subsystem=web] cd .type+
+[++host:port /++subsystem]+
h4. List contents command (ls)
+ls+ command will list the contents of a node path. The command has an optional node path argument. If the argument is specified, the command will print the contents of the node path specified in the argument. If the argument is not specified, the command will print the contents of the current node path (indicated in the prompt).
If the node path ends on a node type then the contents will be the child node names. If the node path ends on a node name then the contents will be the child node types.
If the contents of the node path is empty, nothing will be printed.
Example:
+[localhost:9999 /subsystem=web] ls+
+virtual-server connector+
+[localhost:9999 /subsystem=web] ls connector +
+http+
+[localhost:9999 /subsystem=web]+
h2. Special characters in node names
White ':' and '/' have special significance for in the format of the operation request, these characters aren't disallowed in node names.
If they are typed in though, the operation request parser will be confused and will probably result it an error. To workaround this issue you should quote the names with special characters, e.g.
+[localhost:9999 /subsystem=datasources] cd data-source="java:/H2DS"+
+[localhost:9999 /subsystem=datasources/data-source=java:/H2DS]+
The node name, actually, is also allowed to contain '"'. In case the node name has to be quoted and it also contains quotes in its content then the quotes that are a part of the node name content have to be escaped using, i.e. '\"'.
+[localhost:9999 /] cd nodetype="node:name/with\"quotes\""+
+[localhost:9999 /node:name/with"quotes"]
+
Note, that the tab-completion takes care of this automatically.
h3. Command history
Command (and operation request) history is enabled by default. The history is kept both: in-memory and in a file on the disk, i.e. it is preserved between the command line sessions. The history file name is .jboss-cli-history and is automatically created in the user's home directory. When the command line interface is launched this file is read and the in-memory history is initialized with its content.
While in the command line session, you can use the arrow keys to go back and forth in the history of commands and operations. To manipulate the history you can use +history+ command.
If executed w/o the argument, it will print all the recorded commands and operations (up to the configured maximum, which is by default 500) from the in-memory history.
+history+ supports three optional arguments:
* disable - will disable history expansion (but will not clear the previously recorded history);
* enabled - will re-enable history expansion (starting from the last recorded command before the history expansion was disabled);
* clear - will clear the in-memory history (but not the file one).
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16581]
Create a new document in JBoss AS 7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years
[jBPM Development] - jbpm-human-task has dependency on jboss-seam -- causing issues with JSF
by Wendy Schmitz
Wendy Schmitz [http://community.jboss.org/people/wendyschmitz] created the discussion
"jbpm-human-task has dependency on jboss-seam -- causing issues with JSF"
To view the discussion, visit: http://community.jboss.org/message/641797#641797
--------------------------------------------------------------
I am creating a richfaces web application that will act as the front-end for an embedded jbpm engine. I'm running into the following exception when I launch the first page in the application:
2011-12-15 10:10:51 SeamPhaseListener [WARN] uncaught exception, passing to exception handler
java.lang.NullPointerException
at org.jboss.seam.jsf.SeamPhaseListener.raiseEventsAfterPhase(SeamPhaseListener.java:435)
at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:188)
at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:189)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:107)
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:409)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
ava:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja
va:588)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:619)
It seems like Seam is invoked when I launch my Richfaces/JSF application, causing it to interfere with the normal JSF processing. It turns out that jbpm-human-task has a dependency on jboss-seam, and when I remove jbpm-human-task from my pom, I no longer have this exception. How can I use jbpm's human task component in my Richfaces/JSF web app without it breaking the app?
Thanks,
Wendy
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/641797#641797]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years
[JBoss AS 7 Development] - Logging Id's
by Ales Justin
Ales Justin [http://community.jboss.org/people/alesj] modified the document:
"Logging Id's"
To view the document, visit: http://community.jboss.org/docs/DOC-16810
--------------------------------------------------------------
Logging id ranges for JBoss AS7 i18n message interfaces.
|| %1,3% *Status* ||
| C | = | Complete |
| I | = | In Progress |
| P | = | Merged, but not complete |
| W | = | Waiting Merge |
|| *Range* || *Subsystem
* || *Status
* ||
| *10100 - 10199* | *Transaction* | C |
| *10200 - 10399
* | *Clustering**
* | C |
| *10400 - 10499* | *Connector**
* | C |
| *10500 - 10599* | *CLI
* |
|
| *10600 - 10699* | *Controller Client* | C |
| *10700 - 10799* | *CMP* |
|
| *10900 - 10999* | *Host Controller* | C |
| *11000 - 11099* | *EE* | C |
| *11100 - 11199* | *Embedded* | C |
| *11200 - 11299* | *JAXRS* | C |
| *11300 - 11399* | *JMX* | C |
| *11400 - 11499* | *JPA* | C |
| *11500 - 11599* | *Logging* | C |
| *11600 - 11699* | *Messaging* | C |
| *11700 - 11799* | *mod_cluster* | C |
| *11800 - 11899* | *Naming* | C |
| *11900 - 11999* | *OSGi (as plugin 00-10; service 11-99)* | C |
| *12000 - 12099* | *Process Controller* | C |
| *12100 - 12199* | *Protocol* | C |
| *12200 - 12299* | *Management Client Content* | *I* |
| *12300 - 12399* | *Platform MBeans* | *I* |
| *13100 - 13199* | *Security* |
|
| *14100 - 14399* | *Ejb3* | P |
| *14400 - 14499* | *AppClient* | C |
| *14500 - 14599* | *JDR* | C |
| *14600 - 14899* | *Controller* | C |
| *14900 - 14999* | *Deployment Repository* | C |
| *15000 - 15099* | *Deployment Scanner* | C |
| *15100 - 15199* | *Deployment HTTP API* | C |
| *15200 - 15299* | *Deployment Management* | C |
| *15300 - 15399* | *Network* | C |
|
| *EE Deployment* |
|
|
| *Jacorb* |
|
|
| *JAXR* |
|
| *15400-15499* | *Mail* | C |
| 17000-17099 | *POJO* | W |
|
| *Remoting* |
|
|
| *SAR* |
|
|
| *Security* |
|
| *15700-15999* | *Server* |
|
|
| *Threads* |
|
|
| *Web* |
|
| *15500-15699* | *Web Services* | C |
| *1**6000-16099* | *Weld* |
|
|
| *Xts* |
|
| *15800-15899* | *Domain Controller* | C |
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16810]
Create a new document in JBoss AS 7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years
[JBoss AS 7 Development] - Logging Id's
by Ales Justin
Ales Justin [http://community.jboss.org/people/alesj] modified the document:
"Logging Id's"
To view the document, visit: http://community.jboss.org/docs/DOC-16810
--------------------------------------------------------------
Logging id ranges for JBoss AS7 i18n message interfaces.
|| %1,3% *Status* ||
| C | = | Complete |
| I | = | In Progress |
| P | = | Merged, but not complete |
| W | = | Waiting Merge |
|| *Range* || *Subsystem
* || *Status
* ||
| *10100 - 10199* | *Transaction* | C |
| *10200 - 10399
* | *Clustering**
* | C |
| *10400 - 10499* | *Connector**
* | C |
| *10500 - 10599* | *CLI
* |
|
| *10600 - 10699* | *Controller Client* | C |
| *10700 - 10799* | *CMP* |
|
| *10900 - 10999* | *Host Controller* | C |
| *11000 - 11099* | *EE* | C |
| *11100 - 11199* | *Embedded* | C |
| *11200 - 11299* | *JAXRS* | C |
| *11300 - 11399* | *JMX* | C |
| *11400 - 11499* | *JPA* | C |
| *11500 - 11599* | *Logging* | C |
| *11600 - 11699* | *Messaging* | C |
| *11700 - 11799* | *mod_cluster* | C |
| *11800 - 11899* | *Naming* | C |
| *11900 - 11999* | *OSGi (as plugin 00-10; service 11-99)* | C |
| *12000 - 12099* | *Process Controller* | C |
| *12100 - 12199* | *Protocol* | C |
| *12200 - 12299* | *Management Client Content* | *I* |
| *12300 - 12399* | *Platform MBeans* | *I* |
| *13100 - 13199* | *Security* |
|
| *14100 - 14399* | *Ejb3* | P |
| *14400 - 14499* | *AppClient* | C |
| *14500 - 14599* | *JDR* | C |
| *14600 - 14899* | *Controller* | C |
| *14900 - 14999* | *Deployment Repository* | C |
| *15000 - 15099* | *Deployment Scanner* | C |
| *15100 - 15199* | *Deployment HTTP API* | C |
| *15200 - 15299* | *Deployment Management* | C |
| *15300 - 15399* | *Network* | C |
|
| *EE Deployment* |
|
|
| *Jacorb* |
|
|
| *JAXR* |
|
| *15400-15499* | *Mail* | C |
| 17000-17099 | *POJO* | I |
|
| *Remoting* |
|
|
| *SAR* |
|
|
| *Security* |
|
| *15700-15999* | *Server* |
|
|
| *Threads* |
|
|
| *Web* |
|
| *15500-15699* | *Web Services* | C |
| *1**6000-16099* | *Weld* |
|
|
| *Xts* |
|
| *15800-15899* | *Domain Controller* | C |
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16810]
Create a new document in JBoss AS 7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years