Deploytool

Hi all,
deploytool is used in the tutorial for JWSDP 1.0 and included with the pack, and is also used in some books (e.g. Java Web Services by Deitel et al). It doesn't appear to be included in the current release JWSDP 1.1 and is not mentioned in the Java Web Services Tutorial which accompanies JWSDP 1.1.
Is there a reason for not using deploytool?

Hi,
I can tell you a reason why it is better not to use the deploytool
for the J2EE 1.4 RI Server. It causes many problems like the often
posted missing JNDI-Tab. It is better to use Ant to deploy your
Applications. I tried out the deploytool, because I was not familar
with Ant. I can tell you, it is faster to learn about Ant than wasting
your Time with deploytool Bugs.

Similar Messages

Error occured while creating WAR using DeployTool

Hi,
I am creating a webservice application. I used JAXB to create JAVA implementation of my XML schema. My webservice core is based on JAVA servlets. I have included all required JAXB API / implementation JARs into the lib directory. When I try to proceed from "Choose Component Type" screen in DeployTool I get the following error:
Unable to load servlet class specified in module.
Please consult online help for assistance.
java.lang.ClassNotFoundException: jp/co/swiftinc/relax/verifier/RELAXErrorHandler
I tried to search this file locally and on internet but couldn't find. Please help me how to avoid this problem during creation of war file. Thanx
Regards,
Yasir Khan

Hi Yasir,
remove the jaxb.jar from the WEB_INF/lib and move
them to your SUNWappserv/lib/endorsed - dir, together
with the following jars:
dom.jar jaxb-api.jar jaxb-impl.jar jaxb-libs.jar
jaxb-xjc.jar namespace.jar relaxngDatatype.jar
r xalan.jar
xercesImpl.jar xsdlib.jar
(restart the deploytool if used)
This should work,
Bas van OudenaardeHi Bas
Thank you for the very useful tip but I don't seem to have a SUNWappserv/lib/endorsed - directory inside my .war archive , could you please advise on this issue

Mysql driver issue with Deploytool 1.3

Hi,
I would like to have J2EE 1.3 container managed entity beans being able to talk with a Mysql database . I have added my jar file to deploytool and have the mysql database server running and the database table ready to be used. I am using Mysql Connector Java 3.0 and have put the required driver jar file into the ext directory of the JAVA_HOME path. I have windows XP.
Here is my configuration in deploytool :
Tools--> Server configuration --> Data source --> standart
JDBC driver : com.mysql.jdbc.Driver
JNDI name : jdbc/zob
JDBC url : jdbc:mysql (the database is running on localhost and the table to use is ready)
Then in the entity tab of my bean --> Deployment Settings --> Database Settings, I put jdbc/zob as JNDI name. No username or password is required.
If I try to generate Default SQL, I get the following error:
Erroe: while generating SQL
java.rmi.ServerException:RemoteException occured in server thread;nested exception is:
java.rmi.RemoteException: Error connecting to database;nested exception is:
java.sql.SQLException:No suitable driver
Please make sure the database name/user/password is valid and the J2EE server and database are running.
I would be very grateful for help because I can't see what is missing or wrong. Thank you very much in advance.

First thing to do is try to narrow in on the problem a little bit. Try writing a simple test JSP or something that runs on the container to manually get a Connection from your Connection Pool. Then do a simple query to make sure you can actually connect.
InitialContext ic = new InitialContext();
DataSource ds = (DataSource) ic.lookup("java:comp/env/jdbc/zob");
Connection conn = ds.getConnection();
do your test query
...Once you have established that your Connection Pool is working, then go ahead and try to get your entity bean working. I haven't used MySQL before, I have always used Oracle on some remote server, never on localhost. Maybe the URL convention is different when it's on localhost, but it seems like you're missing the host, port, and instance parts; you just have the driver.
I'm sure you've already checked this but I'll say it just in case, make sure you have your driver class somewhere that the container can see it. I know, it's obvious, but you never know...
Good luck!!

Unable to use j2ee -stop or the deploytool

I am a J2EE newbie. I have recently installed j2sdkee1.3.1 on Windows XP. The J2SDK version I am using is j2sdk1.4.0_01.
I can start the J2EE server successfully and view http://localhost:8000/index.html.
However, I am unable to stop the server using j2ee -stop. When I try to start deploytool, it hangs.
Any suggestions

