January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3445) CLONE - Fix description for read-resource operation

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created AS7-3445: -------------------------------------- Summary: CLONE - Fix description for read-resource operation Key: AS7-3445 URL: https://issues.jboss.org/browse/AS7-3445 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Rostislav Svoboda Assignee: Emanuel Muckenhuber Fix For: 7.1.0.Final {code} bin/jboss-admin.sh -c command=":read-operation-description(name="read-resource")" ... "include-runtime" => { "type" => BOOLEAN, "description" => "Whether to include runtime attributes (i.e. those whose value does not come from the persistent configuration) in the response. If absent, false is the default. Ignored if the 'recursive' parameter is set to true; i.e. runtime attributes can only be read in non-recursive queries.", ... {code} Remove 'Ignored if the 'recursive' parameter is set to true; i.e. runtime attributes can only be read in non-recursive queries.' Support for recursive queries with runtime details was added in AS7-2033 -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1420) DefaultSocketFactory: failed socket creations lead to sockets lingering in hashmap

by Bela Ban (JIRA)

Bela Ban created JGRP-1420: ------------------------------ Summary: DefaultSocketFactory: failed socket creations lead to sockets lingering in hashmap Key: JGRP-1420 URL: https://issues.jboss.org/browse/JGRP-1420 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0.4, 3.1 In TCPConnectionMap.TCPConnection(), the following code is executed: sock=socketFactory.createSocket(); // (1) sock.bind(); // (2) sock.connect(); // (3) In the first step, an unconnected socket is created and added to the 'sockets' hashmap in DefaultSocketFactory. This is used to dump the open sockets in a JGroups program (e.g. via probe.sh socks). However, if step (3) fails, e.g. because the destination is not reachable, the socket should be removed from the 'sockets' hashmap, but isn't ! SOLUTIUON: #1 Check all occurrences of this or similar code and make sure exceptions don't lead to lingering sockets #2 Make the 'sockets' hashmap a weak hashmap, so refs can be GC'ed when memory is low #3 Store string reps of the sockets rather than the sockets 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

14 years, 3 months

1
2
0 / 0

[JBoss JIRA] (JBADMCON-166) JBoss Admin console allows to add JMS destination with the same name twice without an error

by Tom Ross (JIRA)

Tom Ross created JBADMCON-166: --------------------------------- Summary: JBoss Admin console allows to add JMS destination with the same name twice without an error Key: JBADMCON-166 URL: https://issues.jboss.org/browse/JBADMCON-166 Project: JBoss Admin Console Issue Type: Bug Components: Hibernate Environment: EAP 5.1.2, HornetQ 2.2.10 Reporter: Tom Ross When creating a JMS destination in JBoss Admin console it is possible to create a destination with the same name twice. In each case the console reports "Successfully added new JMS Queue." -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-2933) Regression: WebMetaDataParser gives error on war with no version info in web.xml

by Kabir Khan (Created) (JIRA)

Regression: WebMetaDataParser gives error on war with no version info in web.xml -------------------------------------------------------------------------------- Key: AS7-2933 URL: https://issues.jboss.org/browse/AS7-2933 Project: Application Server 7 Issue Type: Bug Reporter: Kabir Khan Assignee: Jean-Frederic Clere Fix For: 7.1.0.CR1 To play with the deployment subsystem I normally deploy http://gwt-examples.googlecode.com/files/Calendar.war, which has no version info in its web.xml: {code} $unzip -p ~/temp/Calendar.war WEB-INF/web.xml <?xml version="1.0" encoding="ISO-8859-1"?> <web-app> <display-name>gwt-Calendar Compiled: Sun Jan 27 06:17:26 GMT 2008</display-name> <description>Google Web Toolkit Project</description> </web-app> {code} After https://github.com/jbossas/jboss-as/commit/977c1dd3c1717f53d96ae7dce32154... I see this error when deploying that war 16:35:07,788 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "Calendar.war" 16:35:08,023 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."Calendar.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."Calendar.war".PARSE: Failed to process phase PARSE of deployment "Calendar.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] at java.lang.Thread.run(Thread.java:680) [:1.6.0_29] Caused by: java.lang.IllegalStateException: Cannot obtain servlet version at org.jboss.metadata.parser.servlet.WebMetaDataParser.parse(WebMetaDataParser.java:103) at org.jboss.metadata.parser.servlet.WebMetaDataParser.parse(WebMetaDataParser.java:54) at org.jboss.as.web.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:87) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] ... 5 more A test should be added with a similar web.xml to guard against this in future -- 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

14 years, 3 months

6
5
0 / 0

[JBoss JIRA] (AS7-3331) JacORB SSL config parameters should use enumeration instead of values encoded in integers

by David Bosschaert (JIRA)

David Bosschaert created AS7-3331: ------------------------------------- Summary: JacORB SSL config parameters should use enumeration instead of values encoded in integers Key: AS7-3331 URL: https://issues.jboss.org/browse/AS7-3331 Project: Application Server 7 Issue Type: Task Components: IIOP, Server Affects Versions: 7.1.0.CR1b Reporter: David Bosschaert Assignee: Stefan Guilhen The JacORB SSL settings use a fairly cryptic way to express something that would be better represented as a string with 4 allowed values. >From the description: {noformat}client-supports: Value that indicates the client SSL supported parameters (EstablishTrustInTarget=20,EstablishTrustInClient=40,MutualAuth=60). client-requires: Value that indicates the client SSL required parameters (EstablishTrustInTarget=20,EstablishTrustInClient=40,MutualAuth=60). server-supports: Value that indicates the server SSL supported parameters (EstablishTrustInTarget=20,EstablishTrustInClient=40,MutualAuth=60). server-requires: Value that indicates the server SSL required parameters (EstablishTrustInTarget=20,EstablishTrustInClient=40,MutualAuth=60).{noformat} -- 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

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] (AS7-3184) Subdeployments not shown in JBoss console

