Startseite › Foren › Hilfe bei Problemen › Anmeldung an Server nicht mehr möglich
Verschlagwortet: j-lawyer-server.ear, Server, Verbindung, Windows
- Dieses Thema hat 3 Antworten sowie 3 Stimmen und wurde zuletzt vor vor 1 Jahr, 10 Monaten von Veraendert aktualisiert.
-
AutorBeiträge
-
14. Mai 2019 um 22:08 #2844RATeilnehmer
Hallo,
seit gestern besteht das Problem, dass wir uns beim Login nicht mehr mit dem Server verbinden können (Benutzername / Password oder Verbindungsparameter falsch).
Der Server läuft auf localhost Port 8080, beides ist korrekt eingestellt.
Der Rechner wurde bereits neu gestartet. Der MySql-Dienst und der j-lawyer-Dienst ebenfalls – ohne Erfolg.
Die letzten Logeinträge von Server:
2019-05-14 21:43:53,582 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server. 2019-05-14 21:43:53,618 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0018: Host default-host starting 2019-05-14 21:43:53,670 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] 2019-05-14 21:43:53,675 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:/jlawyerdb] 2019-05-14 21:43:53,755 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 2019-05-14 21:43:53,777 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-7) WFLYIIOP0009: CORBA ORB Service started 2019-05-14 21:43:53,933 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Program Files\j-lawyer-server\wildfly-9.0.2.Final\standalone\deployments 2019-05-14 21:43:53,964 WARN [org.jboss.as.messaging] (MSC service thread 1-5) WFLYMSG0001: AIO wasn't located on this platform, it will fall back to using pure Java NIO. 2019-05-14 21:43:54,090 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\Program Files\j-lawyer-server\wildfly-9.0.2.Final\standalone\data\messagingjournal,bindingsDirectory=C:\Program Files\j-lawyer-server\wildfly-9.0.2.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\Program Files\j-lawyer-server\wildfly-9.0.2.Final\standalone\data\messaginglargemessages,pagingDirectory=C:\Program Files\j-lawyer-server\wildfly-9.0.2.Final\standalone\data\messagingpaging) 2019-05-14 21:43:54,092 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock 2019-05-14 21:43:54,118 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221013: Using NIO Journal 2019-05-14 21:43:54,153 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE 2019-05-14 21:43:54,164 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP 2019-05-14 21:43:54,167 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP 2019-05-14 21:43:54,257 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock 2019-05-14 21:43:54,258 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock 2019-05-14 21:43:54,269 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final 2019-05-14 21:43:54,511 INFO [org.jboss.messaging] (MSC service thread 1-7) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor 2019-05-14 21:43:54,513 INFO [org.jboss.messaging] (MSC service thread 1-7) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor 2019-05-14 21:43:54,653 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live 2019-05-14 21:43:54,653 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [e7c4dd51-915e-11e5-aa8e-bf817050df39] 2019-05-14 21:43:54,657 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue 2019-05-14 21:43:54,701 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ 2019-05-14 21:43:54,704 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 66) HQ221003: trying to deploy queue jms.queue.searchIndexProcessorQueue 2019-05-14 21:43:54,706 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 69) HQ221003: trying to deploy queue jms.topic.systemMonitoringTopic 2019-05-14 21:43:55,002 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA 2019-05-14 21:43:55,022 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 71) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 2019-05-14 21:43:55,023 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 68) HQ221003: trying to deploy queue jms.topic.faxQueueTopic 2019-05-14 21:43:55,027 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 70) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory 2019-05-14 21:43:55,028 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 67) HQ221003: trying to deploy queue jms.topic.dirObserverTopic 2019-05-14 21:43:55,053 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started 2019-05-14 21:43:55,054 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra 2019-05-14 21:43:55,056 INFO [org.jboss.as.messaging] (MSC service thread 1-7) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory 2019-05-14 21:43:55,055 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] 2019-05-14 21:43:56,356 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management 2019-05-14 21:43:56,356 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 2019-05-14 21:43:56,357 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) started in 6236ms - Started 260 of 434 services (234 services are lazy, passive or on-demand)
Die letzten Log-Einträge des Client:
2019-05-14 21:52:13,231 INFO [org.jboss.ejb.client.remoting] EJBCLIENT000017: Received server version 2 and marshalling strategies [river] 2019-05-14 21:52:13,233 INFO [org.jboss.ejb.client.remoting] EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@60299586, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection@18866c6a,channel=jboss.ejb,nodename=eberhard-hp]} on channel Channel ID d6634591 (outbound) of Remoting connection 05530d25 to localhost/127.0.0.1:8080 2019-05-14 21:52:13,237 ERROR [com.jdimension.jlawyer.client.LoginDialog] Error connecting to server java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:j-lawyer-server, moduleName:j-lawyer-server-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@54f834b9 at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:774) at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116) at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146) at com.sun.proxy.$Proxy2.login(Unknown Source) at com.jdimension.jlawyer.client.LoginDialog.cmdLoginActionPerformed(LoginDialog.java:473) at com.jdimension.jlawyer.client.LoginDialog.access$300(LoginDialog.java:38) at com.jdimension.jlawyer.client.LoginDialog$3.actionPerformed(LoginDialog.java:165) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEventImpl(Unknown Source) at java.awt.EventQueue.access$500(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue$4.run(Unknown Source) at java.awt.EventQueue$4.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source)
14. Mai 2019 um 22:13 #2845j-lawyer.orgAdministratorVielen Dank für die Logs. Kann ich bitte das komplette server.log an die Mailadresse im Impressum geschickt bekommen?
Und: falls Sie noch am PC sitzen, kann ich gern direkt per Fernwartung helfen.
Beste Grüße
Jens
(j-lawyer.org14. Mai 2019 um 23:06 #2846j-lawyer.orgAdministratorKommentar für potentielle Mitleser / zu Dokumentationszwecken:
Der Server hat – augenscheinlich in Folge eines „Hängers“ oder eines Absturzes – sich nicht mehr vollständig gestartet. Das Problem kann behoben werden, indem das Änderungsdatum der Datei
j-lawyer-server.ear
im Installationsverzeichnis des Servers aktualisiert wird, bspw. über die Eingabeaufforderung (im entsprechenden Verzeichnis):
copy /b j-lawyer-server.ear +,,
Jens
(j-lawyer.org)9. Januar 2023 um 12:41 #5239VeraendertTeilnehmersorry
-
AutorBeiträge
- Du musst angemeldet sein, um zu diesem Thema eine Antwort verfassen zu können.