[JBoss JIRA] (AS7-4214) Operation rolled back using rollback-across-groups rollout plan returns success
by Dominik Pospisil (JIRA)
Dominik Pospisil created AS7-4214:
-------------------------------------
Summary: Operation rolled back using rollback-across-groups rollout plan returns success
Key: AS7-4214
URL: https://issues.jboss.org/browse/AS7-4214
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.2.Final
Reporter: Dominik Pospisil
Assignee: Brian Stansberry
If there are multiple server groups involved in management operation and one group fails and the rollback of the other groups is forced by using rollback-across-groups rollout plan the operation still return success. I think that in such situation the operation should return failure as the operation is not executed on any of the servers.
Example of the outcome of a operation which failed on main-one and main-three and was rolled back on main-two and test-one:
[CLI-out] {
[CLI-out] "outcome" => "success",
[CLI-out] "result" => undefined,
[CLI-out] "server-groups" => {
[CLI-out] "main-server-group" => {
[CLI-out] "main-one" => {
[CLI-out] "host" => "master",
[CLI-out] "response" => {
[CLI-out] "outcome" => "failed",
[CLI-out] "failure-description" => {"JBAS014671: Failed services" => {"jboss.web.connector.test-http" => "org.jboss.msc.service.StartException in service jboss.web.connector.test-http: JBAS018007: Error starting web connector"}},
[CLI-out] "rolled-back" => true,
[CLI-out] "response-headers" => {"process-state" => "restart-required"}
[CLI-out] }
[CLI-out] },
[CLI-out] "main-two" => {
[CLI-out] "host" => "master",
[CLI-out] "response" => {
[CLI-out] "outcome" => "failed",
[CLI-out] "rolled-back" => true
[CLI-out] }
[CLI-out] },
[CLI-out] "main-three" => {
[CLI-out] "host" => "slave",
[CLI-out] "response" => {
[CLI-out] "outcome" => "failed",
[CLI-out] "result" => undefined,
[CLI-out] "failure-description" => {"JBAS014671: Failed services" => {"jboss.web.connector.test-http" => "org.jboss.msc.service.StartException in service jboss.web.connector.test-http: JBAS018007: Error starting web connector"}},
[CLI-out] "rolled-back" => true
[CLI-out] }
[CLI-out] }
[CLI-out] },
[CLI-out] "test-server-group" => {"test-one" => {
[CLI-out] "host" => "master",
[CLI-out] "response" => {
[CLI-out] "outcome" => "failed",
[CLI-out] "rolled-back" => true
[CLI-out] }
[CLI-out] }}
[CLI-out] }
[CLI-out] }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
- 2
- 3
[JBoss JIRA] Created: (JBRULES-2384) Unable to process deployment descriptor for context'/drools-server'
by Megha Shetty (JIRA)
Unable to process deployment descriptor for context'/drools-server'
-------------------------------------------------------------------
Key: JBRULES-2384
URL: https://jira.jboss.org/jira/browse/JBRULES-2384
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: All
Environment: windows
Reporter: Megha Shetty
Assignee: Mark Proctor
I am getting the following error when i am trying to deploy drools-server.war through jboss.
Unable to process deployment descriptor for context'/drools-server'
Following is the complete log when i am starting the jboss server
JAVA_HOME is not set. Unexpected results may occur.
Set JAVA_HOME to the directory of your local JDK to avoid this message.
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: E:\Eclipse Europa\jboss-4.2.3.GA
JAVA: java
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcIn
terval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: E:\Eclipse Europa\jboss-4.2.3.GA\bin\run.jar
===============================================================================
14:35:43,295 INFO [Server] Starting JBoss (MX MicroKernel)...
14:35:43,295 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=
JBoss_4_2_3_GA date=200807181417)
14:35:43,295 INFO [Server] Home Dir: E:\Eclipse Europa\jboss-4.2.3.GA
14:35:43,295 INFO [Server] Home URL: file:/E:/Eclipse Europa/jboss-4.2.3.GA/
14:35:43,295 INFO [Server] Patch URL: null
14:35:43,295 INFO [Server] Server Name: default
14:35:43,295 INFO [Server] Server Home Dir: E:\Eclipse Europa\jboss-4.2.3.GA\se
rver\default
14:35:43,311 INFO [Server] Server Home URL: file:/E:/Eclipse Europa/jboss-4.2.3
.GA/server/default/
14:35:43,311 INFO [Server] Server Log Dir: E:\Eclipse Europa\jboss-4.2.3.GA\ser
ver\default\log
14:35:43,311 INFO [Server] Server Temp Dir: E:\Eclipse Europa\jboss-4.2.3.GA\se
rver\default\tmp
14:35:43,311 INFO [Server] Root Deployment Filename: jboss-service.xml
14:35:43,482 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
14:35:43,482 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,S
un Microsystems Inc.
14:35:43,498 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:35:43,857 INFO [Server] Core system initialized
14:35:45,670 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083
/
14:35:45,670 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:jboss-log4j.xml
14:35:46,513 INFO [TransactionManagerService] JBossTS Transaction Service (JTA
version) - JBoss Inc.
14:35:46,513 INFO [TransactionManagerService] Setting up property manager MBean
and JMX layer
14:35:46,701 INFO [TransactionManagerService] Starting recovery manager
14:35:46,748 INFO [TransactionManagerService] Recovery manager started
14:35:46,748 INFO [TransactionManagerService] Binding TransactionManager JNDI R
eference
14:35:50,263 INFO [EJB3Deployer] Starting java:comp multiplexer
14:35:51,607 INFO [NativeServerConfig] JBoss Web Services - Native
14:35:51,622 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200
803312044)
14:35:52,466 INFO [Embedded] Catalina naming disabled
14:35:52,575 INFO [AprLifecycleListener] The Apache Tomcat Native library which
allows optimal performance in production environments was not found on the java
.library.path: C:\WINDOWS\system32;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32
;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
14:35:52,607 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0
.1-8080
14:35:52,607 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80
09
14:35:52,607 INFO [Catalina] Initialization processed in 147 ms
14:35:52,607 INFO [StandardService] Starting service jboss.web
14:35:52,607 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
14:35:52,638 INFO [Catalina] Server startup in 24 ms
14:35:52,794 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w
eb.deployer/ROOT.war/
14:35:53,560 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/
http-invoker.sar/invoker.war/
14:35:53,669 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/
jbossws.sar/jbossws-context.war/
14:35:53,732 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../
deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
14:35:54,153 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep
loy/management/console-mgr.sar/web-console.war/
14:35:54,513 INFO [MailService] Mail Service bound to java:/Mail
14:35:54,669 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-local-jdbc.rar
14:35:54,763 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-xa-jdbc.rar
14:35:54,856 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-local-jdbc.rar
14:35:54,935 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-xa-jdbc.rar
14:35:55,544 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jms/jms-ra.rar
14:35:55,716 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/mail-ra.rar
14:35:55,903 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/quartz-ra.rar
14:35:55,903 INFO [QuartzResourceAdapter] start quartz!!!
14:35:55,950 INFO [SimpleThreadPool] Job execution threads will use class loade
r of thread: main
14:35:55,950 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
14:35:55,966 INFO [RAMJobStore] RAMJobStore initialized.
14:35:55,966 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzSchedule
r' initialized from default resource file in Quartz package: 'quartz.properties'
14:35:55,966 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
14:35:55,966 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED started.
14:35:56,966 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
14:35:57,200 INFO [A] Bound to JNDI name: queue/A
14:35:57,200 INFO [B] Bound to JNDI name: queue/B
14:35:57,200 INFO [C] Bound to JNDI name: queue/C
14:35:57,200 INFO [D] Bound to JNDI name: queue/D
14:35:57,200 INFO [ex] Bound to JNDI name: queue/ex
14:35:57,216 INFO [testTopic] Bound to JNDI name: topic/testTopic
14:35:57,216 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
14:35:57,216 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
14:35:57,216 INFO [testQueue] Bound to JNDI name: queue/testQueue
14:35:57,231 INFO [UILServerILService] JBossMQ UIL service available at : /127.
0.0.1:8093
14:35:57,263 INFO [DLQ] Bound to JNDI name: queue/DLQ
14:35:57,341 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
14:35:57,794 INFO [TomcatDeployer] deploy, ctxPath=/drools-guvnor, warUrl=.../d
eploy/drools-guvnor.war/
14:36:08,965 INFO [TomcatDeployer] deploy, ctxPath=/drools-server, warUrl=.../d
eploy/drools-server.war/
14:36:09,012 WARN [config] Unable to process deployment descriptor for context
'/drools-server'
14:36:09,371 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep
loy/jmx-console.war/
14:36:09,496 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8
080
14:36:09,512 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
14:36:09,512 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBos
s_4_2_3_GA date=200807181417)] Started in 26s:201ms
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
- 3
- 3
[JBoss JIRA] (AS7-4360) hoernetq acceptor params need to subresources
by Heiko Braun (JIRA)
Heiko Braun created AS7-4360:
--------------------------------
Summary: hoernetq acceptor params need to subresources
Key: AS7-4360
URL: https://issues.jboss.org/browse/AS7-4360
Project: Application Server 7
Issue Type: Feature Request
Components: JMS
Reporter: Heiko Braun
Assignee: Brian Stansberry
Fix For: 7.1.2.Final
i.e. to allow /subsystem=messaging/hornetq-server=default/acceptor=test/param=test:add(value=foobar)
currently I cannot add any parameter
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
- 1
- 3
[JBoss JIRA] (JBRULES-3276) Make Drools javadoc available online
by Richard Calmbach (Created) (JIRA)
Make Drools javadoc available online
------------------------------------
Key: JBRULES-3276
URL: https://issues.jboss.org/browse/JBRULES-3276
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-docs
Affects Versions: 5.3.0.Final, 5.2.0.Final
Reporter: Richard Calmbach
Assignee: Mark Proctor
The javadoc for Drools has not been available online since v5.1.1. If it is somewhere, it is not linked up from the obvious place at http://www.jboss.org/drools/documentation.
Tasks:
1. Make Drools javadoc available online (not just as a download) concurrently with releases.
2. Link to javadoc from http://www.jboss.org/drools/documentation
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
- 2
- 1
[JBoss JIRA] (JBRULES-3335) mvn eclipse:eclipse broken for drools-persistence-jpa
by Adar Dembo (Created) (JIRA)
mvn eclipse:eclipse broken for drools-persistence-jpa
-----------------------------------------------------
Key: JBRULES-3335
URL: https://issues.jboss.org/browse/JBRULES-3335
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.3.1.Final
Reporter: Adar Dembo
Assignee: Mark Proctor
>From a clean repository, I'm seeing a maven error when I run "mvn eclipse:eclipse":
{noformat}
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Drools multiproject
[INFO] Drools :: Core
[INFO] Drools :: Compiler
[INFO] Drools :: Templates
[INFO] Drools :: Decision Tables
[INFO] Drools :: JSR-94 API Module
[INFO] Drools :: Clips
[INFO] Drools :: Verifier
[INFO] Drools :: Persistence :: JPA
[INFO] Drools examples
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Drools multiproject 5.4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-multiproject >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-multiproject ---
[INFO]
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-multiproject <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-multiproject ---
[INFO] Not running eclipse plugin goal for pom project
[INFO] Using Eclipse Workspace: null
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Drools :: Core 5.4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-core >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-core ---
[INFO]
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-core <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-core ---
[INFO] Using Eclipse Workspace: null
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Wrote settings to /home/adar/Source/drools/drools-core/.settings/org.eclipse.jdt.core.prefs
[INFO] Wrote Eclipse project for "drools-core" to /home/adar/Source/drools/drools-core.
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Drools :: Compiler 5.4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-compiler >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-compiler ---
[INFO]
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-compiler <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-compiler ---
[INFO] Using Eclipse Workspace: null
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Wrote settings to /home/adar/Source/drools/drools-compiler/.settings/org.eclipse.jdt.core.prefs
[INFO] Wrote Eclipse project for "drools-compiler" to /home/adar/Source/drools/drools-compiler.
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Drools :: Templates 5.4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-templates >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-templates ---
[INFO]
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-templates <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-templates ---
[INFO] Using Eclipse Workspace: null
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Wrote settings to /home/adar/Source/drools/drools-templates/.settings/org.eclipse.jdt.core.prefs
[INFO] Wrote Eclipse project for "drools-templates" to /home/adar/Source/drools/drools-templates.
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Drools :: Decision Tables 5.4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-decisiontables >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-decisiontables ---
[INFO]
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-decisiontables <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-decisiontables ---
[INFO] Using Eclipse Workspace: null
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Wrote settings to /home/adar/Source/drools/drools-decisiontables/.settings/org.eclipse.jdt.core.prefs
[INFO] Wrote Eclipse project for "drools-decisiontables" to /home/adar/Source/drools/drools-decisiontables.
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Drools :: JSR-94 API Module 5.4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-jsr94 >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-jsr94 ---
[INFO]
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-jsr94 <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-jsr94 ---
[INFO] Using Eclipse Workspace: null
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Wrote settings to /home/adar/Source/drools/drools-jsr94/.settings/org.eclipse.jdt.core.prefs
[INFO] Wrote Eclipse project for "drools-jsr94" to /home/adar/Source/drools/drools-jsr94.
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Drools :: Clips 5.4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-clips >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-clips ---
[INFO]
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-clips <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-clips ---
[INFO] Using Eclipse Workspace: null
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Wrote settings to /home/adar/Source/drools/drools-clips/.settings/org.eclipse.jdt.core.prefs
[INFO] Wrote Eclipse project for "drools-clips" to /home/adar/Source/drools/drools-clips.
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Drools :: Verifier 5.4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-verifier >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-verifier ---
[INFO]
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-verifier <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-verifier ---
[INFO] Using Eclipse Workspace: null
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Wrote settings to /home/adar/Source/drools/drools-verifier/.settings/org.eclipse.jdt.core.prefs
[INFO] Wrote Eclipse project for "drools-verifier" to /home/adar/Source/drools/drools-verifier.
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Drools :: Persistence :: JPA 5.4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-persistence-jpa >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-persistence-jpa ---
[INFO]
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-persistence-jpa <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ drools-persistence-jpa ---
[INFO] Using Eclipse Workspace: null
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Resource directory's path matches an existing source directory. Resources will be merged with the source directory src/test/resources
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Drools multiproject ............................... SUCCESS [0.873s]
[INFO] Drools :: Core .................................... SUCCESS [1.087s]
[INFO] Drools :: Compiler ................................ SUCCESS [0.758s]
[INFO] Drools :: Templates ............................... SUCCESS [0.374s]
[INFO] Drools :: Decision Tables ......................... SUCCESS [0.341s]
[INFO] Drools :: JSR-94 API Module ....................... SUCCESS [0.219s]
[INFO] Drools :: Clips ................................... SUCCESS [0.073s]
[INFO] Drools :: Verifier ................................ SUCCESS [0.102s]
[INFO] Drools :: Persistence :: JPA ...................... FAILURE [0.225s]
[INFO] Drools examples ................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.294s
[INFO] Finished at: Thu Jan 05 15:30:50 PST 2012
[INFO] Final Memory: 27M/618M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse (default-cli) on project drools-persistence-jpa: Request to merge when 'filtering' is not identical. Original=resource src/test/resources: output=target/test-classes, include=[], exclude=[**/*.h2.db|**/*.java], test=true, filtering=true, merging with=resource src/test/resources: output=target/test-classes, include=[**/*.h2.db], exclude=[**/*.java], test=true, filtering=false -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :drools-persistence-jpa
{noformat}
Here's my maven version:
{noformat}
Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800)
Maven home: /home/adar/Source/apache-maven-3.0.3
Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.0.0-14-generic", arch: "amd64", family: "unix"
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
- 2
- 1
[JBoss JIRA] (JBRULES-3404) In drools-camel-server-5.3.x.Final.war, there seems to be duplicate JPA persistence units
by Nicholas DiPiazza (JIRA)
Nicholas DiPiazza created JBRULES-3404:
------------------------------------------
Summary: In drools-camel-server-5.3.x.Final.war, there seems to be duplicate JPA persistence units
Key: JBRULES-3404
URL: https://issues.jboss.org/browse/JBRULES-3404
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-camel
Affects Versions: 5.3.1.Final, 5.3.0.Final
Environment: Causes deployment problem in WebLogic 10.x, but not Tomcat.
Reporter: Nicholas DiPiazza
Assignee: Mark Proctor
There seems to be duplicate persistence units for persistence unit "org.drools.grid"
One in: WEB-INF\classes\META-INF\persistence.xml
Another in: WEB-INF\lib\drools-grid-impl-5.3.0.Final.jar\META-INF\persistence.xml
In Tomcat, it doesn't seem to care and let's you deploy nicely.
In WebLogic 10.x, it will throw an error: "Duplicate persistence unit" and won't let you deploy until you either rename one of them or remove it.
Renaming the WEB-INF\classes\META-INF\persistence.xml's persistence unit another name causes this error:
<Feb 25, 2012 9:07:39 PM GMT-07:00> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request w
ith ID '1330229237884' for task '0'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'drools-camel-ser
ver-5.3.1.Final.war''
weblogic.application.ModuleException: Failed to load webapp: 'drools-camel-server-5.3.1.Final.war'
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:404)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
Truncated. see log file for complete stacktrace
Caused By: org.hibernate.HibernateException: The chosen transaction strategy requires access to the JTA TransactionManager
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:371)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1341)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:132)
Truncated. see log file for complete stacktrace
>
The only way to get it to even deploy is to remove one of the duplicates.
Which one can we remove? Why does this only happen in WebLogic and not in Tomcat? You'd figure the duplicate persistence unit should be complained about in all app server environments???
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
- 2
- 1
[JBoss JIRA] (AS7-4361) CLONE - Console usability: main menu items are not clickable
by Rostislav Svoboda (JIRA)
Rostislav Svoboda created AS7-4361:
--------------------------------------
Summary: CLONE - Console usability: main menu items are not clickable
Key: AS7-4361
URL: https://issues.jboss.org/browse/AS7-4361
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Alpha1
Reporter: Rostislav Svoboda
Assignee: Heiko Braun
Fix For: 7.1.2.Final
You need to click the [+] sign in order to expand. The name of the system (or the whole row should be clickable).
This has been around for a really long time so I am filing this so its not forgotten.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
- 1
- 0
[JBoss JIRA] (AS7-4359) Port the legacy jmx-console to AS7
by Lami Akagwu (JIRA)
Lami Akagwu created AS7-4359:
--------------------------------
Summary: Port the legacy jmx-console to AS7
Key: AS7-4359
URL: https://issues.jboss.org/browse/AS7-4359
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Reporter: Lami Akagwu
Assignee: Darran Lofthouse
Fix For: 7.2.0.Alpha1
I've seen a few people asking for a port of the old jmx-console to AS7, for monitoring purposes, until equivalent functionality is available through the new GWT-based console.
I've ported the old console in this branch:
https://github.com/dandreadis/jboss-as/commits/jmx-console
It only includes a new top-level directory 'jmx-console'. The directory is not build by default, and when you build it manually it does not alter the server configuration in any way, you need to manually copy the resulting target/jboss-as-jmx-console-VERSION.war to the server deployment directory (and rename it to jmx-console.war)
If there is interest, it could be included in the AS7 distro in some top level 'legacy' directory so it is not deployed by default?
The resulting .war is attached on this JIRA, in case someone wants to use it. It work just as well on AS 7.0.2 and the latest AS 7.1.x development branch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
- 1
- 0
[JBoss JIRA] (JBRULES-3340) org.drools.factmodel.AnnotationDefinition is not Serializable
by Robert Perry (Created) (JIRA)
org.drools.factmodel.AnnotationDefinition is not Serializable
-------------------------------------------------------------
Key: JBRULES-3340
URL: https://issues.jboss.org/browse/JBRULES-3340
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-guvnor
Affects Versions: 5.3.1.Final
Environment: Guvnor 5.3.1.Final
JBoss AS 7.0.2.Final
Reporter: Robert Perry
Assignee: Mark Proctor
java.io.NotSerializableException is thrown regarding org.drools.factmodel.AnnotationDefinition when Building Packages in Guvnor including DRL's defining Fact Types using Java Annotations for Meta Data.
Modifying AnnotationDefinition and AnnotationDefinition.AnnotationPropertyVal to implement Serializable, seems to correct this problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
- 3
- 3
[JBoss JIRA] (AS7-4358) testFailoverFromRemoteClientWhenOneNodeGoesDown fails intermittently
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-4358:
-----------------------------------
Summary: testFailoverFromRemoteClientWhenOneNodeGoesDown fails intermittently
Key: AS7-4358
URL: https://issues.jboss.org/browse/AS7-4358
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.1.Final
Reporter: Radoslav Husar
Assignee: jaikiran pai
Priority: Critical
Fix For: 7.1.2.Final
On the first look, this doesn't seem to be a problem with the test, but with implementation. SFSBs should failover with no problems.
{noformat}
Regression
org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.RemoteEJBClientDDBasedSFSBFailoverTestCase(UDP).testFailoverFromRemoteClientWhenOneNodeGoesDown
Failing for the past 1 build (Since Failed#1799 )
Took 27 sec.
Error Message
No EJB receiver contexts available in cluster ejb
Stacktrace
java.lang.IllegalStateException: No EJB receiver contexts available in cluster ejb
at org.jboss.ejb.client.EJBClientContext.requireClusterEJBReceiverContext(EJBClientContext.java:751)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:87)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy25.increment(Unknown Source)
at org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.RemoteEJBClientDDBasedSFSBFailoverTestCase.testFailoverFromRemoteClientWhenOneNodeGoesDown(RemoteEJBClientDDBasedSFSBFailoverTestCase.java:121)
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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270)
at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53)
at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111)
at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263)
at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
Standard Output
18:23:19,193 INFO [org.jboss.ejb.client.remoting.ChannelAssociation] (Remoting "config-based-ejb-client-endpoint" task-4) Channel Channel ID 9fef721a (outbound) of Remoting connection 60a2f435 to /0:0:0:0:0:0:0:1:4447 can no longer process messages
18:23:19,282 INFO [org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.RemoteEJBClientDDBasedSFSBFailoverTestCase] (main) remote-ejb-client-dd-based-stateful-bean-failover-test.jar:
/META-INF/
/META-INF/jboss-ejb3.xml
/org/
/org/jboss/
/org/jboss/as/
/org/jboss/as/test/
/org/jboss/as/test/clustering/
/org/jboss/as/test/clustering/NodeNameGetter.class
/org/jboss/as/test/clustering/cluster/
/org/jboss/as/test/clustering/cluster/ejb3/
/org/jboss/as/test/clustering/cluster/ejb3/stateful/
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/CounterResult.class
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/dd/
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/dd/RemoteEJBClientDDBasedSFSBFailoverTestCase.class
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/dd/DDBasedClusteredSFSB.class
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/RemoteCounter.class
18:23:19,312 INFO [org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.RemoteEJBClientDDBasedSFSBFailoverTestCase] (main) remote-ejb-client-dd-based-stateful-bean-failover-test.jar:
/META-INF/
/META-INF/jboss-ejb3.xml
/org/
/org/jboss/
/org/jboss/as/
/org/jboss/as/test/
/org/jboss/as/test/clustering/
/org/jboss/as/test/clustering/NodeNameGetter.class
/org/jboss/as/test/clustering/cluster/
/org/jboss/as/test/clustering/cluster/ejb3/
/org/jboss/as/test/clustering/cluster/ejb3/stateful/
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/CounterResult.class
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/dd/
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/dd/RemoteEJBClientDDBasedSFSBFailoverTestCase.class
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/dd/DDBasedClusteredSFSB.class
/org/jboss/as/test/clustering/cluster/ejb3/stateful/remote/failover/RemoteCounter.class
18:23:19,340 INFO [org.jboss.arquillian.container.test.impl.client.container.ClientContainerController] (main) Manual starting of a server instance
18:23:19,348 INFO [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/opt/jdk1.6.0_29/bin/java, -Xmx512m, -XX:MaxPermSize=256m, -Djboss.dist=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../../../build/target/jboss-as-7.1.2.Final-SNAPSHOT, -Djava.net.preferIPv4Stack=false, -Djava.net.preferIPv6Addresses=true, -Dts.timeout.factor=100, -Dnode0=::1, -Dnode1=fccc::2, -Dmcast=ff01::1, -Djbossas.ts.submodule.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust, -Djbossas.ts.integ.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/.., -Djbossas.ts.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../.., -Djbossas.project.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../../.., -Djboss.dist=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../../../build/target/jboss-as-7.1.2.Final-SNAPSHOT, -Djboss.inst=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-0, -Djboss.node.name=node-0, -ea, -Djboss.home.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-0, -Dorg.jboss.boot.log.file=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/log/boot.log, -Dlogging.configuration=file:/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/configuration/logging.properties, -Djboss.modules.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../../../build/target/jboss-as-7.1.2.Final-SNAPSHOT/modules, -Djboss.bundles.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../../../build/target/jboss-as-7.1.2.Final-SNAPSHOT/bundles, -jar, /home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-0/jboss-modules.jar, -mp, /home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../../../build/target/jboss-as-7.1.2.Final-SNAPSHOT/modules, -jaxpmodule, javax.xml.jaxp-provider, org.jboss.as.standalone, -server-config, standalone-ha.xml]
18:23:20,037 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
18:23:20,385 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
18:23:20,450 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" starting
18:23:22,657 INFO [org.xnio] XNIO Version 3.0.3.GA
18:23:22,672 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
18:23:22,686 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
18:23:22,711 INFO [org.jboss.remoting] JBoss Remoting version 3.2.4.GA
18:23:22,775 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
18:23:22,798 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 28) JBAS016200: Activating ConfigAdmin Subsystem
18:23:22,845 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem.
18:23:22,850 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 37) JBAS010260: Activating JGroups subsystem.
18:23:22,890 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 42) JBAS011800: Activating Naming Subsystem
18:23:22,930 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 43) JBAS011940: Activating OSGi Subsystem
18:23:22,933 INFO [org.jboss.as.security] (ServerService Thread Pool -- 48) JBAS013101: Activating Security Subsystem
18:23:22,967 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 52) JBAS015537: Activating WebServices Extension
18:23:23,004 INFO [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
18:23:23,035 INFO [org.jboss.as.security] (MSC service thread 1-6) JBAS013100: Current PicketBox version=4.0.7.Final
18:23:23,176 INFO [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service
18:23:23,183 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]
18:23:23,213 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 29) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
18:23:23,347 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
18:23:23,427 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) Starting Coyote HTTP/1.1 on http--0_0_0_0_0_0_0_1-1-8080
18:23:23,435 INFO [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-1) Starting Coyote AJP/1.3 on ajp--0_0_0_0_0_0_0_1-1-8009
18:23:23,443 INFO [org.jboss.modcluster.ModClusterService] (MSC service thread 1-5) Initializing mod_cluster 1.2.1.Beta1
18:23:23,532 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-5) Listening to proxy advertisements on ff01:0:0:0:0:0:0:3:23364
18:23:23,739 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
18:23:23,754 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
18:23:23,759 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
18:23:23,765 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
18:23:24,013 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
18:23:24,144 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/deployments
18:23:24,149 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /0:0:0:0:0:0:0:1%1:9999
18:23:24,149 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /0:0:0:0:0:0:0:1%1:4447
18:23:24,279 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://[0:0:0:0:0:0:0:1%1]:9990
18:23:24,280 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" started in 4673ms - Started 135 of 262 services (126 services are passive or on-demand)
18:23:25,985 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/data/content/0d/a9afad7449a09d5a718de7df3da43268214fba/content
18:23:26,023 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "remote-ejb-client-dd-based-stateful-bean-failover-test.jar"
18:23:26,596 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named DDBasedClusteredSFSB in deployment unit deployment "remote-ejb-client-dd-based-stateful-bean-failover-test.jar" are as follows:
java:global/remote-ejb-client-dd-based-stateful-bean-failover-test/DDBasedClusteredSFSB!org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.RemoteCounter
java:app/remote-ejb-client-dd-based-stateful-bean-failover-test/DDBasedClusteredSFSB!org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.RemoteCounter
java:module/DDBasedClusteredSFSB!org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.RemoteCounter
java:jboss/exported/remote-ejb-client-dd-based-stateful-bean-failover-test/DDBasedClusteredSFSB!org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.RemoteCounter
java:global/remote-ejb-client-dd-based-stateful-bean-failover-test/DDBasedClusteredSFSB
java:app/remote-ejb-client-dd-based-stateful-bean-failover-test/DDBasedClusteredSFSB
java:module/DDBasedClusteredSFSB
18:23:26,914 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011941: Register module: Module "deployment.remote-ejb-client-dd-based-stateful-bean-failover-test.jar:main" from Service Module Loader
18:23:27,276 WARNING [org.jgroups.protocols.UDP] (pool-18-thread-1) send buffer of socket java.net.DatagramSocket@68ed8363 was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
18:23:27,278 WARNING [org.jgroups.protocols.UDP] (pool-18-thread-1) receive buffer of socket java.net.DatagramSocket@68ed8363 was set to 20MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
18:23:27,279 WARNING [org.jgroups.protocols.UDP] (pool-18-thread-1) send buffer of socket java.net.MulticastSocket@29ec6c08 was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
18:23:27,281 WARNING [org.jgroups.protocols.UDP] (pool-18-thread-1) receive buffer of socket java.net.MulticastSocket@29ec6c08 was set to 25MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
18:23:27,289 INFO [stdout] (pool-18-thread-1)
18:23:27,290 INFO [stdout] (pool-18-thread-1) -------------------------------------------------------------------
18:23:27,290 INFO [stdout] (pool-18-thread-1) GMS: address=node-0/ejb, cluster=ejb, physical address=0:0:0:0:0:0:0:1:55200
18:23:27,291 INFO [stdout] (pool-18-thread-1) -------------------------------------------------------------------
18:23:30,175 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-1) ISPN000078: Starting JGroups Channel
18:23:30,193 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-1) ISPN000094: Received new cluster view: [node-0/ejb|0] [node-0/ejb]
18:23:30,198 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-1) ISPN000079: Cache local address is node-0/ejb, physical addresses are [0:0:0:0:0:0:0:1:55200]
18:23:30,217 INFO [org.infinispan.factories.GlobalComponentRegistry] (pool-21-thread-1) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.3.FINAL
18:23:30,453 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-21-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.
18:23:30,461 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-20-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.
18:23:30,514 INFO [org.jboss.as.clustering.infinispan] (pool-21-thread-1) JBAS010281: Started remote-connector-client-mappings cache from ejb container
18:23:31,478 INFO [org.jboss.as.clustering.infinispan] (pool-20-thread-1) JBAS010281: Started repl cache from ejb container
18:23:31,506 INFO [org.jboss.as.clustering] (MSC service thread 1-5) JBAS010238: Number of cluster members: 1
18:23:31,540 INFO [org.jboss.ejb.client.ClusterContext] (ejb-client-cluster-node-connection-creation-3-thread-1) Added a new EJB receiver in cluster context ejb for node node-0. Total nodes in cluster context = 1
18:23:31,676 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-1) ISPN000031: MBeans were successfully registered to the platform mbean server.
18:23:31,713 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-1) JBAS010281: Started org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.DDBasedClusteredSFSB cache from ejb container
18:23:31,948 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "remote-ejb-client-dd-based-stateful-bean-failover-test.jar"
18:23:32,612 INFO [org.jboss.arquillian.container.test.impl.client.container.ClientContainerController] (main) Manual starting of a server instance
18:23:32,625 INFO [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [/opt/jdk1.6.0_29/bin/java, -Xmx512m, -XX:MaxPermSize=256m, -Djboss.dist=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../../../build/target/jboss-as-7.1.2.Final-SNAPSHOT, -Djava.net.preferIPv4Stack=false, -Djava.net.preferIPv6Addresses=true, -Dts.timeout.factor=100, -Dnode0=::1, -Dnode1=fccc::2, -Dmcast=ff01::1, -Djbossas.ts.submodule.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust, -Djbossas.ts.integ.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/.., -Djbossas.ts.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../.., -Djbossas.project.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../../.., -Djboss.dist=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../../../build/target/jboss-as-7.1.2.Final-SNAPSHOT, -Djboss.inst=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-1, -Djboss.node.name=node-1, -Djboss.port.offset=100, -ea, -Djboss.home.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-1, -Dorg.jboss.boot.log.file=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-1/standalone/log/boot.log, -Dlogging.configuration=file:/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-1/standalone/configuration/logging.properties, -Djboss.modules.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../../../build/target/jboss-as-7.1.2.Final-SNAPSHOT/modules, -Djboss.bundles.dir=/home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../../../build/target/jboss-as-7.1.2.Final-SNAPSHOT/bundles, -jar, /home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-1/jboss-modules.jar, -mp, /home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/../../../build/target/jboss-as-7.1.2.Final-SNAPSHOT/modules, -jaxpmodule, javax.xml.jaxp-provider, org.jboss.as.standalone, -server-config, standalone-ha.xml]
18:23:33,232 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
18:23:33,510 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
18:23:33,586 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" starting
18:23:35,298 INFO [org.xnio] XNIO Version 3.0.3.GA
18:23:35,313 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
18:23:35,333 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
18:23:35,357 INFO [org.jboss.remoting] JBoss Remoting version 3.2.4.GA
18:23:35,397 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
18:23:35,406 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 28) JBAS016200: Activating ConfigAdmin Subsystem
18:23:35,463 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem.
18:23:35,512 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 37) JBAS010260: Activating JGroups subsystem.
18:23:35,624 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 42) JBAS011800: Activating Naming Subsystem
18:23:35,626 INFO [org.jboss.as.connector] (MSC service thread 1-6) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
18:23:35,689 INFO [org.jboss.as.security] (ServerService Thread Pool -- 48) JBAS013101: Activating Security Subsystem
18:23:35,701 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 43) JBAS011940: Activating OSGi Subsystem
18:23:35,737 INFO [org.jboss.as.security] (MSC service thread 1-5) JBAS013100: Current PicketBox version=4.0.7.Final
18:23:35,808 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 52) JBAS015537: Activating WebServices Extension
18:23:35,809 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 29) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
18:23:35,861 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
18:23:35,878 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default]
18:23:36,209 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.2.GA
18:23:36,264 INFO [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-3) Starting Coyote AJP/1.3 on ajp--fccc_0_0_0_0_0_0_2-1-8109
18:23:36,268 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-5) Starting Coyote HTTP/1.1 on http--fccc_0_0_0_0_0_0_2-1-8180
18:23:36,331 INFO [org.jboss.modcluster.ModClusterService] (MSC service thread 1-2) Initializing mod_cluster 1.2.1.Beta1
18:23:36,432 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-2) Listening to proxy advertisements on ff01:0:0:0:0:0:0:3:23364
18:23:36,565 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
18:23:36,584 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
18:23:36,598 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
18:23:36,604 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
18:23:36,792 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
18:23:37,048 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /fccc:0:0:0:0:0:0:2%1:10099
18:23:37,049 INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on /fccc:0:0:0:0:0:0:2%1:4547
18:23:37,077 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory /home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-1/standalone/deployments
18:23:37,248 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://[fccc:0:0:0:0:0:0:2%1]:10090
18:23:37,251 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" started in 4421ms - Started 135 of 262 services (126 services are passive or on-demand)
18:23:39,323 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-1/standalone/data/content/e9/50d95fc0606113431b03555676f1e37d9fa530/content
18:23:39,392 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "remote-ejb-client-dd-based-stateful-bean-failover-test.jar"
18:23:39,936 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-5) JNDI bindings for session bean named DDBasedClusteredSFSB in deployment unit deployment "remote-ejb-client-dd-based-stateful-bean-failover-test.jar" are as follows:
java:global/remote-ejb-client-dd-based-stateful-bean-failover-test/DDBasedClusteredSFSB!org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.RemoteCounter
java:app/remote-ejb-client-dd-based-stateful-bean-failover-test/DDBasedClusteredSFSB!org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.RemoteCounter
java:module/DDBasedClusteredSFSB!org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.RemoteCounter
java:jboss/exported/remote-ejb-client-dd-based-stateful-bean-failover-test/DDBasedClusteredSFSB!org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.RemoteCounter
java:global/remote-ejb-client-dd-based-stateful-bean-failover-test/DDBasedClusteredSFSB
java:app/remote-ejb-client-dd-based-stateful-bean-failover-test/DDBasedClusteredSFSB
java:module/DDBasedClusteredSFSB
18:23:40,362 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011941: Register module: Module "deployment.remote-ejb-client-dd-based-stateful-bean-failover-test.jar:main" from Service Module Loader
18:23:40,769 WARNING [org.jgroups.protocols.UDP] (pool-18-thread-1) send buffer of socket java.net.DatagramSocket@2b650cea was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
18:23:40,771 WARNING [org.jgroups.protocols.UDP] (pool-18-thread-1) receive buffer of socket java.net.DatagramSocket@2b650cea was set to 20MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
18:23:40,773 WARNING [org.jgroups.protocols.UDP] (pool-18-thread-1) send buffer of socket java.net.MulticastSocket@305f6ed4 was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
18:23:40,774 WARNING [org.jgroups.protocols.UDP] (pool-18-thread-1) receive buffer of socket java.net.MulticastSocket@305f6ed4 was set to 25MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
18:23:40,781 INFO [stdout] (pool-18-thread-1)
18:23:40,785 INFO [stdout] (pool-18-thread-1) -------------------------------------------------------------------
18:23:40,786 INFO [stdout] (pool-18-thread-1) GMS: address=node-1/ejb, cluster=ejb, physical address=fccc:0:0:0:0:0:0:2:55300
18:23:40,788 INFO [stdout] (pool-18-thread-1) -------------------------------------------------------------------
18:23:40,922 INFO [org.jboss.as.clustering] (Incoming-1,null) JBAS010225: New cluster view for partition ejb (id: 1, delta: 1, merge: false) : [node-0/ejb, node-1/ejb]
18:23:40,926 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,null) ISPN000094: Received new cluster view: [node-0/ejb|1] [node-0/ejb, node-1/ejb]
18:23:41,816 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-1) ISPN000078: Starting JGroups Channel
18:23:41,834 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-1) ISPN000094: Received new cluster view: [node-0/ejb|1] [node-0/ejb, node-1/ejb]
18:23:41,839 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-1) ISPN000079: Cache local address is node-1/ejb, physical addresses are [fccc:0:0:0:0:0:0:2:55300]
18:23:41,858 INFO [org.infinispan.factories.GlobalComponentRegistry] (pool-21-thread-1) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.3.FINAL
18:23:42,409 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-21-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.
18:23:42,442 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-20-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.
18:23:42,694 INFO [org.jboss.as.clustering.infinispan] (pool-20-thread-1) JBAS010281: Started repl cache from ejb container
18:23:42,726 INFO [org.jboss.as.clustering] (MSC service thread 1-1) JBAS010238: Number of cluster members: 2
18:23:43,619 INFO [org.jboss.as.clustering.infinispan] (pool-21-thread-1) JBAS010281: Started remote-connector-client-mappings cache from ejb container
18:23:43,766 INFO [org.jboss.ejb.client.ClusterContext] (ejb-client-cluster-node-connection-creation-3-thread-1) Added a new EJB receiver in cluster context ejb for node node-1. Total nodes in cluster context = 1
18:23:43,897 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-2) ISPN000031: MBeans were successfully registered to the platform mbean server.
18:23:43,964 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-2) JBAS010281: Started org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.DDBasedClusteredSFSB cache from ejb container
18:23:44,115 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "remote-ejb-client-dd-based-stateful-bean-failover-test.jar"
18:23:44,793 INFO [org.jboss.ejb.client.remoting.VersionReceiver] (Remoting "config-based-ejb-client-endpoint" task-1) Received server version 1 and marshalling strategies [river]
18:23:44,799 INFO [org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver] (main) Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@7287c801, receiver=Remoting connection EJB receiver [connection=Remoting connection <28a50395>,channel=jboss.ejb,nodename=node-0]} on channel Channel ID 84a8fc0c (outbound) of Remoting connection 14a82a10 to /0:0:0:0:0:0:0:1:4447
18:23:45,019 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-3) ISPN000029: Passivating all entries to disk
18:23:45,019 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011943: Unregister module: Module "deployment.remote-ejb-client-dd-based-stateful-bean-failover-test.jar:main" from Service Module Loader
18:23:45,044 INFO [org.jboss.ejb.client.ClusterContext] (ejb-client-cluster-node-connection-creation-3-thread-8) Added a new EJB receiver in cluster context ejb for node node-0. Total nodes in cluster context = 1
18:23:45,053 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-3) ISPN000030: Passivated 1 entries in 33 milliseconds
18:23:45,054 INFO [org.jboss.ejb.client.remoting.VersionReceiver] (Remoting "config-based-ejb-client-endpoint" task-2) Received server version 1 and marshalling strategies [river]
18:23:45,057 INFO [org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver] (ejb-client-cluster-node-connection-creation-3-thread-6) Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@7287c801, receiver=Remoting connection EJB receiver [connection=Remoting connection <474ad296>,channel=jboss.ejb,nodename=node-1]} on channel Channel ID 9b31633e (outbound) of Remoting connection 4c397cea to /fccc:0:0:0:0:0:0:2%1:4547
18:23:45,066 INFO [org.infinispan.eviction.PassivationManagerImpl] (pool-20-thread-1) ISPN000029: Passivating all entries to disk
18:23:45,072 INFO [org.infinispan.eviction.PassivationManagerImpl] (pool-20-thread-1) ISPN000030: Passivated 0 entries in 5 milliseconds
18:23:45,088 INFO [org.jboss.ejb.client.ClusterContext] (ejb-client-cluster-node-connection-creation-3-thread-6) Added a new EJB receiver in cluster context ejb for node node-1. Total nodes in cluster context = 2
18:23:45,091 INFO [org.jboss.as.clustering.infinispan] (pool-20-thread-1) JBAS010282: Stopped repl cache from ejb container
18:23:45,103 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment remote-ejb-client-dd-based-stateful-bean-failover-test.jar in 123ms
18:23:45,107 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-3) JBAS010282: Stopped org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.DDBasedClusteredSFSB cache from ejb container
18:23:45,122 INFO [org.jboss.as.clustering.infinispan] (pool-21-thread-1) JBAS010282: Stopped remote-connector-client-mappings cache from ejb container
18:23:45,222 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-19-thread-1) ISPN000082: Stopping the RpcDispatcher
18:23:45,256 INFO [org.jboss.as.clustering] (Incoming-7,null) JBAS010225: New cluster view for partition ejb (id: 2, delta: -1, merge: false) : [node-1/ejb]
18:23:45,258 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-7,null) ISPN000094: Received new cluster view: [node-1/ejb|2] [node-1/ejb]
18:23:45,602 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/data/content/0d/a9afad7449a09d5a718de7df3da43268214fba/content
18:23:45,606 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "remote-ejb-client-dd-based-stateful-bean-failover-test.jar"
18:23:45,612 INFO [org.jboss.arquillian.container.test.impl.client.container.ClientContainerController] (main) Manual stopping of a server instance
18:23:45,774 INFO [org.jboss.ejb.client.remoting.ChannelAssociation] (Remoting "config-based-ejb-client-endpoint" task-3) Channel Channel ID 84a8fc0c (outbound) of Remoting connection 14a82a10 to /0:0:0:0:0:0:0:1:4447 can no longer process messages
18:23:46,059 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011943: Unregister module: Module "deployment.remote-ejb-client-dd-based-stateful-bean-failover-test.jar:main" from Service Module Loader
18:23:46,063 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-2) ISPN000029: Passivating all entries to disk
18:23:46,127 INFO [org.infinispan.eviction.PassivationManagerImpl] (pool-20-thread-1) ISPN000029: Passivating all entries to disk
18:23:46,134 INFO [org.infinispan.eviction.PassivationManagerImpl] (pool-20-thread-1) ISPN000030: Passivated 0 entries in 4 milliseconds
18:23:46,138 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-2) ISPN000030: Passivated 1 entries in 74 milliseconds
18:23:46,153 INFO [org.jboss.as.clustering.infinispan] (pool-21-thread-1) JBAS010282: Stopped remote-connector-client-mappings cache from ejb container
18:23:46,153 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment remote-ejb-client-dd-based-stateful-bean-failover-test.jar in 116ms
18:23:46,155 INFO [org.jboss.as.clustering.infinispan] (pool-20-thread-1) JBAS010282: Stopped repl cache from ejb container
18:23:46,178 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-2) JBAS010282: Stopped org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.DDBasedClusteredSFSB cache from ejb container
18:23:46,408 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-19-thread-1) ISPN000082: Stopping the RpcDispatcher
18:23:46,511 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/jenkins/jenkins-work/workspace/as7-param-pull/testsuite/integration/clust/target/jbossas-clustering-udp-1/standalone/data/content/e9/50d95fc0606113431b03555676f1e37d9fa530/content
18:23:46,514 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "remote-ejb-client-dd-based-stateful-bean-failover-test.jar"
18:23:46,519 INFO [org.jboss.arquillian.container.test.impl.client.container.ClientContainerController] (main) Manual stopping of a server instance
18:23:46,646 INFO [org.jboss.ejb.client.remoting.ChannelAssociation] (Remoting "config-based-ejb-client-endpoint" task-2) Channel Channel ID 9b31633e (outbound) of Remoting connection 4c397cea to /fccc:0:0:0:0:0:0:2%1:4547 can no longer process messages
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
- 2
- 3