May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4700) refactor connector subsystems to make easier to browse for us and GSS

by Stefano Maestri (JIRA)

Stefano Maestri created AS7-4700: ------------------------------------ Summary: refactor connector subsystems to make easier to browse for us and GSS Key: AS7-4700 URL: https://issues.jboss.org/browse/AS7-4700 Project: Application Server 7 Issue Type: Task Reporter: Stefano Maestri Assignee: Stefano Maestri -- 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

13 years, 12 months

2
1
0 / 0

[JBoss JIRA] (AS7-3847) Non-standard format of IPv6 address(-es) in LOG files

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3847?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved AS7-3847. ----------------------------------- Resolution: Done I believe this is done; please re-open if not. > Non-standard format of IPv6 address(-es) in LOG files > ----------------------------------------------------- > > Key: AS7-3847 > URL: https://issues.jboss.org/browse/AS7-3847 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.0.Final > Reporter: Pavel Janousek > Assignee: Bartosz Baranowski > Fix For: 7.1.2.Final-redhat1 > > > There are several places where some IPv6 address related info is logged. The format of a such info is formally correct, but used format is against [RFC-5952|http://tools.ietf.org/html/rfc5952] - this RFC has status of +Proposed standard+ and I don't know any software product which doesn't follow it (at least by-default). > I think in enterprise product we should not violate this RFC. > I'm mentioning about LOG messages like: > {code} > 15:14:15,985 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /0:0:0:0:0:0:0:1%1:9999 > 15:14:15,990 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost6.localdomain6/0:0:0:0:0:0:0:1%1:4447 > {code} > In both lines IPv6 address should be stretched to "::1" string. > The second related issue (JBossWeb part) is tracked as AS7-3851. -- 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

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] (AS7-4529) a "failure-causes-rollback="false"" attribute for the filesystem scanner

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4529?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4529: ---------------------------------- Component/s: Domain Management > a "failure-causes-rollback="false"" attribute for the filesystem scanner > ------------------------------------------------------------------------ > > Key: AS7-4529 > URL: https://issues.jboss.org/browse/AS7-4529 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Max Rydahl Andersen > > JBIDE-11509, AS7-783 and TORQUE-576 all talk about the problem of all deployments found at startup is deployed in one operation and if one deployment fails all is rolled back resulting in some rather bad usability issues - especially at development time, but even also at production time for those using file deployments. > Suggestion on irc was that there could be an option on the file scanner (possibly false by default?) to say that failure causes rollback. > Individual deployments could then still fail, but at least not everything would be rolledback and it would still allow proper interdependent deployments to work. -- 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

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-829) make-pristine.sh to reset an AS installation to factory settings

by Bob McWhirter (JIRA)

make-pristine.sh to reset an AS installation to factory settings ---------------------------------------------------------------- Key: AS7-829 URL: https://issues.jboss.org/browse/AS7-829 Project: Application Server 7 Issue Type: Enhancement Reporter: Bob McWhirter Assignee: Jason Greene Not sure how this is better than unzip -q jboss-as-bin.zip, but being able to "reset" the domain and such (and bootstrap logging props) to out-of-the-box settings might be nice. Perhaps a separate script to clean the deployments and content repo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

4
3
0 / 0

[JBoss JIRA] (AS7-4706) Use Infinispan externalizers to reduce serialized size of replicated data

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-4706: --------------------------------- Summary: Use Infinispan externalizers to reduce serialized size of replicated data Key: AS7-4706 URL: https://issues.jboss.org/browse/AS7-4706 Project: Application Server 7 Issue Type: Enhancement Components: Clustering Affects Versions: 7.1.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 7.1.2.Final-redhat1 Testing indicates that serialized web sessions and SFSB are much bigger in AS7 than in AS6. This is largely due to the increased size of the class descriptors which additionally specify module names. While ClassTables have been written for the contents of the MarshalledValues which are stored in the cache, the same optimizations should happen for the cache keys and marshalled values themselves. -- 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

13 years, 12 months

1
1
0 / 0

[JBoss JIRA] (AS7-3874) Complete i18n of EJB3 subsystem

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-3874: ------------------------------------- Summary: Complete i18n of EJB3 subsystem Key: AS7-3874 URL: https://issues.jboss.org/browse/AS7-3874 Project: Application Server 7 Issue Type: Task Components: EJB Reporter: Brian Stansberry Assignee: jaikiran pai Fix For: 7.1.1.Final Needed for ANDIAMO-7 compliance. The EJB3 subsystem has quite a bit of stuff not using EJB3Messages. And probably missing use of EJB3Logger as well, although my scan using 'git grep "throw new"' was focused on missing error messages. -- 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

13 years, 12 months

3
4
0 / 0

[JBoss JIRA] (AS7-4703) CLONE - Create subsystem for JMS bridge

by Miroslav Novak (JIRA)