I am havgin the same problem. When I try to stop I get error as:
Shutting down the J2EE server.
javax.naming.CommunicationException: Can't find SerialContextProvider
at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:63)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:120)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sun.enterprise.util.Utility.lookupObject(Utility.java:108)
at com.sun.enterprise.server.J2EEServer.clientShutdown(J2EEServer.java:996)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:936)
could you please help...
thanks

Java Application Server 8.2 deploytool on Solaris 10 (08/07)

I ran into a wierd problem with the deploy tool for APS 8.2. It can be started from the command line or from a tool bar icon. It will deploy an *.ear file created with 8.1 on a Linux system. However if the pushbutton to Verify J2EE Compliance is pressed, the DeplyTool window closes but the compliance window is opened. If a selection is made such as "Failures only" then the compliance window will also dissappear. This is repeatable. The fix is to run the deploytool in the verbose mode. .../deploytool --verbose. If someone can tell me why that would be good. I know that problem will eventually come back and haunt me. This problem does not occur on Redhat, SLED or SLES.

Are you sure that HTTP port used by this installation was actually 8080? It is the default value, but if that port is in use at installation time, alternative port will be assigned. Installer will show you the new value, but it is easy to miss if you are not looking very closely.
To find out which ports are actually being used check <installdir>domains/domain1/config/domain.xml file.

Can't get EE and SE to play nicely with deploytool

Hi,
I have tried the following combinations of installations:
j2se 1.4.x / j2ee 1.4.x (beta)
j2se 1.4.x / j2ee 1.3.1
j2se 1.3.1 / j2ee 1.4.x (beta)
With all of these combinations, the deploytool utility which comes with the j2ee bundle crashes on me at random times (usually within the first 2 minutes of use). And once its crashed the whole machine needs to be rebooted.
The only combination which works seems to be:
j2se 1.3.1 and j2ee 1.3.1 (so that's what I'm using now),
but I'd like to be able to use the latest and greatest.
So, has anyone else been having similar troubles?
Is this just a deploytool thing?
Cheers, Ben

Yes ! I am facing the same problem. Whenever I try to run, JAVA Web Start or deploytool, it just crashes, and reboots the system.
I am trying to use the 131 combination as you suggested. But I would definately like to use the latest and greatest.
Anybody, if have a solution, let us know please.
Thanks in Advance.
Sajan

Can't find deploytool in jwsdp1.1!!! What's wrong with jwsdp1.1

Hello,
I don't get it. It seems to me that jwsdp 1.1 is really f*cked up. Now, I don't want to offend anybody, but come'on. First of all, maybe the most important question I have right now is:
Where is the deploytool they use in the tutorials. Sorry, but I looked in <jwsdp_home>\bin. Can't find it. Maybe we should use the deploytool of j2ee 1.4 beta release. The only thing is, it doesn't work properly. At least not on my computer. This was my problem:
When I created a new Application (ear) and after that I created a new Bean as a new jar in an existing application, while pointing to the freshly made ear, it just didn't work. There was no deployment descriptor made, nor was there a jar file put inside of the ear.
So end of story, I can't use the deploytool. Does anybody know a solution. Because I am a last years student and have to finish this program in a couple of week. But if I can't deploy it, I have a big problem.
Or at least, does anybody know where I can find decent information about deploying web services???
Thanx in advance...
Beno�t

Thanx already for your reply,
I've seen the wsdeploy file in javaxrpc. But that wasn't the file I was really looking for. I was looking for deploytool.bat.
If you check the wsdp tutorial on page 79, under the title: "Deploying the application using deploytool" they mention this tool. And they state that one can find it at <jwsdp_home>/bin/deploytool
But like I said, it isn't inside the bin directory
I have a strange feeling that the tutorial is not referring to jwsdp1.1 but rather to jwsdp1.0
and that sun have taken some files like deploytool out of the jwsdp package and put them in the J2EE 1.4 package (like deploytool).
E.g. in the same tutorial in chapter 9 somewhere at the pages 399-400 they refer to a file "jwsdponj2ee" which is needed to integrate (i presume) jwsdp on j2ee 1.3.*. This is another file you can't find in the jwsdp 1.1 package. Is this confirming that Sun presumes everybody uses j2ee 1.4 right now?
Any reactions welcome
Beno�t
PS: Does anybody know if there are some people from sun who read these forum, or where I to whom I should direct the above.

Deploytool problems

