[JBoss JIRA] (JGRP-1553) TimeScheduler3
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1553?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1553:
--------------------------------
The above code looks similar to what ScheduledThreadPoolExecutor does (with DelayQueue/PriorityQueue). Also, after the simplications of NAKACK{2} and UNICAST{2}, we won't have many tasks in a timer.
Therefore I'll do the following:
#1 Either fix the above problems in TimeScheduler2 directly, or write a new TimeScheduler3 to do that
#2 default back to timer_type="old". This uses the DefaultTimeScheduler, which intenally uses ScheduledThreadPoolExecutor. This is probably good enough, as we won't have many tasks in the timer.
> TimeScheduler3
> --------------
>
> Key: JGRP-1553
> URL: https://issues.jboss.org/browse/JGRP-1553
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.3
>
>
> The current TimeScheduler2 class has a few deficiencies:
> - taskReady() should only set next-execution-time if its argument is less than next-execution-time
> - no_tasks: when setting this CAS, the result is only checked in 1 location, but not the other
> - Potential loss of task: when calling schedule() on an existing Entry (same execution time), and - before adding the task to Entry - Entry is removed by _run() as it was executed, then the newly added task will never get to run !
> - Simplification: instead of headMap(), just use firstEntry(), removeFirstEntry(). See pseudo code below.
> As a workaround, timer_type="old" will switch back to the previous default timer. The reason for TimeScheduler3 (versus changing TimeScheduler2) is that we can simply switch to the new impl by setting (a new) timer_type="new2". Should this have a bug, we can simply switch back to "new" or "old" (or "wheel".
> Over time, TimeScheduler2 will get removed.
> Pseudo code:
> * loop while has tasks
> ** get the first task
> ** if its time is less than the current time: execute it and remove it
> ** else block (on the next task or 10s) until an element is added
--
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
13 years, 6 months
[JBoss JIRA] (AS7-2667) Applications cannot use Hibernate hibernate.session_factory_name
by avi said (JIRA)
[ https://issues.jboss.org/browse/AS7-2667?page=com.atlassian.jira.plugin.s... ]
avi said commented on AS7-2667:
-------------------------------
I would like to bind my remote object from external JVM to Jboss AS 7 and use its JNDI as central Naming Directory.
How is that possible to create/get org.jboss.msc.service.StartContext from a standalone application?
> Applications cannot use Hibernate hibernate.session_factory_name
> -----------------------------------------------------------------
>
> Key: AS7-2667
> URL: https://issues.jboss.org/browse/AS7-2667
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Naming
> Affects Versions: 7.0.0.Beta2, 7.0.1.Final, 7.1.0.Alpha1
> Reporter: Scott Marlow
> Assignee: Scott Marlow
>
> Applications that expect to bind objects to JNDI, are currently broken. Related jira AS7-421 was marked as fixed, but its not clear what that means (with regard to applications being able to bind to jndi).
--
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
13 years, 6 months
[JBoss JIRA] (AS7-1577) Module creation utility
by Eduardo Silva (JIRA)
[ https://issues.jboss.org/browse/AS7-1577?page=com.atlassian.jira.plugin.s... ]
Eduardo Silva commented on AS7-1577:
------------------------------------
There is a lot of companies that still using old JBoss versions just to avoid this cumbersome task. Which project it will be a good place to start with those tasks?
> Module creation utility
> -----------------------
>
> Key: AS7-1577
> URL: https://issues.jboss.org/browse/AS7-1577
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Class Loading
> Affects Versions: 7.0.0.Beta1
> Reporter: Nicklas Karlsson
> Fix For: Open To Community
>
>
> It would be nice to have a utility for creating modules and/or locating dependencies of a 3rd party jar. It could work something like
> 1. Given n JAR files and a name a module structure and module.xml would be created
> 2. Tattletale would be employed to detect the complete structure of dependencies
> 3. The Modules API would be used to walk the module repository to see if the missing dependencies are already modules and add the correct dependency to the module.xml
> 4. (optional) provide a way to input for maven coordinates of missing dependencies so they too can be converted to modules or included in the module.
> As people are migrating from ASx -> AS7 there will probably be a lot of cursing over CNFEs of own and 3rd party libs
--
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
13 years, 6 months
[JBoss JIRA] (AS7-5738) JNDI View doesn't work in domain mode
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-5738?page=com.atlassian.jira.plugin.s... ]
Heiko Braun resolved AS7-5738.
------------------------------
Resolution: Done
closing. it's not a console issue.
> JNDI View doesn't work in domain mode
> --------------------------------------
>
> Key: AS7-5738
> URL: https://issues.jboss.org/browse/AS7-5738
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Reporter: Heiko Braun
> Assignee: Heiko Braun
> Fix For: 7.2.0.CR1
>
>
> Yields an exception on the server side:
> {noformat}
> [Server:server-one] Caused by: java.lang.ClassNotFoundException: javax.management.j2ee.ManagementHome from [Module "org.jboss.as.naming:main" from local module loader @e49d67c (roots: /Users/hbraun/dev/prj/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules)]
> [Server:server-one] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA]
> {noformat}
--
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
13 years, 6 months