January 2011 - jboss-jira - Jboss List Archives

[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

13 years, 8 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

13 years, 8 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

13 years, 9 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

13 years, 9 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

13 years, 9 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWEB-195) AS7 Startup problem - Could not initialize class org.apache.tomcat.jni.OS

by Krzysztof Maslak (JIRA)

AS7 Startup problem - Could not initialize class org.apache.tomcat.jni.OS ------------------------------------------------------------------------- Key: JBWEB-195 URL: https://issues.jboss.org/browse/JBWEB-195 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Affects Versions: JBossWeb-7.0.0.Beta1 Environment: Fedora 13 2.6.34.7-66.fc13.i686 java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode) Reporter: Krzysztof Maslak Assignee: Remy Maucherat Problem occurs during JBoss startup. Problem appeared after upgrading JBoss Web from version 3.0.0-beta-7 to 7.0.0.Beta1. 16:43:00,465 ERROR [org.jboss.msc] (pool-1-thread-3) MSC-00001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: Failed to start service at org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1207) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20] at java.lang.Thread.run(Thread.java:619) [:1.6.0_20] Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.tomcat.jni.OS at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:573) at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:115) at org.apache.catalina.connector.Connector.initialize(Connector.java:1018) at org.apache.catalina.core.StandardService.addConnector(StandardService.java:351) at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:124) at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:90) at org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1163) ... 3 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-555) JBossAuthorizationManager->getSubjectRoles should check for null CBH

by Anil Saldhana (JIRA)

JBossAuthorizationManager->getSubjectRoles should check for null CBH -------------------------------------------------------------------- Key: SECURITY-555 URL: https://issues.jboss.org/browse/SECURITY-555 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v4_0_alpha2 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v4_0_alpha3 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-468) Annotations @RolesAllowed, @PermitAll and @DenyAll for authorization

by Anil Saldhana (JIRA)

Annotations @RolesAllowed, @PermitAll and @DenyAll for authorization -------------------------------------------------------------------- Key: SECURITY-468 URL: https://jira.jboss.org/jira/browse/SECURITY-468 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: PicketBox_v3_0_beta2 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_beta3 -- 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, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBSER-121) Unable to deserialize java.io.File in java 6

by Yannick Boucher (JIRA)

Unable to deserialize java.io.File in java 6 -------------------------------------------- Key: JBSER-121 URL: https://jira.jboss.org/browse/JBSER-121 Project: JBoss Serialization Issue Type: Bug Affects Versions: 1.0.3 GA Environment: Windows XP. Java jdk1.6.0_20 Reporter: Yannick Boucher Assignee: Clebert Suconic After investigation the implementation of File changed between java 5 & 6. The new implementation use ObjectInputStream.readFields() instead of ObjectInputStream.defaultReadObject(). After a little more investigation I found that any call to readFields() would throw an exception. -- 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, 9 months

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2011