Hello All.
I am having trouble deploying a basic Java Server Faces appilcation...the problem seems to be in the deploytool utility.
Firstly it doesnt seem to detect all the file that are updated since the app was last deployed and hence I have to drag each one into the WAR....very tedious.
Secondly, the re seems to be some dependency between files!!! If you updated one and added it to the WAR you must update others as well.
Thirdly, the server does not allow me to access my app at random times i.e update a file, update the war, save, deplo and try to access the app...only to get a resource unavilable message.
I have a feeling this is a deploytool problem. I am using J2ee version 1.4 with SUNWappserver 8.
Any Ideas?
Thanks

In addition.....every time a update a file in the application, deploytool update one file that....with the wrong version!!! Which doesnt even exist anymore on the disk.....
Using this on Linux...Fedora core 2....

Resource Ref's settings of a CMP bean in SAS PE 8.2 - Deploytool

Dear all,
In the deploytool of SAS8.2, in the [Resource Ref's] tab of a CMP bean do I need to set anything here to enable the CMP bean to connect to the database?
I already have a JDBC source registered in the server and it is called jdbc/mydatasource.
Thanks in advance.

Problem solved. For CMP beans, I just need to set the JNDI name of the CMP resource and this name corresponds to the JNDI name of the the JDBC resource registered in the SAS.
But for BMP beans, I will have to add an entry in the [Resource Ref's] tab. The [Coded name] corresponds to the JNDI name used in the code to look up this JDBC resource.
Thanks all.

Have problem with deploytool,help,Tx!!!

Hi:
I use deploytool to package ConverterApp followed the J2ee tutorial. But after Compile the file, i New a
new jar in Converter app , add the 3 classes to the Content,I get a error that deploytool told me "Cannot load the class convert.ConvertHome ...........",Why??? I confushed about it, Who can Help me???

I really find the Exception in the log file:
---------------- (DEBUG) Exception ---------------------------------------------
[NewEjbWizard.verifyAddedClasses:716]
Error loading class: converter.Converter
java.lang.UnsupportedClassVersionError: converter/Converter (Unsupported major.minor version 49.0)
java.lang.UnsupportedClassVersionError: converter/Converter (Unsupported major.minor version 49.0)
     at java.lang.ClassLoader.defineClass0(Native Method)
     at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
     at com.sun.enterprise.tools.deployment.ui.utils.J2EEClassLoader.findClass(J2EEClassLoader.java:529)
     at com.sun.enterprise.tools.deployment.ui.utils.DTClassLoader.findClass(DTClassLoader.java:424)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
     at com.sun.enterprise.tools.deployment.ui.utils.DTClassLoader._loadClass(DTClassLoader.java:381)
     at com.sun.enterprise.tools.deployment.ui.utils.DTClassLoader.loadClass(DTClassLoader.java:399)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
     at com.sun.enterprise.tools.deployment.ui.utils.DTClassLoader.loadClass(DTClassLoader.java:345)
     at com.sun.enterprise.tools.deployment.ui.ejb.NewEjbWizard.verifyAddedClasses(NewEjbWizard.java:712)
     at com.sun.enterprise.tools.deployment.ui.ejb.NewEjbWizard.validateComponent(NewEjbWizard.java:980)
     at com.sun.enterprise.tools.deployment.ui.utils.Wizard._performValidation(Wizard.java:711)
     at com.sun.enterprise.tools.deployment.ui.utils.Wizard._goForward(Wizard.java:724)
     at com.sun.enterprise.tools.deployment.ui.utils.Wizard$1.actionPerformed(Wizard.java:177)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
     at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:245)
     at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
     at java.awt.Component.processMouseEvent(Component.java:5100)
     at java.awt.Component.processEvent(Component.java:4897)
     at java.awt.Container.processEvent(Container.java:1569)
     at java.awt.Component.dispatchEventImpl(Component.java:3615)
     at java.awt.Container.dispatchEventImpl(Container.java:1627)
     at java.awt.Component.dispatchEvent(Component.java:3477)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
     at java.awt.Container.dispatchEventImpl(Container.java:1613)
     at java.awt.Window.dispatchEventImpl(Window.java:1606)
     at java.awt.Component.dispatchEvent(Component.java:3477)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
     at com.sun.enterprise.tools.deployment.ui.utils.UIEventQueue.dispatchEvent(UIEventQueue.java:168)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:141)
     at java.awt.Dialog$1.run(Dialog.java:540)
     at java.awt.Dialog.show(Dialog.java:561)
     at com.sun.enterprise.tools.deployment.ui.utils.UIDialog._showDialog(UIDialog.java:373)
     at com.sun.enterprise.tools.deployment.ui.utils.UIDialog.show(UIDialog.java:432)
     at com.sun.enterprise.tools.deployment.ui.utils.Wizard.show(Wizard.java:621)
     at com.sun.enterprise.tools.deployment.ui.utils.Wizard.show(Wizard.java:584)
     at com.sun.enterprise.tools.deployment.ui.ejb.NewEjbWizard.show(NewEjbWizard.java:558)
     at com.sun.enterprise.tools.deployment.ui.ejb.NewEjbWizard._showWizard(NewEjbWizard.java:282)
     at com.sun.enterprise.tools.deployment.ui.ejb.NewEjbWizard.newModule(NewEjbWizard.java:265)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.tools.deployment.ui.utils.UIActionDispatcher.invoke(UIActionDispatcher.java:371)
     at com.sun.enterprise.tools.deployment.ui.shared.ModuleManagerImpl.createNewModule(ModuleManagerImpl.java:229)
     at com.sun.enterprise.tools.deployment.ui.DeployToolWindow.createNewModule(DeployToolWindow.java:1811)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.tools.deployment.ui.utils.UIActionDispatcher.invoke(UIActionDispatcher.java:371)
     at com.sun.enterprise.tools.deployment.ui.utils.UIActionDispatcher.invoke(UIActionDispatcher.java:393)
     at com.sun.enterprise.tools.deployment.ui.utils.UIActionDispatcher.actionPerformed(UIActionDispatcher.java:476)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
     at com.sun.enterprise.tools.deployment.ui.utils.UIMenu$UIMenuItem.fireActionPerformed(UIMenu.java:436)
     at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
     at javax.swing.AbstractButton.doClick(AbstractButton.java:289)
     at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1113)
     at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(BasicMenuItemUI.java:943)
     at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
     at java.awt.Component.processMouseEvent(Component.java:5100)
     at java.awt.Component.processEvent(Component.java:4897)
     at java.awt.Container.processEvent(Container.java:1569)
     at java.awt.Component.dispatchEventImpl(Component.java:3615)
     at java.awt.Container.dispatchEventImpl(Container.java:1627)
     at java.awt.Component.dispatchEvent(Component.java:3477)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
     at java.awt.Container.dispatchEventImpl(Container.java:1613)
     at java.awt.Window.dispatchEventImpl(Window.java:1606)
     at java.awt.Component.dispatchEvent(Component.java:3477)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
     at com.sun.enterprise.tools.deployment.ui.utils.UIEventQueue.dispatchEvent(UIEventQueue.java:168)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
