[JBoss Messaging] - JBoss Messaging 1.3.0.GA released
by timfox
I am pleased to announce JBoss Messaging 1.3.0.GA has been released!
(This has been renamed from 1.2.0.SP2 to better follow the JBosss versioning guidelines).
This is an important release, the main theme of which is better useability for JBoss Messaging users, and better integration in JBoss Application Server.
Previous releases of JBoss Messaging used different versions of various thirdparty jars compared to JBoss Application Server. This meant, that when running JBoss Messaging inside the app server it was either necessary to do a "scoped" deployment, where JBoss Messaging is configured to run in its own classloading domain, or to copy the newer jars into the application server, overwriting what was previously there.
Scoped deployments introduced a whole slew of issues, not least of which is they are very difficult to configure and meant that other services using JBoss Messaging had to specify the classloading domain. This resulted in a lot of headaches for our users. Overwriting jars in the application server came with its own problems and gave incompatibilties with other services e.g. EJB3 and web services, and also gave support issues since the user was now using a version of the AS with a customer configuration of jars - something that's hard to support.
Another compatibility issue we previously had was that the jboss-messaging-client.jar packaged up all its dependent libraries in it. This caused problems with users who wanted to use different versions of jars, e.g. log4j.jar.
With JBoss Messaging 1.3.0.GA, the product is no longer deployed as scoped deployment, and we now supply a thin client jar. The installation guide describes what other jars you will need on your client classpath to get it to work (not many). We have ensured that JBoss Messaging 1.3.0.GA and JBoss AS 4.2.0.GA have their dependencies all aligned, this means JBoss Messaging works smoothly with 4.2.0.GA, but also that we no longer recommend (in fact we highly recommend against) installing JBoss Messaging in earlier versions of JBoss AS. You can probably get JBoss Messaging to work in JBoss AS 4.0.x, but we don't guarantee you won't have issues with compatibility with other services, in particular clustering, EJB3 and web services.
Clustering in JBoss Messaging 1.3.0.GA now runs in the "all" configuration, unlike previous versions which had difficulty running in "all".
>From now on we are going to keep our dependencies aligned with the application server which may mean the latest version of JBoss Messaging will only work with the latest version of JBAS. This makes a lot of sense, since before very long, JBoss Messaging is going to be the default JMS provider for JBoss AS, so it will be an intrinsic part of the application server.
This release also includes many important bug fixes - please see the release notes for full details, it also includes some new functionality like an implementation of clustered JMS temporary queues.
We also have changed the clustering behaviour a little. The default connection factories at /ConnectionFactory and /XAConnectionFactory are now *non clustered*, i.e. they don't support automatic failover or automatic connection load balancing. This is to provide better compatibility with applications originally written against JBoss MQ which don't expect load-balancing or automatic failover. If you want a clustered connection factory, one is available at /ClusteredConnectionFactory, or you can deploy your own. See the userguide for more details.
We have also expanded the documentation in this release, and produced a section on how to use the message bridge, which was there in JBoss Messaging 1.2.0 but undocumented, so no-one knew how to use it!
Similarly there is a new section on how to enable XA transaction recovery with JBoss Messaging.
We have also created a couple of new examples - one demonstrating the message bridge in action, and another demonstrating using HAJNDI to talk to a clustered EJB which talks to JBoss Messaging.
The year ahead will be an exciting time for JBoss Messaging, as it will become the default JMS provider in JBoss AS, and is also a key part of Red Hat's messaging strategy - which we will have more to say about over the next few weeks!
Stay tuned, and thanks most of all to you, our users.
Full release notes are available here: http://jira.jboss.com/jira/secure/ReleaseNote.jspa?projectId=12310061&sty...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050621#4050621
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050621
18Â years, 10Â months
[JBoss Seam] - Data Model Values not getting populated
by aschneid75
Hi,
We are running into a slight issue, and it's probably something we are doing wrong, but cannot really see anything going wrong.
We have a JSF page with a data model defined on it. The data model is being populated just fine on page rendering. Inside of this data model we have a text input down one column and a date picker down another (total of five columns). The problem comes in when we change some of the data in the text box or add new text to an empty text box, or modify one of the date pickers.
When submit is pushed, the save() method on the backing bean is called and when we go to process the data model to parse out any changes, the data is the same as when it was rendered. No changed data gets pushed back to the server.
Is there something we are doing wrong, or are we just off base on how the data model is supposed to work?
We can post whatever code or config files would help.
Thanks,
Andrew
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050611#4050611
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050611
18Â years, 10Â months
[Installation, Configuration & Deployment] - Re: NestedRuntimeException: Error creating MBeanProxy: jboss
by jaikiran
anonymous wrote : Where does i have to register the WebService MBean?
You dont have to. This MBean gets created by default and is configured in the jboss-service.xml file present in %JBOSS_HOME%/server/default/conf:
<mbean code="org.jboss.web.WebService"
| name="jboss:service=WebService">
| <attribute name="Port">8083</attribute>
| <!-- Should resources and non-EJB classes be downloadable -->
| <attribute name="DownloadServerClasses">true</attribute>
| <attribute name="Host">${jboss.bind.address}</attribute>
| <attribute name="BindAddress">${jboss.bind.address}</attribute>
| </mbean>
Unless you have done any changes to this file, i would expect this to be deployed. Are there any other exceptions before/after this exception stacktrace. Going by the stacktrace, JBoss is trying to deploy the SchedulerAdminEJB module and running into this exception. I dont have any experience with Jetty, so dont know whether the exception is related to that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050609#4050609
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050609
18Â years, 10Â months
[Persistence, JBoss/CMP, Hibernate, Database] - Oracle Datasource Slow (Max CPU) while JDBC super-fast
by JustinCRL
If I create a direct connection to Oracle using JDBC I can execute a simple query that pulls back about 1,400 records in 100-200 ms. If I used a JBOSS defined data source, the query takes 23 SECONDS!
I'm running:
JBoss 4.02
Oracle 10gR2 (10.2.0.2.0) on Linux
JDK 1.5
WinXP
If I execute the following code, it is very fast.
Class.forName("oracle.jdbc.driver.OracleDriver");
conn = DriverManager.getConnection("jdbc:oracle:thin:@linoradev1.crlcorp.com:1521:CRLDEV", "stsetup", "stsetup");
Statement smt = conn.createStatement();
ResultSet rs = smt.executeQuery("SELECT STUDY.STUDY_PKID AS ID, STUDY.STUDY_CODE AS CODE, STUDY.STUDY_NAME AS STUDY_NAME, SPONSOR.SPONSOR_NAME AS SPONSOR_NAME FROM STUDY, SPONSOR where STUDY.SPONSOR_PKID = SPONSOR.SPONSOR_PKID");
while (rs.next()) {
int id = rs.getInt("ID");
String code = rs.getString("CODE");
String studyName = rs.getString("STUDY_NAME");
String sponsorName = rs.getString("SPONSOR_NAME");
StudySummary study = new StudySummary();
study.setID(id);
study.setStudyCode(code);
study.setStudyName(studyName);
study.setSponsorName(sponsorName);
studies.add(study);
}
If I replace the first two statements with:
DataSource dataSource = (DataSource) new InitialContext().lookup("java:/crlcorp/tls/accessioning");
conn = dataSource.getConnection();
Then it takes 23 seconds.
My -ds.xml file contains:
<local-tx-datasource>
<jndi-name>crlcorp/tls/accessioning</jndi-name>
<connection-url>jdbc:oracle:thin:@linoradev1.crlcorp.com:1521:CRLDEV</connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver
</driver-class>
</local-tx-datasource>
I'm using Classes12.zip for the driver.
>From logging I can tell that the query executes quickly. The slow down occurs when reading the result set. I have also noticed that my CPU is maxed when I'm doing this. This problem has been replicated on a separate desktop.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050606#4050606
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050606
18Â years, 10Â months