WL6.1 Stub bug ?

Hello, can someone help me ?
Thanks in advance
I have this exception :
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must initialize before
invoke ] at weblogic.utils.Debug.assert(Debug.java:84) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:218)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35) at $Proxy107.go(Unknown
Source)
I work on a single WL6.1 sp2 instance, WinNT, development mode.
I have 2 ears: EAR1 (1 ejb-module) and EAR2(1-ejb-module). EAR1 contains a client
jar that acts as a business delegate for EAR2 (lookup + home creation + remote
creation + service invocation). I have a client jar (external app) that calls
the ejb in EAR1; The ejb in EAR1 calls the ejb in EAR2 by the business delegate.
After the first invocation of the business delegate, the home is cached (static
variable in a service locator accessed by the business delegate). At the second
invocation, the business delegate is instantiated again, the home is in the cache
(no more lookups), the remote is created again. And everything is ok.
If I redeploy (auto-deploy in the application directory) EAR2, without changing
anything in it, but only "touching" the ear file in the file system (>touch ear2.ear),
if I call EAR1, it fails to call EAR2. Always. I have to "touch" EAR1 too.
I need to change sometimes the implementation of the ejb in EAR2, so I need to
redeploy it. I wouldn't like to redeploy also the "client" ears (I'll have more
than one, in production).
My question is :
1) Is this a WL (stub / dyn proxy implementation) bug ?
2) If not, cannot I implement home caching in my business delegate ? Do I have
to look up "every time" my home ? (on the same instance the lookup is optimized,
but not if I deploy EAR2 on another instance).
More info :
6.1 sp3 ----> same problem
7.0 ----> it works (different WL stub implementation)
Can someone tell me something ?
Thanks in advance
Mark Cordobal

Similar Messages

Sharing SSBs home...

Hi, it's been a while since I've done any EJBs and I need your help to refresh
my memory. We're implementing a facade and have a stateless session bean that
serves as a workflow bean that will be used by all the clients. The question I
have is the following: Can a home object be shared by all the clients??? In other
words I'd like to create a home object when the system starts up, put it into
my cache and then whenever any client needs to access the bean it gets the home
from a cache and calls ejbCreate() on it. The container will decide whether it
needs to create or return already existing bean from the pool. Is there a problem
when client1 calls create() on the home object and at the same time client2 calls
create() on the same home object? I guess to put the question shortly - is home
interface thread safe?
Thank you very much

Homes are thread safe.
** But pay attention at home caching in WL6.1 ** :
if your client is in a different ear (EAR2), and you have a cache for the home
of the facade to your services (EAR1), when you redeploy EAR1, you have to "reload"
also EAR2 (even if you do not change the interfaces (!!) )
Or you'll get a weblogic.utils.AssertionError.
This in WL6.1.
In 7.0 it works (you can redeploy EAR1 without "reloading" EAR2)
It looks like a WL6.1 stub implementation bug.
Regards
Mark Cordobal
"David" <[email protected]> wrote:
>
Hi, it's been a while since I've done any EJBs and I need your help to
refresh
my memory. We're implementing a facade and have a stateless session bean
that
serves as a workflow bean that will be used by all the clients. The question
I
have is the following: Can a home object be shared by all the clients???
In other
words I'd like to create a home object when the system starts up, put
it into
my cache and then whenever any client needs to access the bean it gets
the home
from a cache and calls ejbCreate() on it. The container will decide whether
it
needs to create or return already existing bean from the pool. Is there
a problem
when client1 calls create() on the home object and at the same time client2
calls
create() on the same home object? I guess to put the question shortly
- is home
interface thread safe?
Thank you very much

Idlj bug: compiler generates stubs files 1000 of times...