[Wizard._goForward:727] Validation failed, 'goForward' ignored.

Problem with deploytool

I'm using IPlanet 6 SP3 and am using the deploytool to deploy my application.
The application deploys without errors, but one of my jar files that lives under WEB-INF/lib does
not get fully unpacked. I have some dtd files which live in the JAR with the names
com/volantis/mcs/protocols/dtd/wml1_1.dtd
com/volantis/mcs/protocols/dtd/wml1_2.dtd
etc.
These files do not get unpacked in the deployed application. Anyone have any idea why?
Thanks
Mat.

I discovered the same issue. It seems that the deploy utility ONLY unpacks
class files and ignores all others. The only workaround that I have
discovered is to place the offending files elsewhere in the web application.
-jeff
"Mat Diss" <[email protected]> wrote in message
news:[email protected]..
I'm using IPlanet 6 SP3 and am using the deploytool to deploy myapplication.
>
The application deploys without errors, but one of my jar files that livesunder WEB-INF/lib does
not get fully unpacked. I have some dtd files which live in the JAR withthe names
>
com/volantis/mcs/protocols/dtd/wml1_1.dtd
com/volantis/mcs/protocols/dtd/wml1_2.dtd
etc.
These files do not get unpacked in the deployed application. Anyone haveany idea why?
>
Thanks
Mat.

Asadmin and deploytool

