Instant Team Sessions Server Beta

ITPlaceManager.jar · 3.11-dev · build 7883 · Published October 12, 2026

Download JAR SHA-256 checksum Companion logging profile

Release notes

Quieter logging: Normal is the default. Routine diagnostics move to Debug or Trace; errors and exception stacks remain visible.
Service health: compact summaries report Sametime, database reads, place services, PlaceLogger capture state and the room-monitor loop.
Room and queue visibility: identified, assigned, monitored, entered and pending rooms, capture-enabled counts, successful saved records, queues and heap usage.
Build identity: each application log file receives a version, build identity and actual UTC build timestamp header, including after rotation.
Exception containment: ordinary callback and timer failures retain context and stacks; startup failures return nonzero exit codes.
Workers and shutdown: stopped workers are removed from pool bookkeeping, configured capacity is restored, and shutdown continues cleanup after ordinary failures.

Hosted build 7883 passed five offline server regression suites and QA scenario checks. Recorded development tests passed peer delivery and exactly-once capture after readiness. Synthetic Tanuki tests passed start, stop and recovery; they do not prove live shutdown, queue draining, reboot or installer behavior in your environment.

Source revision: 3dc21e17c937b3eadca03cb83281374ff9c5baf0. Built October 11, 2026 at 21:04:56 UTC. The preserved application version is 3.11-dev, not a new stable release.

Replace the application JAR

Use an isolated instance with a dedicated PlaceLogger account and test database. Do not run a second logger for the same assigned rooms.
Review the wrapper/launcher classpath and working directory. Confirm which ITPlaceManager.jar is loaded and that Java, native Notes libraries, Sametime libraries and Tanuki are compatible and licensed. Hosted tests used Java 8.
Stop the service and confirm its JVM has exited. Back up the current JAR, wrapper configuration, application properties and logging configuration. Retain the old JAR outside any wildcard classpath.
Verify the downloaded SHA-256 checksum, then replace only the identified application file with ITPlaceManager.jar. Preserve service-account permissions. Do not replace vendor libraries, license files, Notes IDs, credentials or databases.
Review the logging requirements below before using the companion log4j.xml. The JAR alone does not replace your existing profile.
Start using the existing launcher. Confirm the build header identifies build 7883, then wait for healthy services and all assigned rooms entered with capture enabled before sending traffic.
Send a small multi-user conversation. Verify peer receipt and exactly-once capture, then test graceful stop, restart and recovery in the isolated instance.

Logging configuration and runtime requirements

The companion profile creates logs/its-server.log and logs/its-diagnostics.log relative to the server working directory, with 10 MB rotation and three backups. Ensure the service account can write there. Review paths and appenders before adopting it; keep a backup of the customer profile.

Set the JVM property -Dits.logging.mode=Normal, or choose ErrorsOnly, Important, Debug or Trace. For Tanuki, use an unused wrapper.java.additional.N index. Restart to change modes. Debug/Trace may contain sensitive diagnostic data.

Logging dependency check: hosted tests used Log4j 1.2.15 APIs and XML configuration. The new rolling appender and header layout depend on that API. Existing Log4j 2 bridge configurations must be qualified separately. Do not downgrade a maintained runtime or disable security protections to load this beta. Log4j 1.x is obsolete; logging-runtime remediation remains a release gate for broader deployment.

READ_OK proves a database read, not a write. Check successful saved-record counts and actual database capture separately. Exception containment does not guarantee recovery from native crashes or JVM errors.

Sample improved logs

No customer messages, credentials or live operational logs are published. The Normal example is a synthetic illustration of aligned columns and five-minute health summaries. The error example is an actual excerpt from build 7883's offline regression, using a deliberately injected fixture failure to show the retained stack trace.

# ITS Server | version=3.11-dev | build=azure.7883.3dc21e17c937b3eadca03cb83281374ff9c5baf0 | builtAt=2026-10-11T21:04:56Z (UTC)
2026-10-12 09:00:00.000 | INFO | ITPlaceManagerMonitor | PlaceManagerMonitorThread | Services | sametime=CONNECTED | database=READ_OK | placeService=AVAILABLE | placeLogger=ACTIVE | roomMonitor=RUNNING | account=PlaceLoggerDemo
2026-10-12 09:00:00.001 | INFO | ITPlaceManagerMonitor | PlaceManagerMonitorThread | Rooms | identified=12 | assigned=12 | monitored=12 | entered=12 | pending=0 | captureEnabled=12 | savedRecords=60 | dbQueue=0 | archiveQueue=0 | retrieveQueue=0

Normal-mode log example · Error-visibility example

Rollback and feedback

If startup, capture or shutdown fails, stop the test service, confirm the JVM has exited, restore the old JAR and any changed logging/wrapper files, and restart. Preserve failure logs privately. Check capture readiness before resuming traffic.

Send feedback to support@instant-tech.com with build 7883, runtime versions, reproduction steps and sanitized logs. Remove credentials, Notes ID material and sensitive room content.