[JBoss JIRA] (AS7-4317) CLONE - Jacorb listens on ::ffff:127.0.0.1 even is should bind to ::1
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4317?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry reassigned AS7-4317:
-------------------------------------
Assignee: Brian Stansberry
> CLONE - Jacorb listens on ::ffff:127.0.0.1 even is should bind to ::1
> ---------------------------------------------------------------------
>
> Key: AS7-4317
> URL: https://issues.jboss.org/browse/AS7-4317
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, IIOP
> Affects Versions: 7.1.0.Final, 7.1.1.Final
> Reporter: Miroslav Novak
> Assignee: Brian Stansberry
> Priority: Blocker
> Fix For: 7.1.2.Final
>
>
> When server is bound to ipv6 loop-back address ::1 then Jacorb listens on ::ffff:127.0.0.1.
> {code}
> netstat -npl | grep java
> (Not all processes could be identified, non-owned process info
> will not be shown, you would have to be root to see it all.)
> tcp 0 0 ::ffff:127.0.0.1:5455 :::* LISTEN 1438/java
> tcp 0 0 ::1:9999 :::* LISTEN 1438/java
> tcp 0 0 ::1:8080 :::* LISTEN 1438/java
> tcp 0 0 ::1:4447 :::* LISTEN 1438/java
> tcp 0 0 ::ffff:127.0.0.1:5445 :::* LISTEN 1438/java
> tcp 0 0 ::1:9990 :::* LISTEN 1438/java
> tcp 0 0 ::ffff:127.0.0.1:3528 :::* LISTEN 1438/java
> udp 0 5048 :::45329 :::* 1438/java
> udp 0 0 :::9875 :::* 1438/java
> udp 0 0 ::ffff:224.0.1.105:23364 :::* 1438/java
> {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
14 years, 2 months
[JBoss JIRA] (AS7-4317) CLONE - Jacorb listens on ::ffff:127.0.0.1 even is should bind to ::1
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4317?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry moved JBPAPP-8564 to AS7-4317:
-----------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-4317 (was: JBPAPP-8564)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.1.Final
7.1.0.Final
(was: EAP 6.0.0 ER 1)
(was: EAP 6.0.0 ER 3_Beta1)
Release Notes Docs Status: (was: Not Required)
Component/s: Domain Management
IIOP
(was: IIOP)
Security: (was: JBoss Internal)
Fix Version/s: 7.1.2.Final
(was: EAP 6.0.0 ER 4)
Docs QE Status: (was: NEW)
> CLONE - Jacorb listens on ::ffff:127.0.0.1 even is should bind to ::1
> ---------------------------------------------------------------------
>
> Key: AS7-4317
> URL: https://issues.jboss.org/browse/AS7-4317
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, IIOP
> Affects Versions: 7.1.1.Final, 7.1.0.Final
> Reporter: Miroslav Novak
> Priority: Blocker
> Fix For: 7.1.2.Final
>
>
> When server is bound to ipv6 loop-back address ::1 then Jacorb listens on ::ffff:127.0.0.1.
> {code}
> netstat -npl | grep java
> (Not all processes could be identified, non-owned process info
> will not be shown, you would have to be root to see it all.)
> tcp 0 0 ::ffff:127.0.0.1:5455 :::* LISTEN 1438/java
> tcp 0 0 ::1:9999 :::* LISTEN 1438/java
> tcp 0 0 ::1:8080 :::* LISTEN 1438/java
> tcp 0 0 ::1:4447 :::* LISTEN 1438/java
> tcp 0 0 ::ffff:127.0.0.1:5445 :::* LISTEN 1438/java
> tcp 0 0 ::1:9990 :::* LISTEN 1438/java
> tcp 0 0 ::ffff:127.0.0.1:3528 :::* LISTEN 1438/java
> udp 0 5048 :::45329 :::* 1438/java
> udp 0 0 :::9875 :::* 1438/java
> udp 0 0 ::ffff:224.0.1.105:23364 :::* 1438/java
> {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
14 years, 2 months
[JBoss JIRA] (AS7-4316) CLONE - HornetQ listens on ::ffff:127.0.0.1 when bound to ::1
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4316?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry reassigned AS7-4316:
-------------------------------------
Assignee: Brian Stansberry (was: Clebert Suconic)
> CLONE - HornetQ listens on ::ffff:127.0.0.1 when bound to ::1
> -------------------------------------------------------------
>
> Key: AS7-4316
> URL: https://issues.jboss.org/browse/AS7-4316
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, JMS
> Affects Versions: 7.0.0.Final, 7.0.1.Final, 7.0.2.Final, 7.1.0.Final, 7.1.1.Final
> Reporter: Miroslav Novak
> Assignee: Brian Stansberry
> Fix For: 7.1.2.Final
>
>
> When server is bound to ipv6 loop-back address ::1 then HornetQ listens on ::ffff:127.0.0.1.
> {code}
> netstat -npl | grep java
> (Not all processes could be identified, non-owned process info
> will not be shown, you would have to be root to see it all.)
> tcp 0 0 ::ffff:127.0.0.1:5455 :::* LISTEN 1438/java
> tcp 0 0 ::1:9999 :::* LISTEN 1438/java
> tcp 0 0 ::1:8080 :::* LISTEN 1438/java
> tcp 0 0 ::1:4447 :::* LISTEN 1438/java
> tcp 0 0 ::ffff:127.0.0.1:5445 :::* LISTEN 1438/java
> tcp 0 0 ::1:9990 :::* LISTEN 1438/java
> tcp 0 0 ::ffff:127.0.0.1:3528 :::* LISTEN 1438/java
> udp 0 5048 :::45329 :::* 1438/java
> udp 0 0 :::9875 :::* 1438/java
> udp 0 0 ::ffff:224.0.1.105:23364 :::* 1438/java
> {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
14 years, 2 months
[JBoss JIRA] (AS7-4316) CLONE - HornetQ listens on ::ffff:127.0.0.1 when bound to ::1
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4316?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry moved JBPAPP-8563 to AS7-4316:
-----------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-4316 (was: JBPAPP-8563)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.1.Final
7.1.0.Final
7.0.2.Final
7.0.1.Final
7.0.0.Final
(was: EAP 6.0.0 ER 1)
Component/s: Domain Management
JMS
(was: HornetQ)
Security: (was: JBoss Internal)
Fix Version/s: 7.1.2.Final
(was: EAP 6.0.0 ER 5)
Docs QE Status: (was: NEW)
> CLONE - HornetQ listens on ::ffff:127.0.0.1 when bound to ::1
> -------------------------------------------------------------
>
> Key: AS7-4316
> URL: https://issues.jboss.org/browse/AS7-4316
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, JMS
> Affects Versions: 7.1.1.Final, 7.1.0.Final, 7.0.2.Final, 7.0.1.Final, 7.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Clebert Suconic
> Fix For: 7.1.2.Final
>
>
> When server is bound to ipv6 loop-back address ::1 then HornetQ listens on ::ffff:127.0.0.1.
> {code}
> netstat -npl | grep java
> (Not all processes could be identified, non-owned process info
> will not be shown, you would have to be root to see it all.)
> tcp 0 0 ::ffff:127.0.0.1:5455 :::* LISTEN 1438/java
> tcp 0 0 ::1:9999 :::* LISTEN 1438/java
> tcp 0 0 ::1:8080 :::* LISTEN 1438/java
> tcp 0 0 ::1:4447 :::* LISTEN 1438/java
> tcp 0 0 ::ffff:127.0.0.1:5445 :::* LISTEN 1438/java
> tcp 0 0 ::1:9990 :::* LISTEN 1438/java
> tcp 0 0 ::ffff:127.0.0.1:3528 :::* LISTEN 1438/java
> udp 0 5048 :::45329 :::* 1438/java
> udp 0 0 :::9875 :::* 1438/java
> udp 0 0 ::ffff:224.0.1.105:23364 :::* 1438/java
> {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
14 years, 2 months
[JBoss JIRA] (AS7-4314) Timeout for management request clearing before channel shutdown is too short
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-4314:
-------------------------------------
Summary: Timeout for management request clearing before channel shutdown is too short
Key: AS7-4314
URL: https://issues.jboss.org/browse/AS7-4314
Project: Application Server 7
Issue Type: Bug
Reporter: Brian Stansberry
ModelControllerClientOperationHandlerFactoryService and MasterDomainControllerOperationHandlerService add a bit of graceful shutdown handling to the management channel close process by waiting a bit for in-process requests to push out their response before closing the channel. This was meant to be helpful for cases like :reload or :shutdown requests which asynchronously trigger stop of the management channel service and then try to respond to the caller indicating the async request was made. Theres a race between getting the response out and the channel closing.
Problem is the timeout is only 100 ms, which isn't particularly useful and leads to noticeable variability in whether those ops get their responses sent in time.
This JIRA will bump that timeout to 15000 ms and making it configurable via system property "jboss.as.management.channel.close.timeout". The latter isn't very important; I just don't like hard coded things like this with no way to tweak them if an unexpected need arises.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-4312) Create static registry of realms
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-4312:
-------------------------------------
Summary: Create static registry of realms
Key: AS7-4312
URL: https://issues.jboss.org/browse/AS7-4312
Project: Application Server 7
Issue Type: Sub-task
Components: Domain Management
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.2.Final
It can make sense to access the realms from non service based classes such as login modules, this task is for a registry that can be used to lookup the callback handlers and registration with the registry as the services start.
This should include an access controller check so we can restrict exactly what can access the registered realms.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months