[JBoss JIRA] (AS7-6120) Expand support for System Property substitution
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6120?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6120:
----------------------------------
Attachment: expressions.ods
Updated the tracking file.
> Expand support for System Property substitution
> -----------------------------------------------
>
> Key: AS7-6120
> URL: https://issues.jboss.org/browse/AS7-6120
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Jimmy Wilson
> Assignee: Brian Stansberry
> Priority: Blocker
> Labels: eap-6.1-prd, rhq
> Fix For: 7.2.0.Alpha1
>
> Attachments: expressions.ods
>
>
> Audit the core AS and all subsystems shipped in the AS distribution for suport for expression in management resource attributes.
> The basic philosophy toward expressions in previous releases was to only push devs to add support if there was a clear important use case. Devs could choose to add support beyond that, but we wouldn't push that. This JIRA and PRODMGT-195 from which it is derived reflects a change in philosophy. Now the philosophy is to support expressions unless the dev foresees a technical or future compatibility problem arising from doing so.
> This task DOES NOT advocate adding expression support to attributes that represent references to other model elements. Such references may prove problematic in the future and should not be added. We already have some model ref attributes that support expressions; this task DOES NOT advocate removing such support, unless the support has never been provided in a Final release (i.e. it was added during 7.2 development.)
--
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, 3 months
[JBoss JIRA] (AS7-6120) Expand support for System Property substitution
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6120?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6120:
----------------------------------
Attachment: (was: expressions.ods)
> Expand support for System Property substitution
> -----------------------------------------------
>
> Key: AS7-6120
> URL: https://issues.jboss.org/browse/AS7-6120
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Jimmy Wilson
> Assignee: Brian Stansberry
> Priority: Blocker
> Labels: eap-6.1-prd, rhq
> Fix For: 7.2.0.Alpha1
>
> Attachments: expressions.ods
>
>
> Audit the core AS and all subsystems shipped in the AS distribution for suport for expression in management resource attributes.
> The basic philosophy toward expressions in previous releases was to only push devs to add support if there was a clear important use case. Devs could choose to add support beyond that, but we wouldn't push that. This JIRA and PRODMGT-195 from which it is derived reflects a change in philosophy. Now the philosophy is to support expressions unless the dev foresees a technical or future compatibility problem arising from doing so.
> This task DOES NOT advocate adding expression support to attributes that represent references to other model elements. Such references may prove problematic in the future and should not be added. We already have some model ref attributes that support expressions; this task DOES NOT advocate removing such support, unless the support has never been provided in a Final release (i.e. it was added during 7.2 development.)
--
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, 3 months
[JBoss JIRA] (AS7-6339) Unable to propagate security context using IIOP between two AS7 server instances
by Stuart Douglas (JIRA)
Stuart Douglas created AS7-6339:
-----------------------------------
Summary: Unable to propagate security context using IIOP between two AS7 server instances
Key: AS7-6339
URL: https://issues.jboss.org/browse/AS7-6339
Project: Application Server 7
Issue Type: Bug
Components: IIOP
Affects Versions: 7.1.3.Final (EAP)
Reporter: Stuart Douglas
Assignee: Stefan Guilhen
Fix For: 7.2.0.Alpha1
Because AS7 uses the SASClientIdentityInterceptor it expects that the security context will be propagated using a trust based mechanism, however this trust based mechanism has not actually been fully implemented.
In EJBCorbaServant there is some code that comes from AS6 that just assumes username=password, with a comment that this needs to be removed once we have a mechanism to establish trust.
For now I think that we need to do two things:
- Allow the server to easily use the SASClientInterceptor
- Use the SASCurrent as a credential in EjbCorbaServant, so a custom login module can be used to establish trust
--
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, 3 months
[JBoss JIRA] (AS7-6120) Expand support for System Property substitution
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6120?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on AS7-6120:
---------------------------------------
I thought that was likely the case, but I flagged them to force myself to look or to ask you. Thanks for the input.
> Expand support for System Property substitution
> -----------------------------------------------
>
> Key: AS7-6120
> URL: https://issues.jboss.org/browse/AS7-6120
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Jimmy Wilson
> Assignee: Brian Stansberry
> Priority: Blocker
> Labels: eap-6.1-prd, rhq
> Fix For: 7.2.0.Alpha1
>
> Attachments: expressions.ods
>
>
> Audit the core AS and all subsystems shipped in the AS distribution for suport for expression in management resource attributes.
> The basic philosophy toward expressions in previous releases was to only push devs to add support if there was a clear important use case. Devs could choose to add support beyond that, but we wouldn't push that. This JIRA and PRODMGT-195 from which it is derived reflects a change in philosophy. Now the philosophy is to support expressions unless the dev foresees a technical or future compatibility problem arising from doing so.
> This task DOES NOT advocate adding expression support to attributes that represent references to other model elements. Such references may prove problematic in the future and should not be added. We already have some model ref attributes that support expressions; this task DOES NOT advocate removing such support, unless the support has never been provided in a Final release (i.e. it was added during 7.2 development.)
--
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, 3 months
[JBoss JIRA] (AS7-6337) HornetQ prints an ERROR at boot for standalone-full-ha.xml profile on Mac hardware
by Clebert Suconic (JIRA)
[ https://issues.jboss.org/browse/AS7-6337?page=com.atlassian.jira.plugin.s... ]
Clebert Suconic updated AS7-6337:
---------------------------------
Summary: HornetQ prints an ERROR at boot for standalone-full-ha.xml profile on Mac hardware (was: HornetQ prints an ERROR at boot for standalone-full-ha.xml profile)
> HornetQ prints an ERROR at boot for standalone-full-ha.xml profile on Mac hardware
> ----------------------------------------------------------------------------------
>
> Key: AS7-6337
> URL: https://issues.jboss.org/browse/AS7-6337
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Environment: OSX + JDK6
> Reporter: Ales Justin
> Assignee: Clebert Suconic
>
> 22:23:08,477 ERROR [org.hornetq.core.server] (Thread-1 (HornetQ-scheduled-threads-27225657)) HQ224054: Failed to broadcast connector configs: java.io.IOException: Network is unreachable
> at java.net.PlainDatagramSocketImpl.send(Native Method) [classes.jar:1.6.0_37]
> at java.net.DatagramSocket.send(DatagramSocket.java:625) [classes.jar:1.6.0_37]
> at org.hornetq.api.core.UDPBroadcastGroupConfiguration$UDPBroadcastEndpoint.broadcast(UDPBroadcastGroupConfiguration.java:136) [hornetq-core-client-2.3.0.BETA3.jar:]
> at org.hornetq.core.server.cluster.impl.BroadcastGroupImpl.broadcastConnectors(BroadcastGroupImpl.java:216) [hornetq-server-2.3.0.BETA3.jar:]
> at org.hornetq.core.server.cluster.impl.BroadcastGroupImpl.run(BroadcastGroupImpl.java:228) [hornetq-server-2.3.0.BETA3.jar:]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_37]
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [classes.jar:1.6.0_37]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [classes.jar:1.6.0_37]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [classes.jar:1.6.0_37]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [classes.jar:1.6.0_37]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [classes.jar:1.6.0_37]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
--
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, 3 months
[JBoss JIRA] (AS7-6337) HornetQ prints an ERROR at boot for standalone-full-ha.xml profile
by Ales Justin (JIRA)
[ https://issues.jboss.org/browse/AS7-6337?page=com.atlassian.jira.plugin.s... ]
Ales Justin updated AS7-6337:
-----------------------------
Issue Type: Bug (was: Task)
Environment: OSX + JDK6
> HornetQ prints an ERROR at boot for standalone-full-ha.xml profile
> ------------------------------------------------------------------
>
> Key: AS7-6337
> URL: https://issues.jboss.org/browse/AS7-6337
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Environment: OSX + JDK6
> Reporter: Ales Justin
> Assignee: Clebert Suconic
>
> 22:23:08,477 ERROR [org.hornetq.core.server] (Thread-1 (HornetQ-scheduled-threads-27225657)) HQ224054: Failed to broadcast connector configs: java.io.IOException: Network is unreachable
> at java.net.PlainDatagramSocketImpl.send(Native Method) [classes.jar:1.6.0_37]
> at java.net.DatagramSocket.send(DatagramSocket.java:625) [classes.jar:1.6.0_37]
> at org.hornetq.api.core.UDPBroadcastGroupConfiguration$UDPBroadcastEndpoint.broadcast(UDPBroadcastGroupConfiguration.java:136) [hornetq-core-client-2.3.0.BETA3.jar:]
> at org.hornetq.core.server.cluster.impl.BroadcastGroupImpl.broadcastConnectors(BroadcastGroupImpl.java:216) [hornetq-server-2.3.0.BETA3.jar:]
> at org.hornetq.core.server.cluster.impl.BroadcastGroupImpl.run(BroadcastGroupImpl.java:228) [hornetq-server-2.3.0.BETA3.jar:]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_37]
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [classes.jar:1.6.0_37]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [classes.jar:1.6.0_37]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [classes.jar:1.6.0_37]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [classes.jar:1.6.0_37]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [classes.jar:1.6.0_37]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
--
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, 3 months
[JBoss JIRA] (AS7-6337) HornetQ prints an ERROR at boot for standalone-full-ha.xml profile
by Ales Justin (JIRA)
[ https://issues.jboss.org/browse/AS7-6337?page=com.atlassian.jira.plugin.s... ]
Ales Justin commented on AS7-6337:
----------------------------------
Afaik, it's OS specific -- only on OSX.
> HornetQ prints an ERROR at boot for standalone-full-ha.xml profile
> ------------------------------------------------------------------
>
> Key: AS7-6337
> URL: https://issues.jboss.org/browse/AS7-6337
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Environment: OSX + JDK6
> Reporter: Ales Justin
> Assignee: Clebert Suconic
>
> 22:23:08,477 ERROR [org.hornetq.core.server] (Thread-1 (HornetQ-scheduled-threads-27225657)) HQ224054: Failed to broadcast connector configs: java.io.IOException: Network is unreachable
> at java.net.PlainDatagramSocketImpl.send(Native Method) [classes.jar:1.6.0_37]
> at java.net.DatagramSocket.send(DatagramSocket.java:625) [classes.jar:1.6.0_37]
> at org.hornetq.api.core.UDPBroadcastGroupConfiguration$UDPBroadcastEndpoint.broadcast(UDPBroadcastGroupConfiguration.java:136) [hornetq-core-client-2.3.0.BETA3.jar:]
> at org.hornetq.core.server.cluster.impl.BroadcastGroupImpl.broadcastConnectors(BroadcastGroupImpl.java:216) [hornetq-server-2.3.0.BETA3.jar:]
> at org.hornetq.core.server.cluster.impl.BroadcastGroupImpl.run(BroadcastGroupImpl.java:228) [hornetq-server-2.3.0.BETA3.jar:]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_37]
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [classes.jar:1.6.0_37]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [classes.jar:1.6.0_37]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [classes.jar:1.6.0_37]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [classes.jar:1.6.0_37]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [classes.jar:1.6.0_37]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
--
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, 3 months
[JBoss JIRA] (AS7-6337) HornetQ prints an ERROR at boot for standalone-full-ha.xml profile
by Ales Justin (JIRA)
[ https://issues.jboss.org/browse/AS7-6337?page=com.atlassian.jira.plugin.s... ]
Ales Justin commented on AS7-6337:
----------------------------------
It only logs once, at boot time.
It looks like afterwards things work, at least out JMS-based tests all passed; local and cluster wise.
> HornetQ prints an ERROR at boot for standalone-full-ha.xml profile
> ------------------------------------------------------------------
>
> Key: AS7-6337
> URL: https://issues.jboss.org/browse/AS7-6337
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Environment: OSX + JDK6
> Reporter: Ales Justin
> Assignee: Clebert Suconic
>
> 22:23:08,477 ERROR [org.hornetq.core.server] (Thread-1 (HornetQ-scheduled-threads-27225657)) HQ224054: Failed to broadcast connector configs: java.io.IOException: Network is unreachable
> at java.net.PlainDatagramSocketImpl.send(Native Method) [classes.jar:1.6.0_37]
> at java.net.DatagramSocket.send(DatagramSocket.java:625) [classes.jar:1.6.0_37]
> at org.hornetq.api.core.UDPBroadcastGroupConfiguration$UDPBroadcastEndpoint.broadcast(UDPBroadcastGroupConfiguration.java:136) [hornetq-core-client-2.3.0.BETA3.jar:]
> at org.hornetq.core.server.cluster.impl.BroadcastGroupImpl.broadcastConnectors(BroadcastGroupImpl.java:216) [hornetq-server-2.3.0.BETA3.jar:]
> at org.hornetq.core.server.cluster.impl.BroadcastGroupImpl.run(BroadcastGroupImpl.java:228) [hornetq-server-2.3.0.BETA3.jar:]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_37]
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [classes.jar:1.6.0_37]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [classes.jar:1.6.0_37]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [classes.jar:1.6.0_37]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [classes.jar:1.6.0_37]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [classes.jar:1.6.0_37]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
--
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, 3 months