[Clustering/JBoss] - Problem with datasources, they start, but my apps cannot use
by sebastianlacuesta
Hi, I'm having a very strange behavior with a cluster. The main problem is that I have diferent datasources, that they appear to start correctly, when I try to use them I get a NullPointerException. There are some other strange things that occur:
The first node starts without problem, no matter which one of the node is. All the other nodes start with the following error at the end:
03:41:47,953 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.mq:service=DestinationManager
State: CONFIGURED
I Depend On:
jboss.mq:service=MessageCache
jboss.mq:service=PersistenceManager
jboss.mq:service=StateManager
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.mq:service=StateManager
State: NOTYETINSTALLED
Depends On Me:
jboss.mq:service=DestinationManager
03:41:48,076 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-192.168.2.2-8080
03:41:48,231 INFO [ChannelSocket] JK: ajp13 listening on /192.168.2.2:8009
03:41:48,242 INFO [JkMain] Jk running ID=0 time=0/29 config=null
03:41:48,267 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 27s:894ms
I'm using jboss 4.0.4.GA, I became mad and tried 4.0.5.GA, I reproduced the same configuration but I got the same errors. The errors pasted above where taken from the 4.0.5 version.
The permissions in files are all correct (99% sure) permissions to databases are all correct (100% sure).
I'm using CentOS 4.4, and jdk 1.5.0
Thanks in advance, if you need more info to diagnose the problem, I'll post it. Excuse me if my english is not good.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023973#4023973
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4023973
17Â years, 10Â months
[JBoss Seam] - Re: Using <s:selectItems> with a list of entities
by pgmjsd
Here's the view code:
| <h:selectOneMenu id="theSelect" value="#{myBean.selectedUser}">
| <s:selectItems value="#{myBean.users}" var="user"
| noSelectionLabel="Select a user..." label="#{user.name}"/>
| <ec:convertEntity/>
| </h:selectOneMenu>
|
Here's the SLSB:
@Name("myBean")
| @Stateful
| @Logging
| public class TestBean implements TestLocal
| {
| @PersistenceContext
| private EntityManager em;
|
| private List<User> users;
|
| private User selectedUser;
|
| public List<User> getUsers()
| {
| if (users == null)
| {
| Query q = em.createQuery("select t from User t join t.roles r where r = :role");
| q.setParameter("role", Role.SPECIAL_ROLE);
| //noinspection unchecked
| users = q.getResultList();
| }
| return users;
| }
|
| public User getSelectedUser()
| {
| return selectedUser;
| }
|
| public void setSelectedUser(User selectedUser)
| {
| this.selectedUser = selectedUser;
| }
| @Destroy
| @Remove
| public void destroy()
| {
| }
| }
|
I'm using Seam 1.1.6 and EntityConverter 0.1.
The problem happens when rendering the <h:selectOneMenu> for the first time. I can see with the debugger that the ConverterChain has two converters in it: the NoSelectionConverter and the EntityConverter. The EntityConverter never get's called for the list of Users when rendering.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023971#4023971
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4023971
17Â years, 10Â months
[JBoss jBPM] - Re: Stateless Process Engine executor threading issues
by jorgemoralespou_2
You might be right. And that probably explains the behaviour I'm observing, but how can I actually signal a Token if I'm not hold to a Context.
Execution of nodes should occur within a Context, as long as I know, and since I signaling every node in the execution path, the execution get's done right.
For what I understand from the sources, JBPMContext is bound to the execution thread, and for that reason, seems multi-threadable. As long as I instantiate one JBPMContext in a new thread, the one dispatching the http request from my ws faccade, it should scale properly.
Probably there is an issue with such a load for Hibernate, or something else that escapes my eyes.
Also, I don't want to persist results from executions, or at least only the minimal required, the process instance result, but I don't see any way of disabling this, or any other superflual services for my needs.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023965#4023965
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4023965
17Â years, 10Â months