[JBoss JIRA] Created: (AS7-1447) data-source connection-url is not writable
by Nicklas Karlsson (JIRA)
data-source connection-url is not writable
------------------------------------------
Key: AS7-1447
URL: https://issues.jboss.org/browse/AS7-1447
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.Final
Reporter: Nicklas Karlsson
Assignee: Jesper Pedersen
Trying to edit the JDBC URL of a datasource gives
22:51:00,148 ERROR [org.jboss.as.controller] (HttpManagementService-threads - 1)
Operation ("write-attribute") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "java:jboss/datasources/ExampleDS")
]) - failure description: "Attribute connection-url is not writeable"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBRULES-3259) Full build gives a strange warning "[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory."
by Toni Rikkola (Created) (JIRA)
Full build gives a strange warning "[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory."
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-3259
URL: https://issues.jboss.org/browse/JBRULES-3259
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.3.0.Final
Reporter: Toni Rikkola
Assignee: Geoffrey De Smet
Priority: Minor
Happens on several modules, here is an example of the log:
[INFO] ------------------------------------------------------------------------
[INFO] Building Drools distribution 5.3.0.Final
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ drools-distribution ---
[INFO] Deleting /Users/rikkola/Codes/drools/drools/drools-distribution/target
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-distribution ---
[INFO]
[INFO] >>> maven-source-plugin:2.1.2:jar (default) @ drools-distribution >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-distribution ---
[INFO]
[INFO] <<< maven-source-plugin:2.1.2:jar (default) @ drools-distribution <<<
[INFO]
[INFO] --- maven-source-plugin:2.1.2:jar (default) @ drools-distribution ---
[INFO]
[INFO] >>> maven-source-plugin:2.1.2:test-jar (default) @ drools-distribution >>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-distribution ---
[INFO]
[INFO] <<< maven-source-plugin:2.1.2:test-jar (default) @ drools-distribution <<<
[INFO]
[INFO] --- maven-source-plugin:2.1.2:test-jar (default) @ drools-distribution ---
[INFO]
[INFO] --- maven-javadoc-plugin:2.7:jar (default) @ drools-distribution ---
[INFO] Not executing Javadoc as the project is not a Java classpath-capable package
[INFO]
[INFO] --- maven-assembly-plugin:2.2.1:single (default) @ drools-distribution ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly-drools.xml
[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory.
[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory.
[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory.
[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory.
[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory.
[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory.
[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory.
[INFO] Copying files to /Users/rikkola/Codes/drools/drools/drools-distribution/target/drools-distribution-5.3.0.Final
--
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
12 years, 8 months
[JBoss JIRA] (JBMESSAGING-1901) Deadlock when a node is being shutdown by the MessagingClusterHealthMBean if the DB and Network is broken at the same time
by Yong Hao Gao (Created) (JIRA)
Deadlock when a node is being shutdown by the MessagingClusterHealthMBean if the DB and Network is broken at the same time
--------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1901
URL: https://issues.jboss.org/browse/JBMESSAGING-1901
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.8.SP3, 1.4.0.SP3.CP14
Reporter: Yong Hao Gao
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP4
The stack trace shows the deadlock:
"Thread-23":
waiting to lock monitor 0x0000000001681638 (object 0x00000000d730fa60, a org.jboss.jms.server.MessagingClusterHealthMBean),
which is held by "Incoming-13,192.168.1.110:55200"
"Incoming-13,192.168.1.110:55200":
waiting to lock monitor 0x0000000001681c20 (object 0x00000000d92e1580, a org.jboss.messaging.core.impl.postoffice.MessagingPostOffice$StateMonitor),
which is held by "Thread-23"
Java stack information for the threads listed above:
===================================================
"Thread-23":
at org.jboss.jms.server.MessagingClusterHealthMBean.stopNodeOnDBFailure(MessagingClusterHealthMBean.java:94)
- waiting to lock <0x00000000d730fa60> (a org.jboss.jms.server.MessagingClusterHealthMBean)
at org.jboss.jms.server.ServerPeer.stopJBMNodeForRecovery(ServerPeer.java:2115)
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice$StateMonitor.run(MessagingPostOffice.java:4256)
- locked <0x00000000d92e1580> (a org.jboss.messaging.core.impl.postoffice.MessagingPostOffice$StateMonitor)
"Incoming-13,192.168.1.110:55200":
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice$StateMonitor.shutdown(MessagingPostOffice.java:4280)
- waiting to lock <0x00000000d92e1580> (a org.jboss.messaging.core.impl.postoffice.MessagingPostOffice$StateMonitor)
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.stop(MessagingPostOffice.java:797)
at org.jboss.messaging.core.jmx.MessagingPostOfficeService.stopService(MessagingPostOfficeService.java:554)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:405)
at org.jboss.system.ServiceMBeanSupport.stop(ServiceMBeanSupport.java:281)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.jms.server.MessagingClusterHealthMBean.stopService(MessagingClusterHealthMBean.java:140)
at org.jboss.jms.server.MessagingClusterHealthMBean.stopNodeOnDBFailure(MessagingClusterHealthMBean.java:107)
- locked <0x00000000d730fa60> (a org.jboss.jms.server.MessagingClusterHealthMBean)
at org.jboss.jms.server.ServerPeer.stopJBMNodeForRecovery(ServerPeer.java:2115)
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.quarantine(MessagingPostOffice.java:1751)
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.nodesLeft(MessagingPostOffice.java:1571)
at org.jboss.messaging.core.impl.postoffice.GroupMember$ControlMembershipListener.viewAccepted(GroupMember.java:609)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUpEvent(MessageDispatcher.java:733)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:776)
at org.jgroups.JChannel.up(JChannel.java:1336)
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:454)
at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:439)
at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:153)
at org.jgroups.protocols.FRAG2.up(FRAG2.java:188)
at org.jgroups.protocols.FC.up(FC.java:493)
at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:543)
- locked <0x00000000d92a8ae0> (a org.jgroups.Membership)
at org.jgroups.protocols.pbcast.CoordGmsImpl.handleViewChange(CoordGmsImpl.java:463)
at org.jgroups.protocols.pbcast.GMS.up(GMS.java:749)
at org.jgroups.protocols.VIEW_SYNC.up(VIEW_SYNC.java:192)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:233)
at org.jgroups.protocols.UNICAST.up(UNICAST.java:328)
at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:895)
at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:708)
at org.jgroups.protocols.BARRIER.up(BARRIER.java:136)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
at org.jgroups.protocols.FD.up(FD.java:284)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:328)
at org.jgroups.protocols.MERGE2.up(MERGE2.java:144)
at org.jgroups.protocols.Discovery.up(Discovery.java:264)
at org.jgroups.protocols.PING.up(PING.java:273)
at org.jgroups.protocols.TP$ProtocolAdapter.up(TP.java:2319)
at org.jgroups.protocols.TP.passMessageUp(TP.java:1253)
at org.jgroups.protocols.TP.access$100(TP.java:50)
at org.jgroups.protocols.TP$1.run(TP.java:1177)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Found 1 deadlock.
--
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
12 years, 8 months
[JBoss JIRA] (AS7-2173) Undeploy failure shadows deployment failure for ARQ tests
by Thomas Diesler (Created) (JIRA)
Undeploy failure shadows deployment failure for ARQ tests
---------------------------------------------------------
Key: AS7-2173
URL: https://issues.jboss.org/browse/AS7-2173
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Reporter: Thomas Diesler
Assignee: Andrew Rubinger
{code}
04:22:14,469 INFO [org.jboss.as.server.deployment] (pool-2-thread-1) Content added at location /home/ondra/work/AS-7/ozizka-as7/testsuite/integration/target/jbossas/standalone/data/content/bf/815f1962565545e298089d58c3988d770833cb/content
04:22:14,470 INFO [org.jboss.as.server.deployment] (MSC service thread 1-10) Starting deployment of "resteasy-osgi-client.war"
04:22:14,677 INFO [org.jboss.as.server.controller] (pool-2-thread-1) Deployment of "resteasy-osgi-client.war" was rolled back with failure message {"Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"resteasy-osgi-client.war\".CONFIGURE_MODULE missing [ jboss.module.information.service.\"deployment.osgi.cmpn\".\"4.2.0.200908310645\" ]"]}
04:22:14,678 INFO [org.jboss.as.server.deployment] (MSC service thread 1-10) Stopped deployment resteasy-osgi-client.war in 1ms
04:22:14,685 ERROR [org.jboss.as.controller] (pool-2-thread-1) Operation ("undeploy") failed - address: ([("deployment" => "resteasy-osgi-client.war")]): java.util.NoSuchElementException: No child 'runtime-name' exists
at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:362) [jboss-dmr-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.dmr.ModelNode.require(ModelNode.java:703) [jboss-dmr-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.as.server.deployment.DeploymentUndeployHandler.execute(DeploymentUndeployHandler.java:58)
{code}
--
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
12 years, 8 months
[JBoss JIRA] Created: (AS7-1881) Some property in resource-adapters are duplicated in wrong positions
by Stefano Maestri (JIRA)
Some property in resource-adapters are duplicated in wrong positions
--------------------------------------------------------------------
Key: AS7-1881
URL: https://issues.jboss.org/browse/AS7-1881
Project: Application Server 7
Issue Type: Clarification
Components: JCA
Reporter: Stefano Maestri
Assignee: Stefano Maestri
Fix For: 7.1.0.Beta1
{noformat}
[standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=xmpp-ra.rar:read-resource
{
"outcome" => "success",
"result" => {
"archive" => "xmpp-ra.rar",
"background-validation" => undefined,
"background-validation-millis" => undefined,
"blocking-timeout-wait-millis" => undefined,
"config-properties" => {"host" => "talk.google.om"},
"connection-definitions" => [{
"class-name" => "com.ramphastos.xmpp.XmppConnectionFactory",
"jndi-name" => "xmpp",
"pool-name" => "xmpp-ra_rar-Pool",
"min-pool-size" => 10,
"max-pool-size" => 100
}],
"flush-strategy" => undefined,
"idle-timeout-minutes" => undefined,
"max-pool-size" => undefined,
"min-pool-size" => undefined,
"pool-prefill" => undefined,
"pool-use-strict-min" => undefined,
"transaction-support" => "NoTransaction"
}
}
{noformat}
why two times min/max-pool-size? which one to rely on?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (AS7-1665) Problem with JBoss 7
by Peter Penzov (JIRA)
Problem with JBoss 7
--------------------
Key: AS7-1665
URL: https://issues.jboss.org/browse/AS7-1665
Project: Application Server 7
Issue Type: Enhancement
Reporter: Peter Penzov
Priority: Minor
rcbandit@rcbandit-laptop:~/Desktop/jboss-as-7.0.1.Final/bin$ ./domain.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/rcbandit/Desktop/jboss-as-7.0.1.Final
JAVA: java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman
=========================================================================
12:17:36,671 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
12:17:38,033 INFO [org.jboss.as.process.Host Controller.status] (main) Starting process 'Host Controller'
[Host Controller] 12:17:38,606 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
[Host Controller] 12:17:39,953 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.0.GA
[Host Controller] 12:17:41,139 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.0.Beta2
[Host Controller] 12:17:41,287 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.0.Beta3
[Host Controller] 12:17:41,457 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.0.Beta3
[Host Controller] 12:17:46,885 WARN [org.jboss.as] (Controller Boot Thread) No security realm defined for native management service, all access will be unrestricted.
[Host Controller] 12:17:46,892 INFO [org.jboss.as] (Controller Boot Thread) creating http management service using network interface (management) port (9990)
[Host Controller] 12:17:46,926 WARN [org.jboss.as] (Controller Boot Thread) No security realm defined for http management service, all access will be unrestricted.
[Host Controller] 12:17:47,502 INFO [org.jboss.as.remoting] (MSC service thread 1-4) Listening on /127.0.0.1:9999
[Host Controller] 12:17:47,629 INFO [org.jboss.as.host.controller] (Controller Boot Thread) Starting server server-one
12:17:47,693 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) Starting process 'Server:server-one'
[Host Controller] 12:17:48,044 INFO [org.jboss.as.host.controller] (Controller Boot Thread) Starting server server-two
12:17:48,115 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 3) Starting process 'Server:server-two'
[Server:server-one] 12:17:49,082 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
[Server:server-two] 12:17:49,087 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
[Server:server-two] 12:17:50,023 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.0.GA
[Server:server-one] 12:17:50,044 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.0.GA
[Server:server-two] 12:17:50,197 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.1.Final "Zap" starting
[Server:server-one] 12:17:50,250 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.1.Final "Zap" starting
[Server:server-one] 12:17:52,015 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: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/lib/jvm/java-6-openjdk/jre/lib/i386/server:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/java/packages/lib/i386:/usr/lib/i386-linux-gnu/jni:/lib/i386-linux-gnu:/usr/lib/i386-linux-gnu:/usr/lib/jni:/lib:/usr/lib
[Server:server-two] 12:17:52,018 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-3) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/lib/jvm/java-6-openjdk/jre/lib/i386/server:/usr/lib/jvm/java-6-openjdk/jre/lib/i386:/usr/lib/jvm/java-6-openjdk/jre/../lib/i386:/usr/java/packages/lib/i386:/usr/lib/i386-linux-gnu/jni:/lib/i386-linux-gnu:/usr/lib/i386-linux-gnu:/usr/lib/jni:/lib:/usr/lib
[Server:server-one] 12:17:52,341 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
[Server:server-two] 12:17:52,344 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8230
[Server:server-two] 12:17:52,677 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32010: JBossTS Recovery Service (tag: JBOSSTS_4_15_3_Final) - JBoss Inc.
[Server:server-one] 12:17:52,695 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-2) ARJUNA32010: JBossTS Recovery Service (tag: JBOSSTS_4_15_3_Final) - JBoss Inc.
[Server:server-one] 12:17:52,702 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
[Server:server-two] 12:17:52,716 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA12324: Start RecoveryActivators
[Server:server-two] 12:17:52,778 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
[Server:server-one] 12:17:52,815 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-2) ARJUNA12324: Start RecoveryActivators
[Server:server-two] 12:17:52,826 INFO [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA12296: ExpiredEntryMonitor running at Mon, 29 Aug 2011 12:17:52
[Server:server-one] 12:17:52,865 INFO [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA12296: ExpiredEntryMonitor running at Mon, 29 Aug 2011 12:17:52
[Server:server-two] 12:17:52,881 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA12343: RecoveryManagerImple is ready. Socket listener is turned off.
[Server:server-two] 12:17:52,881 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32013: Starting transaction recovery manager
[Server:server-one] 12:17:52,967 INFO [com.arjuna.ats.arjuna] (MSC service thread 1-2) ARJUNA12343: RecoveryManagerImple is ready. Socket listener is turned off.
[Server:server-one] 12:17:52,967 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-2) ARJUNA32013: Starting transaction recovery manager
[Server:server-two] 12:17:52,984 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA32017: JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_15_3_Final) - JBoss Inc.
[Server:server-one] 12:17:53,021 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-2) ARJUNA32017: JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_15_3_Final) - JBoss Inc.
[Server:server-two] 12:17:53,052 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
[Server:server-one] 12:17:53,050 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
[Server:server-one] 12:17:53,080 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.0.Beta2
[Server:server-two] 12:17:53,087 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.0.Beta2
[Server:server-one] 12:17:53,222 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.0.Beta3
[Server:server-two] 12:17:53,222 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.0.Beta3
[Server:server-two] 12:17:53,282 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.0.Beta3
[Server:server-one] 12:17:53,319 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
[Server:server-one] 12:17:53,323 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.0.Beta3
[Server:server-two] 12:17:53,458 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
[Server:server-one] 12:17:53,501 INFO [org.jboss.as.naming] (MSC service thread 1-1) Starting Naming Service
[Server:server-two] 12:17:53,636 INFO [org.jboss.as.naming] (MSC service thread 1-4) Starting Naming Service
[Server:server-two] 12:17:53,881 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-4) Starting remote JMX connector
[Server:server-one] 12:17:53,881 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1) Starting remote JMX connector
[Server:server-one] 12:17:54,237 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
[Server:server-one] 12:17:54,278 INFO [org.jboss.as.connector] (MSC service thread 1-2) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
[Server:server-two] 12:17:54,288 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
[Server:server-two] 12:17:54,455 INFO [org.jboss.as.connector] (MSC service thread 1-2) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
[Host Controller] 12:17:55,350 INFO [org.jboss.as.host.controller.mgmt] (pool-3-thread-1) Server [Server:server-one] registered using connection [org.jboss.as.protocol.mgmt.ManagementChannel@5facbd]
[Host Controller] 12:17:55,375 INFO [org.jboss.as.host.controller.mgmt] (pool-3-thread-2) Server [Server:server-two] registered using connection [org.jboss.as.protocol.mgmt.ManagementChannel@b124fa]
[Host Controller] 12:17:55,405 INFO [org.jboss.host.controller] (pool-3-thread-2) Registering server server-two
[Host Controller] 12:17:55,406 INFO [org.jboss.host.controller] (pool-3-thread-1) Registering server server-one
[Server:server-two] 12:17:55,656 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
[Server:server-one] 12:17:55,656 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
[Server:server-one] 12:17:55,711 INFO [org.jboss.as.logging] (MSC service thread 1-4) Removing bootstrap log handlers
[Server:server-two] 12:17:55,758 INFO [org.jboss.as.logging] (MSC service thread 1-4) Removing bootstrap log handlers
[Server:server-one] 12:17:55,831 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) Bound data source [java:jboss/datasources/ExampleDS]
[Server:server-two] 12:17:55,835 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) Bound data source [java:jboss/datasources/ExampleDS]
[Server:server-one] 12:17:56,972 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
[Server:server-two] 12:17:56,972 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
[Server:server-one] 12:17:57,035 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 8915ms - Started 87 of 138 services (51 services are passive or on-demand)
[Server:server-two] 12:17:57,043 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 8758ms - Started 87 of 138 services (51 services are passive or on-demand)
[Host Controller] 12:20:06,708 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856
[Host Controller] 12:20:12,786 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months