Posts tagged app server

Content Services: WebSphere stops responding when many concurrent threads are running

Samartha Vashishtha 

When the storeContent operation for Content Services 9 is invoked with more than 30 threads, the WebSphere application server may stop responding.

Follow these steps to resolve the issue:

  1. In WebSphere Administrative Console, click Servers > Server Types > WebSphere application servers and then click a server name.
  2. In the right pane, click Thread pools under Additional Properties.
  3. Click WebContainer and, on the Configuration page, increase the value of the Maximum Size field by double the number of threads that you need to run. For example, increase the value of the Maximum Size field by 80 if you want to run 40 threads.
  4. Click Apply or OK.
  5. Click Save directly to the master configuration.
  6. Restart the WebSphere application server.

——-
Original article at http://blogs.adobe.com/livecycledocs/2011/02/content-services-websphere-stops-responding-when-many-concurrent-threads-are-running.html.

Setting up JBoss to auto reconnect after database outage

Darren Melanson

If you had a database outage or failure while JBoss was up, you’re likely in a situation where you would have to restart JBoss because the database connections didn’t get reconnected for you. You’re likely also faced with a massive set of log files due to the data source complaining about it not being able to connect to the database.

If you want JBoss to automatically reconnect the data source pool(s) for you, here’s some settings to use (only valid if using a “local-tx-datasource”):

1) <autoReconnect>true</autoReconnect>
2) <check-valid-connection-sql>an efficient select statement</check-valid-connection-sql>
3) <failOverReadOnly>false</failOverReadOnly>
4) <maxReconnects>50</maxReconnects>
5) <initialTimeout>15</initialTimeout>

In the above settings, if the data source connectivity is lost (database down or network failure) – then JBoss will automatically attempt to reconnect 50 times every 15 seconds. You can obviously set those numbers to values suitable to your environment. It’s also important to set the failOverReadOnly flag to false as it ensures that recovered connections are writable.

Additionally, some people prefer to include a valid and efficient SQL statement in the “check-valid-connection”, it’s completely optional but a good practice in environments where stale connections are common. Optionally, there’s also “new-connection-sql” which will check on newly created connections.

——-
Original article at http://blogs.adobe.com/livecycle/2011/03/setting-up-jboss-to-auto-reconnect-after-database-outage.html.

Go to Top