"pgib" wrote :
| I previously had a ServletContextListener subclass where contextInitialized() would kill all timers and start them. The problem is, now if I have more nodes join the cluster, the timers are killed and recreated. Is there a better way to accomplish this?
|
I haven't tried it myself - but how about using a HASingleton @Service instead of the ServletContextListener?
"pgib" wrote :
| Additionally, I thought maybe I could start the Timer in the @PostConstruct of the SLSBs themselves. However, this fails with TimerService.getTimers should not be access from this bean method: IN_EJB_CREATE
|
|
As per the table in EJB3 spec, section 4.5.2 - methods on TimerService are not allowed to be invoked in the @PostConstruct of the bean.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254193#4254193
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254193
In reading 5.4.11. HTTP(S) Client Invoker - proxy and basic authentication of the docs here:
http://www.jboss.org/file-access/default/members/jbossremoting/freezone/d...
it gives an example of how you can setup http proxy by using the metadata map passed to the invoke method.
2 questions:
1) I have had a report that using the System properties method of setting those http proxy props did not work (on 2.2.1.GA - though I'm more interested if it works/is broken on 2.2.2.SP8) - I cannot confirm this because I did not try it, but user dfilgueiras80 says it did not work , from forum post http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254159#4253994 Can someone confirm that they've actually seen that work (setting the system properties and have them take effect)?
2) I thought the invoker locator params (those in the URL query string, e.g. http://host:port/?these¶meters&here) were used by the client to configure each request sent by the client. I realize that some of the invoker locator params are meaningless to the client (they are only used on the server side) but I thought things like http.proxyPort and the like (if specified in the invoker locator used by the client) would be used for each request. Is that not true? Is there some way we can specify http proxy settings in the invoker locator URL and have the client use them as part of the request metadata (which is used by the invoke method)?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254185#4254185
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254185
Hello,
i have just installed the jbpm-4 via the ant script:
ant demo.setup
it has installed jboss 5.0.0 and eclipse, and started eclipse. When i access my localhost address, i can see the jboss menu.
But if i go to the bpm-console, like it is said by the jbpm install instructions, i get the error
HTTP Status 404 - /jbpm-console/ resource not found.
There is no comment about what could have gotten wrong in the install instructions, or any kind of troubleshooting.
please help me out! what could the problem be?
Thank you very much in advance!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254183#4254183
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254183