ConnectionClosedException when POSTing images via HTTPS

Greetings,
I am trying to send images to a server from my Verizon BlackBerry 8330 using an HTTPS connection. I am performing the following steps:
HttpsConnection https = (HttpsConnection)Connector.open("https://myserver");
https.setRequestMethod(HttpsConnection.POST);
https.setRequestProperty("Content-Type", "image/jpg");
FileConnection file = (FileConnection)Connector.open("file:///filename", Connector.READ_WRITE);
InputStream is = file.openInputStream();
OutputStream os = https.openOutputStream();
byte[] b = new byte[1024];
for(int i; (i = is.read(b)) != -1;) {
os.write(b, 0, i);
int code = https.getResponseCode();I am receiving a ConnectionClosedException when I call getResponseCode() after the final write() to the OutputStream, but I can't think of anything in my code that is closing the connection.
Does anyone know what could be causing the connection to be closed between the time that I open the connection and finish writing to its OutputStream?
Thank you.

Similar Messages

Problem with loading an image via HTTP

Hallo,
When using the JBCL TransparentImage control i can load images
from my local HD. But when i use setImageURL it won't work. I
looked at the sources and it seems to me that the problem lies
within the default toolkit. The following code works when using
a local file. Via HTTP the Observer get's one notification with
just the error-flag set.
URL url=new URL("http://localhost/mxtj_inetmaps/mp_map1.gif");
// String sFileName="c:\\mapinfo\\inetmap\\mp_map1.gif";
Toolkit tk=Toolkit.getDefaultToolkit();
Image i=tk.getImage(url);
// Image i=tk.getImage(sFileName);
MyObserver mo=new MyObserver();
tk.prepareImage(i, -1, -1, mo);
Could someone help me, how to show a Web-Image within a control ?
Bye Heiko.
null

Hi,
There is no getImage that accepts the parameters in the order in which you have given them. Try this:
getImage( getCodeBase(), "flower.gif" );
Regards,
Manfred.

Disk Utility, restore image via HTTP, and error 22 (invalid argument)

I'm trying to restore a properly-created and prepared (i.e. volume checksum applied) Apple Software Restore disk image to a volume on a target computer. The source image is hosted on a Web server and accessible via HTTP.
The image restoration process appears to succeed for the most part, but at the end, I get an error 22 (invalid argument). This may be after the image restoration has finished, and when the resulting volume is being mounted. (I wonder if the problem is automount-related?)
The same image, so far, restores to the same volume successfully when restored locally, mounting the drive in target disk mode on the host Mac.
I am curious if anyone else has seen this same behavior and found a solution. Or is everyone else having the same kinds of problems with HTTP-based restores?
MacBook Pro Mac OS X (10.4.9) 15-inch, Core 2 Duo 2.16 GHz, 2 GB RAM

Visit http://www.bombich.com/. See if you find any related info on that site. If not email Mike Bombich about the problem. If anyone knows the answer I would think he should.

Update correspondence history (DFKKCOHI) when posting manually via FPE1

Hi experts,
Here is a difficult one. I need to update the correspondance history when posting manually certain types of documents via FPE1. I was told to use business event 723 - Correspondence : Free --> Create (tcode FQEVENTS) that is one of the events for Document. I thought that by creating and activating my customer function module Z_FKK_SAMPLE_0723 it should be enough, placing my own code there. But I can see that when I post a document via FPE1 this event is never triggered, even though now is activated. Am I missing something??
After a lot of debugging I found out that event 1118 is called instead (one of the events called among others).
From include LFKPPFB0
* finally call the posting module
CALL FUNCTION 'FKK_CREATE_DOC'
    EXPORTING
      I_FKKKO          = FKKKO
      I_UPDATE_TASK    = ' '
      I_FKKOPL_CF      = 'X'
      I_DIALOG         = 'X'
    IMPORTING
      E_OPBEL          = XOPBEL
    TABLES
      T_FKKOP          = XFKKOP
      T_FKKOPK         = XFKKOPK
      T_FKKOPW         = XFKKOPW
      T_FKKOPL         = XFKKOPL
      T_FKKOPKC        = XFKKOPKC
      T_FKKOPREL       = XFKKOPREL
      T_FKKOP_ESR      = XFKKOPESR
    EXCEPTIONS
      ERROR_MESSAGE    = 4.
IF SY-SUBRC = 0.
    PERFORM EVENT_1118.
ELSE.
    PERFORM MESSAGE_STORE USING '1119'.
    PERFORM MESSAGES_SHOW.
    PERFORM OKCODE_OVER.
ENDIF.
And that this event (FKK_SAMPLE_1118) is empty so you can write your own code there. But I don't know how risky this is.
Please I need some advice with this issue. My two questions are:
- 1) why event 723 is not triggered when I do I manual post?? What do I have to do to trigger it?
- 2) My plan B is to force the call to event 723 from event 1118, which I for sure know that is triggered. Anybody can see any problem in this?
Anybody has been in a similar situation making a new event in FQEVENTS?
Thanks in advance, points will surely be rewarded.
Elena

