Assembly Gallery
User login
Navigation
Cape Clear Server 7.0.3 Release Notes
Fixed Issues in Cape Clear Server 7.0.3
The following table lists the issues fixed in Cape Clear Server 7.0.3:
| Issue Summary: | JBoss JMS connection lost |
| ID: | SVR-2440 |
| Component: | Transports - JMS |
| Description: | Cape Clear fails to re-establish connections when JBoss goes down. |
| Issue Summary: | BPEL Process hangs during wait activity |
| ID: | SVR-248 |
| Component: | Administration - Orchestration Manager |
| Description: | Timer events created within a looped wait activity lead to multiple concurrent timer events for the same wait activity. |
| Issue Summary: | Cannot create a simple Generic JMS server transport that does not name ContextFactory |
| ID: | SVR-2490 |
| Component: | Transports - JMS |
| Description: | It is not possible to create a basic JMS server transport without specifying a ContextFactory. |
Known Issues in Cape Clear Server 7.0.3
The following table lists the known issues in Cape Clear Server 7.0.3:
| Issue Summary: | Increased PermGen Size Required for WebLogic |
| ID: | SVR-2437 |
| Component: | Integrations - WebLogic |
| Description: | When running Cape Clear Server deployed within WebLogic, a "java.lang.OutOfMemoryError: PermGen space" failure may occur. To ensure that the JVM permanent generation space will not be exhausted, configure a JVM startup parameter of -XX:MaxPermSize=512m in the WebLogic $CAPECLEAR_DOMAIN_HOME/bin/setDomainEnv.cmd file (for Windows) or $CAPECLEAR_DOMAIN_HOME/bin/setDomainEnv.sh (for UNIX platforms). |
| Issue Summary: | "java.lang.OutOfMemoryError: PermGen space failure" when editing Orchestration manager web.xml |
| ID: | SVR-2171 |
| Component: | Administration - Orchestration Manager |
| Description: | Editing the Orchestration Manager web.xml file for a running server will lead to a redeployment of the Orchestration manager web application. That redeployment may lead to a "java.lang.OutOfMemoryError: PermGen space failure"
The most common cause for that error is that you simply don't have enough space to load up all your classes. Use the param '-XX:MaxPermSize=128m' to increase the memory available. |
| Issue Summary: | Routes in a comma separated list of routes in a clustered route cannot have spaces after commas |
| ID: | SVR-2194 |
| Component: | Administration - Manager |
| Description: | When adding a route to the name.of.routes setting, you cannot use comma after the names. For example, if you created two HTTP routes named testroute1, testroute2 and then tried to create a cluster route whose setting for name.of.routes is"testroute1, testroute2" fails while "testroute1,testroute2" works. You need to strip whitespace after the comma. |
| Issue Summary: | The Adapters Template page in Cape Clear Manager displays JMS adapter templates, which are Retired Features |
| ID: | SVR-2239 |
| Component: | Administration - Manager |
| Description: | The Adapters Template page in Cape Clear Manager displays JMS adapter templates, which are Retired Features. The following items should be removed from the Cape Clear Manager JSPs:
* JMS JBossJMS@localhost JMS provider JBoss 4.0 JBoss 4.0 channel configuration |
| Issue Summary: | BPEL timer events should deal in UTC (Zulu time) to avoid daylight savings switch over issues |
| ID: | SVR-2269 |
| Component: | Documentation - Release Notes - Issues Outstanding |
| Description: | There is a bug in the way we handle duration based alarms and waits that start before the switch over time for daylight savings and that expire afterwards. Currently these calculations are done using local time and disregard the time changeover. Deadline based alarms and waits are not affected by this issue. Example: When clocks go forward 1 hour, we will expire alarms and waits up to 1 hour too early. When clocks go back 1 hour, we will expire them up to 1 hour too late. |
| Issue Summary: | Supercede recovery policy |
| ID: | SVR-2115 |
| Component: | Runtime -BPEL Runtime |
| Description: | The observed behavior for the BPEL 'supercede' recovery policy for BPEL process instances on standalone servers is currently equivalent to the 'no-recover' setting. Setting a supercede value will not achieve the desired effect. |
| Issue Summary: | Faults returned to JMS transport are discarded if jms.drop.noreplyto is set to true |
| ID: | SVR-2005 |
| Component: | Transports - JMS |
| Description: | If an exception occurs during the processing of a request message, the JMS transport will silently drop the returned Fault if JMSReplyTo is not set and if the jms.drop.noreplyto configuration property is set to true in the app descriptor. |
Subscribe to Feeds
Developer News
Forums
Blogs
Search
Active forum topics
