September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBSEAM-47) Entity beans and session replication

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-47?page=comments#action_12343881 ] Gavin King commented on JBSEAM-47: ---------------------------------- This can now be handled my @Mutable .... should we make @Mutable a default for @Entity? > Entity beans and session replication > ------------------------------------ > > Key: JBSEAM-47 > URL: http://jira.jboss.com/jira/browse/JBSEAM-47 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > > We need to force HttpSession puts for entity bean and java bean components to ensure that state changes get replicated... -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3683) snmp-adaptor.sar/attributes.mib MIB syntax errors

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3683?page=comments#action_12343879 ] Dimitris Andreadis commented on JBAS-3683: ------------------------------------------ Thanks! Why you changed some counters to Gauge32 and left 2 of them as INTEGER? > snmp-adaptor.sar/attributes.mib MIB syntax errors > ------------------------------------------------- > > Key: JBAS-3683 > URL: http://jira.jboss.com/jira/browse/JBAS-3683 > Project: JBoss Application Server > Issue Type: Patch > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.4.GA > Environment: Using NET-SNMP 5.2.3 to parse the MIB > Reporter: Gerald Turner > Assigned To: Dimitris Andreadis > Priority: Trivial > Fix For: JBossAS-4.0.5.GA > > Attachments: snmp-adaptor-attributes.mib.patch.gz > > > Trivial patch to fix some syntax errors in attributes.mib. Things like the operator ":: =" cannot include a space and STATUS must be defined in an OBJECT-TYPE. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-3641) Updated bin/jboss_init_hpux.sh script

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3641?page=all ] Dimitris Andreadis closed JBAS-3641. ------------------------------------ Resolution: Done Updated. > Updated bin/jboss_init_hpux.sh script > ------------------------------------- > > Key: JBAS-3641 > URL: http://jira.jboss.com/jira/browse/JBAS-3641 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Environment: HP-UX > Reporter: john mendonca > Assigned To: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.Beta, JBossAS-3.2.8.SP2 > > Attachments: jboss_init_hpux.sh, jboss_init_hpux.sh > > > Entered at the request of Luc Texier: > <HP request from the Customer support Portal> > Please replace the <jbosshome>/bin/jboss_init_hpux.sh script with the attached updated version in your next release cycle: > - handles multiple jboss as instances > - updated comments (including installation instructions) > - more robust code -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-359) Abstract Seam core components from JSF-EL

by Gavin King (JIRA)

Abstract Seam core components from JSF-EL ----------------------------------------- Key: JBSEAM-359 URL: http://jira.jboss.com/jira/browse/JBSEAM-359 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Currently a bunch of core components (and possibly other stuff) calls to JSF for EL evaluation. We have already said we will migrate to using the unified EL stuff. However, the user should be able to plug in their own EL (eg. OGNL), so we should introduce a new core component ExpressionEvaluator to allow custom creation of MethodBindings and ValueBindings. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-358) Adding core.FacesMessages requires JSF libraries to compile component

by Christian Bauer (JIRA)

Adding core.FacesMessages requires JSF libraries to compile component --------------------------------------------------------------------- Key: JBSEAM-358 URL: http://jira.jboss.com/jira/browse/JBSEAM-358 Project: JBoss Seam Issue Type: Bug Reporter: Christian Bauer Priority: Minor I have this in a Seam component: // For error messages @In(create=true) private FacesMessages facesMessages; This is org.jboss.seam.core.FacesMessages. It doesn't extend anything from JSF but I still can't compile my Seam component without the JSF stubs on the classpath: /Users/turin/work/local/lab8/modules/beans/src/auction/beans/PlaceBidImpl.java Error:Error:line (112)cannot access javax.faces.application.FacesMessage file javax/faces/application/FacesMessage.class not found This is inconvenient because this is the only JSF compile-time dependency in all of my Seam components and I have to add the JSF libs to my compile classpath just for this. I don't really know why this is required... because of the static methods in FacesMessages? In any case, it would be nice to be able to send JSF messages without binding the component to JSF and I initially thought that this was the usecase for core.FacesMessages in Seam. -- 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

19 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-338) Changes to SeamInterceptor break non-JSF calls.

by Gavin King (JIRA)

Changes to SeamInterceptor break non-JSF calls. ----------------------------------------------- Key: JBSEAM-338 URL: http://jira.jboss.com/jira/browse/JBSEAM-338 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical The CVS changes to SeamInterceptor have it call Component.forName() outside of the Seam contexts when called via MDB or RMI. Need to call beginCall(), endCall() from the @PostConstruct and @PostActivate methods. -- 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

