March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3363) Admin console: Creating a connector should show a list of available socket bindings

by Jan Martiska (JIRA)

Jan Martiska created AS7-3363: --------------------------------- Summary: Admin console: Creating a connector should show a list of available socket bindings Key: AS7-3363 URL: https://issues.jboss.org/browse/AS7-3363 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Priority: Optional Attachments: connector.png For better usability experience: there should be a combobox or something listing the current possibilities (existing socket bindings), because if you enter a socket binding name that does not exist, the creation of connector will fail. Screenshot shows it all. -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JGRP-1025) Harden FLUSH

by Bela Ban (JIRA)

Harden FLUSH ------------ Key: JGRP-1025 URL: https://jira.jboss.org/jira/browse/JGRP-1025 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Vladimir Blagojevic Fix For: 2.9 Make sure no FLUSH is left hanging, e.g. due to the crash of the flush leader after the START-FLUSH round. In other words, make analyze the code and make sure STOP-FLUSH is eventually called. -- 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

14 years, 2 months

2
8
0 / 0

[JBoss JIRA] (JBRULES-3431) Drools camel server doesn't work if deployed

by Alexandre Porcelli (JIRA)

Alexandre Porcelli created JBRULES-3431: ------------------------------------------- Summary: Drools camel server doesn't work if deployed Key: JBRULES-3431 URL: https://issues.jboss.org/browse/JBRULES-3431 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-camel Affects Versions: 5.4.0.Beta2 Environment: Tomcat 6, Tomcat 7 and JBoss AS 7. Reporter: Alexandre Porcelli Assignee: Alexandre Porcelli Fix For: 5.4.0.CR1 Probably due an update of Camel version, found several errors during deployment, things like non-existent xml files or misconfigured options. Its also fix this problem: http://camel.465427.n5.nabble.com/org-apache-camel-RuntimeCamelException-... -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] (AS7-3427) CLI archive

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-3427: -------------------------------------- Summary: CLI archive Key: AS7-3427 URL: https://issues.jboss.org/browse/AS7-3427 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Bernard Tison The idea is to have an archive containing deployment archives along with the cli script files: one of which deploys and sets up/configures the necessary resources and the other one undeploys and cleans things up, if necessary. The idea has been discussed http://lists.jboss.org/pipermail/jboss-as7-dev/2011-May/001836.html https://community.jboss.org/thread/164554 -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] (AS7-4138) Managed Servers started with no native interface in host controller to connect back to.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4138: ------------------------------------- Summary: Managed Servers started with no native interface in host controller to connect back to. Key: AS7-4138 URL: https://issues.jboss.org/browse/AS7-4138 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Darran Lofthouse Assignee: Brian Stansberry Fix For: 7.1.2.Final When running in domain model if there is a problem starting the native management interface this is not checked and the managed servers continue to be started - the issue with this is that the managed servers can not connect back to their host controller so they end up not really being managed ;-) One issue to keep in mind is that the management interfaces are supposed to start later in the process so that clients can not connect to them prematurely. Also the following comments already in DomainModelControllerService: - <bstansberry> darranl: DomainModelControllerService already has this in the block that installs the native mgmt service <bstansberry> / TODO look into adding some of these services in the handlers, but ON-DEMAND. <bstansberry> // Then here just add some simple service that demands them An easy way to reproduce in the past has been to use an incorrectly configured security realm although those issue identified have now been fixed - in the meantime specifying a non-existent security realm should trigger the same 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, 2 months

3
2
0 / 0

[JBoss JIRA] (AS7-4219) Invalid descriptor doesn't rejected - requirement of <servlet-name> uniqueness by specs.

by Remy Maucherat (JIRA)

