September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8190) Standalone server configuration object model

by Brian Stansberry (JIRA)

Standalone server configuration object model -------------------------------------------- Key: JBAS-8190 URL: https://jira.jboss.org/browse/JBAS-8190 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 7.0.0.M1 Object model that represents the standalone configuration schema. Note that it's quite possible that there will not be a separate, distinct object model for this and the object model that represents a regular Server in a Domain will suffice. Or perhaps we'll provide a class that provides a view onto the regular Domain/ServerGroup/Server object model for use by clients (e.g. embedded AS users) who want a simplified view. Key thing is we don't want every subsystem that needs to understand the domain configuration model to have to understand both the standalone and the full variant of it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-8259) Socket based communication between ServerManager and ProcessManager

by Brian Stansberry (JIRA)

Socket based communication between ServerManager and ProcessManager ------------------------------------------------------------------- Key: JBAS-8259 URL: https://jira.jboss.org/browse/JBAS-8259 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 Default communication mechanism between SM and PM is via stdio. This should almost always be fine, since we use the jboss-stdio lib to capture application usage of stdio and preserve the original streams for our own use. But there is a slight possibility that an extension module running in the SM will use JNI, which can pollute the stdio streams. So, we need an option to allow users to configure SM-PM communication via sockets. (The same issue applies for Server-PM and Server-SM communication, but there the SM can parse host.xml and get configuration from it, so the details are different from this SM-PM use case.) Tasks: 1) Put SM-PM communication behind an abstraction 2) Implement stdio-based and socket-based versions of the abstraction 3) Modify process manager module to accept PM socket configuration via command line params 4) PM passes it's socket configuration to SM via command line when it starts PM 5) Decide how to configure SM's socket -- via host.xml? (Note SM needs a socket for communication with the DC -- use that?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-8311) Establish a full Sever Manager to Server communication protocol

by John Bailey (JIRA)

Establish a full Sever Manager to Server communication protocol ---------------------------------------------------------------- Key: JBAS-8311 URL: https://jira.jboss.org/browse/JBAS-8311 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: John Bailey Assignee: John Bailey Fix For: 7.0.0.M1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8260) Socket based communication between ServerManager and Server

by Brian Stansberry (JIRA)

Socket based communication between ServerManager and Server ----------------------------------------------------------- Key: JBAS-8260 URL: https://jira.jboss.org/browse/JBAS-8260 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 Default communication mechanism between SM and Servers is via stdio, with the ProcessManager routing messages. This should usually be fine, since we use the jboss-stdio lib to capture application usage of stdio and preserve the original streams for our own use. But there is a possibility that an extension module running in the SM or a Server will use JNI, which can pollute the stdio streams. The odds of this are higher in a Server, since extending the capability of the SM with something that needs JNI seems unlikely. So, we need an option to allow users to configure SM-Server communication via sockets. Tasks: 1) Put SM-Server communication behind an abstraction 2) Implement stdio-based and socket-based versions of the abstraction 3) Update host.xml schema to include configuration elements for the sockets on both the SM and the Servers. Note that the SM will need a socket anyway for communication with a remote DomainController, so perhaps this socket could be reused. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8262) Reliable communication between ProcessManager, SocketManager, Server(s)

by Brian Stansberry (JIRA)

Reliable communication between ProcessManager, SocketManager, Server(s) ----------------------------------------------------------------------- Key: JBAS-8262 URL: https://jira.jboss.org/browse/JBAS-8262 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 Messages sent between the related PM/SM/Server processes need to be reliable. These messages should be relatively low volume, so simplest is probably a simple ACK scheme with retransmission until an ACK is received. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-8199) ProcessManager

by Brian Stansberry (JIRA)

ProcessManager -------------- Key: JBAS-8199 URL: https://jira.jboss.org/browse/JBAS-8199 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 Implementation of the ProcessManager as discussed at http://community.jboss.org/docs/DOC-15215 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (SECURITY-447) Support Active Directory Primary Groups

by Darran Lofthouse (JIRA)

Support Active Directory Primary Groups --------------------------------------- Key: SECURITY-447 URL: https://jira.jboss.org/jira/browse/SECURITY-447 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.SP1 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.3.SP3 The following has some useful details on the history of primary groups: - http://dunnry.com/blog/DeterminingYourPrimaryGroupInActiveDirectoryUsingN... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1803) Add possibility to edit local producer information

by Chris Laprun (JIRA)

Add possibility to edit local producer information -------------------------------------------------- Key: JBPORTAL-1803 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1803 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun Assigned To: Chris Laprun -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
10
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1108) Re-factor WSRPProducer to extract a MetaData interface

by Chris Laprun (JIRA)

Re-factor WSRPProducer to extract a MetaData interface ------------------------------------------------------ Key: JBPORTAL-1108 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1108 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.DR1, 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.Alpha1 Methods pertaining to registration, cookies and session expiration should all be part of the MetaData... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1250) Optimize access to service description

by Chris Laprun (JIRA)

Optimize access to service description -------------------------------------- Key: JBPORTAL-1250 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1250 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6 Final Producer information code still tries to access service too many times. Should add a transaction-like concept during which the service description would stay valid since for a single operation it is currently possible to request the service description several times (when cache is not used)... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2010