This post is a problem report and solution at the same in case someone else is having the same problem I had.
I installed MVN, GIT, Java SDK 1.7.x environment in Win7HomePremium system. Compilation and installation of PMS went just fine. However when I tried to launch PMS from PMS.EXE or PMS.BAT commands, nothing happened and no GUI. TaskManager had JAVAW.EXE process but it didn't seem to do anything I had to manually stop the process. I went through FAQ instructions to make sure PMS was not running in headless mode "no-gui" mode but no help.
Debug.log file had following lines in the beginning, but then the last line was always "Releasing connection back to connection manager" and that's it.
- Code: Select all
[main] DEBUG 10:54:42.300 Java version: 1.7.0_02
[main] DEBUG 10:54:42.300 Java vendor: Oracle Corporation
[main] DEBUG 10:54:42.300 Java class path: update.jar;pms.jar
[main] DEBUG 10:54:42.300 Operating system name: Windows 7
[main] DEBUG 10:54:42.300 Operating system architecture: x86
[main] DEBUG 10:54:42.300 Operating system version: 6.1
[main] DEBUG 10:54:42.956 SUN 1.7: SUN (DSA key/parameter generation; DSA signing; SHA-1, MD5 digests; SecureRandom; X.509 certificates; JKS keystore; PKIX CertPathValidator; PKIX CertPathBuilder; LDAP, Collection CertStores, JavaPolicy Policy; JavaLoginConfig Configuration)
-snip-snip-snip
[main] DEBUG 10:54:48.291 checkNetworkInterface(parent = null, child interfaces = [name:lo (Software Loopback Interface 1), name:net0 (WAN Miniport (SSTP)), name:net1 (WAN Miniport (L2TP)), name:net2 (WAN Miniport (PPTP)), name:ppp0 (WAN Miniport (PPPOE)), name:eth0 (WAN Miniport (IPv6)), name:eth1 (WAN Miniport (Network Monitor)), name:eth2 (WAN Miniport (IP)), name:ppp1 (RAS Async Adapter), name:net3 (Bluetooth Device (RFCOMM Protocol TDI)), name:eth3 (Bluetooth Device (Personal Area Network)), name:eth4 (Realtek PCIe GBE Family Controller), name:net4 (Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC), name:net5 (Teredo Tunneling Pseudo-Interface), name:net6 (WAN Miniport (IKEv2)), name:net7 (Microsoft 6to4 -sovitin), name:eth5 (VMware Virtual Ethernet Adapter for VMnet1), name:eth6 (VMware Virtual Ethernet Adapter for VMnet8), name:net8 (Microsoft ISATAP -sovitin #4), name:net9 (Microsoft ISATAP -sovitin #5), name:net10 (Microsoft ISATAP -sovitin), name:net11 (Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC-Virtual WiFi Filter Driver-0000), name:net12 (Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC-QoS Packet Scheduler-0000), name:eth7 (Realtek PCIe GBE Family Controller-QoS Packet Scheduler-0000), name:eth8 (Realtek PCIe GBE Family Controller-WFP LightWeight Filter-0000), name:eth9 (WAN Miniport (IPv6)-QoS Packet Scheduler-0000), name:eth10 (WAN Miniport (IP)-QoS Packet Scheduler-0000), name:eth11 (WAN Miniport (Network Monitor)-QoS Packet Scheduler-0000), name:net13 (Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC-Native WiFi Filter Driver-0000), name:net14 (Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC-WFP LightWeight Filter-0000)])
[main] DEBUG 10:54:48.291 checking lo, display name : Software Loopback Interface 1
[main] DEBUG 10:54:48.291 available addresses for lo is : [/127.0.0.1]
[main] DEBUG 10:54:48.291 non loopback/ipv4 addresses : []
[main] DEBUG 10:54:48.291 checkNetworkInterface(parent = lo, child interfaces = [])
[main] DEBUG 10:54:48.291 checkNetworkInterface(parent = lo) finished.
[main] DEBUG 10:54:48.291 sub address for lo is []
[main] DEBUG 10:54:48.291 checking /127.0.0.1 from /127.0.0.1/8 [/127.255.255.255] on lo
[main] DEBUG 10:54:48.291 has /127.0.0.1, which is skipped, because loopback=true, ipv6=false
[main] INFO 10:54:48.291 found lo, without valid address
--snip snip--
[main] DEBUG 10:54:48.291 checking eth4, display name : Realtek PCIe GBE Family Controller
[main] DEBUG 10:54:48.291 available addresses for eth4 is : []
[main] DEBUG 10:54:48.291 non loopback/ipv4 addresses : []
[main] DEBUG 10:54:48.291 checkNetworkInterface(parent = eth4, child interfaces = [])
[main] DEBUG 10:54:48.306 checkNetworkInterface(parent = eth4) finished.
[main] DEBUG 10:54:48.306 sub address for eth4 is []
[main] INFO 10:54:48.306 found eth4, without valid address
[main] DEBUG 10:54:48.306 checking net4, display name : Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC
[main] DEBUG 10:54:48.306 available addresses for net4 is : [/192.168.0.200]
[pool-1-thread-1] DEBUG 10:54:49.055 << "HTTP/1.1 200 OK[\r][\n]"
[pool-1-thread-1] DEBUG 10:54:49.055 << "HTTP/1.1 200 OK[\r][\n]"
--snip snip--
pool-1-thread-1] DEBUG 10:54:49.071 << "X-Content-Type-Options: nosniff[\r][\n]"
[pool-1-thread-1] DEBUG 10:54:49.071 << "[\r][\n]"
[pool-1-thread-1] DEBUG 10:54:49.071 Buffering response body
[pool-1-thread-1] DEBUG 10:54:49.071 << "LatestVersion="1.50.0"[\n]"
[pool-1-thread-1] DEBUG 10:54:49.071 << "DownloadUrl.windows="http://ps3mediaserver.googlecode.com/files/pms-setup-windows-1.50.0.exe"[\n]"
[pool-1-thread-1] DEBUG 10:54:49.071 Should NOT close connection in response to directive: keep-alive
[pool-1-thread-1] DEBUG 10:54:49.071 Releasing connection back to connection manager.
After trying "everything" I finally found a solution. I modified the default PMS.BAT file and PMS GUI booted up and everything seemed to work with my Samsung TV. Original PMS.BAT had cmdline options "-Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8". I removed these two options and line was just as follows:
- Code: Select all
start "" "javaw.exe" -Xmx768M -classpath update.jar;pms.jar net.pms.PMS
The difference between "working and non-working" debug.log file is how PMS traverse through network adapters and tries to find a valid IP address. Non-working log doesnt have "found net4 -> 192.168.0.200" line but working debug.log has this line. Seems that "broken version" doesnt find any valid IP addresses to listen connections so GUI doesnt open but javaw stays there and no clear error messages.
I guess default PMS.EXE/PMS.BAT and -Djava.net.preferIPv4Stack=true option breaks how PMS goes through list of adapters. I have several adapters so this is probably an issue in this scenario only (WWAN, WLAN, etherhet, several VMWare virtaul adapters, Bluetooth adapters, Mobile 3G adapters etc).
Anyway. This is no longer a problem in my system because I found the workaround. I just thought to mention this in case someone else is hitting the same problem. Thanks for the good work with PMS.
