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....

Similar Messages

Beginner - Deploytool problems

Hi Everyone,
I am just starting to learn to run the j2ee server and have run into problems with the 'depoloytool'. Whenever the i try to connect to the server (localhost:4848) via the deploytool the deploytool hangs. Wierdly, the problem goes away when the network cable is disconnected. deploytool also detects an incorrect password and hangs only when the password is correct.
I have verified the following
1) My OS is supported. My OS is Windows XP Professional
2) The right version of jsdk is installed (j2sdk1.4.2)
3) The right version of j2ee is installed (j2sdkee1.4)
4) Server was running before deploytool was started. Some deployed applications were also verified from the web browser.
I have tried fiddling with the following
1) the java.policy file in the jre\lib\security folder to allow "listen,accept,connect,resolve" privileges to localhost
2) The hosts file to specify 127.0.0.1 as localhost.
I am at loss of what to do. If anyone has any ideas please help me.
I have gone through the these forums and have come across one similar thread.
http://forum.java.sun.com/thread.jsp?forum=13&thread=277109
David.

Hey
I had this problem on both windows XP pro and linux
<quick solution>
edit all your xml config files so that they refer to "localhost", not your computer network name
<quick solution>
The reason:
The problem for me was that some of the configuration files referred to my computer as its fully qualified network name, terrence.
the files (for me) are:
<install-dir>/domains/domain1/server/config/*.xml
I use a NAT dsl modem, so the modem was just discarding all the requests to connect to terrence were getting dropped (no pinholes set up!)
even though deploytool calls your local computer localhost, it still tries to acces it thru ur network name some times, i think
Hope that helps
P.S. Any idea why sun doesnt just use "localhost" in the config files?

Struts framework & J2EE deploytool problem

When creating a new application in the J2EE deploytool with the example WAR file "struts-example.war" from the struts framework i can view this at "http://localhost:8000/example/" with no problem. However, when creating my own WAR file of the build struts framework example i get after deployment and calling "http://localhost:8000/example/" the following:
"javax.servlet.ServletException: Cannot find message resources under key org.apache.struts.action.MESSAGE"
The WAR and EAR configs look exactly alike in the J2EE deploytool.
What bugging me is i can not find the problem.
Please inform
Thanbks

Thank you very much for the response.
As you mentioned I put the "ApplicationResources.properties" file in the classes directory, this gives me the same error.
However, i am using struts 1.1 if it matters and in web.xml the following is defined:
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config.xml</param-value>
</init-param>
and in struts-config.xml :
<message-resources
parameter="org.apache.struts.webapp.example.ApplicationResources"/>
This is the directory where the "ApplicationResources.properties" also excists.
As mentioned the example war coming with the framework works fine, so i assume it is not related to any envioronment vars.
It is probably clear that i am new to all this. My objective is to determine whether my exising framework with a servlet session controlling usecase can be integrated with the strutsframework.
I thank you for your time
regards, Erwin

Deploytool problem: Tools- Server Configuration not being displayed

I am having the above titled problem when following the instructions from section 7.2.2 of the JMS tutorial.
Please help
Owen.

Typically, when I start J2EE, I get the following:
C:\j2sdkee1.4\logs>j2ee -verbose
J2EE server listen port: 1050
Naming service started: 1050
Binding DataSource, name = jdbc/InventoryDB, url = jdbc:cloudscape:rmi:Cloudscap
eDB;create=true
Binding DataSource, name = jdbc/DB1, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/DB2, 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/XACloudscape, url = jdbc/XACloudscape__xa
Binding DataSource, name = jdbc/XACloudscape__xa, dataSource = COM.cloudscape.co
re.RemoteXaDataSource@1250ff2
Binding DataSource, name = jdbc/_ejb_container, url = jdbc/_ejb_container__xa
Binding DataSource, name = jdbc/_ejb_container__xa, dataSource = COM.cloudscape.
core.XaDataSource@1b6235b
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
ResourceAdapter jmsra.rar started...
Initializing Coyote HTTP/1.1 on port 8000
Initializing Coyote HTTP/1.1 on port 7000
Loaded registry information 1432 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
Binding Connection Factory, name = QueueConnectionFactory
Binding Connection Factory, name = jms/TopicConnectionFactory
Binding Connection Factory, name = TopicConnectionFactory
Binding Connection Factory, name = jms/QueueConnectionFactory
Binding Connection Factory, name = eis/JAXR
Cannot create Destination jms/Topic since it already exists
Binding Administered Object, name = jms/Topic
Cannot create Destination jms/Queue since it already exists
Binding Administered Object, name = jms/Queue
Starting EJB Timer Service...
J2EE server startup complete.
I do not see any reason in the above as to why deploytool might not be working as I think it should. Maybe others have an idea?
Owen.

Cloudscape and deploytool problem

My deploytool and cloudscape have been working well until yesterday. The error message that I received with cloudscape was
ERROR (no SQLState): Connection refused to host: 218.186.XX.XXX; nested exceptio
n is:
java.net.ConnectException: Connection timed out: connect
ij version 4.0 (c) 1997-2001 Informix Software, Inc.
And also, the deploytool cant seem to find my localhost.
Wonder if anyone knows what is this problem? It seems that my localhost is not able to host. Any help will be appreciated.

I would try rebooting cloudscape.

Deploytool problem

hello
I am not able to run the deploytool of J2EE.
When i run it from the console, i get the following error
Bad Command or file name
Out of Environment space
Out of Environment space
Bad Command or file name
I am not able to find out where i have something wrong.
What should i do now...
My OS is windows 98 second edition
any help will be greatly appreciated
Hussain

Hussain,
take a look at the following URL
http://forums.java.sun.com/thread.jsp?forum=136&thread=166386&start=0&range=15
-Chris

About deploytool problem

There is a checkbox "return a client jar" when I deploy a EJB.It will output a client.jar file if I deploy the EJB successfully.But what is the client.jar and how can I use it?

Thank you!
You means that the ejb-client.jar contain the "stub,skeleton" that should be used by RMI and the ejb-jar that EJB container used?
If I want to run a EJB in my server(For example:Tomcat) and I must have the ejb-client.jar in the Tomcat?

Problem in running an EJB using deploytool in j2ee

I tried the deploytool in j2sdkee1.3 and wrote a simple ejb. I succeeded in compiling the files and in deploying, but when I typed runclient -client Hello.ear -name HelloClient -textauth in the command line, I met problem and the error message is : Binding name:Bingname:'java:comp/env/HelloWorld'
java.security.AccessControlException: access
denied<java.util.PropertyPermission * read,write)
unbinding name:'java:comp/env/HelloWorld'
what can I do ? many thanks

4 .class files: Hello,HelloHome,HelloEJB,HelloClient. Following some instructions I succeeded in deploying the ejb,and the error occured when i typed"runclient -client Hello.ear -name HelloClient" in the command-line. PropertyPermission error ?

Problem using sun deploytool

I am trying to use the deploytool on a simple bean in the book 'Mastering EJBs'
I added the EJB and reference and made an appclient. When I go to verify I get the following error:
Problem in parsing the xml file
cvc-complex-type.2.4.a: Invalid content was found starting with element 'ejb-local-ref'. One of '{"http://java.sun.com/xml/ns/j2ee":display-name, "http://java.sun.com/xml/ns/j2ee":icon, "http://java.sun.com/xml/ns/j2ee":env-entry, "http://java.sun.com/xml/ns/j2ee":ejb-ref, "http://java.sun.com/xml/ns/j2ee":service-ref, "http://java.sun.com/xml/ns/j2ee":resource-ref, "http://java.sun.com/xml/ns/j2ee":resource-env-ref, "http://java.sun.com/xml/ns/j2ee":message-destination-ref, "http://java.sun.com/xml/ns/j2ee":callback-handler, "http://java.sun.com/xml/ns/j2ee":message-destination}' is expected.
When I run the appclient I get:
appclient -client hellotestClient.jar
Mar 10, 2005 9:38:15 PM com.sun.enterprise.appclient.Main <init>
WARNING: ACC006: No application client descriptor defined for: [null]

<?xml version='1.0' encoding='UTF-8'?> <ejb-jar ��version="2.1" ��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/ejb-jar_2_1.xsd" ��> ��<display-name>Ejb1</display-name> ��<enterprise-beans> ��<session> ��<display-name>HelloBean</display-name> ��<ejb-name>HelloBean</ejb-name> ��<home>examples.HelloHome</home> ��<remote>examples.Hello</remote> ��<local-home>examples.HelloLocalHome</local-home> ��<local>examples.HelloLocal</local> ��<ejb-class>examples.HelloBean</ejb-class> ��<session-type>Stateful</session-type> ��<transaction-type>Bean</transaction-type> ��<ejb-ref> ��<ejb-ref-name>ejb/helloBean</ejb-ref-name> ��<ejb-ref-type>Session</ejb-ref-type> ��<home>examples.HelloHome</home> ��<remote>examples.Hello</remote> ��</ejb-ref> ��<security-identity> ��<use-caller-identity> ��</use-caller-identity> ��</security-identity> ��</session> ��</enterprise-beans> </ejb-jar

Problems starting Deploytool of j2sdkee1.3.1

Hi everybody!!
I recently installed j2sdkee1.3.1 on Windows 2000(Advanced Server).
I set up the JAVA_HOME and J2EE_HOME environment variables accordingly. I have j2sdk1.4.1 installed prior to it. So, the J2EE server starts properly and I can see the welcome & congrats page at http://localhost:8000/index.html.
But, the problem I am facing is that the DEPLOYTOOL just doesn't start.
I am mentioning below the exact messages that I get on my command prompt
while trying to start the deploytool after I have started the J2EE server on another command prompt:
C:\>deploytool
Starting deploytool, version 1.3.1
(Type 'deploytool -help for command line options)
No local string for enterprise.tools.deployment.main.error_creating_ui
Unable to create UI: java.lang.ExceptionInIntializerError
I thought that may be there could be a problem in installation so I uninstalled the j2sdkee1.3.1 and then reinstalled it, but still I was facing the same problem.
So,then I thought that may be there could be some problem with the installation bundle of j2sdkee1.3.1 that I installed. So I got hold of
another bundle of j2sdkee1.3.1 and installed it. But still I am getting
the same problem.
Please help me, I am stuck with this problem for past couple of months.
Thanking you all!!
Tariq

Hi Tariq,
Can you try the deploytool with jdk1.3,I suspect there the Linkage Error being due to incompatibility of some classes which have been changed in jdk1.4.
And the classes which make run the deploytool are dependent on those classes(which have been modified in jdk1.4).Check what the Linkage Error means in java docs
Subclasses of LinkageError indicate that a class has some dependency on another class; however, the latter class has incompatibly changed after the compilation of the former class
So the classes which make the deploytool have some dependencies on the classes which have been modified in jdk1.4 latter class has incompatibly ....
Got it!!!!
That is what I can tell you out of my experience.....
regards
Vicky

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.

Problems with deploytool

hi,
i have just started with j2ee...i have win98/j2sdk1.4.0/j2sdkee1.2.1...
i get an error message when i start the deploytool...
is the config mentioned above compatible..or is something else wrong..
thanks in advance..

You'll probably want to upgrade to at least J2EE Version 1.3.1 and may be even 1.4 for starters. You'll find detailed instructions on how to do either at
http://groups.msn.com/J2EETools
Good luck!

Help! Problem in deploying ejb with j2ee1.4 deploytool

I have the error message.
my system setup
Project name G:\Test33.ear
J2EE_HOME d:\j2sdkee1.4
JAVA_HOME d:\jdk1.4.2
program path g:\
ear path g:\
i cannot deploy it on j2sdkee1.4.
Any help in this regard is very welcome.
What is the context path i have to setup to deploy this project
distribute: G:\Test33.ear
Deploy action running...
Contacted Server...
Application Test33 transferred
Application Test33 transferred
Deployment of Test33 is complete.
Deployment of Test33 is complete.
Completed
--- Operation Completed Successfully ---
start: Test33
Running...
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
     java.rmi.RemoteException: null; nested exception is:
     javax.management.ReflectionException
     at com.sun.corba.se.internal.iiop.ShutdownUtilDelegate.mapSystemException(ShutdownUtilDelegate.java:61)
     at javax.rmi.CORBA.Util.mapSystemException(Util.java:65)
     at org.omg.stub.com.sun.enterprise.tools.deployment.backend._JarInstaller_Stub.start(Unknown Source)
     at com.sun.enterprise.deployapi.actions.ModuleStateAction.run(ModuleStateAction.java:58)
     at java.lang.Thread.run(Thread.java:534)
Caused by: java.rmi.RemoteException: null; nested exception is:
     javax.management.ReflectionException
     at com.sun.enterprise.tools.deployment.backend.JarInstallerImpl.start(JarInstallerImpl.java:1171)
     at org.omg.stub.com.sun.enterprise.tools.deployment.backend._JarInstallerImpl_Tie._invoke(Unknown Source)
     at com.sun.corba.se.internal.corba.ServerDelegate.dispatch(ServerDelegate.java:353)
     at com.sun.corba.se.internal.iiop.ORB.process(ORB.java:252)
     at com.sun.corba.se.internal.iiop.RequestProcessor.process(RequestProcessor.java:81)
     at com.sun.corba.se.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.java:106)
Caused by: javax.management.ReflectionException
     at com.sun.management.j2se.MOAgents.EmmaBeanUtil.invoke(EmmaBeanUtil.java:346)
     at com.sun.enterprise.management.model.emma.J2EEApplicationMdlEmmaAgent.invoke(J2EEApplicationMdlEmmaAgent.java:406)
     at com.sun.jdmk.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:334)
     at com.sun.jdmk.MetaDataImpl.invoke(MetaDataImpl.java:496)
     at com.sun.jdmk.DefaultMBeanAccessor.invoke(DefaultMBeanAccessor.java:528)
     at com.sun.jdmk.MBeanServerImpl.invoke(MBeanServerImpl.java:579)
     at com.sun.enterprise.management.agent.MEJBUtility.invoke(MEJBUtility.java:314)
     at com.sun.enterprise.management.util.J2EEManagementObjectManager.startModule(J2EEManagementObjectManager.java:636)
     at com.sun.enterprise.tools.deployment.backend.JarInstallerImpl.start(JarInstallerImpl.java:1161)
     ... 5 more
!!! Operation Failed !!!
[Completed (time=39.7sec, status=13)]
**********************************************************************

Don't suppose you ever fixed this, or anyone know how ?!! I'm on XP, sdkee1.4-beta
Cheers

A problem about deploytool

In Web WAR's resource reference tab, i find two fields called coded name and jndi name.
What are the relationships between the two?
are they always the same in a specific Web WAR?
Please tell me in details.
Thanks!!!!

That tab allows you to map names coded in your web component to other JNDI names. For instance, if you are connecting to a JDBC resource, the coded name doesn't need to match the name of the JDBC resource in JNDI. At deploy time, you can map the coded name to the actual JDBC resource configured for your server.
In almost all cases, the coded name and the actual JNDI name will be different.
For a concrete example, if I have a WAR that manages addresses, and I have a database table that stores those addresses, the coded name is jdbc/AddressDB. When I deploy the WAR, I'll map the coded name to jdbc/CustomerDB, a JDBC resource I've set up to store all customer information.
-Ian Evans

Deploytool problems

Similar Messages

Maybe you are looking for