[ https://issues.jboss.org/browse/AS7-4219?page=com.atlassian.jira.plugin.s... ] Remy Maucherat commented on AS7-4219: ------------------------------------- For the record, I marked this as a duplicate of another JIRA, which added XML validation. I'll now let you have fun with this JIRA and its companion "blocker". > Invalid descriptor doesn't rejected - requirement of <servlet-name> uniqueness by specs. > ---------------------------------------------------------------------------------------- > > Key: AS7-4219 > URL: https://issues.jboss.org/browse/AS7-4219 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.2.Final > Reporter: Pavel Janousek > Assignee: Remy Maucherat > > Invalid web.xml deployment descriptor like this: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" metadata-complete="false"> > <servlet> > <servlet-name>ConflictServlet</servlet-name> > <servlet-class>org.jboss.as.test.integration.web.servlet.deployment.DummyServlet</servlet-class> > </servlet> > <servlet> > <servlet-name>ConflictServlet</servlet-name> > <servlet-class>org.jboss.as.test.integration.web.servlet.deployment.DummyServlet</servlet-class> > </servlet> > </web-app> > {code} > isn't rejected during deploying a such WAR application. > Uniqueness of <servlet-name> is requirement of Servlet deployment descriptor. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-38) Update the pom dependencies so clients can just depend on Remoting JMX

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-38: -------------------------------------- Summary: Update the pom dependencies so clients can just depend on Remoting JMX Key: REMJMX-38 URL: https://issues.jboss.org/browse/REMJMX-38 Project: Remoting JMX Issue Type: Task Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 1.0.3.Final For Maven users it should not be complex for them to get the correct set of dependencies for a client. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] (REMJMX-8) Connection state notification suppport

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-8?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated REMJMX-8: ---------------------------------- Fix Version/s: 1.1.0.Beta1 (was: 1.0.3.Final) > Connection state notification suppport > -------------------------------------- > > Key: REMJMX-8 > URL: https://issues.jboss.org/browse/REMJMX-8 > Project: Remoting JMX > Issue Type: Task > Components: Connection, Notifications > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta1 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-39) Allow for the Remoting Connection to be available from the MBeanServerConnection

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-39: -------------------------------------- Summary: Allow for the Remoting Connection to be available from the MBeanServerConnection Key: REMJMX-39 URL: https://issues.jboss.org/browse/REMJMX-39 Project: Remoting JMX Issue Type: Task Components: Connection Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.3.Final In environments such as jconsole Remoting JMX will have been used to obtain the initial connection to the server - if jconsole then is expanded to enable management calls to the server this also needs to be able to connect to the server. This Jira is to create a way to obtain the Remoting Connection from the MBeanServerConnection so that additional channels can be opened. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] (AS7-4219) Invalid descriptor doesn't rejected - requirement of <servlet-name> uniqueness by specs.

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-4219?page=com.atlassian.jira.plugin.s... ] Pavel Janousek reopened AS7-4219: --------------------------------- Hm, linked JIRA was resolved in December last year, my report is against recent master in March, so it is evidently that problem *isn't* fully resolved yet. Developers have been claiming when we are reopening project JIRAs against already released release of AS7 (they say we should open *new* JIRA), so what exactly do you want? How we can report a such problem? > Invalid descriptor doesn't rejected - requirement of <servlet-name> uniqueness by specs. > ---------------------------------------------------------------------------------------- > > Key: AS7-4219 > URL: https://issues.jboss.org/browse/AS7-4219 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.2.Final > Reporter: Pavel Janousek > Assignee: Remy Maucherat > > Invalid web.xml deployment descriptor like this: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" metadata-complete="false"> > <servlet> > <servlet-name>ConflictServlet</servlet-name> > <servlet-class>org.jboss.as.test.integration.web.servlet.deployment.DummyServlet</servlet-class> > </servlet> > <servlet> > <servlet-name>ConflictServlet</servlet-name> > <servlet-class>org.jboss.as.test.integration.web.servlet.deployment.DummyServlet</servlet-class> > </servlet> > </web-app> > {code} > isn't rejected during deploying a such WAR application. > Uniqueness of <servlet-name> is requirement of Servlet deployment descriptor. -- 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, 2 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 March 2012