Adobe Experience Manager Sites & More

akashdeepAEM · 7/14/17

Hi,

In Adobe CQ5.6.1, we have a service which makes a get request using HttpClients to consume external API response,

for which had a timeout set for 3sec

HttpClient httpClient = new HttpClient();

HttpClientParams clientParams = httpClient.getParams();

// Cause timeout if connection not established within [timeout/1000] seconds

clientParams.setConnectionManagerTimeout(timeout);

clientParams.setSoTimeout(timeout);

getMethod = new GetMethod(url);

getMethod.addRequestHeader("Content-type", "application/json");

getMethod.addRequestHeader("Accept", "application/json");

getMethod.addRequestHeader("ID", uuid);

getMethod.addRequestHeader("user", APIUser);

getMethod.addRequestHeader("password", APIPassword);

getMethod.addRequestHeader("token", APIToken);

int statusCode = httpClient.executeMethod(getMethod);

but since we were unable to get response from the called service and were getting a read socket timeout exception:

Caused by: java.net.SocketTimeoutException: Read timed out

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(SocketInputStream.java:152)

at java.net.SocketInputStream.read(SocketInputStream.java:122)

at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)

at java.io.BufferedInputStream.read(BufferedInputStream.java:254)

at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)

at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)

at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)

at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)

at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)

at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)

at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)

at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)

at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)

at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)

Therefore, we tried increasing the timeout value to 100sec which later resulted in the Tar error as mentioned below.

The read timeout error is now replaced with this new Tar Error.

It would be great to have suggestions to proceed with it. Is it something to do on the configurations on Tar side.

*ERROR* [pool-6-thread-5] com.day.crx.persistence.tar.TarJournal Can not append java.io.IOException: Last transaction not committed or rolled back

at com.day.crx.persistence.tar.TarSet.startTransaction(TarSet.java:925)

at com.day.crx.persistence.tar.ClusterTarSet.startTransaction(ClusterTarSet.java:1434)

at com.day.crx.persistence.tar.TarJournal.append(TarJournal.java:251)

at org.apache.jackrabbit.core.journal.AppendRecord.update(AppendRecord.java:266)

at org.apache.jackrabbit.core.cluster.ClusterNode$WorkspaceUpdateChannel.updateCommitted(ClusterNode.java:700)

at org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(SharedItemStateManager.java:845)

at org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedItemStateManager.java:1537)

at org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java:400)

at org.apache.jackrabbit.core.state.XAItemStateManager.update(XAItemStateManager.java:354)

at org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java:375)

at org.apache.jackrabbit.core.state.SessionItemStateManager.update(SessionItemStateManager.java:275)

at org.apache.jackrabbit.core.ItemSaveOperation.perform(ItemSaveOperation.java:258)

at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)

at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)

at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:329)

at org.apache.jackrabbit.core.session.SessionSaveOperation.perform(SessionSaveOperation.java:65)

at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)

at org.apache.jackrabbit.core.SessionImpl.perform(SessionImpl.java:361)

at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:812)

at com.day.crx.core.CRXSessionImpl.save(CRXSessionImpl.java:142)

at org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.commit(JcrResourceProvider.java:511)

at org.apache.sling.resourceresolver.impl.helper.ResourceResolverContext.commit(ResourceResolverContext.java:148)

at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.commit(ResourceResolverImpl.java:1090)

at org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.issueClusterLocalHeartbeat(HeartbeatHandler.java:248)

at org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.issueHeartbeat(HeartbeatHandler.java:195)

at org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.run(HeartbeatHandler.java:150)

at org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:56)

at org.quartz.core.JobRunShell.run(JobRunShell.java:213)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:745)

13.07.2017 09:56:47.912 *ERROR* [pool-6-thread-5] org.apache.jackrabbit.core.cluster.ClusterNode Unable to commit log entry. org.apache.jackrabbit.core.journal.JournalException: Can not append

at com.day.crx.persistence.tar.TarJournal.logAndConvert(TarJournal.java:532)

at com.day.crx.persistence.tar.TarJournal.append(TarJournal.java:273)