WAR deployment to IBM WebSpherer (jnlpdownloadservlet)

I want to deploy a self-created WAR file (created e.g. with Venus Application Publisher) to IBM Websphere (3.5.4). The WAR-import process itself works fine. But the web application does not work.
Clicking/launching a JNLP-File over the download-servlet causes an response (on the browser) "The document contained no data...".
The Websphere log says something like:
"Basic Protocol lookup"
"Error code returned for request: /TestApp/test.jnlp"
"Response: com.sun.javaws.servlet.DownloadRequest$NotFoundRequest"
Has anyone suggestions about possible mistakes ? Or running examples ... ??

Have you find a solution ?
I have the same problem but I have com.sun.javaws.servlet.DownloadRequest$NotFoundResponse. For me, WAS don't understand the path. I don't known why.
I need Help
Thanks
The Websphere log says something like:
"Basic Protocol lookup"
"Error code returned for request: /TestApp/test.jnlp"
"Response:
com.sun.javaws.servlet.DownloadRequest$NotFoundRequest"
Has anyone suggestions about possible mistakes ? Or
running examples ... ??

Similar Messages

  • Deploy on IBM WebSphere 6

    I am trying out a small 'HelloWorld' stateless EJB from scratch.
    Deployed it on JBoss & Weblogic (used jboss.xml & weblogic-ejb-jar.xml respectively -which gives jndi binding) using ANT and build file.
    But same thing when I am trying on IBM Websphere 6 - it seems to be complicated. I tried to edit 'ibm-ejb-jar-bnd.xmi' - but the attributes are bit confusing and when I tried to deploy the application thr admin console, there are too many steps to follow.
    1)Can any body provide sample 'ibm-ejb-jar-bnd.xmi' ? The one generated by WSAD seems like using runtime classes bindings. Also, whether this file is sufficient?
    2)What is the simplest way to deploy on WebSphere 6?
    regards
    Manisha

    Hi Manisha,
    A few suggestions.
    1. Please build your J2EE application/EJB/Web Module using WSAD 6. So you will get an EAR, EJB Jar or a WAR file. During build WSAD will create the xmi files.
    2. Using WSAD now export your EAR/JAR/WAR files to your disk.
    3. Stop WSAD.
    4. Start your Wensphere App Server 6. Open admin console.
    5. I don't remember the name of menu, should be install applications, import he EAR/JAR/WAR file created by you on server.
    ===================================================
    Another process may be,
    1. Use the xmi file generated by WSAD as your starting point. Then edit it as per your requirements.
    2.Compile your classes.
    3. Create a JAR/EAR/WAR file out of your classes and deployment descriptors and xmi files.
    4. Start WAS 6, open admin console. Go to installation. Provide path of your JAR/EAR/WAR file. Follow the installation steps.
    5. During this process RMIC compilation will also happen and container will generate required classes and compile them.
    6. Finish your deployment.
    ======================================================
    If you need any further help do let me know with steps followed by you.
    HTH
    VJ

  • Struts problem on IBM Websphere

    Hi,
    We have a struts application that works fine when running in the IBM Webphere Studio Application Developer.
    But when it is deployed to IBM Websphere in our test environment, it spits out the following error on start up.
    RVE0100E: Did not realize  init() exception thrown by servlet action: javax.servlet.UnavailableException: Parsing error processing resource path
         at org.apache.struts.action.ActionServlet.handleConfigException(ActionServlet.java:1035)
         at org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:1014)
         at org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:955)
         at org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
         at javax.servlet.GenericServlet.init(GenericServlet.java:258)
         at com.ibm.servlet.engine.webapp.StrictServletInstance.doInit(ServletManager.java:802)
         at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._init(StrictLifecycleServlet.java:141)
         at com.ibm.servlet.engine.webapp.PreInitializedServletState.init(StrictLifecycleServlet.java:254)
         at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.init(StrictLifecycleServlet.java:107)
         at com.ibm.servlet.engine.webapp.ServletInstance.init(ServletManager.java:388)
         at javax.servlet.GenericServlet.init(GenericServlet.java:258)
         at com.ibm.servlet.engine.webapp.ServletManager.addServlet(ServletManager.java:84)
         at com.ibm.servlet.engine.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java:211)
         at com.ibm.servlet.engine.webapp.WebAppServletManager.loadAutoLoadServlets(WebAppServletManager.java:350)
         at com.ibm.servlet.engine.webapp.WebApp.loadServletManager(WebApp.java:1217)
         at com.ibm.servlet.engine.webapp.WebApp.init(WebApp.java:145)
         at com.ibm.servlet.engine.srt.WebGroup.loadWebApp(WebGroup.java:259)
         at com.ibm.servlet.engine.srt.WebGroup.init(WebGroup.java:168)
         at com.ibm.servlet.engine.ServletEngine.addWebApplication(ServletEngine.java:857)
         at com.ibm.ws.runtime.WebContainer.install(WebContainer.java:43)
         at com.ibm.ws.runtime.Server.startModule(Server.java:618)
         at com.ibm.ejs.sm.active.ActiveModule.startModule(ActiveModule.java:511)
         at com.ibm.ejs.sm.active.ActiveModule.startAction(ActiveModule.java:355)
         at com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:948)
         at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:137)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java:93)
         at com.ibm.ejs.sm.active.ActiveObject.invokeContainedObject(ActiveObject.java:686)
         at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java:110)
         at com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java:62)
         at com.ibm.ejs.sm.agent._AdminAgentImpl_Tie._invoke(_AdminAgentImpl_Tie.java:73)
         at com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(ExtendedServerDelegate.java:532)
         at com.ibm.CORBA.iiop.ORB.process(ORB.java:2450)
         at com.ibm.CORBA.iiop.OrbWorker.run(OrbWorker.java:186)
         at com.ibm.ejs.oa.pool.ThreadPool$PooledWorker.run(ThreadPool.java:104)
         at com.ibm.ws.util.CachedThread.run(ThreadPool.java(Compiled Code)) I have seen similar problems reported in forums and the cause is usually a problem with the struts-config file. But I have tried stripping our struts-conifg file right back and it still gives the same error. Our complete struts-config file is as follows:
    <?xml version="1.0" encoding="ISO-8859-1" ?>
    <!DOCTYPE struts-config PUBLIC "-//Apache Software Foundation//DTD Struts Configuration 1.1//EN" "http://jakarta.apache.org/struts/dtds/struts-config_1_1.dtd">
    <!--
         This is the Struts configuration file for the example application,
         using the proposed new syntax.
         NOTE:  You would only flesh out the details in the "form-bean"
         declarations if you had a generator tool that used them to create
         the corresponding Java classes for you.  Otherwise, you would
         need only the "form-bean" element itself, with the corresponding
         "name" and "type" attributes.
    -->
    <struts-config>
      <!-- ========== Form Bean Definitions =================================== -->
         <form-beans>
              <form-bean name="cardDetailForm" type="au.com.hbf.asktedadmin.form.CardDetailForm">
              </form-bean>
              <form-bean name="cardCategoryDetailForm" type="au.com.hbf.asktedadmin.form.CardCategoryDetailForm">
              </form-bean>
              <form-bean name="pollDetailForm" type="au.com.hbf.asktedadmin.form.PollDetailForm">
              </form-bean>
              <form-bean name="searchCategoryDetailForm" type="au.com.hbf.asktedadmin.form.SearchCategoryDetailForm">
              </form-bean>
         </form-beans>
      <!-- ========== Global Forward Definitions ============================== -->
      <!-- ========== Action Mapping Definitions ============================== -->
         <action-mappings>
         <action
             path="/home"
             type="au.com.hbf.asktedadmin.actions.HomeAction">
              <forward name="success" path="/home.jsp">
                   <description>Home Page</description>
              </forward>
              <forward name="error" path="/error.jsp">
              </forward>
          </action>     
         <action
             path="/viewCards"
            type="au.com.hbf.asktedadmin.actions.CardViewAction">
             <forward name="success" path="/viewCards.jsp"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/viewArchivedCards"
            type="au.com.hbf.asktedadmin.actions.ArchivedCardViewAction">
             <forward name="success" path="/viewArchivedCards.jsp"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/getCard"
             name="cardDetailForm"
             validate="false"
             scope="session"
             input="/viewCards.jsp"
            type="au.com.hbf.asktedadmin.actions.CardUpdateAction">
             <forward name="success" path="/cardDetails.jsp"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/updateCard"
             name="cardDetailForm"
             validate="true"
             scope="session"
             input="/cardDetails.jsp"
            type="au.com.hbf.asktedadmin.actions.CardUpdateAction">
             <forward name="success" path="viewCards.do"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/viewCardCategories"
            type="au.com.hbf.asktedadmin.actions.CardCategoryViewAction">
             <forward name="success" path="/viewCardCategories.jsp"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/getCardCategory"
             name="cardCategoryDetailForm"
             validate="false"
             scope="session"
             input="/viewCardCategories.jsp"
            type="au.com.hbf.asktedadmin.actions.CardCategoryUpdateAction">
             <forward name="success" path="/cardCategoryDetails.jsp"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/updateCardCategory"
             name="cardCategoryDetailForm"
             validate="true"
             scope="session"
             input="/cardCategoryDetails.jsp"
            type="au.com.hbf.asktedadmin.actions.CardCategoryUpdateAction">
             <forward name="success" path="viewCardCategories.do"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/viewPolls"
            type="au.com.hbf.asktedadmin.actions.PollViewAction">
             <forward name="success" path="/viewPolls.jsp"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/getPoll"
             name="pollDetailForm"
             validate="false"
             scope="session"
             input="/viewPolls.jsp"
            type="au.com.hbf.asktedadmin.actions.PollUpdateAction">
             <forward name="success" path="/pollDetails.jsp"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/addPoll"
             name="pollDetailForm"
             validate="false"
             scope="session"
             type="au.com.hbf.asktedadmin.actions.PollUpdateAction">
             <forward name="success" path="/pollDetails.jsp"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/updatePoll"
             name="pollDetailForm"
             validate="true"
             scope="session"
             input="/pollDetails.jsp"
            type="au.com.hbf.asktedadmin.actions.PollUpdateAction">
             <forward name="success" path="viewPolls.do"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/listSearchCategories"
            type="au.com.hbf.asktedadmin.actions.SearchCategoryListAction">
             <forward name="success" path="/listSearchCategories.jsp"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/getSearchCategory"
             name="searchCategoryDetailForm"
             validate="false"
             scope="session"
             input="/listSearchCategories.jsp"
            type="au.com.hbf.asktedadmin.actions.SearchCategoryUpdateAction">
             <forward name="success" path="/searchCategoryDetails.jsp"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/updateSearchCategory"
             name="searchCategoryDetailForm"
             validate="false"
             scope="session"
             input="/searchCategoryDetails.jsp"
            type="au.com.hbf.asktedadmin.actions.SearchCategoryUpdateAction">
             <forward name="success" path="listSearchCategories.do"></forward>
              <forward name="continue" path="/searchCategoryUrls.jsp"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         <action
             path="/updateSearchCategoryUrl"
             name="searchCategoryDetailForm"
             validate="false"
             scope="session"
             input="/searchCategoryUrls.jsp"
            type="au.com.hbf.asktedadmin.actions.SearchCategoryUrlUpdateAction">
             <forward name="success" path="/searchCategoryDetails.jsp"></forward>
              <forward name="error" path="/error.jsp"></forward>
         </action>     
         </action-mappings>
         <controller processorClass="au.com.hbf.hef.web.struts.request.StrutsRequestProcessor"/>
      <!-- ========== Message Resources Definitions =========================== -->
         <message-resources parameter="au.com.hbf.asktedadmin.resources.AskTedAdminApplicationResources"/>
    </struts-config>

    I don't think this is the problem.
    The AskTedAdminApplicationResources is included in the war under WEB-INF\classes\au\com\hbf\asktedadmin\resource\AskTedAdminApplicationResources.properties
    And like I say, it works fines in the Studio Developer, but fails when deployed to websphere.

  • Oracle Coherence vs IBM WebSphere Extended Deployment

    Hi All,
    Does anyone compared the features of oracle coherence vs IBM WebSphere Extended Deployment Grid? If so, Which one is best among them.
    Thanks in advance,
    Shiva

    Hi All,
    Does anyone compared the features of oracle coherence vs IBM WebSphere Extended Deployment Grid? If so, Which one is best among them.
    Thanks in advance,
    Shiva

  • Can IBM WebSphere be used as a web server?

    I have heard that IBM WebSphere be used as a web server.
    Is this true?
    If so , can an SAP EP7 be used as a web server since Websphere is a portal as well.
    Thanks!

    Hi,
    Apache in general doesn't have a good application focus, so most configuration in httpd.conf is for all applications (which to apache are only folders).
    It does however use virtual host that are commonly used to separate configuration between applications.
    For SAP NetWeaver Java (all java stackbased systems can be web servers) the configuration is either done at the virtual host level or at the Java EE application level.
    The HTTP Provider ( http://help.sap.com/saphelp_nw04s/helpdata/en/8c/541eed26ef934cb161ed0b65a050ee/frameset.htm) provides you with the possibility of setting up virtual hosts.
    These virtual hosts can have a root directory which is similar to the DocumentRoot command in httpd.conf: basically it tells you were the .html files are.
    Note that the HTTP provide cannot process dynamic files(like .jsp, .php etc), only static HTML files
    The Java EE application use the various deployment descriptors for WAR and EAR for defining security settings, servlet settings (can replace need for rewrite rules) and everything else needed for the application to run.
    Java EE application can have dynamic files in the form of .jsp and it should be trivial to create a wrapper Java EE application where you just put your html files in a folder in order to mimic a web server.
    However, you should redeploy the application when you make changes to the html files in order to make sure the application is stored correctly in the database and synchronized to all cluster nodes.
    Regards
    Dagfinn

  • JSF on IBM WebSphere Web Server 5.1.0.3

    Hello...
    I did not get any response from IBM yet... so i am trying my luck with you...
    Can IBM WebSphere Web Application Server 5.1.0.3 with J2EE v1.4 support JavaServer Faces 1.0?
    Regards,
    B.

    Hello,
    Thanks for your reply.
    However i need to know whether WebSphere v5.1.0.3 on which there is J2EE v1.4 is specifically compatible with JSF 1.0
    And i am developing in Oracle JDeveloper J2EE Edition. I will probably deploy my app in WAR format
    Regards,
    B.

  • Can not deploy application on websphere 6.0

    Hi all,
    I use Jdeveloper(10.1.2) and Jheadstart(10.1.2) converted a oracle form to J2EE.It can run on Oracle Application Server and Tomcat.I try to deploy it on websphere 6.0,after i added ADF runtime *.jar file into {WAS_HOME}\lib\ext manually,websphere can not work,error message as follows:
    ADMU3200I: Server launched. Waiting for initialization status.
    ADMU3011E: Server launched but failed initialization. Server log files should
    contain failure information.
    java.lang.reflect.InvocationTargetException
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
         at java.lang.reflect.Method.invoke(Method.java:391)
         at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)
    Caused by: com.ibm.websphere.management.exception.AdminException: Failed while trying to start the Windows Service, retCode = -1
         at com.ibm.ws.management.tools.WindowsService.doWASServiceAction(WindowsService.java:247)
         at com.ibm.ws.management.tools.WsServerLauncher.execWithWinService(WsServerLauncher.java:150)
         at com.ibm.ws.management.tools.WsServerController.executeUtilityOnWindows(WsServerController.java:129)
         at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:114)
         ... 6 more
    when i remove all jar file from {WAS_HOME}\lib\ext, webspher works well.
    And i can not find bc4j_jclient_common.jar from %JDEV_HOME%BC4J\lib.
    so how can I deal with this problem?Thanks in advance!!
    Best regards,
    Appcat
    Message was edited by:
    Appcat

    JDeveloper 10.1.3 does not include bc4j_jclient_common.jar
    Re: BC4J Library bc4j_jclient_common.jar not provided in JDeveloper 10.1.3

  • JMS Receiver Adapter - com.ibm.websphere.naming.WsnInitialContextFactory

    Hello experts,
    I am trying to configure JMS Adapter to Access Websphere Application Server via JNDI. The configuration is as follow:
    Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
    Connection Factory: jms/messageQueueCF
    Server URL: iiop://ammtnode.iubs.intra:2809/
    Queue Name: jms/EXT_INPUT_QUEUE
    I deployed all required jar files but Iu2019m still unable to connect to WAS because adapter cannot initialize ORB:
    javax.naming.NamingException: Failed to initialize the ORB
    I wrote a small java class to check where the problem was:
    ============================================================================
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialContextFactory");
    env.put(Context.PROVIDER_URL, "iiop://ammtnode.iubs.intra:2809/");
    env.put("java.naming.corba.orb",org.omg.CORBA.ORB.init((String[])null,null));
    Context jndiContext = null;
    try {
    jndiContext = new InitialContext(env);
    ConnectionFactory connectionFactory = (ConnectionFactory) jndiContext.lookup("jms/messageQueueCF");
    Connection qConn = connectionFactory.createConnection();
    Session qSession = qConn.createSession(false,Session.AUTO_ACKNOWLEDGE);
    Queue q = (Queue) jndiContext.lookup("jms/EXT_INPUT_QUEUE");
    MessageProducer producer = qSession.createProducer(q);
    TextMessage message = qSession.createTextMessage();
    message.setText(text);
    producer.send(message);
    producer.close();
    qSession.close();
    qConn.close();
    } catch (Exception e) {
         e.printStackTrace();
    ============================================================================
    I got the same error until I wrote this line:
    env.put("java.naming.corba.orb",org.omg.CORBA.ORB.init((String[])null,null));
    And everything worked fine. Now I want to do the same in my JMS Receiver adapter but I donu2019t know how to introduce this line in the Initial Context Environment. I tried as JMS additional parameters and additional properties as well. However, nothing worked. Does anybody know what Iu2019m doing wrong?
    Thank you in advance!

    Here I post the entire error:
    0#0#Warning##Java###Catching #1#com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up connection fact
    oryjms/messageQueueCF, for profile: ConnectionProfile of channel: CC_I002_AMM_JmsReceiveron node: 5949650 having object id: 0
    360697bc61b3666aba07a2708ca095a: javax.naming.NamingException: Failed to initialize the ORB
            at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:134)
            at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:247)
            at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:185)
            at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:170)
            at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:153)
            at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:279)
            at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:166)
            at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:411)
            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
    Caused by: javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class
    com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:libra
    ry:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
            at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
            at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
            at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
            at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
            at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
            at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
            ... 11 more
    Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
    patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
    LoaderAT131b92e6ATalive
            at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
            at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
            at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
            at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
            at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
            at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
            ... 19 more
    Caused by:
    javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class com.sap.eng
    ine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:library:com.sap.
    aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
            at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
            at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
            at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
            at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
            at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
            at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
            ... 11 more
    Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
    patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
    LoaderAT131b92e6ATalive
            at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
            at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
            at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
            at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
            at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
            at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
            ... 19 more
    Caused by:
    javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class com.sap.eng
    ine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:library:com.sap.
    aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
            at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
            at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
            at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
            at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
            at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
            at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
            at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:247)
            at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:185)
            at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:170)
            at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:153)
            at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:279)
            at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:166)
            at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:411)
            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
    Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
    patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
    LoaderAT131b92e6ATalive
            at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
            at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
            at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
            at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
            at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
            at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
            ... 19 more

  • JMS adapter fails to open IBM WebSphere MQ Manager V6 Remote Queue

    Hello,
    We are trying to connect to a Remote Queue with the SAP PI 7.0 SP9 JMS adapter to IBM WebSphere MQ V6 on Linux SLES9 x86_64.
    We did deployed the JMS-adapter with the V6 native libaries on SAP PI.
    In the Communication Channel we use the Adapter Type = JMS, Sender, Transport Protocol = WebSphereMQ(non-JMS).
    The MQ Queue Manager is on the same server as SAP PI so we use localhost, Server Port, Queue Manager Name, Channel Name and JMS Queue Name
    The <sid>adm user is a member of the mqm group.
    When I check the RWB I see this fault message:
    Error during channel initialization; exception trace: javax.jms.JMSException: <b>MQJMS2008: failed to open MQ Queue</b> at ...
    and also
    com.ibm.mq.MQException: <b>MQJE001: Completion Code 2, Reason 2045</b>
    When we lookup the reason 2045 we get this explaination on MQ:
    MQRC_OPTION_NOT_VALID_FOR_TYPE
    We also have a type = Receiver Communication Channel on the same MQ Queue Manager that one is working fine.
    Please advise!
    Best regards,
    Mike Laanen

    Mike,
    check whether the Queues are created and activated if it done. then check whether you have authorization for those queues.
    Regards
    Sreeram.G.Reddy

  • Apache Tomcat vs IBM Websphere

    Hi,
    In our current deployment, I am using Apache Tomcat as the Java Application Server that comes bundled with Hyperion Planning 9.3.1 suite of applications. The documentation also suggests Oracle Application Server, IBM Websphere and BEA WebLogic. Currently the application stack is Hyperion Planning only, with Financial Reporting for the reporting needs.
    For our current situation, we have shortlisted between using the bundled Apache Tomcat or IBM Websphere. For comparison I wanted to know how stable Apache Tomcat is in general compared to websphere? How many concurrent users can it handle? Are there any specific limitations of Apache Tomcat that I should consider? Can someone list the major pros and cons of each?
    Thanks in advance
    Shehzad

    I agree with Jake.. Tomcat can handle much more than a few users. Whether it can handle the load for your environment may depend on your usage pattern, size of forms, etc.
    We typically use Tomcat for our Dodeca product that uses the Java API to talk to Essbase. It doesn't product 'forms' but rather just transfers data via XML between the client and server. With that product, we do have one customer that is serving appx 7,000 users on a single Tomcat server. In that case, however, the usage pattern is that field users log in daily (or sometimes weekly) and run a few reports (that retrieve data via XML).
    Note that Tomcat has a configuration parameter in the server.xml file to set the max number of threads that can be spawned by the process. You may want to tune that parameter if you decide to run Tomcat in production (and absolutely be sure to give it more heapsize in the java options).
    Tim Tow
    Applied OLAP, Inc

  • XI to IBM Websphere Default JMS Provider with JNDI

    Hello everybody!
    We face a problem with connecting SAP XI to IBM WebSphere Default JMS Provider (need to send a message from XI to WebSphere JMS and receive the response).
    We have the following versions installed:
        SAP XI: 7.0 SP8 , Sun JDK 1.4.2
        IBM WebSphere: IBM WebSphere Application Server ND, 6.0.2.17, J2RE 1.4.2 IBM
    We cannot set the JMS adapter of SAP XI for conecting with IBM WebSphere Default JMS Provider. The Communication Channel has erroneous state (at runtime) and the Communication Channel Monitoring tool displays the error message as described below (under "Variant 1" and "Variant 2" sub-headings) depending on the settings performed. 
    For connecting, the following JMS-provider settings were used at IBM WebSphere side:
       JMS Providers: Default Messaging Provider
       Queue Connection Factories: name:QueueConnectionFactory, jndi:jms/QueueConnectionFactory, provider: Default Messaging Provider
       Queues: name Queue, jndi: jms/Queue, provider: Default Messaging Provider
    The XI communication channel (and associated JMS-adapter) was set as Variants 1 and 2 show. Settings for both cases and received error messages were the following:
    <b>Variant 1.</b>
        Adapter type: JMS
        Type: Receiver
        JMS Provider: Access JMS Provider with JNDI (Java Naming and Directory Interface)
        JNDI Lookup Name of QueueConnectionFactory:  jms/QueueConnectionFactory
        JNDI Lookup Name of JMS Queue: jms/Queue
        Name of JNDI Initial Context Factory: com.sap.engine.services.jndi.InitialContextFactoryImpl
        JNDI Server Address: iiop://WEBSPHERE.HOST:2809/ 
        As the result, the Communication Channel Monitoring displays that the channel has erroneous state and the following error message is written:
        "Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of jms/QueueConnectionFactory.
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)"
    <b>Variant 2</b>
        The same settings as in Variant 1 above, were used and additionally the following settings were done:
        - Name of JNDI Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
        - The archive aii_af_jmsproviderlib.sda containing libraries required by WsInitialContextFactory, was deployed to the SAP WebAS where the XI is running. Those libraries were taken from WebSphere Application Server Pluggable Application Client installation package (described in the article "WebSphere Application Server Pluggable Application Client" located at http://www-128.ibm.com/developerworks/websphere/library/techarticles/0409_bhogal/0409_bhogal.html)
        - Also, as it is recommended in the referred article, the files required by IBM's iiop protocol (ibmext.jar ibmorb.jar ibmorbapi.jar) were put to the folder jre/lib/endorsed of the server(Sun JVM 1.4.2 is used by SAP WebAS / XI).
        As the result, the Communication Channel Monitoring displays that the channel has erroneous state as well and the following error message is written:
       "No adapter registered for this channel"
    We have not found the recommended solution either in SDN forums or in Internet in general. Is it yet possible to connect SAP XI to IBM WebSphere Default JMS Provider having mentioned product versioning? If yes, what settings have to be performed?

    IBM Websphere Default JMS Provider which is installed alongwith the application server is nothing but a scaled down version of the IBM WebSphere MQSeries. you should be able to connect to it with the same settings that can be used for a separate MQSeries server connectivity from XI.

  • IBM WebSphere Connection

    Hello.
    I've been trying to add a server to the runtime tab of the Java Studio Enterprise 8. The location of the IBM Websphere installation directory is in another pc(our server pc). when i try to connect i would either get an null pointer exception or i cannot deploy my web applications on the server.
    can anyone help me with this. thanks.

    What have you specified for your installation directory?
    As I remember it still needs the local installation of WebSphere server to access the remote server.

  • * IBM Websphere Vs Oracle's Weblogic server *

    IBM Websphere Vs Oracle's Weblogic server
    Can ODI run on IBM Websphere?
    How feasible is it to shift ODI from Oracle Web logic to IBM Websphere?
    What challenges , efforts required in ODI code to do so?
    Please suggest.
    Thanks in Advance.
    Regards,
    Dinesh.

    1. Well for your 1st question I believe you can.
    2. I believe it will go fine because you just need one application server to deploy your ee agent.
    3. I have never tried IBM websphere as an application sewrver in ODI but it shouldnt be that much completed as you are thinking. Better you do R&D in your local system. Also I am not sure about the issues you will face in future. ( for ex maple PermGen errors, issues in clustering etc)
    Thanks

  • Xmlparserv2.jar cause IBM WebSphere v5.1 down.

    Anyone knows:
    I have a j2ee project based on IBM WebSphere v5.1 + Oracle DB 10g(XMLDB included).There's a big trouble bother me.
    My project used Oracle xml implemention,such as DOM parser included in xmlparserv2.jar.and when i deploy my project to WAS(WebSphere Application Server),it throws errors and can not startup normally.it's sounds that WAS cann't determine which xml implemention it should choose:
    Error message below:
    ==============================================
    *** 启动服务器 ***
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O java.net.MalformedURLException: unknown protocol: f
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at java.net.URL.<init>(URL.java(Compiled Code))
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at java.net.URL.<init>(URL.java(Compiled Code))
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at java.net.URL.<init>(URL.java:450)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:214)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:177)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.xml.BaseFactory.load(BaseFactory.java:191)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.xml.BaseFactory.load(BaseFactory.java:173)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.WASProduct.loadVersionInfo(WASProduct.java:1876)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.WASProduct.getVersionInfo(WASProduct.java:1829)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.WASProduct.getPlatform(WASProduct.java:845)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.component.TraceImpl.initialize(TraceImpl.java:59)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at java.lang.reflect.Method.invoke(Method.java:386)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    ************ Start Display Current Environment ************
    Host Operating System is Windows XP, version 5.1
    Java version = J2RE 1.4.1 IBM Windows 32 build cn1411-20031011 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
    was.install.root = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51
    user.install.root = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51
    Java Home = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51\java\jre
    ws.ext.dirs = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/java/lib;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/classes;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/classes;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/ext;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/web/help;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime;F:\document\musicool\CVS\libs\xsdbeans.jar;F:/Program_Files/IBM/SQLLIB/java/db2java.zip;f:/Program_Files/IBM/WebSphere_Studio/wstools/eclipse/plugins/com.ibm.etools.webservice_5.1.1/runtime/worf.jar
    Classpath = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/properties;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/properties;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/bootstrap.jar;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/j2ee.jar;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/lmproxy.jar;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/urlprotocols.jar;F:\document\musicool\CVS\libs\workflow.jar;F:\document\musicool\CVS\libs\DBClient.jar;F:\document\musicool\CVS\libs\log4j-1.2.8.jar;F:\document\musicool\CVS\libs\log.jar;F:\document\musicool\CVS\libs\utility.jar;F:\document\musicool\CVS\libs\webwork.jar;F:\document\musicool\CVS\libs\xdb.jar;F:\Oracle\product\10.1.0\Client_1\lib\xsu12.jar;f:/Program_Files/IBM/WebSphere_Studio/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1/runtime/wteServers.jar;f:/Program_Files/IBM/WebSphere_Studio/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1/runtime/wasToolsCommon.jar
    Java Library path = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/java/bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/java/jre/bin;F:\Program_Files\IBM\WebSphere_Studio\eclipse\jre\bin;.;F:\Program_Files\IBM\WebSphere_Studio\eclipse\jre\bin;F:\eclipse\301\bpelz_install\bin;f:\Oracle\product\10.1.0\Client_1\bin;f:\Oracle\product\10.1.0\Client_1\jre\1.4.2\bin\client;f:\Oracle\product\10.1.0\Client_1\jre\1.4.2\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;f:\Program_Files\IBM\WebSphere_Studio\extras\bin;f:\Program_Files\IBM\WebSphere_Studio\bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51\java\bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51\java\jre\bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51\java\jre\bin\classic;f:\Program_Files\UltraEdit;f:\Program_Files\SecureCRT;F:\PROGRA~1\IBM\SQLLIB\BIN;F:\PROGRA~1\IBM\SQLLIB\FUNCTION;F:\PROGRA~1\IBM\SQLLIB\SAMPLES\REPL;C:\Program Files\Common Files\Ulead Systems\MPEG;;;;;f:\Program_Files\Real\Helix_Producer_Plus;F:\Program_Files\Rational\common;F:\eclipse\301\bpelz_install\bin;f:\Program_Files\UltraEdit
    ************* End Display Current Environment *************
    [05-5-2 12:06:49:938 CST] 3d455614 ManagerAdmin I TRAS0017I: 启动跟踪状态是 *=all=disabled。
    [05-5-2 12:06:50:609 CST] 3d455614 AdminInitiali A ADMN0015I: AdminService 初始化
    [05-5-2 12:06:50:656 CST] 3d455614 MBeanDescript W ADMN0001W: 无法è¯æ³•åˆ†æž MBean 描述符文件 com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: 无法è¯æ³•åˆ†æž MBean 描述符文件 com/ibm/ws/management/descriptor/xml/JVM.xml。
    at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
    at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
    at java.lang.reflect.Method.invoke(Method.java:386)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    。
    [05-5-2 12:06:50:688 CST] 3d455614 WsServer E WSVR0003E: 服务器 server1 无法启动
    com.ibm.ws.exception.ConfigurationError: Problem initializing AdminImpl:
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:413)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
    at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
    at java.lang.reflect.Method.invoke(Method.java:386)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    Caused by: com.ibm.ws.exception.ConfigurationWarning: Problem registering JVM MBean.
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:283)
    ... 11 more
    Caused by: com.ibm.websphere.management.exception.AdminException: ADMN0005E: 无法激活 MBean：类型 JVM、合作者 [email protected]c1619、配置标识 JVM 和描述符 null。
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:289)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
    ... 11 more
    Caused by: com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: 无法è¯æ³•åˆ†æž MBean 描述符文件 com/ibm/ws/management/descriptor/xml/JVM.xml。
    at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
    ... 13 more
    ---- Begin backtrace for nested exception
    com.ibm.ws.exception.ConfigurationWarning: Problem registering JVM MBean.
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:283)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
    at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
    at java.lang.reflect.Method.invoke(Method.java:386)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    Caused by: com.ibm.websphere.management.exception.AdminException: ADMN0005E: 无法激活 MBean：类型 JVM、合作者 [email protected]c1619、配置标识 JVM 和描述符 null。
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:289)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
    ... 11 more
    Caused by: com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: 无法è¯æ³•åˆ†æž MBean 描述符文件 com/ibm/ws/management/descriptor/xml/JVM.xml。
    at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
    ... 13 more
    ---- Begin backtrace for nested exception
    com.ibm.websphere.management.exception.AdminException: ADMN0005E: 无法激活 MBean：类型 JVM、合作者 [email protected]c1619、配置标识 JVM 和描述符 null。
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:289)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
    at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
    at java.lang.reflect.Method.invoke(Method.java:386)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    Caused by: com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: 无法è¯æ³•åˆ†æž MBean 描述符文件 com/ibm/ws/management/descriptor/xml/JVM.xml。
    at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
    ... 13 more
    ---- Begin backtrace for nested exception
    com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: 无法è¯æ³•åˆ†æž MBean 描述符文件 com/ibm/ws/management/descriptor/xml/JVM.xml。
    at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
    at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
    at java.lang.reflect.Method.invoke(Method.java:386)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    [05-5-2 12:06:50:703 CST] 3d455614 WsServer E WSVR0009E: 启动期间发生错误
    =================================
    Best Regard.
    Musicool

    I had this issue too. I removed all non-Oracle classes (javax, org.w3c) from the jar file and things then worked as expected. Basically, these javax and w3c files were duplicating versions already existing in the WPS classpath (I presume) and were causing the failure.
    Hope this helps.
    -Tim

  • Blog post on deploying mapviewer in websphere

    For those who may be interested, LJ's recent blog post describes how to deploy mapviewer (11.1.1.5) on websphere 7.
    http://oraclemaps.blogspot.com/2011/07/deploying-mapviewer-on-ibm-websphere-7.html

    I am sorry you feel uncomfortable about the license terms. Being a software company owner I know the difficulty of figuring out the license restrictions of various software components. However that is exactly I provide ExpressionFlow example code with creative commons attribution license. The creative commons licenses do not restrict where the example code can be used and the terms are rather widely known. Shoud example code have no license terms, you would not know how you would be allowed to use or share the code. Now you have it black-on-white.
    Human-readable summary of the Creative Commons Attribution 3.0 Unported license:
    You are free:
    to Share — to copy, distribute and transmit the work
    to Remix — to adapt the work
    Under the following conditions:
    Attribution —
    You
    must attribute the work in the manner specified by the author or
    licensor (but not in any way that suggests that they endorse you or
    your use of the work).
    With the understanding that:
    Waiver
    Any of the above conditions can be waived if you get permission from the copyright holder.
    Other Rights
    In no way are any of the following rights affected by the license:
    Your fair dealing or fair use rights;
    The author's moral rights;
    Rights other persons may have either in the work itself or in how the work is used, such as publicity or privacy rights.
    Notice
    — For any reuse or distribution, you must make clear to others the
    license terms of this work. The best way to do this is with a link to
    this web page.
    Tomi Maila

Maybe you are looking for

  • Questions about Lumia Line and Windows Phone 8

    hey , i am using Nokia 701, a Symbian smarphone i love very much, but would like to know more about the WP OS and how it fares against it. If u have answers for the questions below or even better - if u own a Lumia 720, which i find interesting, plea

  • Issue in creating a SiteMap application

    Hi Experts,     I am working on creating a Sitemap application for our portal users.I am following the below link http://help.sap.com/saphelp_nw73ehp1/helpdata/en/49/e45186272f7517e10000000a42189b/content.htm i have added the com.sap.portal.navigatio

  • Bapi/Idoc to Webservice

    Hi experts, I need help in sending purchase orders from SAP using Bapi's or Idoc's to a 3rd party system using webservice, but I need to call  two webservices in the 3rd party system(target) one after the other.To be precise once  the 1st webservice

  • IPhone 6+ Controls Itself..?

    Hi! In December, I received and iPhone 6+ for Christmas. It was a really expensive gift, and it's frustrating that I'm already having a major problem with it. Everything that I try to do on my phone is interrupted! It operates on iOS 8.1.2, which I'v

  • Report Painter Elements

    Dear friends: I am working on 4.7 v. I have copied a report and making changes to meet my requirments. In report painter, I selected Edit - Hidden rows - delete. Some of the elments i am unable to delete. The system shows the messages " You cannot de