[Installation, Configuration & Deployment] - Re: Multiple Instance of JBoss
by visolvejboss
Hello,
The details were explained in that link itself. For your reference we will provide the same information here.
There are two methods of running multiple instances.
1. With the use ipaddress parameter
# run.sh -b localhost
# run.sh -b {ipaddess}
Note that, with this method we are starting two instances of JBoss with the same configuration mode (default). One of the problem with this method is second JBoss instance will thorw an error if you configured to run Hsqldb as your database.
2. By specifying the different ports for each service
To excute this method, you should have two configurations and you should specify different portnumber for each service in this two configurations.
Manually changing the port number for each service is tedious job. So, we can use the ServiceBinding service avaiable in JBoss.
Take an example, you want to run default and all mode in the same server. You can achive this by umcommenting the Service Binding section of the jboss-service.xml file in the conf directory of any of configuration (default or all).
<mbean code="org.jboss.services.binding.ServiceBindingManager"
| name="jboss.system:service=ServiceBindingManager">
| <attribute name="ServerName">ports-01</attribute>
| <attribute name="StoreURL">${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml</attribute>
| <attribute name="StoreFactoryClassName">
| org.jboss.services.binding.XMLServicesStoreFactory
| </attribute>
| </mbean>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960865#3960865
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960865
19 years, 9 months
[JBossCache] - Re: Problem using FileCacheLoader
by confuz
"genman" wrote :
| In terms of design, it's a good idea to make each tree node represent a relational database row (fixed in size), rather than store the contents of an entire database table.
|
| For example, if you were storing customers, each customer should have its own node.
|
Hi Genman,
I can not found any passivation policy support node's value level. but what i need is 100,000 in one node, 20,000 in-memory and 80,000 in passivated status. so i implement that by what you suggested(one node represent a record), but currently in my local machine, the program will hang when putting nodes in to cache and nodes had exceeded 40,000
any suggestions on this issue, thanks
regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960864#3960864
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960864
19 years, 9 months
[JBoss Portal] - Re: User Input Req for 2.6 Usability and UI enhancements
by Frozen4Time
I definately realize that the suggestions I made aren't all that easy and would require some redsign in the layout engine. I guess the point is that I understand the challenges. Never the less I wanted to make my suggestion.
An AJAX based lyout engine would be really nice, but it doesn't HAVE to be that dynamic. Even if the layout util has to make a round trip to the server when layout changes are made, that wouls still be nice enough. This is how EXO works. Its not AJAX, but when you add a container or portlet, an http request goes to the server and a new page comes back with the additions/modifcations.
This isn't quite as slick as the google editor, but it gets the job done. Basically, the key being that you are looking at the page while you are making changes to it.
The reason I have been mentioning EXO is because that is what I am currently using for a project. EXO isn't terribly stable, is a pain to install and hard to pre-configure. These are the things I love about JBoss portal. The only real hold up is the layout engine. The fact that you mention letting users layout their own pages says to me you guys are moving in the right direction since a portal user would expect a simple easy to use layout engine.
I am really trying to champion JBoss portal in my organization and these features would make that task much easier.
Being able to dynamically create any layout you want would be a big benefit, but as you say that would involve being able to cofigure this at runtime which would involve creating a lot of infrastructure as well as changing existing conventions. That being said I think it would be a great feature.
Anyway thanks for your comments.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960859#3960859
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960859
19 years, 9 months
[JBoss Seam] - Remote EJBs
by ptmain
I'm having a difficult time with the concept of my JSP page directly working with EJBs, but I'm trying to let go of the past. I totally bought into the "business delegate" and "value object" architecture for hiding the fact that I used EJBs, etc.
Any comments about how this (directly referencing EJB from a JSP) is no longer evil (if it ever was)?
I do have a few EJB questions:
1. How do I access a remote EJB using Seam? I don't necessarily mean all beans would be remote. I'm working with an application that would need to interact with several sets of services, some local and some remote. I'm wondering if there is some Seam magic for this, so I don't have to have gooey jndi/home iface/remote iface junk in my app.
2. Also, is there anything special I need to do to make one of my EJB sessions also respond to remote calls? [I don't know too much of the EJB3 stuff yet, but I'm hoping I could just add the "@Remote" annotation to the interface - however, how would it be registered with jndi?]
3. What happens on my web page when the JSF listener is a remote session bean and its server is down (our old friend RemoteException)? Is that handled gracefully by Seam, or is there a mechanism for me to handle it gracefully?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960858#3960858
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960858
19 years, 9 months