[JBoss JIRA] (AS7-3866) Data-source disable operation does not supprt allow-resource-service-restart attribute
by Dominik Pospisil (JIRA)
Dominik Pospisil created AS7-3866:
-------------------------------------
Summary: Data-source disable operation does not supprt allow-resource-service-restart attribute
Key: AS7-3866
URL: https://issues.jboss.org/browse/AS7-3866
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Dominik Pospisil
Assignee: Brian Stansberry
Data-source disable operation does not supprt allow-resource-service-restart attribute (as remove does).
Steps to reproduce:
[standalone@localhost:9999 /] data-source add --name=TestDS --jndi-name=java:jboss/datasources/TestDS --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1
[standalone@localhost:9999 /] data-source enable --name=TestDS
[standalone@localhost:9999 /] /subsystem=datasources/data-source=TestDS:disable{allow-resource-service-restart}
{
"outcome" => "success",
"response-headers" => {
"operation-requires-restart" => true,
"process-state" => "restart-required"
}
}
[standalone@localhost:9999 /] data-source enable --name=TestDS
JBAS014749: Operation handler failed: Service jboss.data-source-config.TestDS is already registered
[standalone@localhost:9999 /]
--
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 months
[JBoss JIRA] (AS7-3620) mod_cluster registers ROOT context
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3620:
-----------------------------------
Summary: mod_cluster registers ROOT context
Key: AS7-3620
URL: https://issues.jboss.org/browse/AS7-3620
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Critical
Fix For: 7.1.0.Final
mod_cluster registers ROOT context even though its specified in excluded-list
default profile
[rhusar@rhusar jboss-as-7.1.0.Final-SNAPSHOT]$ ./bin/standalone.sh -c standalone-ha.xml
http://localhost:6666/mod_cluster_manager
mod_cluster/1.1.x
Auto Refresh show DUMP output show INFO output
Node 498bb1f0-00d9-3436-a341-7f012bc2e7ec (http://localhost.localdomain:8080):
Enable Contexts Disable Contexts
Balancer: mycluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 26,Ttl: 60000000,Status: OK,Elected: 5,Read: 81387,Transferred: 2531,Connected: 0,Load: 1
Virtual Host 1:
Contexts:
/, Status: ENABLED Request: 0 Disable
Aliases:
default-host
localhost
example.com
--
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 months
[JBoss JIRA] (AS7-3790) TS: Unable to pass tests in integration smoke test part of testsuite in IPv6 environment
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/AS7-3790?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas commented on AS7-3790:
-------------------------------------
Is this still an issue with latest master?
> TS: Unable to pass tests in integration smoke test part of testsuite in IPv6 environment
> ----------------------------------------------------------------------------------------
>
> Key: AS7-3790
> URL: https://issues.jboss.org/browse/AS7-3790
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.1.0.Final
> Reporter: Pavel Janousek
> Assignee: Shelly McGowan
>
> I've tried to build AS7 and run default part of testsuite (including integration smoke tests) in IPv6 environment like:{code}./build.sh clean install -Dnode0=::1 -Dipv6{code}
> My lookpack network interface was configured as:{code}[root@fedora15-vrt1 Documents]# ifconfig lo
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:60156 errors:0 dropped:0 overruns:0 frame:0
> TX packets:60156 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:37911245 (36.1 MiB) TX bytes:37911245 (36.1 MiB)
> [root@fedora15-vrt1 Documents]#
> {code}
> The result is failure because timeout:
> {code}
> <snip>
> main:
> build-smoke:
> [INFO] Executed tasks
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-ts-integ-smoke ---
> [INFO] Compiling 110 source files to /home/pjanouse/devel/tmp/ozizka/jboss-as/testsuite/integration/smoke/target/test-classes
> [WARNING] /home/pjanouse/devel/tmp/ozizka/jboss-as/testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/surefire/servermodule/AbstractServerInModuleTestCase.java:[54,62] [deprecation] getModulesDir() in org.jboss.as.server.ServerEnvironment has been deprecated
> [INFO]
> [INFO] --- maven-surefire-plugin:2.10:test (smoke-full.surefire) @ jboss-as-ts-integ-smoke ---
> [INFO] Surefire report directory: /home/pjanouse/devel/tmp/ozizka/jboss-as/testsuite/integration/smoke/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.as.test.smoke.embedded.demos.messaging.MessagingTestCase
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [1.952s]
> [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [1.435s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.276s]
> [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [1.525s]
> [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [11.337s]
> [INFO] JBoss Application Server: Controller Client ....... SUCCESS [5.599s]
> [INFO] JBoss Application Server: Controller Core ......... SUCCESS [21.175s]
> [INFO] JBoss Application Server: Domain Management ....... SUCCESS [3.940s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [2.620s]
> [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [2.615s]
> [INFO] JBoss Application Server: Embedded ................ SUCCESS [4.239s]
> [INFO] JBoss Application Server: Platform MBean integration SUCCESS [5.673s]
> [INFO] JBoss Application Server: Process Controller ...... SUCCESS [6.888s]
> [INFO] JBoss Application Server: Network ................. SUCCESS [3.532s]
> [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [8.944s]
> [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [4.899s]
> [INFO] JBoss Application Server: Server .................. SUCCESS [11.049s]
> [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [5.775s]
> [INFO] JBoss Application Server: JMX Subsystem ........... SUCCESS [9.914s]
> [INFO] JBoss Application Server: Naming Subsystem ........ SUCCESS [8.926s]
> [INFO] JBoss Application Server: EE ...................... SUCCESS [13.024s]
> [INFO] JBoss Application Server: Transaction Subsystem ... SUCCESS [7.015s]
> [INFO] JBoss Application Server: Clustering Subsystem .... SUCCESS [0.184s]
> [INFO] JBoss Application Server: Common code for clustering subsystems SUCCESS [5.332s]
> [INFO] JBoss Application Server: JGroups Subsystem ....... SUCCESS [8.036s]
> [INFO] JBoss Application Server: Infinispan Subsystem .... SUCCESS [23.168s]
> [INFO] JBoss Application Server: Security Subsystem ...... SUCCESS [11.052s]
> [INFO] JBoss Application Server: Connector Subsystem ..... SUCCESS [19.138s]
> [INFO] JBoss Application Server: Clustering Server API ... SUCCESS [13.274s]
> [INFO] JBoss Application Server: Clustered registry service SUCCESS [2.203s]
> [INFO] JBoss Application Server: JacORB Subsystem ........ SUCCESS [16.268s]
> [INFO] JBoss Application Server: EJB Subsystem ........... SUCCESS [35.557s]
> [INFO] JBoss Application Server: Distributed Web Session SPI SUCCESS [5.422s]
> [INFO] JBoss Application Server: Clustering Server API implementation SUCCESS [5.224s]
> [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SUCCESS [7.409s]
> [INFO] JBoss Application Server: Web Subsystem ........... SUCCESS [19.789s]
> [INFO] JBoss Application Server: Web Services Subsystem .. SUCCESS [0.183s]
> [INFO] JBoss Application Server: Web Services Server Integration Subsystem SUCCESS [9.624s]
> [INFO] JBoss Application Server: Application Client Bootstrap SUCCESS [7.014s]
> [INFO] JBoss Application Server: Command line interface .. SUCCESS [12.399s]
> [INFO] JBoss Application Server: EJB Client BOM .......... SUCCESS [0.226s]
> [INFO] JBoss Application Server: JMS Client BOM .......... SUCCESS [0.213s]
> [INFO] JBoss Application Server: EJB and JMS client combined jar SUCCESS [4.948s]
> [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SUCCESS [3.795s]
> [INFO] JBoss Application Server: Clustered service provider registry services SUCCESS [4.434s]
> [INFO] JBoss Application Server: Clustered singleton services SUCCESS [5.016s]
> [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SUCCESS [24.135s]
> [INFO] JBoss Application Server: Config Admin ............ SUCCESS [5.690s]
> [INFO] JBoss Application Server: Deployment Scanner ...... SUCCESS [7.514s]
> [INFO] JBoss Application Server: EE Deployment ........... SUCCESS [4.195s]
> [INFO] JBoss Application Server: JAXR Client ............. SUCCESS [4.562s]
> [INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [0.231s]
> [INFO] JBoss Application Server: JPA SPI ................. SUCCESS [4.460s]
> [INFO] JBoss Application Server: JPA UTIL ................ SUCCESS [1.698s]
> [INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [7.273s]
> [INFO] JBoss Application Server: Weld Integration ........ SUCCESS [8.499s]
> [INFO] JBoss Application Server: JAX-RS Integration ...... SUCCESS [8.492s]
> [INFO] JBoss Application Server: JBoss Diagnostic Reporter SUCCESS [0.158s]
> [INFO] JBoss Application Server: JDR ..................... SUCCESS [6.291s]
> [INFO] JBoss Application Server: JSR-77 Subsystem ........ SUCCESS [5.485s]
> [INFO] JBoss Application Server: Management Client Content SUCCESS [3.706s]
> [INFO] JBoss Application Server: Host Controller ......... SUCCESS [18.260s]
> [INFO] JBoss Application Server: Logging Subsystem ....... SUCCESS [13.138s]
> [INFO] JBoss Application Server: Mail subsystem .......... SUCCESS [7.227s]
> [INFO] JBoss Application Server: Messaging Subsystem ..... SUCCESS [18.398s]
> [INFO] JBoss Application Server: ModCluster Subsystem .... SUCCESS [7.415s]
> [INFO] JBoss Application Server: OSGi .................... SUCCESS [0.148s]
> [INFO] JBoss Application Server: OSGi Subsystem .......... SUCCESS [9.388s]
> [INFO] JBoss Application Server: OSGi ConfigurationAdmin . SUCCESS [4.866s]
> [INFO] JBoss Application Server: POJO Subsystem .......... SUCCESS [7.217s]
> [INFO] JBoss Application Server: sosreport scripts ....... SUCCESS [2.259s]
> [INFO] JBoss Application Server: Service Archive Subsystem SUCCESS [6.041s]
> [INFO] JBoss Application Server: XTS Subsystem ........... SUCCESS [7.902s]
> [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SUCCESS [3.552s]
> [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SUCCESS [4.524s]
> [INFO] JBoss Application Server: Infinispan Hibernate 2nd level cache provider SUCCESS [1.783s]
> [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SUCCESS [3.333s]
> [INFO] JBoss Application Server: Build ................... SUCCESS [21.975s]
> [INFO] JBoss Application Server: Arquillian .............. SUCCESS [0.190s]
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS [1.574s]
> [INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [3.888s]
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [2.520s]
> [INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [18.181s]
> [INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [3.492s]
> [INFO] JBoss Application Server: Exported Java EE Specification APIs SUCCESS [0.261s]
> [INFO] JBoss Application Server: Arquillian TestNG Integration SUCCESS [15.898s]
> [INFO] JBoss Application Server: Demos: Aggregator ....... SUCCESS [2.748s]
> [INFO] JBoss Application Server: Demos: Spec ............. SUCCESS [4.056s]
> [INFO] JBoss Application Server: Demos: Legacy TO BE MOVED SUCCESS [10.657s]
> [INFO] JBoss Application Server: Distribution ............ SUCCESS [1.035s]
> [INFO] JBoss Application Server: Remoting Subsystem Test . SUCCESS [2.981s]
> [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SUCCESS [2.360s]
> [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SUCCESS [1.969s]
> [INFO] JBoss Application Server Test Suite: Shared ....... SUCCESS [7.605s]
> [INFO] JBoss Application Server Test Suite: Aggregator ... SUCCESS [6.152s]
> [INFO] JBoss Application Server Test Suite: Integration .. SUCCESS [2.203s]
> [INFO] JBoss Application Server Test Suite: Integration - Smoke FAILURE [15:07.181s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 26:31.461s
> [INFO] Finished at: Thu Feb 16 11:51:51 CET 2012
> [INFO] Final Memory: 341M/494M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (smoke-full.surefire) on project jboss-as-ts-integ-smoke: Failure or timeout -> [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 :jboss-as-ts-integ-smoke
> [pjanouse@fedora15-vrt1 jboss-as]$
> {code}
> Unfortunately org.jboss.as.test.smoke.embedded.demos.messaging.MessagingTestCase.txt and org.jboss.as.test.smoke.embedded.demo~essaging.MessagingTestCase-output.txt files in jboss-as/testsuite/integration/smoke/target/surefire-reports are created, but leaved empty only. Nor work-around mentioned in [ARQ-696|https://issues.jboss.org/browse/ARQ-696?focusedCommentId=12667010...] comment doesn't help.
> BTW I've checked standalone-full.xml and basic things are correctly assigned to ::1 (especially _management_ and _public_ interface)
--
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 months
[JBoss JIRA] (AS7-3973) Yet another place where hardcoded IPv4 address scheme is used
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/AS7-3973?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas commented on AS7-3973:
-------------------------------------
I don't see those two tests having hard coded localhost, they both pass for me when binding to an external non-localhost ip. Can you post the stack trace?
Some of the webservice ones still have issues however, as localhost is referenced in the wsdl. Also the iiop tests reference it in the @EJB() annotation.
> Yet another place where hardcoded IPv4 address scheme is used
> -------------------------------------------------------------
>
> Key: AS7-3973
> URL: https://issues.jboss.org/browse/AS7-3973
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.1.1.Final
> Reporter: Pavel Janousek
> Assignee: Ondrej Zizka
> Priority: Blocker
>
> After the last Stuart commit and merge to upstream (on Thursday morning CET time zone), there are still some places where hardcoded IPv4 address scheme is used.
> Wrong TestCases are:
> - org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase
> - org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase
> Both of them use 127.0.0.1 directly even -Dnode0=::1 - it seems to be some other magic inside them because [there|http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-t...] TS passed, but I also reconfigure my machine to avoid IPv4 name address translation like:
> {code}
> #127.0.0.1 localhost.localdomain
> #127.0.0.1 pjanouse.brq.redhat.com localhost
> ::1 localhost6.localdomain6 localhost6 localhost
> ::1 pjanouse.brq.redhat.com localhost
> 127.0.0.2 both
> ::2 both
> 2001:0000:1234:0000:0000:c1c0:abcd:0876 ip6
> {code}
> I've got this result:{code}
> Tests in error:
> org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out
> org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out
> org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out
> org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out
> {code}
> It seems there are several other problems in clustering and domain, but I'll report them after deeper investigation.
--
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 months