[Design of JBoss ESB] - JBoss ESB Performance/optimal configurations
by Busrider2008
Been working with prototypes and some quickstarts from the JBoss ESB 4.3 GA application server and I have been a little confused with all the options of JBossMQ, JBossMessaging, using ActiveMQ with the ESB, and using straight vanilla JMS outside the bus.
Running some initial tests for performance on a series of actions in my test service (display message, Smooks transformation, XML2 Pojo, and dislaynewmessage) just so I can see where some bottlenecks might be...I am seeing that using the ESB with ActiveMQ as the JMS provider looks to be quickest per action.
The monitoring console available on localhost:8080 shows each ESB and has success, failure threads, and processing time. First question, the numbers for processing time are in what unit of time?
Second question, what is the suggested optimal configuration using the ESB? Maxthreads per JMS Listener? I have not seen a good thread yet on numbers people are seeing playing with different providers and libraries.
I will continue to profile the time for processing using JProbe with filtering by particular methods, but any suggestions would be great in the meantime.
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165741#4165741
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165741
17 years, 8 months
[Design of the JBoss EJB Container] - JBOSS 5.0 + SQL SERVER 2005 = ClassNotFoundException: com.mi
by szymanski
Hi friends,
I'm trying to use JBOSS 5.0 with MS SQLSERVER 2005, but I'm getting the following error:
[JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
| org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Failed to register driver for: com.microsoft.sqlserver.jdbc.SQLServerDriver; - nested throwable: (java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver.
I put the lib driver in the server/default/lib folder and my datasource-ds.xml is like this
<?xml version="1.0" encoding="UTF-8"?>
| <datasources>
| <local-tx-datasource>
| <jndi-name>MSSQLDS</jndi-name>
| <connection-url>
| jdbc:sqlserver://localhost;instanceName=SQL2005;portNumber=1433;databaseName=question;
| </connection-url>
| <driver-class>
| com.microsoft.sqlserver.jdbc.SQLServerDriver
| </driver-class>
| <user-name>xxx</user-name>
| <password>xxx</password>
| <metadata>
| <type-mapping>MS SQLSERVER</type-mapping>
| </metadata>
| </local-tx-datasource>
| </datasources>
every time that I start the server, I get the error, what hell is going on...?
Thanks to everyone.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165727#4165727
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165727
17 years, 8 months
[Design of Messaging on JBoss (Messaging/JBoss)] - How to specify which transports are supported
by timfox
I've been doing a refactoring of our remoting layer.
I've made a lot of changes and simplifications and I've separated out all our core and generic remoting code - this code has no dependencies on any particular transport implementation e.g. MINA.
I have also created a service provider interface package (spi), in a similar way you get JDBC spi, JTA spi etc This is a set of classes which define the contract between out remoting code and the transport itself (e.g. MINA).
Basically, to integrate a particular transport provider you need to implement a set of classes which are then used by our remoting code:
Acceptor
AcceptorFactory
Connector
ConnectorFactory
TransportConnection.
This are simple interfaces since the bulk of the code has been moved to the core remoting code which is the same for all transport providers.
There are methods on RemotingService and ConnectionRegistry:
registerAcceptorFactory(...)
unregisterAcceptorFactory(...)
registerConnectionFactory(...)
unregisterConnectorFactory(...)
One remaining unresolved issue is how to tell the RemotingService/ConnectionRegistry which transports it supports (i.e. who calls register?)- currently this is hardcoded,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165669#4165669
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165669
17 years, 8 months