by Richard Opalka (Created) (JIRA)

Subdeployments not shown in JBoss console ----------------------------------------- Key: AS7-3184 URL: https://issues.jboss.org/browse/AS7-3184 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1 Reporter: Richard Opalka Assignee: Heiko Braun Priority: Critical Fix For: 7.1.0.Final When there are subdeployments in ear these are not shown in JBoss administation console. For example there's missing web subdeployment with webservice endpoints listing. -- 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

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-2859) Management: unable to add connector listening on created interface

by Dominik Pospisil (Created) (JIRA)

Management: unable to add connector listening on created interface ------------------------------------------------------------------ Key: AS7-2859 URL: https://issues.jboss.org/browse/AS7-2859 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Beta1 Reporter: Dominik Pospisil Assignee: Brian Stansberry Creating connector listening on newly created inteface fails with: MSC00001: Failed to start service jboss.network.test-interface: org.jboss.msc.service.StartException in service jboss.network.test-interface: failed to resolve interface test-interface Steps to reproduce: 1) create new interface /interface=test-interface:add(nic="tun0") 2) add socket binding which uses created interface /socket-binding-group=standard-sockets/socket-binding=test-binding:add(interface="test-interface", port=9091) 3) add web connector /subsystem=web/connector=test:add(socket-binding="test-binding", protocol="HTTP/1.1", scheme="http") Step 3 fails with: 16:27:56,388 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.network.test-interface: org.jboss.msc.service.StartException in service jboss.network.test-interface: failed to resolve interface test-interface at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:95) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_23] at java.lang.Thread.run(Thread.java:679) [:1.6.0_23] 16:27:56,592 INFO [org.jboss.as.controller] (Remoting "simkin:MANAGEMENT" task-2) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.network.test-interface: org.jboss.msc.service.StartException in service jboss.network.test-interface: failed to resolve interface test-interface -- 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

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-2073) Add Connector Operation returns success even if connector fails to start

by Dominik Pospisil (Created) (JIRA)

Add Connector Operation returns success even if connector fails to start ------------------------------------------------------------------------ Key: AS7-2073 URL: https://issues.jboss.org/browse/AS7-2073 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Web Affects Versions: 7.1.0.Alpha1 Reporter: Dominik Pospisil Assignee: Brian Stansberry Steps to reproduce: 1) start standalone server 2) issue: /socket-binding-group=standard-sockets/socket-binding=https:add(port=8443) /subsystem=web/connector=test-connectr:add(socket-binding=https, scheme=https, protocol="HTTP/1.1", enabled=true) What happens is that created connector fails to start due to misssing keystore file. However the configuration model is updated and the operation returns success. I think that the model should be rolled back and the operation should return failure. -- 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

14 years, 3 months

7
11
0 / 0

[JBoss JIRA] (AS7-2403) Host Controller should log joining/leaving domain (INFO) level

by Kevin Barfield (Created) (JIRA)

Host Controller should log joining/leaving domain (INFO) level -------------------------------------------------------------- Key: AS7-2403 URL: https://issues.jboss.org/browse/AS7-2403 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Kevin Barfield Assignee: Brian Stansberry Priority: Minor When a host joins/leaves a domain, there is a INFO log message showing the slave join on the domain controller console. There should be the same INFO log message on the host controller console. -- 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

14 years, 3 months

6
5
0 / 0

[JBoss JIRA] (AS7-3437) JMS clients - Remote JNDI lookup does not work in EAP6/AS7

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/AS7-3437?page=com.atlassian.jira.plugin.s... ] Miroslav Novak commented on AS7-3437: ------------------------------------- JNP is not important in example code. "properties" should just express that lookups are remote. Main point of this jira was to have remote JNDI. Since AS7-1338 was re-opened, all discussions can move there. > JMS clients - Remote JNDI lookup does not work in EAP6/AS7 > ---------------------------------------------------------- > > Key: AS7-3437 > URL: https://issues.jboss.org/browse/AS7-3437 > Project: Application Server 7 > Issue Type: Feature Request > Reporter: Miroslav Novak > Assignee: David Lloyd > Priority: Blocker > Fix For: No Release > > > EAP6/AS7 have not yet implemented remote jndi lookups. This feature is important for standalone jms clients to work and also ensure backward compatibility with EAP5/AS6 applications. Following piece of code should work without change: > Properties properties = new Properties(); > properties.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory"); > properties.setProperty("java.naming.provider.url", "jnp://server_hostname:1099"); > properties.setProperty("java.naming.factory.url.pkgs", "org.jnp.interfaces.NamingContextFactory"); > context = new InitialContext(properties); > ConnectionFactory cf = (ConnectionFactory) context.lookup("RemoteConnectionFactory"); > con = cf.createConnection(); > session = con.createSession(false, Session.CLIENT_ACKNOWLEDGE); > Queue queue = (Queue) context.lookup("/queue/test"); > For now there is a workaround but it's not suitable for us. Example code: > https://github.com/jbossas/jboss-as/tree/master/demos/legacy/src/main/jav... > There are AS7 jiras related to this missing feature which are closed as rejected/duplicated. In AS7-1338 J. Green explains that some kind of remote jndi functionality will be in AS 7.1 (as part of the EE full profile). Unfortunately AS 7.1 is still missing this feature. -- 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

14 years, 3 months

1
0
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 January 2012