[JBoss JIRA] Created: (AS7-1844) MDB prevents server from shutdown
by Martin Vecera (JIRA)
MDB prevents server from shutdown
---------------------------------
Key: AS7-1844
URL: https://issues.jboss.org/browse/AS7-1844
Project: Application Server 7
Issue Type: Bug
Components: EJB, JMS
Affects Versions: 7.0.1.Final, 7.1.0.Alpha1
Reporter: Martin Vecera
Assignee: Carlo de Wolf
When there is an MDB deployed and I send a single message to the queue this MDB listens to, the server hangs on during shutdown. I believe this is the reason:
17:35:29,181 WARN [org.jboss.messaging] (MSC service thread 1-3) failed to destroy jms queue: TasksQueue: HornetQException[errorCode=104 message=Cannot delete queue jms.queue.TasksQueue on binding jms.queue.TasksQueue - it has consumers = org.hornetq.core.postoffice.impl.LocalQueueBinding]
at org.hornetq.core.server.impl.HornetQServerImpl.destroyQueue(HornetQServerImpl.java:1083)
at org.hornetq.jms.server.impl.JMSServerManagerImpl.destroyQueue(JMSServerManagerImpl.java:710)
at org.jboss.as.messaging.jms.JMSQueueService.stop(JMSQueueService.java:68)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1869)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]
The MDB throws and EJBException in the onMessage() method and the message ends in DLQ. I'm not sure if this is related to the problem. If needed I could create a reproducer that I can provide, but it is not ready at the moment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] (AS7-2781) After entityManager.find(), no session or session was closed
by Lars Bohl (Created) (JIRA)
After entityManager.find(), no session or session was closed
------------------------------------------------------------
Key: AS7-2781
URL: https://issues.jboss.org/browse/AS7-2781
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.0.2.Final
Environment: ubuntu 11.04
Reporter: Lars Bohl
Assignee: Scott Marlow
Attachments: lord.tgz
After entityManager.find(), the session appears to be closed (can't access persistent collection). A functionally equivalent query for id works fine.
see comments in MemberListProducer#retrieveAllMembersOrderedByName (Attachment!)
Stacktrace:
17:57:18,210 INFO [org.jboss.web] (MSC service thread 1-7) registering web context: /lord
17:57:18,263 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "lord.war"
17:57:19,858 INFO [my.lord.data.MemberListProducer] (http-0.0.0.0-0.0.0.0-8080-1) m.name=John Smith
17:57:19,859 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-0.0.0.0-0.0.0.0-8080-1) Error Rendering View[/index.xhtml]: org.jboss.weld.exceptions.WeldException: WELD-000049 Unable to invoke [method] @PostConstruct public my.lord.data.MemberListProducer.retrieveAllMembersOrderedByName() on my.lord.data.MemberListProducer@2d275595
at org.jboss.weld.bean.AbstractClassBean.defaultPostConstruct(AbstractClassBean.java:595) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.postConstruct(ManagedBean.java:200) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:340) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:122) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:693) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.bean.AbstractReceiverBean.getReceiver(AbstractReceiverBean.java:84) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.bean.ProducerMethod$1.produce(ProducerMethod.java:146) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:361) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:693) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.el.AbstractWeldELResolver.lookup(AbstractWeldELResolver.java:152) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.el.AbstractWeldELResolver.getValue(AbstractWeldELResolver.java:112) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.as.weld.webtier.jsf.ForwardingELResolver.getValue(ForwardingELResolver.java:46) [jboss-as-weld-7.0.2.Final.jar:7.0.2.Final]
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:175) [jboss-el-api_2.2_spec-1.0.0.Final.jar:1.0.0.Final]
at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:67) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.el.parser.AstEmpty.getValue(AstEmpty.java:45) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:187) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:55) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:413) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1750) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1759) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1759) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:401) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:131) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final]
at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final]
at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:49) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26]
at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.introspector.jlr.WeldMethodImpl.invoke(WeldMethodImpl.java:193) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
at org.jboss.weld.bean.AbstractClassBean.defaultPostConstruct(AbstractClassBean.java:591) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
... 50 more
Caused by: org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: my.lord.model.Member.additionalInfos, no session or session was closed
at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:393) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:385) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.collection.internal.AbstractPersistentCollection.readSize(AbstractPersistentCollection.java:125) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.collection.internal.PersistentBag.size(PersistentBag.java:243) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at my.lord.data.MemberListProducer.retrieveAllMembersOrderedByName(MemberListProducer.java:63) [classes:]
... 60 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] (JGRP-1394) Reduce memory used by data structures
by Bela Ban (Created) (JIRA)
Reduce memory used by data structures
-------------------------------------
Key: JGRP-1394
URL: https://issues.jboss.org/browse/JGRP-1394
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.2
Some protocols maintain data structures, usually one per cluster member. For example, NAKACK has a hashmap of members and their associated NakreceiverWindows. Each NRW has a RetransmitTable and a Retransmitter.
Another example is STABLE.
Look at those data structures and try to reduce their memory footprint. This may not be important for small clusters, but becomes important in large clusters. E.g if we have 1000 cluster nodes, then every data structure's memory footprint is multiplied by 1000 !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] (AS7-2899) entities returned from Queries that are created from transaction scoped entity manager used without jta, should be detached.
by Scott Marlow (Created) (JIRA)
entities returned from Queries that are created from transaction scoped entity manager used without jta, should be detached.
----------------------------------------------------------------------------------------------------------------------------
Key: AS7-2899
URL: https://issues.jboss.org/browse/AS7-2899
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: Scott Marlow
Assignee: Scott Marlow
JPA 2.0 section 3.8.6 Query Execution:
"
Query and TypedQuery methods other than the executeUpdate method are not required to be invoked within a transaction context, unless a lock mode other than LockModeType.NONE has been specified for the query. In particular, the getResultList and getSingleResult methods are not required to be invoked within a transaction context unless such a lock mode has been specified for the query.[47] If an entity manager with transaction-scoped persistence context is in use, the resulting entities will be detached; if an entity manager with an extended persistence context is used, they will be managed. See Chapter 7 for further discussion of entity manager use outside a transaction and persistence context types.
"
AS7-2781 has a test case that demonstrates that this doesn't happen (the Query is currently commented out).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] (JBRULES-3301) Planner's "presumedScore is corrupted because it is not the realScore" exception should analyse and clearly list what could be wrong.
by Geoffrey De Smet (Created) (JIRA)
Planner's "presumedScore is corrupted because it is not the realScore" exception should analyse and clearly list what could be wrong.
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-3301
URL: https://issues.jboss.org/browse/JBRULES-3301
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-planner
Affects Versions: 5.3.0.Final
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Critical
Fix For: 5.4.0.Beta1
The exception "presumedScore is corrupted because it is not the realScore", can occur for multiple reasons:
- The Move.createUndoMove() method is incorrectly implemented. If a Move A moves from X to Z, then the undo Move should move A from Z to X.
- The score constraints do insertLogical's of something else than a class that extends ConstraintOccurrence. Although it is technically not 100% required to do this, there are specific technical requirements on those logically inserted classes by Drools Expert to keep the score uncorrupted. So it's far easier just to use IntConstraintOccurrence or to extend ConstraintOccurrence correctly.
- The score constraints, which do insertLogical's of ConstraintOccurrence, forget to add a cause too little or too much. The exception message should identify which of the ConstraintOccurrences are corrupted and only list those.
- Drools Expert 5.1 or lower is used (these possibly have bugs in the statefull working memory. From drools 5.2 this is proven not the be the case).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBAS-9095) Management only mode
by Brian Stansberry (JIRA)
Management only mode
--------------------
Key: JBAS-9095
URL: https://issues.jboss.org/browse/JBAS-9095
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.0.0.Beta4
There is a requirement that "Instances will still be configurable even if they are not currently running. Changes will become active when the instance is next started." That could be interpreted as meaning the xml config files are human editable (which they are), but it would be nice to support something richer; i.e. starting standalone server or ProcessController+HostController processes that install no runtime services beyond what's needed to accept, process and persist management changes.
This is a container task; there will be subtasks for standalone mode and domain mode.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] (AS7-1485) Packaging Xerces in war causes JSF ClassCastException on SAXParserFactory
by Philippe Guinot (Commented) (JIRA)
[ https://issues.jboss.org/browse/AS7-1485?page=com.atlassian.jira.plugin.s... ]
Philippe Guinot commented on AS7-1485:
--------------------------------------
Hello,
I'm actually having troubles because of this JSF patch. Using jsf-impl-1.2_15-jbossorg-1, I can't load any of my facelet: I just get a 404 error !
If I replace in the JBoss module the JAR by jsf-impl-1.2_15.jar, then everything is fine.
I've put some breakpoints in the affected classes, but I can't see anything wrong: no exception is thrown. Here are the details about the class loaders:
* The previous TCCL: ModuleClassLoader for Module "deployment.My_EAR.ear.My_WAR.war:main" from Service Module Loader
* The new class loader ServletContextListener.class.getClassLoader() = ModuleClassLoader for Module "javax.servlet.api:main" from local module loader @ee51b2c
If I comment the class loader settings, then it my facelets work again.
And I do not use Xerces other than the xercesImpl-2.9.1-jbossas-1 version in the org.apache.xerces module.
Thank you for your help.
> Packaging Xerces in war causes JSF ClassCastException on SAXParserFactory
> -------------------------------------------------------------------------
>
> Key: AS7-1485
> URL: https://issues.jboss.org/browse/AS7-1485
> Project: Application Server 7
> Issue Type: Bug
> Components: JSF
> Affects Versions: 7.0.0.Final, 7.0.2.Final
> Reporter: Brad Maxwell
> Assignee: Brad Maxwell
> Fix For: Open To Community
>
>
> Packaging Xerces in war causes JSF ClassCastException on SAXParserFactory
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost]. (main) Exception sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
> java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl cannot be cast to javax.xml.parsers.SAXParserFactory
> at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:128)
> at com.sun.faces.config.ConfigureListener$WebXmlProcessor.getConfiguredFactory(ConfigureListener.java:702)
> at com.sun.faces.config.ConfigureListener$WebXmlProcessor.scanForFacesServlet(ConfigureListener.java:674)
> at com.sun.faces.config.ConfigureListener$WebXmlProcessor.<init>(ConfigureListener.java:648)
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:156)
> at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureListener.java:60)
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4389)
> at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:321)
> at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:145)
> at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
> at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months