Dear Maxim,

I pulled the latest version of OM and test the recording part of application 
and feel one old issue is creating problem again.

Scenario to replicate is the same like before :


1.       Start Recording.

2.       After few minutes , just click on “Exist” button.

3.       Recording stopped successfully.

4.       Now go to “/hibernate” directory and I saw “*.mp4” file is created 
there but it was only of few KBs  only in size (50-60 KBs).

5.       When I tried to open it (In media player or in VLC player) it show 
that some process using this file so not able to open.

6.       Now just stop the red5 server or go to task manager and kill  java 
process.

7.       Now I saw full size “*.mp4” file created immediately as java killed 
and runs very well.

So the issue what I feel is- It is stuck somewhere in JVM and not able to 
create full size “*.mp4” but as java killed then full size “*.mp4” is created 
successfully and runs in VLC well.

Can you please have look.

Thanks,
Amit

From: K, Amit (MIND)
Sent: Wednesday, October 4, 2017 5:06 PM
To: Maxim Solodovnik <solomax...@gmail.com>
Cc: 'user@openmeetings.apache.org' <user@openmeetings.apache.org>
Subject: RE: Warning!!!PossibleSpam Re: Regarding JIRA - OPENMEETINGS-1715 OM 
Version 4.0.0

One more thing I noticed while exiting by “Exit” button click- To reproduce 
steps are below:


1.       Start Recording.

2.       After few minutes , just click on “Exist” button.

3.       Recording stopped successfully.

4.       Now go to “/hibernate” directory and I saw “*.mp4” file is created 
there but it was only of few KBs  only in size (50-60 KBs).

5.       When I tried to open it (In media player or in VLC player) it show 
that some process using this file so not able to open.

6.       Now just stop the red5 server or go to task manager and kill  java 
process.

7.       Now I saw full size “*.mp4” file created immediately as java killed 
and runs very well.

So the conclusion is- It is stuck somewhere in JVM and not able to create full 
size “*.mp4” but as java killed then full size “*.mp4” is created successfully 
and runs in VLC well.

Thanks,
Amit


From: K, Amit (MIND)
Sent: Wednesday, October 4, 2017 4:09 PM
To: Maxim Solodovnik <solomax...@gmail.com<mailto:solomax...@gmail.com>>
Cc: 'user@openmeetings.apache.org' 
<user@openmeetings.apache.org<mailto:user@openmeetings.apache.org>>
Subject: RE: Warning!!!PossibleSpam Re: Regarding JIRA - OPENMEETINGS-1715 OM 
Version 4.0.0

Hi Maxim,

I just saw code changes related… now it will work perfect.

Thanks for your kind and continuous support…. ☺


From: K, Amit (MIND)
Sent: Wednesday, October 4, 2017 3:21 PM
To: Maxim Solodovnik <solomax...@gmail.com<mailto:solomax...@gmail.com>>
Cc: 'user@openmeetings.apache.org' 
<user@openmeetings.apache.org<mailto:user@openmeetings.apache.org>>
Subject: RE: Warning!!!PossibleSpam Re: Regarding JIRA - OPENMEETINGS-1715 OM 
Version 4.0.0

Recording is stopped very well… but conversion to .mp4 not executed 
(startConversionThread).

From: Maxim Solodovnik [mailto:solomax...@gmail.com]
Sent: Wednesday, October 4, 2017 3:09 PM
To: K, Amit (MIND) <ami...@mind-infotech.com<mailto:ami...@mind-infotech.com>>
Cc: Openmeetings user-list 
<user@openmeetings.apache.org<mailto:user@openmeetings.apache.org>>
Subject: Warning!!!PossibleSpam Re: Regarding JIRA - OPENMEETINGS-1715 OM 
Version 4.0.0

What is the issue in this case? recording is not stopped?

On Wed, Oct 4, 2017 at 4:34 PM, K, Amit (MIND) 
<ami...@mind-infotech.com<mailto:ami...@mind-infotech.com>> wrote:
Hi Maxim…

Almost fixed.. thanks for your effort.. But ☺ :

As I click on the “Exit” button, related code ran but as there is no user exist 
in room it halt execution with message “Unable to find recordingId on recording 
stop”  in
RecordingService.java class
stopRecording(IScope scope, IClient client) method.

We also need to look that situation too.

Thanks,
Amit

From: Maxim Solodovnik 
[mailto:solomax...@gmail.com<mailto:solomax...@gmail.com>]
Sent: Wednesday, October 4, 2017 2:28 PM
To: K, Amit (MIND) <ami...@mind-infotech.com<mailto:ami...@mind-infotech.com>>
Cc: Openmeetings user-list 
<user@openmeetings.apache.org<mailto:user@openmeetings.apache.org>>
Subject: Re: Regarding JIRA - OPENMEETINGS-1715 OM Version 4.0.0

Should be fixed

On Wed, Oct 4, 2017 at 3:52 PM, Maxim Solodovnik 
<solomax...@gmail.com<mailto:solomax...@gmail.com>> wrote:
Seems to be broken once again
Will fix

On Wed, Oct 4, 2017 at 2:46 PM, Maxim Solodovnik 
<solomax...@gmail.com<mailto:solomax...@gmail.com>> wrote:
According to my tests sharing/recording is stopped and connection to the server 
is closed.
Will try to double check

On Wed, Oct 4, 2017 at 2:16 PM, K, Amit (MIND) 
<ami...@mind-infotech.com<mailto:ami...@mind-infotech.com>> wrote:
Dear Maxim,

1.    Regarding JIRA - 
OPENMEETINGS-1715<https://issues.apache.org/jira/browse/OPENMEETINGS-1715> OM 
Version 4.0.0
2.    Screen-sharing and recording should be stopped in case user exit the room.


Above issue is marked as resolved in JIRA.

But as I see after pulling latest from repository, the behavior is still same.

To make it more clear:

The point was about to stop the recording (Running using applet) as user exits 
the room. Cases are below:


1.       As user click on “Exit” button from top left corner of room on browser 
recording/screen sharing should be stopped.

2.       As user close browser using cross button of browser recording/screen 
sharing should be stopped.

In both cases I saw recording listener was still running and recording size 
still increases even I did Point #1 and #2 explained above.

Thanks,
Amit


________________________________

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any 
virus/trojan/worms/malicious code transmitted by this email. 
www.motherson.com<http://www.motherson.com>



--
WBR
Maxim aka solomax



--
WBR
Maxim aka solomax



--
WBR
Maxim aka solomax

________________________________

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any 
virus/trojan/worms/malicious code transmitted by this email. 
www.motherson.com<http://www.motherson.com>



--
WBR
Maxim aka solomax

________________________________

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any 
virus/trojan/worms/malicious code transmitted by this email. www.motherson.com

Reply via email to