JDBC, Tomcat, J2EE server

I would like to request help with JDBC, Tomcat and the J2EE server.
I have figured out how to connect a servlet running in Tomcat 4.0 to a Filemaker database using Filemaker's JDBC drivers:
Class.forName("com.fmi.jdbc.JdbcDriver");
fmpConnection = DriverManager.getConnection("jdbc:fmpro:http://127.0.0.1:80");
Now I'm trying to use the drivers in a web application (CMP, session facade - much along the lines of Sun's Duke's Bank app) in the free J2EE server downloadable from Sun. When I try to 'Generate Default SQL' in the 'deployment settings' for the CMP that uses the driver (via JNDI), an error dialogue box displays "java.sql.SQL.Exception: Feature Not Supported". No default sql is generated.
This web app works all right with MySQL.
I was wondering if someone out there could offer some advice on how to interpret the error message.
Thanks.

Hi,
throw away ur jdbc driver.some standard jdbc methods (required by the
container) may be missing in your jdbc driver. refer vendor
documnets/faq on error messages and its expalanation.stick on the
database and driver which is giving u a satisfacory performance
(seems MySQL is working fine for u !).
HTH,
asharaf

Similar Messages

JDBC Adapter: J2EE server crashes while sending large messages

We want to use the following scenario to transfer data from a MS SQL Server to SAP BW via XI:
JDBC Sender Adapter XI SAP ABAP Proxy.
All works fine with a small amount of data. But if the select statement delivers too many record sets and the size of the transformed XML payload is greater then 50 MB the J2EE server crashes. A complete restart is necessary. It seems to be am memory problem.
Here are the entries from our log files:
dev_server0
[Thr 6151] Mon Jul 24 12:46:57 2006
[Thr 6151] JLaunchIExitJava: exit hook is called (rc=666)
[Thr 6151] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 940893 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 6151] SigISetIgnoreAction : SIG_IGN for signal 17
[Thr 6151] JLaunchCloseProgram: good bye (exitcode=666)
std_server0.out
FATAL: Caught OutOfMemoryError! Node will exit with exit code 666java.lang.OutOfMemoryError
Is this a general problem of the XI or a specific one of our configuration? Is it possible to transfer such large messages via XI? If not, is there a workaround for such scenarios?
(Memory heap size of the J2EE server is 1024 MB.)

> Hi Gil,
>
> i had nearly the same problems some times in praxis
> and the mapping was the reason. Just change your
> interface determination temporary, delete the mapping
> and test again to find out if the mapping is the
> reason.
>
> Regards,
> Udo
I have changed my interface determination so that no message mapping is used. The J2EE server still crashes.
> Hi Gil,
> This does sounds like a memory problem especially
> when it comes to 50M message with a minimum XI sys
> requierments...
> To be sure you can check on the RWB for the
> componnent monitoring at the JDBC adapters and look
> for your adapter
> look at the status of the adapter and the trace
> there...
Hi Nimrod
In case of such an error I have no entries in channel monitor. So I can't see anything there. I have also no entries in message monitor of the RWB in this case. So I don't get any information with standard XI tools.
> My reccomendation to you is to set the poll intervall
> to a shorter period,this way you'll make sure you get
> less records...I hope you have remembered to add a
> status/flag column on the table to be set after
> selection so no duplicate records will be taken on
> the second pools.
>
The problem is that the source of my data is not a simple SQL statement but a stored procedure. So I don't know exactly how many records will be delivered. A update command is not possible.

Initialising class when J2EE server starts

Hi,
I am facing a problem. I wish to instantiate a class when the J2EE/ tomcat server starts. This is similar to the property set in weblogic as
weblogic.system.startupClass.startup = <name of ur startup class>
Here we can specifiy the class to be instantiated during startup of server.
Can i do something similar in tomcat/ j2ee server?
I do not wish to use a servlet since my webapplication contains jsps and other supporting classes and my own apis.
Thank you in adv.
...supriya.

if you use ServletContext Listeners you should be ready as far as web app is concerned. Most servers I believe offer JMX integration so that you can listen for server startups. : )

Tomcat web context with j2ee server

Hi everybody!
Can anyone tell me how to add a web context to tomcat when it is running with j2ee server, since it no longer reads the ./conf/server.xml file.
Thank you.

Hi!
Sun's J2sdkee1.3 is built on tomcat server. When tomcat is started up by j2sdkee it doesn't load (or ignores) the ./conf/server.xml file where should be defined the web context used by tomcat, like:
<Context path="/examples" docBase="D:/path/to/examples"
debug="0"
reloadable="true"
trusted="true" >
</Context>
And I cannot find a way to add a context which has a different document base as the one defined in the ./config/web.properties
thanks.

Problem in jdbc-tomcat-mysql connection

