[JBoss Portal] - Problem migrating applications from Jboss AS to Portal
by Sanver
Hi, We are using a jboss Portal 2.6 alpha1 on one of our machines and I'm trying to migrate an application I'm using with struts and EJB's on a Jboss AS version 4.0.5.
At first the problem seems that the portal doesn't find the struts .jar's, so I decided to move the .jars (xwork-2.0.1.jar, struts2-core-2.0.6.jar, ognl-2.6.11.jar, and freemarker-2.3.8.jar) into the /server/default/lib directory.. At first it appeared to work, because the application was succesfully deployed, but, once i tried to test how it worked, The system launched an exception saying that couldn't find an action that corresponded with the actual petition...
I hope someone can help me, it's quite frustrating to see it working correctly over a jboss AP and not into the portal...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050013#4050013
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050013
18 years, 10 months
[EJB 3.0] - SFSB passivation/activation
by mbolcina
I have SFSB on SESSION scope. SFSB looks like this:
| @Stateful
| @Scope(ScopeType.SESSION)
| @Name("dnListBean")
| public class DnListBean extends ListManagerSimple<Dn> implements DnListLocal
| {
| private Long resultCount;
| private List<Dn> resoultList;
|
| @PrePassivate
| public void prePasivate()
| {
| System.out.println("DnListBean.prePasivate()");
| System.out.println("resultCount="+resultCount);
| }
|
| @PostActivate
| public void postActive()
| {
| System.out.println("DnListBean.postActive()");
| System.out.println("resultCount="+resultCount);
| }
|
| ...
| }
|
Problem is that when SFSB gets passivate (after some time if user does nothing on page) and then back activate (after user for eg. refresh page which uses this sesssion bean) all data is lost.
Here is log from console:
| 09:14:02,021 INFO [STDOUT] DnListBean.prePasivate()
| 09:14:02,022 INFO [STDOUT] resultCount=64
| 09:14:33,674 INFO [STDOUT] DnListBean.postActive()
| 09:14:33,674 INFO [STDOUT] resultCount=null
|
Am I missing something?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050009#4050009
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050009
18 years, 10 months
[JBoss Messaging] - Re: 1.2.0.GA transparent node failover does not always work
by timfox
"bander" wrote :
| So JBM is actively changing whatever is bound as nodes go up and down etc?
Yes. But it's actually more than that. The connection factory maintains a list of nodes to failover onto and to load balance connetions across, when the cluster topology changes (a node joins or leaves) then two things happen:
1) The connection factory is rebound in JNDI with the updated list
2) An update message is sent to all the clients which already have their connection factories to make them update their internal lists.
I suspect other providers might also use a similar approach.
So if you re-use a CF from before the crash then it's likely it won't know about the different topology - at least you can't guarantee it since you'll have to start making nig assumptions based on the implementation details of the particular messaging system you're using. Safest thing to do is to throw it away and start again.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050008#4050008
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050008
18 years, 10 months