[JBoss JIRA] (AS7-3973) Yet another place where hardcoded IPv4 address scheme is used
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-3973?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek updated AS7-3973:
--------------------------------
Description:
After the last Stuart commit and merge to upstream (on -Thursday- Wednesday 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.
was:
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.
> 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- Wednesday 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
13 years, 9 months
[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
13 years, 9 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
13 years, 9 months