July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-921) Booting AS7 on a system without any network connection throws up an error from ModClusterService

by jaikiran pai (JIRA)

Booting AS7 on a system without any network connection throws up an error from ModClusterService ------------------------------------------------------------------------------------------------ Key: AS7-921 URL: https://issues.jboss.org/browse/AS7-921 Project: Application Server 7 Issue Type: Bug Environment: AS7 upstream (dated May 30 2011) Reporter: jaikiran pai Assignee: Jean-Frederic Clere Fix For: 7.0.0.CR1 Starting AS7 (upstream) on a system which doesn't have any network connection throws up the following error during startup: {code} 15:38:22,766 ERROR [org.jboss.modcluster.ModClusterService] (MSC service thread 1-1) Error starting advertise listener: java.net.SocketException: No such device at java.net.PlainDatagramSocketImpl.join(Native Method) [:1.6.0_21] at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:172) [:1.6.0_21] at java.net.MulticastSocket.joinGroup(MulticastSocket.java:277) [:1.6.0_21] at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.init(AdvertiseListenerImpl.java:181) at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.start(AdvertiseListenerImpl.java:193) at org.jboss.modcluster.ModClusterService.init(ModClusterService.java:174) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.init(CatalinaEventHandlerAdapter.java:335) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.start(CatalinaEventHandlerAdapter.java:115) at org.jboss.as.modcluster.ModClusterService.start(ModClusterService.java:188) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] {code} Note that the server startup continues and starts up fine even with this error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
7
0 / 0

[JBoss JIRA] Created: (JBEE-85) Release javax.management.j2ee APIs

by Shelly McGowan (JIRA)

Release javax.management.j2ee APIs ---------------------------------- Key: JBEE-85 URL: https://issues.jboss.org/browse/JBEE-85 Project: JBoss JavaEE APIs Issue Type: Release Reporter: Shelly McGowan Assignee: Shelly McGowan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBEE-82) Release 2.0.0.CR1 jboss-javaee-specs-bom to align with AS 7.0.0.CR1

by Shelly McGowan (JIRA)

Release 2.0.0.CR1 jboss-javaee-specs-bom to align with AS 7.0.0.CR1 ------------------------------------------------------------------- Key: JBEE-82 URL: https://issues.jboss.org/browse/JBEE-82 Project: JBoss JavaEE APIs Issue Type: Release Components: javaee6_specs_bom Reporter: Shelly McGowan Assignee: Shelly McGowan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBEE-84) Release EJB 3.1 APIs which includes a change to the jax-rpc dependency (only)

by Shelly McGowan (JIRA)

Release EJB 3.1 APIs which includes a change to the jax-rpc dependency (only) ----------------------------------------------------------------------------- Key: JBEE-84 URL: https://issues.jboss.org/browse/JBEE-84 Project: JBoss JavaEE APIs Issue Type: Release Reporter: Shelly McGowan Assignee: Shelly McGowan There is a jax-rpc release now available in the JBoss Java EE API specs project: The EJB 3.1 pom has been changed to replace the dependency: <dependency> <groupId>javax.xml</groupId> <artifactId>jaxrpc-api</artifactId> <version>1.1</version> </dependency> with: <dependency> <groupId>org.jboss.spec.javax.xml.rpc</groupId> <artifactId>jboss-jaxrpc-api_1.1_spec</artifactId> <version>1.0.0.Final</version> <scope>provided</scope> </dependency> Therefore, a 1.0.1 release will be done for consideration of inclusion in AS 7 to minimize incorrect transitive dependencies. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBEE-19) Update jboss-ejb-api to EJB 3.1

by Carlo de Wolf (JIRA)

Update jboss-ejb-api to EJB 3.1 ------------------------------- Key: JBEE-19 URL: https://jira.jboss.org/jira/browse/JBEE-19 Project: JBoss JavaEE APIs Issue Type: Task Components: EJB API Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical -- 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

13 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-1367) size-rotating-file-handler rotate-size doens't properly handle add/update with management API

by Stan Silvert (JIRA)

size-rotating-file-handler rotate-size doens't properly handle add/update with management API --------------------------------------------------------------------------------------------- Key: AS7-1367 URL: https://issues.jboss.org/browse/AS7-1367 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.0.Final Reporter: Stan Silvert Assignee: Stan Silvert Fix For: 7.1.0.Alpha1 >From the management API, rotate-size doesn't handle the one-character suffixes for (b)yte, (k)ilobyte, (m)egabyte, etc. So for instance, if you say: /subsystem=logging/size-rotating-file-handler=SIZE:update-properties(rotate-size=5m) You will get an error because it will try to convert that to a long. If you enter a valid long without a suffix, then the value will be corrupted when the server is restarted. The solution is to keep this attribute as a String in the management model and only parse out the suffix when you need to convert to a long for the runtime. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8911) Expose ServerEnvironment as a management resource

by Brian Stansberry (JIRA)

Expose ServerEnvironment as a management resource ------------------------------------------------- Key: JBAS-8911 URL: https://issues.jboss.org/browse/JBAS-8911 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta1 Expose the information in the ServerEnvironment (which is the data acquired from the command line rather than the domain config) as a read-only management resource. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-8136) Consistent mechanism for masking passwords across the configuration

by Brian Stansberry (JIRA)

Consistent mechanism for masking passwords across the configuration ------------------------------------------------------------------- Key: JBAS-8136 URL: https://jira.jboss.org/browse/JBAS-8136 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> The means to mask passwords is different for >> the newer jboss-beans.xml files from the older mbean >> configurations. Would much rather have a one and done solution >> instead of managing two different solutions. With the AS 7 unified domain configuration this should fall out naturally, but we need to guard that no subsystems introduce non-standard ways of doing this. -- 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

13 years, 2 months

7
10
0 / 0

[JBoss JIRA] Created: (JBAS-8975) Annotation scanner for @Remote

by David Lloyd (JIRA)

Annotation scanner for @Remote ------------------------------ Key: JBAS-8975 URL: https://issues.jboss.org/browse/JBAS-8975 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-8974) Integrate Remoting 3.2.0

by David Lloyd (JIRA)

Integrate Remoting 3.2.0 ------------------------ Key: JBAS-8974 URL: https://issues.jboss.org/browse/JBAS-8974 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011