July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBPORTAL-660) Test servlet and filter commands

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-660?page=all ] Julien Viet updated JBPORTAL-660: --------------------------------- Fix Version/s: 2.6 Final (was: 2.4 Final) > Test servlet and filter commands > -------------------------------- > > Key: JBPORTAL-660 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-660 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Server > Affects Versions: 2.4 Final > Reporter: Julien Viet > Fix For: 2.6 Final > > -- 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: (JBPORTAL-908) do some real tests for portal migration app use

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-908?page=all ] Julien Viet updated JBPORTAL-908: --------------------------------- Fix Version/s: 2.6 Final (was: 2.4 Final) > do some real tests for portal migration app use > ----------------------------------------------- > > Key: JBPORTAL-908 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-908 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Migration > Reporter: Boleslaw Dawidowicz > Assigned To: Boleslaw Dawidowicz > Priority: Optional > Fix For: 2.6 Final > > Time Spent: 2 days, 4 hours > > perform some tests of migration app: > - with some *real* data > - for various databases (mysql, postgres) > - simulate data incostistency maybe? -- 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: (JBPORTAL-663) Test instance container

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-663?page=all ] Julien Viet updated JBPORTAL-663: --------------------------------- Fix Version/s: 2.6 Final (was: 2.4 Final) > Test instance container > ----------------------- > > Key: JBPORTAL-663 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-663 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.4 Final > Reporter: Julien Viet > Fix For: 2.6 Final > > -- 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: (JBPORTAL-662) Test portal object container

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-662?page=all ] Julien Viet updated JBPORTAL-662: --------------------------------- Fix Version/s: 2.6 Final (was: 2.4 Final) > Test portal object container > ---------------------------- > > Key: JBPORTAL-662 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-662 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.4 Final > Reporter: Julien Viet > Fix For: 2.6 Final > > -- 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: (JBPORTAL-659) Test web app instrumentation

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-659?page=all ] Julien Viet updated JBPORTAL-659: --------------------------------- Fix Version/s: 2.6 Final (was: 2.4 Final) > Test web app instrumentation > ---------------------------- > > Key: JBPORTAL-659 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-659 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Server > Affects Versions: 2.4 Final > Reporter: Julien Viet > Fix For: 2.6 Final > > -- 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-952) Shuting down JBP generates exception

by Sacha Labourey (JIRA)

Shuting down JBP generates exception ------------------------------------ Key: JBPORTAL-952 URL: http://jira.jboss.com/jira/browse/JBPORTAL-952 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Environment: 2.4rc1 Reporter: Sacha Labourey (please add "2.4 Branch" to affect version or 2.4rc1, etc. for proper reporting) start jbp, shutdown. It generates this: 21:32:30,640 INFO [Http11BaseProtocol] Pausing Coyote HTTP/1.1 on http-0.0.0.0- 8080 21:32:31,640 INFO [StandardService] Stopping service jboss.web 21:32:31,656 ERROR [UserInterceptor$UserFinalizer] Cannot finalize user 1 java.lang.NullPointerException at org.jboss.portal.core.aspects.server.UserInterceptor$UserFinalizer.or g$jboss$portal$core$aspects$server$UserInterceptor$UserFinalizer$finalizeUser$ao p(UserInterceptor.java:222) at org.jboss.portal.core.aspects.server.UserInterceptor$UserFinalizer$fi nalizeUser_7936384301567100739.invokeNext(UserInterceptor$UserFinalizer$finalize User_7936384301567100739.java) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.j ava:275) at org.jboss.portal.core.aspects.server.UserInterceptor$UserFinalizer$fi nalizeUser_7936384301567100739.invokeNext(UserInterceptor$UserFinalizer$finalize User_7936384301567100739.java) at org.jboss.portal.core.aspects.server.UserInterceptor$UserFinalizer.fi nalizeUser(UserInterceptor.java) at org.jboss.portal.core.aspects.server.UserInterceptor$UserFinalizer.va lueUnbound(UserInterceptor.java:200) at org.apache.catalina.session.StandardSession.removeAttributeInternal(S tandardSession.java:1609) at org.apache.catalina.session.StandardSession.expire(StandardSession.ja va:739) at org.apache.catalina.session.StandardSession.expire(StandardSession.ja va:645) at org.apache.catalina.session.StandardManager.stop(StandardManager.java :677) at org.apache.catalina.core.StandardContext.stop(StandardContext.java:43 45) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1066) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1066) at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:447) at org.jboss.web.tomcat.tc5.StandardService.stop(StandardService.java:61 0) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:743) at org.apache.catalina.startup.Catalina.stop(Catalina.java:601) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java: 503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:1 64) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.web.tomcat.tc5.Tomcat5.stopService(Tomcat5.java:497) at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSu pport.java:315) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB eanSupport.java:247) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept or.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM BeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor .java:97) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl ler.java:978) at $Proxy0.stop(Unknown Source) at org.jboss.system.ServiceController.stop(ServiceController.java:508) at sun.reflect.GeneratedMethodAccessor326.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.stop(Unknown Source) at org.jboss.deployment.SARDeployer.stop(SARDeployer.java:336) at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:658) at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:631) at org.jboss.deployment.MainDeployer.shutdown(MainDeployer.java:510) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept or.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM BeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.server.ServerImpl$ShutdownHook.shutdownDeployments(S erverImpl.java:1050) at org.jboss.system.server.ServerImpl$ShutdownHook.shutdown(ServerImpl.j ava:1025) at org.jboss.system.server.ServerImpl$ShutdownHook.run(ServerImpl.java:9 88) 21:32:31,828 INFO [Http11BaseProtocol] Stopping Coyote HTTP/1.1 on http-0.0.0.0 -8080 -- 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