Hi Prashant,
Thanks for that. YES! That may be to update text in document. But while uploading invoices I will not have document number details, it will be created when we process batch which been created using rfbibl00. How can I capture document numbers after processing batch session? Because with document number details I will able to use SAVE_TEXT to update remaining text fields. So can you please suggest best way to do this if you can? Many thanks.
Regards,
Tim

"Rend Error" when sending image via iChat/AIM

On my brand new iMac aluminum, I am unable to send, and friends are unable to send, images via iChat AIM 3.1.8 (V445). When either of us try to send, we get the message "An undefined AIM error has occured. The server message was: Rend: Error"
I then spin around and use my old G4 iMac to send an image - no problem. My buddy is also able to send to me, no problem.
Both computers are connected to the same Linksys WRT54G router. When I searched for the term 'rend' only one thread came back which suggested to change the port from 5190 to 443. I did this and it didn't help.
Any other suggestions?

Hi Craig,
In the Linksys set up pages you have Application and Gaming (Which is where I think you are talking about)
In there there are several options.
Port Forwarding, Port Triggering, DMZ (possibly UPnP Forwarding and QoS)
Disable any Port Forwarding or Port Triggering. DO not use the DMZ.
Save settings. (you should still have Web browsing and Mail abilities).
GO to the Administration tab on the top row.
Enable UPnP.
Save Settings.
UPnP allows multiple computers to use the same ports.
This way the Linksys can be left doing DHCP if you wish and it will not matter if your computer gets a new IP every now and then. Also the Ports are opened by the application and close after a timed period of non use.
You can limit the "Hops" to the number of devices the computer is from the Linksys (1 ?) to make it more secure.
On the main set up page you could limit the the DHCP range to the number of computers you have to prevent outside connections.
The ports you describe so far are only the TExt chatting and file sending ports
11:23 AM Monday; August 13, 2007

POA crashes when streaming contacts via HTTP

Hi,
streaming messages and calendar items as RFC 822 works like a charm.
But when streaming contacts of an address book via HTTP the POA crashes?
Is this a known issue or is it possible at all to stream address book items?
My environment:
Groupwise 8.0.0 on Windows 2003 Server (german)
Thank you in advance,
Thilo

There is no support to stream contacts.
I'll create a bug to prevent processing of contacts
in the streaming code (which will prevent the crash).
Preston
>>> On Monday, May 30, 2011 at 1:35 PM, Thilo Brüßhaber<[email protected]>
wrote:
> Hi,
>
> streaming messages and calendar items as RFC 822 works like a charm.
> But when streaming contacts of an address book via HTTP the POA crashes?
> Is this a known issue or is it possible at all to stream address book
items?
>
> My environment:
> Groupwise 8.0.0 on Windows 2003 Server (german)
>
> Thank you in advance,
> Thilo

When sending images via iPhoto it doesn't register as sent mail in A

When sending images from iPhoto it does not register as sent mail in Apple Mail. Is there an option to allow this?

No. But in iPhoto's Info tray for that photo there will be a note that the photo was mailed and to whom:
Click to view full size
OT

Ipad only uses one file name when uploading images via email

