October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2172) Resurrect the mixed domain testing and fix any problems

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2172?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2172: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> made a comment on [bug 1015243|https://bugzilla.redhat.com/show_bug.cgi?id=1015243] This is necessary to be able to test interoperatbility of a EAP 6.2 DC running EAP 6.0.x and 6.1.x slaves. > Resurrect the mixed domain testing and fix any problems > ------------------------------------------------------- > > Key: WFLY-2172 > URL: https://issues.jboss.org/browse/WFLY-2172 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 8.0.0.CR1 > > > THis has not been run for quite some time, and needs to be included in the general testing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] Heiko Braun reassigned WFLY-2183: --------------------------------- Assignee: James Perkins (was: Heiko Braun) > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Logging > Reporter: Heiko Braun > Assignee: James Perkins > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2057) org.jboss.as.server.deployment.RegisteredDeploymentUnitProcessor has unstable compareTo()

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2057?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2057: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1013470|https://bugzilla.redhat.com/show_bug.cgi?id=1013470] from NEW to POST > org.jboss.as.server.deployment.RegisteredDeploymentUnitProcessor has unstable compareTo() > ----------------------------------------------------------------------------------------- > > Key: WFLY-2057 > URL: https://issues.jboss.org/browse/WFLY-2057 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: David Lloyd > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 8.0.0.Beta1 > > > As the description says, org.jboss.as.server.deployment.RegisteredDeploymentUnitProcessor's compareTo is wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2118) PersistenceException breaks default error page

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/WFLY-2118?page=com.atlassian.jira.plugin.... ] Juergen Zimmermann commented on WFLY-2118: ------------------------------------------ Stuart, are you saying that I should re-open this issue, *after* the beta. > PersistenceException breaks default error page > ---------------------------------------------- > > Key: WFLY-2118 > URL: https://issues.jboss.org/browse/WFLY-2118 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Juergen Zimmermann > Assignee: Stuart Douglas > Attachments: mojarra-2.1.zip, testcase-WFLY-2118.zip > > > I'm using the latest WildFly snapshot with Undertow 1.0.0.Beta13. When I get a PersistenceException caused by Hibernate due to an invalid entity (according to Bean Validation), then the webbrowser doesn't get the default error page. The stacktrace is shown below. I'll attach a testcase. > {code} > [com.arjuna.ats.arjuna] ARJUNA012125: TwoPhaseCoordinator.beforeCompletion - failed for SynchronizationImple< 0:ffffc0a8b801:4240ead4:523ac52c:15, org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization@20cf7473 >: javax.persistence.PersistenceException: error during managed flush > at org.hibernate.jpa.spi.AbstractEntityManagerImpl$CallbackExceptionMapperImpl.mapManagedFlushFailure(AbstractEntityManagerImpl.java:1785) [hibernate-entitymanager-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.engine.transaction.synchronization.internal.SynchronizationCallbackCoordinatorImpl.beforeCompletion(SynchronizationCallbackCoordinatorImpl.java:118) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization.beforeCompletion(RegisteredSynchronization.java:53) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76) [narayana-jts-jacorb-5.0.0.M4.jar:5.0.0.M4 (revision: ${buildNumber})] > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:273) [narayana-jts-jacorb-5.0.0.M4.jar:5.0.0.M4 (revision: ${buildNumber})] > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:93) [narayana-jts-jacorb-5.0.0.M4.jar:5.0.0.M4 (revision: ${buildNumber})] > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) [narayana-jts-jacorb-5.0.0.M4.jar:5.0.0.M4 (revision: ${buildNumber})] > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1170) [narayana-jts-jacorb-5.0.0.M4.jar:5.0.0.M4 (revision: ${buildNumber})] > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) [narayana-jts-jacorb-5.0.0.M4.jar:5.0.0.M4 (revision: ${buildNumber})] > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.endTransaction(TransactionalInterceptorBase.java:131) [narayana-jts-jacorb-5.0.0.M4.jar:5.0.0.M4 (revision: ${buildNumber})] > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInOurTx(TransactionalInterceptorBase.java:77) [narayana-jts-jacorb-5.0.0.M4.jar:5.0.0.M4 (revision: ${buildNumber})] > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired.intercept(TransactionalInterceptorRequired.java:52) [narayana-jts-jacorb-5.0.0.M4.jar:5.0.0.M4 (revision: ${buildNumber})] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_40] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_40] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_40] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_40] > at org.jboss.weld.interceptor.proxy.SimpleMethodInvocation.invoke(SimpleMethodInvocation.java:30) [weld-core-impl-2.1.0.Beta1.jar:2013-09-05 17:01] > at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:90) [weld-core-impl-2.1.0.Beta1.jar:2013-09-05 17:01] > at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:75) [weld-core-impl-2.1.0.Beta1.jar:2013-09-05 17:01] > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:48) [weld-core-impl-2.1.0.Beta1.jar:2013-09-05 17:01] > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:41) [weld-core-impl-2.1.0.Beta1.jar:2013-09-05 17:01] > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:53) [weld-core-impl-2.1.0.Beta1.jar:2013-09-05 17:01] > at testcase.web.CustomerModel$Proxy$_$$_WeldSubclass.create(Unknown Source) [classes:] > at testcase.web.CustomerModel$Proxy$_$$_WeldClientProxy.create(Unknown Source) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_40] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_40] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_40] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_40] > at javax.el.ELUtil.invokeMethod(ELUtil.java:326) [javax.el-3.0-b07.jar:3.0-b07] > at javax.el.BeanELResolver.invoke(BeanELResolver.java:536) [javax.el-3.0-b07.jar:3.0-b07] > at javax.el.CompositeELResolver.invoke(CompositeELResolver.java:256) [javax.el-3.0-b07.jar:3.0-b07] > at com.sun.el.parser.AstValue.invoke(AstValue.java:269) [javax.el-3.0-b07.jar:3.0-b07] > at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:304) [javax.el-3.0-b07.jar:3.0-b07] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:40) [weld-core-impl-2.1.0.Beta1.jar:2013-09-05 17:01] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50) [weld-core-impl-2.1.0.Beta1.jar:2013-09-05 17:01] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:40) [weld-core-impl-2.1.0.Beta1.jar:2013-09-05 17:01] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50) [weld-core-impl-2.1.0.Beta1.jar:2013-09-05 17:01] > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.26.jar:2.1.26] > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:87) [jsf-api-2.1.26.jar:2.1] > at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:101) [jsf-impl-2.1.26.jar:2.1.26] > at javax.faces.component.UICommand.broadcast(UICommand.java:315) [jsf-api-2.1.26.jar:2.1] > at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:786) [jsf-api-2.1.26.jar:2.1] > at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1251) [jsf-api-2.1.26.jar:2.1] > at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) [jsf-impl-2.1.26.jar:2.1.26] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.26.jar:2.1.26] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.26.jar:2.1.26] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jsf-api-2.1.26.jar:2.1] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:59) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:209) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:196) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:69) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:130) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:614) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40] > Caused by: javax.validation.ConstraintViolationException: Validation failed for classes [testcase.domain.Customer] during persist time for groups [javax.validation.groups.Default, ] > List of constraint violations:[ > ConstraintViolationImpl{interpolatedMessage='Min length = 2, max length = 32', propertyPath=name, rootBeanClass=class testcase.domain.Customer, messageTemplate='Min length = {min}, max length = {max}'} > ConstraintViolationImpl{interpolatedMessage='Zip code is 5 digits', propertyPath=zip, rootBeanClass=class testcase.domain.Customer, messageTemplate='Zip code is 5 digits'} > ConstraintViolationImpl{interpolatedMessage='A name must have one capital letter, followed by small letters', propertyPath=name, rootBeanClass=class testcase.domain.Customer, messageTemplate='A name must have one capital letter, followed by small letters'} > ] > at org.hibernate.cfg.beanvalidation.BeanValidationEventListener.validate(BeanValidationEventListener.java:159) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.cfg.beanvalidation.BeanValidationEventListener.onPreInsert(BeanValidationEventListener.java:94) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.action.internal.EntityInsertAction.preInsert(EntityInsertAction.java:196) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.action.internal.EntityInsertAction.execute(EntityInsertAction.java:96) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.engine.spi.ActionQueue.execute(ActionQueue.java:377) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:369) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:286) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:340) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:52) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1235) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.internal.SessionImpl.managedFlush(SessionImpl.java:405) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > at org.hibernate.engine.transaction.synchronization.internal.SynchronizationCallbackCoordinatorImpl.beforeCompletion(SynchronizationCallbackCoordinatorImpl.java:113) [hibernate-core-4.3.0.Beta4.jar:4.3.0.Beta4] > ... 68 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1714) Headers: data in some headers might be too large in big clusters

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1714?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-1714 at 10/4/13 4:34 AM: --------------------------------------------------------- * {{PingHeader}}: DONE * {{FD_SOCK.FdHeader}}: DONE * {{STABLE.StableHeader}}: DONE was (Author: belaban): * {{PingHeader}}: DONE * {{FD_SOCK.FdHeader}}: DONE > Headers: data in some headers might be too large in big clusters > ---------------------------------------------------------------- > > Key: JGRP-1714 > URL: https://issues.jboss.org/browse/JGRP-1714 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.4 > > > Similar to JGRP-1710 and JGRP-1713, investigate headers which might become too big, and move their contents into the message body. Check all headers which contain > * a view > * a digest > * a list of members > Candidates: > * {{PingHeader}}. > Probable solution: move {{PingHeader.PingData}} from the header to the message body -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2128) Support one-port connection for JMS

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-2128?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-2128: ------------------------------ Priority: Critical (was: Major) > Support one-port connection for JMS > ----------------------------------- > > Key: WFLY-2128 > URL: https://issues.jboss.org/browse/WFLY-2128 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 8.0.0.Alpha4 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Critical > Fix For: 8.0.0.Beta1 > > > WildFly 8 needs to support one-port where all the remote connections goes through HTTP with Upgrade header. > A JMS client will be able to connect to WildFly's HTTP port to access its JMS resources instead of connecting to the TCP socket on HornetQ remote port (5445). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-263) JASPI Support for Web Services

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-263?page=com.atlassian.jira.plugin.s... ] Alessio Soldano updated WFLY-263: --------------------------------- Assignee: Jim Ma (was: Alessio Soldano) > JASPI Support for Web Services > ------------------------------ > > Key: WFLY-263 > URL: https://issues.jboss.org/browse/WFLY-263 > Project: WildFly > Issue Type: Feature Request > Components: Security, Web Services > Reporter: Anil Saldhana > Assignee: Jim Ma > Fix For: 8.0.0.Beta1 > > > Take care of the JASPI requirements for SOAP layer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-284) Timer nullpointer due to race condition during update

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-284?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-284: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> made a comment on [bug 1015323|https://bugzilla.redhat.com/show_bug.cgi?id=1015323] Fixed by Mark with this commit: https://github.com/droolsjbpm/drools/commit/859b1a5915fe89ba37483afc84c6d... > Timer nullpointer due to race condition during update > ----------------------------------------------------- > > Key: DROOLS-284 > URL: https://issues.jboss.org/browse/DROOLS-284 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.0.0.CR5 > > > If the timer fires at the same time as an update it results in the child being propagated twice. We need to synchronize to ensure that this does not happen. The update should cancel the timer, so it doens't try and schedule a propagation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-284) Timer nullpointer due to race condition during update

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-284?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-284: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1015323|https://bugzilla.redhat.com/show_bug.cgi?id=1015323] from NEW to MODIFIED > Timer nullpointer due to race condition during update > ----------------------------------------------------- > > Key: DROOLS-284 > URL: https://issues.jboss.org/browse/DROOLS-284 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.0.0.CR5 > > > If the timer fires at the same time as an update it results in the child being propagated twice. We need to synchronize to ensure that this does not happen. The update should cancel the timer, so it doens't try and schedule a propagation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2164) Read only App, Module and Comp Naming Contexts

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2164?page=com.atlassian.jira.plugin.... ] Eduardo Martins updated WFLY-2164: ---------------------------------- Description: Java EE 7 (and its TCK) mandates that java:app, java:module and java:comp contexts to be read only. was:Wildfly allows EE components to modify their naming environment (and every other naming context too), and such behaviour may be undesirable, thus the EE subsystem configuration should include an attribute to globally turn on or off such functionality. > Read only App, Module and Comp Naming Contexts > ---------------------------------------------- > > Key: WFLY-2164 > URL: https://issues.jboss.org/browse/WFLY-2164 > Project: WildFly > Issue Type: Feature Request > Components: EE, Naming > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > Java EE 7 (and its TCK) mandates that java:app, java:module and java:comp contexts to be read only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 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 October 2013