[JBoss Messaging] - Re: Failed to download and/or install client side AOP stack
by monk2005
Tim,
Following is the config part for HTTPS from both remoting-https-service.xml and connection-factories-service.xml files.
I think I figured out what is going on though. For MQ only SSL port (443) was used for all the JMS communication between client and server. I see that for JBM 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 Tim, 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 invoker. -->
| <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=4098841#4098841
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098841
18Â years, 6Â months
[JBoss Messaging] - Problems with MaxDeliveryAttempts
by noxis
With JBM 1.4.0.CR1 MaxDeliveryAttempts works fine with my MDB.
Since 1.4.0.CR2 (CR3, GA, trunk) I have to set DLQMaxResent in MDB, because MaxDeliveryAttempts is ignored. I can also see this message after redelivery:
anonymous wrote :
| 2007-10-25 15:49:37,118 WARN [org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler] Message redelivered=6 max=5 sending it to the dlq delegator->JBossMessage[2]:PERSISTENT, deliveryId=7
|
Queue configuration:
| <mbean code="org.jboss.jms.server.destination.QueueService" name="jboss.messaging.destination:service=Queue,name=trStatus"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="DLQ">jboss.messaging.destination:service=Queue,name=trStatus</attribute>
| <attribute name="RedeliveryDelay">2000</attribute>
| <attribute name="MaxDeliveryAttempts">10</attribute>
| </mbean>
|
Is this expected behaviour since 1.4.0.CR2?
I have found that this behaviour was introduced by commit:
"Fix on JMSXDeliveryCount" date: 2007-08-01, revision: 2943
BTW. As you can see in my config, I am trying to do infinite redelivery by pointing DLQ to the same queue. Is this ok? Maybe there is a better solution?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098839#4098839
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098839
18Â years, 6Â months
[JBoss Portal] - External portal definition
by lucboudreau
Hi people. I don't know if this is the right place to discuss this, so please don't flame....
I have Pentaho Pro 1.6 and JBoss portal 2.6.2. I want to create a portal in JBP which uses Pentaho portlet classes but I don't want the definitions and configuration (portlet.xml, portlet0instances.xml, etc) to be included in the Pentaho webapp, but rather in their own deployable and independant webapp. Like this :
$JBOSS_DEPLOY
|
|-----> pentaho.war
|-----> jboss-portal.sar
|-----> my_portal.war
Such a setup allows to redeploy my portal without having to interrupt the service on either of the two other webapps. This is a dream setup and so far, I encountered many challenges to this.
Simply including portlet definitions in a separate webapp can't work because JBoss looks for the classes and can't find them, thus resulting in class not found. Adding classes in the webapp is out of the question, for this would duplicate the pentaho system for EVERY portal I want to externalize.
So I've been investigating the possibility of telling my portal context to share the pentaho.war context. I don'T know if this is possible of if this would result in yet more troubles... I need some insights on this.
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098838#4098838
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098838
18Â years, 6Â months