May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-737) Provide an operation to test/verify a datasource configuration

by Heiko Braun (JIRA)

Provide an operation to test/verify a datasource configuration -------------------------------------------------------------- Key: AS7-737 URL: https://issues.jboss.org/browse/AS7-737 Project: Application Server 7 Issue Type: Enhancement Components: JCA Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
4
0 / 0

[JBoss JIRA] Resolved: (AS7-664) Allow for state to be maintained aganst the connection within the Management HTTP Server

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-664?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved AS7-664. ---------------------------------- Resolution: Done JBoss AS Commits https://github.com/jbossas/jboss-as/commit/f9d8f77e1bc2999504e04f18eb70c5... https://github.com/jbossas/jboss-as/commit/8ba6b1a7217c36c212deb02e742226... HTTP Server Commits https://github.com/jbossas/httpserver/commit/deb8fd66047388eb04b18590a3e9... https://github.com/jbossas/httpserver/commit/f03b20a449bdd3f67a614d55e000... https://github.com/jbossas/httpserver/commit/e1e85fd356b507340ecd4e49b291... > Allow for state to be maintained aganst the connection within the Management HTTP Server > ---------------------------------------------------------------------------------------- > > Key: AS7-664 > URL: https://issues.jboss.org/browse/AS7-664 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 7.0.0.CR1 > > > There is a need for state between client and server to be maintained, this task is to allow it to be maintained against the connection. > Uses for this could be authenticate on connection and cache the authentication against the connection. > Track generated nonces against the connection so a nonce can only be used on that connection. > Cache GSSContext used for negotiation against the connection. > Notes: - > An alternative could be session cookies, however this would require all clients to support cookies or some form of URL re-writing to embed the session ID, HTTP keep-alive is standard for HTTP 1.1 > Another alternative could be to identify the address of the client, however this would just be the IP address / host name and port - there are no guarantees that a new connection would not re-use the same port especially if more than one administrator was running on that host. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2873) Rule fires unexpectedly - not CE fails

by Wolfgang Laun (JIRA)

Rule fires unexpectedly - not CE fails -------------------------------------- Key: JBRULES-2873 URL: https://issues.jboss.org/browse/JBRULES-2873 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical The rule shown below fires, and then the code on the RHS prints "But cell ... matches" which is only possible when there is a Cell according to the constraints in the "not" CE. - The full Sudoku code is available. rule "column elimination" when not Setting() $i: Integer() # occurs in a Cell $c: Cell( free contains $i, $cs: cellSqr, $cc: cellCol ) # but not in another cell of the same square and a different column not Cell( this != $c, free contains $i, cellSqr == $cs, cellCol != $cc ) ## not ( $oc: Cell( this != $c ) ## and ## eval( $oc.getFree().contains( $i ) && ## $oc.getCellSqr().equals( $cs ) && ## ! $oc.getCellCol().equals( $cc ) ) ) # but there is a cell in the same column and another square containing this value $cx: Cell( freeCount > 1, free contains $i, cellCol == $cc, cellSqr != $cs ) then # remove the value from that other cell System.out.println( "column elimination due to " + $c.posAsString() + ": remove " + $i + " from " + $cx.posAsString() ); for( int iRow = 0; iRow < 9; iRow++ ){ for( int iCol = 0; iCol < 9; iCol++ ){ Cell cell = Sudoku.sudoku.cells[iRow][iCol]; if( ! cell.equals( $c ) && cell.getCellSqr().equals( $cs ) && ! cell.getCellCol().equals( $cc ) && cell.getFree().contains( $i ) ){ System.out.println( "But cell " + cell.toString() + " matches!" ); } } } for( Cell c: $cs.getCells() ){ System.out.print( c.posAsString() + ": " + c.getFree() + " cc="+c.getCellCol() + " cs="+c.getCellSqr() + "; " ); } System.out.println(); modify( $cx ){ blockValue( $i ) } end -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-9279) Add additional resteasy providers

by Stuart Douglas (JIRA)

Add additional resteasy providers --------------------------------- Key: JBAS-9279 URL: https://issues.jboss.org/browse/JBAS-9279 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta2 Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.0.0.CR1 We need the following additional Resteasy providers: * resteasy-spring (OPTIONAL if we support Spring within EAP) * resteasty-guice (OPTIONAL if we support Guice in EAP) * resteasy-jackson (REQUIRED) * resteasy-multipart (REQUIRED) * resteasy-atom (REQUIRED) * resteasy-jsapi (REQUIRED) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9209) Consider storing OSGi bundles outside the modules hirachy

by Thomas Diesler (JIRA)