We have been using Java SDK 1.4 and EE 1.3 because we can not figure out how to deploy a working EJB on deploytool 1.4. It deploys, but the client code does not work. Of course it works in EE 1.3. We are able to set up the context but are unable to access the home methods.
     Context initialContext = null;
     PtListHome ptListHome = null;
     try {
          initialContext = new InitialContext();
          Object object = initialContext.lookup("PtList");
          ptListHome = (PtListHome) javax.rmi.PortableRemoteObject.narrow(object,PtListHome.class);
THE ABOVE LINE FAILS TO EXECUTE AND THE CATCH EXCEPTION OCCURS HERE.
          PtList item = ptListHome.findByPrimaryKey("1");
          String folder = item.getFolder();
          out.println(folder);
} catch ( Exception e) {
          out.print("catch Exception: ");
          e.printStackTrace();
          out.println(e.getMessage());
%>
<html>
<head>
</head>
<body>
We are thinking that it is the way we set up the connection pooling and jdbc resource using asadmin. Here is the code that we used.
create-jdbc-connection-pool datasourceclassname org.gjt.mm.mysql.Driver user admin mysql
create-jdbc-resource user admin connectionpoolid mysql jdbc/mysql
create-jdbc-resource user admin connectionpoolid mysql jdbc/MD
MD IS THE NAME OF THE DATABASE WHERE THE TABLE PtList is located. WE TRIED WITH AND WITHOUT CREATING THIS JDBC RESOURCE.
I couldn't attach the jar files but can email you if you can help.
Max

Check out the file WEB-INF/web.xml. There should be eight lines related to the servlet: <servlet>...</servlet> and <servlet-mapping>...</servlet-mapping>. Is <url-pattern>/ModemServlet</url-pattern> in there? Copy&paste&post the eight lines here.
Do you deploy the application at "/"? Deploy it at e.g. "/foo", then try /foo/ModemServlet.
If Sun Server is iPlanet's name this week, the web server has two log files: errors and access. Does errors mention the servlet at all, and what does the access log line look like when you access the URL?
Try restarting the web server after deployment. Shouldn't be necessary, but you never know.

Why is deploytool missing from JavaStudio Creator

I have installed both the the Sun App Server and Studio Creator/w App Server. But the icon for the deploytool is not added to my start menu (windows).
It is there on the App Server without Creator. I have tried starting the deploytool from the command line but I cannot get it to work. I like the Studio Creator, but I also don't want to have two instances of the server installed in order to use the deploytool. How can I use the deploytool in Java Studio Creator?

Hi,
Are you finding ways to deploy the built application onto the bundled appserver.The green Icon on the menu can do this job for you (Deploy and run).
Regards.

CRITICAL: Error occured while working with configuring .in WAS deploytool

Hi,
I have installed developer workspace WAS edition SP11.
I had given a master password to all the users created while installation.
But now for deployement and visual administration that password is not working.
So i started deploytool to enable Superadmin.
It allows me to change the value but when i save it,
it throws error stating:
<b>"CRITICAL : Error occured while working with configuration"</b>
and then deploytool stops abruptly.
Unless I enable superadmin, i wont be able to reset all my passwords.
How do i proceed??
AbhiJeet..

Hi all and Abhijeet especially,
have you found the cause of this problem? I'm experiencing exactly the same thing. What's to be done about this?
<u>excerpt from configtool log file:</u>
Error occurred while working with Configuration.
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: ,
     at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:294)
     at
     com.sap.engine.core.configuration.impl.cache.ConfigurationCache.commitConfigurationHandler(ConfigurationCache.java:1217)
     at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.commit(ConfigurationHandlerImpl.java:833)
     at com.sap.engine.configtool.batch.task.TaskUtil.changeProperties(TaskUtil.java:337)
     at com.sap.engine.configtool.batch.task.ChangeServicePropsTask.go(ChangeServicePropsTask.java:59)
     at com.sap.engine.configtool.batch.task.TasksThread.run(TasksThread.java:46)
Caused by: com.sap.dbtech.jdbc.exceptions.BatchUpdateExceptionSapDB: [-3018]: Invalid numeric parameter(input position 2)
     at com.sap.dbtech.jdbc.CallableStatementSapDB.executeBatch(CallableStatementSapDB.java:608)
     at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1102)
     at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1066)
     at
     com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.execInsertEntryBatch(DBAccessDefault.java:1170)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:257)
     ... 5 more
Message was edited by: Chee Choong Ching

Major bugs in J2EE 1.4 Deploytool

I posted a topic earlier on some error I received when trying to deploy a .war in the latest J2EE App. server. Since then I've found alot of other bugs that occur when using the deploytool. These range from minor issues to bugs where files get corrupted.
As of now, the deploytool is virtual unusable and I would really like a standalone tool for deploying my applications. Are these bugs known by Sun and is there a patch/updated version in progress?
Since I really need to use J2EE 1.4 I'm kinda stuck with this application server, so switching to JBoss or something else is not an alternative.

The file corruption bug is usually experienced when using deploytool on machines with non-English locales and is a known bug. The workaround is to set the locale for your machine to en-US. If you are experiencing other problems, please report it here: http://java.sun.com/webapps/bugreport/

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

Deploytool

Similar Messages

Maybe you are looking for