19 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-779) Split the faq directory into faq and faq-pojo

by Ben Wang (JIRA)

Split the faq directory into faq and faq-pojo --------------------------------------------- Key: JBCACHE-779 URL: http://jira.jboss.com/jira/browse/JBCACHE-779 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ben Wang Assigned To: Ben Wang Priority: Minor Fix For: 2.0.0 faq is for core JBoss Cache while faq-pojo is for PojoCache -- 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

19 years, 10 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBAS-2737) InternalManagedConnectionPool.removeTimedOut() should not destroy connections below the minimum pool size

by Weston Price (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2737?page=all ] Weston Price resolved JBAS-2737. -------------------------------- Fix Version/s: JBossAS-5.0.0.Beta Resolution: Done Added capability to force pool to never destroy connections below min if configured to do so. > InternalManagedConnectionPool.removeTimedOut() should not destroy connections below the minimum pool size > --------------------------------------------------------------------------------------------------------- > > Key: JBAS-2737 > URL: http://jira.jboss.com/jira/browse/JBAS-2737 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.3 SP1 > Environment: SUSE Linux, Sun JDK 1.4.2_08 (though this issue would be relevant to all platforms) > Reporter: Jim Paterson > Fix For: JBossAS-5.0.0.Beta > > > By default JBoss JDBC connection pools have a 15 minute idle time. Every time the IdleRemover runs it currently destroys every connection in the pool that has not been used in the last 15 minutes. It then establishes new connections if necessary to take the pool back up to its minimum size. > In most cases this behaviour probably doesn't cause problems. However, in our scenario it does. We are using DB2 and, in some situations, DB2 caches previously compiled query plans on a per connection basis. One specific example we have is a highly optimized search stored procedure that uses temporary tables. The IdleRemover is causing roughly 60% of our calls to this procedure to go through a new connection. This changes the response time from this stored procedure from ~200ms to ~2seconds as if triggers re-compilations in the database. > Because of this behaviour we do not want the application server to drop and restore connections unless they are in error or the pool has grown beyond the minimum size during a period of peak load. > I can understand that the current implementation protects the application server against stale connections. However, there are other mechanisms in the JDBC connection pool to handle this i.e. the the check-valid-connection-sql and valid-connection-checker-class-name parameters. > Do you agree that the current implementation should be changed? -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-3339) ValidConnectionChecker for Sybase DB

by Weston Price (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3339?page=all ] Weston Price resolved JBAS-3339. -------------------------------- Fix Version/s: JBossAS-5.0.0.Beta (was: JBossAS-4.0.5.GA) Resolution: Done Added SybaseValidConnection checker using equivalent select from dual method > ValidConnectionChecker for Sybase DB > ------------------------------------ > > Key: JBAS-3339 > URL: http://jira.jboss.com/jira/browse/JBAS-3339 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.5.GA > Reporter: Weston Price > Assigned To: Weston Price > Priority: Minor > Fix For: JBossAS-5.0.0.Beta > > > During consulting engagement a feature request for a Sybase validation connection checker was introduced. This would answer an issue for the client where RDBMS systems are brought down for mainteniance and they have to reboot JBossAS instances using Sybase. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-302) Invoking Topic management interface's listMessagesDurableSub()/ listMessagesNonDurableSub() with empty params throws exception

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-302?page=all ] Ovidiu Feodorov updated JBMESSAGING-302: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 > Invoking Topic management interface's listMessagesDurableSub()/ listMessagesNonDurableSub() with empty params throws exception > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBMESSAGING-302 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-302 > Project: JBoss Messaging > Issue Type: Bug > Components: Configuration and Management > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.0.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > 9:18:53,568 ERROR [[HtmlAdaptor]] Servlet.service() for servlet HtmlAdaptor threw exception > ava.lang.NumberFormatException: For input string: "" > at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > at java.lang.Long.parseLong(Long.java:424) > at java.lang.Long.valueOf(Long.java:518) > at sun.beans.editors.LongEditor.setAsText(LongEditor.java:24) > at org.jboss.util.propertyeditor.PropertyEditors.convertValue(PropertyEditors.java:260) > at org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:239) > at org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:223) > at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:262) > at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100) > at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > 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.CustomPrincipalValve.invoke(CustomPrincipalValve.java:54) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:173) > 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.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:595) -- 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

19 years, 10 months

1
0
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 September 2006