We have an image tool that uploads images to a template website. The problem is the file names for these images must be unique any duplicate file names will be rejected. Some of our users want to be able to upload from the field but Ipad only assigns the file name "photo.JPG" to jpegs. It doesn't seem to include the sequential extension that actually does exist for the image on the file name when uploading. Is there a way to get ipad to do so, or is this something that Apple maybe want to consider looking into. I can easily see the average Joe emailing themselves images and hitting save only to replace and lose an older image because let's face it, not all users are on MACs and PC's do not allow multiple files to have the same file name in the same folder.

Hi,
Based on the description, you could send email to external addresses without the Twin Oaks software. However, with the Twin Oaks software, you couldn't send successfully.
For this issue, I recommend you enable message tracking and check whether you could retrieve message tracking log entires when you send emails to external addresses through the Twin Oaks software.
If you couldn't retrieve message these tracking log entires when you send emails to external addresses through the Twin Oaks software, it means that the Exchange server is OK and the crux of the problem is the Twin Oaks software.
Here is an article about message tracking log for your reference.
Get-MessageTrackingLog
http://technet.microsoft.com/en-us/library/aa997573(v=exchg.141).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

XI to post data via HTTPS

Hi !
There is a government web page with an HTML page that has a FORM tag, with this attributes (action data is not real)
action ="https://www.website.com/forms.do"
enctype="multipart/form-data"
method="post"
name="form"
inside, it has some INPUT tags:
<INPUT name="user"></INPUT>
<INPUT name="password"></INPUT>
<INPUT type="file" name="file"></INPUT>
<INPUT name="submit" type="submit" value="Send"></INPUT>
I need XI to post the input data that it receives via RFC.
Should I use the HTTP Adapter? SOAP Adapter?
How can I simulate the form submission via XI ?
How do I do to send the file data? (it is received by XI from an RFC as a long text line)
Thanks,
Matias.

Maybe you can with HTTP receiver adapter and some tricks...
But you may also follow this way: an JAVA proxy that receive the message and make all the HTTP dialog:
Explained here:
/people/amol.joshi2/blog/2006/06/28/must-fire-a-http-get-from-xi---try-this
Regards,
Sandro

Posting XML via HTTP post returns "Envelope missing in SOAP message header"

Hi,
I am trying to post a simple XML message directly to the integration server using an html document, where the form that contains the XML message is a simple
<b><FORM action="http://servername:8000/sap/xi/engine?type=entry" method="post"></b>
So, I add my xml message like this:
<?xml version="1.0" encoding="UTF-8">
<ns:PlantMaintenanceMessageType xmlns:ns="http://sap.com/demo/plantmaintenance">
      <EquipmentID>SLIEQUIP5</EquipmentID>
      <FunctionalLocation>KB</FunctionalLocation>
      <Date/>
      <Time/>
</ns:PlantMaintenanceMessageType>
but I get a message back from the Integration Server as:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>
<SAP:P1>Envelope</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<b><SAP:Stack>XML tag Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack></b>
</SAP:Error>
Seems like I am missing the Envelope so my Integration Server can understand my post. What does the Envelope look like or should conatain so that the Integration Server accepts my XML file ?
Thanks !

