August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (EJBTHREE-630) EJB timers not persisted upon undeployment

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-630?page=all ] Carlo de Wolf resolved EJBTHREE-630. ------------------------------------ Resolution: Done Default the EJB3 timer service factory will use the JBoss timer service and restore it's timer upon deployment. > EJB timers not persisted upon undeployment > ------------------------------------------ > > Key: EJBTHREE-630 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-630 > Project: EJB 3.0 > Issue Type: Task > Reporter: Dimitris Andreadis > Assigned To: Carlo de Wolf > Fix For: EJB 3.0 RC9 - FD > > > Since jboss 4.0.4.GA (see JBAS-1091) ejb timers can be persisted at undeployment time. > However, this was a feature added to the org.jboss.ejb.txtimer.EJBTimerService API with a second removeTimerService method: > /** > * Remove the TimerService for a given containerId. > * > * This should be used to remove the timer service and timers for > * any type of container (session, entity, message) at the time of > * undeployment. > * > * @param containerId The string identifier for a class of TimedObjects > * @param keepState Flag indicating whether timer persistent state should be kept or removed > */ > void removeTimerService(ObjectName containerId, boolean keepState) throws IllegalStateException; > EJB3 uses the old removeTimerService() method that has the legacy behaviour of removing the timers at undeployment time. > void removeTimerService(ObjectName containerId, Object pKey) throws IllegalStateException; > So, call the new method instead. However, this will mean the EJB3 bundle will only run on JBoss4.0.4+ -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-619) Build EJB Timer Service on top of Quartz

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-619?page=comments#action_12341840 ] Carlo de Wolf commented on EJBTHREE-619: ---------------------------------------- The EJB3 stack can now be configured to use Quartz timer service by setting system property org.jboss.ejb3.timerservice.factory to org.jboss.ejb3.timerservice.quartz.QuartzTimerServiceFactory. > Build EJB Timer Service on top of Quartz > ---------------------------------------- > > Key: EJBTHREE-619 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-619 > Project: EJB 3.0 > Issue Type: Feature Request > Reporter: Carlo de Wolf > Assigned To: Carlo de Wolf > Fix For: EJB 3.0 RC9 - FD > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3555) LdapExtLoginModule fails if no initial bind credentials are supplied but anonymous login would be possible

by Felix Ho￟feld (JIRA)

LdapExtLoginModule fails if no initial bind credentials are supplied but anonymous login would be possible ---------------------------------------------------------------------------------------------------------- Key: JBAS-3555 URL: http://jira.jboss.com/jira/browse/JBAS-3555 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.4.GA Environment: 1.) LdapExtModule on JBoss 4.0.4.GA 2.) Novell eDirectory, possibly other LDAP-Server configuration, too Reporter: Felix Ho￟feld Assigned To: Scott M Stark Priority: Trivial Fix For: JBossAS-4.0.5.CR1 If an anonymous bind to the LDAP-Server is allowed no bindDN and bindCredential is supplied in login-context.xml. This causes the LoginModule to fail due to an NPE. The responsible lines are around 485: env.setProperty(Context.SECURITY_PRINCIPAL, dn); env.put(Context.SECURITY_CREDENTIALS, credential); The HashMap.put fails if dn or credetials are null. The obvious solution is to change the lines to: if (dn != null) env.setProperty(Context.SECURITY_PRINCIPAL, dn); if (credential != null) env.put(Context.SECURITY_CREDENTIALS, credential); -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Closed: (JBIDE-320) HQL Console in eclipse does not use eclipse preferences for colours of text, background or syntax highlighting

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-320?page=all ] Max Andersen closed JBIDE-320. ------------------------------ Fix Version/s: 2.0.0.Beta2 Resolution: Done There you go. done in http://opensource.atlassian.com/projects/hibernate/browse/HBX-735 > HQL Console in eclipse does not use eclipse preferences for colours of text, background or syntax highlighting > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-320 > URL: http://jira.jboss.com/jira/browse/JBIDE-320 > Project: JBoss IDE > Issue Type: Bug > Components: Hibernate Tools > Affects Versions: 1.6 > Environment: All > Reporter: Andrew Redhead > Fix For: 2.0.0.Beta2 > > Attachments: hql-consol-owncolours.png, hql-console-defaults.png > > > The HQL console uses black text and hard coded colours for syntax highlighting. > I use a black background and green text for most text/java/etc editing in eclipse. > With these settings, I end up with black text on a black background, which is kind of hard to read... ;) > At the moment, every time I use the HQL console, I have to change my preferences to use a white background (then change it back when I have finished). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCOMMON-2) Logging delegate initialization code should display extra info on failure

