In case you want to support the openCRX project, please continue on our community page - if you are looking for support from us, please read on here:
Free support from the openCRX Community
There are various forums where you can post your
questions and get answers to your questions related to openCRX in a timely
fashion. We encourage
you to make use of this great and absolutely free resource. We do ask you to keep in mind, however, that the openCRX community operates on a "best effort" basis, i.e. the openCRX community has no contractual obligation to offer support, let alone free support.
Please note
that we can only help you track down problems if you provide us with
the relevant parts of the openCRX log file (located in the directory ...\jboss-3.2.5\server\default\log and
named openCRX.shared.<currentDate>.log if
you use the openCRX JBoss edition). Providing the console output only is not sufficient! If you get "strange" errors try to stop your application server and delete all the temporary files (with JBoss, delete all the files in the tmp and work directories). The following approch should get you
a useful log file:
set LogLevel = warning in server.log.properties (alternatively, use the Log Administration Console to change the LogLevel on-the-fly)
shutdown and restart JBoss
login and do what it takes to get ready to cause the error, but do
NOT cause the error just yet
(NOTE: the application will be considerable slower as before because of the trace level)
clear the openCRX log file (named openCRX.shared.<currentDate>.log)
to get rid of all the information that we don't need; open the file with a
text editor, clear the contents, and save the empty file again (note that deleting
the file usually does not work because the file is locked...)
now it is time to cause the error (i.e. click that button that will cause the error...)
open a new Support Request or submit a bug on sourceforge and upload the resulting openCRX
log file together with a short description of what you did to cause the error
we will look at the issue and post a reply at our earliest convenience
Paid support from openCRX affiliates
We also unify developers, contributors and affiliates to offer
you support at a professional level for openCRX with a guaranteed quality of service.
Tell
us what your problem is and we will route your
request
to the entity best suited to help you solve your problem. You can choose
from various support
levels tailored to your needs in terms of availability of support and required
response time:
If none of the offerings listed in the table above suits you, please
and tell
us what your requirements are. We will try to find a solution for you. In addition
to production support we also offer Development Support
and Consulting.
20 hours of support, e-mail only, business hours,
48 hours target response time
More Information
If you have proprietary feature requests or need new features by a specified date, please
or CRIXP Corp. directly. The following chart gives a high-level overview of where you can place feature requests and how new features eventually end up in a new openCRX release: