November 2008 - jopr-issues - Jboss List Archives

[JBoss JIRA] Created: (JOPR-16) if the call to redeploy() during an EAR/WAR update fails, we should attempt to rollback to the original EAR/WAR file

by Ian Springer (JIRA)

if the call to redeploy() during an EAR/WAR update fails, we should attempt to rollback to the original EAR/WAR file -------------------------------------------------------------------------------------------------------------------- Key: JOPR-16 URL: https://jira.jboss.org/jira/browse/JOPR-16 Project: Jopr Issue Type: Bug Components: Plugin - JBoss AS 4 Affects Versions: 2.1 Reporter: Ian Springer Assignee: Ian Springer Fix For: 2.2 This is mainly needed to for Embedded (see https://jira.jboss.org/jira/browse/EMBJOPR-28 for a description of why). -- 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

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Updated: (JOPR-9) Cannot handle multiple JBossAS connections with different credentials

by Ian Springer (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-9?page=com.atlassian.jira.plugin.... ] Ian Springer updated JOPR-9: ---------------------------- Attachment: rhq-jmx-plugin-1.1.0.GA.jar The attached rhq-jmx-plugin-1.1.0.GA.jar is a patched version of the 1.1.0.GA plugin, which included EMS 1.2.6, instead of EMS 1.2.5. To update a RHQ 1.1.0.GA, Jopr 2.1.0.GA, or JON 2.1.0.GA installation with this patched jmx plugin, do the following: 1) Overwrite <rhq-server-dir>/jbossas/server/default/deploy/rhq.ear/rhq-downloads/rhq-plugins/rhq-jmx-plugin-1.1.0.GA.jar with the patched jar. 2) If your Jopr Server is running, you should see a message informing you that it detected the updated jmx plugin jar and deployed it. If not, start up your Server now. 3) Update all of your Agents to the new version of the jmx plugin jar. To do so, either run the "plugins update" command from each Agent's prompt or execute the "Update All Plugins" operation from the corresponding Agent Resource's Operations tab. Note, if you have more than a handful of Agents, you may want to create a Compatible Group containing all Agent Resources and then execute the "Update All Plugins" operation on the Compatible Group. The JNP credentials bug should no longer occur. > Cannot handle multiple JBossAS connections with different credentials > --------------------------------------------------------------------- > > Key: JOPR-9 > URL: https://jira.jboss.org/jira/browse/JOPR-9 > Project: Jopr > Issue Type: Bug > Affects Versions: 2.1 > Reporter: Greg Hinkle > Assignee: Ian Springer > Fix For: 2.2 > > Attachments: rhq-jmx-plugin-1.1.0.GA.jar > > > Opened from RHQ-1030... > Basically, the JBoss JNP context factory is storing principal and credentials in thread-locals so that we can have two stubs to different AS instances that require different principal/credentials. I tried jnp.restoreLoginIdentity and jnp.multi-threaded, but that will only let you support different connections in different threads. > After some testing, it looks like we can just have EMS setup the SecurityAssociation before every call into the stub. It should be fairly easy since EMS uses dynamic proxies around the stubs. > SecurityAssociation.setPrincipal(new SimplePrincipal("-principal-")); > SecurityAssociation.setCredential("-credentials-"); -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JOPR-9) Cannot handle multiple JBossAS connections with different credentials

