[Installation, Configuration & Deployment] - Jboss-4.0.5 port binding problem
by baileyc
I am attempting to use a port-bindings.xml file to run multiple jboss instances on a single server, but find that the bindings appear to be not being used by jboss, with no errors being reported, and the server starts perfectly ok but using the default ports.
I would appreciate any asisstance, have I overlooked anything?
I start jboss with the standard default server configuration with the additional following definitions on command line:
| -Djboss.bind.address=localhost -Djboss.portbindings.config=ports-01
|
The jboss-service.xml has the following definition:-
| <mbean code="org.jboss.services.binding.ServiceBindingManager"
| name="jboss.system:service=ServiceBindingManager">
| <attribute name="ServerName">${jboss.portbindings.config}</attribute>
| <attribute name="StoreURL">${jboss.server.config.url}/port-bindings.xml</attribute>
| <attribute name="StoreFactoryClassName">
| org.jboss.services.binding.XMLServicesStoreFactory
| </attribute>
| </mbean>
|
The boot log shows the port-bindings.xml file being picked up and what appears to be the correct ServiceName
| 10:46:23,602 DEBUG [ServiceCreator] About to create bean: jboss.system:service=ServiceBindingManager with code: org.jboss.services.binding.ServiceBindingManager
| 10:46:23,628 DEBUG [ServiceCreator] Created bean: jboss.system:service=ServiceBindingManager
| 10:46:23,630 DEBUG [ServiceConfigurator] ServerName set to ports-01 in jboss.system:service=ServiceBindingManager
| 10:46:23,632 DEBUG [ServiceConfigurator] StoreURL set to file:/jbosssandpit/server/default/conf/port-bindings.xml in jboss.system:service=ServiceBindingManager
| 10:46:23,634 DEBUG [ServiceConfigurator] StoreFactoryClassName set to org.jboss.services.binding.XMLServicesStoreFactory in jboss.system:service=ServiceBindingManager
|
The problem ocurrs in that although the ports have been changed in the xml file, jboss still appears to use the defaults
| 10:46:23,878 DEBUG [ServiceCreator] Created bean: jboss:service=Naming
| 10:46:23,878 DEBUG [ServiceConfigurator] CallByValue set to false in jboss:service=Naming
| 10:46:23,883 DEBUG [ServiceConfigurator] Port set to 1099 in jboss:service=Naming
| 10:46:23,885 DEBUG [ServiceConfigurator] BindAddress set to localhost in jboss:service=Naming
| 10:46:23,886 DEBUG [ServiceConfigurator] RmiPort set to 1098 in jboss:service=Naming
| 10:46:23,888 DEBUG [ServiceConfigurator] RmiBindAddress set to localhost in jboss:service=Naming
| 10:46:23,890 DEBUG [ServiceController] recording that jboss:service=Naming depends on jboss.system:service=ThreadPool
| 10:46:23,890 DEBUG [ServiceConfigurator] considering LookupPool with object name jboss.system:service=ThreadPool
|
The relevant entries from the ports-bindings.xml
| <!-- ********************************************************** -->
| <!-- * ports-01 * -->
| <!-- ********************************************************** -->
| <server name="ports-01">
|
| <!-- EJB3 Remoting Connector ejb3.deployer/META-INF/jboss-service.xml -->
|
| <service-config name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3"
| delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
| <delegate-config>
| <attribute name="InvokerLocator">socket://${jboss.bind.address}:3973</attribute>
| </delegate-config>
| <binding port="3973"/>
| </service-config>
|
| <!-- ********************* jboss-service.xml ****************** -->
|
| <service-config name="jboss:service=Naming"
| delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
| >
| <delegate-config portName="Port" hostName="BindAddress">
| <attribute name="RmiPort">1198</attribute>
| </delegate-config>
| <binding port="1199" host="${jboss.bind.address}"/>
| </service-config>
| .
| .
| .
| </server>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998120#3998120
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998120
19 years, 3 months
[JBoss Seam] - Re: Seam and Portal Future
by jboss＠biancashouse.com
I agree with Smithy. Right now it is proving to be just too difficult to work out the right combinations of artifacts to get Seam and Portal and jBPM and Facelets and AJAX etc working together.
Even the JBoss guys have not yet been able to do it !
I also agree with Norman, that Portal does make our life easier, because we can let non-developers get on with building the page structure and adding content items using the Admin and CMS Admin portlets resp. while we concentrate on building the important self-service processes of our web app.
So I have this cunning idea ...
- use Portal's various admin portlets to build your page structure and content
- use Seam + Facelets + jBPM + AJAX to render your web pages and dialogues, extracting the page structure and content items from Portal's DB using the Portal (and JCR) APIs. So, in effect, our web app will be driven by the Portal DB.
- some time later, when a future version of Portal becomes available that fixes our problems, we can move our Seam app towards pure portlets.
So JBoss guys: will v3 of Portal be resolving the above ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998118#3998118
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998118
19 years, 3 months
[JBoss Seam] - Seam design
by monkeyden
I'm in the process of designing a new, and much larger Seam application and had some design questions. First, here are a few things I'd like to have in my next Seam implementation:
1. Provide some separation of interests without committing to the onerous DAO pattern
2. Provide some way to implement non-persistent business methods. These might be state-sensitive mutators (e.g. modifying some entity attribute when some other entity attribute crosses a threshold)
3. Provide a lightweight object to interact with in the SLSB, rather than the entity itself, without having to duplicate all of the entities methods.
My first thought was to have my business objects extend their respective entities, to make use of it's methods and implement finders and non-persistent business methods, but then I lose EJB 3.0 persistence, so that's out of the question.
>From my first implementation of DAOs, I felt as though I was writing (generating) a lot more boilerplate code than I should. Has anyone discovered a way to get reasonable separation without having to replicate the entire entity interface?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998111#3998111
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998111
19 years, 3 months