Consider storing OSGi bundles outside the modules hirachy --------------------------------------------------------- Key: JBAS-9209 URL: https://issues.jboss.org/browse/JBAS-9209 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Thomas Diesler Assignee: Thomas Diesler [tdiesler@localhost jboss-as]$ git grep "This is an OSGi bundle" build/src/main/resources/modules/org/apache/aries/jmx/main/module.xml:  build/src/main/resources/modules/org/apache/aries/util/main/module.xml:  build/src/main/resources/modules/org/apache/felix/configadmin/main/module.xml:  build/src/main/resources/modules/org/jboss/as/osgi/configadmin/main/module.xml:  build/src/main/resources/modules/org/jboss/osgi/common/main/module.xml:  build/src/main/resources/modules/org/jboss/osgi/jmx/main/module.xml:  build/src/main/resources/modules/org/osgi/compendium/main/module.xml:  -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-8873) Unexpected error forwarding to login page - No active contexts for scope type javax.enterprise.context.RequestScoped

by q q (JIRA)

Unexpected error forwarding to login page - No active contexts for scope type javax.enterprise.context.RequestScoped -------------------------------------------------------------------------------------------------------------------- Key: JBAS-8873 URL: https://issues.jboss.org/browse/JBAS-8873 Project: JBoss Application Server Issue Type: Bug Components: Weld/CDI Environment: JBoss 6.0.0.M2, Windows XP SP3 Reporter: q q 2010-04-22 09:55:36,484 WARN [org.apache.catalina.authenticator.FormAuthenticator] (http-127.0.0.1-8080-1) Unexpected error forwarding to login page: javax.servlet.ServletException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-9276) Make the annotation @Management works in association with @Singleton

by Laurent Vandwalle (JIRA)

Make the annotation @Management works in association with @Singleton -------------------------------------------------------------------- Key: JBAS-9276 URL: https://issues.jboss.org/browse/JBAS-9276 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: 6.0.0.Final Reporter: Laurent Vandwalle Fix For: 6.1.0 In JBoss 5.1, the use of @Management in association with @Service allowed to manage (JMX Management) the singleton EJB. In JBoss 6.0 Final, @Service annotations can be replace by the JEE6 standard annotation @Singleton. The problem is that the @Management annoation does not work if used in association with the @Singleton annotation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2914) Rule misfires due to "not matches" not working

by Wolfgang Laun (JIRA)

Rule misfires due to "not matches" not working ----------------------------------------------- Key: JBRULES-2914 URL: https://issues.jboss.org/browse/JBRULES-2914 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.M1 Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical A constraint such as owner != $code || (owner == $code && mode not matches "-.{2}x.*") can be shown to fail, apparently due to the "not matches" returning true. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2917) matching of field==v1 || field==v2 breaks when variable binding is added

by Wolfgang Laun (JIRA)

matching of field==v1 || field==v2 breaks when variable binding is added ------------------------------------------------------------------------ Key: JBRULES-2917 URL: https://issues.jboss.org/browse/JBRULES-2917 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.M1 Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical Fix For: 5.2.0.M1 class Assignment { Class source, target; } The following rule fails to match when target == java.lang.Object.class rule ObjectIsAssignable when Assignment( $t: target == (java.lang.Object.class) || target == source ) then end The following rule fails to match when target == source rule ObjectIsAssignable when Assignment( $t: target == source || target == (java.lang.Object.class) ) then end The error does not occur if the binding ($t) is omitted. See Workaround. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2982) Massive performance degradation from 5.2.0.M1 to 5.2.0.M2

by Roman Novak (JIRA)

Massive performance degradation from 5.2.0.M1 to 5.2.0.M2 --------------------------------------------------------- Key: JBRULES-2982 URL: https://issues.jboss.org/browse/JBRULES-2982 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.2.0.M2 Reporter: Roman Novak Assignee: Mark Proctor Priority: Critical the drools-planner SolutionInitializer takes 75 minutes to complete im 5.2.0.M2 5.2.0.M1 took 9,5 Minutes It also seems that accumulation queries with init, action, result sections break down completely in performance. The following query takes now 3 minutes 45 secs to complete. Before it was ~1 sec. The cardinalities: PostingPeriodOpt = 5 MediumLocationOpt = 25000 MediumBookingOpt = 13000 query "queryMediumPartlyTaken" $pp : PostingPeriodOpt() $mlo : MediumLocationOpt(mTypeId == $pp.mTypeId) $mp: MediumPeriodUsage( subOptimal > 0 ) from accumulate( $mbo : MediumBookingOpt ( mediId == $mlo.mediId, eval(timeInterval.overlaps($pp.getCycle())) ), init ( MediumPeriodUsage $mpu = new MediumPeriodUsage($mlo, $pp); ), action( $mpu.addBooking( $mbo.getIndexRange() ); ), result( $mpu ) ) end -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2011