WLS 6.1 sp3 and XA and DB2

          Our configuration is:
          WLS 6.1 with sp3 on Solaris and DB2 7.2.7 on AIX running on remote server. Local
          DB2 client is installed on Solaris (LD_LIBRARY_PATH and other DB2 related variables
          are set accordingly).
          In some parts of our system we decided to use message-driven beans to process
          some work off side. In some of them we interact with database and send JMS messages
          to trigger some other MDBs. And we need all these operation to be one unit of
          work. Since we have operation on JMS and DB stores, we were forced to use XA and
          DB2 XA JDBC driver type 2.
          Most of the time things work fine ( always in our dev environment where WLS, DB2
          runs on the same Win2000 box), but rundomly we get JVM to crash on Solaris - like
          once a day or two. We are about to roll out to production but with these crashes
          we are confident about stablity of our app. We found that in most cases (but not
          all) those were related to the situation when DB2 connection were dropped or become
          invalid.
          On BEA website I found the information that WLS does not work in XA mode with
          DB2 7.1, because "APP driver falls back to NET driver". Does this still apply
          to DB2 7.2.7? If yes then I do not understand why Java->JNI call would fall back
          to Java->JNI->Java? Besides on IBM site there is nothing which says that type
          2 driver (so called APP one) requires JDBC client running on the same machine
          as database. If BEA claims that this indeed is the case, then it poses severe
          limitation to XA JDBC driver of IBM. Well, it means it is pretty much useless
          (who runs DB and app server on the same box ?)
          Today we just found new information about additional setting for XA connection
          pools that apply to DB2 and Sybase. For DB2 you need to set KeepXAConnTillTxComplete
          to true in your config.xml. We do not know yet if it is going to make things better
          (any input from BEA?)
          Can we get firm statement answer from BEA whether our configuration is supported
          or if not how we can achieve data/JMS integrity without using DB2 XA driver. Would
          using regular DB2 driver in pseudo-XA mode be a best work around, provided that
          the regular one is stable.
          How precisely WLS behave when it needs to orchestrate distributed transaction
          using pseudo-XA JDBC driver and fully-XA JMS server? In second phase does it first
          as DB to commit and if it succeeds it commits JMS, otherwise it rollbacks everything?
          We are very anxious to get our questions answered please.
          Thanks,
          Waldek
          

Look for sometime around November. No exact date.
Eric
"Dominic Tulley" <[email protected]> wrote in message
news:[email protected]..
Thanks Eric,
you know what I'm going to ask next right?
Any ideas when SP4 comes out?
Cheers,
-Dominic
"Eric Gross" <[email protected]> wrote in message
news:[email protected]..
The next version of Apache that we will support will be 2.0.42/2.0.43
and
the module for that will be included in the next Service Pack for6.1(SP4)
and 7.0(SP2).
The problem with Apache 2 is that when a new release comes out a newmodule
needs to be compiled. Most of the time. For 2.0.42/2.0.43 this is notthe
case.
Regards,
Eric
"Dominic Tulley" <[email protected]> wrote in
message
news:3da3f246$[email protected]..
I'm trying to set this up (initially just apache in front of a single
WLS
server but ultimately I want to put it in front of a cluster).
I've installed Apache 2.0.40.
I've copied the mod_wl_20.so file into the apache modules folder.
I've edited the httpd.conf file and added the line:
LoadModule weblogic_module modules/mod_wl_20.so
When I run apache -t to check the configuration I get the following:
C:\Program Files\Apache Group\Apache2\bin>apache -t
Syntax error on line 173 of C:/Program Files/Apache
Group/Apache2/conf/httpd.conf:
Cannot load C:/Program Files/Apache Group/Apache2/modules/mod_wl_20.sointo
server: The specified procedure could not be found.
So what's going on here?
Looking at previous postings it sounds like there's an issue with
versions
of apache after 2.0.39 but I can't find a download for that version.Also,
it sounded like the issues were for WLS 7, not 6.1. Can this work
with
2.0.40 or am I wasting my time?
If I get the mod_wl_20.so from dev2dev I get the "incompatible plugin"
message that has been mentioned in this group already.
Any suggestions appreciated,
-Dominic

