Tambo's Tricks

Fix network TV streaming (Working then nothing) Mediaportal extension with Kodi

jerometambo — Fri, 23 Dec 2016 00:00:00 GMT

If, like myself, you have a Mediacenter based on Kodi (with Mediaportal for TV server) and you want to watch your TV channels from anywhere, you might have seen the "Working in the wind" problem:

Figure 1. When you click on your channel

Figure 2. And voilà

So let’s read the Kodi’s logs:

19:30:52 T:5604  NOTICE: DVDPlayer: Opening: pvr://channels/tv/Toutes les chaînes/pvr.mediaportal.tvserver_17.pvr
19:30:52 T:5604 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
19:30:52 T:2472  NOTICE: Creating InputStream
19:30:52 T:2472  NOTICE: AddOnLog: MediaPortal PVR Client: Open Live stream for channel uid=17
19:30:53 T:2472  NOTICE: AddOnLog: MediaPortal PVR Client: Channel timeshift buffer: C:\Tv\live3-0.ts.tsbuffer
19:30:53 T:2472  NOTICE: AddOnLog: MediaPortal PVR Client: Creating a new TsReader...
19:30:53 T:2472  NOTICE: AddOnLog: MediaPortal PVR Client: TsReader open 'C:\Tv\live3-0.ts.tsbuffer'
19:30:53 T:2472  NOTICE: AddOnLog: MediaPortal PVR Client: Cannot access 'C:\Tv\live3-0.ts.tsbuffer' directly. Assuming multiseat mode. Need to translate to UNC filename.
19:30:53 T:2472  NOTICE: AddOnLog: MediaPortal PVR Client: Translate path C:\Tv\live3-0.ts.tsbuffer -> smb://kodi:kodi@BBMEDIACENTER/Tv/live3-0.ts.tsbuffer
19:30:53 T:2472   ERROR: AddOnLog: MediaPortal PVR Client: Cannot find or access file: smb://kodi:kodi@BBMEDIACENTER/Tv/live3-0.ts.tsbuffer. Check share access rights.
19:30:53 T:2472   ERROR: AddOnLog: MediaPortal PVR Client: Cannot open timeshift buffer C:\Tv\live3-0.ts.tsbuffer
19:30:53 T:2472  NOTICE: AddOnLog: MediaPortal PVR Client: TsReader: closing file
19:30:54 T:2472  NOTICE: AddOnLog: MediaPortal PVR Client: CloseLiveStream: True
19:30:54 T:2472   ERROR: CDVDPlayer::OpenInputStream - error opening [pvr://channels/tv/Toutes les chaînes/pvr.mediaportal.tvserver_17.pvr]
19:30:54 T:2472  NOTICE: CDVDPlayer::OnExit()
19:30:54 T:5604  NOTICE: CDVDPlayer::CloseFile()
19:30:54 T:5604  NOTICE: DVDPlayer: waiting for threads to exit
19:30:54 T:5604  NOTICE: DVDPlayer: finished waiting
19:30:54 T:5604  NOTICE: CDVDPlayer::CloseFile()

It seems that TsReader can’t access the SMB share, even this SMB share works.

The simpliest solution to this problem is to chage the streaming library from TsReader to ffmpeg:

Figure 3. System → Settings → Add-ons → My add-ons → PVR clients → MediaPortal PVR Client → Configure → Playback

Figure 4. Success !

I hope it can prevent you from nervous crisis with Kodi :).

Tchou !

Useful links:

How to use JavaEE 6 upload feature with configurable properties (max filesize, temp directory, etc.) and Tomcat performance tricks

jerometambo — Tue, 20 Dec 2016 00:00:00 GMT

Since Servlet 3.0 (JavaEE 6), Servlet 3.0 supports two additional HttpServletRequest methods:

Collection getParts()

Part getPart(String name)

With this, you don’t need other library anymore to perform some file uploads.

To set the upload properties, you can use the @MultipartConfig annotation. The @MultipartConfig annotation indicates that the servlet expects requests to be made using the multipart/form-data MIME type. Here’s an example:

@MultipartConfig(location="/tmp", fileSizeThreshold=1024*1024,
    maxFileSize=1024*1024*5, maxRequestSize=1024*1024*5*5)

Instead of using the @MultipartConfig annotation to hard-code these attributes in your file upload servlet, you could add the following as a child element of the servlet configuration element in the web.xml file:

But if you want to set dynamically your upload settings (via properties for example) from your java code, you’re stuck. Using the Dynamic servlet registration as described in my previous post, you can instanciate the configuration object and set whatever you want:

package org.jerometambo.dynamicservletinitializer.servlet;

import javax.servlet.ServletContextEvent;
import javax.servlet.ServletContextListener;
import javax.servlet.ServletRegistration.Dynamic;

/**
 * Servlets initialization.
 */
public class DynamicServletInitializer implements ServletContextListener {

