November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1110) Support configuring home-load-balance-policy

by Brian Stansberry (JIRA)

Support configuring home-load-balance-policy -------------------------------------------- Key: EJBTHREE-1110 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1110 Project: EJB 3.0 Issue Type: Task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 5.0.0.Beta3 Users are allowed to configure a home interface on an @Clustered EJB3 bean. They should be able to configure the load balance policy used by that home, the same as they can for EJB2 homes. This means an added attribute for the @Clustered annotation and a change to the jboss_5_0.xsd. -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5018) Support bean declarations only in jboss.xml

by Brian Stansberry (JIRA)

Support bean declarations only in jboss.xml ------------------------------------------- Key: JBAS-5018 URL: http://jira.jboss.com/jira/browse/JBAS-5018 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB2, EJB3 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta3 JBossEnterpriseBeansMetaData.merge is not including any beans only declared in jboss.xml in the merged view. Since we have expanded the jboss.xml to essentially make the ejb-jar.xml unnecessary, we should be allowing for jboss.xml only entries. -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5017) Error opening Server Session rc=202

by Yang Yu (JIRA)

Error opening Server Session rc=202 ----------------------------------- Key: JBAS-5017 URL: http://jira.jboss.com/jira/browse/JBAS-5017 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Environment: Windows2000, Sun JDK 1.5.0_10 b03 Reporter: Yang Yu The JBoss server is functioning very well, but there are a bunch of error messages "Error opening Server Session rc=202" showing up in the JBoss console. I'd like to know what could cause this issue and how to avoid it, thanks in advance. -- 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

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4802) FirstAvailable target should not be transient

by Brian Stansberry (JIRA)

FirstAvailable target should not be transient --------------------------------------------- Key: JBAS-4802 URL: http://jira.jboss.com/jira/browse/JBAS-4802 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor If a bean proxy that already has a target established gets serialized (e.g. passed through a remote call), the sticky target is lost on the other end. This can lead to invocations against the same target bean on multiple servers. I don't see any reason for FirstAvailable.electedTarget to be transient. Problem here is changing this changes the serialized form of the class, breaking interoperability. Class also does not implement Externalizable. -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5005) Upgrade to JBoss Cache 1.4.1.SP7

by Brian Stansberry (JIRA)

Upgrade to JBoss Cache 1.4.1.SP7 -------------------------------- Key: JBAS-5005 URL: http://jira.jboss.com/jira/browse/JBAS-5005 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.3.GA Includes some useful fixes around buddy replication. -- 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

17 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4925) Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5)

by Dimitris Andreadis (JIRA)

Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5) ------------------------------------------------- Key: JBAS-4925 URL: http://jira.jboss.com/jira/browse/JBAS-4925 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JBoss Cache Affects Versions: JBossAS-4.2.2.GA Reporter: Dimitris Andreadis Assigned To: Brian Stansberry Fix For: JBossAS-4.2.3.GA Upgrade JBossCache to the latest SP6. -- 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

17 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-4934) JBossCacheWrapper should not re-use data gravitation option

by Brian Stansberry (JIRA)

JBossCacheWrapper should not re-use data gravitation option ----------------------------------------------------------- Key: JBAS-4934 URL: http://jira.jboss.com/jira/browse/JBAS-4934 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.2.0.GA, JBossAS-4.0.5.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.3.GA JBossCacheWrapper has a minor optimization where it creates an instance of Option, sets it to forceDataGravitation=true and then tries to re-use it across all invocations where we need to gravitate. This is invalid usage; JBC does not promise an Option will be in its original state when an invocation returns. Just need to create an Option for each call; no big deal. -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4939) Hudson JBoss-AS-5.0.x-TestSuite-sun15-noip testsuite run does not complete

by Dimitris Andreadis (JIRA)

Hudson JBoss-AS-5.0.x-TestSuite-sun15-noip testsuite run does not complete -------------------------------------------------------------------------- Key: JBAS-4939 URL: http://jira.jboss.com/jira/browse/JBAS-4939 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Brian Stansberry Priority: Critical Fix For: JBossAS-5.0.0.Beta3 JBoss-AS-5.0.x-TestSuite-sun15-noip does not complete. After discussing the issue in the jboss-dev list, Brian found out the nodes are not configured properly. Open this JIRA case to make sure we follow up. Eventually, we should get rid of the 'noip' run. -- 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

17 years, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1751) portlet-instances.xml security-constraints are not verified using request.isUserInRole()

by Johannes Fiala (JIRA)

portlet-instances.xml security-constraints are not verified using request.isUserInRole() ---------------------------------------------------------------------------------------- Key: JBPORTAL-1751 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1751 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Security Affects Versions: 2.6.2 Final, 2.6.1 Final Environment: Java JDK 1.4.2 Reporter: Johannes Fiala Assigned To: Julien Viet The implementation which verifies the security of portlet-instances.xml against the user roles currently doesn't seem to use request.isUserInRole(). Fact 1: If you use a role-link in the portlet.xml (to have a role which is not originally created by the Jboss Portal Loginmodule (IdentityLoginModule)) <portlet> ... <security-role-ref> <role-name>PortletUser</role-name> <role-link>User</role-link> </security-role-ref> </portlet> and then use it in the portlet-instances.xml: <instance> ... <security-constraint> <policy-permission> <role-name>PortletUser</role-name> <action-name>view</action-name> </policy-permission> </security-constraint> </instance> </deployment> the portlet instance will not show up. If you use the User-role instead, it works correctly. However, if I do a request.isUserInRole("PortletUser") in the portlet itself, it will always show up as expected. Fact 2: Additionally, it seems the portlet-instances.xml- security check also makes use of the org.jboss.portal.identity.auth.UserPrincipal. I wrote a custom loginmodule and added the "User"-role using my own Principal-class. Again, the portlet instance doesn't show up with my custom loginmodule. If I check it using request.isUserInRole("User"), it shows up correctly. -- 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

17 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBBUILD-429) Port [JBBUILD-428 - Add support for ThreadLocal.remove()] to JBossRetro1.0.4.GA

by Magesh Kumar B (JIRA)

Port [JBBUILD-428 - Add support for ThreadLocal.remove()] to JBossRetro1.0.4.GA ------------------------------------------------------------------------------- Key: JBBUILD-429 URL: http://jira.jboss.com/jira/browse/JBBUILD-429 Project: JBoss Build System Issue Type: Support Patch Components: JBossRetro Environment: JBoss4.0.5GA + JBossWS1.2.1.GA + JBWS-1860 + JDK1.4 Reporter: Magesh Kumar B Assigned To: Magesh Kumar B Priority: Blocker When the above combination is used the JBossWS DOMUtils throws the following exception: java.lang.NullPointerException at org.jboss.ws.core.utils.DOMUtils.getOwnerDocument(DOMUtils.java:529) at org.jboss.ws.core.soap.SOAPDocument.<init>(SOAPDocument.java:55) at org.jboss.ws.core.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:77) at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:66) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:243) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:179) at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:197) at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:449) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:534) This is due to the fact that jboss-retro sets null to the ThreadLocal's that are removed. -- 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

17 years, 1 month

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007