[JBoss Messaging] - Re: Bridge error because of network problems also influences
by mclu
Hi Howard!
I did some tests over the weekend.
I added
true
or
true
to my invoker configuration (see below)
But this results in timeouts while getting connections so bridge or in general JMS does not work then:
| Caused by: org.jboss.remoting.ConnectionFailedException: Timed out trying to create control socket
| at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.handleConnect(BisocketClientInvoker.java:272)
| at org.jboss.remoting.MicroRemoteClientInvoker.connect(MicroRemoteClientInvoker.java:263)
| at org.jboss.remoting.Client.connect(Client.java:1528)
| at org.jboss.remoting.Client.connect(Client.java:468)
| at org.jboss.remoting.callback.ServerInvokerCallbackHandler.connect(ServerInvokerCallbackHandler.java:161)
| at org.jboss.remoting.ServerInvoker.getCallbackHandler(ServerInvoker.java:1863)
| at org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1497)
| at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.handleInternalInvocation(BisocketServerInvoker.java:643)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:853)
| at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
| at org.jboss.remoting.Client.invoke(Client.java:1640)
| at org.jboss.remoting.Client.addCallbackListener(Client.java:1709)
| at org.jboss.remoting.Client.addListener(Client.java:927)
| at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:259)
|
By the way! I am using an SSL Bisocket connector from the the sslbisocket example configuration.
This is my remoting-bisocket-service.xml:
| <server>
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.messaging:service=Connector,transport=sslbisocket"
| display-name="SSL Bisocket Transport Connector">
| <attribute name="Configuration">
| <config>
| <invoker transport="sslbisocket">
| <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="socket.check_connection" isParam="true">false</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">24457</attribute>
| <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
| <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
| <attribute name="serverSocketFactory">jboss.messaging:service=ServerSocketFactory,type=SSL</attribute>
| <attribute name="numberOfCallRetries" isParam="true">1</attribute>
| <attribute name="pingFrequency" isParam="true">214748364</attribute>
| <attribute name="pingWindowFactor" isParam="true">10</attribute>
| <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
| <attribute name="stopLeaseOnFailure" isParam="true">true</attribute>
| <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
| <attribute name="timeout" isParam="true">0</attribute>
| <attribute name="numberOfRetries" isParam="true">10</attribute>
| <attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
| <attribute name="callbackTimeout">10000</attribute>
| <!-- <attribute name="force_remote">true</attribute> -->
| </invoker>
| <handlers>
| <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| <depends>jboss.messaging:service=ServerSocketFactory,type=SSL</depends>
| </mbean>
|
| <mbean code="org.jboss.remoting.security.SSLServerSocketFactoryService"
| name="jboss.messaging:service=ServerSocketFactory,type=SSL"
| display-name="SSL Server Socket Factory">
| <depends optional-attribute-name="SSLSocketBuilder" proxy-type="attribute">jboss.messaging:service=SocketBuilder,type=SSL</depends>
| </mbean>
|
| <mbean code="org.jboss.remoting.security.SSLSocketBuilder"
| name="jboss.messaging:service=SocketBuilder,type=SSL"
| display-name="SSL Server Socket Factory Builder">
| <attribute name="UseSSLServerSocketFactory">true</attribute>
| </mbean>
|
| </server>
|
What should we do now?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218145#4218145
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218145
17 years, 3 months
[Installation, Configuration & DEPLOYMENT] - JBoss + Apache
by Endy
I have a dozen sites running on my old server, some purely Java sites and some PHP ones, all running on good 'ol Orion. I'm migrating to a new server, and switching to JBoss.
I've been contemplating on how to set up everything. I've been thinking of running both Apache for the PHP sites, and JBoss for my Java sites, in parallel and configure/bind them to listen to the specific IPs without being aware of each other. Ie, Apache would listen to the IPs for the PHP sites and handle those, while JBoss would listen the IPs for the Java sites. Both would have virtual host configs since there are multiple sites. I figured this approach would be a lot easier than using Apache as front end and JBoss as back end or vice versa.
The question is, is this a feasible approach ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218144#4218144
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218144
17 years, 3 months
[JBossWS] - JBoss ws-security client error
by manasamurthy
When I run my web service client war, I get the below error. These are the steps I have followed:
1. Generate code using wsconsume
2. Deploy both client and server (server running locally)
3. Add jboss-wsse-client.xml appropriately
4. On the first call to the server after getting port I get the exception:
[Fatal Error] :-1:-1: Premature end of file.
2009-03-16 00:44:28,298 -0700 ERROR [org.jboss.ws.extensions.security.jaxws.WSSecurityHandler] uniqueId=ec95a826-a291-47ab-abbe-17ecd2435531 hostname=pditvm10286 requestURI=/billing/payment-request/list.url clientIP=127.0.0.1 (abc(a)gmail.com) Cannot handle inbound ws-security
javax.xml.soap.SOAPException: Cannot obtain SOAPHeader from SOAPMessage
at javax.xml.soap.SOAPMessage.getSOAPHeader(SOAPMessage.java:202)
at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:113)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:78)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient.handleInbound(WSSecurityHandlerClient.java:40)
at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140)
at org.jboss.ws.core.jaxws.client.ClientImpl.callResponseHandlerChain(ClientImpl.java:168)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:363)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy304.initializeItemCatalogService(Unknown Source)
My jboss-wsse-client.xml looks like this
<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/ws-security/config http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
</jboss-ws-security>
I have ensured the server code works, by writing a standalone client with the same code and it runs fine. Am I missing anything?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218142#4218142
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218142
17 years, 3 months