HTTP was recommended if I wanted to pass my firewall, but it seems to me that my problems has nothing to do with that.
The thing is: I started using JBoss some weeks ago for a project I'm about to finish.
Everything was testet over my internal network and worked fine - and I honestly thought it would be a matter of minutes to deploy my client and access my applicationserver over the internet.
But no...
As a part of the problem-solving I changed to HTTP.
The ultimate goal for me is to make that same kind of connection over the net as on my LAN. Don't really care what flavour it has. :-)
Maybe I should tell you that I have two IP-addresses on my server - one internal and one external. There seems to be some confusion about what IP-address JBoss is using.
My jboss-service.xml:
===========================
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE server (View Source for full doctype...)>
- <!-- $Id: jboss-service.xml,v 1.59.2.22 2003/04/13 19:57:10 slaboure Exp $
-->
- <!-- =====================================================================
-->
- <!--
-->
- <!-- JBoss Server Configuration
-->
- <!--
-->
- <!-- =====================================================================
-->
-
- <!--
Load all jars from the JBOSS_DIST/server//lib directory. This
can be restricted to specific jars by specifying them in the archives
attribute.
-->
- <!--
Preload all custom editors for VMs that don't use the thread
context class loader when searching for PropertyEditors. Uncomment
if your JDK 1.3.0 VM fails to find JBoss PropertyEditors.
java.math.BigDecimal=org.jboss.util.propertyeditor.BigDecimalEditor
java.lang.Boolean=org.jboss.util.propertyeditor.BooleanEditor
java.lang.Class=org.jboss.util.propertyeditor.ClassEditor
java.util.Date=org.jboss.util.propertyeditor.DateEditor
java.io.File=org.jboss.util.propertyeditor.FileEditor
java.net.InetAddress=org.jboss.util.propertyeditor.InetAddressEditor
java.lang.Integer=org.jboss.util.propertyeditor.IntegerEditor
javax.management.ObjectName=org.jboss.util.propertyeditor.ObjectNameEditor
java.util.Properties=org.jboss.util.propertyeditor.PropertiesEditor
[Ljava.lang.String;=org.jboss.util.propertyeditor.StringArrayEditor
java.net.URL=org.jboss.util.propertyeditor.URLEditor
-->
- <!-- ====================================================================
-->
- <!-- Log4j Initialization
-->
- <!-- ====================================================================
-->
-
resource:log4j.xml
- <!--
Set the org.apache.log4j.helpers.LogLog.setQuiteMode. As of log4j1.2.8
this needs to be set to avoid a possible deadlock on exception at the
appender level. See bug#696819.
-->
true
- <!-- ====================================================================
-->
- <!-- JBoss RMI Classloader - only install when available
-->
- <!-- ====================================================================
-->
-
java.rmi.server.RMIClassLoaderSpi
org.jboss.system.JBossRMIClassLoader
- <!-- ====================================================================
-->
- <!-- Service Binding
-->
- <!-- ====================================================================
-->
- <!-- Automatically activated when generatting the clustering environment
-->
- <!-- @TESTSUITE_CLUSTER_CONFIG@
-->
- <!--
| Binding service manager for port/host mapping. This is a sample
| config that demonstrates a JBoss instances with a server name 'jboss1'
| loading its bindings from an XML file using the ServicesStoreFactory
| implementation returned by the XMLServicesStoreFactory.
|
| ServerName: The unique name assigned to a JBoss server instance for
| lookup purposes. This allows a single ServicesStore to handle mulitiple
| JBoss servers.
|
| StoreURL: The URL string passed to org.jboss.services.binding.ServicesStore
| during initialization that specifies how to connect to the bindings store.
| StoreFactory: The org.jboss.services.binding.ServicesStoreFactory interface
| implementation to create to obtain the ServicesStore instance.
jboss1
file:/etc/jboss-bindings.xml
org.jboss.services.binding.XMLServicesStoreFactory
-->
- <!-- ====================================================================
-->
- <!-- Class Loading
-->
- <!-- ====================================================================
-->
-
8083
- <!-- Should resources and non-EJB classes be downloadable
-->
true
- <!-- ====================================================================
-->
- <!-- JSR-77 Single JBoss Server Management Domain
-->
- <!-- ====================================================================
-->
-
jboss.system:service=MainDeployer
jboss.system:service=ServiceDeployer
jboss.j2ee:service=EARDeployer
jboss.ejb:service=EJBDeployer
jboss.jca:service=RARDeployer
jboss.jca:service=ConnectionFactoryDeployer
jboss.web:service=WebServer
jboss:service=Mail
jboss.mq:service=DestinationManager
jboss:service=Naming
jboss:service=TransactionManager
jboss:service=ClientUserTransaction
- <!-- ====================================================================
-->
- <!-- JNDI
-->
- <!-- ====================================================================
-->
-
- <!--
The listening port for the bootstrap JNP service. Set this to -1
to run the NamingService without the JNP invoker listening port.
-->
1099
- <!--
10990
-->
- <!-- ====================================================================
-->
- <!-- Security
-->
- <!-- ====================================================================
-->
-
jboss.security:service=XMLLoginConfig
-
login-config.xml
- <!-- JAAS security manager and realm mapping
-->
-
org.jboss.security.plugins.JaasSecurityManager
- <!-- ====================================================================
-->
- <!-- The deployers...
-->
- <!-- ====================================================================
-->
- <!-- EJB deployer, remove to disable EJB behavior
-->
-
true
false
false
true
- <!--
StrictVerifier: Setting this to 'true' will cause all deployments
to fail when the Verifier detected a problem with the contained
Beans.
-->
true
<depends optional-attribute-name="TransactionManagerServiceName">jboss:service=TransactionManager
<depends optional-attribute-name="WebServiceName">jboss:service=WebService
- <!-- EAR deployer, remove if you are not using Web layers
-->
- <!-- ====================================================================
-->
- <!-- Monitoring and Management
-->
- <!-- ====================================================================
-->
- <!--
Uncomment to enable JMX monitoring of the bean cache
-->
- <!--
Uncomment to enable JMX monitoring of the entity bean locking
-->
- <!-- ====================================================================
-->
- <!-- Invokers to the JMX node
-->
- <!-- ====================================================================
-->
- <!-- RMI/JRMP invoker
-->
-
4445
- <!--
custom
custom
custom
ssl-domain-name
-->
jboss:service=TransactionManager
-
jboss:service=TransactionManager
-
1
300
300
60000
0
0
false
<depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager
- <!-- ====================================================================
-->
- <!-- Deployment Scanning
-->
- <!-- ====================================================================
-->
- <!--
Uncomment to enable caching of deployment units
data/deployment-cache
<depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer
<depends optional-attribute-name="Store">jboss.deployment:type=DeploymentStore,flavor=File
-->
- <!--
An mbean for hot deployment/undeployment of archives.
-->
-
- <!--
Uncomment (and comment/remove version below) to enable usage of the
DeploymentCache
<depends optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache
-->
<depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer
- <!--
The URLComparator can be used to specify a deployment ordering
for deployments found in a scanned directory. The class specified
must be an implementation of java.util.Comparator, it must be able
to compare two URL objects, and it must have a no-arg constructor.
Two deployment comparators are shipped with JBoss:
- org.jboss.deployment.DeploymentSorter
Sorts by file extension, as follows:
"sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip",
"*"
- org.jboss.deployment.scanner.PrefixDeploymentSorter
If the name portion of the url begins with 1 or more digits, those
digits are converted to an int (ignoring leading zeroes), and
files are deployed in that order. Files that do not start with
any digits will be deployed first, and they will be sorted by
extension as above with DeploymentSorter.
-->
org.jboss.deployment.DeploymentSorter
- <!--
org.jboss.deployment.scanner.PrefixDeploymentSorter
-->
- <!--
The Filter specifies a java.io.FileFilter for scanned
directories. Any file not accepted by this filter will not be
deployed. The org.jboss.deployment.scanner.DeploymentFilter
rejects the following patterns:
"#*", "%*", ",*", ".*", "_$*", "*#", "*$", "*%", "*.BAK",
"*.old", "*.orig", "*.rej", "*.bak", "*,v", "*~", ".make.state",
".nse_depinfo", "CVS", "CVS.admin", "RCS", "RCSLOG", "SCCS",
"TAGS", "core", "tags"
-->
org.jboss.deployment.scanner.DeploymentFilter
5000
- <!--
URLs are comma separated and resolve relative to the server home URL
unless the given path is absolute. If the URL ends in "/" it is
considered a collection and scanned, otherwise it is simply deployed;
this follows RFC2518 convention and allows discrimination between
collections and directories that are simply unpacked archives.
URLs may be local (file:) or remote (http:). Scanning is supported
for remote URLs but unpacked deployment units are not.
Example URLs:
deploy/
scans ${jboss.server.url}/deploy/, which is local or remote
depending on the URL used to boot the server
${jboss.server.home}/deploy/
scans ${jboss.server.home)/deploy, which is always local
file:/var/opt/myapp.ear
deploy myapp.ear from a local location
file:/var/opt/apps/
scans the specified directory
http://www.test.com/netboot/myapp.ear
deploys myapp.ear from a remote location
http://www.test.com/netboot/apps/
scans the specified WebDAV location
-->
deploy/
- <!--
Indicates if the scanner should recursively scan directories that contains no "." in their names.
This can be used to group applications/services that must be deployed and that have the same
logical function in the same directory i.e.
deploy/JMX/
deploy/JMS/
...
-->
False
- <!--
An alternate hot deployer mbean. Use URLDirectoryScanner if you need to
specify which urls are directories to scan, and which are urls to be
deployed directly. URLDeploymentScanner assumes that all directories are to
be scanned, which can cause problems if directory referred to in the
deploy attribute is an exploded archive.
<depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer
org.jboss.deployment.DeploymentSorter
org.jboss.deployment.scanner.DeploymentFilter
5000
/* Each entry specifies either a dir (directory to be scanned),
or url (url to be deployed). Like the URLs for the DeploymentScanner
above, a file: protocol will be assumed if not specified otherwise.
*/
-->