This is the trace
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external =</Trace>
<Trace level="1" type="T">Sender agency external =</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = sapqxh:8020</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.228.137.106</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="3" type="T">system-ID = QXH</Trace>
<Trace level="3" type="T">client = 220</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:04Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 4880474945AE67E2E10000000AE4896A</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 4880474945AE67E2E10000000AE4896A</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTL0000</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTL0000</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 4880474945AE67E2E10000000AE4896A</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK.</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MIOA_US139_EmployeeData*</Trace>
<Trace level="1" type="T">select interface namespace urn:abbott-com:US139</Trace>
<Trace level="1" type="T">found interface MIOA_US139_EmployeeData</Trace>
<Trace level="1" type="T">found action ARCH</Trace>
<Trace level="1" type="T">set interface action to ARCH</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = QXH</Trace>
<Trace level="3" type="T">client = 220</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - BS_AIMS</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:08Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2008-07-18T14:19:11Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) BS_AIMS MIIA_US139_EmployeeData</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MIIA_US139_EmployeeData</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:11Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="Timestamp">2008-07-18T14:19:14Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTM0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = QXH</Trace>
<Trace level="3" type="T">client = 220</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2008-07-18T14:19:20Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping already defined in interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 3CCA7AE76D3F33F19F8D7A8DAD494E65</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping C387A5F00F8B11DCAB84C751AAE12E82</Trace>
<Trace level="1" type="T">Interface Mapping urn:abbott-com:US139 IM_US139_EmployeeData</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_US139_EmployeeData_</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_US139_EmployeeData_.</Trace>
<Trace level="3" type="T">Load c387a5f0-0f8b-11dc-ab84-c751aae12e82, urn:abbott-com:US139, -1, com/sap/xi/tf/_MM_US139_EmployeeData_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_MM_US139_EmployeeData_.class (urn:abbott-com:US139, -1) in swcv c387a5f0-0f8b-11dc-ab84-c751aae12e82.</Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_US139_EmployeeData_ completed. (executeStep() of com.sap.xi.tf._MM_US139_EmployeeData_</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:22:07Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2008-07-18T14:22:12Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-QEHCLNT230</Trace>
<Trace level="2" type="T">-BS_AIMS</Trace>
<Trace level="2" type="T">urn:abbott-com:US139.MIIA_US139_EmployeeData</Trace>
<Trace level="2" type="T">Channel found: - BS_AIMS - CC_BS_AIMS_File_Out_09</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-07-18T14:22:12Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- 
<Trace level="1" type="Timestamp">2008-07-18T14:22:18Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Unknown channel type: File</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: File</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">old values in cache (no lock found) - start reading from SLD</Trace>
<Trace level="1" type="T">error reading SAP_XIAdapterFramework from SLD</Trace>
<Trace level="2" type="T">Adapter Framework(s) found</Trace>
<Trace level="2" type="T">Service Port(s) found - take first one</Trace>
<Trace level="2" type="T">URL found</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
<Trace level="3" type="T">URL = http://sapqxh:52000/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = PIISUSER</Trace>
<Trace level="3" type="T">Cached =</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="1" type="T">Empty response received!</Trace>
<Trace level="3" type="System_Error">HTTP-client: error response=</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 007</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 008</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>

'Sending failure' message when sening image via bluetooth from phone

Hia,
I'm getting a 'sending failure' message when sending an image from my phone to my new imac.
I have no trouble sending content from this phone to my old powerbook and have no trouble sending content from my new imac to my phone.
Cheers,
David

If you have a new iMac then you posted in the wrong forum. This area is for G5 iMac issues. Apple has not made any G5 iMacs since 2005.
Suggest that you re-post over in the Internet, Networking and your *Intel-based* iMac Forums

Oddities when serving images via NES from a servlet that is part of a WAR

Just wanted to confirm that the following behavior is normal:
          Environment:
          NT 4.0 SP5
          NES 3.6 SP3
          WLS 5.1 SP3
          jdk 1.2.2
          Goal: When constructing a page that has images embedded in it from my
          servlet, I would like NES to serve the images.
          I've found out that I've to refer to my images with an absolute URL that
          maps to the images directory under Netscape's document root. If I refer to
          my image with a relative URL (request.getContextPath() +
          "/images/cookie.jpg"), then WebLogic tries to retrieve the image from the
          WAR. What is interesting is if I use relative references to images within my
          servlet (minus the WAR, i.e. with the servlet registered in
          weblogic.properties), I see that the image is being served by Netscape.
          Why does the WAR require absolute references to images and the previous
          mechanism does not? Is this behavior consistent with the spec? How are you
          guys handling this (are you using absolute references to static content when
          using WAR?)?
          I'm really baffled by this and wanted to see how others view this. Any
          comments/feedback will be much appreciated.
          Thanks,
          Sanjiv


Hi Cameron,
          You are right but see my "Goal" below. I want to serve my images from my web
          server and NOT by WebLogic. Anyway, I spent too much time on this and found
          out that I was getting inconsistent results during testing different
          approaches because I was not restarting my web server. Once I became
          consistent in restarting my web server and closing all browser windows
          before each test, I got consistent results. So, here's what works for me:
          If I want to have my JSPs/servlets running in WLS to serve images that are
          included in their output from my web server, then I've to use absolute URLs.
          An example would be:
          img src="/images/a.gif"
          On the other hand if I use relative paths like img src="images/a.gif", then
          the browser request for the image is sent to WebLogic, which then looks for
          the image in the WAR (as it should).
          All of this might be common knowledge to most folks but not me.
          Thanks,
          Sanjiv
          Cameron Purdy <[email protected]> wrote in message
          news:[email protected]...
          > The WAR does not require absolute paths. Your JSP must be served from a
          URL
          > that, when combined with a relative path, actually specifies an image in
          the
          > WAR.
          >
          > Cameron Purdy, LiveWater
          >
          > "Sanjiv Gulati" <[email protected]> wrote in message
          > news:[email protected]...
          > > Just wanted to confirm that the following behavior is normal:
          > >
          > > Environment:
          > > NT 4.0 SP5
          > > NES 3.6 SP3
          > > WLS 5.1 SP3
          > > jdk 1.2.2
          > >
          > > Goal: When constructing a page that has images embedded in it from my
          > > servlet, I would like NES to serve the images.
          > >
          > > I've found out that I've to refer to my images with an absolute URL that
          > > maps to the images directory under Netscape's document root. If I refer
          to
          > > my image with a relative URL (request.getContextPath() +
          > > "/images/cookie.jpg"), then WebLogic tries to retrieve the image from
          the
          > > WAR. What is interesting is if I use relative references to images
          within
          > my
          > > servlet (minus the WAR, i.e. with the servlet registered in
          > > weblogic.properties), I see that the image is being served by Netscape.
          > >
          > > Why does the WAR require absolute references to images and the previous
          > > mechanism does not? Is this behavior consistent with the spec? How are
          you
          > > guys handling this (are you using absolute references to static content
          > when
          > > using WAR?)?
          > >
          > > I'm really baffled by this and wanted to see how others view this. Any
          > > comments/feedback will be much appreciated.
          > >
          > > Thanks,
          > > Sanjiv
          > >
          > >
          >
          >

Getting data into a JSF application by posting it via http

(My apologies if there is a thread for this topic - I am not sure what to search for to find if one already exists)
I have 2 applications - the first is a JSF application into which the user logs in, and accesses various tools. The second is a swing app into which the user logs in and accesses various other tools. The logins are universal - one user, one login, two applications. I am providing a link in the swing app to launch the jsf app. I would like the swing app to pass the user identification when launching the JSF session/browser so the user isn't required to type the info again.
(I am guessing I can use a JSP call to bridge the two - something that pulls off the id, and plugs it into the session bean? Just not sure how to do that or if there is a better way)
Many thanks in advance for any assistance!!!

Hi,
thank you for your answers:-)
In conclusion the result is:
1) There is no "direct" way to read POST-Parameter in WebDynPro ABAP
=> You have to write a wrapper in BSP or an ICF - HTTP_REQUEST_HANDLER
(A ABAP-Class that implements the Interface "IF_HTTP_EXTENSION"
that reads the POST-Parameter-Value and transfers the value into a reachable localtion for WebDynPro-Abap.
2) For parsing the XML-Data I can use for example STRANS tcode or Simple Transformations
3) For transfering the Data between the BSP / the Request-Handler and WebDynPro for ABAP, I can use for example SharedMemory, Shared Objects.
Regards
Steffen
Edited by: Steffen Spahr on Jul 19, 2011 8:35 AM
Edited by: Steffen Spahr on Jul 19, 2011 8:55 AM

