[Installation, Configuration & DEPLOYMENT] - multiple ear files? good idea, or bad idea? how to?
by cooper123
Here's the basic infrastructure of the system of a system I'm now responsible for cleaning up:
1. core SOA (has persistence, transactions, web services, security)
2. various service modules (App A, App B, etc.) that talk to the core SOA - for example, this is where the DAO, BO, TO, persistence (hibernate) objects are.
3. client application (App A, App B, etc.)
Currently, during the build process the core SOA (#1) and all the service modules (#2) are bundled together in a single ear file. The client applications each have their own war. All these files get deployed to a server running JBoss (we are using version 4.03, but I'm looking to upgrade it).
I'd like to split up the large ear file (#1 and #2) into several ear files:
-a single ear file for the core
-a separate ear file for each service module (the service modules are supposedly independent of one another)
The reason I want to do this is that if I update App B, I should only have to redeploy the service module and client app for App B. I shouldn't have to reploy the whole entire thing.
My questions:
-does it make sense to separate the core SOA and the various service modules into separate ear files?
-if so, in JBoss, how do I ensure that the core SOA gets loaded before the various service modules?
-is there anything you can think of off the top of your head that I should be careful
thanks in advance!!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158099#4158099
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158099
18 years, 1 month
[JBoss Messaging] - Re: Help on JBoss Messaging
by ebenezerlovelin
Thank you so much for the link.
I am confused a lot now; I apologize for troubling you. Let me ask few things and I am sure when I get this answered, I will have the confusion cleared.
1. When you say anonymous wrote : we aways send the message to the consumers on the box where you sent the message do you mean that it is better to have two or more nodes (in that case, two or more queues) in the same Jboss Server i.e., have two or more instances, messaging-node0, messaging-node1....in the same Jboss Server in a single machine?
If you meant that, I have tried exactly the same thing; I have one Jboss 4.2.2 GA server with two messaging nodes, messaging-node0 and messaging-node1. Now when I send messages to one queue, I thought that the load balancer will balance the load by sending the messges to all the queues available in the cluster...in my case, the two queues. But it doesnt happen; it sends it to one queue and while in the process of sending, if the queue fails, then it sends it to the next queue.
2. When you say anonymous wrote : If you have multiple producers (one on each box), you would have the load distributed Do you mean to say that I should have NOT just one producer, but have 2 or more producers to produce messages to have the load evenly distributed? If you say yes, I am going to test with 2 or more producers(one in each node) to see if the load is balnced.
3. Also, while receiving or consuming, when I have 2 or more consumers (in different nodes on the cluster), will each consumer consume from the queue where the messages are queued up. Let me put it this way; I have three physical machines and three Jboss AS 4.2.2 GA, one for every machine and I have distributed queues named testDistributedQueue in all the nodes. Now, I have TWO producers(let us say, in node 1 and node 2) producing the messages to the queues (in node 1 and node 2) and THREE consumers (one in each node, 1, 2 and 3) listening to the queues.
3.1 While sending, will the messages be evenly sent across to all the THREE queues including the third queue (remember only TWO producers are sending the messages)
3.2 While consuming, will all the consumers consume evenly...
Thanks in advance.
Regards,
Ebe
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158097#4158097
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158097
18 years, 1 month
[JBoss Portal] - Re: Portal-Cluster: REPL_ASYNC vs. REPL_SYNC
by IronMan77
Although the logout has been fixed in 2.6.5-sp1 (i can confirm that!) it's no viable option for us. As we were already in a production environment there are to many changes in my opinion (many services have been renamed for example) to use it.
As a follow up to the portlet preferences problem:
We currently working to a solution with a hardare loadbalancer, but with sticky sessions - no HTTP-Session replication and no SSO. Only the configuration is clustered with a shared db.
I can reproduce the issues without the load balancer if i adress the cluster nodes direct. Example: Three nodes (node-1, node-2, node-3).
Say i configure a (new!) portlet instance via the admin portlet on node-1 and add it to a (new) window on a existing page.
Log in to node-2 or being already logged in on node-3 (it doesn't seem to matter) the content of the PortletPreferences for the new instance from the JBossRenderRequest are NOT populated right - the "fall back" (mostly - not every time) to the standard values from the portlet.xml. They are ALWAYS(!) correct in node-1 and on all nodes(!) within the admin-portlet.
I have spent some time debugging the issue - it seems that the InstanceDefintion is not popluated correct from the TreeCache. The InstanceDefinition should contain a value like "local_51" but it contains a value like "./portletname-local" or something. I have given up at this point , we are now working with the ASYNC setting.
Kind regards,
Stephan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158095#4158095
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4158095
18 years, 1 month