[JBoss JIRA] Created: (AS7-1459) Add a commandline flag to the startup script to enable debugging
by Dan Allen (JIRA)
Add a commandline flag to the startup script to enable debugging
----------------------------------------------------------------
Key: AS7-1459
URL: https://issues.jboss.org/browse/AS7-1459
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Affects Versions: 7.0.0.Final
Reporter: Dan Allen
Assignee: Alexey Loubyansky
The startup script (standalone.sh & standalone.bat) should honor a commandline option that can be used to start the server with debugging enabled. Currently, the developer has to uncomment the JAVA_OPTS line in the standalone.conf file manually.
Proposal for starting the server with debugging enabled:
./bin/standalone.sh --debug
If necessary, the optional flag could accept the port as an optional argument.
./bin/standalone.sh --debug 8787
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-4461) Operation transformation infrastructure
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-4461:
-------------------------------------
Summary: Operation transformation infrastructure
Key: AS7-4461
URL: https://issues.jboss.org/browse/AS7-4461
Project: Application Server 7
Issue Type: Sub-task
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Ability for extensions to register operation transformers. (This will likely be part of the resource transformation task AS7-4457.) Hooks to access that transformation registry during operation execution. This is to include:
1) Host level operations that target the slave HC directly but are proxied by the master HC.
2) Server level operations that target the slave HC's servers directly but are proxied by the master HC.
3) The first phase of domain-wide 2 phase operations where the master HC transmits the op to the slave HCs.
4) The second phase of domain-wide 2 phase operations where the master HC transmits server-level ops to the slave HCs for forwarding to their servers.
Item 4) above may be simple, as all the master HC is doing is executing ops according to instructions provided by the slave HCs in step 3). Those instructions will be correct for that slave HC.
--
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
13 years, 9 months
[JBoss JIRA] (AS7-5279) Clustering passivation tests fail intermittently
by Jason Greene (JIRA)
Jason Greene created AS7-5279:
---------------------------------
Summary: Clustering passivation tests fail intermittently
Key: AS7-5279
URL: https://issues.jboss.org/browse/AS7-5279
Project: Application Server 7
Issue Type: Bug
Reporter: Jason Greene
Assignee: Radoslav Husar
Fix For: 7.2.0.CR1
These have been disabled for now.
org.jboss.as.test.clustering.cluster.web.passivation.SessionBasedSessionPassivationTestCase(UDP).testSessionPassivationWithMaxIdleTime
Failing for the past 1 build (Since #4433 )
Took 20 sec.
add description
Error Message
Session should have activated and have been deserialized
Stacktrace
junit.framework.AssertionFailedError: Session should have activated and have been deserialized
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.jboss.as.test.clustering.cluster.web.passivation.SessionPassivationAbstractCase.testSessionPassivationWithMaxIdleTime(SessionPassivationAbstractCase.java:111)
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:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
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:135)
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.JUnit4Provider.execute(JUnit4Provider.java:234)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
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:188)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
Standard Output
passivating-session.war:
/WEB-INF/
/WEB-INF/jboss-web.xml
/WEB-INF/web.xml
/WEB-INF/classes/
/WEB-INF/classes/org/
/WEB-INF/classes/org/jboss/
/WEB-INF/classes/org/jboss/as/
/WEB-INF/classes/org/jboss/as/test/
/WEB-INF/classes/org/jboss/as/test/clustering/
/WEB-INF/classes/org/jboss/as/test/clustering/single/
/WEB-INF/classes/org/jboss/as/test/clustering/single/web/
/WEB-INF/classes/org/jboss/as/test/clustering/single/web/SimpleServlet$Custom.class
/WEB-INF/classes/org/jboss/as/test/clustering/single/web/SimpleServlet.class
passivating-session.war:
/WEB-INF/
/WEB-INF/jboss-web.xml
/WEB-INF/web.xml
/WEB-INF/classes/
/WEB-INF/classes/org/
/WEB-INF/classes/org/jboss/
/WEB-INF/classes/org/jboss/as/
/WEB-INF/classes/org/jboss/as/test/
/WEB-INF/classes/org/jboss/as/test/clustering/
/WEB-INF/classes/org/jboss/as/test/clustering/single/
/WEB-INF/classes/org/jboss/as/test/clustering/single/web/
/WEB-INF/classes/org/jboss/as/test/clustering/single/web/SimpleServlet$Custom.class
/WEB-INF/classes/org/jboss/as/test/clustering/single/web/SimpleServlet.class
Sun Jul 29 13:56:07 EDT 2012starting deployment=deployment-0, container=container-0
13:56:07,503 INFO [org.jboss.arquillian.container.test.impl.client.container.ClientContainerController] (main) Manual starting of a server instance
13:56:07,518 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-master-testsuite/testsuite/integration/clust/../../../build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT, -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv6Addresses=false, -Dts.timeout.factor=100, -Dnode0=127.0.0.1, -Dnode1=127.0.0.1, -Dmcast=230.0.0.4, -Djbossas.ts.submodule.dir=/home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust, -Djbossas.ts.integ.dir=/home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/.., -Djbossas.ts.dir=/home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/../.., -Djbossas.project.dir=/home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/../../.., -Djboss.dist=/home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/../../../build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT, -Djboss.inst=/home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/target/jbossas-clustering-udp-0, -Djboss.node.name=node-0, -ea, -Djboss.home.dir=/home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/target/jbossas-clustering-udp-0, -Dorg.jboss.boot.log.file=/home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/log/boot.log, -Dlogging.configuration=file:/home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/configuration/logging.properties, -Djboss.bundles.dir=/home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/../../../build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/bundles, -jar, /home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/target/jbossas-clustering-udp-0/jboss-modules.jar, -mp, /home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/../../../build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules, -jaxpmodule, javax.xml.jaxp-provider, org.jboss.as.standalone, -server-config, standalone-ha.xml]
13:56:08,101 INFO [org.jboss.modules] JBoss Modules version 1.1.2.GA
13:56:08,371 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
13:56:08,458 INFO [org.jboss.as] JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting
13:56:10,219 INFO [org.xnio] XNIO Version 3.0.5.GA
13:56:10,223 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
13:56:10,229 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.5.GA
13:56:10,240 INFO [org.jboss.remoting] JBoss Remoting version 3.2.8.GA
13:56:10,274 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
[0m13:56:10,290 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 29) JBAS016200: Activating ConfigAdmin Subsystem
[0m[0m13:56:10,307 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 34) JBAS010280: Activating Infinispan subsystem.
[0m[0m13:56:10,326 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 38) JBAS010260: Activating JGroups subsystem.
[0m[0m13:56:10,387 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 45) JBAS011906: Activating OSGi Subsystem
[0m[0m13:56:10,398 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 44) JBAS011800: Activating Naming Subsystem
[0m[0m13:56:10,405 INFO [org.jboss.as.security] (ServerService Thread Pool -- 50) JBAS013171: Activating Security Subsystem
[0m[0m13:56:10,441 INFO [org.jboss.as.security] (MSC service thread 1-6) JBAS013170: Current PicketBox version=4.0.9.Final
[0m[0m13:56:10,506 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension
[0m[0m13:56:10,538 INFO [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.11.Final)
[0m[0m13:56:10,586 INFO [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service
[0m[0m13:56:10,624 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
[0m[0m13:56:10,878 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
[0m[0m13:56:11,055 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.1.0.Beta1
[0m[0m13:56:11,198 INFO [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-1) Starting Coyote AJP/1.3 on ajp-/127.0.0.1:8009
[0m[0m13:56:11,218 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-5) Starting Coyote HTTP/1.1 on http-/127.0.0.1:8080
[0m[0m13:56:11,367 INFO [org.jboss.modcluster.ModClusterService] (ServerService Thread Pool -- 56) Initializing mod_cluster 1.2.1.Final
[0m[0m13:56:11,422 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (ServerService Thread Pool -- 56) Listening to proxy advertisements on 224.0.1.105:23,364
[0m[0m13:56:11,536 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 34) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[0m13:56:11,554 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 34) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[0m13:56:11,692 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/deployments
[0m[0m13:56:11,707 INFO [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on 127.0.0.1:4447
[0m[0m13:56:11,707 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:9999
[0m[0m13:56:11,721 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
[0m[0m13:56:11,839 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
[0m[0m13:56:11,840 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
[0m[0m13:56:11,841 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" started in 4040ms - Started 138 of 280 services (141 services are passive or on-demand)
[0m[0m13:56:14,216 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/data/content/84/b127e0e0c2cc54b595d7ceb90de1fe084586ea/content
[0m[0m13:56:14,275 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "passivating-session.war"
[0m[0m13:56:14,736 INFO [org.jboss.osgi.framework] (MSC service thread 1-5) JBOSGI011006: OSGi Framework - 2.0.0.CR13
[0m[0m13:56:15,871 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[0m13:56:15,872 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[0m13:56:15,901 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[33m13:56:16,315 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 3) send buffer of socket java.net.DatagramSocket@46d8dc2e 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)
[0m[33m13:56:16,318 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 3) receive buffer of socket java.net.DatagramSocket@46d8dc2e 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)
[0m[33m13:56:16,320 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 3) send buffer of socket java.net.MulticastSocket@4bcf6203 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)
[0m[33m13:56:16,323 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 3) receive buffer of socket java.net.MulticastSocket@4bcf6203 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)
[0m[0m13:56:16,341 INFO [stdout] (ServerService Thread Pool -- 3)
[0m[0m13:56:16,342 INFO [stdout] (ServerService Thread Pool -- 3) -------------------------------------------------------------------
[0m[0m13:56:16,344 INFO [stdout] (ServerService Thread Pool -- 3) GMS: address=node-0/web, cluster=web, physical address=127.0.0.1:55200
[0m[0m13:56:16,345 INFO [stdout] (ServerService Thread Pool -- 3) -------------------------------------------------------------------
[0m[0m13:56:18,575 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 3) ISPN000078: Starting JGroups Channel
[0m[0m13:56:18,599 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 3) ISPN000094: Received new cluster view: [node-0/web|0] [node-0/web]
[0m[0m13:56:18,603 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 3) ISPN000079: Cache local address is node-0/web, physical addresses are [127.0.0.1:55200]
[0m[0m13:56:18,620 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 3) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.5.FINAL
[0m[0m13:56:18,623 INFO [org.infinispan.config.ConfigurationValidatingVisitor] (ServerService Thread Pool -- 3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[0m13:56:18,846 INFO [org.infinispan.config.ConfigurationValidatingVisitor] (ServerService Thread Pool -- 28) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[0m13:56:18,923 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 28) ISPN000031: MBeans were successfully registered to the platform mbean server.
[0m[0m13:56:18,943 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 3) ISPN000031: MBeans were successfully registered to the platform mbean server.
[0m[0m13:56:18,956 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 28) JBAS010281: Started default-host/passivating-session cache from web container
[0m[0m13:56:18,958 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 3) JBAS010281: Started repl cache from web container
[0m[0m13:56:18,994 INFO [org.jboss.as.clustering] (MSC service thread 1-6) JBAS010238: Number of cluster members: 1
[0m[0m13:56:19,028 INFO [org.jboss.web] (MSC service thread 1-5) JBAS018210: Register web context: /passivating-session
[0m[0m13:56:19,106 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[0m13:56:19,136 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[0m13:56:19,139 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[0m13:56:19,141 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[0m13:56:19,689 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "passivating-session.war"
[0mSun Jul 29 13:56:20 EDT 2012started deployment=deployment-0, container=container-0
[0m13:56:46,229 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018224: Unregister web context: /passivating-session
[0m[0m13:56:46,322 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-5) ISPN000029: Passivating all entries to disk
[0m[0m13:56:46,352 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-5) ISPN000030: Passivated 1 entries in 29 milliseconds
[0m[0m13:56:46,364 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-5) JBAS010282: Stopped default-host/passivating-session cache from web container
[0m[0m13:56:46,398 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-1) ISPN000029: Passivating all entries to disk
[0m[0m13:56:46,402 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-1) ISPN000030: Passivated 0 entries in 3 milliseconds
[0m[0m13:56:46,431 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-1) JBAS010282: Stopped repl cache from web container
[0m[0m13:56:46,433 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment passivating-session.war in 238ms
[0m[0m13:56:46,498 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000082: Stopping the RpcDispatcher
[0m[0m13:56:46,559 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/jenkins/jenkins-work/workspace/as7-master-testsuite/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/data/content/84/b127e0e0c2cc54b595d7ceb90de1fe084586ea/content
[0m[0m13:56:46,562 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "passivating-session.war"
[0m
--
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
13 years, 9 months
[JBoss JIRA] (AS7-5557) Connection pool config unable to run check-valid-connection-sql only in background thread
by Paul Sideleau (JIRA)
Paul Sideleau created AS7-5557:
----------------------------------
Summary: Connection pool config unable to run check-valid-connection-sql only in background thread
Key: AS7-5557
URL: https://issues.jboss.org/browse/AS7-5557
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final
Environment: SQL Server 2012
JTDS 1.2.5
JBOSS 7 Cluster using domain controller
Centos OS virtual
Reporter: Paul Sideleau
There may be a bug trying to get check-valid-connection-sql to only run in the background thread instead of every-time a connection is checked out from the pool.
We have our connection pools configured to do background validation. The validate-on-match is explicitly set to false. Our SQL is simply "SELECT 1".
We are using JTDS driver 1.2.5 against SQL Server 2012.
We use new relic for performance monitoring and it is showing that the "SELECT 1" is executed every time a connection is checked out from the pool. When we had this configured under JBOSS 6, new relic correctly did not show the "SELECT 1" statement occurring.
Here is an example datasource that we place in our domain.xml file:
<datasource jta="true" jndi-name="java:jboss/MSSQLDS-DKR" pool-name="jboss/DKR41" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:jtds:sqlserver://OUR_DATABASE;sendStringParametersAsUnicode=true;</connection-url>
<driver>jtds-1.2.5.jar</driver>
<transaction-isolation>TRANSACTION_READ_UNCOMMITTED</transaction-isolation>
<pool>
<min-pool-size>45</min-pool-size>
<max-pool-size>150</max-pool-size>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>username</user-name>
<password>password</password>
</security>
<validation>
<check-valid-connection-sql>SELECT 1</check-valid-connection-sql>
<validate-on-match>false</validate-on-match>
<background-validation>true</background-validation>
<background-validation-millis>60000</background-validation-millis>
<use-fast-fail>true</use-fast-fail>
</validation>
<timeout>
<blocking-timeout-millis>5000</blocking-timeout-millis>
<idle-timeout-minutes>2</idle-timeout-minutes>
<query-timeout>30</query-timeout>
</timeout>
</datasource>
Thank you
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5028) ability to removethe response-header Server:Apache-Coyote/1.1
by nimo stephan (JIRA)
nimo stephan created AS7-5028:
---------------------------------
Summary: ability to removethe response-header Server:Apache-Coyote/1.1
Key: AS7-5028
URL: https://issues.jboss.org/browse/AS7-5028
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.1.Final
Reporter: nimo stephan
Jboss AS 7 includes the following HTTP-Header for every response:
Server:Apache-Coyote/1.1
For security issues, it is good to hide this header so attackers cannot easily derivate its underlying technology (which, in this case, indicates that Java-Technology/Tomcat is used).
Possible solutions is:
Invent a new system-property "org.jboss.as.sendServerHeader" which can be set, for example, in standalone.xml:
<system-properties>
<property name="org.apache.coyote.http11.Http11Protocol.SERVER" value=""/>
<property name="org.jboss.as.sendServerHeader" value="false"/>
</system-properties>
Note:
- leaving the value of "org.apache.coyote.http11.Http11Protocol.SERVER" results in printing the Server-Header also, instead of to go away. However, with that value I can rename the Server-Header, but not deleting it.
- At first, I have thought this is a JSF-Rendering-Issue, so I created that issue here http://java.net/jira/browse/JAVASERVERFACES-2445, but it stated out that printing the Server-Header is a "application server level concern".
--
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
13 years, 9 months
[JBoss JIRA] (AS7-4673) Failure to set "SetBigStringTryClob=true" ConnectionProperties in xa-datasource-property
by Roger S (JIRA)
Roger S created AS7-4673:
----------------------------
Summary: Failure to set "SetBigStringTryClob=true" ConnectionProperties in xa-datasource-property
Key: AS7-4673
URL: https://issues.jboss.org/browse/AS7-4673
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final
Environment: Red Hat Enterprise Linux Server release 5.7, JDK 7
Reporter: Roger S
I found that when the following is set in the standalone.xml of JBoss-7.1.1.Final, it will have a fatal error:
<xa-datasource....>
....
<xa-datasource-property name="ConnectionProperties">SetBigStringTryClob=true</xa-datasource-property>
....
</xa-datasource>
The error is:
Caused by: javax.resource.ResourceException: No property editor found for type: class java.util.Properties
at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:601)
at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:430)
When I don't define the SetBigStringTryClob setting, all is fine. However, the SetBigStringTryClob is really important for the application to work correctly. Hope there's at least a workaround.
This worked without problems in JBoss 4.2.3.
--
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
13 years, 9 months
[JBoss JIRA] (AS7-3700) jboss-as-arquillian-container-managed 7.0.2.Final ships with jboss-logging 3.0.0.GA, but some of its modules require a higher version: jboss-logging 3.0.1.GA. Same for xnio-api and jbosgi-vfs.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-3700?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on AS7-3700:
---------------------------------------
Is this still an issue in later releases?
> jboss-as-arquillian-container-managed 7.0.2.Final ships with jboss-logging 3.0.0.GA, but some of its modules require a higher version: jboss-logging 3.0.1.GA. Same for xnio-api and jbosgi-vfs.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-3700
> URL: https://issues.jboss.org/browse/AS7-3700
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Reporter: Geoffrey De Smet
> Priority: Trivial
>
> The xnio-api is probably the most dangerous one of these 3.
> It ships with xnio-api 3.0.0.Beta2, but some code requires 3.0.0.Beta3.
> {code}
> IncompatibleDependencyOverwrite error for org.jboss.logging:jboss-logging:3.0.0.GA paths to dependency are:
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.sasl:jboss-sasl:1.0.0.Beta2
> +-org.jboss.logging:jboss-logging:3.0.0.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-testenricher-msc:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.osgi.spi:jbosgi-spi:1.0.28
> +-org.jboss.logging:jboss-logging:3.0.0.Beta3
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
> +-org.jboss.as:jboss-as-protocol:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.osgi.spi:jbosgi-spi:1.0.28
> +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.5
> +-org.jboss.logging:jboss-logging:3.0.0.Beta3
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
> +-org.jboss.as:jboss-as-protocol:7.0.2.Final
> +-org.jboss.remoting3:jboss-remoting:3.2.0.Beta2
> +-org.jboss.logging:jboss-logging:3.0.0.Beta5
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-controller:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-domain-http-api:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-deployment-repository:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-process-controller:7.0.2.Final
> +-org.jboss.logging:jboss-logging:3.0.1.GA
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final
> +-org.jboss.osgi.resolver:jbosgi-resolver-api:1.0.9
> +-org.jboss.osgi.resolver:jbosgi-resolver-metadata:1.0.9
> +-org.jboss.logging:jboss-logging:3.0.0.Beta3
> ,
> IncompatibleDependencyOverwrite error for org.jboss.xnio:xnio-api:3.0.0.Beta2 paths to dependency are:
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
> +-org.jboss.as:jboss-as-protocol:7.0.2.Final
> +-org.jboss.remoting3:jboss-remoting:3.2.0.Beta2
> +-org.jboss.xnio:xnio-api:3.0.0.Beta2
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-controller-client:7.0.2.Final
> +-org.jboss.as:jboss-as-protocol:7.0.2.Final
> +-org.jboss.xnio:xnio-nio:3.0.0.Beta3
> +-org.jboss.xnio:xnio-api:3.0.0.Beta3
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.as:jboss-as-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-server:7.0.2.Final
> +-org.jboss.as:jboss-as-remoting:7.0.2.Final
> +-org.jboss.xnio:xnio-api:3.0.0.Beta3
> ,
> IncompatibleDependencyOverwrite error for org.jboss.osgi.vfs:jbosgi-vfs:1.0.5 paths to dependency are:
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-common:7.0.2.Final
> +-org.jboss.osgi.spi:jbosgi-spi:1.0.28
> +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.5
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final
> +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.6
> and
> +-org.jboss.as:jboss-as-arquillian-container-managed:7.0.2.Final
> +-org.jboss.as:jboss-as-arquillian-protocol-jmx:7.0.2.Final
> +-org.jboss.as:jboss-as-osgi-service:7.0.2.Final
> +-org.jboss.osgi.framework:jbosgi-framework-core:1.0.0.CR8
> +-org.jboss.osgi.vfs:jbosgi-vfs30:1.0.6
> +-org.jboss.osgi.vfs:jbosgi-vfs:1.0.6
> {code}
> Maybe JBoss modules makes this not as bad as it is with normal maven projects.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months