[Clustering/JBoss] - Re: JBoss5.0.0.Beta1 multiple instances error
by Annegret
Hi,
I use JBoss 5.0.0 Beta 2 and run in the ths same problem : portconflict on 8080
After changing some ports in the server configuration directly additional to the binding file I managed to run 2 instances of JBoss on the same machine.
I had to change additional to the binding file the following ports in the server configuration directly:
JBoss/server/deployers/jbossweb.deployer/server.xml
ports 8080 and 8009
| <Service name="jboss.web">
|
| <!-- A HTTP/1.1 Connector on port 8080 -->
| <Connector port="8080" address="${jboss.bind.address}"
| maxThreads="250" strategy="ms" maxHttpHeaderSize="8192"
| emptySessionPath="true"
| enableLookups="false" redirectPort="8443" acceptCount="100"
| connectionTimeout="20000" disableUploadTimeout="true"/>
|
| <snip>
|
| <!-- A AJP 1.3 Connector on port 8009 -->
| <Connector port="8009" address="${jboss.bind.address}"
| emptySessionPath="true" enableLookups="false" redirectPort="8443"
| protocol="AJP/1.3"/>
|
JBoss/server/deploy/cluster-beans.xml
ports 4447, 1100, 1101
| <bean name="JRMPInvokerHA"
| class="org.jboss.invocation.jrmp.server.JRMPInvokerHA">
|
| <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=invoker,type=jrmpha", exposedInterface=org.jboss.invocation.jrmp.server.JRMPInvokerMBean.class, registerDirectly=true)</annotation>
|
| <depends>HAPartition</depends>
|
| <property name="serverAddress">${jboss.bind.address}</property>
| <property name="RMIObjectPort">4447</property>
|
| <!--
| <property name="RMIObjectPort">0</property>
| <property name="RMIClientSocketFactory">custom</property>
| <property name="RMIServerSocketFactory">custom</property>
| -->
| </bean>
|
| <snip>
|
| <bean name="HAJNDI" class="org.jboss.ha.jndi.HANamingService">
|
| <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=HAJNDI", exposedInterface=org.jboss.ha.jndi.HANamingServiceMBean.class, registerDirectly=true)</annotation>
|
| <depends>HAPartition</depends>
|
| <property name="clusterPartition"><inject name="HAPartition"/></property>
|
| <!-- Bind address of bootstrap and HA-JNDI RMI endpoints -->
| <property name="bindAddress">${jboss.bind.address}</property>
| <!-- Port on which the HA-JNDI stub is made available -->
| <property name="port">1100</property>
| <!-- RmiPort to be used by the HA-JNDI service once bound. 0 => auto. -->
| <property name="rmiPort">1101</property>
| <snip>
|
JBoss/server/deploy/messaging/remoting-service.xml
port 4457
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.messaging:service=Connector,transport=bisocket"
| display-name="Bisocket transport Connector">
| <attribute name="Configuration">
| <config>
| <invoker transport="bisocket">
| <attribute name="marshaller" isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
| <!-- Serialization type must be jms - do not change! -->
| <attribute name="serializationtype" isParam="true">jms</attribute>
| <attribute name="dataType" isParam="true">jms</attribute>
| <attribute name="socket.check_connection" isParam="true">false</attribute>
| <attribute name="timeout">0</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">4457</attribute>
| <snip>
|
|
How can I override these ports using the binding file ?
Annegret
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104418#4104418
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104418
18 years, 8 months
[JBoss Seam] - Problems understanding Seam's jBPM support
by MSchmidke
Hello all,
I'm writing a Seam application which even uses jBPM for some simple business process.
I have no problems using jBPM itself, but since I am using Seam, of course I want to use all benefits Seam gives to me, so I tried to understand chapters 7.3ff of Seam documentation, but there is still one big question:
Which is the suggested way to work with jBPM objects in my own code? Mainly, how should I create the JbpmContext?
Usually, I write:
| @In
| private org.hibernate.Session session;
| ...
| JbpmConfiguration config = JbpmConfiguration.getInstance();
| JbpmContext context = config.createJbpmContext();
| context.setSession(session);
| ProcessInstance pi = context.loadProcessInstanceForUpdate(72150L);
| ...
| context.close();
|
This is the normal jBPM way. Is there also a seam improved way? For example, by injection?
What about JbpmContext lifecycle? May I hold it in a SFSB Seam component field? (Can it be passivated?)
In my SFSB, I use extended Hibernate Sessions as suggested by Seam:
| @Create
| @Begin(flushMode = FlushModeType.MANUAL)
| public void create() {
| }
| @End
| public String actionButton() {
| session.flush();
| return "startseite";
| }
|
How can I combine this best with jBPM?
Any suggestions?
Marcus.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104403#4104403
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104403
18 years, 8 months
[JBoss jBPM] - Re: GPD 3.0.9 Freezes Upon Opening Sample Process
by sujithbabu
I faced a similar issue last week. I used Eclipse 3.1.2 (fresh installation) with GPD jbpm-gpd-site-3.0.9.2 to solve this.
Yo can download these at this location
http://sourceforge.net/project/showfiles.php?group_id=70542&package_id=11...
This is what the doumentation says
********************************************
Eclipse Update Site (jbpm-gpd-site-.zip): If you want to be absolutely sure that the designer installation goes smoothly, we recommend to use the update site mechanism together with a new Eclipse installation. Of cource the Eclipse version should match the downloaded update site archive. To get started with the designer plugin, follow the instructions in the 'readme.html' file included in the archives root folder to succesfully install the GPD.
Eclipse Feature (jbpm-gpd-feature-.zip): If you are tired of each time having to do a fresh Eclipse installation and you are willing to cope with some possible issues, you can try the feature download. In this case installation is as easy as extracting the archive into your Eclipse installation (make sure the included 'plugins' and 'features' folders end up in the same location of your Eclipse installation) overwriting the files and folders with the same name that are possibly already present. This installation is very easy, but you could run into incompatibility issues when you overwrite plugins already present in your installation because of other features that you did install. Though they have the same name it could happen that the versions of these colliding plugins are not equal, hence the possible incompatibilities. The installation instructions are repeated in the 'readme.html' file.
********************************************
Key is fresh installtion of Eclipse 3.1.X (3.1.2 worked for me) with jbpm-gpd-site-3.0.9.2. Hope this helps
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104399#4104399
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104399
18 years, 8 months