hi everybody
i m in serious problem since last 15-20 days. i m trying hard to make the connection jdbc-mysql using tomcat with the help of a jsp test page but every time i am facing almost the similar probems listed below in detail:
to make sure that the jdrivers's .jar (mysql-connector-java-3.1.7-bin.jar) available for such connections working fine i have tried the above said connection without using tomcat....which is working fine...for this i have created a dummy database with a dummy table ..and written some queries in the .java file of my code which upon running inserts the specified values in the defined(dummy) database.
this is the confirmation that the classpath etc..are ok in regard to the mysql-connector-java-3.1.7-bin.jar
now i have placed a copy of this .jar file in to the commons/lib directory of the tomcat web server(which is suppossed to be the place for such external jars)
after doing so i have followed 2 methods :
method 1st:........
i have made aone more jar file from the following .java file....
import javax.naming.*;
import javax.sql.*;
import java.sql.*;
public class TestSQLLoad
String user = "Not Connected";
String pwd = "no pwd";
int id = -1;
public void init() {
try{
Context ctx = new InitialContext();
if(ctx == null ) {
throw new Exception("Boom - No Context");
DataSource ds = (DataSource)ctx.lookup("java:comp/env/jdbc/TestDB");
if (ds != null) {
Connection conn = ds.getConnection();
if(conn != null) {
user = "Got Connection "+conn.toString();
Statement stmt = conn.createStatement();
String q = "select name, password, id from user";
ResultSet rst = stmt.executeQuery(q);
if(rst.next()) {
user=rst.getString(1);
pwd=rst.getString(2);
id = rst.getInt(3);
conn.close();
}catch(Exception e) {
e.printStackTrace();
public String getUser() {
return user;
public String getPassword() {
return pwd;
public int getID()
return id;
after compiling it at the cmd prompt i made a .jar file from the .class of it and named it MySQLLoad.jar...then i placed it also in to the commons/lib directory where the mysql-connector-java-3.1.7-bin.jar was already placed.
then i have changed the server.xml and web.xml files from the conf directory of the tomcat as given here:
server.xml



<Server port="8005" shutdown="SHUTDOWN">

<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />

<GlobalNamingResources>

<Environment name="simpleValue" type="java.lang.Integer" value="30"/>

<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml" />
</GlobalNamingResources>


<Service name="Catalina">


<Connector
port="80" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />

     



<Connector port="8009"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />






<Engine name="Catalina" defaultHost="localhost">




<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>







<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">









<Context path="/testdb" docBase="TOMCAT_HOME/webapps/tomcat-docs/testdb"
debug="5" reloadable="true" crossContext="true" >
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_DBTest_log." suffix=".txt"
timestamp="true"/>
<Resource name="jdbc/TestDB"
auth="Container"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/TestDB">
<parameter>
<name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>

<parameter>
<name>maxActive</name>
<value>10</value>
</parameter>

<parameter>
<name>maxIdle</name>
<value>5</value>
</parameter>

<parameter>
<name>maxWait</name>
<value>10000</value>
</parameter>

<parameter>
<name>username</name>
<value>root</value>
</parameter>
<parameter>
<name>password</name>
<value>mysql</value>
</parameter>

<parameter>
<name>driverClassName</name>
<value>com.mysql.jdbc.Driver</value>
</parameter>

<parameter>
<name>url</name>
<value>jdbc:mysql://localhost/testdb?autoReconnect=true</value>
</parameter>
</ResourceParams>
</Context>
</Host>
</Engine>
</Service>
</Server>
and the other xml file i.e
web.xml is here:
<?xml version="1.0" encoding="ISO-8859-1"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">
















































<servlet>
<servlet-name>default</servlet-name>
<resource-ref>
<description>DB Connection</description>
<res-ref-name>jdbc/TestDB</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<servlet-class>org.apache.catalina.servlets.DefaultServlet</servlet-class>
<init-param>
<param-name>debug</param-name>
<param-value>0</param-value>
</init-param>
<init-param>
<param-name>listings</param-name>
<param-value>true</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>












<servlet>
<servlet-name>invoker</servlet-name>
<servlet-class>
org.apache.catalina.servlets.InvokerServlet
</servlet-class>
<init-param>
<param-name>debug</param-name>
<param-value>0</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>










<!--

Look at the URl below:
How to connect to Microsoft SQL server with Type 4 JDBC driver
http://www.java-tips.org/content/view/615/29/

Error starting J2EE server

I have recently installed the J2EE SDK 1.3.1 and J2SE SDK 1.4.1_02. Upon starting the j2ee server (j2ee -verbose), get the following error message.
Exception in thread "main" java.lang.ExceptionInInitializerError
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:175)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
Caused by: java.lang.NullPointerException
at java.net.InetAddress.cacheAddress(InetAddress.java:648)
at java.net.InetAddress.cacheAddress(InetAddress.java:633)
at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1016)
at java.net.InetAddress.getLocalHost(InetAddress.java:1125)
at com.sun.enterprise.util.Utility.getLocalHost(Utility.java:56)
at com.sun.enterprise.repository.ConfigurationImpl.<clinit>(ConfigurationImpl.java:18)
... 2 more
I am running Linux 7.2, Apache 1.3.27, Tomcat 4.1.24., and have two (2) NICs.
Any ideas on what might cause this issue?

I believe I got the server working. The system may have had an issue recognizing the environmental variables being set in the .bash_profile and the setconfig.sh.
If anyone could clarify the errors above, I would greatly appreciate the information.
J2EE server listen port: 1050
Naming service started:1050
Binding DataSource, name = jdbc/DB1, url = jdbc:cloudscape:rmi:CloudscapeDB;create=true
Binding DataSource, name = jdbc/DB2, url = jdbc:cloudscape:rmi:CloudscapeDB;create=true
Binding DataSource, name = jdbc/InventoryDB, url = jdbc:cloudscape:rmi:CloudscapeDB;create=true
Binding DataSource, name = jdbc/Cloudscape, url = jdbc:cloudscape:rmi:CloudscapeDB;create=true
Binding DataSource, name = jdbc/EstoreDB, url = jdbc:cloudscape:rmi:CloudscapeDB;create=true
Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
Binding DataSource, name = jdbc/XACloudscape__xa, dataSource = COM.cloudscape.core.RemoteXaDataSource@1c208b0
Starting JMS service...
Initialization complete - waiting for client requests
Binding: < JMS Destination : jms/Queue , javax.jms.Queue >
Binding: < JMS Destination : jms/Topic , javax.jms.Topic >
Binding: < JMS Cnx Factory : QueueConnectionFactory , Queue , No properties >
Binding: < JMS Cnx Factory : jms/QueueConnectionFactory , Queue , No properties
>
Binding: < JMS Cnx Factory : jms/TopicConnectionFactory , Topic , No properties
>
Binding: < JMS Cnx Factory : TopicConnectionFactory , Topic , No properties >
Starting web service at port: 8000
Starting secure web service at port: 7000
J2EE SDK/1.3.1
Starting web service at port: 9191
J2EE SDK/1.3.1
J2EE server startup complete.

Can't start J2EE server :o(

Hi,
I'm getting started with J2EE but I can't start the J2EE server. I have to point out that I read the instructions in J2EE Tutorial 1.3 but I use J2EE SDK 1.4 Beta.. But it should work, shouldn't it??? I don't expect the problem to be very serious but I'm a greener and can't solve it myself :oI
Thanks a lot for every hint and sorry for my not very good English :o)
Dojcland
Here are the "printStackTraces" I get:
(The last line you can see is the last one that appears. Never "C:\" again. If I close the window "Stopping J2EE server" message appears before the window is closed.)
C:\>j2ee -stop
Shutting down the J2EE server.
Unable to shutdown the J2EE server.
C:\>cleanup
This will delete all deployed applications and clean all log files
Do you want to proceed (y/n)
y
Cleaning directory C:\j2sdkee1.4\logs ...
Cleaning directory C:\j2sdkee1.4\repository ...
Cleaning directory C:\j2sdkee1.4\connector\adapters ...
Cleaning directory C:\j2sdkee1.4\public_html ...
Cleaning directory C:\WINNT\TEMP\j2ee-ri-Dojcland ...
Cleaning directory C:\j2sdkee1.4\web\repository ...
Cleanup completed. Please restart j2ee server.
C:\>j2ee -verbose
J2EE server listen port: 1050
Naming service started: 1050
Binding DataSource, name = jdbc/DB1, url =
jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/EstoreDB, url =
jdbc:cloudscape:rmi:CloudscapeDB
;create=true
Binding DataSource, name = jdbc/InventoryDB, url =
jdbc:cloudscape:rmi:Cloudscap
eDB;create=true
Binding DataSource, name = jdbc/DB2, url =
jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/Cloudscape, url =
jdbc:cloudscape:rmi:Cloudscape
DB;create=true
Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
Binding DataSource, name = jdbc/XACloudscape__xa, dataSource =
COM.cloudscape.co
re.RemoteXaDataSource@119e583
Binding DataSource, name = jdbc/_ejb_container, url = jdbc/_ejb_container__xa
Binding DataSource, name = jdbc/_ejb_container__xa, dataSource =
COM.cloudscape.
core.XaDataSource@b05236
Starting JMS service...
Initialization complete - waiting for client requests
Starting JMS via Resource Adapter
Deploying jmsra.rar in C:\j2sdkee1.4\lib\system_apps\jmsra.rar
org.w3c.dom.DOMException: DOM003 Namespace error
at org.apache.xerces.dom.AttrNSImpl.<init>(AttrNSImpl.java:129)
at
org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(CoreDocument
Impl.java:1422)
at
org.apache.xerces.dom.ElementImpl.setAttributeNS(ElementImpl.java:596
at
com.sun.enterprise.deployment.node.DeploymentDescriptorNode.setAttrib
ute(DeploymentDescriptorNode.java:501)
at
com.sun.enterprise.deployment.node.LocalizedNode.writeLocalizedMap(Lo
calizedNode.java:65)
at
com.sun.enterprise.deployment.node.DisplayableComponentNode.writeDisp
layableComponentInfo(DisplayableComponentNode.java:56)
at
com.sun.enterprise.deployment.node.BundleNode.writeDescriptor(BundleN
ode.java:104)
at
com.sun.enterprise.deployment.node.connector.ConnectorNode.writeDescr
iptor(ConnectorNode.java:210)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.getDocument(J2
EEDocumentBuilder.java:77)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocu
mentBuilder.java:120)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToSt
ring(J2EEDocumentBuilder.java:153)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModuleAndItsComponents(J2EEManagementObjectManager.java:408)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModule(J2EEManagementObjectManager.java:203)
at
com.sun.enterprise.resource.ResourceInstaller.installSystemResourceAd
apter(ResourceInstaller.java:706)
at com.sun.enterprise.jms.JmsUtil.startJmsService(JmsUtil.java:236)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:239)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
java.lang.IllegalArgumentException: The input node can not be null for a
DOMSour
ce for newTemplates!
at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:346)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocu
mentBuilder.java:125)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToSt
ring(J2EEDocumentBuilder.java:153)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModuleAndItsComponents(J2EEManagementObjectManager.java:408)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModule(J2EEManagementObjectManager.java:203)
at
com.sun.enterprise.resource.ResourceInstaller.installSystemResourceAd
apter(ResourceInstaller.java:706)
at com.sun.enterprise.jms.JmsUtil.startJmsService(JmsUtil.java:236)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:239)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
Exception stringifying deployment descriptor
java.lang.IllegalArgumentException: The input node can not be null for a
DOMSour
ce for newTemplates!
at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:346)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocu
mentBuilder.java:125)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToSt
ring(J2EEDocumentBuilder.java:153)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModuleAndItsComponents(J2EEManagementObjectManager.java:408)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModule(J2EEManagementObjectManager.java:203)
at
com.sun.enterprise.resource.ResourceInstaller.installSystemResourceAd
apter(ResourceInstaller.java:706)
at com.sun.enterprise.jms.JmsUtil.startJmsService(JmsUtil.java:236)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:239)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
ResourceAdapter jmsra.rar started...
Initializing Coyote HTTP/1.1 on port 8000
Initializing Coyote HTTP/1.1 on port 7000
Loaded registry information 3275 ms
Starting service J2EE(TM) Web Server
Apache Tomcat/5.0
Missing application web.xml, using defaults only
StandardEngine[Standard-Engine]
.StandardHost[localhost].StandardContext[]
Added certificates -> request attribute Valve
Starting Coyote HTTP/1.1 on port 8000
Starting Coyote HTTP/1.1 on port 7000
JACC:Policy Repository set to C:\j2sdkee1.4\repository\policy
Added certificates -> request attribute Valve
Configured an authenticator for method FORM
J2EE Web Admin Tool started
JAXR:Installing JAXR RA
Deploying jaxr-ra.rar in C:\j2sdkee1.4\lib\system_apps\jaxr-ra.rar
org.w3c.dom.DOMException: DOM003 Namespace error
at org.apache.xerces.dom.AttrNSImpl.<init>(AttrNSImpl.java:129)
at
org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(CoreDocument
Impl.java:1422)
at
org.apache.xerces.dom.ElementImpl.setAttributeNS(ElementImpl.java:596
at
com.sun.enterprise.deployment.node.DeploymentDescriptorNode.setAttrib
ute(DeploymentDescriptorNode.java:501)
at
com.sun.enterprise.deployment.node.LocalizedNode.writeLocalizedMap(Lo
calizedNode.java:65)
at
com.sun.enterprise.deployment.node.DisplayableComponentNode.writeDisp
layableComponentInfo(DisplayableComponentNode.java:57)
at
com.sun.enterprise.deployment.node.BundleNode.writeDescriptor(BundleN
ode.java:104)
at
com.sun.enterprise.deployment.node.connector.ConnectorNode.writeDescr
iptor(ConnectorNode.java:210)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.getDocument(J2
EEDocumentBuilder.java:77)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocu
mentBuilder.java:120)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToSt
ring(J2EEDocumentBuilder.java:153)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModuleAndItsComponents(J2EEManagementObjectManager.java:408)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModule(J2EEManagementObjectManager.java:203)
at
com.sun.enterprise.resource.ResourceInstaller.installSystemResourceAd
apter(ResourceInstaller.java:706)
at com.sun.enterprise.jaxr.JaxrUtil.installJaxrRA(JaxrUtil.java:40)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:278)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
Exception stringifying deployment descriptor
java.lang.IllegalArgumentException: The input node can not be null for a
DOMSour
ce for newTemplates!
at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:346)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocu
mentBuilder.java:125)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToSt
ring(J2EEDocumentBuilder.java:153)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModuleAndItsComponents(J2EEManagementObjectManager.java:408)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModule(J2EEManagementObjectManager.java:203)
at
com.sun.enterprise.resource.ResourceInstaller.installSystemResourceAd
apter(ResourceInstaller.java:706)
at com.sun.enterprise.jaxr.JaxrUtil.installJaxrRA(JaxrUtil.java:40)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:278)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
java.lang.IllegalArgumentException: The input node can not be null for a
DOMSour
ce for newTemplates!
at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:346)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocu
mentBuilder.java:125)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToSt
ring(J2EEDocumentBuilder.java:153)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModuleAndItsComponents(J2EEManagementObjectManager.java:408)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModule(J2EEManagementObjectManager.java:203)
at
com.sun.enterprise.resource.ResourceInstaller.installSystemResourceAd
apter(ResourceInstaller.java:706)
at com.sun.enterprise.jaxr.JaxrUtil.installJaxrRA(JaxrUtil.java:40)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:278)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
Binding Connection Factory, name = QueueConnectionFactory
Binding Connection Factory, name = jms/TopicConnectionFactory
Binding Connection Factory, name = jms/QueueConnectionFactory
Binding Connection Factory, name = TopicConnectionFactory
Binding Connection Factory, name = eis/JAXR
Binding Administered Object, name = jms/Topic
Binding Administered Object, name = jms/Queue
Starting EJB Timer Service...
J2EE server startup complete.

