July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4388) Provide clustering management use cases

by Heiko Braun (JIRA)

Heiko Braun created AS7-4388: -------------------------------- Summary: Provide clustering management use cases Key: AS7-4388 URL: https://issues.jboss.org/browse/AS7-4388 Project: Application Server 7 Issue Type: Task Components: Console Reporter: Heiko Braun Assignee: Bela Ban In order to prep the UI, we would need a list of typical clustering management use cases. -- 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, 12 months

6
11
0 / 0

[JBoss JIRA] (AS7-3751) Change the default object store of JBoss transactions to use the hornetq object store

by Tom Jenkinson (JIRA)

Tom Jenkinson created AS7-3751: ---------------------------------- Summary: Change the default object store of JBoss transactions to use the hornetq object store Key: AS7-3751 URL: https://issues.jboss.org/browse/AS7-3751 Project: Application Server 7 Issue Type: Feature Request Components: Transactions Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: Open To Community This would provide a performance boost, however it is not supportable until AS7-925 is complete as the object store cannot be manipulated on the filesystem to resolve heuristics, tooling is necessary. PS Do not implement this feature without tooling or discussing with me, I will add this after tooling is added. -- 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, 12 months

1
1
0 / 0

[JBoss JIRA] (AS7-4657) Add resolve-expressions param to operation read-resource

by Michael Voegele (JIRA)

Michael Voegele created AS7-4657: ------------------------------------ Summary: Add resolve-expressions param to operation read-resource Key: AS7-4657 URL: https://issues.jboss.org/browse/AS7-4657 Project: Application Server 7 Issue Type: Feature Request Reporter: Michael Voegele When reading a resource remotely, it would be nice to have the possibility to have expressions resolved. Following does of course not work, as the code runs in a separate jvm. {code:java} private void readRecursive(ModelNode modelNode, String modelNodeName, Map<String, Object> map) { switch (modelNode.getType()) { ... case EXPRESSION: // this would be great but won't work as it runs in a different jvm // ModelNode expression = modelNode.resolve(); // readRecursive(expression, modelNodeName, map); map.put(modelNodeName, modelNode.asString()); break; ... } {code} Therefore a param resolve-expressions for the read-resource operation would be good. -- 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, 12 months

2
4
0 / 0

[JBoss JIRA] (AS7-3834) Socket bind for JIoEndpoint fails on shutdown when using link-local IPv6 address

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created AS7-3834: ---------------------------------------- Summary: Socket bind for JIoEndpoint fails on shutdown when using link-local IPv6 address Key: AS7-3834 URL: https://issues.jboss.org/browse/AS7-3834 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.0.Final Reporter: Richard Achmatowicz Assignee: Mladen Turk 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

11 years, 12 months

7
27
0 / 0

[JBoss JIRA] (AS7-4740) Help description should reference form item titles opposed to the retype field names

by Heiko Braun (JIRA)

Heiko Braun created AS7-4740: -------------------------------- Summary: Help description should reference form item titles opposed to the retype field names Key: AS7-4740 URL: https://issues.jboss.org/browse/AS7-4740 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.Alpha1 -- 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, 12 months

1
4
0 / 0

[JBoss JIRA] (AS7-4610) Interface not found when deploying an EJB of class A that extends B and B implements an Interface

by Christoph Gutmann (JIRA)

Christoph Gutmann created AS7-4610: -------------------------------------- Summary: Interface not found when deploying an EJB of class A that extends B and B implements an Interface Key: AS7-4610 URL: https://issues.jboss.org/browse/AS7-4610 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.1.Final Reporter: Christoph Gutmann Assignee: jaikiran pai The class hierarchy is as follows: -class EJBClient extends class Client (POJO) -class Client implements interface MyInterface (POJO) When deploying EJB 'EJBClient', JBoss does not resolve indirectly implemented interface by an EJB via a superclass. This did work in JBoss5. When deploying such an EJB you get the error message {code} Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Bean class org.foo.EJBClient specifies @Local annotation, but does not implement 1 interface {code} -- 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, 12 months

3
3
0 / 0

[JBoss JIRA] (AS7-5083) Complete support OSGi webapps in JBossWeb

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5083: ----------------------------------- Summary: Complete support OSGi webapps in JBossWeb Key: AS7-5083 URL: https://issues.jboss.org/browse/AS7-5083 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Priority: Critical Fix For: 7.2.0.Alpha1 Attachments: webapp-1.0.pdf OSGi webapps are currently deployed onto jboss-osgi-webapp, which contains an embedded PAX-Web WAR extender that in turn delegates to the PAX-Web provided WebContainer based on Jetty. In the future, OSGi webapps should be handled by JBossWeb and be deployed onto the JBoss embedded Tomcat instance. -- 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, 12 months

2
11
0 / 0

[JBoss JIRA] (AS7-5235) Complete support for HttpService on JBossWeb

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5235: ----------------------------------- Summary: Complete support for HttpService on JBossWeb Key: AS7-5235 URL: https://issues.jboss.org/browse/AS7-5235 Project: Application Server 7 Issue Type: Task Components: OSGi, Web Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: 7.2.0.CR1 #1 Add support for MimeType, Content-Lenght, etc #2 Delegate authentication/authorisation to HttpContext #3 Add support for "/" root context #4 Make HttpService an optional capability #5 Make virtual host/port configurable -- 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, 12 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-1534) Ability to use alternate persistent stores for EJB timers

by Stuart Douglas (JIRA)

Ability to use alternate persistent stores for EJB timers --------------------------------------------------------- Key: AS7-1534 URL: https://issues.jboss.org/browse/AS7-1534 Project: Application Server 7 Issue Type: Feature Request Components: EJB Affects Versions: 7.0.1.Final Reporter: Stuart Douglas Assignee: Stuart Douglas We need the ability to store persistent timers in a JDBC database -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
7
0 / 0

[JBoss JIRA] Created: (RELOADED-8) Create a JSR-250 compliant injection framework on top of VDF

by Carlo de Wolf (JIRA)

Create a JSR-250 compliant injection framework on top of VDF ------------------------------------------------------------ Key: RELOADED-8 URL: https://jira.jboss.org/jira/browse/RELOADED-8 Project: JBoss Reloaded Issue Type: Feature Request Components: injection Affects Versions: injection-0.1.0 Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- 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

12 years

2
7
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