Miroslav Novak created AS7-4703: ----------------------------------- Summary: CLONE - Create subsystem for JMS bridge Key: AS7-4703 URL: https://issues.jboss.org/browse/AS7-4703 Project: Application Server 7 Issue Type: Task Components: JMS Affects Versions: 7.1.1.Final Reporter: Miroslav Novak Assignee: Jeff Mesnil Currently there is no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl) in AS7. In JBoss AS 6 and earlier you could deploy the bridge as an MBean or JBoss MC bean, but the current configuration schema in AS7 simply doesn't support it. The bridge is a nice feature so we need a way to deploy it. It doesn't make sense to add the JMS bridge to a <hornetq-server> because the bridge can operate independently of a local HornetQ server. It really needs its own subsystem. -- 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

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] (AS7-4702) mod_cluster takes up to 10 seconds to register with load balancer

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-4702: --------------------------------- Summary: mod_cluster takes up to 10 seconds to register with load balancer Key: AS7-4702 URL: https://issues.jboss.org/browse/AS7-4702 Project: Application Server 7 Issue Type: Enhancement Components: Clustering Affects Versions: 7.1.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.2.Final-redhat1 This should happen immediately following mod_cluster startup (as was the case in EAP5). We can be assured that the requisite connector is started since it is already a dependency. -- 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

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] (AS7-3752) Socket bind for Http11Apr fails on startup when using link-local IPv6 address

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created AS7-3752: ---------------------------------------- Summary: Socket bind for Http11Apr fails on startup when using link-local IPv6 address Key: AS7-3752 URL: https://issues.jboss.org/browse/AS7-3752 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.0.Final Reporter: Richard Achmatowicz Assignee: Remy Maucherat Start AS 7.1.0.Final with a link local IPv6 address: {noformat} [nrla@lenovo ~]$ /sbin/ifconfig eth0 Link encap:Ethernet HWaddr F0:DE:F1:40:75:B8 inet addr:192.168.0.103 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::f2de:f1ff:fe40:75b8/64 Scope:Link inet6 addr: 3ffe:ffff:100:f101::1/64 Scope:Global [nrla@lenovo ~]$ ./standalone.sh -Djboss.bind.address=fe80::f2de:f1ff:fe40:75b8 -Djboss.bind.address.management=fe80::f2de:f1ff:fe40:75b8 {noformat} and the following exception occurs: {noformat} 11:01:28,909 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /fe80:0:0:0:f2de:f1ff:fe40:75b8:4447 11:01:29,013 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.1.GA 11:01:29,185 ERROR [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-6) Error initializing endpoint: java.lang.Exception: Socket bind failed: [22] Invalid argument at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:578) [jbossweb-7.0.10.Final.jar:] at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:121) [jbossweb-7.0.10.Final.jar:] at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.10.Final.jar:] at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] 11:01:29,254 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] Caused by: LifecycleException: Protocol handler initialization failed: java.lang.Exception: Socket bind failed: [22] Invalid argument at org.apache.catalina.connector.Connector.init(Connector.java:985) at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) ... 5 more 11:01:29,442 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /fe80:0:0:0:f2de:f1ff:fe40:75b8:9999 11:01:29,462 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/nrla/projects/jboss-as/build/target/jboss-as-7.1.0.Final-SNAPSHOT/standalone/deployments 11:01:29,615 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 11:01:29,626 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector 11:01:29,649 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.0.Final-SNAPSHOT "Flux Capacitor" started (with errors) in 2317ms - Started 133 of 203 services (1 services failed or missing dependencies, 68 services are passive or on-demand) {noformat} I had a look around and found this related (in fact the same) bug report: https://issues.apache.org/bugzilla/show_bug.cgi?id=43327 Looks like it may have been fixed for IPv6 addresses other than link-local. Link-local addresses are used often for running on a local network segment. -- 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

13 years, 12 months

4
25
0 / 0

[JBoss JIRA] (AS7-4194) Allow for pluggable user stores within realms

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4194: ------------------------------------- Summary: Allow for pluggable user stores within realms Key: AS7-4194 URL: https://issues.jboss.org/browse/AS7-4194 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.2.Final We need to add the ability to plug in custom user store implementations - this will mean that should users and their passwords and roles be stored somewhere that we do not currently integrate with a custom store can be implemented to provide the bridge for username / password authentication. This should be provided in the form of a SPI as we will need clearly identify what these user stores can access and provide interfaces they can implement while being sure of backwards compatibility. This task will need to take into account both the loading of passwords based on usernames and realms and separately the loading of the roles. Implementations are free to manage their own connections but this should also contain support for using outbound connections defined in the domain model. The authentication process and role loading process occurs as two steps so this connection management should allow a connection to be shared by both steps. As a two step process this should also cope with state potentially being passed from step 1 to step 2 - i.e. an implementation may choose to load everything it knows about a user in step 1 and just return it in step 2. If a pluggable step is used in either step it should still be possible to use an AS provided mech for the other step. -- 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

13 years, 12 months

3
5
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 May 2012