    public void contextInitialized(ServletContextEvent servletContextEvent) {
        final int size = Parameters.UPLOAD_SIZE_LIMIT * 1024; //from wherever you want
        Dynamic registered = servletContextEvent.getServletContext().addServlet("HelloWorld", HelloWorld.class);
        registered.addMapping("/HelloWorld");
        registered.setMultipartConfig(new MultipartConfigElement(Parameters.UPLOAD_TEMP_DIR, size, size, size));
    }

    public void contextDestroyed(ServletContextEvent sce) {

    }

}

You can find an example on my github: https://github.com/jerometambo/dynamicservletinitializer on the uploadConfigFromProperties branch.

You can find an utils lib to deal with File uploads on my github: https://github.com/jerometambo/javaeeuploadutils on the master branch.

Useful links:

Tchou !

How to dynamically register a Servlet (SCI since Servlet 3.0) with Tomcat 7 / 8 speed-up optimization

jerometambo — Thu, 15 Dec 2016 00:00:00 GMT

Since Tomcat 7, and it’s even worth with Tomcat 8, the time to start up a webapp has seriously increased. There are 2 excellent posts about how to speed-up the start-up of a webapp in Tomcat by changing your webapp configuration (mostly web.xml) :

If you exclude JARs from scanning in Tomcat, you will not be able to perform some dynamic registration of Servlet via the @WebListener annotation a ServletContextListener implementation :

package org.jerometambo.dynamicservletinitializer.servlet;

import javax.servlet.ServletContextEvent;
import javax.servlet.ServletContextListener;
import javax.servlet.ServletRegistration.Dynamic;

/**
 * Then register the main {@link Servlet}. Inject configurations like {@link MultipartConfigElement}.
 */
@WebListener
public class DynamicServletInitializer implements ServletContextListener {
  /** The main {@link Servlet} name. */
  public static final String MAIN_SERVLET = "HelloWorld";
  /** The main error page name. */
  public static final String ERROR_PAGE = "errorPage";

  @Override
  public void contextInitialized(ServletContextEvent servletContextEvent) {
	registerMainServlet(servletContextEvent);
  }

  /**
   * Registers the main servlet in application.
   */
  protected void registerMainServlet(ServletContextEvent servletContextEvent) {
    Dynamic registered = servletContextEvent.getServletContext().addServlet(MAIN_SERVLET, HelloWorldServlet.class);
    registered.addMapping("/HelloWorld");
    registered.setInitParameter(ERROR_PAGE, getErrorPage());
  }

  /**
   * @return the relative path of the error page in application.
   */
  protected String getErrorPage() {
    return "/jsp/org/jerometambo/errorPage.jsp";
  }

}

The trick in order to be able to use SCI and features like this one with Tomcat 7/8 tuning, is to declare your listener in your web.xml:





  
    
  
    org.jerometambo.dynamicservletinitializer.servlet.DynamicServletInitializer

You can find an example on my github: https://github.com/jerometambo/dynamicservletinitializer on the master branch.

I hope it can help you to fasten up your applications start-up.

Tchou !

How to use CXF 3.x implementation of JAX-RS 2.0 (REST) with Weblogic 12c

jerometambo — Tue, 13 Dec 2016 00:00:00 GMT

When I had to deploy a webapp with REST web services based on CXF 3.x on Weblogic 12c server, my problems started. With default configuration, Weblogic wants to use its internal implementation (JAX-RS 2.0 and serialization) to deploy the REST web services (Error 500):

java.lang.LinkageError: ClassCastException: attempting to castjar:file:/opt/weblogic/oracle_common/modules/javax.ws.rs.javax.ws.rs-api.jar!/javax/ws/rs/ext/RuntimeDelegate.class to jar:file:/opt/weblogic/oracle_common/modules/javax.ws.rs.javax.ws.rs-api.jar!/javax/ws/rs/ext/RuntimeDelegate.class

at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:146)

at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:120)

at javax.ws.rs.core.Response$ResponseBuilder.newInstance(Response.java:848)

at javax.ws.rs.core.Response.status(Response.java:590)

at javax.ws.rs.core.Response.status(Response.java:601)

After many researches and the reading of Oracle posts (I even tried to open a SR at Oracle but it wasn’t really helpful this time), I manage to find a working configuration. This configuration sets Weblogic not to choose its own implementations for web services deployment and resources serialization.

To let CXF works (and Jackson here for the serialization side), you have to change these configuration files:

../webapp/WEB-INF/weblogic.xml :




	
		javax.ws.rs.*
		com.fasterxml.jackson.*

../META-INF/weblogic-application.xml



    
      javax.ws.rs.*
      com.fasterxml.jackson.*
      weblogic.jaxrs.api.client.*
      weblogic.jaxrs.internal.api.*
      weblogic.jaxrs.dispatch.*
      weblogic.jaxrs.monitoring.util.*

I hope this can help some REST web services developers with CXF 3 who have to deal with Weblogic 12c :)

Tchou !