January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8411) Interface specified at host level but not at domain is accepted

by Brian Stansberry (JIRA)

Interface specified at host level but not at domain is accepted --------------------------------------------------------------- Key: JBAS-8411 URL: https://jira.jboss.org/browse/JBAS-8411 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 The current build/src/main/resources/domain/configuration/host.xml includes the declaration of an <interface name="public" at the host level and that interface is not declared in the domain. It's used in the <domain-controller><local> element but I think it should be required to be declared there. Interfaces directly under host should be used to clarify the host-specific IP address mapping for stuff declared in domain.xml. If the address name is only used in the DC config, then declare it there. -- 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

15 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-8550) Filesystem deployment service should use a different marker file for failed deployments

by Brian Stansberry (JIRA)

Filesystem deployment service should use a different marker file for failed deployments --------------------------------------------------------------------------------------- Key: JBAS-8550 URL: https://jira.jboss.org/browse/JBAS-8550 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.M2 >From Jesper Pedersen: Shouldn't a deployment which fails be called .failed instead of .deployed ? -- 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

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8795) Allow the plan for executing an operation to specify a list of required hosts / servers

by Brian Stansberry (JIRA)

Allow the plan for executing an operation to specify a list of required hosts / servers --------------------------------------------------------------------------------------- Key: JBAS-8795 URL: https://issues.jboss.org/browse/JBAS-8795 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 This is to record an idea for future consideration. When a client submits an operation to the domain or host controller, it can include rules for how many servers the operation can fail on within a server group before the operation is reverted across the server group. Add the ability to specify a list of servers and or hosts where the operation must succeed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources

by Savas Ali Tokmen (JIRA)

[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources --------------------------------------------------------------------------------------------- Key: JBAS-8319 URL: https://jira.jboss.org/browse/JBAS-8319 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: VFS Affects Versions: 6.0.0.M3, JBossAS-5.1.0.GA, JBossAS-5.0.1.GA, JBossAS-5.0.0.GA Environment: JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA) JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA) JBoss 6.0.0 M3 (jboss-vfs 3.0.0 CR5) Reporter: Savas Ali Tokmen Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x, and even maybe 6.x. Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.), we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP URL which contains all our deployable artifacts. As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5 and JBoss 6; in JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws: java.io.IOException: No context factory for http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war -- 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

15 years, 3 months

7
24
0 / 0

[JBoss JIRA] Created: (JBRULES-2858) misc. decision table bugs and improvements

by Wolfgang Laun (JIRA)

misc. decision table bugs and improvements ------------------------------------------ Key: JBRULES-2858 URL: https://issues.jboss.org/browse/JBRULES-2858 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 5.1.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.0.M2 RuleTable and column headers (CONDITION, ACTION,...) are ignored when written with a leading space. Errors are reported in row & column numbers; this should be done using cell names. Duplicate columns for rule attributes are silently ignored; there should be a diagnostic. NumberFormatException thrown on bad integer must be caught and result in a proper diagnostic. Description entry is notwritten into the generated DRL. Some attributes cannot be produced: lock-on-active, etc. NPE thrown for certain entries Documentation is rather "off" in several places. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-31) White Paper on JMX Security

by Anil Saldhana (JIRA)

White Paper on JMX Security --------------------------- Key: SECURITY-31 URL: http://jira.jboss.com/jira/browse/SECURITY-31 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: White Papers Reporter: Anil Saldhana Assigned To: Anil Saldhana There is a need for a simple technical white paper that talks about the various scenarios involved in security jmx in JBoss. This includes the jmx consoles as well as the invokers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8204) Deployment via a deployment plan

by Brian Stansberry (JIRA)

Deployment via a deployment plan -------------------------------- Key: JBAS-8204 URL: https://jira.jboss.org/browse/JBAS-8204 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M2 I want us to have some sort of deployment plan notion in our deployment API so users can specify in a document how a rolling upgrade should occur, e.g. here's the new deployment(s), first quiesce this set of servers, then upgrade, roll on to this set of servers, etc. Basically describe in a document the set of operations that are meant to be atomic. -- 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

15 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2833) DroolsCompilerAntTask should scan for drools.package first

by Tihomir Surdilovic (JIRA)

DroolsCompilerAntTask should scan for drools.package first ---------------------------------------------------------- Key: JBRULES-2833 URL: https://issues.jboss.org/browse/JBRULES-2833 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-ant Affects Versions: 5.1.1.FINAL Reporter: Tihomir Surdilovic Assignee: Tihomir Surdilovic Fix For: 5.2.0.M1 DroolsCompilerAntTask should scan for drools.package first, before other rule resources -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWEB-95) Provide a com.sun.net.httpserver.HttpServerProvider implementation

by Scott M Stark (JIRA)

Provide a com.sun.net.httpserver.HttpServerProvider implementation ------------------------------------------------------------------ Key: JBWEB-95 URL: http://jira.jboss.com/jira/browse/JBWEB-95 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tomcat Module Reporter: Scott M Stark Assigned To: Mladen Turk To plug jbossweb into jdk6, we need a com.sun.net.httpserver.HttpServerProvider implementation http://java.sun.com/javase/6/docs/jre/api/net/httpserver/spec/com/sun/net... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
12
0 / 0

[JBoss JIRA] Created: (JBWEB-183) "Wrong" encoding of ObjectNames for connector mbeans

by Dimitris Andreadis (JIRA)

"Wrong" encoding of ObjectNames for connector mbeans ---------------------------------------------------- Key: JBWEB-183 URL: https://jira.jboss.org/browse/JBWEB-183 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Affects Versions: JBossWeb-2.0.0.GA_CP10 Reporter: Dimitris Andreadis Assignee: Remy Maucherat Looking into this bug report: JBPAPP-3050: I think the "problem" is in tomcat/jbossweb. When it creates the JMX ObjectNames for connector MBeans, e.g. look at: http://anonsvn.jboss.org/repos/jbossweb/tags/JBOSSWEB_2_0_0_GA_CP15/src/s... ... public String getName() { String encodedAddr = ""; if (getAddress() != null) { encodedAddr = "" + getAddress(); if (encodedAddr.startsWith("/")) encodedAddr = encodedAddr.substring(1); encodedAddr = URLEncoder.encode(encodedAddr) + "-"; <=== HERE } return ("http-" + encodedAddr + endpoint.getPort()) ... Basically it encodes the address and so http-localhost/127.0.0.1-8080 becomes http-localhost%2F127.0.0.1-8080 If you address the MBean like this, it is visible to any JMX subystem (twiddle, SNMP, concole, etc.), so that could be considered a valid workaround: jboss.web:type=ThreadPool,name=http-localhost%2F127.0.0.1-8080 I guess tomcat/jboss should be using javax.management.ObjectName.quote(String) to encode the name: http://download.oracle.com/javase/1.5.0/docs/api/javax/management/ObjectN... No big deal. -- 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

15 years, 3 months

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