by Ovidiu Feodorov (JIRA)

Logging delegate initialization code should display extra info on failure ------------------------------------------------------------------------- Key: JBCOMMON-2 URL: http://jira.jboss.com/jira/browse/JBCOMMON-2 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Ovidiu Feodorov Assigned To: Scott M Stark Priority: Minor Fix For: 1.0.0.CR1 Patched attached -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCOMMON-3) Project compiles without javac.debug=on

by Ovidiu Feodorov (JIRA)

Project compiles without javac.debug=on --------------------------------------- Key: JBCOMMON-3 URL: http://jira.jboss.com/jira/browse/JBCOMMON-3 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ovidiu Feodorov Assigned To: Scott M Stark Fix For: 1.0.0.CR1 -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] Resolved: (JGRP-65) Performance tests and publish results

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-65?page=all ] Bela Ban resolved JGRP-65. -------------------------- Resolution: Done http://www.jgroups.org/javagroupsnew/perf/Report.html > Performance tests and publish results > ------------------------------------- > > Key: JGRP-65 > URL: http://jira.jboss.com/jira/browse/JGRP-65 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assigned To: Vladimir Blagojevic > Fix For: 2.4 > > > Run perf.Test with > - 4 members > - 1 - 4 senders > - Message sizes ranging from 100 bytes to 100K > - Number of messages 1 million > - Different transports -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-693) ResourceHandler fails to parse valid jboss-web.xml conforming to jboss-web_4_0.dtd

by Scott M Stark (JIRA)