ClassCastException when RMI callback via HTTP tunneling

Hello,
I have a typical stock quote type of weblogic RMI application running WLS
6.0. If I use T3 for client to register its stub on the server side, the
server callback works fine. I use standard jndi lookup to find the server,
if I simply switch the provider_url form:
env.put(Context.PROVIDER_URL, "t3://192.168.1.5:7001");
to
env.put(Context.PROVIDER_URL, "http://192.168.1.5:7001");
the client can still connect to server and register itself, but server
callback fails:
this client method: qClient.setFreshData(vList) generates the following
error:
java.lang.ClassCastException: ocsmon.wServerThread
at weblogic.servlet.logging.CLFLogger.log(CLFLogger.java:65)
at
weblogic.servlet.logging.LogManagerHttp.log(LogManagerHttp.java:293)
at weblogic.servlet.internal.HttpServer.log(HttpServer.java:670)
at
weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:
851)
at
weblogic.rjvm.http.HTTPServerJVMConnection.sendMsg(HTTPServerJVMConnection.j
ava:361)
at
weblogic.rjvm.MsgAbbrevJVMConnection.sendOutMsg(MsgAbbrevJVMConnection.java:
367)
at
weblogic.rjvm.MsgAbbrevJVMConnection.sendMsg(MsgAbbrevJVMConnection.java:173
at
weblogic.rjvm.ConnectionManager.sendMsg(ConnectionManager.java:482)
at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:419)
at
weblogic.rjvm.MsgAbbrevOutputStream.flushAndSendRaw(MsgAbbrevOutputStream.ja
va:114)
at
weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:
122)
at
weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:144)
at
weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRe
quest.java
:84)
at
ocsmon.QuoteClientInterface_WLStub.setFreshData(QuoteClientInterface_WLStub.
java:218)
at ocsmon.wServerThread.run(wQuoteServer.java:350)
ocsmon.wServerThread is the thread spawned on the server side that obtains
the qClient stub from the server's registry and calls the refreshQuotes
method on it. 'vList' is a Vector of Strings containing the quotes.
What went wrong?
thanks
-Alan