by Ian Springer (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-9?page=com.atlassian.jira.plugin.... ] Ian Springer commented on JOPR-9: --------------------------------- REPRO STEPS ============= Setup 5 or more JBossAS and/or JBossEAP instances *all on the same machine* (you'll want to bind each instance to a different IP - e.g., 127.0.0.1, 127.0.0.2, etc.). For each instance: 1) Make sure authentication is enabled for the JMX invoker service (uncomment the block in deploy/jmx-invoker-service.xml). 2) Set it up to use a unique username and password in conf/props/jmx-console-users.properties, e.g.: instance1: admin1:admin1 instance2: admin2:admin2 instance3: admin3:admin1 instance4: admin4:admin4 instance5: admin4:admin5 Note, for two of the instances, use the same username, but different passwords (like instance4 and instance5 above). 3) Start up the instance and let JON discover it. 4) Import the discovered resource. 5) Edit its conn props and set the username and password to the correct values for the instance. 6) Verify that the instance turns green. Once all instances are green, let the AS instances and the JON Server and Agent run for a few hours. Check periodically and make sure all instances are still green and that there are no EMS connection/authentication errors in the Agent log. > Cannot handle multiple JBossAS connections with different credentials > --------------------------------------------------------------------- > > Key: JOPR-9 > URL: https://jira.jboss.org/jira/browse/JOPR-9 > Project: Jopr > Issue Type: Bug > Affects Versions: 2.1 > Reporter: Greg Hinkle > Assignee: Ian Springer > Fix For: 2.2 > > > Opened from RHQ-1030... > Basically, the JBoss JNP context factory is storing principal and credentials in thread-locals so that we can have two stubs to different AS instances that require different principal/credentials. I tried jnp.restoreLoginIdentity and jnp.multi-threaded, but that will only let you support different connections in different threads. > After some testing, it looks like we can just have EMS setup the SecurityAssociation before every call into the stub. It should be fairly easy since EMS uses dynamic proxies around the stubs. > SecurityAssociation.setPrincipal(new SimplePrincipal("-principal-")); > SecurityAssociation.setCredential("-credentials-"); -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (JOPR-9) Cannot handle multiple JBossAS connections with different credentials

by Ian Springer (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-9?page=com.atlassian.jira.plugin.... ] Ian Springer resolved JOPR-9. ----------------------------- Resolution: Done Fixed using Greg's suggested fix - MC4J r594, RHQ r1889. Note, after svn up'ing to RHQ r1889, people should do a clean build of the jmx plugin to make sure the EMS 1.2.5 jar gets purged from the plugin's lib dir. > Cannot handle multiple JBossAS connections with different credentials > --------------------------------------------------------------------- > > Key: JOPR-9 > URL: https://jira.jboss.org/jira/browse/JOPR-9 > Project: Jopr > Issue Type: Bug > Affects Versions: 2.1 > Reporter: Greg Hinkle > Assignee: Ian Springer > Fix For: 2.2 > > > Opened from RHQ-1030... > Basically, the JBoss JNP context factory is storing principal and credentials in thread-locals so that we can have two stubs to different AS instances that require different principal/credentials. I tried jnp.restoreLoginIdentity and jnp.multi-threaded, but that will only let you support different connections in different threads. > After some testing, it looks like we can just have EMS setup the SecurityAssociation before every call into the stub. It should be fairly easy since EMS uses dynamic proxies around the stubs. > SecurityAssociation.setPrincipal(new SimplePrincipal("-principal-")); > SecurityAssociation.setCredential("-credentials-"); -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JOPR-9) Cannot handle multiple JBossAS connections with different credentials

by Joseph Marques (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-9?page=com.atlassian.jira.plugin.... ] Joseph Marques commented on JOPR-9: ----------------------------------- Fady found this even earlier than RHQ-1030 -- http://jira.rhq-project.org/browse/RHQ-945 > Cannot handle multiple JBossAS connections with different credentials > --------------------------------------------------------------------- > > Key: JOPR-9 > URL: https://jira.jboss.org/jira/browse/JOPR-9 > Project: Jopr > Issue Type: Bug > Affects Versions: 2.1 > Reporter: Greg Hinkle > Assignee: Ian Springer > Fix For: 2.2 > > > Opened from RHQ-1030... > Basically, the JBoss JNP context factory is storing principal and credentials in thread-locals so that we can have two stubs to different AS instances that require different principal/credentials. I tried jnp.restoreLoginIdentity and jnp.multi-threaded, but that will only let you support different connections in different threads. > After some testing, it looks like we can just have EMS setup the SecurityAssociation before every call into the stub. It should be fairly easy since EMS uses dynamic proxies around the stubs. > SecurityAssociation.setPrincipal(new SimplePrincipal("-principal-")); > SecurityAssociation.setCredential("-credentials-"); -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Work started: (JOPR-9) Cannot handle multiple JBossAS connections with different credentials

by Ian Springer (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-9?page=com.atlassian.jira.plugin.... ] Work on JOPR-9 started by Ian Springer. > Cannot handle multiple JBossAS connections with different credentials > --------------------------------------------------------------------- > > Key: JOPR-9 > URL: https://jira.jboss.org/jira/browse/JOPR-9 > Project: Jopr > Issue Type: Bug > Affects Versions: 2.1 > Reporter: Greg Hinkle > Assignee: Ian Springer > Fix For: 2.2 > > > Opened from RHQ-1030... > Basically, the JBoss JNP context factory is storing principal and credentials in thread-locals so that we can have two stubs to different AS instances that require different principal/credentials. I tried jnp.restoreLoginIdentity and jnp.multi-threaded, but that will only let you support different connections in different threads. > After some testing, it looks like we can just have EMS setup the SecurityAssociation before every call into the stub. It should be fairly easy since EMS uses dynamic proxies around the stubs. > SecurityAssociation.setPrincipal(new SimplePrincipal("-principal-")); > SecurityAssociation.setCredential("-credentials-"); -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Assigned: (JOPR-9) Cannot handle multiple JBossAS connections with different credentials

by Ian Springer (JIRA)

[ https://jira.jboss.org/jira/browse/JOPR-9?page=com.atlassian.jira.plugin.... ] Ian Springer reassigned JOPR-9: ------------------------------- Assignee: Ian Springer > Cannot handle multiple JBossAS connections with different credentials > --------------------------------------------------------------------- > > Key: JOPR-9 > URL: https://jira.jboss.org/jira/browse/JOPR-9 > Project: Jopr > Issue Type: Bug > Affects Versions: 2.1 > Reporter: Greg Hinkle > Assignee: Ian Springer > Fix For: 2.2 > > > Opened from RHQ-1030... > Basically, the JBoss JNP context factory is storing principal and credentials in thread-locals so that we can have two stubs to different AS instances that require different principal/credentials. I tried jnp.restoreLoginIdentity and jnp.multi-threaded, but that will only let you support different connections in different threads. > After some testing, it looks like we can just have EMS setup the SecurityAssociation before every call into the stub. It should be fairly easy since EMS uses dynamic proxies around the stubs. > SecurityAssociation.setPrincipal(new SimplePrincipal("-principal-")); > SecurityAssociation.setCredential("-credentials-"); -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JOPR-15) With jmx remoting enabled JBAS JVM servers are found as sibling resources rather than child resources

by Charles Crouch (JIRA)

With jmx remoting enabled JBAS JVM servers are found as sibling resources rather than child resources ----------------------------------------------------------------------------------------------------- Key: JOPR-15 URL: https://jira.jboss.org/jira/browse/JOPR-15 Project: Jopr Issue Type: Bug Components: Plugin - JBoss AS 4 Affects Versions: 2.1 Reporter: Charles Crouch Normally when you start a JBAS instance with -Djboss.platform.mbeanserver the JON agent will discover the JVM MBeanServer running underneath the JBAS instance as a *child* resource of the JBAS Server. However if you have jmx remoting enabled then the JVM resource is found as *sibling* of the JBAS resource. -- 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

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JOPR-13) add Path and Exploded traits to WAR and EAR Resource types

by Ian Springer (JIRA)

add Path and Exploded traits to WAR and EAR Resource types ---------------------------------------------------------- Key: JOPR-13 URL: https://jira.jboss.org/jira/browse/JOPR-13 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4 Affects Versions: 2.1 Reporter: Ian Springer Assignee: Ian Springer Priority: Minor Fix For: 2.2 This is useful information for both enterprise and embedded. -- 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

16 years, 1 month

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jopr-issues November 2008