Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: JBossAS-5.0.0.GA
Affects Version/s: JBossAS-5.0.0.CR2
Component/s: Deployers
Labels:

Affects:

Compatibility/Configuration
Estimated Difficulty:
Low
Workaround:

Workaround Exists
Workaround Description:
Hide

-4457
Workaround: the file $JBOSS_HOME/server/default/deploy/messaging/remoting-bisocket-service.xml should be updated by replacing the default at line:
<attribute name="serverBindPort">4457</attribute> by another value.

4712
Workaround: the file $JBOSS_HOME/server/default/conf/jbossjta-properties.xml should be updated by replacing the default port at line:
<property name "com.arjuna.ats.arjuna.recovery.recoveryPort" value="4712"/> by another value.
Show
-4457 Workaround: the file $JBOSS_HOME/server/default/deploy/messaging/remoting-bisocket-service.xml should be updated by replacing the default at line: <attribute name="serverBindPort">4457</attribute> by another value. 4712 Workaround: the file $JBOSS_HOME/server/default/conf/jbossjta-properties.xml should be updated by replacing the default port at line: <property name "com.arjuna.ats.arjuna.recovery.recoveryPort" value="4712"/> by another value.

SFDC Cases Counter:
SFDC Cases Links:

Description

Use case: Runs multiple JBoss servers on the same machine.

$JBOSS_HOME: JBoss installation directory.

The default configuration port updated in the file $JBOSS_HOME/server/default/conf/bindings.xml (default to 01 or 02) doesn't override the following default ports:

4457
4712

Attachments

Issue Links

is incorporated by

JBAS-5192 ServiceBindingManager that can handle pojo services

Closed

Activity

People

Assignee:: Brian Stansberry

Reporter:: Alain GATTONE (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2008/11/19 5:43 AM

Updated:: 2011/03/22 2:31 PM

Resolved:: 2008/11/29 11:32 PM