2
3
0 / 0

[JBoss JIRA] Closed: (JBAS-3282) ScheduleManager MBean uses fixed-rate execution on Java 1.4 and fixed-delay execution on Java 5.0

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3282?page=all ] Dimitris Andreadis closed JBAS-3282. ------------------------------------ Fix Version/s: JBossAS-5.0.0.Beta Resolution: Done Schedule & SchedulerManager mbeans now have a FixedRate attribute which is false by default to match the default JMX Timer scheduling behaviour of FixedDelay execution as of JDK5 or JBoss v4.0.5. However, in the example configurations of: deploy/scheduler-service.xml deploy/schedule-manager-service.xml The default is overriden using FixedRate==true to match the expected behaviour of the jboss 4.x Timer, over jdk1.4 (which is FixedRate). > ScheduleManager MBean uses fixed-rate execution on Java 1.4 and fixed-delay execution on Java 5.0 > ------------------------------------------------------------------------------------------------- > > Key: JBAS-3282 > URL: http://jira.jboss.com/jira/browse/JBAS-3282 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.4.GA > Reporter: Darran Lofthouse > Assigned To: Dimitris Andreadis > Priority: Critical > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 > > > The ScheduleManager MBean uses fixed-rate execution on Java 1.4 and fixed-delay execution on Java 5.0 > The reason for this is because the ScheduleManager makes use of the javax.management.timer.Timer class, when running with Java 1.4 we use our implementation of the timer but when running with Java 5.0 we use the JRE implementation. > To get fixed-rate execution (which has been our default till Java 5.0) the ScheduleManager should be using the method addNotification(String, String, Object, Date, long, long, boolean) with the final boolean set to true. > We should possibly make the decision to use fixed-delay or fixed-rate configurable incase people are already expecting fixed-dalay with Java 5.0. -- 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] Assigned: (JBAS-3282) ScheduleManager MBean uses fixed-rate execution on Java 1.4 and fixed-delay execution on Java 5.0

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3282?page=all ] Dimitris Andreadis reassigned JBAS-3282: ---------------------------------------- Assignee: Dimitris Andreadis (was: Darran Lofthouse) > ScheduleManager MBean uses fixed-rate execution on Java 1.4 and fixed-delay execution on Java 5.0 > ------------------------------------------------------------------------------------------------- > > Key: JBAS-3282 > URL: http://jira.jboss.com/jira/browse/JBAS-3282 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scheduling/Timers > Affects Versions: JBossAS-4.0.4.GA > Reporter: Darran Lofthouse > Assigned To: Dimitris Andreadis > Priority: Critical > Fix For: JBossAS-4.0.5.CR1 > > > The ScheduleManager MBean uses fixed-rate execution on Java 1.4 and fixed-delay execution on Java 5.0 > The reason for this is because the ScheduleManager makes use of the javax.management.timer.Timer class, when running with Java 1.4 we use our implementation of the timer but when running with Java 5.0 we use the JRE implementation. > To get fixed-rate execution (which has been our default till Java 5.0) the ScheduleManager should be using the method addNotification(String, String, Object, Date, long, long, boolean) with the final boolean set to true. > We should possibly make the decision to use fixed-delay or fixed-rate configurable incase people are already expecting fixed-dalay with Java 5.0. -- 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: (JBIDE-341) Source lookup not supported

by Robert Stryker (JIRA)

Source lookup not supported --------------------------- Key: JBIDE-341 URL: http://jira.jboss.com/jira/browse/JBIDE-341 Project: JBoss IDE Issue Type: Bug Components: AOP Plugin Affects Versions: 2.0.0.Alpha, 1.6 Reporter: Robert Stryker Assigned To: Robert Stryker Fix For: 2.0.0.Beta2 Source lookup no longer supported due to a change in some eclipse code. Default source lookup provider no longer set. -- 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] Created: (JBAS-3392) JBossSocketFactory should flag absence of securityDomain

by Anil Saldhana (JIRA)

JBossSocketFactory should flag absence of securityDomain -------------------------------------------------------- Key: JBAS-3392 URL: http://jira.jboss.com/jira/browse/JBAS-3392 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.GA, JBossAS-3.2.8.SP2 If there is absence of securityDomain attribute on the connector setting in the server.xml, the JBossSocketFactory is throwing a NPE (which is masked by the Tomcat JSSESocketFactory implementation that throws a plain IOException). An evidence of this issue is the: http://jira.jboss.com/jira/browse/JBAS-3390 -- 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
2
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