The idlj compiler generates client stubs multiple times while compiling a single idl file. For example the following idl file results in the idlj compiler generating the client stubs 5 times:
module com { module adobe { module ids {
     module preferences {
          interface BookPrefs;
module com { module adobe { module ids {
          module book {
          interface Book {
               short add(in short x, in short y);
module com { module adobe { module ids {
     module preferences {
          interface BookPrefs {
               short delete(in short x, in short y);
}; }; };It simply redundantly generates the stubs, overwriting each time. This is not generally a problem for a file of this size, but we have a large idl file that takes several hours to generate stubs for. If I look at CPU usage it is about at 10%, but if I look at disk I/O it is pegged at 100%. Through some simple debugging I discovered that idlj is writing stubs for each interface many thousands of times.
I've downloaded the source to idlj and have identified the problem and have a fix. the large idl file that used to take several hours, now takes less than 30 seconds.
I'd like to get this bug reported and fixed. How do I go about that?

I was going through some very old emails, and I found your post, which I
missed last year (8 months ago!). If you are still interested, send
me the details, and we will take care of this. Send email to
[email protected]

WL6.1sp2: Autodeploy and ear files - probable bug

I've a beef with autodeploy in WL6.1sp2 when working
with full-blown ear files.
If I change an API in one of my beans or add an API then
drop that updated ear file into the applications directory,
it doesn't work.
For some reason the autodeploy mechanisms have a tmp
directory for my ear in the main wlserver6.1 directory
(such as: tmp_ejbipusushi8880) that seems to be getting
in the way. When I delete that, the autodeploy then works.
(Skipping a couple of cleanup bits, restart, etc.)
Thus, I think there's a bug lurking in the autodeploy
mechanisms. What a pain that was to figure out how to get
around.
Joel

Hi..
Please see my reply to your previous posting. If that doesn't help then
please open a case with support.
Thanks,
Michael
Joel Riedesel wrote:
I've a beef with autodeploy in WL6.1sp2 when working
with full-blown ear files.
If I change an API in one of my beans or add an API then
drop that updated ear file into the applications directory,
it doesn't work.
For some reason the autodeploy mechanisms have a tmp
directory for my ear in the main wlserver6.1 directory
(such as: tmp_ejbipusushi8880) that seems to be getting
in the way. When I delete that, the autodeploy then works.
(Skipping a couple of cleanup bits, restart, etc.)
Thus, I think there's a bug lurking in the autodeploy
mechanisms. What a pain that was to figure out how to get
around.
Joel--
Michael Young
Developer Relations Engineer
BEA Support

NetBeans MobilityPack 5 BUG?? how can I send a byte array?

I�ve created a WebApp and a Simple servlet with one public method.
public byte[] getStr(byte[] b) {
String s = "A string";
return s.getBytes();
Then I've used "Mobile To Web App" wizard to generate stubs to that getStr method. And when I�ve tried to call that getStr method:
byte[] aByte = "st".getBytes();
byte[] b = client.getStr(aByte);
I've got an error at Server in Utility.java in generated ReadArray method.
* Reads an array from the given data source and returns it.
*@param source The source from which the data is extracted.
*@return The array from the data source
*@exception IOException If an error occured while reading the data.
public static Object readArray(DataInput in) throws IOException {
short type = in.readShort();
int length = in.readInt();
if (length == -1) {
return null;
} else {
switch (type) {
case BYTE_TYPE: {
byte[] data = new byte[length];
in.readFully(data);
return data;
default: {
throw new IllegalArgumentException("Unsupported return type (" + type + ")");
At this line "in.readFully(data);" I�ve got an EOFException.
The the aByte = "st".getBytes(); was 2bytes long and at the server "int length = in.readInt();" it was 363273. Why?
All code was generated by NetBeans Mobility pack 5 it's not mine so its a bug?
How can I fix this?

I found that bug. I've described it here
http://www.netbeans.org/issues/show_bug.cgi?id=74109
There's a solution how to fix the generated code.

N78 v20.149 Bug List Thread

Hi everyone, thanks for all your advice and comments now that v20.149 has been released here (only on FOTA and not NSU yet) are the changes I have noticed, along with some newly discovered bugs:
NOTE: all the documented features/improvements are performed with the Theme Effects turned on.
Changes/Improvements/New features I have noticed from v12.046 to v20.149:
Standby screen:
*While scanning for wireless networks in the home screen, instead of saying “No networks found” as in the past, it says “No WLANs available”, also some other minor name changes in this menu.
*Share online icon in standby screen seems to be different
*When going back to the music player via the standby screen, it goes straight into the player without a fading in/out transition as it did before when Theme Effects are turned on (an instantaneous response). However, for going into other sections from the standby screen the fade in/out transition still occurs.
*When Music Player is operating, and seeing the track name on the screen, and then when one song ends and goes to the next track, the speed at which this happens is much improved although not flawless (there is still some lag).
*Scrolling up and down through the entries in the standby screen is very fast and not slow like before.
Call log, Contacts and calling function:
*Calling speed (from standby screen to Contacts or Call Log) and transition to call/disconnected screens much faster and improved
*Faster resume of music playback after call is ended
*Volume bar is changed from ten dotted increment to continuous coloured volume triangle (this has also been reflected in other menus and options throughout the phone)
Maps:
*Maps updated to version 2.0
Music Player:
*Much faster interface and speed through all menus
*Pressing volume keys is much improved and faster and more accurate response than before (where it may have taken time in the past for the volume level to update)
*Music controls (i.e. Rewind, Fast forward, play/pause, stop) are no longer the same colour as the matching theme, now it is just the same light green colour across all themes
*Visualisations are still a bit slow, but faster than before
Photos:
*Transition into the Photos application is much faster than before
*Scrolling through photos and videos and the like is still jerky and thumbnails still take a while to be updated from pixelated to clear thumbnails
Settings:
*In Themes, there is a new theme called Music (very yucky looking I must admit)
*Power saver now includes “Now playing” option, so when the backlight goes off, the currently playing song and time are displayed on the screen for a number of seconds before disappearing. This occurs before keypad lock is activated, and when any key is pressed, the names of the song light up (in green or red). Also when going from one track to the next while this screensaver is activated, the date is displayed briefly.
Other:
*General speed improvements across all menus and applications
*Help function is much faster and speed improved
*New help topics added to Help function
*Speed dial now works without any lag
*New RealPlayer interface and version updated (where the RealPlayer screen is no longer displayed but grey bars on top and bottom of the video)
*About application has been updated for the year dates so that they are all “2009”.
*Installation of applications and refresh of available applications within the Application Manager is much improved and faster (although icons for installed applications are now not displayed)
*”Application update” added to Applications
*Carousel menu has new options under each heading
*Navi-wheel seems to have been tweaked a bit more
*Background light settings actually work now
*Truncated email-account login name fixed
Other documented changes that have been stated by others for v13.052 and now v20.149:
*Improvements:
Connectivity:
- System Error message appears when trying to stream a clip from a busy server
- Timestamp corruption error in long streaming which leads to 'Error in receiving live
content'
-VPN not working through WLAN in offline mode
- Priorities of protected IAPs could not be changed via UI
- Mail For Exchange did not play tone for every mail received as per S60 3.0 and 3.1
products
- DM settings were not generated automatically when Email settings are defined in variant
Photos:
- Thumbnail displayed does not match actual image if user deletes thumbnail file in
memory card private folder
Internet:
- UI issues when viewing Youtube videos
Music:
- Playing WMA audio files improved
- IHF cannot be enabled during call when FMT is on
- DRM: The ampersand character ('&') encoding is not correct
Other changes:
- Weekly recurring clock alarm always sets for the current weekday regardless of the day
chosen
- Contact Groups are not titled correctly
- Help text located in settings/general/Navi Wheel
- Help text for Voice commands
- Access point generation difficulties after factory reset
New features:
- Boingo – Cancelled
- Comes With Music (CWM) - This SW Version includes CWM enablers
Changes:
Bluetooth
* N78 to CK-07W Audio Lost at regular intervals
* Call Not Working With Bluetooth Headset
WLAN
* WLAN APN passed along with SDP contents is not utilized by Real Player
Power Management
* Sleep current too high while video applications at background
GPS
* The phone freezes when launching the Trip distance by clicking the link in Help content
PC Suite
* Harvester Server doesn’t close all necessary connections to other services during backup/restore
SIM/USIM
* Incorrect error codes are passed by TSY from SIM server to application layer for Smart card feature
Radio
* RadioLauncher gets corrupted state when VisualRadio exits
* FM frequency range extends below 87.5MHz
Podcast
* Podcasts: garbled search results when entering a number as the search title
Photos
* Crash when launching Photos application after restoring from memory card
* Slideshow doesn’t work after used device for a while
Internet
Maps
* Maps:”My position” and “My place” are translated into the same Chinese
Messaging
* E-mail username truncated causes problem with login
* Adding new number from SMS to existing number in ADN causes corruption
Download!
* Download client doesn’t work with certain operators WAP APN
Other Changes:
* Java platform version number not updated in IAD
* Widget installer plugin cannot be upgraded
* Removing battery during alarm makes the device unusable
* Stub sis file doesn’t include httptransfer component
* Paths are incorrect in cenrep creation file (Naviscroll and FMTX affected)
* Internal Debugging tool wrongly included in Production SW
* Device cuts off URL parameter in RTSP streaming link
* Delivery via Device Management corrupts EAP-FAST PAC file
* TCK failure with HTTP and AMR Combination
* SpaceUI doesn’t allow for changes when a default number is assigned in Phonebook
* Display corrupts with 3rd party application BestCalc
Bugs/missing features already found:
*Will not let you enter the Date and Time settings, instead going back to the main menu
*Will not let you enter settings for the alarm Clock, instead going back to the main menu (related to the Date and Time above)
*Carousel menu by pressing that small silver key is still inconsistent, sometimes appears with scroll bar and performance is still slow
*Still no N-gage client within firmware
I have yet to check all the bugs that were documented for v12.046 in the thread /discussions/board/message?board.id=swupdate&thread.id=42047&page=4, but I will go about that very soon and document all the changes here in this thread. But so far, so good, the firmware appears to be a lot better and more stable than 12.046. Again, thanks to all users for their current feedback on problems. Remember to be sure to add your experiences with the N78 here!
Message Edited by celandine on 15-Jan-2009 02:59 PM

My n78 froze at the standby screen when it rebooted itself during the upgrade from v12 to v20.149. The background image and active standby icons appeared, but nothing else - no network provider name, no battery or signal level indicator, no clock, no calender entries, no wlan scanning, no share online. I left it for 15 minutes or so before crossing my fingers and removing and replacing the battery (since the power button did nothing). Not a great start I thought. But it started up ok.
new/unfixed bugs
The clock alarm did not switch the phone back on after the first 5 minute snooze, but it did do the snooze resume thing when I actually switched the phone on 15 minutes later... I setup a "within 24 hours" alarm and that had no problems switching on the phone several times with a 1 minute snooze so I guess I'll have to wait until tomorrow morning to see if my weekday alarm snoozes properly now...
The FM transmitter was transmitting at 107.5 even though the settings screen and active standby message showed 106.9 which I had set it to before the update... Viewing and saving the fm transmitter settings did update the frequency to 106.9 though.
I'm still unable to set default numbers for some contacts - the contacts app exits to the standby screen.
Unable to zoom camera/photos when musicplayer and fm transmitter activated.
improvements
At least the loudspeaker function works after using the FM transmitter now.
Playback of videos through the images app seems much improved - i.e. it actually plays video clips all the way through without freezing the picture.
I'll post more if I notice anything

BUG in WLE IDL compiler

Hi,
I want to report a bug in the WLE5.0 IDL compiler. It occurs in the
generated stub, skeleton and implementation files (*c,*s and _i)
files. Here is a description of the problem:
Say we have the following IDL:
Filename:filewithmoduleM1.idl
module M1 {
#include "BoundaryClasses\CORBA\Types\M1Complex.idl"
interfaceService {
boolean method1 (
interface Factory {
Service findService ();
The IDL compiler loses track of the Module M1 and does not scope the
interfaces inside the module. Henck even if we register a factory called
APSBalReporting::Factory it is registered as Factory. The problem gets
more interesting if we have another module that includes the first as
shown below:
Filename:filewithmoduleM2.idl
#include filewithmoduleM1.idl
module M2 {
#include "BoundaryClasses\CORBA\Types\M1Complex.idl"
interface Service {
boolean method2 (
interface Factory {
Service findService ();
Here it thinks that Service and Factory are the ones for module M1 and
so generates the return type as M1::Factory and M1::Service instead of
M2::Factory and M2::Service.
The IDL compiler used to work fine with code such as the above
previously.
Please let me know if you have any feedback for this bug and if any of
you have tried it.
Thanks,
Raman Ramesh
678-358-3581
mailto:[email protected]
www.cicube.com

BEA customers who need this problem corrected must use WLE 5.1. A patch to WLE 5.0
or WLE 5.0.1 is not available.
Wendell MacKenzie wrote:
We received a patch that fixed this problem under WLE 5.01. There were problems
back porting the fix into the 5.0 release. Talk to Tom Hegadorn.
Mary Ann Slavin wrote:
Actually that is Clarify CASE 162819 not a Clarify CR number. That particular
problem has been corrected in WLE 5.1. This problem cannot be patched in WLE
5.0.1, so if you have encountered this problem, you should upgrade to WLE 5.1
and it is corrected as part of the base product, no patch required.
MAS
Wendell MacKenzie wrote:
You have 2 choices:
- upgrade to Version 5.1 (which includes CR162819)
- obtain the patch from BEA support for CR162819 to fix a bug in the IDL
compiler
that caused Module and Interface scope names to work incorrectly. Also,
where
nesting of IDL #includes exceeded 1 level deep, this caused problems.
You will have to install the patch onto version 5.01.
Regards,
Wendell MacKenzie
Ram Ramesh wrote:
Hi,
I want to report a bug in the WLE5.0 IDL compiler. It occurs in the
generated stub, skeleton and implementation files (*c,*s and _i)
files. Here is a description of the problem:
Say we have the following IDL:
Filename:filewithmoduleM1.idl
module M1 {
#include "BoundaryClasses\CORBA\Types\M1Complex.idl"
interfaceService {
boolean method1 (
interface Factory {
Service findService ();
The IDL compiler loses track of the Module M1 and does not scope the
interfaces inside the module. Henck even if we register a factory called
APSBalReporting::Factory it is registered as Factory. The problem gets
more interesting if we have another module that includes the first as
shown below:
Filename:filewithmoduleM2.idl
#include filewithmoduleM1.idl
module M2 {
#include "BoundaryClasses\CORBA\Types\M1Complex.idl"
interface Service {
boolean method2 (
interface Factory {
Service findService ();
Here it thinks that Service and Factory are the ones for module M1 and
so generates the return type as M1::Factory and M1::Service instead of
M2::Factory and M2::Service.
The IDL compiler used to work fine with code such as the above
previously.
Please let me know if you have any feedback for this bug and if any of
you have tried it.
Thanks,
Raman Ramesh
678-358-3581
mailto:[email protected]
www.cicube.com

A swf loader bug?

It looks like I may have found a bug in the swf loader. Before I submit this problem I want to make sure there is not something I'm missing in my code. I wrote this class to load a tutorial when the user first launches a sub application in a project I'm working on. This is a simplified version of the class that exemplifies the problem. The same methods I use to launch the swf from within an mxml work just fine, but when I externalize the process in this class, I can hear the tutorial, but I get no visual. Is this a bug or am I missing something?
Here is the tutorial launcher class:
package proj.fuego.utils
     import flash.events.Event;
     import mx.controls.SWFLoader;
     import mx.flash.UIMovieClip;
     public class TutPlayerSimple extends UIMovieClip
          private var gutLoader:SWFLoader;
          public function TutPlayerSimple(fullTutorialPath:String)
             gutLoader = new SWFLoader();
             gutLoader.addEventListener(Event.COMPLETE, addToStage);
             gutLoader.load(fullTutorialPath + ".swf");
             //addChild(gutLoader);
          private function addToStage(evt:Event):void
             addChild(evt.target.content);
This is my mxml:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" minWidth="1024" minHeight="768" applicationComplete="application1_applicationCompleteHandler(event)">
     <mx:Script>
          <![CDATA[
             import mx.controls.SWFLoader;
             import mx.events.FlexEvent;
             import proj.fuego.utils.TutPlayerSimple;
             private var fullTutorialPath:String = "ll_tut";
             private var tutPlayer:TutPlayerSimple;
             protected function application1_applicationCompleteHandler(event:FlexEvent):void
                  // TODO Auto-generated method stub
                  var context:LoaderContext = new LoaderContext();
                  tutPlayer = new TutPlayerSimple(fullTutorialPath);
                  //context.checkPolicyFile = true;
                  //gutLoader.loaderContext = context;
                  trace("Loading Tut:", fullTutorialPath + ".swf");
                  addChild(tutPlayer);
          ]]>
     </mx:Script>
</mx:Application>

That didn't look right. You'll need to addChild SWFLoader. Not sure what will happen if you just try to add its content. There might also be issues putting Flex components inside a UIMovieCip.
Alex Harui
Flex SDK Developer
Adobe Systems Inc.
Blog: http://blogs.adobe.com/aharui

SceneBuilder 1.1-b18 stubs an items list for ChoiceBox elements

In Scene Builder, I placed a ChoiceBox and gave it an fx:id.
In the "controller" class:
@FXML ChoiceBox<UserGroup> userGroupCB;In the "initialize()" method of the "controller", I set a StringConverter for the choice box so that it would display the "name" property of the domain object:
    @FXML
    protected void initialize() {
        userGroupCB.setConverter(new StringConverter<UserGroup>() {
            @Override
            public String toString(UserGroup userGroup) {
                return userGroup.getName();
            @Override
            public UserGroup fromString(String arg0) {
                return null;
        ....Prior to setting this converter, I had added a toString() method to the UserGroup and everything worked just fine without the converter. However, I really didn't want to default to using the toString() method, so I set the converter.
Boom! Crash! A ClassCastException occurred when setting the converter in the "initialize()" method. Scratch head, pull hair.
By chance, I looked at the FXML in an XML editor and discovered that Scene Builder had stubbed out an <item> list!
    <ChoiceBox ... >
      <items>
        <FXCollections fx:factory="observableArrayList">
          <String fx:value="Item 1" />
          <String fx:value="Item 2" />
          <String fx:value="Item 3" />
        </FXCollections>
      </items>
    </ChoiceBox>So, yeah, of course, unbeknownst to me, it was expecting a String and I was specifying a UserGroup in the converter! (See also the @FXML ChoiceBox<UserGroup> ivar above.) Silly me.
Why is Scene Builder stubbing out this <item> list?! There's no reason for it.
Note that it does the same thing for ComboBox.
I suppose that when I invoke "setItems()" on this choice box [this occurs outside the initialize() method because the values in the choice box are context sensitive, but always UserGroup items], but I shouldn't have to work around what shouldn't be a problem in the first place.
Does anyone else think this is unexpected behind the scenes behavior for Scene Builder?

Eric Le Ponner wrote:
Scene Builder puts some sample item strings in ChoiceBox, ComboBox... to
improve previewing experience.
However it currently does not offer a way to clear/edit items. That's a known limitation.
You can workaround this easily by clearing the "items" property manually in the FXML file.I understand that putting the sample data there was meant for previewing. And once discovered by looking at the XML in a code editor, I removed those items.
However, I would not describe this as a "limitation". It's bad design, especially since, if you do not work with the FXML directly, but only through Scene Builder (and that's what we should be doing), you wouldn't really know that those items are there. Unless the user selects an option called something like "add sample data to FXML file", not sample data should be there.
Improving previewing experience can be done other ways than inserting "sample" XML into the FXML document. The preview runner can do this as it walks the scene graph, inserting sample data where it would prove useful. There is a "Show Sample Data" if you want to see data. Even that should not be putting the sample data into the FXML file.
The sample data just doesn't belong in the FXML, period.
Time to file a bug report.
Edited by: pfurbacher on Mar 14, 2013 2:59 PM

Bug with Java WSDP1.3 Toolkit?

Hi
I used the Java WSDP1.3 toolkit to generate the stubs for the webservice
"http://www.xmethods.net/sd/2001/BabelFishService.wsdl". After creating the stubs , I deployed them in Tomcat 4.1 to test the methods of this service. The output (SOAPException) I am getting when testing this service is
" Error : java.rmi.RemoteException: Runtime exception; nested exception is: unexpected element type: expected={http://www.w3.org/2001/XMLSchema}QName, actual={http://www.w3.org/2001/XMLSchema}string"
Then I used the Axis 1.1 toolkit to generate stubs for the same service and deployed the stubs in tomcat 4.1. The output (SOAPException) I am getting when testing this service is
"Error : Our connection to the Altavista BabelFish site has been cut. This service will remain down indefinitely until an alternate translation engine can be found. We apologize for any inconvenience."
I got the same exception as axis when tested the service with XMLSPY.
Why JAVA WSDP1.3 is not capturing the correcting SOAP Exception?. Is it a bug in the Java WSDP1.3 SOAP toolkit?

Any answers for the query. I face a similar bug with the same versions.

RequestDispatcher.forward() bug in WLS61???

Hi
          attached is a web application called forward that demonstrate a possible
          bug in weblogic 6.1 server.
          Description of the application
          index.html:
          <html>
          <head>
          <title>form</title>
          </head>
          <body>
          <form name="form" method="post" action="forwardServlet">
          <input type="hidden" name="nextPage" size="20"
          value="result.jsp">
          </form>
          <script language="javascript">
          document.forms["form"].submit();
          </script>
          </body>
          </html>
          the index.html of the application just cause the web browser to send a
          request to the ForwardServlet with a parameter nextPage=result.jsp
          ForwardServlet.java:
          import javax.servlet.http.*;
          import javax.servlet.*;
          import java.io.*;
          public class ForwardServlet extends HttpServlet {
          public void service(HttpServletRequest request,
          HttpServletResponse response) throws ServletException,
          IOException {
          RequestDispatcher disp =
          getServletContext().getRequestDispatcher("/" +
          request.getParameter("nextPage") + "?result=kabooom");
          disp.forward(request, response);
          the servlet forwards the request to the nextPage(result.jsp) using
          RequestDispatcher.forward adding to the URI a parameter result=kabooom;
          result.jsp:
          ****<P>
          <%
          String result = request.getParameter("result");
          out.println(result);
          %>
          <P>****
          the jsp just takes the "result" parameter from the request object and
          prints it. However it gets a null instead of the String kaboom
          We use this method of adding parameters in many places in our application
          and it should work according to the API:
          "For a RequestDispatcher obtained via getRequestDispatcher(), the
          ServletRequest object has its path elements and parameters adjusted to match
          the path of the target resource."
          Everything worked fine in WLS5.1
          P.S
          if ForwardServlet.java looks like:
          import javax.servlet.http.*;
          import javax.servlet.*;
          import java.io.*;
          public class ForwardServlet extends HttpServlet {
          public void service(HttpServletRequest request,
          HttpServletResponse response) throws ServletException,
          IOException {
          RequestDispatcher disp =
          getServletContext().getRequestDispatcher("/result.jsp?result=kabooom");
          disp.forward(request, response);
          and not touching the request object itself the result.jsp will display
          kaboom!!!!
          Dror Last
          Senior Software Engineer
          Unisfair Inc.
          12 Yad Haruzim St. Tel Aviv 67778 Israel
          Tel: +972-3-5373738 Ext. 243
          Fax: +972-3-5373731
          GSM: +972-55-723710
          mailto:[email protected]
          http://www.unisfair.com/
          [forward.war]


Yes, SP1 fixes the problem.
          Thanks,
          Beth
          "Ian M. Goldstein" <[email protected]> wrote in message
          news:[email protected]...
          > Service Pack 1 is available now via WebSupport
          > http://websupport.beasys.com/custsupp/
          >
          > Regards,
          > -- Ian
          >
          > "Robert Patrick" <[email protected]> wrote in message
          > news:[email protected]...
          > > Contact BEA technical support...
          > >
          > > Beth wrote:
          > >
          > > > Hi,
          > > >
          > > > We are having this same problem with WL6.1.
          > > > Where do we get this patch? It doesn't appear that SP1 is out yet.
          > > >
          > > > Thanks,
          > > > Beth
          > > >
          > > > "Andrew" <[email protected]> wrote in message
          > > > news:[email protected]...
          > > > >
          > > > > I spoke with BEA about this bug, as we were exhibiting almost the
          > exact
          > > > same behavior.
          > > > > It is definitely a bug, and their engineering department said it is
          > fixed
          > > > with
          > > > > 6.1 SP1 which is due to be released in September. They gave me a
          > patch to
          > > > test,
          > > > > and it did indeed fix this bug.
          > > > >
          > > > > Andrew
          > > > >
          > > > > "Willie" <[email protected]> wrote:
          > > > > >Hi,
          > > > > >
          > > > > >Any update on this one? We are running into the exact same problem
          > and
          > > > > >it is
          > > > > >blocking us from moving into 6.1. The same code worked well in 6.0.
          > Is
          > > > > >this
          > > > > >a WL bug? When is the fix going to be available?
          > > > > >
          > > > > >Thanks!
          > > > > >Willie
          > > > > >
          > > > > >"Dror Last" <[email protected]> wrote in message
          > > > > >news:[email protected]...
          > > > > >> Hi
          > > > > >>
          > > > > >> attached is a web application called forward that demonstrate a
          > > > possible
          > > > > >> bug in weblogic 6.1 server.
          > > > > >>
          > > > > >> Description of the application
          > > > > >> ------------------------------------------
          > > > > >>
          > > > > >> index.html:
          > > > > >>
          > > > > >> <html>
          > > > > >> <head>
          > > > > >> <title>form</title>
          > > > > >> </head>
          > > > > >> <body>
          > > > > >> <form name="form" method="post" action="forwardServlet">
          > > > > >> <input type="hidden" name="nextPage" size="20"
          > > > > >> value="result.jsp">
          > > > > >> </form>
          > > > > >> <script language="javascript">
          > > > > >> document.forms["form"].submit();
          > > > > >> </script>
          > > > > >> </body>
          > > > > >> </html>
          > > > > >>
          > > > > >> the index.html of the application just cause the web browser to
          > send
          > > > > >a
          > > > > >> request to the ForwardServlet with a parameter
          nextPage=result.jsp
          > > > > >>
          > > > > >> ForwardServlet.java:
          > > > > >>
          > > > > >>
          > > > > >> import javax.servlet.http.*;
          > > > > >> import javax.servlet.*;
          > > > > >> import java.io.*;
          > > > > >>
          > > > > >> public class ForwardServlet extends HttpServlet {
          > > > > >>
          > > > > >> public void service(HttpServletRequest request,
          > > > > >> HttpServletResponse response) throws
          ServletException,
          > > > > >> IOException {
          > > > > >> RequestDispatcher disp =
          > > > > >> getServletContext().getRequestDispatcher("/" +
          > > > > >> request.getParameter("nextPage") +
          > "?result=kabooom");
          > > > > >> disp.forward(request, response);
          > > > > >> }
          > > > > >> }
          > > > > >>
          > > > > >> the servlet forwards the request to the nextPage(result.jsp)
          using
          > > > > >> RequestDispatcher.forward adding to the URI a parameter
          > result=kabooom;
          > > > > >>
          > > > > >>
          > > > > >> result.jsp:
          > > > > >>
          > > > > >> ****<P>
          > > > > >> <%
          > > > > >> String result = request.getParameter("result");
          > > > > >> out.println(result);
          > > > > >> %>
          > > > > >> <P>****
          > > > > >>
          > > > > >> the jsp just takes the "result" parameter from the request
          object
          > > > > >and
          > > > > >> prints it. However it gets a null instead of the String kaboom
          > > > > >>
          > > > > >>
          > > > > >> We use this method of adding parameters in many places in our
          > > > application
          > > > > >> and it should work according to the API:
          > > > > >> "For a RequestDispatcher obtained via getRequestDispatcher(),
          the
          > > > > >> ServletRequest object has its path elements and parameters
          adjusted
          > > > > >to
          > > > > >match
          > > > > >> the path of the target resource."
          > > > > >>
          > > > > >> Everything worked fine in WLS5.1
          > > > > >>
          > > > > >>
          > > > > >> P.S
          > > > > >>
          > > > > >> if ForwardServlet.java looks like:
          > > > > >>
          > > > > >> import javax.servlet.http.*;
          > > > > >> import javax.servlet.*;
          > > > > >> import java.io.*;
          > > > > >>
          > > > > >> public class ForwardServlet extends HttpServlet {
          > > > > >>
          > > > > >> public void service(HttpServletRequest request,
          > > > > >> HttpServletResponse response) throws
          ServletException,
          > > > > >> IOException {
          > > > > >> RequestDispatcher disp =
          > > > > >>
          > getServletContext().getRequestDispatcher("/result.jsp?result=kabooom");
          > > > > >> disp.forward(request, response);
          > > > > >> }
          > > > > >> }
          > > > > >>
          > > > > >> and not touching the request object itself the result.jsp will
          > display
          > > > > >> kaboom!!!!
          > > > > >>
          > > > > >>
          > > > > >> Dror Last
          > > > > >> Senior Software Engineer
          > > > > >> Unisfair Inc.
          > > > > >> 12 Yad Haruzim St. Tel Aviv 67778 Israel
          > > > > >> Tel: +972-3-5373738 Ext. 243
          > > > > >> Fax: +972-3-5373731
          > > > > >> GSM: +972-55-723710
          > > > > >> mailto:[email protected]
          > > > > >> http://www.unisfair.com/
          > > > > >>
          > > > > >>
          > > > > >>
          > > > > >>
          > > > > >>
          > > > > >
          > > > > >
          > > > >
          > >
          >
          >

WL 6.1sp1&sp2 BUG: HttpServletRequest.getRequestURL()

          HttpServletRequest.getRequestURL() always returns "http://..." even if the request
          was made with "https://...". The fix is to replace the protocol specification with
          the results from getScheme() like so:
          StringBuffer aURL = request.getRequestURL();
          // broken on WL 6.1 -- need to correct the scheme
          aURL = aURL.replace(0, aURL.toString().indexOf(':'),
          request.getScheme());


Tonna I wrote:
          > Hi there,
          > Which version was this bug resolved in? Is it still outstanding in WL6.1sp4?
          > We?re currently using WL6.1sp2?if it?s resolved in WL6.1SP4 we may consider upgrading
          > instead of putting in a fix.
          >
          > Cheers
          > Tonna
          >
          > Nagesh Susarla <[email protected]> wrote:
          >
          >>thanks for pointing this out!
          >>its indeed a bug
          >>
          >>Steve Ditlinger wrote:
          >>
          >>>HttpServletRequest.getRequestURL() always returns "http://..." even
          >>
          >>if the request
          >>
          >>>was made with "https://...". The fix is to replace the protocol specification
          >>
          >>with
          >>
          >>>the results from getScheme() like so:
          >>>
          >>> StringBuffer aURL = request.getRequestURL();
          >>> // broken on WL 6.1 -- need to correct the scheme
          >>> aURL = aURL.replace(0, aURL.toString().indexOf(':'),
          >>>request.getScheme());
          >
          >
          Yes the fix is a part of 61sp4. If you still have any issues with the
          above mentioned problem, or if you need a patch please contact support
          the associated bug-id : CR076389
          rgds
          Nagesh

Unable to Install WL6.0 on NT4SP5 server

I am attempting to install Weblogic Server 6.0 on an NT 4 SP 5 server. 96MB RAM, 2G free disk space, Pentium II processor. After doubleclicking on the weblogic600_win.exe file, the installer extracts files to c:\temp\ixxxxxxx folder. Then the installer just goes away. Nothing happens. I can install wl6 on every other server I have access to without problems. I've disabled ALL services on the box and disabled virus protection, but I'm running out of ideas. I am an administrator on the server, and I've even tried logging on locally, not on the domain to do the install and it's the same. The extraction completes then the installer just dies. Any ideas??
Thanks,
Brian Ketelsen
Geneva Pharmaceuticals

Michael,
You've got to be kidding?!?! I have to uninstall all versions of the VM?
Even though I think its crazy, I removed 1.2.2, 1.3 and 1.3 RT I still get the
same problem.
Please help
I'm running Win 2000 with the latest service packs installed (pre sp2).
Michael Girdley wrote:
This is a bug that we have found in install anywhere. It basically gives up
if it locates a conflicting JRE already installed on the system. For me, I
disabled my existing JVMs by uninstalling them. That solved the problem.
Thanks,
Michae
Michael Girdley, BEA Systems Inc
Learning WebLogic? Buy the book.
http://www.learnweblogic.com/
"Brian Ketelsen" <[email protected]> wrote in message
news:3a5a0f6e$[email protected]..
I am attempting to install Weblogic Server 6.0 on an NT 4 SP 5 server.96MB RAM, 2G free disk space, Pentium II processor. After doubleclicking on
the weblogic600_win.exe file, the installer extracts files to
c:\temp\ixxxxxxx folder. Then the installer just goes away. Nothing
happens. I can install wl6 on every other server I have access to without
problems. I've disabled ALL services on the box and disabled virus
protection, but I'm running out of ideas. I am an administrator on the
server, and I've even tried logging on locally, not on the domain to do the
install and it's the same. The extraction completes then the installer just
dies. Any ideas??
Thanks,
Brian Ketelsen
Geneva Pharmaceuticals

Webapp client using weblogic-generated stubs

Hi,
I have a simple webservice that has been tested for a while and works without
any trouble when
accessed from a standalone java client using the weblogic-generated webservice
stubs.
I am trying to code a webapp client (using jsp/struts) using the same stubs, and
seem to keep
getting this error. It appears on the client side, doesn't even reach the server
side.
I am using weblogic 8.1 SP1. (It is interesting that even though everything was
compiled and
deployed with weblogic 8.1, there is some reference to 7.0-- which is not even
installed on the
system, so I don't know where it is coming from.)
<May 7, 2004 12:58:23 PM EDT> <Info> <WebService> <BEA-220025> <Handler weblogic.webservice.core.handler.ClientHandler
threw an exception from its handleResponse method. The exception was:
java.lang.IllegalAccessError: Already connected.>
java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Exception
during processing: java.lang.IllegalAccessError: Already connected (see Fault
Detail for stacktrace)
Detail:
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">
</bea_fault:stacktrace>java.lang.IllegalAccessError: Already connected
at weblogic.net.http.HttpURLConnection.setRequestProperty(Ljava.lang.String;Ljava.lang.String;)V(HttpURLConnection.java:570)
at com.hp.ov.ipa.instr.bip.HttpURLConnectionArmInstrumentation.methodEntry(Ljava.lang.Object;Ljava.lang.Object;Ljava.lang.Object;I)Ljava.lang.Object;(HttpURLConnectionArmInstrumentation.java:98)
at weblogic.net.http.HttpURLConnection.getInputStream()Ljava.io.InputStream;(HttpURLConnection.java:???)
at weblogic.net.http.HttpURLConnection.getHeaderField(Ljava.lang.String;)Ljava.lang.String;(HttpURLConnection.java:542)
at java.net.URLConnection.getContentType()Ljava.lang.String;(URLConnection.java:381)
at weblogic.webservice.binding.http11.Http11ClientBinding.receive(Ljavax.xml.rpc.handler.MessageContext;)V(Http11ClientBinding.java:202)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(Ljavax.xml.rpc.handler.MessageContext;)Z(ClientHandler.java:63)
at weblogic.webservice.core.HandlerChainImpl.handleResponse(Ljavax.xml.rpc.handler.MessageContext;)Z(HandlerChainImpl.java:230)
at weblogic.webservice.core.ClientDispatcher.receive(Lweblogic.webservice.WLMessageContext;)Ljava.lang.Object;(ClientDispatcher.java:229)
at weblogic.webservice.core.ClientDispatcher.dispatch([Ljava.lang.Object;)Ljava.lang.Object;(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(Ljava.util.Map;[Ljava.lang.Object;Ljava.io.PrintStream;)Ljava.lang.Object;(DefaultOperation.java:444)
at weblogic.webservice.core.DefaultOperation.invoke(Ljava.util.Map;[Ljava.lang.Object;)Ljava.lang.Object;(DefaultOperation.java:430)
at weblogic.webservice.core.rpc.StubImpl._invoke(Ljava.lang.String;Ljava.util.Map;)Ljava.lang.Object;(StubImpl.java:270)
Thanks in advance,
E

Hi,
Thanks for your help with this. As it turns out, I received this message from
the weblogic team here:
=======
All,
The J2EE monitoring tool OVTA rolled out to Weblogic Farm Linux QA and Stage environment
had a bug in the instrumentation. The bug induces a java.lang.IllegalAccessError.
A patch as been rolled out to fix this issue.
=======
Once the patch was rolled out and weblogic was restarted, the issue disappeared.
Thanks again for your help!
E
Bruce Stephens <[email protected]> wrote:
Hello,
What is
com.hp.ov.ipa.instr.bip.HttpURLConnectionArmInstrumentation.methodEntry
at the time of failure?
If you could provide a short reproducer, we could give it a spin; or
open a dialog with our support team.
Thanks,
Bruce
Elisheva G wrote:
Hi, thanks for responding.
I have precisely the same client jsp running without any errors onapache tomcat
accessing
webservices residing in weblogic 8.1 It's only when I try to migratethe client
code from tomcat
to weblogic that I see this "already connected" exception being thrownfrom within
the weblogic-
generated stubs.
I successfully get a port from the service, but when I try to executethe business
method in the
port, that is where the exception is thrown -- consistently.
Any ideas? I am seeing identical behavior on 2 different applications.
Thanks in advance,
E
Bruce Stephens <[email protected]> wrote:
Hello,
The 7.0 reference is a namespace and not a problem and not associated
with your issue. I think you are seeing normal process threading
issues
with jsp sessions. There is an example using a jsp [1] and one with
SSL
[2] that you might want to examine.
HTH,
Bruce
[1]
http://manojc.com/?sample28
[2]
http://webservice.bea.com/clientauth.zip
Elisheva G wrote:
Hi,
I have a simple webservice that has been tested for a while and
works
without
any trouble when
accessed from a standalone java client using the weblogic-generatedwebservice
stubs.
I am trying to code a webapp client (using jsp/struts) using the
same
stubs, and
seem to keep
getting this error. It appears on the client side, doesn't even
reach
the server
side.
I am using weblogic 8.1 SP1. (It is interesting that even though
everything
was
compiled and
deployed with weblogic 8.1, there is some reference to 7.0-- whichis not even
installed on the
system, so I don't know where it is coming from.)
<May 7, 2004 12:58:23 PM EDT> <Info> <WebService> <BEA-220025> <Handlerweblogic.webservice.core.handler.ClientHandler
threw an exception from its handleResponse method. The exception
was:
java.lang.IllegalAccessError: Already connected.>
java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException:Exception
during processing: java.lang.IllegalAccessError: Already connected(see Fault
Detail for stacktrace)
Detail:
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">
</bea_fault:stacktrace>java.lang.IllegalAccessError: Already connected
at weblogic.net.http.HttpURLConnection.setRequestProperty(Ljava.lang.String;Ljava.lang.String;)V(HttpURLConnection.java:570)
at com.hp.ov.ipa.instr.bip.HttpURLConnectionArmInstrumentation.methodEntry(Ljava.lang.Object;Ljava.lang.Object;Ljava.lang.Object;I)Ljava.lang.Object;(HttpURLConnectionArmInstrumentation.java:98)
at weblogic.net.http.HttpURLConnection.getInputStream()Ljava.io.InputStream;(HttpURLConnection.java:???)
at weblogic.net.http.HttpURLConnection.getHeaderField(Ljava.lang.String;)Ljava.lang.String;(HttpURLConnection.java:542)
at java.net.URLConnection.getContentType()Ljava.lang.String;(URLConnection.java:381)
at weblogic.webservice.binding.http11.Http11ClientBinding.receive(Ljavax.xml.rpc.handler.MessageContext;)V(Http11ClientBinding.java:202)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(Ljavax.xml.rpc.handler.MessageContext;)Z(ClientHandler.java:63)
at weblogic.webservice.core.HandlerChainImpl.handleResponse(Ljavax.xml.rpc.handler.MessageContext;)Z(HandlerChainImpl.java:230)
at weblogic.webservice.core.ClientDispatcher.receive(Lweblogic.webservice.WLMessageContext;)Ljava.lang.Object;(ClientDispatcher.java:229)
at weblogic.webservice.core.ClientDispatcher.dispatch([Ljava.lang.Object;)Ljava.lang.Object;(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(Ljava.util.Map;[Ljava.lang.Object;Ljava.io.PrintStream;)Ljava.lang.Object;(DefaultOperation.java:444)
at weblogic.webservice.core.DefaultOperation.invoke(Ljava.util.Map;[Ljava.lang.Object;)Ljava.lang.Object;(DefaultOperation.java:430)
at weblogic.webservice.core.rpc.StubImpl._invoke(Ljava.lang.String;Ljava.util.Map;)Ljava.lang.Object;(StubImpl.java:270)
Thanks in advance,
E

WL6.1 SocketException

"I am facing this problem of SocketException being thrown on server console a number of times. I have just moved to weblogic 6.1 from 6.0. I have compiled all the classes with references to weblogic.jar and jdk from WL6.1.
The cause of this exception is not known. Though this does not really harm my application, it's not desirable.
Thanks in advance for help.
The trace is as under -
<Sep 25, 2002 3:49:09 PM EDT> <Error> <JavaSocketMuxer> <IOException on socket:
'Socket[addr=localhost/127.0.0.1,port=2506,localport=7001]'
java.net.SocketException: Connection shutdown: JVM_recv in socket input stream r
ead
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:85)
at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:
281)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:2
33)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Sep 25, 2002 3:49:09 PM EDT> <Error> <HTTP> <Connection failure
java.net.SocketException: Connection%2

          Dimitri, you surely mean that the servlet will be reloaded without restarting the
          server, right! Well, it doesn't work!
          Now, if the flag ServletReloadCheckSecs should be set to "0" in the WebAppComponenet
          element is meant to work, then WL6.1 is randomly buggy.
          However, no-none commited to a bug-free society.
          Dimitri Rakitine <[email protected]> wrote:
          >WebLogic doesn't recompile .java classes - it will reload servlet if
          >it's
          >..class file changes.
          >
          >I agree that autocompilation feature in Resin and Orion (Oracle?) is
          >super-convinient. Send it to [email protected] - maybe someday they will
          >implement it.
          >
          >florin <[email protected]> wrote:
          >
          >> WL6.1 documentation claims that "If you set this attribute (the Files
          >tab of your
          >> Web Application) to zero, WebLogic Server checks the time stamp on
          >every request."
          >> Sure. Next time.
          >
          >> My web application is set to be the default web application. Any ideas
          >why it
          >> doesn't work for me?
          >
          >> I deffinatelly miss Orion's ease of use. One might think that more
          >money is better.
          >
          >
          >> Thanks for your help.
          >
          >
          >--
          >Dimitri

WL6.1 Stub bug ?

Similar Messages

Maybe you are looking for