ResourceHandler fails to parse valid jboss-web.xml conforming to jboss-web_4_0.dtd ---------------------------------------------------------------------------------- Key: EJBTHREE-693 URL: http://jira.jboss.com/jira/browse/EJBTHREE-693 Project: EJB 3.0 Issue Type: Bug Environment: org.jboss.test.web.test.WebIntegrationUnitTestCase Reporter: Scott M Stark Assigned To: Scott M Stark Deployment of a valid jboss-web_4_0.dtd jboss-web.xml fails to parse with the following exception: 17:29:09,626 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../tmp/deploy/tmp30208jbosstest-web.ear-contents/root-web-exp.war/ 17:29:09,756 INFO [TomcatDeployer] deploy, ctxPath=/jbosstest, warUrl=.../tmp/deploy/tmp30208jbosstest-web.ear-contents/jbosstest-web-exp.war/ 17:29:10,011 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-local-ref> of interface org.jboss.test.web.interfaces.StatelessSessionLocal and ejbLink of SecuredEJB in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,012 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-local-ref> of interface org.jboss.test.web.interfaces.StatelessSessionLocal and ejbLink of ENCBean0 in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,012 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-local-ref> of interface org.jboss.test.web.interfaces.RunAsTargetLocal and ejbLink of UnsecureRunAsServletWithPrincipalNameAndRolesTarget in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,015 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-local-ref> from interface only org.jboss.test.web.interfaces.StatelessSessionLocal in web.xml of jbosstest-web.warnot used by any EJBs 17:29:10,016 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-local-ref> of interface org.jboss.test.web.interfaces.StatelessSessionLocal and ejbLink of websubdir/relative.jar#SessionBean in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,016 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-local-ref> of interface org.jboss.test.web.interfaces.StatelessSessionLocal and ejbLink of jbosstest-web-ejbs.jar#OptimizedEJB in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,016 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-local-ref> of interface org.jboss.test.web.interfaces.RunAsTargetLocal and ejbLink of UnsecureRunAsServletWithPrincipalNameTarget in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,016 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-local-ref> of interface org.jboss.test.web.interfaces.StatelessSessionLocal and ejbLink of ENCBean1 in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,016 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface org.jboss.test.web.interfaces.StatelessSession and ejbLink of OptimizedEJB in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,017 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface org.jboss.test.web.interfaces.StatelessSession and ejbLink of ENCBean1 in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,017 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface org.jboss.test.web.interfaces.StatelessSession and ejbLink of ENCBean0 in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,017 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface org.jboss.test.web.interfaces.StatelessSession and ejbLink of SecuredEJB in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,017 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface org.jboss.test.web.interfaces.StatelessSession and ejbLink of StatefulEJB in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,017 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface org.jboss.test.web.interfaces.StatelessSession and ejbLink of ENCBean1 in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,017 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface org.jboss.test.cts.interfaces.CtsBmp and ejbLink of BMPBean in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,017 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface org.jboss.test.web.interfaces.StatelessSession and ejbLink of websubdir/relative.jar#SessionBean in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,018 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> from interface only org.jboss.test.web.interfaces.StatelessSession in web.xml of jbosstest-web.warnot used by any EJBs 17:29:10,018 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface org.jboss.test.web.interfaces.StatelessSession and ejbLink of UnsecuredEJB in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,018 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface org.jboss.test.web.interfaces.Entity and ejbLink of Entity in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,018 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface org.jboss.test.web.interfaces.EntityFacade and ejbLink of EntityFacade in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,018 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface org.jboss.test.web.interfaces.StatelessSession and ejbLink of NotOptimizedEJB in web.xml of jbosstest-web.war it might not be deployed yet 17:29:10,019 ERROR [BaseModelMBean] Exception invoking method addChild java.lang.RuntimeException: mapped-name is required for mdr/ProducesLink of deployment jbosstest-web.war at org.jboss.injection.ResourceHandler.loadXmlMessageDestinationRefs(ResourceHandler.java:116) at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:126) at org.jboss.web.tomcat.tc6.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:338) at org.jboss.web.tomcat.tc6.WebAppLoader.start(WebAppLoader.java:75) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4204) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;J)Ljava.lang.Object;(Unknown Source) at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5269) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;J)Ljava.lang.Object;(Unknown Source) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.web.tomcat.tc6.TomcatDeployer.performDeployInternal(TomcatDeployer.java:305) at org.jboss.web.tomcat.tc6.TomcatDeployer.performDeploy(TomcatDeployer.java:130) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:388) at org.jboss.web.WebModule.startModule(WebModule.java:83) at org.jboss.web.WebModule.startService(WebModule.java:61) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) The schema for the jboss-web.xml descriptor either needs to handle both servlet 2.4/2.5 constructs, or be conditional on the descriptor version. -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-533) Class not found when creating durable subscription from a different classloading domain

by Ovidiu Feodorov (JIRA)

Class not found when creating durable subscription from a different classloading domain --------------------------------------------------------------------------------------- Key: JBMESSAGING-533 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-533 Project: JBoss Messaging Issue Type: Bug Components: AOP Support Affects Versions: 1.0.1.CR4 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.0.1.CR5 Initialization of the AOP stack fails when creating a durable subscription from a different classloading domain. The same type of issue as the one that made necessary using ThreadContextClassLoaderChanger. See http://jira.jboss.org/jira/browse/JBMESSAGING-254 -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JASSIST-26) javassist give an exception:class not found

by dong chunguo (JIRA)

javassist give an exception:class not found ------------------------------------------- Key: JASSIST-26 URL: http://jira.jboss.com/jira/browse/JASSIST-26 Project: Javassist Issue Type: Task Environment: Weblogic 8.1; Reporter: dong chunguo Assigned To: Shigeru Chiba hi, I use javassist in EJB,but it give me an exception:class not found. The Code is : ClassPool pool = ClassPool.getDefault(); pool.insertClassPath(new ClassClassPath(ClassLoader.getSystemClassLoader().getClass())); CtClass cc = cp.get("class1"); How can I set the "insertClassPath".What should I do,it'll work? -- 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, 11 months

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 August 2006