FlashPlayer send incorrect timestamps to FMS

When I publish live audio/video via NetStream in some cases flash player starts to send incorrect timestamps.
How to reproduce:
1 Start live audio/video stream. Wait for 10 seconds (video/audio timestamps - goes from 0 to 10)
2 Detach camera from NetStream (turn off video) and continue to publish audio for 60 seconds (video timestamps 10, audio timestamps - from 10 to 70)
3 Turn off audio (mute or just be quiet) for 10 seconds (timestamps don't change)
4 Turn on video (attach camera to NetStream again) for 10 seconds (video timestamps go crazy and jump to 140)
5 Turn on audio - HERE video will be frozen because audio timestamps overtakes video timestamps from 90 to 140. Before audio timestamps reach 140 - video timestamps will be 0 and video is frozen.

If you want to report a Flash Player bug: https://bugbase.adobe.com/
This is a user forum, and there is no guarantee that anybody from the developer team will ever see your post.

Similar Messages

How to Send WSU:TimeStamp dynamically in BPEL 11g

I have requirement to send <wsu:Timestamp> dynamically like creation and expiration must be having 5 min difference.
<wsu:Timestamp>
<wsu:Created>*2012-06-08T09:18:14Z*</wsu:Created>
<wsu:Expires>*2012-06-08T09:23:14Z*</wsu:Expires>
</wsu:Timestamp>
how to send 5 minutes difference in WSS policies.

Hi,
I have created a task flow which will contain all merchant details, and i try to drag this task flow as html form with post request, then i am getting error like nested forms in that page. can any one help how can achive this.
my requirement is: when user click on submit button then i need to invoke http post request which needs to embedded username and pwd with my form data. it's very urgent pls respond if any one knows.

Incorrect Timestamp dateTime format: expected YYYY-MM-DDTHH:MM:SS.NNNNNNNNN

When i insert the data XML data using BPEL Process getting the following exception for date-format
detail>oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : Exception Description: Incorrect Timestamp dateTime format: [2010-01-01] (expected [YYYY-MM-DDTHH:MM:SS.NNNNNNNNN])</detail>
</part>
I have used the following date format and tried all the cases same above error.
xp20:format-dateTime(../../DocumentHeader/EffectiveDate,'[Y0001]-[M01]-[D01] [h]:[m01]:[s01]')
xp20:format-dateTime(../../DocumentHeader/EffectiveDate,'[Y0001]-[M01]-[D01]')
Any idea how to convert Date to date format given error?

Hi,
I'm guessing the problem is not with the format, but with the input date...
What content is coming in your EffectiveDate tag?
It should be something like this...
<EffectiveDate>2012-08-06T12:11:01Z</EffectiveDate>
If the date format is not in ISO 8601, the XPath function won't work...
Cheers,
Vlad

Flash 11 sending incorrect accept-language header in IE9

I am building a website and while web requests from the browser and from javascript report the correct accept-language header (as set inside the IE9 properties, as well as set in system settings on Windows), Flash continues to send English. This seems to be a bug in Flash as I can see no other way to force it to send the same value as the browser.
Can someone confirm this? Also, our Flash developer says that when he looks inside the capabilities object for the current language, it seems that he's also getting the incorrect one. From my research, it sounds like IE sends scripts and plugins only the System Localization language (ie Language in which Windows was shipped), and not the system setting language.
However, since Flash seems to be using the browser http stack for its web calls, I don't see why this behavior should be broken on IE when it works fine for Firefox, Chrome and Opera.

I don't think this is new behavior. When searching on Google, I found a similar post from years ago about this same issue. To reproduce it, get on any internet explorer, set your language to something other than English (or whatever your default happens to be currently).
Go to a website like speedtest.com and press f12 for the developer tools. go to the network tab and enable network monitoring. refresh the page. you will see that all of the page requests send accept-language correctly as your new language.
Next, run the speedtest. you will see a bunch more requests pop up in the network monitor. check the headers. it will send accept-language as en-US, regardless of your settings.
https://bugbase.adobe.com/index.cfm?event=bug&id=3154517

Recording RTMFP P2P stream by sending simultaneous stream to FMS (and other things...)

Only just getting started on this whole domain of learning, so go easy!
If I set up a P2P video/audio chat (similar to the sample VideoPhone thing on the Cirrus site), can I get the stream from both parties to send to a server at the same time so that I can record it? If so, would I have to use a FMS to stream it to and perform the recording (and if so which version could I get away with)? Are there any (preferably free, or just tutorialised) solutions for the recording side of things?
Currently it seems like the only option for doing the P2P thing is to use Stratus/Cirrus unless I use FMS4 Enterprise. Is that correct?
Is there any example code out there that can help? Has anyone got any experience of how effective this kind of situation can be, in terms of quality of the stream and recording? Does any of this make sense?
The Enterprise version of FMS is "Call for price": can anyone give me ball-park figures?
Would appreciate any advice or pointers on these very general questions.

can I get the stream from both parties to send to a server at the same time so that I can record it?
     I really do not know how one can do that - it would be like creating separate stream to server and replicating same data which you send to peer and i do not know how useful it would be - again it will increase the load on server which we are trying to avoid using P2P
If so, would I have to use a FMS to stream it to and perform the recording (and if so which version could I get away with)?
     I think above answer takes care of this. I am not expert on P2P - so someone can correct me if i am completely off
Are there any (preferably free, or just tutorialised) solutions for the recording side of things?
     Not something i am aware off.
Currently it seems like the only option for doing the P2P thing is to use Stratus/Cirrus unless I use FMS4 Enterprise. Is that correct?
     Yes - as of now only FMS4 Enterprise edition supports P2P

Win 7 pro sends incorrect username when attempting to connect to another machine on lan

Under 'Network -- when typing name such as \\computer0:
Cannot successfully login/join/access xp pro machine on lan under win 7 PRO sp1 (\\computer1) but CAN do so under win 7 home premium sp1 (\\computer2).
Looked at credential manager (on both computer1&2) and entries for \\computer0 are almost identical. Successful machine shows username: \\COMPUTER2-MACHINE\myusername and unsuccessful PRO machines shows username: myusername. Passwords are correct and
the same.
When I created a new entry on \\computer1 as 10.0.0.11 for \\computer0 and added the same username and password, it DOES logon/connect/access computer0.
I am certain the username is being passed incorrectly as the currently logged on user on computer0 rather than the user name defined in credential manager. I have run Wireshark on computer0 during the failing computer1 attempt to access \\computer0
AND during the successful access by \\computer2 to access \\computer0 AND when \\computer1 successfully accesses computer0 via using \\10.0.0.11 The username in the security blob | ntlm secure service provider ... is clearly shown to NOT be what is defined
in credential manager.
Any thoughts? suggestions?
tia,
Steve

Hello Andy,
Thanks for your suggestion. I tried it. No luck. Same situation. CAN logon to \\10... but not to \\computer0
I deleted the entries. Rebooted. Tried access to \\computer0. Failed. Created credential. Tried. Failed. Tried \\10... Failed. Created credential for 10... Tried. Succeeded.
Can you tell me how I can completely delete the credentials? (It's a recently purchased used laptop and not much of mine installed on it yet.)
Are there any 'reserved word' credentials that might conflict with my 'computer0'? It's real name is \\ma785gm after it's motherboard.
Thanks,
Steve

PI 7.1 URL for SOAP Sender incorrect

Hello experts,
I have a SOAP sender agreement and generated the WSDL from the "Display WSDL..." option on ID, now the problem is that the soap address tags for HTTP_Port and HTTPS_Port are being created with the hostname of my PI server without domain, but all other url's in the wsdl file and including the WSDL URL of the wsdl file have the correct server name and domain, so when somebody gets the wsdl file from the file location and upload it to even Eclipse or just consume it from any other composite cannot reach the service exposed in PI, so I was wondering if any of you experts can help me with where can I find the parameters that Integration Directory use to create the soap address urls fro HTTP and HTTPS automatically, I've checked all the exchange profile and all the reference to server have the domain, I'm not a basis consultant and our basis team cannot find the problem, if anyone can help me with where can I find these parameters would be really appreciated, thanks in advance for your answers.
Rergards,
Julio

HI JULIO,
SOAP sender agreement and generated the WSDL from the "Display WSDL..." option on ID
Q. HOW TO CHECK THE JTTP SENDER SIDE URL........WE HAVE ONE OPTION IN ID.....CHECK THE BELOW PROCESS FOR REF.....
ID-->TOOLS>DEFINE WEB DERVER->CONTINUE->PROPOS URL (CLICK)>CONTUNUE-->SELECT THE INTERFACE
NAME (NAME NAME SPACE SOFTWARE COMPONENT NAME)---->CONTINUE --->(THEN SERVICE , INTERFACE
NAME ,INTERFACE NAME SPACE)-->CONTINUE->OVERVIEW
THIS IS THE PROCESS TO GET THE SENDER SIDER URL
REGARDS,
KESAVA

Incorrect TimeStamp in Generic Delta (UTC Issue)

Hi,
I have a problem regarding a generic delta extractor. The pointer stored in rsa7 (ROOSGENDLM table) is not UTC but system time. As standard tables store the timestamp using UTC format the delta extractor is not picking up the correct data.
Do you know a solution for this?

Hi,
Thanks for your reply. However I think that unfortunately this solution is not enough
For example:
I execute a delta. My TimeStamp is registered as UTC +2: 20080612160000. (Here I have the error, it should be in UTC)
Now I modify a record in R3 and it is registered with timestamp UTC: 20080612140000.
If I execute a delta it will take all the records higher than 20080612160000. Therefore my modification will never be uploaded.

Incorrect timestamp to string conversions?

Why does this code give different times when the UTC format? input changes? The FieldPoint controller
timezone is set to UTC and compensate for DST is disabled. I would expect the two conversions to give the
same result in this case but they don't. RT 8.5.1. The timestamps of readings in MAX are correct and the
string formatted with UTC format? True is correct.
Thanks.
Matt
Attachments:
utc_time.vi ‏8 KB

We're still seeing this in LabVIEW 2012.
But it only appears to affect dates in BST, as soon as you get back into GMT this '-1' day error goes away
Attachments:
test - BST - UTC format bug.vi ‏16 KB

Incorrect timestamp on logs exported to Excel

Exporting logged data to Excel loses the original timestamp. The time in the Excel file is the system time at which the Excel file was created. The entry in the spreadsheet for time X0 is just 0. The original log file (within SignalExpress) has the correct starting time for the data but that time doesn't seem to get passed to Excel. I have the timestam option set to 'Absolute'
Thanks,
Dave Detty

Hi Dave,
I've been able to track down the issue, and I filed a bug report to have it fixed.
It also looks like the date and time should be that of the timestamp of the first signal, and the X0 is designed to be the offset of each signal in the file from the Date and Time; which is really only useful when there are multiple signals in 1 file.
I wasn't able to find a workaround for this. I'm very sorry...
Phil

Voicemail Displays incorrect timestamp

Normally, my online number's voicemail works fine...but occasionally it displays the wrong timestamp. This is a serious problem for us, as some of our customers leave messages that say that they need a delivery "tomorrow."*
Is there a fix or workaround?
-Jeff
*e.g. Order for Friday Delivery left on Thursday is listed with a timestamp that says it was left on Friday, so we think it's an order for Saturday. End result, very unhappy customers and a very unhappy me (at least -$15,000/year per lost client).

hearthstonebaki wrote:
Normally, my online number's voicemail works fine...but occasionally it displays the wrong timestamp. This is a serious problem for us, as some of our customers leave messages that say that they need a delivery "tomorrow."*
Is there a fix or workaround?
-Jeff
*e.g. Order for Friday Delivery left on Thursday is listed with a timestamp that says it was left on Friday, so we think it's an order for Saturday. End result, very unhappy customers and a very unhappy me (at least -$15,000/year per lost client).
Sounds like you should go through http://support.skype.com/ and file a request there. If you have a subscription, you may be able to do more than file a request - you may have the option to have a real-time keyboard chat with someone.
BTW if you are truly losing that much money per client your business loses and you can't get Skype's voicemail to work like you want, it would be highly advisable to find some other mechanism for voicemail. Maybe even a mobile phone just for this purpose. Depending on how you obtain that voicemail, you could set up your Skype account to forward unanswered calls to that voicemail. If you have a subscription that covers calling to the number for that voicemail, you would not be billed by Skype for the forwarded calls. It would certainly be cheaper than losing a fraction of that $15000/year for just one lost client.
I don't know where you are, so I can't offer specifics on pricing for that. I'm in the US. Along with my Skype account, I forward unanswered Skype calls to a mobile number here in the States. The costs for calling the US mobile number are covered by my US$ 7.99/month Unlimited North America subscription (I also call Mexico), but the US$ 2.99/month Unlimited USA & Canada subscription would be more than enough to cover the costs of forwarded calls. And if I'm not logged into Skype, I can simply answer the incoming Skype calls - including those from my online numbers - on the mobile. I have an "unlimited talk/text/data" plan on my mobile phone, so there are no additional charges from the mobile carrier to receive those forwarded Skype calls.
Good luck!
Patrick
Location/Ubicacion: Arizona USA
Time Zone/Hora Local: UTC/GMT -7
If this message has adequately addressed your issue, please click on the “Accept as Solution” button. If you found a post useful then please "Give Kudos" at the bottom of my post, so that this information can benefit others.
Si esto mensaje le ha ayudado, por favor haga clic en "Aceptar como solución". Si encuentra un mensaje útil, por favor "Da Kudos" al final del mensaje, por lo que esta información puede beneficiar a otros.
I am not a Skype employee. No soy un empleado de Skype.

SMB Incorrect Timestamp (1 hour shift)

I receive difficulties when i mount my desktops homedir(running 10.4.8/PPC) by windows sharing(smb)
The Modificationtime is off by an hour.
Finder on Desktop:
Matlabskriptum.pdf 18:52
Finder on Remote Machine mounting the share: Matlabskriptum.pdf 19:52
Windows Explorer:
Matlabskriptum.pdf 19:52
Linux shell:
Matlabskriptum.pdf 19:52
/etc/localtime links to /usr/share/zoneinfo/Europe/Vienna
the TZ variable is empty

Not sure what you are trying to do. If you are using some shell tool like rsync you should be aware that Windows file modtimes are not compatible with any *nix system. rsync has a --size option which sort of overcomes this incompatibility.

FMS 3.5 says 'Bad network data': error in handling RTMP extended timestamps / chunkSize?

Hello all,
For a client, I am working on a project where a live RTMP stream is published to an Adobe FMS 3.5.6 server from a java application, using Red5 0.9.1 RTMPClient code.
This works fine, until the timestamp becomes higher than 0xFFFFFF after 4.6 hours, and the RTMP extended timestamp field starts being used. I have already found: when the extended timestamp was written after the header, the last 4 bytes of the data were being cut off. I have fixed this locally, and now the data being sent seems to me to be conformant to the spec. However, FMS still throws an error message in the core log and then kills the connection from the Red5 client. Here is the error message:
This is the error message:
2011-06-03 14:28:02 13060 (e)2611029 Bad network data; terminating connection : chunkstream error:message length 11893407 is longerthan max rtmp packet length -
2011-06-03 14:28:02 13060 (e)2631029 Bad network data; terminating connection : (Adaptor: _defaultRoot_, VHost: _defaultVHost_, IP: 127.0.0.1, App: live/_definst_, Protocol: rtmp, Client: 5290168480216205379, Handle: 2147942405) : 05 FF FF FF 00 13 = 09 01 00 00 00 01 00 01 01 ' 01 00 00 00 00 00 13 4 09 0 00 00 01 ! 9A & L 0F FA F6 12 , B4 A6 CE H 8A AB DC G BB d k 1B 9F ) 13 13 D2 9A E5 t 8 B8 8D 94 ! 8A AE F6 AF } " U 0 D3 Q EF FF ~ 8D 97 D9 FF BE A3 F3 C9 97 o 9D # F9 7F h A4 F7 } / FB & F1 DC 9C BF BD D3 E7 CA 97 FE E2 B9 E4 F7 9E 1A F6 BA } C9 w FC _ / / w FE n EF D7 P 9C F4 BE 82 8E F7 | BE 97 B4 BB D7 FE ED I / FB D1 93 9A F9 X \ 85 BD DD I E3 4 E8 M 13 D3 " ) BE A9 92 E5 83 D4 B4 12 DE D5 A3 E6 F4 k DE BF Q 3 A0 g r A4 f D9 BD w * } F7 r 8A S 2 . AB BD EE ^ l f AF E1 0B $ AF 9D D7 - BF E8 ! D3 } D3 i E3 B8 F2 M A8 " B1 A5 EF s ] A5 BC 96 E5 u e X q D2 F1 r F9 i 92 b EE Z d F9 * A6 BB FD 17 w 4 DD 3 o u EB ] ] EF FE B5 B1 0A F2 A0 DD FD B2 98 DF E8 e F6 CB FD 96 V % A5 D5 k ] FD w EF AF k v AA E8 ! 9F / w BE FA 9A _ E F2 D3 , ? 17 } AD 7 EC B3 } 07 B5 | z { { A5 = 11 90 CF BF ; 4 FE EF 95 F7 E7 DF B9 , AF z 91 CF C9 BD DE CB { F5 17 } F2 E5 D7 DF z E6 [ 96 > Y m 9F EB AF DD D8 E8 v B9 A8 E9 % A7 | 1 CF 8B D Z k N DF F8 N FA S R FE . ~ CB A 9 E1 ) 8F 8E BB EC c 6 13 F1 AC FD FD FC 8A F7 F3 K B9 FA ^ / A4 FC B9 AA F6 DE C2 [ 1A E c r B3 BF E5 EC B5 x 94 FD . A9 t I Q % EA EC DE | K FE z A4 97 F9 " 1 0F CA FB F5 F5 p 9E 99 3 - ; B8 F4 F1 FF t A3 EC BC # DE AC 91 13 19 o < 06 F5 FD 7F 7 _ $ D B t B5 0D 8A C1 C1 BA 0B FE DB B7 83 _ } BD z F7 CB { FC M A9 8D = D5 B1 < 85 = EF E1 ; BA H y FC BC B4 C A2 D9 ` e E4 94 H 5 13 ' 93 93 8E E C2 1C R 97 9 X B7 FF 10 9F { ) F1 CF AB AC ] EE H A2 DE D3 C5 m F6 K A2 A7 A2 89 D2 z EB DF 97 ^ k 9E 99 BB E7 B6 97 w { ~ + C7 B2 } FE ' C4 | B6 o H DD r A8 9F DC FF F9 Q b l 93 T B6 EE FF 11 j CD s P C F1 3 R I F8 D8 R 9D 93 AA D5 + DE FC BE " B9 E1 ` CB BD 0F F5 C7 AA w CF 8D p 9A F7 g f N FF 84 B7 K Q 93 g E1 - D3 s } w v AE 96 98 ED CF BA E9 2 . f 99 95 97 o 13 CA F7 s e $ F4 B5 15 C4 A8 DE M F7 w \ 8D 00 C6 C2 b D3 / 7 w F2 ' BF CD 89 FF > D7 FB BC A2 S N FB A5 CD AF D3 F9 9D DF AE B5 17 CF 9D B7 , B9 9 ^ 7F [ 93 84 F7 } _ EA DF u \ 99 Z t E CA M EF 7 " AD FE 92 9E n 7F EB D8 C { 99 8B 9E w H BF B1 | g 9F F3 FA E1 - E5 CB BB x CF p 8B D2 w v EF w FA E2 F7 s C5 AC $ FC B4 DB BE G E4 DC F0 A0 96 F3 ! t DC FF % A5 CB A4 ^ AB D2 BD E7 9A E ' 08 + AF U 17 EB 8A w A7 N E4 A5 x 93 12 _ - ; 09 DD DF m 11 BE w \ } BA D3 t BC D9 97 9B C5 7F D8 H F1 D 7 8A ^ FA n F0 B8 W E6 84 5 - 8 B5 h o C4 F7 83 P 88 CB AE m t BB L 95 A9 s 90 A2 Y o DF K _ / l D2 D1 C9 91 ' E4 BD / / D 97 m BB E7 14 93 % C5 ; DD CF D8 : ~ B5 4 F FA U F0 8F w w DC FD 83 FC 13 EF w p DA A5 07 _ * - 1D 14 9D D5 84 F E6 F0 FF E4 15 w n A5 9F DE d AE F5 " - f D2 AE 96 1F # FA F1 x C1 L DF l M 06 8A E4 z DB 17 BA l DA e 15 CD 85 86 1F 09 82 h ] C6 { E7 C5 AF Z C5 B0 83 v D9 03 FC / ~ -
The message for which the hex dump is displayed, is a video message of size 4925 bytes. Below is the basic logging in my application:
*** Event sent to RTMP connector: Video - ts: 16777473 length: 4925. Waiting time: -57937, event timestamp: 16777473
14:28:02.045 [RtmpPublisher-workerThread] DEBUG o.r.s.s.consumer.ConnectionConsumer - Message timestamp: 16777473
14:28:02.045 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - Channel id: 5
14:28:02.045 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - Last ping time for connection: -1
14:28:02.045 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - Client buffer duration: 0
14:28:02.046 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - Packet timestamp: 16777473; tardiness: -30892; now: 1307104082045; message clock time: 1307104051152, dropLiveFuturefalse
14:28:02.046 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!12b Wrote expanded timestamp field
14:28:02.046 [NioProcessor-22] DEBUG o.r.server.net.rtmp.BaseRTMPHandler - Message sent
I have captured the entire frame containing this message with wireshark, and annotated it a bit. You can find it here:
http://pastebin.com/iVtphPgU
The video message of 4925 bytes (hex 00 13 3D) is cut up into chunks of 1024 bytes (chunkSize 1024 set by Red5 client and sent to FMS). Indeed, after the 12-byte header and the 4-byte extended timestamp, there are 1024 bytes before the 1-byte header for the next chunk (hex C5). The chunks after that also contain 1024 bytes after the chunk header. This appears correct to me (though please correct me if I'm wrong).
When we look at the error message in the core log, the hex dump displayed also contains 1024 bytes, but it starts from the beginning of the message header. The last 16 bytes of the message chunk itself are not shown.
My question is this: is the hex dump in the error message always capped to 1024 bytes, or did FMS really read too little data?
Something that may be of help, is the reported 'too long' message length 11893407. This corresponds to hex B5 7A 9F, which can also be found in the packet, namely at row 0c60 (I've annotated it as [b5 7a 9f]. This location is exactly 16 bytes after the start of the 4th chunk data, not really a place to look for timestamps.
My assumptions during this bug hunting session were the following (would be nice if someone could validate these for me):
- message length, as specified in the RTMP 12 and 8-bit headers, defines the total number of data bytes for the message, NOT including the header of the first message chunk, its extended timestamp field, or the 1-byte headers for subsequent chunks. The behaviour is the same whether or not the message has an extended timestamp.
- chunk size, as set by the chunkSize message, defines the total number of data bytes for the chunk, not incuding the header or extended timestamp field. The behaviour is the same whether or not the message has an extended timestamp.
I believe I've chased this problem as far as I can without having access to the FMS 3.5 code, or at least being able to crank up the debug logging to the per-message level. I realize it's a pretty detailed issue and a long shot, but being able to publish a stream continuously 24/7 is critical for the project.
I would be very grateful if someone could have a look at this hex dump to see if the message itself is correct, and if so, to have a look at how FMS3.5.6 handles this.
Don't hesitate to ask me for more info if it can help.
Thanks in advance
Davy Herben
Solidity

Hello,
It took a bit longer than expected, but I have managed to create a minimal test application that will reproduce the error condition on all machines I've tested on. The application will simply read an H264 file and publish it to an FMS as a live stream. To hit the error condition faster, without having to wait 4.6 hours, the application will add a fixed offset to all timestamps before sending it to the FMS.
I have created two files:
http://www.solidity.be/publishtest.jar : Runnable java archive with all libraries built in
http://www.solidity.be/publishtest.zip : Zip file containing sources and libraries
You can run the jar as follows:
java -jar publishtest.jar <inputFile> <server> <port> <application> <stream> <timestampOffset>
- inputFile: path to an H264 input video file
- server: hostname or IP of FMS server to publish to
- port: port number to publish to (1935)
- application: application to publish to (live)
- stream: stream to publish to (output)
- timestampOffset: nr of milliseconds to add to the timestamp of each event, in hexadecimal format. Putting FFFFFF here will cause the server to reject the connection immediately, while FFFF00 or FFF000 will allow the publishing to run for awhile before the FMS kills it
Example of a complete command line:
java -jar publishtest.jar /home/myuser/Desktop/movie.mp4 localhost 1935 live output FFF000
Good luck with the bug hunting. Let me know if there is anything I can help you with.
Kind regards,
Davy Herben

Send email from FMS?

Is it possible to send an email from FMS? If not, how would I
go about creating a connection from FMS to a http server running
PHP? Just use LoadVars like a regular Flash client? Would that
invoke cross-domain issues to resolve?

FMS isn't a mailserver, so it can't send mail directly.
You can connect up to your php server using LoadVars. You can
also use netServices and AMFPHP, but that's probably overkill for
your purposes. Loadvars on the server side is pretty much the same
as loadvars on the client side. There is no sandbox for FMS like
there is for the Flashplayer, so the cross domain concerns don't
apply.

Timestamp issue in JDBC sender adapter

All,
Database is sending the timestamp in th below format,
28-06-2010 12:41:20
but SAP PI JDBC adapter is converting the same data as below.
28-06-2010 12:41:20.0
we are getting an extra ZERO, can any one tell me the solution for not getting extra ZERO.
Thank You,
Madhav

Try to Use JDBC Date Function in Select Query .
to_char( Coloumn_name , 'DD-MON-YYYY HH:MI:SS')
it will forcefully get the date in following format .. but one thing to remeber this will covert your date into string format ..so to catch the following date on sender Message Type , it may require to create that structure with string type.
Regards
Prabhat Sharma(Dragon).

FlashPlayer send incorrect timestamps to FMS

Similar Messages

Maybe you are looking for