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

Similar Messages

  • Configure j2ee server

    hi
    i am fuad
    iam tring to use j2ee server but i don't know what is the configuration that should be done
    so if some one can help me what that ponit
    before iam using tomcat now i want use tamcat
    thank you

    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 install and configure J2EE server in ECC 6.0

    hi,
    I created a web service in ECC and I want to test it via SOAMANAGER but when I clik on open web service for selected naviagator binfing it gives me an error
    wsnavigator call WAS TERMINATED Because The Corresponding Service is not available.
    I searched the forum, apparently it is because the J2EE server is not configured
    thank you for your help

    Try this-----
    Setting Up a Connection to a J2EE Server for the Web Services Navigator
    To be able to use the Web Service Navigator to test a Web service, you need to set up a connection to a J2EE server, because the Web Service Navigator runs on the Java stack.
    Procedure
    Go to the Technical Administration tab.
    Choose Global System Settings.
    Choose the Web Services Navigator tab.
    Choose Edit / Display.
    Specify a host name and a port number.
    If you are working with a J2EE engine with SAP NetWeaver 2004 or 7.0, select J2EE engine is 6.40 / 7.0.
    If this option is not selected, the system assumes that you are working with a J2EE engine with version 7.10 or later.
    Save.
    Setting Up the Connection to the Services Registry
    To create a connection between the provider system and the Services Registry, perform the following steps for each consumer.
    From the SOA Manager main screen, go to the Technical Administration tab.
    Choose Global System Settings.
    Go to the Services Registry tab.
    Choose New to create a new connection.
    Note
    To change the settings of an existing connection, choose Edit. To delete an existing connection, Choose Delete.
    End of the note.
    Specify a Services Registry.
    The Services Registry name has to be written as a single word, for example, ERP_REGISTRY.
    To make this the primary Services Registry, select Primary.
    Each time a provider is configured, its endpoints are automatically published to the primary Services Registry.
    Choose Next.
    Choose a proxy class to use for communication with the Services Registry.
    You can choose either of the following:
    CO_SERVICES_REGISTRY_FLAT_SI
    The recommended consumer proxy to configure the connection to the Services Registry. CO_SERVICES_REGISTRY_FLAT_SI is the interface between the ABAP back-end system and the Services Registry system, and contains the appropriate authentication information.
    CO_ESREGISTRY_WSSI
    This consumer proxy was used in previous versions.
    The service path is determined automatically based on the proxy class name.
    Specify a logical port.
    Use uppercase characters for the logical port name.

  • Setting Root folder when configuring J2EE Server

    Hi,
    I'd like to know if it's possible to point the root folder to a remote server, i.e I'd like my Flex app to point to remote location.
    Thanks

    I think we're all looking for the same information, so I hope someone sees these postings and can help us out.  It would be nice to find out how to connect to a BlazeDS server on xyz.com from a client on abc.com.  Or is it even possible?<br /><br />Before going that far, I wanted to figure out how to configure Flex so that the client and the server would not have to run from the same container. This what I did.  If you build your project in Flex Builder, you can follow these instructions:<br /><br />http://livedocs.adobe.com/flex/3/html/projects_3.html#214351<br /><br />You will then see a .flexProperties file in your project directory (not visible from the IDE, so go to the file system).  The contents look something like this:<br /><br /><?xml version="1.0" encoding="UTF-8" standalone="no"?><br /><flexProperties flexServerType="2" serverContextRoot="/xyz" serverRoot="/opt/blazeds-turnkey-3.0.0/tomcat/webapps/xyz" serverRootURL="http://yourhost:8400/zyz" toolCompile="true" useServerFlexSDK="false" version="1"/><br /><br />This way you can have the BlazeDS server on the same machine, but separate from the client.  I would like to know though how to accomplish the same through using the command line SDK compiler, w/o using Flex Builder.  I can't find any documentation on this.

  • What to be mentioned in "Root folder" while configuring J2EE ...

    Hi, I am using Flex Builder 3 (trial version)...
    While creating new project, i chose Application Server as "J2EE" , selected "Use remote object access service" and selected "LiveCycle Data Services"..
    In the "Configure J2EE server" page, I unchecked "Use default location for local LCDS server.
    I DONT KNOW WAT TO MENTION IN "Root folder"....
    pls suggest me..
    ( By default "Root URL" is http://localhost:8700/flex/ )
    regards,
    bossim.

    hi
    check this help http://help.sap.com/saphelp_nw04s/helpdata/en/58/bce81866d9984096350cae0d6753c3/frameset.htm
    Regards,
    Arun S

  • FB4 Beta 2 error message on "validate configuration" for web root

    Hello:
    I have been working in FB4 beta 1 and had a php project working fine. After installing FB4 beta 2, i am now having problems with the flex server web root and/or root URL. i am now getting the following error message when I try and "validate configuration" for a configuration which had been working. The error message is:
    "(the web root) is not a valid location because the project contains a linked resource at that location"
    Here are my settings which had been workin g with FB4beta1, but which now result in the error message with FB4beta2:
    >> web root c:\wamp\www
    >> root URL: http://localhost
    >> output folder: c:\wamp\www\projectname-debug
    I am running wamp server on my local machine as my testing server; I run windows XP pro; this is a php project
    Has anyone seen this problem in FB4 beta2?
    thanks very much

    I just recently had this issue myself but I did a Clean on my project and it seems to working fine now.
    Hope this helps if you are still having this issue.
    Keith

  • How to install and configure configure IGS for J2EE server 700

    Hi,
    Please help me in installing and configuring IGS for J2EE server700 as i need it to run Business Graphics for my Web DynPro application. Earlier i had installed J2EE server 640 and i didnt have to do any separate installation for IGS. I just had to configure the IGS URL from Visual Admin. But i can't find any igswd.exe running on my J2EE700 engine.
    Please let me know the procedure for this.
    Thanks an Regards,
    Smriti.

    Hi,
    Check the below link,
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/17/86c039c7811f11e10000000a114084/frameset.htm">About IGS Configuration and Adminisatration</a>
    Regards,
    Suresh.T

  • Configuring the J2EE server in WSADMIN

    I am a newbie to the WAS (although not to ABAP).  Futhermore I am a developer, not a BASIS person.  So please gentle and kind in your responses
    I am trying to test my first Web Service that I've created from an ABAP RFC.  In testing it via WSADMIN, I have found that I need to configure a J2EE server.
    Here's the message I am receiving...
    Diagnosis
    The J2EE Server provides the Web Service homepage with test functions. To use these test functions, the address of the J2EE Server must be defined.
    My questions are:
    1) Do I need this J2EE server defined to make my web service work or is it only required for testing?
    2) What are the requirements for a J2EE server?
    Thanks,
    Wardell

    Helpppp!!!!, i have the same problem, could you resolve it??? please help me.

  • How to Configure the Weblogic Server 6.0 Beta version with Solaris 8

    Hello,
    I have problem in starting the weblogic server 6.0 beta version.
    It is occupying hell of space and running very slow. When I try
    to deploy the bean it is throwing exception like timeout.
    Plese do suggest me what to do. and how to configure properly.
    Thank you,

    That typically happens when you have your database connections configured
    incorrectly. WebLogic is timing out on accessing the database.
    Michael Girdley
    BEA Systems Inc
    "Laxmikanth" <[email protected]> wrote in message
    news:3a35523c$[email protected]..
    >
    Hello,
    I have problem in starting the weblogic server 6.0 beta version.
    It is occupying hell of space and running very slow. When I try
    to deploy the bean it is throwing exception like timeout.
    Plese do suggest me what to do. and how to configure properly.
    Thank you,

  • Configuring name server in j2ee visual admin

    hi all
    i found the go.bat file in the following path in my system
    /usr/sap/EEP/JC00/j2ee/admin/go.bat
    now i want to run that "go.bat" but i don't know how to run this in linux machine but my portal server is installed in linux machine.so, can any one help me how to run that file in order to configure name server .
    and also can any one tell me how to find out the server name and port number in order to fill the following format in name sererver
    tcpip://<%nameserver%>:portnumber
    plzz help me out
    Thks&Rgds
    Gnana

    hi dominlik
    yeah go file is there but while running the following was displayed
    [root@entegdt26 admin]# ls
    adminCFG.properties  go      go.jar    lib  logviewer-standalone
    cfg                  go.bat  launcher  log
    [root@entegdt26 admin]# sh go
    go: line 7: /usr/java/bin/java: No such file or directory
    [root@entegdt26 admin]#
    can  u tell me how to mark it as executable using chmod coz i am not aware of linux
    its very very urgent help out only one day i've time with in this i've to configure trex name server and create index in ep
    awaiting for reply
    Regards
    gnana

  • How to configure Engine/SDM for SAP J2EE  Server

    Hi Experts,
    I deployed the EAR file on J2EE Server.
    This EAR file is linked to WebModuleProject (xyz)whic has a WAR file.
    This WAR file contains one JSP. (test_jsp.jsp)
    Then on following the URL
    <a href="http://server:port/xyz/test_jsp.jsp">http://server:port/xyz/test_jsp.jsp</a>
    i m getting the following error message:
    Nov 29, 2007 11:01:40 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !
    How do i configure engine/SDM?
    What is SDM engine?

    I configured the SDM/Engine successfully
    but still following the url
    <a href="http://server:port/xyz/test_jsp.jsp">http://server:port/xyz/test_jsp.jsp</a>
    i m getting the following error
    404   Not Found
      The requested resource /WebModuleProject/test_jsp.jsp is not available
      Details:   File [WebModuleProject/test_jsp.jsp] not found in application root of alias [/] of J2EE application [sap.com/com.sap.engine.docs.examples].
    Please experts help me to dig out this problem
    Can anybody suggest me why i m getting the error?

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

  • Cannot start J2EE server on Windows 2000 server

    Hi..
    I installed J2EE 1.3(beta) along with J2SE1.3 that comes with the Java Jump start CDs.
    The installation process went fine...I configured the environment variables but when I try to start the J2EE server from command prompt I get the following error.
    E:\>j2ee -verbose
    Exception in thread "main" java.lang.NoClassDefFoundError: javax/naming/Context at com.sun.enterprise.server.J2EEServer.<clinit>(J2EEServer.java:59)
    The same error is encountered with other switches(stop, version etc.) of j2ee.
    There is no conflict of port numbers. Can anyone please guide me properly what I have done wrong in the installation process?
    Thanks

    Well...I removed the CLASSPATH variable all together and reinstalled J2SE 1.3 again(refreshed all the environment variables) and then started j2ee server....and it worked this time...
    Thanks alot...

  • Failure to start J2EE Server

    Hi,
    I am trying to start the J2EE server in Windows XP environment. It worked for once. But after that, the server says that it failed to start the domain.
    When I checked the log file in domain directory, I found exceptions that are related to JMS. I don't know how to fix this. I would appreciate if anyone could help me. The following are the exceptions that I found from log file.
    Starting J2EETM 1.4 Application Server Beta 2 ...
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:47:26:643 GMT-05:00][CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2] from [Sun Microsystems Inc.]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:716 GMT-05:00][ADM0020:Following is the information about the JMX MBeanServer used:]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:726 GMT-05:00][ADM0021:MBeanServer Implementation Name:[JMX]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:726 GMT-05:00][ADM0022:MBeanServer Implementation Vendor:[Sun Microsystems]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:736 GMT-05:00][ADM023:JMX Implementation Version:[1.2_r08]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:736 GMT-05:00][ADM024:MBeanServer ID:[vishist_1067363248606]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:736 GMT-05:00][ADM025:MBeanServer Implementation Classname:[com.sun.jmx.mbeanserver.JmxMBeanServer]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:806 GMT-05:00][ADM0002:System MBean initialized:[ias:type=controller]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:826 GMT-05:00][ADM0002:System MBean initialized:[ias:type=configurator]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:836 GMT-05:00][ADM0001:MBeanServer initialized successfully]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:866 GMT-05:00][ADM0005:Timestamp files for configuration created for:[server]]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:47:28:866 GMT-05:00][ADM0102: Starting a thread for tracking manual changes]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.jms][28.October.2003 12:48:38:106 GMT-05:00][JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.jms][28.October.2003 12:48:38:106 GMT-05:00][JMS5036: More details may be available in the log file for the JMS service broker instance domain1_server. Please refer to the JMS provider documentation for the exact location of this log file.]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.resource.jms][28.October.2003 12:48:38:106 GMT-05:00][JMS5024: JMS service startup failed.]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:106 GMT-05:00][Service com.sun.enterprise.jms.JmsProviderLifecycle@1d33a6b cannot be initialized! : com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:106 GMT-05:00][CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:268)
    at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:209)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:166)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
    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 org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:252)
    ... 8 more
    Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation. - caught java.net.ConnectException
    at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(ExceptionHandler.java:183)
    at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(ExceptionHandler.java:136)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:53)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
    at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:233)
    at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
    at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:509)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1020)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1554)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:438)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:247)
    at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
    at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
    at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
    at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:733)
    at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:305)
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:245)
    ... 8 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
    at java.net.Socket.connect(Socket.java:452)
    at java.net.Socket.connect(Socket.java:402)
    at java.net.Socket.<init>(Socket.java:309)
    at java.net.Socket.<init>(Socket.java:124)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
    ... 26 more
    ]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:126 GMT-05:00][Server Startup failed. Exiting...]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:126 GMT-05:00][Server shutdown in progress...]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:266 GMT-05:00][CORE5051: Shutting down all J2EE applications ...]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:286 GMT-05:00][CORE5049: Unexpected error occurred while shutting down applications
    java.lang.NullPointerException
    at com.sun.enterprise.server.ApplicationLifecycle.onShutdown(ApplicationLifecycle.java:339)
    at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:409)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:184)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:131)
    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 org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    ]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:48:38:346 GMT-05:00][ADM0103: Stopping the thread for tracking manual changes]>
    <[WARNING][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:48:38:366 GMT-05:00][core.tmp_folder_deletion_failed]>
    <[INFO][j2eesdk1.4_beta2][][][10][javax.enterprise.system.tools.admin][28.October.2003 12:48:38:366 GMT-05:00][ADM032:The System MBeanServer released]>
    <[SEVERE][j2eesdk1.4_beta2][][][10][javax.enterprise.system.core][28.October.2003 12:48:38:406 GMT-05:00][Server stopped due to Server startup failure.]>

    Based on this, assigned JMS port is already in use during the server startup. One possibility is that the previous shutdown of the server did not go through, or some completely unrelated process started using JMS port (default value of JMS port is 7676).
    To fix this, you can either try to find out what is using JMS port and shut that process down, or modify <install_dir>/domains/domain1/server/config/domain.xml file with different JMS port number.

  • BACK button difference between Weblogic and J2EE server

              Hi Everyone,
              I have a J2EE application implemented mainly with JSP and EJB, which can run on
              both J2EE and Weblogic Servers seperately. When running on either of them, the
              server acts as both a web and application server.
              It is my understanding that it first goes to the cache in the browser when you
              try to revisit the previous page (JSP files) by clicking the BACK button in the
              browser. If the page is there, it just displays that page from the cache. If not,
              it will go to the server to retrive (execute) that page.
              When I run my application over J2EE server and try to visit the previous page
              by using the BACK button in the browser, it does this way correctly. But when
              I run my
              application over Weblogic server, it always goes to the server and execute the
              JSP file again in the server, rather than simply retriving that page from the
              cache. If your JSP file is simply doing data retriving, that is fine. But if it
              is doing data inserting, it will insert your data again. This is not good.
              I know that the Weblogic server is mainly an application server. But I am not
              sure when it acts as a web server,
              why it works differently from J2EE which also can acts as both an pplication and
              a web server. Does anyone have any ideas or suggestions about this?
              Thanks a lot.
              -John
              

    I believe that the correct behaviour is to rerun the .jsp page unless the
              user specifically sets the header to allow the browser to cache it. That
              being said... You should never make a web application that can be broken by
              the user hitting "reload" or the browser automatically retrying. An
              application like this is very fragile and will probably break in practice.
              I suggest that you either make all your pages idempotent or you keep track
              through a hidden form field a transaction id and only allow the execution of
              any particular transaction once. As far as WebLogic not being a good web
              server, I would say that with 6.1 you get most of the management advantages
              of using a separate web server and also most of the static file performance
              you will find with apache or IIS.
              Sam
              "John Wang" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Hi Bruno,
              >
              > Thank you for your prompt reply.
              >
              > I think I might not explain my problem clearly. My application
              > is in developing stage now. So we are just working on a single
              > serevr which can acts as both a web and an application server.
              > Later we are going to distribute our application into a web and an
              application
              > seperately.
              >
              > As you said, it seems that my problem is because the weblogic server is
              mainly
              > an application server and does not act as a web server very well. So if I
              distribute
              > my application into both a web and an application servers, it should be
              fine,
              > since it is ok when I run it over the J2EE server. Is this correct?
              >
              > In other words, I can say that the J2EE server is configured better in its
              role
              > as a web server than the weblogic server, isn't it?
              >
              > In addition, all my JSP files are only dealing with catching
              > data from user input and displaying data. Data inserting is done
              > by EJB and JavaBeans through the JSP files. Because those JavaBeans in the
              JSP
              > files, each time when I use the BACK button, it will invoke those
              JavaBeans and
              > EJBs through the JSP files and do things like inserting in the background.
              That
              > is what I mean in my previous message.
              >
              > Thanks.
              >
              > -John
              >
              > "Bruno" <[email protected]> wrote:
              > >
              > >Hi John,
              > >
              > >You should use a real Web Server on the front side of your application.
              > >Weblogic
              > >is mainly an application server that has to be used in middle tier. But
              > >it's not
              > >a good Web Server. Like almost all J2EE application. You should use a
              > >separate
              > >web server like apache, optimised to serve static file. Furthemore, this
              > >approach
              > >will enable you to physically separate the two servers for a better
              security.
              > >Anyway, usually jsp files are dynamic files and are not intended to be
              > >totally
              > >cached (except in special cases). I think you should just use JSP to
              > >display data.
              > >If you want to do data inserting, you should use EJB or JavaBeans for
              > >that rather
              > >than JSP.
              > >
              > >Hope it helps
              > >
              > >Regards
              > >
              > >"John Wang" <[email protected]> wrote:
              > >>
              > >>Hi Everyone,
              > >>
              > >>I have a J2EE application implemented mainly with JSP and EJB, which
              > >>can run on
              > >>both J2EE and Weblogic Servers seperately. When running on either of
              > >>them, the
              > >>server acts as both a web and application server.
              > >>
              > >>It is my understanding that it first goes to the cache in the browser
              > >>when you
              > >>try to revisit the previous page (JSP files) by clicking the BACK button
              > >>in the
              > >>browser. If the page is there, it just displays that page from the
              cache.
              > >>If not,
              > >>it will go to the server to retrive (execute) that page.
              > >>
              > >>When I run my application over J2EE server and try to visit the previous
              > >>page
              > >>by using the BACK button in the browser, it does this way correctly.
              > >>But when
              > >>I run my
              > >>application over Weblogic server, it always goes to the server and
              execute
              > >>the
              > >>JSP file again in the server, rather than simply retriving that page
              > >>from the
              > >>cache. If your JSP file is simply doing data retriving, that is fine.
              > >>But if it
              > >>is doing data inserting, it will insert your data again. This is not
              > >>good.
              > >>
              > >>I know that the Weblogic server is mainly an application server. But
              > >>I am not
              > >>sure when it acts as a web server,
              > >>why it works differently from J2EE which also can acts as both an
              pplication
              > >>and
              > >>a web server. Does anyone have any ideas or suggestions about this?
              > >>
              > >>Thanks a lot.
              > >>
              > >>-John
              > >>
              > >
              >
              

Maybe you are looking for