[JBoss Messaging] - Re: Client Connect Fails with
by jhd
Here is my remoting-bisocket-service.xml file. I'm using the file "as is" from JBM 1.4.0 SP3.
| <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=bisocket"
| display-name="Bisocket Transport Connector">
| <attribute name="Configuration">
| <config>
| <invoker transport="bisocket">
|
| <!-- There should be no reason to change these parameters - warning!
| Changing them may stop JBoss Messaging working correctly -->
| <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="timeout" isParam="true">0</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">4457</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="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>
| <!-- End immutable parameters -->
|
| <!-- Periodicity of client pings. Server window by default is twice this figure -->
| <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
|
| <!-- Number of seconds to wait for a connection in the client pool to become free -->
| <attribute name="numberOfRetries" isParam="true">10</attribute>
|
| <!-- Max Number of connections in client pool. This should be significantly higher than
| the max number of sessions/consumers you expect -->
| <attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
|
| <!-- Use these parameters to specify values for binding and connecting control connections to
| work with your firewall/NAT configuration
| <attribute name="secondaryBindPort">xyz</attribute>
| <attribute name="secondaryConnectPort">abc</attribute>
| -->
|
| </invoker>
| <handlers>
| <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| </mbean>
|
| </server>
|
I'm not sure what should change here if anything.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140609#4140609
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140609
18 years
[Beginners Corner] - Re: Cannot instantiate class: org.jnp.interfaces.NamingCont
by jaikiran
anonymous wrote : Yet, in all cases I am getting the deployment error:
| *** DEPLOYMENTS IN ERROR: Name -> Error
|
| vfsfile:/C:/jboss/server/default/deploy/simple_session.ear -> java.io.IOException: invalid manifest format
| --------------------------------------
| more specifically:
| 22:14:17,015 WARN [VFSStructureBuilder] Error populating deployment vfsfile:/C:/jboss/server/default/deploy/simple_session.ear
You dont have to change anything in the EAR file. Let the EAR file be as it was earlier (when it was deploying properly).
The changes you have to make is in the client.jar file which you are using to run the standalone client. The MANIFEST.MF file in that jar file should be edited to contain the Class-Path entry. The link that i posted in my earlier reply also mentions that
anonymous wrote :
| Warning : The text file must end with a new line or carriage return. The last line will not be parsed properly if it does not end with a new line or carriage return.
Furthermore, the folder structure should look something like this:
D:
| |
| |--- SomeFolder
| | |
| | |--- client.jar
| | | |
| | | |--- META-INF
| | | | |
| | | | |--- MANIFEST.MF
| | |
| | |
| | |--- jbossall-client.jar
|
The MANIFEST.MF should contain something like:
| Main-Class: lemonpress.client.SimpleSessionClient
| Class-Path: jbossall-client.jar beans.jar
|
|
Note that the jarpath that you specify in the Class-Path entry is relative to the jar file. So in this case, the jbossall-client.jar file will be searched in the same folder as client.jar. Please go through the documentation that i posted earlier, for more details.
While posting the logs or xml content or code, remember to wrap it in a code block using the Code button in the message editor window and please hit the Preview button to make sure your post is correctly formatted
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140600#4140600
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140600
18 years