Examples of JMSWireFormat

org.jboss.jms.server.remoting.JMSWireFormat
We do not use Java or JBoss serialization to send data over the wire. Serialization adds considerable overhead in terms of the amount of data sent (it adds class information plus block data information) which significantly degrades performance. Instead we define a customer wire format that minimises the amount of data sent. The only exception to this rule is when sending an ObjectMessage which contains a user defined object whose type is only known at run-time. In this case we use serialization. @author Tim Fox @author Ovidiu Feodorov @version $Revision: 2399 $ $Id: JMSWireFormat.java 2399 2007-02-23 01:21:29Z ovidiu.feodorov@jboss.com $
org.jboss.jms.wireformat.JMSWireFormat
We do not use Java or JBoss serialization to send data over the wire. Serialization adds considerable overhead in terms of the amount of data sent (it adds class information plus block data information) which significantly degrades performance. Instead we define a customer wire format that minimises the amount of data sent. The only exception to this rule is when sending an ObjectMessage which contains a user defined object whose type is only known at run-time. In this case we use serialization. @author Tim Fox @author Ovidiu Feodorov @version $Revision: 3265 $ $Id: JMSWireFormat.java 3265 2007-10-31 12:44:42Z timfox $

Examples of org.jboss.jms.server.remoting.JMSWireFormat

      catch (Exception e)
      {
         throw new MessagingNetworkFailureException("Failed to connect client", e);
      }


      client.setMarshaller(new JMSWireFormat());
      client.setUnMarshaller(new JMSWireFormat());
      
      return client;
   }

View Full Code Here

Examples of org.jboss.jms.server.remoting.JMSWireFormat

         // We explictly set the Marshaller since otherwise remoting tries to resolve the marshaller
         // every time which is very slow - see org.jboss.remoting.transport.socket.ProcessInvocation
         // This can make a massive difference on performance. We also do this in
         // JMSRemotingConnection.setupConnection
         
         callbackClient.setMarshaller(new JMSWireFormat());
         callbackClient.setUnMarshaller(new JMSWireFormat());
      }
      else
      {
         log.debug("ServerInvokerCallbackHandler callback Client is not available: " +
                   "must be using pull callbacks");

View Full Code Here

Examples of org.jboss.jms.server.remoting.JMSWireFormat

      // We explicitly set the Marshaller since otherwise remoting tries to resolve the marshaller
      // every time which is very slow - see org.jboss.remoting.transport.socket.ProcessInvocation
      // This can make a massive difference on performance. We also do this in
      // ServerConnectionEndpoint.setCallbackClient.


      client.setMarshaller(new JMSWireFormat());
      client.setUnMarshaller(new JMSWireFormat());


      Map metadata = new HashMap();


      metadata.put(InvokerLocator.DATATYPE, "jms");
      // Not actually used at present - but it does no harm

View Full Code Here

Examples of org.jboss.jms.server.remoting.JMSWireFormat


   // Private --------------------------------------------------------------------------------------
  
   private void initializeRemoting(MBeanServer mbeanServer) throws Exception
   {
      JMSWireFormat wf = new JMSWireFormat();


      MarshalFactory.addMarshaller("jms", wf, wf);


      handler = new JMSServerInvocationHandler();
   }

View Full Code Here

Examples of org.jboss.jms.wireformat.JMSWireFormat

         // counter history takes up growing memory to store the stats and could theoretically
         // eventually cause the server to run out of RAM


         txRepository.loadPreparedTransactions();


         JMSWireFormat wf = new JMSWireFormat();
         MarshalFactory.addMarshaller("jms", wf, wf);


         //Now everything is started we can tell the invocation handler to start handling invocations
         //We do this right at the end otherwise it can start handling invocations before we are properly started
         JMSServerInvocationHandler.setClosed(false);

View Full Code Here

Examples of org.jboss.jms.wireformat.JMSWireFormat

      catch (Exception e)
      {
         throw new MessagingNetworkFailureException("Failed to connect client", e);
      }


      client.setMarshaller(new JMSWireFormat());
      client.setUnMarshaller(new JMSWireFormat());
      
      return client;
   }

View Full Code Here

Examples of org.jboss.jms.wireformat.JMSWireFormat

         // We explictly set the Marshaller since otherwise remoting tries to resolve the marshaller
         // every time which is very slow - see org.jboss.remoting.transport.socket.ProcessInvocation
         // This can make a massive difference on performance. We also do this in
         // JMSRemotingConnection.setupConnection


         callbackClient.setMarshaller(new JMSWireFormat());
         callbackClient.setUnMarshaller(new JMSWireFormat());
      }
      else
      {
         log.trace("ServerInvokerCallbackHandler callback Client is not available: " +
                   "must be using pull callbacks");

View Full Code Here

Examples of org.jboss.jms.wireformat.JMSWireFormat

         // counter history takes up growing memory to store the stats and could theoretically
         // eventually cause the server to run out of RAM


         txRepository.loadPreparedTransactions();


         JMSWireFormat wf = new JMSWireFormat();
         MarshalFactory.addMarshaller("jms", wf, wf);


         //Now everything is started we can tell the invocation handler to start handling invocations
         //We do this right at the end otherwise it can start handling invocations before we are properly started
         JMSServerInvocationHandler.setClosed(false);

View Full Code Here

Examples of org.jboss.jms.wireformat.JMSWireFormat

      // We explicitly set the Marshaller since otherwise remoting tries to resolve the marshaller
      // every time which is very slow - see org.jboss.remoting.transport.socket.ProcessInvocation
      // This can make a massive difference on performance. We also do this in
      // ServerConnectionEndpoint.setCallbackClient.


      client.setMarshaller(new JMSWireFormat());
      client.setUnMarshaller(new JMSWireFormat());
      
      onewayClient.setMarshaller(new JMSWireFormat());
      onewayClient.setUnMarshaller(new JMSWireFormat());
      
      Map metadata = new HashMap();
      
      metadata.put(InvokerLocator.DATATYPE, "jms");

View Full Code Here

Examples of org.jboss.jms.wireformat.JMSWireFormat

         // counter history takes up growing memory to store the stats and could theoretically
         // eventually cause the server to run out of RAM


         txRepository.loadPreparedTransactions();


         JMSWireFormat wf = new JMSWireFormat();
         MarshalFactory.addMarshaller("jms", wf, wf);


         //Now everything is started we can tell the invocation handler to start handling invocations
         //We do this right at the end otherwise it can start handling invocations before we are properly started
         JMSServerInvocationHandler.setClosed(false);

View Full Code Here

0 1 2 3 4

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.