July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-3330) Tomcat6 Integration Issues With HEAD

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3330?page=all ] Anil Saldhana updated JBAS-3330: -------------------------------- Summary: Tomcat6 Integration Issues With HEAD (was: Tomcat6 Integration) > Tomcat6 Integration Issues With HEAD > ------------------------------------ > > Key: JBAS-3330 > URL: http://jira.jboss.com/jira/browse/JBAS-3330 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-5.0.0.Beta > Reporter: Anil Saldhana > Assigned To: Anil Saldhana > Fix For: JBossAS-5.0.0.Beta > > > This is the container task for all the issues that relate to the Tomcat6 integration in HEAD. > Individual JIRA issues can be linked to this issue for audit. > Note to Bill:- > This issue is assigned to you initially until you can get HEAD building clean with JDK4 and JDK5. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-3330) Tomcat6 Integration

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3330?page=all ] Anil Saldhana reopened JBAS-3330: --------------------------------- There are multiple issues with this integration. For example: http://jira.jboss.com/jira/browse/JBAS-3390 The tomcat-ssl-config is not starting because of an issue with JBossSocketFactory > Tomcat6 Integration > ------------------- > > Key: JBAS-3330 > URL: http://jira.jboss.com/jira/browse/JBAS-3330 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-5.0.0.Beta > Reporter: Anil Saldhana > Assigned To: Anil Saldhana > Fix For: JBossAS-5.0.0.Beta > > > This is the container task for all the issues that relate to the Tomcat6 integration in HEAD. > Individual JIRA issues can be linked to this issue for audit. > Note to Bill:- > This issue is assigned to you initially until you can get HEAD building clean with JDK4 and JDK5. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-593) suspend() and resume() failing in JBPM 3.1

