[JBoss JIRA] Created: (JBAS-8901) dependency injection fails when deploying large graphs of inter-dependent EJBs
by Radai Rosenblatt (JIRA)
dependency injection fails when deploying large graphs of inter-dependent EJBs
------------------------------------------------------------------------------
Key: JBAS-8901
URL: https://issues.jboss.org/browse/JBAS-8901
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: 6.0.0.Final
Environment: windows xp 32bit, jdk 6u23
Reporter: Radai Rosenblatt
Assignee: Carlo de Wolf
i've attached a maven project that generates a random ear containing 100 EJBs that are inter-denendent. the graph generated is directed (no loops). graph roots are @Singleton @Startup beans that have a @PostConstruct method. in this method, they access all of their injected @EJBs, which then do the same recursively. the ears generated deploy fine for small cases (5 beans), but when trying to deploy a 100-bean ear several injections fail.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBAS-6657) managementView.load() fails to merge ServerInfo, ThreadPool, GlobalRequestProcessor, and Host ManagedObjects
by Ian Springer (JIRA)
managementView.load() fails to merge ServerInfo, ThreadPool, GlobalRequestProcessor, and Host ManagedObjects
------------------------------------------------------------------------------------------------------------
Key: JBAS-6657
URL: https://jira.jboss.org/jira/browse/JBAS-6657
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Fix For: JBossAS-5.1.0.CR1
These are all MOs that are needed by the Embedded Console.
Here's the log output:
10:47:18,464 DEBUG [ProfileServiceFactory] About to load profile via Management View...
10:47:23,964 WARN [AbstractManagedObjectPopulator] Cannot create String name from non-Simple property: ManagedProperty{JNDIName,JNDIName,metaType=SimpleMetaType:java.lang.String}, value=null
10:47:23,980 WARN [AbstractManagedObjectPopulator] Cannot create String name from non-Simple property: ManagedProperty{JNDIName,JNDIName,metaType=SimpleMetaType:java.lang.String}, value=null
10:47:57,870 WARN [ManagementViewImpl] Failed to merged the following runtime ManagedObjects: {jboss.system:type=ServerInfo/jboss.system:type=ServerInfo=ManagedObject{jboss.system:type=ServerInfo}, jboss.web:name=http-127.0.0.1-8080,type=ThreadPool/=ManagedObject{jboss.web:name=http-127.0.0.1-8080,type=ThreadPool}, jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestProcessor/=ManagedObject{jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestProcessor}, jboss.web:host=127.0.0.1,type=Host/=ManagedObject{jboss.web:host=127.0.0.1,type=Host}}
10:48:00,917 DEBUG [ProfileServiceFactory] Loaded profile via Management View in 42453 milliseconds.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBAS-8140) Standard JTS-based configuration
by Brian Stansberry (JIRA)
Standard JTS-based configuration
--------------------------------
Key: JBAS-8140
URL: https://jira.jboss.org/browse/JBAS-8140
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: Unscheduled
This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010:
>> Would like to have a configuration with JBossTM JTS implementation
>> already installed and optimized for servers that need distributed
>> transactions. Proper transaction management is an advanced topic for
>> JBoss admins and having Redhat's expertise already configured on a
>> server is very reassuring.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBRULES-3093) Drools Fusion broker example throws stacktraces in drools 5.2.0
by Geoffrey De Smet (JIRA)
Drools Fusion broker example throws stacktraces in drools 5.2.0
---------------------------------------------------------------
Key: JBRULES-3093
URL: https://issues.jboss.org/browse/JBRULES-3093
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Geoffrey De Smet
Assignee: Kris Verlaenen
Fix For: 5.2.0
{code}
=============================================================
Unexpected exception caught: Unexpected exception executing action org.jbpm.process.instance.event.DefaultSignalManager$SignalAction@1eeba19
org.drools.RuntimeDroolsException: Unexpected exception executing action org.jbpm.process.instance.event.DefaultSignalManager$SignalAction@1eeba19
at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:996)
at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1059)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:733)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:699)
at org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:218)
at org.drools.examples.broker.Broker.receive(Broker.java:68)
at org.drools.examples.broker.events.EventFeeder$FeedJob.execute(EventFeeder.java:85)
at org.drools.time.impl.JDKTimerService$JDKCallableJob.call(JDKTimerService.java:146)
at org.drools.time.impl.JDKTimerService$JDKCallableJob.call(JDKTimerService.java:124)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IllegalArgumentException: XOR split could not find at least one valid outgoing connection for split Take Action
at org.jbpm.workflow.instance.node.SplitInstance.internalTrigger(SplitInstance.java:98)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:122)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerConnection(NodeInstanceImpl.java:185)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:150)
at org.jbpm.workflow.instance.impl.ExtendedNodeInstanceImpl.triggerCompleted(ExtendedNodeInstanceImpl.java:47)
at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:162)
at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:143)
at org.jbpm.workflow.instance.node.RuleSetNodeInstance.signalEvent(RuleSetNodeInstance.java:73)
at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.signalEvent(WorkflowProcessInstanceImpl.java:339)
at org.jbpm.process.instance.event.DefaultSignalManager.internalSignalEvent(DefaultSignalManager.java:80)
at org.jbpm.process.instance.event.DefaultSignalManager$SignalAction.execute(DefaultSignalManager.java:175)
at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:994)
... 15 more
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 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, 5 months
[JBoss JIRA] Created: (JBAS-9097) Management only standalone mode
by Brian Stansberry (JIRA)
Management only standalone mode
-------------------------------
Key: JBAS-9097
URL: https://issues.jboss.org/browse/JBAS-9097
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.0.0.Beta4
See parent task for core concept.
In standalone mode, the issue is distinguishing operations that provide management services from those that don't. If the server is started in "management only" mode a RuntimeContext should only be provided to handlers for those operations.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months