geileseitehier
Erster Beitrag
ich kann den kim-client von telekom t-systems nicht starten. in der clientmodule.log findet sich folgendes
der vorgegebene default port 8086 geht auch nicht. ich habe ihn auf 8087 geändert. der 8087 ging auch nicht. ich habe viel an der firewall von windows server 2012 r2 geändert, sie sogar ausgeschaltet.
dann habe ich zufällig gelesen, dass nur 1 programm pro port auf einen port lauschen kann. ich fand zufällig, dass solutio charly (PVS) auf den port 8086 lauscht. über den 8087 fand ich nichts. letzter versuch war 8088. der ging!
und die firewall ist auch eingeschaltet! ich brauchte keinen eintrag für KIM TCP oder KIM UDP an port 8088!
2021-09-09 12:34:10.093 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] ERROR com.tsystems.gematik.komle.clientmodule.ClientModule - catching javax.management.JMException: Unable to create RMI registry on port 8087
at com.tsystems.gematik.komle.clientmodule.CMJmxServer.createJmException(CMJmxServer.java:584) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.CMJmxServer.startRmiRegistry(CMJmxServer.java:521) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.CMJmxServer.start(CMJmxServer.java:174) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.ClientModule.startJMXServer(ClientModule.java:245) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.ClientModule.startClientModule(ClientModule.java:139) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.admin.CMJMXClient.startClientModule(CMJMXClient.java:78) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.admin.CMJMXClient.executeCommandline(CMJMXClient.java:154) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.ClientModule.handleCmdLine(ClientModule.java:103) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.ClientModule.main(ClientModule.java:467) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_265]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_265]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_265]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_265]
at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84) ~[i4jruntime.jar]
at com.exe4j.runtime.WinLauncher.main(WinLauncher.java:94) ~[i4jruntime.jar]
at com.install4j.runtime.launcher.WinLauncher.main(WinLauncher.java:25) ~[i4jruntime.jar]
Caused by: java.rmi.server.ExportException: Port already in use: 8087; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:346) ~[?:1.8.0_265]
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:254) ~[?:1.8.0_265]
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:412) ~[?:1.8.0_265]
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147) ~[?:1.8.0_265]
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:237) ~[?:1.8.0_265]
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:213) ~[?:1.8.0_265]
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:198) ~[?:1.8.0_265]
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:203) ~[?:1.8.0_265]
at com.tsystems.gematik.komle.clientmodule.CMJmxServer.startRmiRegistry(CMJmxServer.java:496) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
... 14 more
Caused by: java.net.BindException: Address already in use: JVM_Bind
at java.net.DualStackPlainSocketImpl.bind0(Native Method) ~[?:1.8.0_265]
at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106) ~[?:1.8.0_265]
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387) ~[?:1.8.0_265]
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190) ~[?:1.8.0_265]
at java.net.ServerSocket.bind(ServerSocket.java:390) ~[?:1.8.0_265]
at java.net.ServerSocket.<init>(ServerSocket.java:252) ~[?:1.8.0_265]
at java.net.ServerSocket.<init>(ServerSocket.java:143) ~[?:1.8.0_265]
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:45) ~[?:1.8.0_265]
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:345) ~[?:1.8.0_265]
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:670) ~[?:1.8.0_265]
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:335) ~[?:1.8.0_265]
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:254) ~[?:1.8.0_265]
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:412) ~[?:1.8.0_265]
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147) ~[?:1.8.0_265]
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:237) ~[?:1.8.0_265]
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:213) ~[?:1.8.0_265]
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:198) ~[?:1.8.0_265]
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:203) ~[?:1.8.0_265]
at com.tsystems.gematik.komle.clientmodule.CMJmxServer.startRmiRegistry(CMJmxServer.java:496) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
... 14 more
2021-09-09 12:34:10.095 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - Shutdown KOM-LE Client Module JMX Server...
2021-09-09 12:34:10.095 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - Shutdown KOM-LE Client Module JMX Server done.
2021-09-09 12:34:10.095 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - Remove pid file...
2021-09-09 12:34:10.102 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - Remove pid file done.
2021-09-09 12:34:10.803 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.accmgr.ldap.LdapConnectionManager - Initializing Ldap Connection Manager for host:konnektor port: 636
2021-09-09 12:34:10.833 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.accmgr.ldap.LdapConnectionManager - Ldap Connection Manager is initialized
2021-09-09 12:34:10.842 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - Shutdown log4j...
2021-09-09 12:34:10.902 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - Shutdown log4j done.
2021-09-09 12:34:10.902 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] ERROR com.tsystems.gematik.komle.clientmodule.ClientModule - T-KIM Client Module konnte NICHT erfolgreich gestartet werden: Unable to create RMI registry on port 8087, bitte ueberpruefen Sie die Log Datei fuer weitere Details.
at com.tsystems.gematik.komle.clientmodule.CMJmxServer.createJmException(CMJmxServer.java:584) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.CMJmxServer.startRmiRegistry(CMJmxServer.java:521) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.CMJmxServer.start(CMJmxServer.java:174) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.ClientModule.startJMXServer(ClientModule.java:245) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.ClientModule.startClientModule(ClientModule.java:139) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.admin.CMJMXClient.startClientModule(CMJMXClient.java:78) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.admin.CMJMXClient.executeCommandline(CMJMXClient.java:154) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.ClientModule.handleCmdLine(ClientModule.java:103) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at com.tsystems.gematik.komle.clientmodule.ClientModule.main(ClientModule.java:467) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_265]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_265]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_265]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_265]
at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84) ~[i4jruntime.jar]
at com.exe4j.runtime.WinLauncher.main(WinLauncher.java:94) ~[i4jruntime.jar]
at com.install4j.runtime.launcher.WinLauncher.main(WinLauncher.java:25) ~[i4jruntime.jar]
Caused by: java.rmi.server.ExportException: Port already in use: 8087; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:346) ~[?:1.8.0_265]
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:254) ~[?:1.8.0_265]
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:412) ~[?:1.8.0_265]
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147) ~[?:1.8.0_265]
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:237) ~[?:1.8.0_265]
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:213) ~[?:1.8.0_265]
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:198) ~[?:1.8.0_265]
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:203) ~[?:1.8.0_265]
at com.tsystems.gematik.komle.clientmodule.CMJmxServer.startRmiRegistry(CMJmxServer.java:496) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
... 14 more
Caused by: java.net.BindException: Address already in use: JVM_Bind
at java.net.DualStackPlainSocketImpl.bind0(Native Method) ~[?:1.8.0_265]
at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106) ~[?:1.8.0_265]
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387) ~[?:1.8.0_265]
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190) ~[?:1.8.0_265]
at java.net.ServerSocket.bind(ServerSocket.java:390) ~[?:1.8.0_265]
at java.net.ServerSocket.<init>(ServerSocket.java:252) ~[?:1.8.0_265]
at java.net.ServerSocket.<init>(ServerSocket.java:143) ~[?:1.8.0_265]
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:45) ~[?:1.8.0_265]
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:345) ~[?:1.8.0_265]
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:670) ~[?:1.8.0_265]
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:335) ~[?:1.8.0_265]
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:254) ~[?:1.8.0_265]
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:412) ~[?:1.8.0_265]
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147) ~[?:1.8.0_265]
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:237) ~[?:1.8.0_265]
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:213) ~[?:1.8.0_265]
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:198) ~[?:1.8.0_265]
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:203) ~[?:1.8.0_265]
at com.tsystems.gematik.komle.clientmodule.CMJmxServer.startRmiRegistry(CMJmxServer.java:496) ~[ClientModule-2.0.7-2-SNAPSHOT.jar:2.0.7-2-SNAPSHOT-18037]
... 14 more
2021-09-09 12:34:10.095 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - Shutdown KOM-LE Client Module JMX Server...
2021-09-09 12:34:10.095 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - Shutdown KOM-LE Client Module JMX Server done.
2021-09-09 12:34:10.095 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - Remove pid file...
2021-09-09 12:34:10.102 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - Remove pid file done.
2021-09-09 12:34:10.803 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.accmgr.ldap.LdapConnectionManager - Initializing Ldap Connection Manager for host:konnektor port: 636
2021-09-09 12:34:10.833 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.accmgr.ldap.LdapConnectionManager - Ldap Connection Manager is initialized
2021-09-09 12:34:10.842 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - Shutdown log4j...
2021-09-09 12:34:10.902 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - Shutdown log4j done.
2021-09-09 12:34:10.902 [{id=ddbb95dc-f570-4114-aac2-a2486ffd58bc}] [main] ERROR com.tsystems.gematik.komle.clientmodule.ClientModule - T-KIM Client Module konnte NICHT erfolgreich gestartet werden: Unable to create RMI registry on port 8087, bitte ueberpruefen Sie die Log Datei fuer weitere Details.
der vorgegebene default port 8086 geht auch nicht. ich habe ihn auf 8087 geändert. der 8087 ging auch nicht. ich habe viel an der firewall von windows server 2012 r2 geändert, sie sogar ausgeschaltet.
dann habe ich zufällig gelesen, dass nur 1 programm pro port auf einen port lauschen kann. ich fand zufällig, dass solutio charly (PVS) auf den port 8086 lauscht. über den 8087 fand ich nichts. letzter versuch war 8088. der ging!
2021-09-09 12:37:11.814 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - BatchScheduler start...
2021-09-09 12:37:11.919 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - BatchScheduler started successfully.
2021-09-09 12:37:11.942 [{id=2bcfad22-a376-4a76-8053-9c69d0b57fa0}] [QuartzScheduler_Worker-2] INFO com.tsystems.gematik.komle.clientmodule.jobs.CertIdEMailIccsnCacheAlivePeriodWatcherJob - Executing CertIdEMailIccsn cache update job...
2021-09-09 12:37:11.994 [{id=6600319b-d591-48dc-9ac1-cd5cd596796a}] [QuartzScheduler_Worker-1] INFO com.tsystems.gematik.komle.clientmodule.jobs.EmailEncCertCacheAlivePeriodWatcherJob - Executing EmailEncCertificate cache update job...
2021-09-09 12:37:12.379 [{id=2bcfad22-a376-4a76-8053-9c69d0b57fa0}] [QuartzScheduler_Worker-2] INFO com.tsystems.gematik.komle.accmgr.ldap.LdapConnectionManager - Initializing Ldap Connection Manager for host:konnektor port: 636
2021-09-09 12:37:12.407 [{id=2bcfad22-a376-4a76-8053-9c69d0b57fa0}] [QuartzScheduler_Worker-2] INFO com.tsystems.gematik.komle.accmgr.ldap.LdapConnectionManager - Ldap Connection Manager is initialized
2021-09-09 12:37:12.414 [{id=2bcfad22-a376-4a76-8053-9c69d0b57fa0}] [QuartzScheduler_Worker-2] INFO com.tsystems.gematik.komle.clientmodule.jobs.CertIdEMailIccsnCacheAlivePeriodWatcherJob - CertIdEMailIccsn cache update job execution finished.
2021-09-09 12:37:12.415 [{id=6600319b-d591-48dc-9ac1-cd5cd596796a}] [QuartzScheduler_Worker-1] INFO com.tsystems.gematik.komle.clientmodule.jobs.EmailEncCertCacheAlivePeriodWatcherJob - EmailEncCertificate cache update job execution finished.
2021-09-09 12:37:15.226 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.smtp.server.SmtpProxyServer - Starting SMTP Server
2021-09-09 12:37:15.377 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - SMTP Proxy Server started successfully.
2021-09-09 12:37:15.377 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.pop3.server.Pop3ProxyServer - Starting POP3 Server
2021-09-09 12:37:15.380 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - POP3 Proxy Server started successfully.
2021-09-09 12:37:15.380 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - T-KIM Client Module wurde erfolgreich gestartet.
2021-09-09 12:37:11.919 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - BatchScheduler started successfully.
2021-09-09 12:37:11.942 [{id=2bcfad22-a376-4a76-8053-9c69d0b57fa0}] [QuartzScheduler_Worker-2] INFO com.tsystems.gematik.komle.clientmodule.jobs.CertIdEMailIccsnCacheAlivePeriodWatcherJob - Executing CertIdEMailIccsn cache update job...
2021-09-09 12:37:11.994 [{id=6600319b-d591-48dc-9ac1-cd5cd596796a}] [QuartzScheduler_Worker-1] INFO com.tsystems.gematik.komle.clientmodule.jobs.EmailEncCertCacheAlivePeriodWatcherJob - Executing EmailEncCertificate cache update job...
2021-09-09 12:37:12.379 [{id=2bcfad22-a376-4a76-8053-9c69d0b57fa0}] [QuartzScheduler_Worker-2] INFO com.tsystems.gematik.komle.accmgr.ldap.LdapConnectionManager - Initializing Ldap Connection Manager for host:konnektor port: 636
2021-09-09 12:37:12.407 [{id=2bcfad22-a376-4a76-8053-9c69d0b57fa0}] [QuartzScheduler_Worker-2] INFO com.tsystems.gematik.komle.accmgr.ldap.LdapConnectionManager - Ldap Connection Manager is initialized
2021-09-09 12:37:12.414 [{id=2bcfad22-a376-4a76-8053-9c69d0b57fa0}] [QuartzScheduler_Worker-2] INFO com.tsystems.gematik.komle.clientmodule.jobs.CertIdEMailIccsnCacheAlivePeriodWatcherJob - CertIdEMailIccsn cache update job execution finished.
2021-09-09 12:37:12.415 [{id=6600319b-d591-48dc-9ac1-cd5cd596796a}] [QuartzScheduler_Worker-1] INFO com.tsystems.gematik.komle.clientmodule.jobs.EmailEncCertCacheAlivePeriodWatcherJob - EmailEncCertificate cache update job execution finished.
2021-09-09 12:37:15.226 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.smtp.server.SmtpProxyServer - Starting SMTP Server
2021-09-09 12:37:15.377 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - SMTP Proxy Server started successfully.
2021-09-09 12:37:15.377 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.pop3.server.Pop3ProxyServer - Starting POP3 Server
2021-09-09 12:37:15.380 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - POP3 Proxy Server started successfully.
2021-09-09 12:37:15.380 [{id=0e23be6c-3442-4a16-8250-20d7398c0df7}] [main] INFO com.tsystems.gematik.komle.clientmodule.ClientModule - T-KIM Client Module wurde erfolgreich gestartet.
und die firewall ist auch eingeschaltet! ich brauchte keinen eintrag für KIM TCP oder KIM UDP an port 8088!
Zuletzt bearbeitet von einem Moderator: