May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4754) NullPointerException in add-user.sh if username and password equal in silent mode.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4754: ------------------------------------- Summary: NullPointerException in add-user.sh if username and password equal in silent mode. Key: AS7-4754 URL: https://issues.jboss.org/browse/AS7-4754 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 [darranl@localhost bin]$ ./add-user.sh -a --silent=true dddd dddd Exception in thread "main" java.lang.NullPointerException at org.jboss.as.domain.management.security.state.ErrorState.execute(ErrorState.java:61) at org.jboss.as.domain.management.security.AddPropertiesUser.run(AddPropertiesUser.java:125) at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:169) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.modules.Module.run(Module.java:270) at org.jboss.modules.Main.main(Main.java:294) [darranl@localhost bin]$ -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4753) Use Flag.FAIL_SILENTLY for eviction cache operations.

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-4753: --------------------------------- Summary: Use Flag.FAIL_SILENTLY for eviction cache operations. Key: AS7-4753 URL: https://issues.jboss.org/browse/AS7-4753 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Minor Fix For: 7.2.0.Alpha1 Cache evictions (i.e. passivation operations) are not critical and should result in ERROR log messages. RetryingCacheInvoker will need to be modified such that the FAIL_SILENTLY flag is only applied on the last invocation (otherwise, the retry will be defeated). -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-4752) CLONE - Singleton Service fails on Windows with "IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results"

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4752: ----------------------------------- Summary: CLONE - Singleton Service fails on Windows with "IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results" Key: AS7-4752 URL: https://issues.jboss.org/browse/AS7-4752 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Environment: Windows -- any Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: 7.1.2.Final (EAP) As seen on hudson runs and observed by Tom C. (thanks Tom) : http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/ea... {noformat} 07:34:17,664 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/singleton].[org.jboss.as.test.clustering.cluster.singleton.service.MyServiceServlet]] (http--10.16.92.4-8080-1) Servlet.service() for servlet org.jboss.as.test.clustering.cluster.singleton.service.MyServiceServlet threw exception: java.lang.IllegalStateException: java.lang.IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results. at org.jboss.as.clustering.singleton.SingletonService$RpcHandler.getValueRef(SingletonService.java:225) [jboss-as-clustering-singleton-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] at org.jboss.as.clustering.singleton.SingletonService.getValue(SingletonService.java:176) [jboss-as-clustering-singleton-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] at org.jboss.as.clustering.singleton.SingletonService.getValue(SingletonService.java:53) [jboss-as-clustering-singleton-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1203) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at org.jboss.as.test.clustering.cluster.singleton.service.MyServiceServlet.doGet(MyServiceServlet.java:40) [classes:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.event(JBossWebContext.java:67) at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.invoke(JBossWebContext.java:48) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.15.Final-redhat-1.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.15.Final-redhat-1.jar:] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02] Caused by: java.lang.IllegalStateException: JBAS010350: Expected result from singleton provider only, but instead received 0 results. at org.jboss.as.clustering.singleton.SingletonService$RpcHandler.getValueRef(SingletonService.java:221) [jboss-as-clustering-singleton-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] ... 21 more {noformat} Test itself then fails with {noformat} Error Message Deployment with name deployment-1 could not be undeployed. Container container-1 must be still running. {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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4749) modcluster ssl values not saving correctly in console.

by Simeon Pinder (JIRA)

Simeon Pinder created AS7-4749: ---------------------------------- Summary: modcluster ssl values not saving correctly in console. Key: AS7-4749 URL: https://issues.jboss.org/browse/AS7-4749 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Environment: ER6 Reporter: Simeon Pinder Assignee: Paul Ferraro Start up an as7 instance in ha mode and navigate to profiles > Modcluster > SSL and attempt to set some values. On save the values set are not shown until you hit the edit button again. These appear to be saved in ui only. If you navigate away from the screen and return the values are all lost. The situation looks a little better if you explicitly add the ssl child via cli first but it still doesn't persist things correctly. -- 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

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] (AS7-4407) Security tests for EJB Injection fails

by Jan Lanik (JIRA)

Jan Lanik created AS7-4407: ------------------------------ Summary: Security tests for EJB Injection fails Key: AS7-4407 URL: https://issues.jboss.org/browse/AS7-4407 Project: Application Server 7 Issue Type: Task Components: EJB, Remoting, Security Reporter: Jan Lanik Assignee: Darran Lofthouse Priority: Critical Fix For: 7.1.0.Final Support for the PLAIN SASL mechanism to pass the username and password straight to JAAS. -- 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

13 years, 11 months

3
6
0 / 0

[JBoss JIRA] (JBRULES-3459) Performance regression when using 'matches' operator, comparing with 5.3.

by Petr Široký (JIRA)

Petr Široký created JBRULES-3459: ------------------------------------ Summary: Performance regression when using 'matches' operator, comparing with 5.3. Key: JBRULES-3459 URL: https://issues.jboss.org/browse/JBRULES-3459 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.4.0.CR1 Reporter: Petr Široký Assignee: Mark Proctor I am seeing performance regression when using rules with 'matches' and 'not matches' (comparing 5.4.0.CR1 and 5.3.0.Final). In my case the difference is up to 100 % (2000 ms vs 4000 ms). The DRL file contains 100 rules and in the test 500000 non-matching facts are inserted into knowledge session. See the attached standalone maven project. -- 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

13 years, 11 months

2
5
0 / 0

[JBoss JIRA] (AS7-4663) add support for ${prop} style replacement to attributes in the web subsystem

by Tom Fonteyne (JIRA)

Tom Fonteyne created AS7-4663: --------------------------------- Summary: add support for ${prop} style replacement to attributes in the web subsystem Key: AS7-4663 URL: https://issues.jboss.org/browse/AS7-4663 Project: Application Server 7 Issue Type: Feature Request Components: Web Affects Versions: 7.1.1.Final Reporter: Tom Fonteyne Assignee: Remy Maucherat It would be beneficial to allow ${property} style substitution on many if not all attributes of the web subsystem. This was present in JBoss 5.x, so customers are in effect loosing functionality when upgrading. Right now we are specifically looking at getting support for the ssl tag of a connector: attribute: key-alias But it might be easier & more consistent to simply add support for this to all attributes in one go, thereby avoiding to have to revisit this later for more attributes. -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] (AS7-4748) Update to console 1.3.1 (i18n hotfixes)

by Heiko Braun (JIRA)

Heiko Braun created AS7-4748: -------------------------------- Summary: Update to console 1.3.1 (i18n hotfixes) Key: AS7-4748 URL: https://issues.jboss.org/browse/AS7-4748 Project: Application Server 7 Issue Type: Task Components: Build System, Console Reporter: Heiko Braun Assignee: Paul Gier Fix For: 7.1.2.Final (EAP) -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1897) update jasper-jdt

by Jean-Frederic Clere (JIRA)

update jasper-jdt ----------------- Key: AS7-1897 URL: https://issues.jboss.org/browse/AS7-1897 Project: Application Server 7 Issue Type: Bug Components: Web Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 7.1.0.Beta1 the version is still 7.0.0.Beta8 should be the same as org.jboss.web -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
12
0 / 0

[JBoss JIRA] (JBRULES-3328) Add an API to allow access to the constraint occurrences of a solution

by David Glassborow (Created) (JIRA)

Add an API to allow access to the constraint occurrences of a solution ---------------------------------------------------------------------- Key: JBRULES-3328 URL: https://issues.jboss.org/browse/JBRULES-3328 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: FUTURE Reporter: David Glassborow Assignee: Mark Proctor For a given solution, I'd like to show what constraint occurrences are in the working memory, and ideally which occurrences for each planning entity. This allows end users to understand the schedule, in my experience otherwise they stop trusting the system. Currently the demo harness uses an internal API to get this information, and I think it maybe getting the wrong WM, the values looked out of step with the solver last time I looked -- 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

13 years, 11 months

4
4
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 May 2012