Hi,
I have been working in
the server-side environment for couple of years and now
have been searching for the app servers.The Jboss comes
in my list as I had heard a lot regarding that.I have
evaulated the following application servers:
 1)Weblogic7.0
 2)orion1.5
 3)Borland AS 4.5(In progress)
 4)Pramati3.0
 5)websphere4.0(In progress)
 6)iplanet6.5(In progress)
 7)Jboss3.0(In progress)
 The In progress status is due to the some
configuration problems.I have been able to deploy the
 applications successfully in Jboss but configuring the
DataSource is creating the problem.Initially reading
the default DataSource also gave me the problem
,anywway I got some workaround solution and I
 could notice lots of difference out in this
application server.
 In most of the appservers I used to retrieve the
object directly from the JNDI(from different JVM),but
 in Jboss it can't be done so I will have to use the
 EJB,s to retrive the Object from jndi...
 Let me come to the problem which I do get .......
 1)
  I have added the following mbean in the jboss.jcml
file
 <!-- vk for the Oracle Data Source 24/05/2002 -->
  <mbean code="org.jboss.jdbc.XADataSourceLoader"
name="DefaultDomain:service=XADataSource,name=Oracle9DS">
    <attribute name="PoolName">Oracle9DS</attribute>
    <attribute
name="DataSourceClass">oracle.jdbc.xa.client.OracleXADataSource</attribute>
    <attribute name="Properties"></attribute>
    <attribute
name="URL">jdbc:oracle:thin@192.168.0.1:1521:ORC1</attribute>
    <attribute name="GCMinIdleTime">1200000</attribute>
    <attribute name="JDBCUser">username</attribute>
    <attribute name="MaxSize">10</attribute>
    <attribute name="Password">password</attribute>
    <attribute name="GCEnabled">false</attribute>
    <attribute
name="InvalidateOnError">false</attribute>
    <attribute name="TimestampUsed">false</attribute>
    <attribute name="Blocking">true</attribute>
    <attribute name="GCInterval">120000</attribute>
    <attribute name="IdleTimeout">1800000</attribute>
    <attribute
name="IdleTimeoutEnabled">false</attribute>
    <attribute name="LoggingEnabled">false</attribute>
    <attribute
name="MaxIdleTimeoutPercent">1.0</attribute>
    <attribute name="MinSize">0</attribute>
  </mbean>
  <!-- vk for the Oracle Data Source -->
 I have put the classes12.jar in the lib/ext also...
---------2) When I start the jboss with the tomcat I
get on Windows 2000 professional it gives me
 this result
  
##########################################################################
  .
  .
  .
[Default] The Initial Developer of the Original Code is
Lutris Technologies Inc.

Portions created by Lutris are Copyright (C) 1997-2001
Lutris Technologies, Inc.

All Rights Reserved.
[Default] Server 1.4 is running
[Default] Press [Ctrl]+[C] to abort
[XADataSourceLoader] Started
[XADataSourceLoader] Starting
[DefaultDS] XA Connection pool DefaultDS bound to
java:/DefaultDS
[XADataSourceLoader] Started
[XADataSourceLoader] Starting
[Oracle9DS] XA Connection pool Oracle9DS bound to
java:/Oracle9DS
 ##########################################################################
..... And here it gets held up,which has been
fraustating me,I also tried to get the source code of
the org.jboss.jdbc.XADataSourceLoader but could not get.
---------3) I believe it is waiting for some
resource.....
---------4) Also in my ejbs I have a method which reads
the java:/DefaultDS,it gets the Object but then it
gives Exception....
---------5)
          When I start the jboss with the tomcat I get
on Windows 98 professional it gives me this
 result
  
##########################################################################
   Portions created by Lutris are Copyright (C)
1997-2001 Lutris Technologies, Inc.
All Rights Reserved.
[XADataSourceLoader] Started
[XADataSourceLoader] Starting
[DefaultDS] XA Connection pool DefaultDS bound to
java:/DefaultDS
[XADataSourceLoader] Started
[XADataSourceLoader] Starting
[Configuration] java.lang.NoClassDefFoundError:
javax/transaction/xa/XAException
[Configuration] at java.lang.Class.forName0(Native
Method)
[Configuration] at
java.lang.Class.forName(Class.java:120)
[Configuration] at
org.jboss.jdbc.XADataSourceLoader.startService(XADataSourceLoader.java:344)
[Configuration] at
org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:107)
[Configuration] at
java.lang.reflect.Method.invoke(Native Method)
[Configuration] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[Configuration] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[Configuration] at
org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(ConfigurationService.java:836)
[Configuration] at $Proxy0.start(Unknown Source)
[Configuration] at
org.jboss.util.ServiceControl.start(ServiceControl.java:81)
[Configuration] at
java.lang.reflect.Method.invoke(Native Method)
[Configuration] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[Configuration] at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[Configuration] at org.jboss.Main.<init>(Main.java:210)
[Configuration] at org.jboss.Main$1.run(Main.java:116)
[Configuration] at
java.security.AccessController.doPrivileged(Native
Method)
[Configuration] at org.jboss.Main.main(Main.java:112)
[ServerDataCollector] Starting
[ServerDataCollector] JBoss Management Service
'servercollector'
  
##########################################################################
 jts.jar is already present in the lib/ext,its size is
9k.
I have been trying to get the solution from the forum
but currently the link is down and my requirement is
very urgent.
 Hope you understand my urgency and try to provide the
 solution at earliest,I have spend a week to sort this problem but couldnot get it solved,Please help Jboss gurus....
thank you ....
 regards VickyKak
 vickykak at justice dot com

Have you read and followed the instructions in chapter 10 of the upcoming JBoss3 Quick Start guide ?

Alpha version of this guide at:
http://prdownloads.sourceforge.net/jboss/JBoss.3.0QuickStart.pdf?download

Hmmm...

AFAIK - you say you are reviewing version 3.0, but the config change seems what you would do for version 2.4.x...

3.0 and 2.4.x are radically different.