July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5084) Wrong text when add-user.sh adds a password for a slave HC

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5084: ------------------------------------- Summary: Wrong text when add-user.sh adds a password for a slave HC Key: AS7-5084 URL: https://issues.jboss.org/browse/AS7-5084 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.2.Final (EAP) Reporter: Brian Stansberry Assignee: Darran Lofthouse Priority: Minor Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 About to add user 'bstansberry' for realm 'ManagementRealm' ... Is this new user going to be used for one AS process to connect to another AS process e.g. slave domain controller? yes/no? That "e.g. slave domain controller" is poorly worded. Better is "e.g. a slave host controller connecting to the master domain controller?" Is there any other use case this question is handling? If not, let's just be simple and direct, e.g.: "Is this new user going to be used for a slave host controller connecting to the master domain controller?" -- 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

11 years, 10 months

2
2
0 / 0

[JBoss JIRA] (AS7-5089) ApplicationScoped Object is instantiated twice

by andrei povodyrev (JIRA)

andrei povodyrev created AS7-5089: ------------------------------------- Summary: ApplicationScoped Object is instantiated twice Key: AS7-5089 URL: https://issues.jboss.org/browse/AS7-5089 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld, REST Affects Versions: 7.1.2.Final (EAP) Environment: windows 7, rhel 6.1 Reporter: andrei povodyrev Assignee: Stuart Douglas Using the jboss-javaee6-webapp quickstart project Created EventCache ApplicationScoped object Injected into EventService Rest endpoint Deployed to EAP6 using JDStudio pointed browser to http://localhost:8080/jboss-javaee6-webapp/rest/events As can be seen from the logs EventCache object is instantiated 2 times -- 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

11 years, 10 months

2
6
0 / 0

[JBoss JIRA] (JGRP-1488) NPE in concurrent channel creation with shared transport

by Bela Ban (JIRA)

Bela Ban created JGRP-1488: ------------------------------ Summary: NPE in concurrent channel creation with shared transport Key: JGRP-1488 URL: https://issues.jboss.org/browse/JGRP-1488 Project: JGroups Issue Type: Bug Affects Versions: 3.0.10 Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0.11, 3.1 The NPE below is caused by calling GET_LOCAL_ADDRESS on all up_prots in a shared transport. However, when we create a new JChannel, its protocol stack is added to up_prots *before* the top_prot (RSVP in the case below) is connected to ProtocolStack. SOLUTION: connect the top protocol to ProtocolStack *before* connecting all protocols to each other and adding the bottom prot to up_prots in TP. 11:53:23,057 ERROR [org.jboss.msc.service.fail] (ChannelService lifecycle - 1) MSC00001: Failed to start service jboss.jgroups.channel.capedwarf: org.jboss.msc.service.StartException in service jboss.jgroups.channel.capedwarf: java.lang.NullPointerException at org.jboss.as.clustering.msc.AsynchronousService$1.run(AsynchronousService.java:68) [jboss-as-clustering-common-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_33] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_33] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] Caused by: java.lang.NullPointerException at org.jgroups.protocols.RSVP.up(RSVP.java:192) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.FRAG2.up(FRAG2.java:181) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.FlowControl.up(FlowControl.java:418) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.FlowControl.up(FlowControl.java:418) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.pbcast.GMS.up(GMS.java:889) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:265) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:383) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:602) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.BARRIER.up(BARRIER.java:148) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:143) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.FD.up(FD.java:273) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:288) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.MERGE2.up(MERGE2.java:205) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.Discovery.up(Discovery.java:499) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.TP.fetchLocalAddresses(TP.java:1529) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.TP.start(TP.java:939) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.protocols.UDP.start(UDP.java:225) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:938) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.JChannel.startStack(JChannel.java:841) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.JChannel.connect(JChannel.java:277) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jgroups.JChannel.connect(JChannel.java:261) [jgroups-3.0.9.Final.jar:3.0.9.Final] at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:44) [jboss-as-clustering-jgroups-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.clustering.msc.AsynchronousService$1.run(AsynchronousService.java:65) [jboss-as-clustering-common-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] ... 4 more -- 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

11 years, 10 months

1
1
0 / 0

[JBoss JIRA] (SECURITY-629) Create a new LoginModule to handle the server authentication

by Darran Lofthouse (Created) (JIRA)

Create a new LoginModule to handle the server authentication ------------------------------------------------------------ Key: SECURITY-629 URL: https://issues.jboss.org/browse/SECURITY-629 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.3.SP4 If we supply a module of our own to handle the server authentication we can solve a couple of problems: - 1 - Detect which Krb5LoginModule is actually available without needing different config for different JVMs 2 - Allow a username / password auth even though the identity will be used later with GSSAPI -- 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

11 years, 10 months

2
1
0 / 0

[JBoss JIRA] (SASL-12) Digest Hex to byte mis-match

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-12?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved SASL-12. ---------------------------------- Resolution: Out of Date Out of date and insufficient information. > Digest Hex to byte mis-match > ---------------------------- > > Key: SASL-12 > URL: https://issues.jboss.org/browse/SASL-12 > Project: JBoss SASL Provider > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Beta3 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.2.CR1 > > -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-542) Add Full Kerberos Support for EJB3 Invocations

by Darran Lofthouse (JIRA)

Add Full Kerberos Support for EJB3 Invocations ---------------------------------------------- Key: SECURITY-542 URL: https://jira.jboss.org/browse/SECURITY-542 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA Add full Kerberos support for EJB3 invocations. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
2
0 / 0

[JBoss JIRA] (AS7-2029) ConfigAdmin properties not replicated in domain mode

by Thomas Diesler (Created) (JIRA)

ConfigAdmin properties not replicated in domain mode ---------------------------------------------------- Key: AS7-2029 URL: https://issues.jboss.org/browse/AS7-2029 Project: Application Server 7 Issue Type: Task Components: Domain Management, OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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

11 years, 10 months

7
12
0 / 0

[JBoss JIRA] (AS7-5010) Stack overflow in management API with many Bundles deployed

by Thomas Diesler (JIRA)

11 years, 10 months

4
10
0 / 0

[JBoss JIRA] (AS7-351) Implement the HttpService ontop of JBossWeb

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-351?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler reassigned AS7-351: ---------------------------------- Assignee: Thomas Diesler > Implement the HttpService ontop of JBossWeb > ------------------------------------------- > > Key: AS7-351 > URL: https://issues.jboss.org/browse/AS7-351 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi, Web > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Priority: Critical > Attachments: DefaultHttpContext.java, http-service-1.2.pdf, HttpServiceImpl.java, registerServlet, ResourceServlet.java > > > Resolving this issue consolidates the Http services that we ship and should replace pax-web with an HttpService implemenation based on JBossWeb. > RFC-66 (WebApp) support is also covered by this issue. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-844) ResourceAdapterAssocation isn't applied to Work instances

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-844: ------------------------------------- Summary: ResourceAdapterAssocation isn't applied to Work instances Key: JBJCA-844 URL: https://issues.jboss.org/browse/JBJCA-844 Project: IronJacamar Issue Type: Bug Components: Core, Deployer Affects Versions: 1.1.0.Beta1, 1.0.11.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Critical Fix For: 1.0.12.Final, 1.1.0.Beta2 If a Work class implements ResourceAdapterAssociation the resource adapter instance isn't applied before execution -- 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

11 years, 10 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2012