Hello,
I have a typical stock quote type of weblogic RMI application running WLS
6.0. If I use T3 for client to register its stub on the server side, the
server callback works fine. I use standard jndi lookup to find the server,
if I simply switch the provider_url form:
env.put(Context.PROVIDER_URL, "t3://192.168.1.5:7001");
to
env.put(Context.PROVIDER_URL, "http://192.168.1.5:7001");
the client can still connect to server and register itself, but server
callback fails:
this client method: qClient.setFreshData(vList) generates the following
error:
java.lang.ClassCastException: ocsmon.wServerThread
at weblogic.servlet.logging.CLFLogger.log(CLFLogger.java:65)
at
weblogic.servlet.logging.LogManagerHttp.log(LogManagerHttp.java:293)
at weblogic.servlet.internal.HttpServer.log(HttpServer.java:670)
at
weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:
851)
at
weblogic.rjvm.http.HTTPServerJVMConnection.sendMsg(HTTPServerJVMConnection.j
ava:361)
at
weblogic.rjvm.MsgAbbrevJVMConnection.sendOutMsg(MsgAbbrevJVMConnection.java:
367)
at
weblogic.rjvm.MsgAbbrevJVMConnection.sendMsg(MsgAbbrevJVMConnection.java:173
at
weblogic.rjvm.ConnectionManager.sendMsg(ConnectionManager.java:482)
at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:419)
at
weblogic.rjvm.MsgAbbrevOutputStream.flushAndSendRaw(MsgAbbrevOutputStream.ja
va:114)
at
weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:
122)
at
weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:144)
at
weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRe
quest.java
:84)
at
ocsmon.QuoteClientInterface_WLStub.setFreshData(QuoteClientInterface_WLStub.
java:218)
at ocsmon.wServerThread.run(wQuoteServer.java:350)
ocsmon.wServerThread is the thread spawned on the server side that obtains
the qClient stub from the server's registry and calls the refreshQuotes
method on it. 'vList' is a Vector of Strings containing the quotes.
What went wrong?
thanks
-Alan

Error when posting to WebService on XI system using Soap

Hi,
We have a scenario where we have a 3rd party system posting to the XI webservice. The sender Soap adapter is configured for HTTPS without client authentication.
I am using soapui software to test the connection. Before changes were made to the configuration for SSL, we were able to post to XI using the http url. After the changes were made, when posting using the http url no response is received and no message is produced in XI. Also, when we change the url to https and using the port 50001 to post the SOAP message we get the following error:
The following error occurred while parsing the HTTP request: com.sap.engine.services.httpserver.exceptions.ParseException: Incorrect request line: [CONNECT eagnmnsu39e:50001 HTTP/1.1]..
Can anyone provide some insight to the issue?
We are using a user ID with the correct security profile
Thanks.

http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/index.jsp?topic=/com.ibm.etools.mft.doc/ac04595_.htm
Hope this link will help you.
BR,
Alok

ConnectionClosedException when POSTing images via HTTPS

Similar Messages

Maybe you are looking for