10:30 a.m.
Hello
I am on trail of a problem that I am facing with JB Messaging and Remoting; Tim from
messaging forum suggested that I post here to perhaps resolve this.
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#...
Summary of my problem is that I am unable to connect/send JMS messages to a remote machine
due https remoting configuration. More details is as follows:
My env...
OS: WinXP
Java: 1.6
JBoss AS: 4.2.2 GA
JBM: 1.4.0.GA
Following is the config part for HTTPS from both remoting-https-service.xml and
connection-factories-service.xml files.
For MQ only SSL port (443) was used for all the JMS communication between client and
server. I see that for JBM + Remoting it uses one more port other than regular SSL port,
9443 in this case as configured in remoting-https-service.xml. Furthermore, in my case -
the server machine only has 443 open and all the other ports are blocked (the network
folks gives me the "hairy eyeball" treatment for requesting to open any other
port). They ask why can't you configure it so that all the comm takes place using just
port 443.
So considering the above, what do you recommend? Is it possible to configure the server so
that it uses only port 443? BTW I tried changing the bind port in the
"remoting-https-service.xml" to 443, but as expected, the server complained at
startup that the port is already occupied etc...
Thanks for your help in advance.
connection-factories-service.xml
| <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
|
name="jboss.messaging.connectionfactory:service=HTTPSConnectionFactory"
| xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
| <depends
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends
optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=https</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
|
| <attribute name="JNDIBindings">
| <bindings>
| <binding>/HTTPSConnectionFactory</binding>
| <binding>/XAHTTPSConnectionFactory</binding>
| <binding>java:/HTTPSConnectionFactory</binding>
| <binding>java:/XAHTTPSConnectionFactory</binding>
| </bindings>
| </attribute>
| </mbean>
|
remoting-https-service.xml
| <server>
|
| <!-- Standard bisocket connector - the bisocket transport only opens connection
from client->server
| so can be used with firewalls where only outgoing connections are allowed.
| For examples of HTTP and SSL transports see docs/examples -->
|
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.messaging:service=Connector,transport=https"
| display-name="HTTPS transport Connector">
|
| <attribute name="Configuration">
| <config>
| <invoker transport="https">
| <attribute name="marshaller"
isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="unmarshaller"
isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="dataType"
isParam="true">jms</attribute>
| <attribute
name="leasePeriod">10000</attribute>
| <attribute name="socket.check_connection"
isParam="true">false</attribute>
| <attribute
name="callbackStore">org.jboss.remoting.callback.BlockingCallbackStore</attribute>
| <attribute name="callbackPollPeriod"
isParam="true">102</attribute>
| <attribute name="clientLeasePeriod"
isParam="true">20000</attribute>
| <attribute
name="serverSocketFactory">jboss.messaging:service=ServerSocketFactory,type=SSL</attribute>
| <attribute
name="SSLImplementation">org.jboss.remoting.transport.coyote.ssl.RemotingSSLImplementation</attribute>
| <attribute
name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute
name="serverBindPort">9443</attribute>
| </invoker>
| <handlers>
| <!--
| <handler
subsystem="web">org.jboss.remoting.samples.http.WebInvocationHandler</handler>
|
| <handler
subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| -->
| <handler
subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| <!-- This depends is included because need to make sure this mbean
is running before configure invoke
| r. -->
|
<depends>jboss.messaging:service=ServerSocketFactory,type=SSL</depends>
| </mbean>
|
| </server>
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098884#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...