Similar Messages

  • WLS 6.1 SP3 and apache plugin

    Hello,
    I have WLS 6.1 SP3 and apache 1.3.26 installed on solaris 8.
    I enabled the weblogic Weblogic Plug-In Enabled for my wls server and
    then I configured my apache server like the following:
    1) I used mod_wl.so that comes with wls under
    \bea\wlserver6.1\lib\solaris
    2) Then I loaded that module using APACHE_HOME/bin/apxs -i -a -n
    weblogic mod_wl.so
    When I load the module I get the following:
    [Thu Jan 15 10:05:53 2004] [warn] Loaded DSO libexec/mod_wl.so uses
    plain Apache 1.3 API, this module might crash under EAPI!
    please recompile it with -DEAPI)
    /usr/apache/bin/apachectl start: httpd started
    I don't understand that message
    3) The following lines were added to httpd.conf:
    LoadModule weblogic_module libexec/mod_wl.so
    AddModule mod_weblogic.c
    4) Then I added the following to the httpd.conf:
    <IfModule mod_weblogic.c>
    WebLogicHost 10.1.10.205(my weblogic IP)
    WebLogicPort 7020 (my weblogic port)
    FileCaching On
    MatchExpression *.jsp
    </IfModule>
    The problem is that the apache server is not able to redirect the jsp
    calls to the WLS server and I'm always getting "The page cannot be
    displayed"
    Any information that might guide me to solve this problem is appreciated
    Itani Mohamed
    SoftSolutions
    Tel: +961.1.90.11.70 ext:141
    Fax: +961.1.90.11.75
    www.softsolutions.fr

    Itani,
    Please try the mod-wl-ssl.so module shipped with weblogic, as this module is compiled with -DEAPI flag

  • Message Bridge between WLS 6.1 sp3 and MQSeries 5.2

              Hi,
              I'm really struggling with getting the Message Bridge working with Weblogic 6.1
              sp3 and MQSeries 5.2. Currently I have both installed on the same Windows 2000
              machine. First I'll pose some questions that I have, then I discuss the error
              I'm getting. Here are my questions:
              1. With the jms-xa-adp.rar there is a ra.xml and a weblogic-ra.xml. Within the
              ra.xml deployment descriptor there are config-properties for ConnectionURL, InitialContextFactory,
              ConnectionFactoryJNDI, and DestinationType. If my MQSeries Queue is the source
              jms destination bridge and my weblogic queue is the target jms destination bridge,
              what values do I set for the listed config-properties? I can't seem to find any
              documentation on what these values should be. Am I missing something? Do these
              values even have to be set?
              2. When I go to install a Weblogic instance to a different physical machine what
              has to be installed in terms of MQSeries? So I'll have MQSeries on physical machineA
              and Weblogic on a different physical machineB. I want machineA to forward all
              messages placed on a MQSeries Queue to forward them to machineB where the weblogic
              Queue resides. Does machineB also have to contain an MQSeries installation?
              Or can I just grab the necessary libraries and jar files and place them on the
              Weblogic machineB so they can be included?
              3. Is it correct that if I distribute Weblogic onto one physical server and MQSeries
              onto a different physical server that I cannot use Exactly-once quality of service?
              Other notes:
              1. I have the following patches installed for Weblogic 6.1 sp3:
              CR081404_610sp3.jar
              CR081511_61sp3.jar
              2. Here is the commands I used to create my ConnectionFactory and Queue within
              MQSeries:
              def xaqcf(MQTestConnectionFactory) qmanager(QM_jeff)
              def q(MQTestQueue) qmanager(QM_jeff) queue(default)
              Okay...here is my error:
              <21-Aug-02 11:08:34 ADT AM> <Error> <MessagingBridge> <Error occurred in bridge
              "Messaging Bridge" during transferring messages (java.lang.Exception: java.lang.
              reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTargetException:
              javax.resource.ResourceException: Error creating consumer or receiving message
              at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1086)
              at weblogic.jms.adapter.JMSBaseConnection.receiveInternal(JMSBaseConnection.java:774)
              at weblogic.jms.adapter.JMSBaseConnection.receiveCommon(JMSBaseConnection.java:656)
              at weblogic.jms.adapter.JMSBaseConnection.receive(JMSBaseConnection.java:811)
              at weblogic.jms.adapter.JMSConnectionHandle.receive(JMSConnectionHandle.java:111)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:60)
              at $Proxy82.receive(Unknown Source)
              at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1215)
              at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:854)
              at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
              Has anyone see this error before? Here is part of my ra.xml file....I just put
              these entries in to see what happens:
              <config-property>
              <config-property-name>ConnectionURL</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property value>file:/C:/Develop/app_servers/WebSphere/MQSeries</config-property-value>
              </config-property>
              <config-property>
              <config-property-name>InitialContextFactory</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value>com.sun.jndi.fscontext.RefFSContextFactory</config-property-value>
              </config-property>
              <config-property>
              <config-property-name>ConnectionFactoryJNDI</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value>MQTestConnectionFactory</config-property-value>
              </config-property>
              <config-property>
              <config-property-name>DestinationJNDI</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value>MQTestQueue</config-property-value>
              </config-property>
              <config-property>
              <config-property-name>DestinationType</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value></config-property-value>
              </config-property>
              <config-property>
              <config-property-name>AdapterType</config-property-name>
              <config-property-type>java.lang.String</config-property-type>
              <config-property-value>XATransaction</config-property-value>
              </config-property>
              Here is a snip of my config.xml:
              <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
              Name="Messaging Bridge" QualityOfService="Atmost-once"
              SourceDestination="Source JMS Bridge Destination"
              TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
              <JMSBridgeDestination
              AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              ConnectionFactoryJNDIName="MQTestConnectionFactory"
              ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
              DestinationJNDIName="MQTestQueue" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
              Name="Source JMS Bridge Destination"/>
              <JMSBridgeDestination
              AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
              ConnectionURL="t3://localhost:7001"
              DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
              InitialContextFactory="weblogic.jndi.WLInitialContextFactory" Name="Target
              JMS Bridge Destination"/>
              Any help would be greatly appreciated. Thank you in advance for your help.
              Sincerely,
              Jeff
              

              I tried your suggestion and it worked!! The only thing is, it
              makes the deployment of the resource adapter a little more
              complicated. Now my customers are going to have to edit their
              config.xml, instead of just dropping in the appropriate rar into
              the applications directory. But one nice side affect of placing
              the rar's in a different directory is it makes the Message
              Bridge a little more stable. I was finding it to be very
              unstable. One time I would startup my Application Server and
              everything was fine, then I would shutdown. The next time I
              started it up, I would get exceptions. I have yet to see that
              behavior with this new configuration.
              Thanks again for all of your help, it is greatly appreciated!!
              Jeff
              Dongbo Xiao <[email protected]> wrote:
              >Looks like that somehow you have the adapter deployed
              >multiple times, may not be intended. The cause is that
              >everything in the application directory will be automatically
              >deployed and all of them are added to the config.xml. During
              >the next boot, those appear in the config.xml will be deployed and
              >everything in the application directory too. As a result, the adapters
              >are deployed twice. The complain about runtime mbean not found may
              >mean the one that is overridden by the new one.
              >
              >The work around is not to put your adapters in the application
              >directory, instead, put them in a different directory and point to
              >the directory in your config.xml.
              >
              >Dongbo
              >Jeff wrote:
              >>
              >> One more thing...
              >> I noticed that the exception specified that it couldn't find
              >> mydomain:Location=myserver,Name=jms-xa-
              >> adp_Pool_1,ServerRuntime=myserver,Type=ConnectorConnectionPoolRun
              >> time MBean, but what's interesting that if I run the following
              >> java weblogic.Admin GET -type ConnectorConnectionPoolRuntime -
              >> property ActiveConnectionsCurrentCount -url
              >> http://localhost:7001 -username xxxx -password xxxx I get the
              >> following output:
              >>
              >> {MBeanName="mydomain:Location=myserver,Name=jms-xa-
              >> adp_Pool_3,ServerRuntime=myse
              >> rver,Type=ConnectorConnectionPoolRuntime"{ActiveConnectionsCurren
              >> tCount=0}}
              >> {MBeanName="mydomain:Location=myserver,Name=jms-notran-
              >> adp_Pool_2,ServerRuntime=
              >> myserver,Type=ConnectorConnectionPoolRuntime"{ActiveConnectionsCu
              >> rrentCount=0}}
              >>
              >> So from that...it looks like the MBean is there. Any ideas why it
              >is not being
              >> found?
              >>
              >> Thanks,
              >>
              >> Jeff
              >>
              >> "Jeff" <[email protected]> wrote:
              >> >
              >> >
              >> >
              >> >Thank you very much!!
              >> >
              >> >I tried your suggestions and created a general Queue Connection Factory
              >> >within
              >> >MQSeries. Then I setup my MQSeries JMS Bridge Destination to use
              >the
              >> >jms-notrans-adp.rar
              >> >resource adapter. With this configuration, I can send messages to
              >MQSeries
              >> >and
              >> >they get forwarded to Weblogic.
              >> >
              >> >But, if I create a XAQueueConnectionFactory within MQSeries I cannot
              >> >get the bridge
              >> >working at all. I realize that MQSeries has a bug with Transactions
              >> >and remote
              >> >servers, but I have MQSeries and Weblogic running on the same machine.
              >> > I thought
              >> >I could setup an XAConnectionFactory in MQSeries, set the MQSeries
              >JMS
              >> >Bridge
              >> >Destination to use the jms-xa-adp.rar and specify Exactly-once QOS
              >and
              >> >it should
              >> >work? I tried it and it didn't work. ( see attachment for weblogic.log
              >> >showing
              >> >exception ).
              >> >
              >> >Here is my config.xml:
              >> > <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
              >> > Name="Request Messaging Bridge" QOSDegradationAllowed="true"
              >> > QualityOfService="Exactly-once"
              >> > SourceDestination="Source JMS Bridge Destination"
              >> > TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
              >> > <JMSBridgeDestination
              >> > ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
              >> > ConnectionURL="t3://localhost:7001"
              >> > DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
              >Name="Target
              >> >JMS Bridge Destination"/>
              >> > <JMSBridgeDestination
              >> > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              >> > ConnectionFactoryJNDIName="MQTestConnectionFactory"
              >> > ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
              >> > DestinationJNDIName="MQTestQueue"
              >> > InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
              >> >Name="Source
              >> >JMS Bridge Destination"/>
              >> >
              >> >Again, thank you very much for your response. It helped me a great
              >deal.
              >> > Any
              >> >thoughts on the above problem please foward them along.
              >> >
              >> >Oh...and to answer the question posed to me, yes the CR081511_61sp3.jar
              >> >file is
              >> >dated 8/13/2002
              >> >
              >> >
              >> >Sincerely,
              >> >
              >> >Jeff
              >> >
              >> >Dongbo Xiao <[email protected]> wrote:
              >> >>Please see my comments inline.
              >> >>
              >> >>
              >> >>Jeff wrote:
              >> >>>
              >> >>> Hi,
              >> >>> I'm really struggling with getting the Message Bridge working with
              >> >>Weblogic 6.1
              >> >>> sp3 and MQSeries 5.2. Currently I have both installed on the same
              >> >>Windows 2000
              >> >>> machine. First I'll pose some questions that I have, then I discuss
              >> >>the error
              >> >>> I'm getting. Here are my questions:
              >> >>>
              >> >>> 1. With the jms-xa-adp.rar there is a ra.xml and a weblogic-ra.xml.
              >> >> Within the
              >> >>> ra.xml deployment descriptor there are config-properties for ConnectionURL,
              >> >>InitialContextFactory,
              >> >>> ConnectionFactoryJNDI, and DestinationType. If my MQSeries Queue
              >> >is
              >> >>the source
              >> >>> jms destination bridge and my weblogic queue is the target jms
              >destination
              >> >>bridge,
              >> >>> what values do I set for the listed config-properties? I can't
              >seem
              >> >>to find any
              >> >>> documentation on what these values should be. Am I missing something?
              >> >> Do these
              >> >>> values even have to be set?
              >> >>>
              >> >>
              >> >>You DON'T have to do anything to the adapter deployment descriptor
              >> >>files.
              >> >>The values given there for the listed config-properties are just
              >default
              >> >>values.
              >> >>The values configured in JMSBridgeDestination instances are the values
              >> >>used to
              >> >>override the default values in the dd file.
              >> >>
              >> >>> 2. When I go to install a Weblogic instance to a different physical
              >> >>machine what
              >> >>> has to be installed in terms of MQSeries? So I'll have MQSeries
              >on
              >> >>physical machineA
              >> >>> and Weblogic on a different physical machineB. I want machineA
              >to
              >> >>forward all
              >> >>> messages placed on a MQSeries Queue to forward them to machineB
              >where
              >> >>the weblogic
              >> >>> Queue resides. Does machineB also have to contain an MQSeries
              >installation?
              >> >>> Or can I just grab the necessary libraries and jar files and place
              >> >>them on the
              >> >>> Weblogic machineB so they can be included?
              >> >>>
              >> >>
              >> >>You don't have to install MQSeries on the machine that the WebLogic
              >> >>server is running. You need the necessary libraries and jar files
              >> >>though.
              >> >>
              >> >>> 3. Is it correct that if I distribute Weblogic onto one physical
              >server
              >> >>and MQSeries
              >> >>> onto a different physical server that I cannot use Exactly-once
              >quality
              >> >>of service?
              >> >>>
              >> >>
              >> >>That is correct and it is a MQSeries transaction limitation.
              >> >>
              >> >>> Other notes:
              >> >>> 1. I have the following patches installed for Weblogic 6.1 sp3:
              >> >>> CR081404_610sp3.jar
              >> >>> CR081511_61sp3.jar
              >> >>>
              >> >>
              >> >>What version of CR081511_61sp3.jar you have? You need the one dated
              >> >on
              >> >>8/13/2002.
              >> >>
              >> >>> 2. Here is the commands I used to create my ConnectionFactory
              >and
              >> >>Queue within
              >> >>> MQSeries:
              >> >>> def xaqcf(MQTestConnectionFactory) qmanager(QM_jeff)
              >> >>> def q(MQTestQueue) qmanager(QM_jeff) queue(default)
              >> >>>
              >> >>
              >> >>The only possible error I see here is that you create a xaqcf while
              >> >your
              >> >>bridge
              >> >>is configured to have "Atmost-once" QOS. The bridge adapter will
              >create
              >> >>XASession
              >> >>if the connection factory is xa because it knows nothing about QOS
              >of
              >> >>the bridge.
              >> >>As I said, there is a limitation in MQSeries transactions, which
              >prevent
              >> >>the
              >> >>transaction to happen between remote servers. Although the bridge
              >does
              >> >>not
              >> >>start the the transaction in your case, but MQSeries xa connection
              >> >>factory may
              >> >>throw error when it detects the other side is remote. Having said
              >that,
              >> >>I am not
              >> >>completely sure this is the problem caused the bridge to fail. I
              >suggest
              >> >>you use
              >> >>a non-xa connection factory on the MQSeries side and see if the problem
              >> >>goes away.
              >> >>
              >> >>> Okay...here is my error:
              >> >>>
              >> >>> <21-Aug-02 11:08:34 ADT AM> <Error> <MessagingBridge> <Error occurred
              >> >>in bridge
              >> >>> "Messaging Bridge" during transferring messages (java.lang.Exception:
              >> >>java.lang.
              >> >>> reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTargetException:
              >> >>> javax.resource.ResourceException: Error creating consumer or receiving
              >> >>message
              >> >>> at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1086)
              >> >>> at weblogic.jms.adapter.JMSBaseConnection.receiveInternal(JMSBaseConnection.java:774)
              >> >>> at weblogic.jms.adapter.JMSBaseConnection.receiveCommon(JMSBaseConnection.java:656)
              >> >>> at weblogic.jms.adapter.JMSBaseConnection.receive(JMSBaseConnection.java:811)
              >> >>> at weblogic.jms.adapter.JMSConnectionHandle.receive(JMSConnectionHandle.java:111)
              >> >>> at java.lang.reflect.Method.invoke(Native Method)
              >> >>> at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:60)
              >> >>> at $Proxy82.receive(Unknown Source)
              >> >>> at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1215)
              >> >>> at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:854)
              >> >>> at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
              >> >>>
              >> >>
              >> >>The latest patch CR081511_61sp3.jar (dated on 8/13/2002) will expose
              >> >>more error
              >> >>information.
              >> >>
              >> >>> Has anyone see this error before? Here is part of my ra.xml file....I
              >> >>just put
              >> >>> these entries in to see what happens:
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>ConnectionURL</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property value>file:/C:/Develop/app_servers/WebSphere/MQSeries</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>InitialContextFactory</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value>com.sun.jndi.fscontext.RefFSContextFactory</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>ConnectionFactoryJNDI</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value>MQTestConnectionFactory</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>DestinationJNDI</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value>MQTestQueue</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>DestinationType</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value></config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>> <config-property>
              >> >>> <config-property-name>AdapterType</config-property-name>
              >> >>> <config-property-type>java.lang.String</config-property-type>
              >> >>> <config-property-value>XATransaction</config-property-value>
              >> >>> </config-property>
              >> >>>
              >> >>
              >> >>As I said earlier, you are not supposed to change the adapter dd
              >file.
              >> >>
              >> >>
              >> >>> Here is a snip of my config.xml:
              >> >>>
              >> >>> <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
              >> >>> Name="Messaging Bridge" QualityOfService="Atmost-once"
              >> >>> SourceDestination="Source JMS Bridge Destination"
              >> >>> TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
              >> >>> <JMSBridgeDestination
              >> >>> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              >> >>> ConnectionFactoryJNDIName="MQTestConnectionFactory"
              >> >>> ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
              >> >>> DestinationJNDIName="MQTestQueue" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
              >> >>> Name="Source JMS Bridge Destination"/>
              >> >>>
              >> >>> <JMSBridgeDestination
              >> >>> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              >> >>> ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
              >> >>> ConnectionURL="t3://localhost:7001"
              >> >>> DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
              >> >>> InitialContextFactory="weblogic.jndi.WLInitialContextFactory"
              >Name="Target
              >> >>> JMS Bridge Destination"/>
              >> >>>
              >> >>
              >> >>Your configuration of the bridge and bridge destinations look fine.
              >> >
              >> >>The last thing is that you have to put MQSeries stuff in your CLASSPATH
              >> >>and PATH for starting the WebLogic server that the bridge is running
              >> >>on.
              >> >>
              >> >>You can also turn on debug for more information.
              >> >>-Dweblogic.Debug.DebugMessagingBridgeStartup=true
              >> >>-Dweblogic.Debug.DebugMessagingBridgeRuntime=true
              >> >>
              >> >>
              >> >>Thanks,
              >> >>Dongbo
              >> >
              

  • Error with pageContext.popBody(); on WLS 6.1 SP3

              Hello,
              I have just migrated my application from WLS6.1 SP2 to WLS6.1 SP3, and I now get
              the following error:
              ***************************************************************** /opt/webapp/usr/bea/wlserver6.1/config/ISOInt/applications/.wlnotdelete_ISOServer1/WEB-INF/_tmp_war_spow/jsp_servlet/_rac/__login.java:152:
              cannot resolve symbol symbol : method popBody () location: class javax.servlet.jsp.PageContext
              while (out != null && out != _originalOut) out = pageContext.popBody(); ^ Note:
              /opt/webapp/usr/bea/wlserver6.1/config/ISOInt/applications/.wlnotdelete_ISOServer1/WEB-INF/_tmp_war_spow/jsp_servlet/_rac/__login.java
              uses or overrides a deprecated API. *****************************************************************
              Please help!
              Thanks in advance, Nicolas
              

    I tested this method in WLS 6.1 SP3 and it works fine. Is it a problem of your JDK?
              Nicolas Marin wrote:
              > Hello,
              >
              > I have just migrated my application from WLS6.1 SP2 to WLS6.1 SP3, and I now get
              > the following error:
              >
              > ***************************************************************** /opt/webapp/usr/bea/wlserver6.1/config/ISOInt/applications/.wlnotdelete_ISOServer1/WEB-INF/_tmp_war_spow/jsp_servlet/_rac/__login.java:152:
              > cannot resolve symbol symbol : method popBody () location: class javax.servlet.jsp.PageContext
              > while (out != null && out != _originalOut) out = pageContext.popBody(); ^ Note:
              > /opt/webapp/usr/bea/wlserver6.1/config/ISOInt/applications/.wlnotdelete_ISOServer1/WEB-INF/_tmp_war_spow/jsp_servlet/_rac/__login.java
              > uses or overrides a deprecated API. *****************************************************************
              >
              > Please help!
              >
              > Thanks in advance, Nicolas
              Regards,
              Ann
              Developer Relations Engineer
              BEA Support
              

  • Performance Monitoring and WLS 8.1 SP3

    I've already send this question to
    "weblogic.developer.interest.management" with no answer. Maybe it was the
    wrong group so I try again here.
    Should I open a case to BEA support ?
    I'm trying to use the performance monitoring tool on a WLS 8.1 SP3 server.
    I've noticed that it is now included in the full distribution of the
    platform
    (apparently not in the service pack 3 where a separate download is
    necessary).
    I have installed a the full platform on Win XP SP1 and started the sample
    server. After booting, I connect to the console and I try to access the
    'Performance
    Monitor' settings by clicking on the corresponding item.
    I only get garbage and the server logs the following:
    <21-Sep-2004 10:20:36 o'clock CEST> <Error> <HTTP> <BEA-101017>
    <[ServletContext
    (id=259488,name=PerformanceMonitor,context-path=/PerformanceMonitor)] Root
    cause
    of ServletException.
    java.lang.NullPointerException
    at
    weblogic.management.console.tags.TextTag.getText(TextTag.java:46)
    at
    weblogic.management.console.tags.LinkTag.doStartTag(LinkTag.java:126)
    at
    weblogic.management.console.tags.StandardBannerTag.printEnd(StandardB
    annerTag.java:186)
    at
    weblogic.management.console.tags.StandardBannerTag.doEndTag(StandardB
    annerTag.java:114)
    at jsp_servlet.__prfinstall._jspService(__prfinstall.java:253)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
    (ServletStubImpl.java:996)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:419)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:463)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:315)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
    n.run(WebAppServletContext.java:6452)
    at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:321)
    at
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    118)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
    rvletContext.java:3661)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
    pl.java:2630)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    --------------- nested within: ------------------
    weblogic.management.console.utils.NestedJspException - with nested
    exception:
    [java.lang.NullPointerException]
    at
    weblogic.management.console.tags.LinkTag.doStartTag(LinkTag.java:141)
    at
    weblogic.management.console.tags.StandardBannerTag.printEnd(StandardB
    annerTag.java:186)
    at
    weblogic.management.console.tags.StandardBannerTag.doEndTag(StandardB
    annerTag.java:114)
    at jsp_servlet.__prfinstall._jspService(__prfinstall.java:253)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
    (ServletStubImpl.java:996)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:419)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:463)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
    pl.java:315)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
    n.run(WebAppServletContext.java:6452)
    at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:321)
    at
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    118)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
    rvletContext.java:3661)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
    pl.java:2630)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    I have a similar problem on Sun Solaris 8 running WLS 8.1SP3 where the
    Performance Monitor has been installed separately.
    (PMConsoleExt.tar.gz)
    any suggestion ?

    Looks like a bug to me. I think you should contact support.

  • Difference between WLS 6.1 SP2   and SP3

    I have recently tested my application in WLS 6.1 SP3 (who work normally in WLS
    6.1 SP2) , I have problem with my jsp page for merging a jsp in another
    What need I do to correct it ?

    Steven,
    The CGIServlet for WebLogic will not run a CGI that doesn't have an extension.
    Just add and extension to your executable and it should run fine.
    jeff
    "Steven" <[email protected]> wrote:
    Hi all,
    I am currently facing a problem with CGI binaries via CGIServlet on WLS
    6.1
    sp4. The web.xml file has been configured correctly as follows:
    -------- start of web.xml -----------
    <servlet>
    <servlet-name>CGIServlet</servlet-name>
    <servlet-class>weblogic.servlet.CGIServlet</servlet-class>
    <init-param>
    <param-name>cgiDir</param-name>
    <param-value>/web/bea6.1sp2/wlserver6.1/config/ngwapp/applications/NGWWebApp
    /cgi-bin</param-value>
    </init-param>
    <init-param>
    <param-name>*.pl</param-name>
    <param-value>/web/perl5/bin/perl5.00405</param-value>
    </init-param>
    <init-param>
    <param-name>*.cgi</param-name>
    <param-value>/web/perl5/bin/perl5.00405</param-value>
    </init-param>
    </servlet>
    <servlet-mapping>
    <servlet-name>CGIServlet</servlet-name>
    <url-pattern>/cgi-bin/*</url-pattern>
    </servlet-mapping>-------- end of web.xml ---------
    When a call is made to http://.../cgi-bin/dialogserver , this results
    in a
    404-File Not Found error.
    The contents of the cgi-bin directory have not been altered and I did
    not
    face this problem earlier when I was using sp2.
    It only happened after I upgraded to sp4. Can anyone help?
    best rgds,
    steven.

  • Wls 7.0 sp2 proxy plugin issue with iplanet6.x and wls 6.1 sp3 app server

    Hi,
    I've a setup with iplanet 6.x webserver using the wls 7.0 sp2 proxy plugin to
    route requests to the clustered app server instances (2 of them) that are in wls
    6.1 sp3.
    The issue is, I'm noticing that the session is not sticky and is getting routed
    onto the other app server instance. The error that I see in the wlproxy.log is
    as follows:
    *******Exception type [PROTOCOL_ERROR] raised
    at line 654 of URL.cpp
    Thu Nov 13 11:30:08 2003 failure on sendRequest() w/ recycled connection
    to Instance1:7001, numfailures=1
    Thu Nov 13 11:30:08 2003 Marking Instance1:7001 as bad
    Thu Nov 13 11:30:08 2003 got exception in sendRequest phase:
    PROTOCOL_ERROR [line 654 of URL.cpp]: unexpected EOF
    reading HTTP status at line 1010
    Thu Nov 13 11:30:08 2003 Failing over after sendRequest exception
    Thu Nov 13 11:30:08 2003 attempt #1 out of a max of 5
    Has anyone seen this issue? Can anyone explain why this issue is occuring.?
    Thanks.

    Did you find a solution for this problem?
    I have somthing very similar going on where I am currently working.
    Thanks!
    Andy.
    "Simple Guy" <[email protected]> wrote:
    >
    Hi,
    I've a setup with iplanet 6.x webserver using the wls 7.0 sp2 proxy plugin
    to
    route requests to the clustered app server instances (2 of them) that
    are in wls
    6.1 sp3.
    The issue is, I'm noticing that the session is not sticky and is getting
    routed
    onto the other app server instance. The error that I see in the wlproxy.log
    is
    as follows:
    *******Exception type [PROTOCOL_ERROR] raised
    at line 654 of URL.cpp
    Thu Nov 13 11:30:08 2003 failure on sendRequest() w/ recycled connection
    to Instance1:7001, numfailures=1
    Thu Nov 13 11:30:08 2003 Marking Instance1:7001 as bad
    Thu Nov 13 11:30:08 2003 got exception in sendRequest phase:
    PROTOCOL_ERROR [line 654 of URL.cpp]: unexpected EOF
    reading HTTP status at line 1010
    Thu Nov 13 11:30:08 2003 Failing over after sendRequest exception
    Thu Nov 13 11:30:08 2003 attempt #1 out of a max of 5
    Has anyone seen this issue? Can anyone explain why this issue is occuring.?
    Thanks.

  • WLS 6.1 SP2 and Apache 1.3.26 Windows NT/2000

    Hi,
    Is there an Apache plugin available for WLS 6.1 (SP2) and Apache 1.3.26 running
    on Windows NT/2000?
    thanks

    I've solved my own problem. I learned that there was a sp4 (let alone a
    sp3) for WLS. Installed that and the problem went away. Sorry for the
    noise.
    -Phil
    Philip Bower <[email protected]> wrote in
    news:[email protected]:
    When I try to deploy the struts-example.war or if I add the struts.jar
    to any other web app I've created, I get this error when I start WLS
    and it tries to deploy that war.
    java.lang.StringIndexOutOfBoundsException
    at weblogic.servlet.internal.WebAppHelper.resolveManifestName
    (WebAppHelper.java:469)
    I'm using version 1.1b3 of struts. I'm having no problems with
    version 1.0.2 of struts.
    I'm guessing its complaining about the manifest file in struts.jar,
    but I don't understand why.
    Here's my version info and the stack trace (my web app is called
    findme in this example). Thanks in advance.
    -Phil
    Server BuildWebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
    All Server Product VersionsWebLogic Server 6.1 SP2 12/18/2001
    11:13:46 #154529 WebLogic XML Module 6.1 SP2 12/18/2001 11:28:02
    #154529
    <Feb 11, 2003 7:45:25 AM EST> <Error> <J2EE> <Error deploying
    application findme: Could not load findme>
    <Feb 11, 2003 7:45:25 AM EST> <Error> <Management> <ApplicationManager
    starting Config caught throwable
    java.lang.reflect.UndeclaredThrowableException:
    java.lang.StringIndexOutOfBoundsException: String index out of range:
    -1
    at java.lang.String.substring(String.java:1525)
    at
    weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper
    .jav a:469)
    at
    weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.j
    ava: 234)
    at
    weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebApp
    Serv letContext.java:3407)
    at
    weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServlet
    Cont ext.java:3376)
    at
    weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContex
    t.ja va:862)

  • WLS 6.1 SP2 and JDK 1.4.0

    In configuring our WLS 6.1 SP2 to run on the released JDK 1.4 and starting the
    server, most things seemed to start fine except for our ObjectIDFactorySession
    EJB. It cacked when it tried to create a bean in the free pool. Stack trace
    below. I know this is not supported, but can anyone shed some light?
    ####<Feb 15, 2002 3:05:03 PM EST> <Warning> <EJB> <023app11> <port7011server>
    <main> <system> <> <010063> <The EJB: ObjectIDFactorySession had an <initial-beans-in-free-pool>
    setting in its weblogic-ejb-jar.xml. An error occurred while creating these initial
    bean instances. The error was:
    nulljava.lang.ExceptionInInitializerError
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:296)
         at java.lang.Class.newInstance(Class.java:249)
         at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:339)
         at javax.rmi.CORBA.Util.<clinit>(Util.java:51)
         at javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:179)
         at javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:58)
         at prototype.com.guardian.util.HomeFactory.createHome(HomeFactory.java:81)
         at prototype.com.guardian.util.HomeFactory.newHome(HomeFactory.java:49)
         at prototype.com.guardian.util.HomeFactory.newSession(HomeFactory.java:95)
         at prototype.com.guardian.fw.ObjectIDFactorySessionBean.ejbCreate(ObjectIDFactorySessionBean.java:31)
         at prototype.com.guardian.fw.ObjectIDFactorySessionBean_r4ogoq_Impl.ejbCreate(ObjectIDFactorySessionBean_r4ogoq_Impl.java:112)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:153)
         at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:198)
         at weblogic.ejb20.pool.Pool.onAfterDeploy(Pool.java:177)
         at weblogic.ejb20.deployer.Deployer.runAfterDeploymentListeners(Deployer.java:1325)
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1013)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.addComponent(Application.java:163)
         at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
         at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:984)
         at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:971)
         at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:956)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:648)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
         at $Proxy65.addTarget(Unknown Source)
         at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:867)
         at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:966)
         at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:886)
         at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:802)
         at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:733)
         at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
         at weblogic.management.mbeans.custom.ApplicationManager.startAdminManager(ApplicationManager.java:278)
         at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
         at $Proxy5.start(Unknown Source)
         at weblogic.management.Admin.startApplicationManager(Admin.java:1184)
         at weblogic.management.Admin.finish(Admin.java:590)
         at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
         at weblogic.Server.main(Server.java:35)
    Caused by: java.lang.RuntimeException: could not find or instantiate any UtilDelegate
    class
         at weblogic.iiop.UtilDelegateImpl.<clinit>(UtilDelegateImpl.java:73)
         ... 77 more
    >

    I've solved my own problem. I learned that there was a sp4 (let alone a
    sp3) for WLS. Installed that and the problem went away. Sorry for the
    noise.
    -Phil
    Philip Bower <[email protected]> wrote in
    news:[email protected]:
    When I try to deploy the struts-example.war or if I add the struts.jar
    to any other web app I've created, I get this error when I start WLS
    and it tries to deploy that war.
    java.lang.StringIndexOutOfBoundsException
    at weblogic.servlet.internal.WebAppHelper.resolveManifestName
    (WebAppHelper.java:469)
    I'm using version 1.1b3 of struts. I'm having no problems with
    version 1.0.2 of struts.
    I'm guessing its complaining about the manifest file in struts.jar,
    but I don't understand why.
    Here's my version info and the stack trace (my web app is called
    findme in this example). Thanks in advance.
    -Phil
    Server BuildWebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
    All Server Product VersionsWebLogic Server 6.1 SP2 12/18/2001
    11:13:46 #154529 WebLogic XML Module 6.1 SP2 12/18/2001 11:28:02
    #154529
    <Feb 11, 2003 7:45:25 AM EST> <Error> <J2EE> <Error deploying
    application findme: Could not load findme>
    <Feb 11, 2003 7:45:25 AM EST> <Error> <Management> <ApplicationManager
    starting Config caught throwable
    java.lang.reflect.UndeclaredThrowableException:
    java.lang.StringIndexOutOfBoundsException: String index out of range:
    -1
    at java.lang.String.substring(String.java:1525)
    at
    weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper
    .jav a:469)
    at
    weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.j
    ava: 234)
    at
    weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebApp
    Serv letContext.java:3407)
    at
    weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServlet
    Cont ext.java:3376)
    at
    weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContex
    t.ja va:862)

  • WLS 6.1 SP2 and Struts 1.1b3 Manifest Problem

    When I try to deploy the struts-example.war or if I add the struts.jar
    to any other web app I've created, I get this error when I start WLS and it
    tries to deploy that war.
    java.lang.StringIndexOutOfBoundsException
    at weblogic.servlet.internal.WebAppHelper.resolveManifestName
    (WebAppHelper.java:469)
    I'm using version 1.1b3 of struts. I'm having no problems with version
    1.0.2 of struts.
    I'm guessing its complaining about the manifest file in struts.jar, but I
    don't understand why.
    Here's my version info and the stack trace (my web app is called findme in
    this example). Thanks in advance.
    -Phil
    Server BuildWebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
    All Server Product VersionsWebLogic Server 6.1 SP2 12/18/2001 11:13:46
    #154529 WebLogic XML Module 6.1 SP2 12/18/2001 11:28:02 #154529
    <Feb 11, 2003 7:45:25 AM EST> <Error> <J2EE> <Error deploying application
    findme: Could not load findme>
    <Feb 11, 2003 7:45:25 AM EST> <Error> <Management> <ApplicationManager
    starting Config caught throwable
    java.lang.reflect.UndeclaredThrowableException:
    java.lang.StringIndexOutOfBoundsException: String index out of range: -1
    at java.lang.String.substring(String.java:1525)
    at
    weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.jav
    a:469)
    at
    weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:
    234)
    at
    weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServ
    letContext.java:3407)
    at
    weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletCont
    ext.java:3376)
    at
    weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.ja
    va:862)
    at
    weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.
    java:815)
    at
    weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
    at weblogic.j2ee.Application.addComponent(Application.java:163)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment
    Target.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment
    Target.java:144)
    at
    weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java
    :76)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp
    l.java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:
    621)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe
    anImpl.java:359)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy29.addWebDeployment(Unknown Source)
    at
    weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployme
    nt(WebServerMBean_CachingStub.java:1121)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment
    Target.java:315)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deploymen
    tTarget.java:279)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(
    DeploymentTarget.java:233)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploy
    mentTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp
    l.java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:
    621)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe
    anImpl.java:359)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy28.updateDeployments(Unknown Source)
    at
    weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments
    (ServerMBean_CachingStub.java:2761)
    at
    weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(App
    licationManager.java:370)
    at
    weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManag
    er.java:160)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp
    l.java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:
    621)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe
    anImpl.java:359)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy36.start(Unknown Source)
    at
    weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start
    (ApplicationManagerMBean_CachingStub.java:480)
    at
    weblogic.management.Admin.startApplicationManager(Admin.java:1180)
    at weblogic.management.Admin.finish(Admin.java:590)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
    at weblogic.Server.main(Server.java:35)
    --------------- nested within: ------------------
    weblogic.j2ee.DeploymentException: Could not load findme - with nested
    exception:
    [java.lang.StringIndexOutOfBoundsException: String index out of range: -1]
    at
    weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:431)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
    at weblogic.j2ee.Application.addComponent(Application.java:163)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment
    Target.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment
    Target.java:144)
    at
    weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java
    :76)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp
    l.java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:
    621)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe
    anImpl.java:359)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy29.addWebDeployment(Unknown Source)
    at
    weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployme
    nt(WebServerMBean_CachingStub.java:1121)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment
    Target.java:315)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deploymen
    tTarget.java:279)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(
    DeploymentTarget.java:233)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploy
    mentTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp
    l.java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:
    621)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe
    anImpl.java:359)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy28.updateDeployments(Unknown Source)
    at
    weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments
    (ServerMBean_CachingStub.java:2761)
    at
    weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(App
    licationManager.java:370)
    at
    weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManag
    er.java:160)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp
    l.java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:
    621)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe
    anImpl.java:359)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy36.start(Unknown Source)
    at
    weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start
    (ApplicationManagerMBean_CachingStub.java:480)
    at
    weblogic.management.Admin.startApplicationManager(Admin.java:1180)
    at weblogic.management.Admin.finish(Admin.java:590)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
    at weblogic.Server.main(Server.java:35)
    >
    <Feb 11, 2003 7:45:32 AM EST> <Error> <J2EE> <Error deploying application
    struts-example: Could notload struts-example>
    <Feb 11, 2003 7:45:32 AM EST> <Error> <Management> <Error deploying
    application .\config\mydomain\applications\struts-example.war:
    java.lang.reflect.UndeclaredThrowableException>

    I've solved my own problem. I learned that there was a sp4 (let alone a
    sp3) for WLS. Installed that and the problem went away. Sorry for the
    noise.
    -Phil
    Philip Bower <[email protected]> wrote in
    news:[email protected]:
    When I try to deploy the struts-example.war or if I add the struts.jar
    to any other web app I've created, I get this error when I start WLS
    and it tries to deploy that war.
    java.lang.StringIndexOutOfBoundsException
    at weblogic.servlet.internal.WebAppHelper.resolveManifestName
    (WebAppHelper.java:469)
    I'm using version 1.1b3 of struts. I'm having no problems with
    version 1.0.2 of struts.
    I'm guessing its complaining about the manifest file in struts.jar,
    but I don't understand why.
    Here's my version info and the stack trace (my web app is called
    findme in this example). Thanks in advance.
    -Phil
    Server BuildWebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
    All Server Product VersionsWebLogic Server 6.1 SP2 12/18/2001
    11:13:46 #154529 WebLogic XML Module 6.1 SP2 12/18/2001 11:28:02
    #154529
    <Feb 11, 2003 7:45:25 AM EST> <Error> <J2EE> <Error deploying
    application findme: Could not load findme>
    <Feb 11, 2003 7:45:25 AM EST> <Error> <Management> <ApplicationManager
    starting Config caught throwable
    java.lang.reflect.UndeclaredThrowableException:
    java.lang.StringIndexOutOfBoundsException: String index out of range:
    -1
    at java.lang.String.substring(String.java:1525)
    at
    weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper
    .jav a:469)
    at
    weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.j
    ava: 234)
    at
    weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebApp
    Serv letContext.java:3407)
    at
    weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServlet
    Cont ext.java:3376)
    at
    weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContex
    t.ja va:862)

  • Running Weblogic 8.1 SP3 and IPlanet 6.0 on same machine

    I have requirement to run Weblogic Platform SP3 and IPlanet 6.0 servers on same Solaris machine
    for a client of ours.
    Please let me if we can do this. What kind of issues we may run into.
    Thanks,
    Sanjay

    Hi
    Of course, you can install both at the same machine.
    Only remember the memory required ... and the real memory available ... this for don't have swap problems.
    Remember too if you are planning to create WLS clusters ... BEA recommends 1 cluster per CPU ... and reserve 1 CPU for the iPlanet web Server. Even, you can install all clusters and web server as your machine support ( under load, try to mantain the CPU usage under 70-80%).
    Jin

  • ArrayStoreException in WLS 8.1SP3: Object and inner type of array differs

    Has anyone seen this? We seem to get them from time to time, am running WLS 8.1 SP3 on JRockit 1.4.2.03. Stack trace follows.
              cheers
              dim
              <BEA-000802> <ExecuteRequest failed
              java.lang.ArrayStoreException: Object and inner type of array differs.
              java.lang.ArrayStoreException: Object and inner type of array differs
              at weblogic.rjvm.BasicOutboundRequest.sendReceive()Lweblogic.rmi.spi.InboundResponse;(BasicOutboundRequest.java:108)
              at weblogic.rmi.internal.BasicRemoteRef.invoke(Ljava.rmi.Remote;Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;[Ljava.lang.Object;Ljava.lang.reflect.Method;)Ljava.lang.Object;(BasicRemoteRef.java:137)
              at weblogic.cluster.replication.ReplicationManager_813_WLStub.update(Lweblogic.cluster.replication.ROID;ILjava.io.Serializable;)V(Unknown Source)
              at weblogic.cluster.replication.ReplicationManager.updateSecondary(Lweblogic.cluster.replication.ROID;Ljava.io.Serializable;Ljava.lang.String;)Ljava.lang.Object;(ReplicationManager.java:811)
              at weblogic.servlet.internal.session.ReplicatedSessionData.syncSession()V(ReplicatedSessionData.java:490)
              at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Ljavax.servlet.http.HttpSession;)V(ReplicatedSessionContext.java:184)
              at weblogic.servlet.internal.ServletRequestImpl.syncSession()V(ServletRequestImpl.java:2471)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic.servlet.internal.ServletRequestImpl;Lweblogic.servlet.internal.ServletResponseImpl;)V(WebAppServletContext.java:3679)
              at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel.ExecuteThread;)V(ServletRequestImpl.java:2630)
              at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
              at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
              Caused by: java.lang.ArrayStoreException: Object and inner type of array differs
              at java.io.ObjectInputStream.readObject(Unknown Source)
              at java.util.HashMap.readObject(Unknown Source)
              at java.io.ObjectInputStream.readSerialData(Unknown Source)
              at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
              at java.io.ObjectInputStream.readObject0(Unknown Source)
              at java.io.ObjectInputStream.readSerialData(Unknown Source)
              at java.io.ObjectInputStream.readObject(Unknown Source)
              at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:120)
              at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:117)
              at weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
              at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
              ... 3 more

    You have to be careful how you define your complex elements, define complex elements outside of the root element or in a seperate file and reference them.
              While the following is syntactically correct, in weblogic you will result in the error you had previously
              <element>
              <complex type>
              </complex type>
              </element>
              Instead do
              <element type="ir:ComEx">
              <complex type name="ComEx"></complex type>
              outside of the root element
              Had this exact same problem today, this is how I fixed it

  • Crystal Report 2008 SP3 and BO XI 3.1 conflict

    Hi every body,
    We have a BOE system:
    BO XI 3.1
    Oracle db 10g
    All running successful and can create some types of WebI report.
    But we also want reports with Crystal Report.
    1> So we install Crystal Report 2008 SP3 (without knowing the conflict error between BO XI 3.1 and Crystal Report 2008 SP3 and overwrite some .dll file). After installing, we can not create WebI report any more. And a error message box display: "DBDriver failed to load: C:\Program File\Business Objects\BusinessObjects ENterprise12.0\win32_x86\dataAccess\connectionServer\dbd_oci.dll ".
    2> We uninstall Crystal Report SP3. But this is not the solution. Still error because of missing .dll files.
    3> We open BO XI 3.1 setup and repair BO XI 3.1. Even we uninstall BO XI 3.1, delete all of its components and delete in regedit key. We install BO XI 3.1 again. Now we have full .dll file, not missing them any more. But when we open universe and click on Table browser, cannot fetching any tables.
    We set rights for Oracle DB user again. But still error: cannot fetching.
    4> We searched the solution for this problem on the internet. But not worked, no answer.
    Can somebody help me bring back the BOE system state again ? pls   :"<
    T______T

    Hi Paul,
    I hope I read your question right!
    Yes, It is possible to run XIR2 and 3.1 on the same server although it's not recommended by BO. You will need to make sure they are both pointing to different CMS databases and different FRS repositories, like you already mentioned you will need to specify different ports for the CMS db and Tomcat.
    Why not uninstall Business Objects XI R2 in your BO development environment or a spare server (if you have one), and do a clean install of XI 3.1 SP3.
    Tip: If you were already having performance issues with your XI R2 environment, I would seriously consider upgrading the hardware. XI 3.1 needs a bit more RAM and CPU than XI R2
    Regards
    Rim Geurts

  • JAX-WS Client throws NULL Pointer Exception in NW 7.1 SP3 and higher

    All,
    My JAX-WS client is throwing an exception when attempting to create a client to connect to the calculation service. The exception is coming out of the core JAX-WS classes that are part of NetWeaver. (see exception below)
    Caused by: java.lang.NullPointerException
         at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatchContextExistingPort(SAPServiceDelegate.java:440)
         at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatchContext(SAPServiceDelegate.java:475)
         at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatch(SAPServiceDelegate.java:492)
         at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.createDispatch(SAPServiceDelegate.java:484)
         at javax.xml.ws.Service.createDispatch(Service.java:166)
    I have done some research and it appears that as of NetWeaver 7.1 SP3 SAP stopped using the SUN JAX-WS runtime and implemented their own SAP JAX-WS runtime. I also took the time to decompile the jar file that contained the SAPServiceDelegate class which is throwing the null pointer exception. (see method from SAPServiceDelegate below)
        private ClientConfigurationContext createDispatchContextExistingPort(QName portName, JAXBContext jaxbContext)
            BindingData bindingData;
            InterfaceMapping interfaceMap;
            InterfaceData interfaceData;
            bindingData = clientServiceCtx.getServiceData().getBindingData(portName);
            if(bindingData == null)
                throw new WebServiceException((new StringBuilder()).append("Binding data '").append(portName.toString()).append("' is missing!").toString());
            QName bindingQName = new QName(bindingData.getBindingNamespace(), bindingData.getBindingName());
            interfaceMap = getInterfaceMapping(bindingQName, clientServiceCtx);
            interfaceData = getInterfaceData(interfaceMap.getPortType());
            ClientConfigurationContext result = DynamicServiceImpl.createClientConfiguration(bindingData, interfaceData, interfaceMap, null, jaxbContext, getClass().getClassLoader(), clientServiceCtx, new SOAPTransportBinding(), false, 1);
            return result;
            WebserviceClientException x;
            x;
            throw new WebServiceException(x);
    The exception is being throw on the line where the interfaceMap.getPortType() is being passed into the getInterfaceData method. I checked the getInterfaceMapping method which returns the interfaceMap (line above the line throwing the exception). This method returns NULL if an interface cannot be found. (see getInterfaceMapping method  below)
       public static InterfaceMapping getInterfaceMapping(QName bindingQName, ClientServiceContext context)
            InterfaceMapping interfaces[] = context.getMappingRules().getInterface();
            for(int i = 0; i < interfaces.length; i++)
                if(bindingQName.equals(interfaces<i>.getBindingQName()))
                    return interfaces<i>;
            return null;
    What appears to be happening is that the getInterfaceMapping method returns NULL then the next line in the createDispatchContextExistingPort method attempts to call the getPortType() method on a NULL and throws the Null Pointer Exception.
    I have included the code we use to create a client below. It works fine on all the platforms we support with the exception of NetWeaver 7.1 SP3 and higher (I already checked SP5 as well)
          //Create URL for service WSDL
          URL serviceURL = new URL(null, wsEndpointWSDL);
          //create service qname
          QName serviceQName = new QName(targetNamespace, "WSService");
          //create port qname
          QName portQName = new QName(targetNamespace, "WSPortName");
          //create service
          Service service = Service.create(serviceURL, serviceQName);
          //create dispatch on port
          serviceDispatch = service.createDispatch(portQName, Source.class, Service.Mode.PAYLOAD);
    What do I need to change in order to create a JAX-WS dispatch client on top of the SAP JAX-WS runtime?

    Hi Guys,
    I am getting the same error. Any resolution or updates on this.
    Were you able to fix this error.
    Thanks,
    Yomesh

  • BO XI 3.1 SP3 and Excel 2010

    Hi There
    My BO is BO XI 3.1 SP3, and excel is 2010, my webi report has over 65523 rows, but I found in the excel, it will split into two tabs, it does not use excel 2010 feature
    does any one know the reason?
    thanks

    Excel 2010 is not suportive by BO XI 3.. It is possible in BO XI 4.0. You can try What Gowtam Allu said, but I am not sure if it works.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/4079f8f6-2b49-2d10-d790-bc596012dc25?quicklink=index&overridelayout=true

Maybe you are looking for

  • XML to DDL

    HI I'm using DBMS_METADATA.GET_SXML to retreive the dll in xml. Its in XML becuase I need a way to process each table's column, constraints etc, inidividually and xml nodes helps do this. Once processed the node(s) need to be transformed back into dd

  • Unit Cost of non stock material - Hubwoo Catalogue

    Hi Team, There is one requirement to transfer the the cost of matrial from SAP PM to ArcFM. Here the materials are assigned to the operations in the PM order. Here we want to transfer the service cost and material cost of the particular operation to

  • How do I restore photos from backup into iPhoto 2?

    I tried to create a backup of only one roll of photos in my Photo Library, but when I dragged it to an external hard drive, instead of copying it, it moved it, so that afterwards I could no longer use iPhoto in my computer to open any of the pictures

  • DSL, LAN, DHCP & DNS settings.

    I am having trouble with setting up my Solaris 10 on the internet. I use SBC DSL for my Windows and Linux programs without any problems. But, the Solaris can't access eth0, or my modem for a direct connection, and I can't establish a proxy connection

  • In DTP Detailed fiscal year variant not processed

    Hi All, I installed and activated CUBE 0IC_C03, now while executing the DTP  2LIS_03_UM / LOGSYSDEV -> 0IC_C03 it throws Error 'Detailed fiscal year variant not processed' then in sdn i searched they told that i have to maintain variant in SPRO TC or