[JBoss JIRA] Created: (AS7-1457) Cleaner Security Provider Registration
by Darran Lofthouse (JIRA)
Cleaner Security Provider Registration
--------------------------------------
Key: AS7-1457
URL: https://issues.jboss.org/browse/AS7-1457
Project: Application Server 7
Issue Type: Task
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Beta1
Currently the SASL security provider registration occurs each place that it is identified as required.
Everything however is modules based so we should see if there is a cleaner way this can happen - even if it was as simple as having a class executed automatically as the module is loaded.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (AS7-2906) Datasource does not support long username
by hantsy bai (Created) (JIRA)
Datasource does not support long username
-----------------------------------------
Key: AS7-2906
URL: https://issues.jboss.org/browse/AS7-2906
Project: Application Server 7
Issue Type: Bug
Environment: JBoss 7.0.2.Final JBoss Maven Plugin 7.0.2.Final
Reporter: hantsy bai
I tried to create a datasource for my demo(seam3-sandbox on github) via jboss maven plugin.
When I use "seam3sandboxuser" and "seam3sandboxpass" as user/password pair, the datasource was created, but I can not connect to the mysql database. Connection exception will be thrown at Jboss starts up.
After I changed user/password to "seam3user"/"seam3pass", it was connected successfully.
PS: I created the related user/pass in mysql before I execute mvn command.
--
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
12 years, 5 months
[JBoss JIRA] (AS7-2081) read-resource with recurse and include-runtime is broken
by David Bosschaert (Created) (JIRA)
read-resource with recurse and include-runtime is broken
--------------------------------------------------------
Key: AS7-2081
URL: https://issues.jboss.org/browse/AS7-2081
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.Beta1
Reporter: David Bosschaert
When I add recursive=true to :read-resource the runtime attributes disappear.
E.g.
{code}subsystem=osgi] :read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => {
"activation" => "eager",
"startlevel" => 1,
"bundle" => {
"19" => undefined,
"17" => undefined,
"18" => undefined,
{code}
The above works, but adding recursive=true produces:
{code}subsystem=osgi] :read-resource(include-runtime=true,rrecursive=true)
{
"outcome" => "success",
"result" => {
"activation" => "eager",
"bundle" => {
"20" => {},
"21" => {},
{code}
The startlevel attribute is gone and the bundle resources are empty. Note that when I run :read-children-resources it does return the correct information
{code}subsystem=osgi] :read-children-resources(child-type=bundle,include-runtime=true)
{
"outcome" => "success",
"result" => {
"0" => {
"id" => 0L,
"startlevel" => 0,
"state" => "ACTIVE",
"symbolic-name" => "system.bundle",
"version" => "0.0.0"
},
"1" => {
"id" => 1L,
"startlevel" => 1,
"state" => "INSTALLED",
"symbolic-name" => "javaee.api",
"version" => "0.0.0"
},
{code}
--
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
12 years, 5 months
[JBoss JIRA] (AS7-2136) Can't wire up MDBs when multiple RARs are deployed
by Carlo de Wolf (Created) (JIRA)
Can't wire up MDBs when multiple RARs are deployed
--------------------------------------------------
Key: AS7-2136
URL: https://issues.jboss.org/browse/AS7-2136
Project: Application Server 7
Issue Type: Bug
Components: JCA
Reporter: Carlo de Wolf
Assignee: Jesper Pedersen
Fix For: 7.1.0.CR1
Whenever multiple RARs are deployed backed by the same implementation class an MDB is unable to wire up to the correct RAR.
{code:java}
@MessageDriven(activationConfig = {
@ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/test")
})
@ResourceAdapter("external-hornetq-ra.rar")
public class ReplyingMDB implements MessageListener
{code}
{noformat}
10:00:01,502 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed to start service jboss.deployment.unit."ejb3mdb.jar".component.ReplyingMDB.CREATE: org.jboss.msc.service.StartException in service jboss.deployment.unit."ejb3mdb.jar".component.ReplyingMDB.CREATE: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: java.lang.IllegalStateException: found more than one RA registered external-hornetq-ra
at org.jboss.as.ejb3.component.EJBUtilities.createActivationSpecs(EJBUtilities.java:126)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenComponentCreateService.java:78)
at org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:78)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
... 3 more
{noformat}
--
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
12 years, 5 months
[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
12 years, 5 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
12 years, 5 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
12 years, 5 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
12 years, 5 months