[Logo] Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
[Expert]
Messages posted by: achhabra  XML
Profile for achhabra -> Messages posted by achhabra [9]
Author Message
Current version of Terracotta products enable machines in a cluster to fail-over by making sure that the state in the failed machine is not lost. With the current products, if the machines are across a WAN the performance of the cluster will be greatly reduced.

We hope to have a solution that will allow you to cluster across a WAN sometime in 2007.

Arvind
Field Engineer
Terracotta, Inc.
Hi Sachin,

You could treat the Terracotta jar files the same way you treat the jar files that are part of your application server (Tomcat, Weblogic etc.) because Terracotta is really part of your runtime environment and not your development environment.

Hope that helps.

Arvind
Field Engineer
Terracotta Inc.
Hi Sachin,

1. Can you give some more details what you are trying to do with Maven? You do not have to compile your code with Terracotta jar files. Terracotta jar files are only used at runtime.

2. All the jar files in the lib folder are needed to run Terracotta client. This folder is specified using the "-Dtc.lib" argument. They are not needed in the classpath. All this is done automatically if you replace "java" with "dso-java". If you want to modify an existing script the command line would be something like:

java -Xbootclasspath/p:"c:\tc\lib\dso-boot\dso-boot-hotspot_win32_150.jar" -Dtc.lib="c:\tc\lib" -Dtc.config="tc-config.xml" -classpath [YourClassPath] [YourMainClass]

3. The boot jar files are platform specific.

Arvind
Field Engineer
Terracotta
Hi Vidar,

The <instrumented-classes><exclude> tag is only for performance enhancement. This tells the DSO that the excluded classes are not part of the shared object graph so DSO should not instrument those classes. If you do not want a particular object to be part of the object graph, you have to use the <transient-fields> tag or <honor-transient> tag. Please see the product guide for more details on these tags.

Looking at the stack trace, it seems that the unshareable object is not stored in any field. It is being "put" in a HashMap so you may not be able to use any of the above methods to exclude this unshareable class. If that is indeed the case, your only choices are either to change the source code or change the app server options (if possible) so that this code is not executed. If instead of extending the java.util.Stack you had a class that encapsulated a java.util.Stack object, Terracotta DSO would allow you to add that object to the shared object graph.

Arvind
Field Engineer
Terracotta, Inc.
Hi Sachin,

We have not tested Terracotta products on Ubuntu Linux. If the same configuration file works on Windows but not on Ubuntu Linux, you can assume that Terracotta DSO does not work on Ubuntu Linux.

Arvind
Field Engineer
Terracotta, Inc.
Hi Vidar,

This error can be avoided by configuring Terracotta DSO / Terracotta Sessions so that the object referenced by the field is not shared. To do that modify the configuration file and specify com.bea.wlw.netui.pageflow.FlowController._transientActionServlet in the <application><dso><transient-fields><field-name> tag.

You can find more details about this tag in the DSO product guide.

Arvind
Field Engineer
Terracotta, Inc.
Hi Sachin,

JDK 1.6 is currently not supported. We are just beginning to test using JDK 1.6. The good news is that it does not take long to test and certify a JDK version.

Arvind
Field Engineer
Terracotta, Inc.
Hi Sachin,

It seems from the exception that Enum is not supported in the current version of DSO. I have forwarded the request to our Engineering team and they are looking into it.

In case Enum is currently not supported, it should be fairly easy to add support for Enum objects in next release of DSO.

Arvind
Field Engineer
Terracotta, Inc.
Hi Sachin,

Our engineering team looked at the code and did not find any reference to the ourIsSQL attribute. Are you pre-processing / instrumenting the TCMessageType class with some other library? Maybe that library is adding the ourIsSQL attribute and there is some conflict.

It would help a lot if you could tell us more about your environment. If you do not want to share this information in a public forum, please send a message to sales@terracottatech.com

Arvind
Field Engineer
Terracotta, Inc.
 
Profile for achhabra -> Messages posted by achhabra [9]
Go to:   
Powered by JForum 2.1.7 © JForum Team