by Chris OBrien (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-593?page=comments#action_12339524 ] Chris OBrien commented on JBPM-593: ----------------------------------- I am using jBPM 3.1.1, and have tried both the Hibernate3.jar that comes with jBPM as well as a Self built Hibernate 3.1.2 jar, and I do not have this issue at all. I can suspend and resume messages with the original queries (I checked) with no issue. Windows XP, JDK 1.4.2_06, jBPM 3.1.1 > suspend() and resume() failing in JBPM 3.1 > ------------------------------------------ > > Key: JBPM-593 > URL: http://jira.jboss.com/jira/browse/JBPM-593 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1 > Environment: Windows XP Pro, JDK 1.5.0_06, jBPM 3.1 > Reporter: Romin Irani > Assigned To: Tom Baeyens > Priority: Blocker > Fix For: jBPM 3.1.2 > > > The resume() and suspend() methods on the ProcessInstance are failing in jBPM 3.1. The resume() and suspend() methods on the ProcessInstance are failing in jBPM 3.1. The error is a SQL Syntax error "unknown column 'token'". On debugging, I have found the following named queries in the org/jbpm/db/hibernate.queries.hbm.xml as given below: > Code: > <query name="MessagingSession.suspendMessagesForToken"> > <![CDATA[ > update org.jbpm.msg.Message > set isSuspended = true > where token = :token > ]]> > </query> > <query name="MessagingSession.resumeMessagesForToken"> > <![CDATA[ > update org.jbpm.msg.Message > set isSuspended = false > where token = :token > ]]> > </query> > On changing them to the following > <query name="MessagingSession.suspendMessagesForToken"> > <![CDATA[ > update org.jbpm.msg.Message m > set m.isSuspended = true > where m.token = :token > ]]> > </query> > <query name="MessagingSession.resumeMessagesForToken"> > <![CDATA[ > update org.jbpm.msg.Message m > set m.isSuspended = false > where m.token = :token > ]]> > </query> > and replacing the file in JBPM JAR file, it worked. Note : I added the alias 'm'. > This is happening with the Hibernate JAR's that are shipped with JBPM 3.1 itself. I have not tried it out with Hibernate 3.1 standalone downloaded directly from the Hibernate site. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3391) Add FixedRate setting to org.jboss.monitor.services.TimerService (used to configure JMX Timers)

by Dimitris Andreadis (JIRA)

Add FixedRate setting to org.jboss.monitor.services.TimerService (used to configure JMX Timers) ----------------------------------------------------------------------------------------------- Key: JBAS-3391 URL: http://jira.jboss.com/jira/browse/JBAS-3391 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Scheduling/Timers Affects Versions: JBossAS-4.0.4.GA Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Priority: Minor Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 With the support for fixed-rate/fixed-delay execution in our implementation of javax.management.timer.Timer, we should expose thise option to TimerService wrapper, too. -- 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

20 years

1
1
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-737) Portlet instance component ref requires '/' application name prefix when automatic app. name discovery is used.

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-737?page=all ] Roy Russo resolved JBPORTAL-737. -------------------------------- Fix Version/s: 2.4 Final Resolution: Rejected Assignee: Roy Russo This is a non-issue in 2.4. > Portlet instance component ref requires '/' application name prefix when automatic app. name discovery is used. > --------------------------------------------------------------------------------------------------------------- > > Key: JBPORTAL-737 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-737 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation, Portal Core > Reporter: Tuomas Kiviaho > Assigned To: Roy Russo > Priority: Minor > Fix For: 2.4 Final > > > I'd like get rid of delete jboss-app.xml and let the deployment decide the application name, because that's currently the only information used from the file. > If I don't have the xml in place all of the portlet instances will be undeployed. > I can see from the database when manually creating a portlet instance that for some reason a '/' before application name has appeared. > When I change the *-object.xml file to have '/' as prefix for every component-ref the portlet instances are deployed, but if I recover the jboss-app.xml and use this new app. naming the result is again undeployment. > There is no mentioning about such side effect in documentation <http://docs.jboss.org/jbportal/v2.2/reference-guide/en/html/xmldescriptor...> > Could the component-ref app name part be automatically discovered when undeclared (cases when *-object.xml and portlet.xml reside in same web application) to reduce hard-to-discover couplings between configuration files. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-3281) javax.management.timer.Timer should perform fixed-delay periodic execution by default

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3281?page=all ] Dimitris Andreadis reopened JBAS-3281: -------------------------------------- > javax.management.timer.Timer should perform fixed-delay periodic execution by default > ------------------------------------------------------------------------------------- > > Key: JBAS-3281 > URL: http://jira.jboss.com/jira/browse/JBAS-3281 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, Scheduling/Timers > Affects Versions: JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1 > Environment: Java 1.4 (For Java 5.0 we use the implementation supplied with the JRE) > Reporter: Darran Lofthouse > Assigned To: Dimitris Andreadis > Priority: Critical > Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.Beta, JBossAS-3.2.8.SP2 > > > The implementation of javax.management.timer.Timer does not match the javadoc: - > http://java.sun.com/j2ee/1.4/docs/api/javax/management/timer/Timer.html > By default the timer should be using fixed-delay execution, our implementation is defaulting to fixed-rate execution. > In addition to this to use fixed-rate execution you should use the method addNotification(String, String, Object, Date, long, long, boolean), however we have not implemented this method and we just throw a RuntimeException if it is invoked. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-3281) javax.management.timer.Timer should perform fixed-delay periodic execution by default

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3281?page=all ] Dimitris Andreadis closed JBAS-3281. ------------------------------------ Resolution: Done > javax.management.timer.Timer should perform fixed-delay periodic execution by default > ------------------------------------------------------------------------------------- > > Key: JBAS-3281 > URL: http://jira.jboss.com/jira/browse/JBAS-3281 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, Scheduling/Timers > Affects Versions: JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1 > Environment: Java 1.4 (For Java 5.0 we use the implementation supplied with the JRE) > Reporter: Darran Lofthouse > Assigned To: Dimitris Andreadis > Priority: Critical > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1, JBossAS-3.2.8.SP2 > > > The implementation of javax.management.timer.Timer does not match the javadoc: - > http://java.sun.com/j2ee/1.4/docs/api/javax/management/timer/Timer.html > By default the timer should be using fixed-delay execution, our implementation is defaulting to fixed-rate execution. > In addition to this to use fixed-rate execution you should use the method addNotification(String, String, Object, Date, long, long, boolean), however we have not implemented this method and we just throw a RuntimeException if it is invoked. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-3281) javax.management.timer.Timer should perform fixed-delay periodic execution by default

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3281?page=all ] Dimitris Andreadis closed JBAS-3281. ------------------------------------ Resolution: Duplicate Issue The 2 API methods supporting fixed-rate execution were implemented. Support for fixed-delay execution was added, and this is now the default (used to be fixed-rate before). org.jboss.test.jbossmx.compliance.timer.PeriodTestCase shows both execution modes. One thing I've noticed is the produced notifications have always fixed-rate timestamps when run under jdk5, while we (jbossmx) correctly produce either fixed-rate or fixed-delay timestamps. The overal time is correct in both cases, though. One thing we need to check is the services that currently use JMX timers, to not assume a fixed-rate execution, by default. > javax.management.timer.Timer should perform fixed-delay periodic execution by default > ------------------------------------------------------------------------------------- > > Key: JBAS-3281 > URL: http://jira.jboss.com/jira/browse/JBAS-3281 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, Scheduling/Timers > Affects Versions: JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1 > Environment: Java 1.4 (For Java 5.0 we use the implementation supplied with the JRE) > Reporter: Darran Lofthouse > Assigned To: Dimitris Andreadis > Priority: Critical > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1, JBossAS-3.2.8.SP2 > > > The implementation of javax.management.timer.Timer does not match the javadoc: - > http://java.sun.com/j2ee/1.4/docs/api/javax/management/timer/Timer.html > By default the timer should be using fixed-delay execution, our implementation is defaulting to fixed-rate execution. > In addition to this to use fixed-rate execution you should use the method addNotification(String, String, Object, Date, long, long, boolean), however we have not implemented this method and we just throw a RuntimeException if it is invoked. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3281) javax.management.timer.Timer should perform fixed-delay periodic execution by default

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3281?page=all ] Dimitris Andreadis updated JBAS-3281: ------------------------------------- Summary: javax.management.timer.Timer should perform fixed-delay periodic execution by default (was: Implementation of javax.management.timer.Timer does not match javadoc) > javax.management.timer.Timer should perform fixed-delay periodic execution by default > ------------------------------------------------------------------------------------- > > Key: JBAS-3281 > URL: http://jira.jboss.com/jira/browse/JBAS-3281 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, Scheduling/Timers > Affects Versions: JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1 > Environment: Java 1.4 (For Java 5.0 we use the implementation supplied with the JRE) > Reporter: Darran Lofthouse > Assigned To: Dimitris Andreadis > Priority: Critical > Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.Beta, JBossAS-3.2.8.SP2 > > > The implementation of javax.management.timer.Timer does not match the javadoc: - > http://java.sun.com/j2ee/1.4/docs/api/javax/management/timer/Timer.html > By default the timer should be using fixed-delay execution, our implementation is defaulting to fixed-rate execution. > In addition to this to use fixed-rate execution you should use the method addNotification(String, String, Object, Date, long, long, boolean), however we have not implemented this method and we just throw a RuntimeException if it is invoked. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-950) Finish -ds section in ref guide

by Roy Russo (JIRA)

Finish -ds section in ref guide ------------------------------- Key: JBPORTAL-950 URL: http://jira.jboss.com/jira/browse/JBPORTAL-950 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 2.4 Final Reporter: Roy Russo Assigned To: Roy Russo -- 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

20 years

1
1
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 July 2006