I used liferay-session-overrid.js and, when the user is not active, I do AuthenticatedSessionManagerUtil.logout (httpRequest, httpResponse)
But sometimes such an error with not found session is reproduced
Can i fix this problem?
This is rarely done, but remains a problem.
The error appears when I try to do on the filter request.getSession()
2019-12-11 20:29:32.704 INFO [default task-7][PreLogoutAction:19] PreLogoutAction was executed!
2019-12-11 20:29:32.705 INFO [default task-7][PreLogoutAction:20] User is empty
2019-12-11 20:29:32.773 INFO [default task-23][PreLogoutAction:19] PreLogoutAction was executed!
2019-12-11 20:29:32.779 INFO [default task-23][PreLogoutAction:20] User is empty
2019-12-11 20:29:32.840 ERROR [default task-14][VirtualHostFilter:375] javax.servlet.ServletException: Unable to execute request
javax.servlet.ServletException: Unable to execute request
at com.liferay.portal.monitoring.internal.servlet.filter.MonitoringFilter.processFilter(MonitoringFilter.java:204)
2019-12-11 20:29:32.844 ERROR [default task-14][RestoringCartFilter:62] java.lang.IllegalStateException: UT000010: Session not found ojlT9glxtyQEXskve3QxttVXcsVbrkI86VojtnBc
java.lang.IllegalStateException: UT000010: Session not found ojlT9glxtyQEXskve3QxttVXcsVbrkI86VojtnBc
at io.undertow.server.session.InMemorySessionManager$SessionImpl.getAttribute(InMem
You can not control that. There is always a possibility that a session does not exists on the server. It could be because your script was too late or because the session was removed in some other way you didn't detect. You'd have to account for that possibility and deal with the error on the frontend side.
Related
I'm fully aware that wildfly 25 has dropped legacy security realms.
So I tried to move from wildfly 20.0.1 to wildfly 25.0.1.
According to the quickstart ee-security, I did
/subsystem=elytron/policy=jacc:add(jacc-policy={})
I also I had to remove in my jboss-web.xml the value :
<security-domain>jaspitest</security-domain>
Otherwise I do get :
{
"WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.jaspitest"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.deployment.unit.\"unite_compte.war\".component.SocieteGestionSIXDAOImpl.CREATE is missing [jboss.security.security-domain.jaspitest]",
I also have my own IdentityStore.
When I try to access the site, the login page appears as expected. When I submit the credentials my IdentityStore is called and the validate(Credential) method returns a valid CredentialValidationResult.
Unfortunately, I do get an Exception :
17:05:14,710 WARNING [javax.enterprise.resource.webcontainer.jsf.lifecycle] (default task-3) #{loginView.submit}: java.lang.IllegalStateException: java.io.IOException: java.io.IOException: ELY01177: Authorization failed.: javax.faces.FacesException: #{loginView.submit}: java.lang.IllegalStateException: java.io.IOException: java.io.IOException: ELY01177: Authorization failed.
Caused by: java.io.IOException: ELY01177: Authorization failed.
at org.wildfly.security.jakarta.authentication#1.17.1.Final//org.wildfly.security.auth.jaspi.impl.JaspiAuthenticationContext$1.handleOne(JaspiAuthenticationContext.java:188)
at org.wildfly.security.jakarta.authentication#1.17.1.Final//org.wildfly.security.auth.jaspi.impl.JaspiAuthenticationContext$1.lambda$handle$0(JaspiAuthenticationContext.java:100)
at org.wildfly.security.jakarta.authentication#1.17.1.Final//org.wildfly.security.auth.jaspi.impl.SecurityActions.doPrivileged(SecurityActions.java:39)
at org.wildfly.security.jakarta.authentication#1.17.1.Final//org.wildfly.security.auth.jaspi.impl.JaspiAuthenticationContext$1.handle(JaspiAuthenticationContext.java:99)
What shall I do to make it work ?
As the quickstart says, you have to update the Wildlfy configuration as well. Specifically, you have to run the configure-elytron.cli script of the quickstart
More info: https://github.com/wildfly/quickstart/tree/main/ee-security#configure-the-server
I am trying to submit a code review request using CodeCollaborator client v7.2.7237 (server version is same too) but fails with the following error call stack –
com.smartbear.ccollab.datamodel.DataModelException: org.apache.xmlrpc.XmlRpcException: I/O error while communicating with HTTP server: Read timed out
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation$2.invoke(XmlRpcClientEngineImplementation.java:355)
at com.sun.proxy.$Proxy63.loadById(Unknown Source)
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation.loadById(XmlRpcClientEngineImplementation.java:441)
at com.smartbear.ccollab.datamodel.Engine$DataObjectCache.loadObjectById(Engine.java:6691)
at com.smartbear.ccollab.datamodel.Engine.loadById(Engine.java:537)
at com.smartbear.ccollab.datamodel.Engine.loadEngineObjectById(Engine.java:564)
at com.smartbear.ccollab.datamodel.Engine.versionCreate(Engine.java:5913)
at com.smartbear.ccollab.datamodel.Scm.uploadScmVersion(Scm.java:629)
at com.smartbear.ccollab.datamodel.Scm.uploadChangeset(Scm.java:448)
at com.smartbear.ccollab.datamodel.Scm.uploadChangeset(Scm.java:392)
at com.smartbear.ccollab.datamodel.Scm.uploadChangelist(Scm.java:291)
at com.smartbear.ccollab.client.commands.AbstractAddChangelistCommand.execute(AbstractAddChangelistCommand.java:139)
at com.smartbear.ccollab.client.commands.admin.review.AbstractReviewCommand.execute(AbstractReviewCommand.java:125)
at com.smartbear.ccollab.client.commands.Command.validateAndExecute(Command.java:345)
at com.smartbear.ccollab.client.commands.Command.validateAndExecute(Command.java:419)
at com.smartbear.collaborator.Collaborator.execute(Collaborator.java:160)
at com.smartbear.collaborator.jobs.AddToReviewJob.processChanges(AddToReviewJob.java:158)
at com.smartbear.collaborator.jobs.AddToReviewJob.run(AddToReviewJob.java:103)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.apache.xmlrpc.XmlRpcException: I/O error while communicating with HTTP server: Read timed out
at org.apache.xmlrpc.client.XmlRpcCommonsTransport.writeRequest(XmlRpcCommonsTransport.java:252)
at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:151)
at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:115)
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientFactory$XmlRpcCommonsTransport2.sendRequest(XmlRpcClientFactory.java:75)
at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:158)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:147)
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation$2.invoke(XmlRpcClientEngineImplementation.java:256)
... 18 more
I have no problems accessing Perforce or CodeCollaborator from the machine when I get this error. I tried to submit using CodeCollaborator plugin in P4V (P4V/NTX64/2019.1/1797168) but got the same error message. I tried JRE 1.6, 1.7 but got the same error.
When I login to my CodeCollaborator account, I see that review request is being created but it is failing to add the source files to the review. My colleagues with the same CodeCollaborator, P4 versions are successfully able to submit the review requests. Checked this thread on CodeCollaborator forum who had reported similar issue but there was no solution to try. Any suggestions on how to troubleshoot ? Thanks.
According to documentation when trial is expired and user opens the app, a message would be shown. But my app closes after showing splash screen without any message in this case.
There is the same question on the Microsoft's forum, but I can't write anything there (it returns me unexpected error when I try to submit my question) and there is no answer.
I get the following line in my event log:
App failed with error: No applicable app licenses found. See the Microsoft-Windows-Twin/Operational log for additional information.
Additional information:
< Data Name="ErrorCode" >-1058406399< /Data >
This is Microsoft's bug and they promise to fix it. You can get more details on the msdn-forum.
I am using Spring to configure a (lazy loaded) Hazelcast Client that connects to a 2 member cluster.
<hz:client id="hazelcast" lazy-init="true">
<hz:group name="${HzName}" password="${HzPassword}"/>
<hz:properties>
<hz:property name="hazelcast.client.connection.timeout">10000</hz:property>
<hz:property name="hazelcast.client.retry.count">600</hz:property>
<hz:property name="hazelcast.jmx">true</hz:property>
<hz:property name="hazelcast.logging.type">slf4j</hz:property>
</hz:properties>
<hz:network smart-routing="true" redo-operation="true" connection-attempt-period="5000"
connection-attempt-limit="2">
<hz:member>${HzMember1}</hz:member>
<hz:member>${HzMember2}</hz:member>
</hz:network>
</hz:client>
My issue is:
If, at the time of my application starting, BOTH of the cluster members happen to be unavailable then I am seeing ClusterListenerThread throwing a SEVERE exception:
WARNING: Unable to get alive cluster connection, try in 4945 ms later, attempt 1 of 2.
16-Apr-2015 14:57:34 com.hazelcast.client.spi.impl.ClusterListenerThread
WARNING: Unable to get alive cluster connection, try in 4987 ms later, attempt 2 of 2.
16-Apr-2015 14:57:39 com.hazelcast.client.spi.impl.ClusterListenerThread
SEVERE: Error while connecting to cluster!
java.lang.IllegalStateException: Unable to connect to any address in the config!
at com.hazelcast.client.spi.impl.ClusterListenerThread.connectToOne(ClusterListenerThread.java:273)
at com.hazelcast.client.spi.impl.ClusterListenerThread.run(ClusterListenerThread.java:79)
Caused by: com.hazelcast.spi.exception.RetryableIOException: java.util.concurrent.ExecutionException: com.hazelcast.core.HazelcastException: java.net.ConnectException: Connection refused
at com.hazelcast.client.connection.nio.ClientConnectionManagerImpl$OwnerConnectionFuture.createNew(ClientConnectionManagerImpl.java:649)
at com.hazelcast.client.connection.nio.ClientConnectionManagerImpl$OwnerConnectionFuture.access$300(ClientConnectionManagerImpl.java:605)
at com.hazelcast.client.connection.nio.ClientConnectionManagerImpl.ownerConnection(ClientConnectionManagerImpl.java:268)
at com.hazelcast.client.spi.impl.ClusterListenerThread.connectToOne(ClusterListenerThread.java:245)
...which subsequently results in my Hazelcast Client bean not being instantiated and therefore everything downstream that relies upon it's existence blowing up as well.
SEVERE: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hazelcast': Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public static com.hazelcast.core.HazelcastInstance com.hazelcast.client.HazelcastClient.newHazelcastClient(com.hazelcast.client.config.ClientConfig)] threw exception; nested exception is java.lang.IllegalStateException: Cannot get initial partitions!
How can I detect and handle the error being thrown by ClusterListenerThread during the instantiation (by Spring) of my Hazelcast Client bean?
nb. I'm frustrated by the fact that the Client bean is not being constructed (despite there being no available members) because I know for a fact that an already constructed Client can handle having all of it's member's become unavailable and will happily start working again when one or more of those members become available again.
What you need to do is configure connectionAttemptLimit and connectionAttemptPeriod.
If you set connectionAttemptLimit to INT_MAX and pick a reasonable connectiontAttemptPeriod, the client will practically try to connect to given memberlist forever every X seconds. This is currently more like a workaround, because when you first open HazelcastClient it will block until one of the members become available. A further workaround, you can try to open the client in another dedicated thread.
About making a fully supported feature, there was a discussion going on by the hazelcast team here.
https://github.com/hazelcast/hazelcast/issues/552
I am adding a question as a reference to the issue.
I am using the Flash in my application and when I restart my tomcat I get the following Error resulting in disabled flash.
Jul 23, 2013 11:20:29 AM com.sun.faces.context.flash.ELFlash$PreviousNextFlashInfoManager decode
SEVERE: JSF1094: Could not decode flash data from incoming cookie value ??o?/tv?
. Processing will continue, but the flash is unavailable for this request.
The workaround to this is to clear my cookies or wait until the cookie expires with the session. Is there a way that I can invalidate this? Should I invalidate the session altogether?
This has been raised as a bug:
https://java.net/jira/browse/JAVASERVERFACES-2862