IF WebSphere is down?

Which Java class gives me the information about, whether webserver(websphere) is down or up?
Pls Help me.
Muthu

You can try to connect to the port the web server is supposed to listen with the creation of a (client) Socket:

Similar Messages

  • Websphere shut down

    I am calling a jsp page in websphere, for example
    "one.jsp"
    <html>
    <script>
    function first(){
    <jsp:forward page="one.jsp"/>
    </script>
    while this page is loading the server is shutdown automatically.
    answers will be appreciated

    You can not put the jsp:forward in a client side function. You can set the current page location to the new url but this wil be a new request

  • 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

  • Problem with Open document SSO using websphere.

    Hi All,
    I have a issue,
    We configured AD SSO using websphere and its working fine but when we try to login to the open document SSO using websphere it prompting for login credentials.
    Is there any steps needed for configure open document SSO using websphere.
    We made all the changes in web.xml file for the Open Document ,same as in Infoview web.xml file.
    When we launch the Open Document, it prompts for the login screen, we get username and passwd fields we do not get the authentication drop down,if we give the AD credentials , we get "Enterprise Authentication error" .We feel the default authentication mode is taken as "Enterprise".
    We have made changes in the web.xml for open document to have authentication.dafault as "secWinAD", also ,for test purpose we made the authentication. visible as "true" but the changes were not taken, we have redeployed the war files.
    Any one please help on this.
    Environment Details-
    BOBJ XI R3.1 SP2
    Web Sphere 6.1.0.25  .
    Thank you in advance.
    Thanks & Regards,
    Bill.

    The same settings in the infoviewapp web.xml must be applied on the opendocument web.xml. Also you must be on XI 3.1 FP1 or higher. There is currently an Edge issue being investigated.
    Regards,
    Tim

  • Weblogic 9.2 ESB integration with Websphere MQ 6.0 throws MQJMS1016

    Hi
              We have setup a Websphere MQ integration where we have a weblogic server as the client.
              The MQ setup is a clean MQ installation no WAS is installed.
              Here are the MQ information
              OS: Windows 2003 R2 Entreprise Edition SP1
              MQ:
              Name: WebSphere MQ
              Version: 6.0.2.1
              CMVC level: p600-201-070323
              BuildType: IKAP - (Production)
              Here are the Weblogic server information
              OS: Windows 2003 R2 Entreprise Edition SP1
              weblogic:
              Name: Weblogic ESB
              VERSION: 9.2
              JDK: jdk150_06
              We have experience that the integration works fine. Until it becomes weekend and there are no activity between the weblogic server and the MQ.
              That is when we get the message:
              ####<2007-07-09 07:53:45 CEST> <Notice> <StdErr> <b00011100938> <esbserver> <asyncDelivery30> <<WLS Kernel>> <> <> <1183960425832> <000000> <2007.07.09 07:53:45 MQJMS1016E an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException>
              ####<2007-07-09 07:53:45 CEST> <Error> <ALSB Kernel> <b00011100938> <esbserver> <asyncDelivery30> <<anonymous>> <> <> <1183960425832> <BEA-380001> <Exception on TransportManagerImpl.sendMessageToService, com.bea.wli.sb.transports.TransportException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException
              com.bea.wli.sb.transports.TransportException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException
              at com.bea.wli.sb.transports.TransportException.newInstance(TransportException.java:146)
              at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$SendAction.run(JmsOutboundMessageContext.java:845)
              at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:514)
              at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:620)
              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:585)
              at com.bea.wli.sb.transports.Util$1.invoke(Util.java:65)
              at $Proxy45.sendMessageAsync(Unknown Source)
              at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:137)
              at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:487)
              at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:354)
              at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:559)
              at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:488)
              at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:127)
              at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:319)
              at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:108)
              at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:6
              at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:834)
              at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:194)
              at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:75)
              at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:669)
              at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:668)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
              at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:666)
              at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:304)
              at com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.java:108)
              at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
              at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
              at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
              at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2804)
              at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)
              at java.lang.Thread.run(Thread.java:595)
              At the time we get this error we also do a thread dump to find the asyncDelivery30 and we can see what happens:
              "asyncDelivery30" RUNNABLE native
              java.net.SocketInputStream.socketRead0(Native Method)
              java.net.SocketInputStream.read(SocketInputStream.java:129)
              java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
              java.io.BufferedInputStream.read(BufferedInputStream.java:235)
              java.io.DataInputStream.readInt(DataInputStream.java:353)
              com.ibm.mq.MQInternalCommunications.timedReadInt(MQInternalCommunications.java:2698)
              com.ibm.mq.MQInternalCommunications.receiveBytesFaster(MQInternalCommunications.java:2796)
              com.ibm.mq.MQInternalCommunications.receive(MQInternalCommunications.java:1149)
              com.ibm.mq.MQSESSIONClient.lowLevelComms(MQSESSIONClient.java:2802)
              com.ibm.mq.MQSESSIONClient.MQGET(MQSESSIONClient.java:1833)
              com.ibm.mq.MQQueue.getMsg2Int(MQQueue.java:1209)
              com.ibm.mq.MQQueue.getMsg2(MQQueue.java:1066)
              com.ibm.mq.jms.MQMessageConsumer.getMessage(MQMessageConsumer.java:3194)
              com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2773)
              com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)
              java.lang.Thread.run(Thread.java:595)
              The message we get from the MQ is this :
              09-07-2007 07:54:05 - Process(7772.406) User(LETMQTESTUser) Program(amqrmppa.exe)
              AMQ9208: Error on receive from host b00011100938 (10.11.64.5).
              EXPLANATION:
              An error occurred receiving data from b00011100938 (10.11.64.5) over TCP/IP.
              This may be due to a communications failure.
              ACTION:
              The return code from the TCP/IP (recv) call was 10054 (X'2746'). Record these
              values and tell the systems administrator.
              If anyone have some input/help concerning this problem. That would really be great

    - The NullPointerException looks like its being generated due to some sort of bug in MQ, so you might have some luck by contacting IBM and/or ensuring your MQ version has all the latest patches.
              - The error is being reported by WLI, which has its own newsgroup - so you might try posting there. I'm guessing that WLI tries to recover from the MQ error by closing down and re-establishing its connections to MQ.
              Tom

  • Disabling load balancing in WebSphere

    Hello,
    We've come across this problem just after we deployed our application to a clustered environment (probably a short sight on our part while designing). This is our situation:
    Environment: WebSphere 6.1, EJB 2.1
    Problem: We use the EJB Timer service for executing some business logic periodically with in our stateless session bean application. We have multiple timers within the same EJB that do stuff dynamically with the same code based on the parameters. However, we don't want the timers to come up automatically when the EJB application (like doing it with in contextInitialized) comes up because we want to bring the timers up and down in a more controlled fashion (more of a business requirement) and so we expose the startTimer and stopTimer methods in our EJB, and we invoke those methods from scripts outside of the WebSphere context as and when needed. This model has worked perfectly in a stand-alone environment. When we switched to our clustered UAT environment and started testing, that's when we got this reality check.
    Our cluster consists of 2 nodes, with 4 clones per node, and our middle ware team worked on the horizontal scaling in this environment. So when we try to invoke the startTimer in each of these node clones, it automatically goes to a random clone, not necessarily the one that we are trying to invoke on. And the same happens when we are trying to stop the timer, it tries to stop it on a random clone and the timer might not even be up on the clone it is trying to stop.
    So my short question: is there any way to force the EJB invocation to go to a particular clone? In other words, can we disable this whole horizontal scaling and just let it go to the clone we want (not let Websphere come in between with its "smart" load balancing) in our request? Something like a magic parameter that can be passed to the java command while invoking the EJB?
    This might sound "impossible" to do it that way and probably better to look at other ways, but we are just looking for something that will not significantly change our architecture at this point in the game.
    Thanks in advance!

    Answer to my question: http://ieoc.com/forums/p/26385/218976.aspx#218976

  • Oracle 10g Agent goes down itself

    I have been observing the Oracle 10g agent goes down by itself and in grid control it reports as Agent unreachable. where do I see the log why Agent is going down on target everytime.

    I guess the location is D:\oracle\agent10g\sysman\log
    However, I do not see any information why th agent went down ..
    log looks like below
    2009-12-29 15:35:40,552 Thread-5812 [IBM WebSphere Application Server] InstanceProperty (version) is marked OPTIONAL but is being used
    (00506)
    2009-12-29 15:35:47,599 Thread-5812 EMAgent started successfully
    (00702)
    2010-01-06 11:00:36,085 Thread-4360 Starting Agent 10.2.0.4.0 from D:\oracle\agent10g
    (00701)
    2010-01-06 11:00:37,929 Thread-4360 [E-Mail IMAP Server] InstanceProperty (imap_host) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:38,804 Thread-4360 Invalid expression (CacheFlushSuccess __delta) > 0 ? (CacheFlushSuccess __delta ) : 0
    (00101)
    2010-01-06 11:00:39,132 Thread-4360 [Database Instance] InstanceProperty (DBVersion) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:39,445 Thread-4360 [Identity Manager Repository] InstanceProperty (Port) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:39,445 Thread-4360 [Identity Manager Repository] InstanceProperty (SID) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:39,445 Thread-4360 [Identity Manager Repository] InstanceProperty (url) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:39,445 Thread-4360 [Identity Manager Repository] InstanceProperty (jdbcdriver) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:39,585 Thread-4360 [Oracle BPEL Process Manager] InstanceProperty (oc4jTargetName) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:40,616 Thread-4360 [E-Mail POP Server] InstanceProperty (pop_host) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:40,726 Thread-4360 [Cluster Database] InstanceProperty (DBVersion) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:40,851 Thread-4360 [Siebel Gateway Server] InstanceProperty (SIEBEL_GATEWAY) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:40,851 Thread-4360 [Siebel Gateway Server] InstanceProperty (SIEBEL_PORT) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:40,866 Thread-4360 [Siebel Server] InstanceProperty (filesystem:filesystem) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:40,866 Thread-4360 [Siebel Server] InstanceProperty (filesystem:installdir) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:40,866 Thread-4360 [Siebel Server] InstanceProperty (filesystem:logdir) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:40,898 Thread-4360 [Load Balancer Switch] InstanceProperty (snmpTimeout) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:40,960 Thread-4360 [E-Mail SMTP Inbound Server] InstanceProperty (smtp_host) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:41,007 Thread-4360 [E-Mail SMTP Outbound Server] InstanceProperty (smtp_host) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:41,085 Thread-4360 Undefined column name interval in expression ( active.requests > 0) ? active.requests/(interval*60) : 0
    (00104)
    2010-01-06 11:00:41,132 Thread-4360 [BEA WebLogic Managed Server] InstanceProperty (version) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:41,226 Thread-4360 [IBM WebSphere Application Server] InstanceProperty (version) is marked OPTIONAL but is being used
    (00506)
    2010-01-06 11:00:48,054 Thread-4360 EMAgent started successfully (00702)

  • How to Debug JSP in Websphere 3.5 ?? Urgent

    Hi,
    can somebody help me debuuging JSP in Websphere Application server 3.5 .Remember I dont have
    Websphere Studio or any other tool.any help in this regard is appreciated.
    Thanks
    Jack

    In most cases, you can debug an application by using the old standby of printing status lines after each significant chunk of code. For example, you can always output the page's parameters to make sure you've received what you think you've received.
    In the cases that Java throws an exception, you can make a rough guess as to what the problem is, based on the exception. A NumberFormatException usually occurs when you try to convert a letter into a number. The original intent would be to take a string "10" and convert that into the integer 10. SQL Exceptions are a little more vague, but again, you can at least narrow down the problem.
    Specific debuggers, while nice to have, are not really necessary. Through experience, and trial and error, you will eventually discover (and remember) the most common kinds of errors and how to avoid them.
    As a general rule, until you become proficient, always code a little chunk of the application at a time, and test that chunk to make sure it's working properly. It's far easier to track down a bug if you know it's somewhere in a dozen lines of code that you wrote that morning.
    If you are using Internet Explorer, you may want to confirm that Explorer is not giving you "friendly error messages". You can check this in the tools->internet options->advanced dialog box. By default, IE hides specific error messages, including JSP errors, because Microsoft rightly feels that your grandmother would just get confused.

  • Websphere upgrade

    we are upgrading websphere Application server from 5.0.2.8 to 5.1.1.1 that would also include moving from JVM 1.3 to i.4
    I would really appreciate if some of you who have gone through a similar upgrade could put down their experiences any good links some problems to look for and some steps to avoid.
    thanks a lot

    I didn't have any problems.Not quite true. I did have problems understanding how IBM packaged the stuff and what I was supposed to run to install the upgrades. But I had no problems with installing the upgrades.

  • Connection TimeOut in Websphere App Server.

    Hi,
    I am using JSF with JNDI and WebSphere to get query details. We have set the Connection Pooling Timeout in JNDI DataSource settings in WebSphere to 60 minutes.
    I have attached the Exception Stack Trace for your verification. This is a very serious exception which is hindering us from running any query that is running more than 10 minutes. Please suggest.
    Exception = com.ibm.wsspi.webcontainer.ClosedConnectionException
    Source = com.ibm.ws.webcontainer.srt.BufferedWriter.writeOut
    probeid = 416
    Stack Dump = com.ibm.wsspi.webcontainer.ClosedConnectionException: OutputStream encountered error during write
         at com.ibm.ws.webcontainer.channel.WCCByteBufferOutputStream.write(WCCByteBufferOutputStream.java:108)
         at com.ibm.ws.webcontainer.srt.SRTOutputStream.write(SRTOutputStream.java:96)
         at sun.nio.cs.StreamEncoder$ConverterSE.implFlushBuffer(StreamEncoder.java:293)
         at sun.nio.cs.StreamEncoder$ConverterSE.implFlush(StreamEncoder.java:299)
         at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:210)
         at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:236)
         at com.ibm.wsspi.webcontainer.util.BufferedWriter.writeOut(BufferedWriter.java:486)
         at com.ibm.wsspi.webcontainer.util.BufferedWriter.flushChars(BufferedWriter.java:372)
         at com.ibm.wsspi.webcontainer.util.BufferedWriter.flush(BufferedWriter.java:347)
         at java.io.PrintWriter.flush(PrintWriter.java:291)
         at com.ibm.ws.cache.servlet.CacheProxyWriter.flush(CacheProxyWriter.java:159)
         at com.ibm.ws.cache.servlet.CacheProxyWriter.flush(CacheProxyWriter.java:159)
         at com.ibm.ws.cache.servlet.FragmentComposer.requestFinished(FragmentComposer.java:393)
         at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:480)
         at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:281)
         at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.java:256)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
         at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:766)
         at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:674)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
         at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
         at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122)
         at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:225)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:321)
         at com.ibm.faces.context.MultipartExternalContextImpl.dispatch(MultipartExternalContextImpl.java:320)
         at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:257)
         at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:220)
         at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:118)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
         at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWrapper.java:276)
         at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:463)
         at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:281)
         at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.java:256)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
         at com.filter.ApplicationSessionExpiryFilter.doFilter(Unknown Source)
         at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
         at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:766)
         at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:674)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
         at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
         at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
         at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
         at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:113)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:263)
         at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
         at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
         at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
         at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
         at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
         at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
         at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
         at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
         at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
    Caused by: java.io.IOException: Async IO operation failed, reason: RC: 32 There is no process to read data written to a pipe.
         at com.ibm.io.async.AbstractAsyncChannel.multiIO(AbstractAsyncChannel.java:474)
         at com.ibm.io.async.AsyncSocketChannelHelper.write(AsyncSocketChannelHelper.java:478)
         at com.ibm.io.async.AsyncSocketChannelHelper.write(AsyncSocketChannelHelper.java:396)
         at com.ibm.ws.tcp.channel.impl.AioSocketIOChannel.writeAIO(AioSocketIOChannel.java:281)
         at com.ibm.ws.tcp.channel.impl.AioTCPWriteRequestContextImpl.processAsyncWriteRequest(AioTCPWriteRequestContextImpl.java:49)
         at com.ibm.ws.tcp.channel.impl.TCPWriteRequestContextImpl.writeInternal(TCPWriteRequestContextImpl.java:166)
         at com.ibm.ws.tcp.channel.impl.TCPWriteRequestContextImpl.write(TCPWriteRequestContextImpl.java:137)
         at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.asynchWrite(HttpServiceContextImpl.java:2376)
         at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.sendOutgoing(HttpServiceContextImpl.java:2165)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundServiceContextImpl.sendResponseBody(HttpInboundServiceContextImpl.java:778)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.writeBufferAsynch(WCChannelLink.java:307)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.writeBufferResponse(WCChannelLink.java:287)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.writeBuffer(WCChannelLink.java:241)
         at com.ibm.ws.webcontainer.channel.WCCByteBufferOutputStream.flushWriteBuffer(WCCByteBufferOutputStream.java:401)
         at com.ibm.ws.webcontainer.channel.WCCByteBufferOutputStream.write(WCCByteBufferOutputStream.java:147)
         at com.ibm.ws.webcontainer.srt.SRTOutputStream.write(SRTOutputStream.java:96)
         at sun.nio.cs.StreamEncoder$ConverterSE.implFlushBuffer(StreamEncoder.java:293)
         at sun.nio.cs.StreamEncoder$ConverterSE.implFlush(StreamEncoder.java:299)
         at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:210)
         at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:236)
         at com.ibm.wsspi.webcontainer.util.BufferedWriter.writeOut(BufferedWriter.java:486)
         at com.ibm.wsspi.webcontainer.util.BufferedWriter.flushChars(BufferedWriter.java:372)
         at com.ibm.wsspi.webcontainer.util.BufferedWriter.flush(BufferedWriter.java:347)
         at java.io.PrintWriter.flush(PrintWriter.java:291)
         at com.ibm.ws.cache.servlet.CacheProxyWriter.flush(CacheProxyWriter.java:159)
         at com.ibm.ws.cache.servlet.CacheProxyWriter.flush(CacheProxyWriter.java:159)
         at org.apache.jasper.runtime.JspWriterImpl.flush(JspWriterImpl.java:233)
         at java.io.PrintWriter.flush(PrintWriter.java:291)
         at com.ibm.ws.cache.servlet.CacheProxyWriter.flush(CacheProxyWriter.java:159)
         at com.ibm.ws.cache.servlet.FragmentComposer.requestFinished(FragmentComposer.java:393)
         at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:480)
         at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:281)
         at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.java:256)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
         at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:766)
         at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:674)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
         at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
         at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122)
         at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:225)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:639)
         at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:1034)
         at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:997)
         at com.ibm._jsp._extract_5F__jspService(_extract_5F_java:91)
         at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:87)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWrapper.java:276)
         at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:463)
         ... 51 more

    http://redeyeinteractive.com/index.eye?cart=1027565021121425&membersku=[membersku]&action=specific&SKU=507921572586523
    if this link don't work go to http://redeyeinteractive.com
    go to there java\applets path u will see a file upload component
    u can down load trial version free it is very easy to use.
    Good luck.

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

  • How to integrate Websphere MQ as an external JMS Provider?

    Hello to all!
    I'm trying to integrate Websphere MQ in SAP Web AS 6.40 as an external JMS provider and I'm having some problems. As the use of SAP XI is impossible for me, I started using the built-in JMS Connector.
    I've already read (and tried to follow) the documentation in http://help.sap.com/saphelp_nw04/helpdata/en/cd/4d4941abbb4c0de10000000a1550b0/frameset.htm, but unfortunately, it didn't help me that much.
    It told me that the JMS Connector is the right place to start, and I already managed to deploy and define the Websphere MQ JMS implementation as a library. And from various examples I'm quite sure that Websphere MQ is an JNDI based JMS provider. But now the problems start.
    According to the SAP library mentioned above, I have to enter the JNDI name to the ConnectionFactory in the "New ConnectionFactory" dialogue in the "Provider" tab. As an example there is the (existing) JNDI name "jmsfactory/default/TopicConnection". For doing the same with my Websphere MQ, I expect to need something alike.
    Hoping that I'm getting the SAP library right at this point, I'm expecting to need a JNDI entry, like, let's say, "jmsfactory/WebsphereMQ/QueueConnection" connected to the class "com.ibm.mq.jms.MQConnectionFactory" (MQConnectionFactory is the class in the MQ JMS implementation that implements the JMS interface "Connection Factory"). How can I put those Websphere MQ classes, that are implementing the JMS interfaces like Connection Factory, QueueConnectionFactory and so on
    in my JNDI tree? The point is, obviously, no JNDI entry was made during deploying Websphere MQ as a library.
    Or am I totally wrong an misunderstood the SAP library completely? Any help on this topic would be highly appreciated.
    Best greetings!
    Bärbel

    Integrating WebSphereMQ with SAP Web Application Server
    Prerequisites
    The native libraries of WebSphereMQ must be added to the environment variables of the host or hosts where the SAP Web AS is running. Typically, if MQ is installed on the same host, the required entries are added to the environment at installation. However, we recommend that you check the MQ documentation for details about the directory where the libraries are located, and make sure it is added to the environment on all hosts with SAP Web AS.
    For example, for Windows OS the following libraries are required:
    -     amqmtmgr.dll
    -     amqvwaa2.dll
    -     amqxcs2.dll
    -     amqxcsn.dll
    -     amqzc.dll
    -     amqzsai.dll
    -     amqzst.dll
    -     amqztm.dll
    -     mqjbdf02.dll
    -     mqjbnd05.dll
    -     mqm.dll
    -     mqmvxd.dll
    -     mqmxa.dll
    -     MQXAi02.dll
    Procedure
    1)     If the version of the SAP Web AS is SP 7 or lower, you must apply a patch for the JMS Connector Service. The required SDA is attached to this e-mail (jmsconnector.sda). To apply it:
    a.     Run the SDM Remote GUI tool. It is located in <SAP_install_dir>\SAPSID\<Instance_ID>\SDM\program.
    b.     In the Deployment tab, add the jmsconnector.sda to the deployment list. Choose   Show Deployment Configuration. Select Update deployed SDAs/SCAs that have any version (this ensures that you will have the SDA deployed even if for some reason its timestamp is older than the one of the SP7 SDA that you already have deployed.)
    c.     Deploy the SDA following the standard deployment procedure. If prompted to choose if you want to delegate the control to the SDM server, choose Yes. The SDM shuts down the cluster, deploys the SDA, and then restarts the cluster.
    2)     Create the IBM MQ library. You can do it using either Visual Administrator or SAP NetWeaver Developer Studio.
    a.     Visual Administrator:
    i.     Go to Services -> JMS Connector.
    ii.     Select JMS Libraries, and choose New.
    iii.     Enter a name for the library, such as MQJMSLIB.
    iv.     Browse to select the following JAR files:
    - com.ibm.mq.jar
    - com.ibm.mqbind.jar
    - com.ibm.mqjms.jar
    - fscontext.jar
    - ldap.jar
    - postcard.jar
    - provider.xml
    - providerutil.jar
    v.     Deploy the library.
    vi.     Go to Services -> Configuration Adapter. In the configuration tree on the right-hand side of the screen browse to cluster_data -> server -> cfg -> ext -> MQJMSLIB-provider.xml. Switch to edit mode using  . Open the XML for editing using  . Add the following entry (after the reference entry for jms):
    <reference type="library" strength="weak">j2eeca</reference>
    Choose OK and restart the cluster to apply the changes.
    b.     SAP NetWeaver Developer Studio:
    i.     Create a J2EE Library project.
    ii.     Select the project and choose File -> Import -> File System. Browse to the MQ folder, which contains the JAR files listed above, and select to import them.
    iii.     Extend the tree of your library project and open server/provider.xml. Go to the Jars tab.
    iv.     Select Jars, and choose Add. Choose to add the JAR files that you have imported in the previous step.
    v.     Go to the References tab. Select References, and choose Add. Choose Select library/interface/service. In the list select jms and j2eeca.
    vi.     Save and close provider.xml. From the context menu of the library project choose Build Library Archive.
    vii.     Select the SDA in the project tree, open its context menu, and choose Deploy to J2EE Engine.
    3)     Create a JMS Connector Factory in Visual Administrator.
    You can either enter the required values directly in the Visual Administrator (Services -> JMS Connector), or you can edit the following sample deployment descriptors and import them in Visual Administrator using  .
    a.     Using JNDI:
    This is example of factories.xml using JNDI based JMS provider.
    <?xml version="1.0" encoding="UTF-8" ?>
      <jms-factories>
        <application-name>
          IBM_Test_App
        </application-name>
        <connection-factory>
          <library-name>
            MQJMSLIB
          </library-name>
          <factory-name>
            IBM_Queue_Factory
          </factory-name>
          <context-factory-type>
    <!—This factory should already exist on WebSphereMQ.-->
            <link-factory-name>
              QCF_1
            </link-factory-name>
            <initial-context-factory>
              com.sun.jndi.fscontext.RefFSContextFactory
            </initial-context-factory>
            <provider-url>
              file:/C:/JNDI-Directory
            </provider-url>
            <security-principal>
            </security-principal>
            <security-credentials>
            </security-credentials>
          </context-factory-type>
        </connection-factory>
      </jms-factories>
    b.     Using object factory JMS provider
    <?xml version="1.0" encoding="UTF-8" ?>
      <jms-factories>
        <application-name>
          IBM_Test_App
        </application-name>
        <connection-factory>
          <library-name>
            MQJMSLIB
          </library-name>
          <factory-name>
            IBM_Queue_Factory
          </factory-name>
          <object-factory-type>
            <object-factory-name>
              com.ibm.mq.jms.MQXAQueueConnectionFactoryFactory
            </object-factory-name>
            <class-name>
              com.ibm.mq.jms.MQXAQueueConnectionFactory
            </class-name>
            <properties>
              <property>
                <property-name>
                  HOST
                </property-name>
    <!-- JMS Provider host name -->
                <property-value>
                  localhost
                </property-value>
              </property>
              <property>
                <property-name>
                  QMGR
                </property-name>
    <!-- Queue Manager -->
                <property-value>
                  MQ_default
                </property-value>
              </property>
              <property>
                <property-name>
                  PORT
                </property-name>
    <!-- JMS Provider port number -->
                <property-value>
                  1414               
                </property-value>
              </property>
              <property>
                <property-name>
                  TRAN
                </property-name>
    <!-- Transport type -->
                <property-value>
                  1                    
                </property-value>
              </property>
            </properties>
          </object-factory-type>
        </connection-factory>
      </jms-factories>
    4)     Use the connection factory in an application:
    Code:
    Context ctx = new InitialContext();
    Object ref = ctx.lookup("java:comp/env/IBM_Queue_Factory");
    QueueConnectionFactory f = (QueueConnectionFactory)ref;
    QueueConnection connection = f.createQueueConnection();
    Resource references:
                     <resource-ref>
              <res-ref-name>
                IBM_Queue_Factory
              </res-ref-name>
              <res-type>
                javax.jms.QueueConnectionFactory
              </res-type>
              <res-auth>
                Container
              </res-auth>
            </resource-ref>
    If you are using 6.40 SP7 or below let me know to send you a patch.
    Regards Nikola

  • BlazeDS - Websphere Memory Consumption!!!!!!!!!!

    I'm using BlazeDS 3.2.0.3978 with Websphere 6.1 and we're seeing a lot of memory problems. Even if we start our application and have no traffic, we still end up consuming all available memory.  When we do get traffic, the memory usage goes up and stays up...even when that traffic dies down.  Our application is using BlazeDS to call to get some data for a graph, then its done.  So, our flex app only needs to make the 1 call to the server, then as far as BlazeDS goes, we should be done.
    Here are the classes that were the largest in a Heap Dump....
    498,689,904 (74%) [88] 17 array of edu/emory/mathcs/backport/java/util/concurrent/ConcurrentHashMap$Segment 0xa0f9d100
    107,241,392 (16%) [536] 129 array of edu/emory/mathcs/backport/java/util/concurrent/ConcurrentHashMap$HashEntry 0xb933a3b8
    78,661,104 (11%) [504] 121 array of edu/emory/mathcs/backport/java/util/concurrent/ConcurrentHashMap$HashEntry 0xb52edff0
    50,593,680 (7%) [552] 133 array of edu/emory/mathcs/backport/java/util/concurrent/ConcurrentHashMap$HashEntry 0xb49eac18
    This is a very serious issue, which I need to get resolved asap...does anyone have any thoughts or suggestions that may help alleviate this problem?
    I'm currently using mx.messaging.channels.AMFChannel with polling enabled to false.
    I've tried to set the session timeout to 1, which didn't seem to make any difference.
    I've tried adding a call to RemoteObject.disconnect() and RemoteObject.channelSet.disconnectAll(), which didn't seem to make any difference.
    Any help you could offer would be greatly appreciated!
    Thanks!!!

    After doing some more digging into the heap dumps, it looks like the ConcurrentHashMapSegment that is using up a majority of the memory is the flexClients Map in FlexClientManager.
    Does anyone have any idea why that Map keeps growing and doesn't ever get cleared out?

  • File Upload in WebSphere App Server (3.5.4)

    Hi
    I am trying to upload a file from the client to the server. I am using oReilley's MultipartRequest to do this. This works fine in my Test Environment in Visual Age. But does not work in Websphere App Server.
    I get a "Error during native read operation". This happens mostly for big files more than 2 MB and sometimes for small files as well.
    Is this is a server issue? ('cos i tried using from jspsmart File Uplaod class and the result was the same).
    Any help is greatly appreciated.
    Thank You

    http://redeyeinteractive.com/index.eye?cart=1027565021121425&membersku=[membersku]&action=specific&SKU=507921572586523
    if this link don't work go to http://redeyeinteractive.com
    go to there java\applets path u will see a file upload component
    u can down load trial version free it is very easy to use.
    Good luck.

  • Meet an error in InfoView when CR Server in Windows and Websphere in Linux.

    Hi Expert,
    I installed the Crystal Reports Server  XI R2 in Windows 2003, and deployed the desktop.war and other war files on Websphere 6.1 in linux.
    And in InfoView through Websphere to view a report with parameter that connect to Oracle, after input the parameter value to click on the OK button, there would pop up an error: " Ln 1 Col 1818: Expected end of tag 'Name' "
    Below are the narrow down:
    1. the InfoView through Tomcat would be OK, can view the report correctly.
    2. If the report without parameter, also can view the report correctly.
    3. The problem should not be caused by the Oracle database;
    4.
    you can find the trace from websphere in the attachment.
    Thanks very much for any help,
    Rongliang

    Here is the trace from websphere, thanks.
    app name : default_hostbusinessobjects/enterprise115/desktoplaunch
    [8/15/10 19:16:43:079 GMT+08:00] 0000008c SystemOut     O dhtml
    [8/15/10 19:16:43:121 GMT+08:00] 0000008c SystemOut     O old dpi:120
    [8/15/10 19:16:43:121 GMT+08:00] 0000008c SystemOut     O request.getParameter(CEConstants.REQUEST_ID): objId - 608
    [8/15/10 19:16:43:121 GMT+08:00] 0000008c SystemOut     O uri: ../../../../InfoView/plugin/crystalenterprise/report/viewDHTMLReport.jsp?objId=608&ceVwr=1
    [8/15/10 19:16:46:143 GMT+08:00] 00000090 SystemOut     O dhtml
    [8/15/10 19:16:46:143 GMT+08:00] 00000090 SystemOut     O old dpi:120
    [8/15/10 19:16:46:143 GMT+08:00] 00000090 SystemOut     O request.getParameter(CEConstants.REQUEST_ID): objId - 608
    [8/15/10 19:16:46:144 GMT+08:00] 00000090 SystemOut     O uri: ../../../../InfoView/plugin/crystalenterprise/report/viewDHTMLReport.jsp?objId=608&ceVwr=1
    [8/15/10 19:16:46:210 GMT+08:00] 00000090 SystemOut     O 576100 [WebContainer : 2] ERROR com.crystaldecisions.sdk.occa.managedreports.ps.internal.CacheReportSource  - processPrompting(): processPrompting failed.
    com.crystaldecisions.sdk.occa.report.lib.ReportSDKException: Ln 1 Col 1818: Expected end of tag 'Name'---- Error code:-2147217395 Error code name:serverProgrammingError
         at com.crystaldecisions.sdk.occa.report.lib.ReportSDKException.throwReportSDKException(Unknown Source)
         at com.crystaldecisions.sdk.occa.managedreports.ps.internal.f.a(Unknown Source)
         at com.crystaldecisions.sdk.occa.managedreports.ps.internal.f.processPrompting(Unknown Source)
         at com.crystaldecisions.report.web.event.bk.a(Unknown Source)
         at com.crystaldecisions.report.web.event.bk.a(Unknown Source)
         at com.crystaldecisions.report.web.event.ag.a(Unknown Source)
         at com.crystaldecisions.report.web.event.b7.broadcast(Unknown Source)
         at com.crystaldecisions.report.web.event.av.a(Unknown Source)
         at com.crystaldecisions.report.web.WorkflowController.do(Unknown Source)
         at com.crystaldecisions.report.web.WorkflowController.doLifecycle(Unknown Source)
         at com.crystaldecisions.report.web.ServerControl.a(Unknown Source)
         at com.crystaldecisions.report.web.ServerControl.processHttpRequest(Unknown Source)
         at com.ibm._jsp._viewDHTMLReport._jspService(_viewDHTMLReport.java:486)
         at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:93)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1697)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:826)
         at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
         at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:216)
         at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
         at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1936)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:120)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:434)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:373)
         at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:101)
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
    [8/15/10 19:16:46:212 GMT+08:00] 00000090 SystemOut     O 2010-08-15 19:16:46
    com.crystaldecisions.report.web.shared.WebReportingException: Ln 1 Col 1818: Expected end of tag 'Name'---- Error code:0
         at com.crystaldecisions.report.web.shared.WebReportingException.throwWebReportingException(Unknown Source)
         at com.crystaldecisions.report.web.event.bk.a(Unknown Source)
         at com.crystaldecisions.report.web.event.bk.a(Unknown Source)
         at com.crystaldecisions.report.web.event.ag.a(Unknown Source)
         at com.crystaldecisions.report.web.event.b7.broadcast(Unknown Source)
         at com.crystaldecisions.report.web.event.av.a(Unknown Source)
         at com.crystaldecisions.report.web.WorkflowController.do(Unknown Source)
         at com.crystaldecisions.report.web.WorkflowController.doLifecycle(Unknown Source)
         at com.crystaldecisions.report.web.ServerControl.a(Unknown Source)
         at com.crystaldecisions.report.web.ServerControl.processHttpRequest(Unknown Source)
         at com.ibm._jsp._viewDHTMLReport._jspService(_viewDHTMLReport.java:486)
         at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:93)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1697)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:826)
         at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
         at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:216)
         at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
         at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1936)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:120)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:434)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:373)
         at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:101)
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
    Caused by: com.crystaldecisions.sdk.prompting.PromptingException: Ln 1 Col 1818: Expected end of tag 'Name' Error code name:ProcessPromptingFail
         at com.crystaldecisions.sdk.prompting.PromptingException.throwPromptingException(Unknown Source)
         at com.crystaldecisions.sdk.occa.managedreports.ps.internal.f.processPrompting(Unknown Source)
         ... 27 more
    Caused by: com.crystaldecisions.sdk.occa.report.lib.ReportSDKException: Ln 1 Col 1818: Expected end of tag 'Name'---- Error code:-2147217395 Error code name:serverProgrammingError
         at com.crystaldecisions.sdk.occa.report.lib.ReportSDKException.throwReportSDKException(Unknown Source)
         at com.crystaldecisions.sdk.occa.managedreports.ps.internal.f.a(Unknown Source)
         ... 28 more
    [8/15/10 19:16:46:212 GMT+08:00] 00000090 SystemOut     O Caused by:
    com.crystaldecisions.sdk.prompting.PromptingException: Ln 1 Col 1818: Expected end of tag 'Name' Error code name:ProcessPromptingFail
         at com.crystaldecisions.sdk.prompting.PromptingException.throwPromptingException(Unknown Source)
         at com.crystaldecisions.sdk.occa.managedreports.ps.internal.f.processPrompting(Unknown Source)
         at com.crystaldecisions.report.web.event.bk.a(Unknown Source)
         at com.crystaldecisions.report.web.event.bk.a(Unknown Source)
         at com.crystaldecisions.report.web.event.ag.a(Unknown Source)
         at com.crystaldecisions.report.web.event.b7.broadcast(Unknown Source)
         at com.crystaldecisions.report.web.event.av.a(Unknown Source)
         at com.crystaldecisions.report.web.WorkflowController.do(Unknown Source)
         at com.crystaldecisions.report.web.WorkflowController.doLifecycle(Unknown Source)
         at com.crystaldecisions.report.web.ServerControl.a(Unknown Source)
         at com.crystaldecisions.report.web.ServerControl.processHttpRequest(Unknown Source)
         at com.ibm._jsp._viewDHTMLReport._jspService(_viewDHTMLReport.java:486)
         at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:93)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1697)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:826)
         at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
         at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:216)
         at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
         at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1936)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:120)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:434)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:373)
         at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:101)
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
    Caused by: com.crystaldecisions.sdk.occa.report.lib.ReportSDKException: Ln 1 Col 1818: Expected end of tag 'Name'---- Error code:-2147217395 Error code name:serverProgrammingError
         at com.crystaldecisions.sdk.occa.report.lib.ReportSDKException.throwReportSDKException(Unknown Source)
         at com.crystaldecisions.sdk.occa.managedreports.ps.internal.f.a(Unknown Source)
         ... 28 more
    [8/15/10 19:16:46:213 GMT+08:00] 00000090 SystemOut     O Caused by:
    com.crystaldecisions.sdk.occa.report.lib.ReportSDKException: Ln 1 Col 1818: Expected end of tag 'Name'---- Error code:-2147217395 Error code name:serverProgrammingError
         at com.crystaldecisions.sdk.occa.report.lib.ReportSDKException.throwReportSDKException(Unknown Source)
         at com.crystaldecisions.sdk.occa.managedreports.ps.internal.f.a(Unknown Source)
         at com.crystaldecisions.sdk.occa.managedreports.ps.internal.f.processPrompting(Unknown Source)
         at com.crystaldecisions.report.web.event.bk.a(Unknown Source)
         at com.crystaldecisions.report.web.event.bk.a(Unknown Source)
         at com.crystaldecisions.report.web.event.ag.a(Unknown Source)
         at com.crystaldecisions.report.web.event.b7.broadcast(Unknown Source)
         at com.crystaldecisions.report.web.event.av.a(Unknown Source)
         at com.crystaldecisions.report.web.WorkflowController.do(Unknown Source)
         at com.crystaldecisions.report.web.WorkflowController.doLifecycle(Unknown Source)
         at com.crystaldecisions.report.web.ServerControl.a(Unknown Source)
         at com.crystaldecisions.report.web.ServerControl.processHttpRequest(Unknown Source)
         at com.ibm._jsp._viewDHTMLReport._jspService(_viewDHTMLReport.java:486)
         at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:93)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1697)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:826)
         at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
         at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:216)
         at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
         at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1936)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:120)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:434)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:373)
         at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:101)
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java(Compiled Code))
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))

Maybe you are looking for

  • Can i move iWeb site control from one computer to another?

    We hired someone to create a website for our company. He created it using iWeb on his computer and now is no longer with the company. How can I move the control of this website to the iWeb application on my computer so that I can manage the site?

  • Error for a custom OAF page

    Hi All, I am getting the error below while trying to enter a value in a field (The field has a search symbol, when i click on it i get an error "You have encountered an unexpected error. Please contact the System Administrator for assistance"). I hav

  • In need of a new Graphics/Video card,..which one?

    My computer stopped booting all the way a couple of days ago. Took it to Apple store where they told me I need a new Graphics card. As of now I have: Chipset Model: NVIDIA GeForce 7300 GT Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 256 MB Vendor: NV

  • How do I get a specific node in Elixir org chart?

    The problem now is, how do I get a node from the org chart?  I have seen various methods like, getChild, getChildAt, getChildByName, but none of them seem to get the node I'm looking for.  Each node has a unique attribute of DistID.  I don't know how

  • Query Related to dates

    Hi i have a table ABC in which i declared two date columns START_DATE AND END_DATE . I want to extract all the dates between these two dates which is not specified into table. eg START_DATE=12-JUN-2009 END_DATE=15-JUN-2009 SELECT TO_DATE(START_DATE,