Check another similar question in the same forums.. I have posted an answer there. Hopefully that should work for you.

Having trouble starting the J2EE Server... for hours and hours...

Hi:
I am having problem starting the J2EE Server.
I have looked through this page where lots of people had similar problem:
http://forum.java.sun.com/thread.jsp?forum=136&thread=468079
but the solutions provided there could not solve my problem...
My problem, specifically, is that when I try to start the sever, I get:
com.sun.enterprise.admin.servermgmt.DomainException: ...
CLI156 Could not start the domain domain1.
I am using Windows XP Professional on IBM ThinkPad X30.
Does anyone have some idea how to solve the problem?
Thanx!

bsankararao,
Thanks for the quick response. I am currently using the latest IE6.0 XPXP2 version and yes I doe have a successful start of the domain1 process. Here is the startup log for verification:
[#|2004-02-02T15:03:04.765-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-02T15:03:12.246-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-02T15:03:12.436-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-02T15:03:14.649-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-02T15:03:15.470-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-02T15:03:15.491-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-02T15:03:15.521-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-02T15:03:32.084-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-02T15:03:34.338-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-02T15:03:34.938-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-02T15:03:36.391-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-02T15:03:36.421-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|autoDeployment status dir missing, creating a new one|#]
[#|2004-02-02T15:03:36.451-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [D:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2004-02-02T15:03:36.471-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-02-02T15:03:36.481-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2004-02-02T15:03:38.043-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2004-02-02T15:03:38.203-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5108: EJBC - Generated code for remote home and EJBObject implementations for [MEjbApp]|#]
[#|2004-02-02T15:03:48.818-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2004-02-02T15:03:49.549-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 12728 msec, Total EJB Compiler Module Time: 10775 msec, Portion spent EJB Compiling: 84%
Breakdown of EJBC Module Time: Total Time for EJBC: 10775 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 10605 msec (98%), JAX-RPC Generation: 20 msec (0%),
|#]
[#|2004-02-02T15:03:49.750-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2004-02-02T15:03:50.571-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-02-02T15:03:51.292-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.029-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.309-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5688 msec, Total EJB Compiler Module Time: 4737 msec, Portion spent EJB Compiling: 83%
Breakdown of EJBC Module Time: Total Time for EJBC: 4737 msec, CMP Generation: 2674 msec (56%), Java Compilation: 1933 msec (40%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2004-02-02T15:03:56.339-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-02-02T15:03:56.810-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-02T15:03:57.210-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-02T15:03:57.461-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-02T15:03:57.521-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-02T15:03:57.571-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-02T15:03:57.571-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-02T15:03:57.721-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-02T15:03:59.924-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-02T15:04:00.315-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-02T15:04:00.355-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-02T15:04:00.936-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-02T15:04:00.946-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-02T15:04:00.966-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-02T15:04:00.986-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-02T15:04:01.266-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075755841276|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-02T15:18:13.512-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T15:18:13.522-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T15:18:39.119-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T15:18:39.119-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T19:27:40.443-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T19:27:41.174-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T19:27:49.076-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T19:27:49.076-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T19:31:57.022-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T19:31:57.022-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T19:32:08.869-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T19:32:08.869-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T20:00:22.424-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T20:00:22.424-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-03T08:30:22.556-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T08:30:23.808-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T08:30:23.998-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T08:30:26.422-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T08:30:27.143-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T08:30:27.203-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T08:30:27.253-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T08:30:31.509-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T08:30:33.462-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T08:30:33.963-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T08:30:34.914-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T08:30:36.036-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T08:30:36.877-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T08:30:36.877-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T08:30:37.027-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T08:30:37.428-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T08:30:37.618-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T08:30:37.638-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T08:30:37.668-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T08:30:37.668-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T08:30:37.798-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T08:30:39.901-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T08:30:40.202-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T08:30:40.242-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T08:30:40.402-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T08:30:40.412-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T08:30:40.442-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T08:30:40.452-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T08:30:40.732-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075818640752|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-03T08:48:32.383-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\domains\domain1\autodeploy\hello.war ] for autodeployment.|#]
[#|2004-02-03T08:48:33.785-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [hello]|#]
[#|2004-02-03T08:48:33.835-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [hello]|#]
[#|2004-02-03T08:48:34.606-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 1862 msec, Total EJB Compiler Module Time: 50 msec, Portion spent EJB Compiling: 2%
Breakdown of EJBC Module Time: Total Time for EJBC: 50 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 10 msec (20%),
|#]
[#|2004-02-03T08:48:34.807-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/hello]|#]
[#|2004-02-03T08:48:35.007-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T08:48:36.719-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-03T08:48:36.729-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\domains\domain1\autodeploy\hello.war.|#]
[#|2004-02-03T14:53:47.246-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T14:53:48.718-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T14:53:48.929-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T14:53:51.222-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T14:53:52.003-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T14:53:52.033-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T14:53:52.043-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T14:53:56.449-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T14:53:58.492-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T14:53:58.983-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T14:53:59.985-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T14:54:01.206-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T14:54:02.048-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T14:54:02.048-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T14:54:02.188-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T14:54:02.678-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T14:54:02.899-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T14:54:02.919-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T14:54:02.939-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T14:54:02.989-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T14:54:02.989-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T14:54:03.119-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T14:54:05.563-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T14:54:05.883-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T14:54:05.943-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T14:54:06.083-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T14:54:06.093-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T14:54:06.123-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T14:54:06.133-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T14:54:06.424-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075841646434|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-03T23:32:20.272-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T23:32:22.004-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T23:32:22.234-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T23:32:24.608-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T23:32:25.629-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T23:32:25.659-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T23:32:25.689-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T23:32:31.237-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T23:32:33.781-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T23:32:34.332-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T23:32:35.453-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T23:32:37.156-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T23:32:38.137-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T23:32:38.137-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T23:32:38.317-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T23:32:38.948-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T23:32:39.179-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T23:32:39.199-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T23:32:39.229-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T23:32:39.269-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T23:32:39.269-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T23:32:39.439-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T23:32:42.343-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T23:32:42.724-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T23:32:42.764-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T23:32:42.944-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T23:32:42.954-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T23:32:42.994-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T23:32:43.014-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T23:32:43.315-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075872763335|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-04T08:31:44.681-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02

Oracle 8i jdbc/Tomcat connection issues

Tomcat 4.1.8
Oracle 8i JDBC Driver
I have been able to create the DataSource as a global resource and as a local resource inside the context of the application.
The code hangs when it attempts to create a connection. I have been able to connect to the database and perform the necessary query in a standalone application to ensure that I actually can connect.
JSP Code:
<html>
<head>
<title>VTW App</title>
</head>
<body>
<%
vtw.VTWApp tst = new vtw.VTWApp();
tst.init();
%>
<h2>Results</h2>
<%= tst.getList() %>
</body>
</html>
Java Code (Class called by JSP):
package vtw;
import javax.naming.*;
import javax.sql.*;
import java.sql.*;
public class VTWApp {
String list = "EMPTY";
public void init() {
try{
Context ctx = new InitialContext();
if(ctx == null )
throw new Exception("Boom - No Context");
System.out.println("Context Created ...");
DataSource ds =
(DataSource)ctx.lookup(
"java:comp/env/jdbc/oracleDB");
if (ds != null) {
          System.out.println("DataSource Created ...");
Connection conn = ds.getConnection();
System.out.println("Connection Pulled");
if(conn != null) {
               System.out.println("Connection Good");
               Statement st = conn.createStatement();
               String query = "";
               query += "select grpid, to_char(min(dtlastendtime),'mm-dd-yyyy hh24:mi:ss') ";
               query += "from calc_table where equipmentsernum in (";
               query += "'888000','888001'";
               query += ") group by grpid";
               ResultSet rs = st.executeQuery(query);
               if(rs != null) {
                    list = "";
                    while(rs.next()) {
                         list += (rs.getString(1) + "," + rs.getString(2));
               rs.close();
               conn.close();
               System.out.println("Connection Closed");
          } else {
               System.out.println("Connection Not Established");
}catch(Exception e) {
e.printStackTrace();
public String getList() { return list; }
}

I figured out the issue ...
In the server.xml file the resource & resource params needed to be modified..
1. Set type to oracle.jdbc.pool.OracleDataSource
2. Set factory to oracle.jdbc.pool.OracleDataSourceFactory
3. In the Java code cast the context lookup to an OracleDataSource instead of a java.sql.DataSource
Oracles DataSource does not subclass the jdbc DataSource for its OracleDataSource class everything works fine now.
<Resource name="jdbc/mydb" scope="Shareable" type="oracle.jdbc.pool.OracleDataSource"/>
<ResourceParams name="jdbc/mydb">
<parameter>
<name>validationQuery</name>
<value></value>
</parameter>
               <parameter>
                    <name>factory</name>
                    <value>oracle.jdbc.pool.OracleDataSourceFactory</value>
               </parameter>
<parameter>
<name>driverClassName</name>
<value>oracle.jdbc.driver.OracleDriver</value>
</parameter>
<parameter>
     <name>url</name>
     <value>jdbc:oracle:thin:@server.company.com:1521:dbname</value>
</parameter>
<parameter>
<name>password</name>
<value>guest</value>
</parameter>
               <parameter>
                    <name>maxWait</name>
                    <value>10000</value>
               </parameter>
               <parameter>
                    <name>maxActive</name>
                    <value>100</value>
               </parameter>
<parameter>
<name>user</name>
<value>guest</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>2</value>
</parameter>
</ResourceParams>

Starting the J2EE server

Hi:
I am new to J2EE and I followed the instruction on the J2EE Tutorial setting up the J2EE SDK. When I tried to start the J2EE server by typing in "C:\j2ee -verbose", the server can't seem to start... After it gets to "Starting JMS service..." , it jumps back to the command prompt "C:\>"
If I then try to do a "j2ee -stop", I get an error "javax.naming.CommunicationException: Can't find SerialContextProvider" (which, I think, indicates the server never got started)
I am using Windows 2000 and I am pretty sure I have the environment variables set properly. Does anyone know why this is happening? Thanx!
The following is the trace of me doing "j2ee -verbose"
J2EE server listen port: 1050
Naming service started:1050
Binding DataSource, name = jdbc/DB1, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/EstoreDB, url = jdbc:cloudscape:rmi:CloudscapeDB
;create=true
Binding DataSource, name = jdbc/Cloudscape, url = jdbc:cloudscape:rmi:Cloudscape
DB;create=true
Binding DataSource, name = jdbc/InventoryDB, url = jdbc:cloudscape:rmi:Cloudscap
eDB;create=true
Binding DataSource, name = jdbc/DB2, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
Binding DataSource, name = jdbc/XACloudscape__xa, dataSource = COM.cloudscape.co
re.RemoteXaDataSource@b301f2
Starting JMS service...
C:\j2sdkee1.3.1\bin>
Eugene

I have read some posts and get the answer
change the pc language to English
and reinstall j2ee
all should be ok!
I get message "J2EE server startup complete" now.
luck!

Need help:Urgent:MS SQL Server and J2EE Server

Hello,
i am developing simple bean managed persistence bean. i want to know how could i use microsoft SQL Server as my database with ejb's in J2EE. i don't want to use cloudscape rather i want to connect through jdbc bridge with sql server. can any body help me out ?
i have developed DSN for my database with the name of DsnProduct and user name for DB is guest and password is guest123.
so do i have to change configuration is my J2EE server . or put some additional code. so far i have added the following line in my implementation class
private String dbName= "java:comp/env/jdbc/ProductDB";
DataSource ds = (DataSource) ic.lookup(dbName);
con = ds.getConnection("guest","guest123");
moreover in server configuration i have added driver
sun.jdbc.odbc.JdbcOdbcDriver
and also provide the following JNDI Name
jdbc/ProductDB
and
it's url is
jdbc:odbc:DsnProduct
i am thankfull for your support.
[email protected]

hi llturro,
Thanks for answering my question. I have tried out what you suggested, but I still can't fix my problem. The following are the messages that display when I try to run my servlet. It seems that the DataSource, Connection and Statement are ok, however when it comes to the ResultSet the error message appear. What's wrong with my ResultSet coding ?
ResultSet rs = stat.executeQuery("SELECT ISBN FROM BOOKSINFO WHERE ISBN='"+primarykey+"'");
setEntityContext Method
Find by primary key
DataSource OK
Connection OK
Primary Key = 013-00-675721-9
Statement OK
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Unknown Exception/Error thrown by EJB method.; nested exception is:
java.lang.NullPointerException
java.rmi.RemoteException: Unknown Exception/Error thrown by EJB method.; nested exception is:
java.lang.NullPointerException
java.lang.NullPointerException
<<no stack trace available>>

J2EE server error,deploytool error

Dear All,
I had downloaded the J2EESDK1.3 and jakarta-ant1.4.1 and the J2SESDK1.3.0_02 from their respective websites.I set the value of the required environment variables i.e the J2EE_HOME, JAVA_HOME and the ANT_HOME to their respective location in my 'C' drive.But I find that when I try to start the J2EE server, the error "Out of environment space" appears in the MSDOS screen.The same error is also visible when I type the following command - "deploytool" at the DOS prompt. Would be grateful if you could please guide me as to what the problem might be and what is the solution to it.Thanks all.
Ramesh Rangarajan

Hi Amol,
Here is the content of my J2EE.bat file:
@echo off
rem
rem Set JAVA_HOME and J2EE_HOME before running this script.
rem
rem set JAVA_HOME to the path where you have Java 2 (JDK1.2) installed.
rem
rem set J2EE_HOME to the path where you have installed this package (EJB server).
rem
if not "%J2EE_HOME%" == "" goto CONT0
echo ERROR: Set J2EE_HOME before running this script.
goto END
:CONT0
if EXIST "%J2EE_HOME%\bin\setenv.bat" goto CONT1
echo ERROR: Set J2EE_HOME to the path of a valid j2sdkee.
goto END
:CONT1
call %J2EE_HOME%\bin\setenv.bat
if not "%JAVA_HOME%" == "" goto CONT2
echo ERROR: Set JAVA_HOME before running this script.
goto END
:CONT2
if EXIST "%JAVA_HOME%\bin\java.exe" goto CONT3
echo ERROR: Set JAVA_HOME to the path of a valid jdk.
goto END
:CONT3
rem @echo on
%JAVACMD% %LISTEN_OPTIONS% -Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter -Dorg.xml.sax.driver=org.apache.crimson.parser.XMLReaderImpl -Djms.home=%JMS_HOME% -Dcom.sun.jms.service.jdbc.dbpath=%JMS_DB_PATH% -Djms.properties=%J2EE_HOME%\config\jms_service.properties -Djava.security.policy==%J2EE_HOME%\lib\security\server.policy -Djava.security.auth.login.config=%J2EE_HOME%\lib\security\login.config -Dcom.sun.enterprise.home=%J2EE_HOME% -classpath %CPATH% com.sun.enterprise.server.J2EEServer %*
:END
Ramesh Rangarajan

How to establish a trusted connection with JDBC for SQL SERVER 2000

Hi!I am using jdk 1.4 and eclipse 3.3.
I create a servlet in eclipse with in-build tomcat.
When I run it ,it was working perfectlly has it was suppose to work.
In this servlet I connect to a sql 2000 database using jdbc-odbc bridge driver.
But when I tried to deploy the servlet on tomcat 5.5 manully on the same machine ,it gave me error saying
[Microsoft][SQLServer JDBC Driver][SQLServer]Login failed
for user 'sa'
I searched around some post and found that ok ,I need trusted connection
But I have 2 Questions
1). Why was in eclipse I was able to connect to the SQL server and why not in the servlet which I deployed manully on tomcat.
2). How do I create a trusted connection with JDBC for SQL server 2000
Thnaks for your help in advance.

Hi! duffymo ,QussayNajjar ,dvohra09 .
Thank for help.
The ideas are really great.
I am trying generate reports for my company.
When I used eclipse the code worked perfectly.
below is code which I used
out.println("Calling For Class Name<br>");
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
out.println("Calling For Class Name success Now calling database <br>");
1). jdbcConnection = DriverManager.getConnection("jdbc:odbc:SQLJasper");
2). jdbcConnection = DriverManager.getConnection("jdbc:odbc:Driver={SQL Server};Server=ServerName;Database=tempdb");
3). jdbcConnection = DriverManager.getConnection("jdbc:odbc:Driver={SQL Server};Server=ServerName;Database=tempdb","UID=UserName","Password=Password");
out.println("connecting to database success<br>");
I had tried to connect the database using this three way.
In 1st I tried using DSN name .
Next 2 self explainer for expert like you.
I used to 2nd variant to connect in eclipse and it worked fine.
I not an expert in java ,I just doing some research on jasperReport.
My best guest is that eclipse is using some library files of which I have no clue.
Thank's for your help,I appretiate it.
Once again thank a billion.
Sorry for the messy righting.

Configure J2EE Server in FB4 beta

Hi,
I think, there are very serious problems with J2EE deployment in FB4 beta2.
1) Can not change or add or delete anything in "Target Runtime".
New button and "Show all runtimes" checkbox don't do anything.   "New" button gets disabled and no way to re-enable it.
Can't unistall Facets either.
Imported my Flex project from FB3. It produced error: "Target Runtime JBoss 5.0 not defined".
So I am going to project Properties/Target Runtime to remove old one and add a "new" JBoss 5.0.
Nothing works (see #1).
2) OK, trying to create a new Flex project, going through Create Flex project wizard.
On page "Configure J2EE Server" it is expecting Server location with existing WEB-INF/flex folder containing flex-config.xml or services-config.xml
But from where, some other existing project ?
Plus, JBoss5 forces you to work with non-exploded archives (WAR, JAR, etc)
How do you resolve that one ?
Am I missing something ?   Or is FB4 beta2 is completely unusable with JBoss 5.1 ?
Is there beta3 or nightly build where it is fixed ?
Please help !
TIA,
Oleg.

Still no solution to that problem ?
Say, I am developing an AIR2 app which has some Java part to it (remoting, Web Service, whatever),
with or without BlazeDS (or LCDS). Anything requiring Web Server (J2EE / servlet container).
How do I add new Server to FB4 beta2 ? Lets say Tomcat 6 or JBoss 5.1.
If I go to Preferences->Server->Runtime Environments, there is only one selection - J2EE Runtime Library (what is that?)
OK, I click Add, then link Download additional server adapters, and in a few seconds prompts for login/pwd for SAP Community Network.
I don't know any... so after I click Cancel, I can only choose Geronimo, GlassFish, Jetty, Weblogic, WASCE.
No Tomcat, No JBoss ?   Nothing like a long selection list in FB3 ?
Search for server runtime environments stops right away.   FB3 can find a dosen ones on my hard disk.
Is it a major hole in FB4 beta2 ?
Makes it pretty useless to me... :-(
Please advise !
Thanks,
Oleg.
Message was edited by: olegkon
Message was edited by: olegkon

How to connect Mysql to J2EE server exactly?

Hi,there
I would like thank you for offering me your precious opinion in advance.
I got a problem with installing Mysql database into J2EE server. All I have done is:
1.Install Mysql and put the Mysql driver,mm.mysql-2.0.4-bin.jar into the directory of J2EE which is j2ee1.3.1/lib.
2. Set the environment variable for invoking the Mysql driver like
this,CLASSPATH=.;%JAVA_HOME%\lib\mysql-connector-java-2.0.14-bin;%
J2EE_HOME%\lib\mysql-connector-java-2.0.14-bin;%JAVA_HOME%\bin;
3.Modify the content of Server.xml file located in J2EE directory like this:
<DefaultContext>
<Resource name="jdbc/mysql" auth="Container"
type="javax.sql.DataSource" />
<ResourceParams name="jdbc/mysql">
<parameter>
<name>driverClassName</name>
<value>org.gjt.mm.mysql.Driver</value>
</parameter>
<parameter>
<name>drivername</name>
<value>jdbc:mysql:localhost:3306:mobiledb</value>
</parameter>
</ResourceParams>
</DefaultContext>
So far,I have no success in connect Mysql to J2EE server. What am I doing wrong?
Thank you for your kind help.

hi, sameer
Thank you for reply. Could you tell me exactly the documents that you see? Do you mean "J2EE tutorial documents"?
Thanks for advice.
Revon

JDBC, Tomcat, J2EE server

Similar Messages

Maybe you are looking for