[Management, JMX/JBoss] - Re: SchedulableMBean arguments
by dmary
thks a lot for ur response, two years after ;)
I'm trying actualy , a little bit the same way , but for moment with db provider.
I was also thinking about JbossCache as I use it in other parts.
I was wondering what is the goods and bads between JbossCache and a database .
One good point for database, is that all tasks are persistents, but when one node is broken, the order node take only the tasks which contains a date after the actual date, lets see my sql request I used in MySql:
SELECT target, method_name, method_signature, start_date, period,
repetitions, date_format FROM Schedule where start_date>NOW()
Nice trick ?!
How do you make that with JbossCache ? do u take all task in cache and look at the date parameter if it is superior ??
and how do you "clean" the cache with executed tasks ?
Damien
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159506#4159506
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159506
17 years, 10 months
[JBoss Messaging] - Re: I got some performance problem while sending a lot of me
by gary.c.chen
Afterward we setted up another test, this time we setted the parameter to ten minutes,
and we setted the FullSize parameter, PageSize parameter, DownCacheSize parameter of the queue to be tested
to 3355444, 10000, and 10000, and the messages we sended in this test were all NON_PERSISTENT messages, so this
time all the messages that sended to the queue were all stored in the memory. We also checked that the
persistent database had never been writed or readed.
In this test case we saw that messages send rate was very fast, almost equaled to it's
target send rate, but the messages received by the consumer were so a little, almost equaled to 1/10
of the messages sended to the queue, so the mesages been buffered in the queue while receiving message
were several hundred thousand or several million. And along with the send rate to be increased the buffered number
was increased, so the time to complete the receving job increased too. And the most important point was that the
receive rate was so poor, almost equaled to 1/10 of it's send rate per parallel test.
Why the messages receive rate so poor?
Does the queue must scan some of (or all) the message handles (or something like that) while a consumer receive a message
because of the message selector mechanism ?
Does the queue will copy all the message handles or synchronize all the message handles before it do this scan
, so the message receiving time of one message receiving trip will increase along with the messages buffered
in the queue increased ?
Does message receive rate is computed like this :
all messages received / message job spended time ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159505#4159505
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159505
17 years, 10 months
[JBoss Portal] - Personalization of Portlets and Themes
by tamil_jboss
Hi... I'm new to JBoss portal environment and have done few sample portlets, themes, and custom layouts. I would like to know if can do the following on JBoss Portal:
1. Customizing Portlets in a Portal page.
--- Ex: suppose I've 4 portlets in a portal page. I would like to provide an option (say 4 check boxes for 4 portlets in a window) to user to select the portlets he/she would like to choose to display on portal page. If 2 portlets are selected and saved, then Portal page should display 2 selected portlets only. When he login next time he should be able to view the 2 portlets he selected earlier.
2. Customizing themes of a portal by an user.
-- Ex: I've 3 different custom themes for my application. I can able to select a theme in the ADMIN portlet. But this theme would apply to the entire user who use the application. Instead, I would like to provide list of themes available (say in a drop down List box) with in the portal application. If a logged in user changes the theme, then the portal theme will be changed for the user only. If he log in next time, the same theme should be retained for him.
I would very much appreciate if any one help me whether it is possible to implement. If so, an example or documentation to implement the above feature would be much useful to me.
Thanks in advance.
regards,
Tamil
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159504#4159504
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159504
17 years, 10 months
[JBoss jBPM] - HTTP Status 403 - Access to the requested resource has been
by alok0007_07
I m facing a problem. I have created some users in JBPM application and i have assigned some task to each user and I want that each user can see only his own task not of others.
But when i logged in with the users i created , i got the taks of other users too...
I m facing the following error while logging in after creating new group and user...
HTTP Status 403 - Access to the requested resource has been denied
do the following for new group and user creation :
1) create a group of name 'guest'
insert into JBPM_ID_GROUP (ID_,CLASS_,NAME_,TYPE_)
values(812,'G','guest','security-role');
2) Then create a user of name 'user'
insert into JBPM_ID_USER (ID_,CLASS_,NAME_,EMAIL_,PASSWORD_)
values(123,'U','guest','guest(a)sample.domain','shipper');
3) Then insert into membership table
insert into JBPM_ID_MEMBERSHIP (ID_,CLASS_,USER_,GROUP_)
values(52,'M',812, 123);
But it gives the same error as i mentioned ... Is anything I left to do ...
Please suggest....waiting for reply..
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159500#4159500
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159500
17 years, 10 months
[Management, JMX/JBoss] - Re: SchedulableMBean arguments
by thehunt
Hi dmary. Actually I found a solution to this and implemented the project. I ll need to dig a bit as its 2 years old now, to find the specific chunks of code you are interested in. I hope i send em to you some time tomorrow.
As far as the fail over behaviour, provider and manager are instantiated but not started on all but the master node (on which their are started ofc). All tasks are placed in a shared cache (Jboss cache), and those which have already been fired are also placed inside a queue. Every node has a Message-driven EJBs pool, reading from this queue, and thus actually executing the scheduled task. When the master node is going down, another random node acts as the the master, starting its already instantiated provider and manager, re-registering all tasks which can easily be found in the shared cache. I don't provide a solution, as it was an experimental project, to the problem arising from the tasks already executing on a node, when the node fails.
For a better overview of the project check this
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98741
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159498#4159498
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159498
17 years, 10 months