Weblogic and xerces and xalan

I understand that xerces and xalan are a part of the weblogic's distribution.
Will BEA also upgrade to newer versions of these softwares as they are available?
If not how do I use newer versions of these softwares with weblogic.
This is becoming a critical issue for us as I already see a remarkable difference
in performance while doing transformations. The newer versions of xalan and xerces
are performing much better with the same xml and xsl documents as compared to
the previous versions.

According to that link your right it is not supported.
Have you tried adding the xerces jars at the beginning of the classpath?

Similar Messages

Weblogic 8.1 with Xalan 2.6.1 and Xerces 2.6.2 ?!?

Hi,
I'm trying to use Xalan 2.6.1 and Xerces 2.6.2 with Weblogic 8.1SP2, but no result yet...
I found docs on bea website:
http://edocs.bea.com/wls/docs81/pdf/faq.pdf
http://e-docs.bea.com/wls/docs81/xml/xml_admin.html
where I found this:
"Warning: In version 8.1 of WebLogic Server, you can plug in only the following versions of the Apache Xerces parser:
Xerces 2.2.0
Xerces 2.3.0
Xerces 2.4.0
In addition, you can plug in only those versions of the Apache Xalan transformer that are compatible with the preceding versions of the Apache Xerces parser."
I can't find any solution to this?
I tried various option:
- xercesImpl2.6 in the classpath variable
- xalan2.6.2 in the endorsed lib
- registered factory impl names in xml registry
- prefer web-inf set to true
Errors result in following exception:
- NoMethodFound (rhino classes inside weblogic.jar)
- ClassCast (xalan/xerces conflicts)
Any one has suggestions?
Regards
Leonardo

According to that link your right it is not supported.
Have you tried adding the xerces jars at the beginning of the classpath?

XALAN and XERCES on WL6

Hi!
I just can't get WLS6.0 to use new versions of XALAN and XERCES. I keep
getting errors that are obviously because Weblogic is loading an older
version of XALAN before my app ever gets loaded, and as a result I'm having
trouble with <xsl:param> and <xsl:variable> tags not being able to recognise
other params and variables in the top level scope. This is crucial to my
application but after a day of messing around with everything from
classpaths to startweblogic.cmd, I'm pretty much stuck.
Does ANYONE know how to fix this?
TIA,
Navneet

Hmm.. what's this I'm hearing about an XML registry for weblogic?
"Jeffrey Winter" <[email protected]> wrote in message
news:3ae702c5$[email protected]..
>
If you put the latest xerces.jar and xalan.jar file before anything elsein the
CLASSPATH in your startup command file it will work. I'm doing in rightnow with
Xerces 1.3.1 and Xalan 2.0.1.
If you're trying to use JAXP however, you'll have problems because WLalways returns
their own internal version of the DocumentBuilderFactory even if you putthe JAXP
1.1 jar file in the class path and specify theorg.apache.xerces.jaxp.DocumentBuilderFactory
in your registry.
We got around this by defining a stub subclass of DocumentBuilderFactoryand instantiating
is directly instead of through DocumentBuilderFactory.newInstance(). It'sa pain,
but after that you can get around using the older versions that they'vebaked
in.

Xmlparserv2.jar with xerces and xalan

Hello,
I have a Spring/Spring Web Flow application. I also have a separate web application that's using the XML Publisher API to generate reports from RTF files. I am now in the process of merging these two into one application.
The Spring app requires the xerces.jar and xalan.jar JARs in order to parse the various XML files required to configure Spring. The XML Publisher app requires the xmlparserv2.jar JAR in order to parse the XML required for generating reports.
When I have all of these JARs in my one web application, I receive an error when I call the FOProcessor.generate() method. Here it is:
oracle.xml.parser.v2.XMLParseException: Bad character (1).
 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:324)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:287)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:292)
 at oracle.xml.parser.v2.XSLProcessor.newXSLStylesheet(XSLProcessor.java:590)
 at oracle.xml.parser.v2.XSLStylesheet.<init>(XSLStylesheet.java:260)
 at oracle.apps.xdo.common.xml.XSLTClassic.transform(XSLTClassic.java:200)
 at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:174)
 at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1022)
 at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:968)
 at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:209)
 at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1561)
 at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:951)
I was thinking this was because there was a conflict between xalan, xerces and xmlparserv2, so I removed the xalan and xerces JARs from the classpath. Now I get the following whenever I try to hit one of my spring MVC actions:
DEBUG org.springframework.beans.factory.xml.DelegatingEntityResolver(99) - Attempting to resolve XML Schema [http://www.springframework.org/schema/beans/spring-beans-2.0.xsd] using [org.springframework.beans.factory.xml.PluggableSchemaResolver]
<Line 43, Column 57>: XML-24509: (Error) Duplicated definition for: 'identifiedType'
<Line 60, Column 28>: XML-24509: (Error) Duplicated definition for: 'beans'
<Line 145, Column 34>: XML-24509: (Error) Duplicated definition for: 'description'
<Line 158, Column 29>: XML-24509: (Error) Duplicated definition for: 'import'
<Line 180, Column 28>: XML-24509: (Error) Duplicated definition for: 'alias'
<Line 209, Column 33>: XML-24509: (Error) Duplicated definition for: 'beanElements'
<Line 223, Column 44>: XML-24509: (Error) Duplicated definition for: 'beanAttributes'
<Line 486, Column 43>: XML-24509: (Error) Duplicated definition for: 'meta'
<Line 494, Column 35>: XML-24509: (Error) Duplicated definition for: 'metaType'
<Line 511, Column 27>: XML-24509: (Error) Duplicated definition for: 'bean'
<Line 531, Column 38>: XML-24509: (Error) Duplicated definition for: 'constructor-arg'
<Line 600, Column 51>: XML-24509: (Error) Duplicated definition for: 'property'
<Line 611, Column 36>: XML-24509: (Error) Duplicated definition for: 'lookup-method'
<Line 647, Column 38>: XML-24509: (Error) Duplicated definition for: 'replaced-method'
<Line 684, Column 31>: XML-24509: (Error) Duplicated definition for: 'arg-type'
<Line 711, Column 26>: XML-24509: (Error) Duplicated definition for: 'ref'
<Line 749, Column 28>: XML-24509: (Error) Duplicated definition for: 'idref'
<Line 783, Column 28>: XML-24509: (Error) Duplicated definition for: 'value'
<Line 811, Column 27>: XML-24509: (Error) Duplicated definition for: 'null'
<Line 825, Column 39>: XML-24509: (Error) Duplicated definition for: 'collectionElements'
<Line 842, Column 48>: XML-24509: (Error) Duplicated definition for: 'list'
<Line 853, Column 47>: XML-24509: (Error) Duplicated definition for: 'set'
<Line 862, Column 41>: XML-24509: (Error) Duplicated definition for: 'map'
<Line 869, Column 45>: XML-24509: (Error) Duplicated definition for: 'entry'
<Line 877, Column 45>: XML-24509: (Error) Duplicated definition for: 'props'
<Line 886, Column 26>: XML-24509: (Error) Duplicated definition for: 'key'
<Line 897, Column 27>: XML-24509: (Error) Duplicated definition for: 'prop'
<Line 916, Column 39>: XML-24509: (Error) Duplicated definition for: 'propertyType'
<Line 960, Column 45>: XML-24509: (Error) Duplicated definition for: 'baseCollectionType'
<Line 971, Column 46>: XML-24509: (Error) Duplicated definition for: 'typedCollectionType'
<Line 987, Column 34>: XML-24509: (Error) Duplicated definition for: 'mapType'
<Line 1008, Column 36>: XML-24509: (Error) Duplicated definition for: 'entryType'
<Line 1047, Column 40>: XML-24509: (Error) Duplicated definition for: 'listOrSetType'
<Line 1056, Column 36>: XML-24509: (Error) Duplicated definition for: 'propsType'
<Line 1069, Column 45>: XML-24509: (Error) Duplicated definition for: 'defaultable-boolean'
ERROR org.springframework.web.servlet.FrameworkServlet(229) - Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Line 10 in XML document from class path resource [spring/servlet/sellitem-webflow-config.xml] is invalid; nested exception is oracle.xml.parser.schema.XSDException: Duplicated definition for: 'identifiedType'
Caused by:
oracle.xml.parser.schema.XSDException: Duplicated definition for: 'identifiedType'
 at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:431)
 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:290)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:287)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:181)
 at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:151)
 at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:77)
 at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:405)
 at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:357)
 at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
 at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:126)
 at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:142)
 at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:123)
 at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:91)
 at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:94)
 at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:294)
 at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
 at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:308)
 at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:252)
 at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:221)
 at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:115)
 at javax.servlet.GenericServlet.init(GenericServlet.java:211)
 at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
 at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:757)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:130)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
 at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
 at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
 at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
 at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
 at java.lang.Thread.run(Unknown Source)
So it seems like these JARs are incompatible with each other. Is there any way I can use the Oracle DocumentBuilder for my XML Publisher classes and the xerces for the rest of the app?
Thanks,
Leo Hart

Now one has any advice? :(

Xerces and Xalan in OC4j

I am using standalone OC4J 10.1.2.0.2 and would want to use Xerces and Xalan in place or Oracle XML parser. I did initialize the container using -Xbootclasspath flag of JRE. but when the application is brought up the transform activty still shows the oracle.xml.jaxp error messages. Our app is built to work with Xerces and Xalan.
Are there any tricks invovled to make Oc4J recognize these libraries and use them ? Thanks

I think you can work that within the orion-application.xml file:
<imported-shared-libraries>
 <remove-inherited name="oracle.xml"/>
 <import-shared-library name="xalan" />
 <import-shared-library name="xerces" />
</imported-shared-libraries>
Where you've defined shared-lib entries for the above.
Reference:
http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-swapxmlparser/doc/readme.html
I don't know if this is handled in the same way for the version you are dealing with, however.

Urgent: Xerces 1.4 .2 (and higher) and WLS 6.0

Hi,
We want to use the Apache Xerces 1.4.3 validation to .XML Schemas and we try to
integrate it in WLS 6.0. sp2
But we are ahving trouble to get the parser working.
I allready tried to explicitly stating to use the org.apache.xerces.framework.DocumentBuilderFactoryImpl
of apache ..... but then the program stops when asking for a DocumentBuilder.
anyone... knows how to get Xerces 1.4.1 (or higher) to be used in WLS6.0 sp2
Nico

I'm using Syslog, JAXP, Xerces 1.3.1, jdom-b7 with WL 6.0sp2 without
problems ( after getting a patch for Syslog )
Use the Xalan that comes with Xerces, not the independent download.
Put xerces.jar ahead of weblogic jars in the startup script
Setup the external registry.
config.xml:
<XMLRegistry
DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
Name="Apache XML registry"
SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl"/>
Set the external registry to be in use.
config.xml:
<Server ... XMLRegistry="Apache XML registry" ... >
If you are calling SaxBuilder() without specifying a class for the builder,
JAXP throws an error. Syslog has a bug which does that, and the patch will
be included in the next release. But if you use:
startup script:
java $JAVA_OPTIONS ...
-Djaxp.debug=true -Dweblogic.xml.debug=true -DSyslog.config.xml=config/gulch
/syslog_config.xml -DSyslog.xml.parser=org.apache.xerces.parsers.SAXParser
-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.Transfor
merFactoryImpl ...
weblogic.Server
com.protomatter.syslog.Syslog.java:
String parserClass = System.getProperty("Syslog.xml.parser");
SAXBuilder builder = null;
if (parserClass == null)
builder = new SAXBuilder();
else
builder = new SAXBuilder(parserClass);
It works.
"metin" <[email protected]> wrote in message
news:[email protected]...
>
Hi,
We had also smilar problem. I used JAXP and SAX 2 implementation withapache xerces
in our XML application. I was not able to to register this package inweblogic
console. Weblogic sets system property to default :
javax.xml.parsers.SAXParserFactory =weblogic.xml.jaxp.RegistrySAXParserFactory
>
It didn't recognize the XML registry definition and it didn't recognizethe system
property that I defined (even in the application).
In weblogic 5.1 we put in the classpath our JAXP jar file in fron of theweblogic.jar.
In weblogic 6.0 this did't work now I use SAX parser from xerces withoutJAXP
SAXParserFactory.
It seems like weblogic has older version of xerces and it does not allowto use
another package because of RegistrySaxParser.
I don't understand why there is no information in weblogic web sites, itseems
many people having these problems.
Good Luck and
best regards,
Metin Koc
"Nico De Groote" <[email protected]> wrote:
Hi,
We want to use the Apache Xerces 1.4.3 validation to .XML Schemas and
we try to
integrate it in WLS 6.0. sp2
But we are ahving trouble to get the parser working.
I allready tried to explicitly stating to use the
org.apache.xerces.framework.DocumentBuilderFactoryImpl
of apache ..... but then the program stops when asking for aDocumentBuilder.
>>
>>
anyone... knows how to get Xerces 1.4.1 (or higher) to be used in WLS6.0
sp2
Nico

[svn:fx-trunk] 7796: get the correct locales of batik and xerces jars into the build

Revision: 7796
Author:   [email protected]
Date:     2009-06-12 13:01:48 -0700 (Fri, 12 Jun 2009)
Log Message:
get the correct locales of batik and xerces jars into the build
bug: https://bugs.adobe.com/jira/browse/SDK-21565
qa: i18n team (make sure they're all there)
checkintests: pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21565
Modified Paths:
    flex/sdk/trunk/build.xml

Originally posted by: rosec.messagingdirect.com
I'll look into it; I'm a bit under the gun here and can't easily upend
my development environment at this time, but hopefully I can look into
it early next week. Thanks for the pointer.
Daniel Megert wrote:
> Chris Rose wrote:
>> I don't know if this has been asked before (and you'd be amazed at how
>> hard it is to find specific information when your search query is
>> "eclipse 100% cpu usage opening class files in a jar"!) but, well,
>> that's what I'm getting:
>>
>> When I open a class file in the editor that is contained in a jar file
>> anywhere on a Java project's classpath, one of my processor pegs at
>> 100% usage for anywhere from 15-120 seconds and eclipse becomes
>> non-responsive for that period of time, not even redrawing the UI.
>>
>> This occurs for jars as large as the jboss client jar and the weblogic
>> 80Mb uber-jar and for jars as small as a 241kb library jar.
>>
>> Is there anything I can do to track down WHY this is happening? I end
>> up having to trace into third party code a lot while debugging
>> container behaviour and this plays merry havoc with the timeouts for
>> remote calls, so I'm quite motivated to suss out why it's happening.
>>
>> Eclipse details are attached.
> There was a bug regarding big JARs on the build path. Can you try
> whether this still happens using 3.4 M7. If so, please file a bug report
> with steps to reproduce. Also, please create some stack dumps while
> waiting and attach them to the bug report.
>
> Dani
Chris Rose
Developer Planet Consulting Group
(780) 577-8433
[email protected]

Weblogic XML Registry and Entity Resolution

Hi,
I have configure Weblogic XML Registry as described in
http://e-docs.bea.com/wls/docs81/ConsoleHelp/xml.html. I have a directory
where my dtds reside (%WLDOMAIN%/xml/registries/MyRegistry/). I using JAXP
(the BEA recommended API which should automatically make use of the registry
for entity resolution). But somehow it seems that it is looking in the root
of the weblogic domain for the entities and not in the registry entities
directory.
A sample doctype in one of my doc looks like <!DOCTYPE substance_id PUBLIC
"-//CAS//DTD substance_id//EN" "substance_id.dtd">
The registry is configured as follows
Public ID System ID
Entity URI When To Cache Cache Timeout Interval
============================================================================
===============
-//CAS//ENTITY CMD Defined Entities//EN CMSents.dtd CMSents.dtd
defer-to-registry-setting -1
-//CAS//DTD control//EN control.dtd
control.dtd defer-to-registry-setting -1
-//CAS//DTD substance_id//EN substance_id.dtd
substance_id.dtd defer-to-registry-setting -1
Below is the exception from the server log. Any help would be greatly
appreaciated.
####<Dec 12, 2003 11:09:32 AM EST> <Debug> <org.cas.felix.util.XML>
<PC81227> <myserver> <ExecuteThread: '13' for queue:
'weblogic.kernel.Default'> <<anonymous>> <BEA1-0009897C74118C32D0F4>
<000000> <exception parsing document <?xml version="1.0"?>
<!DOCTYPE substance_id PUBLIC "-//CAS//DTD substance_id//EN"
"substance_id.dt ... (4869)
java.io.FileNotFoundException: D:\wls_domains\felix\substance_id.dtd (The
system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:6
9)
at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection
.java:156)
at java.net.URL.openStream(URL.java:960)
at
weblogic.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.ja
va:836)
at
weblogic.apache.xerces.impl.XMLEntityManager.startDTDEntity(XMLEntityManager
.java:796)
at
weblogic.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerIm
pl.java:275)
at
weblogic.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XM
LDocumentScannerImpl.java:841)
at
weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLD
ocumentFragmentScannerImpl.java:329)
at
weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:
525)
at
weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:
581)
at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at
weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.jav
a:1175)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:138)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
at org.cas.felix.util.XML.validate(XML.java:88)
at org.cas.felix.util.XML.validate(XML.java:69)
at org.cas.felix.si.master.MasterDocument.<init>(MasterDocument.java:94)
at org.cas.felix.si.master.MasterDocument.<init>(MasterDocument.java:139)
at
org.cas.felix.si.j2ee.processing.FelixSIProcessorBean.processRecord(Unknown
Source)
at org.cas.felix.si.j2ee.processing.FelixSIProcessorBean.onMessage(Unknown
Source)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:374)
at
weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:30
8)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:273)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2550)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2470)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)

Hi Brian,
In your config.xml, in the <XMLRegistry> section, what does the
EntityURI look like? I believe it should be a relative entry, something
like %WLDOMAIN%/xml/registries/MyRegistry
If this is not the issue, I would encourage you to provide this
information with your config.xml to our outstanding support team to
resolve this issue.
Thanks,
Bruce
Brian Sam-Bodden wrote:
>
Hi,
I have configure Weblogic XML Registry as described in
http://e-docs.bea.com/wls/docs81/ConsoleHelp/xml.html. I have a directory
where my dtds reside (%WLDOMAIN%/xml/registries/MyRegistry/). I using JAXP
(the BEA recommended API which should automatically make use of the registry
for entity resolution). But somehow it seems that it is looking in the root
of the weblogic domain for the entities and not in the registry entities
directory.
A sample doctype in one of my doc looks like <!DOCTYPE substance_id PUBLIC
"-//CAS//DTD substance_id//EN" "substance_id.dtd">
The registry is configured as follows
Public ID System ID
Entity URI When To Cache Cache Timeout Interval
============================================================================
===============
-//CAS//ENTITY CMD Defined Entities//EN CMSents.dtd CMSents.dtd
defer-to-registry-setting -1
-//CAS//DTD control//EN control.dtd
control.dtd defer-to-registry-setting -1
-//CAS//DTD substance_id//EN substance_id.dtd
substance_id.dtd defer-to-registry-setting -1
Below is the exception from the server log. Any help would be greatly
appreaciated.
####<Dec 12, 2003 11:09:32 AM EST> <Debug> <org.cas.felix.util.XML>
<PC81227> <myserver> <ExecuteThread: '13' for queue:
'weblogic.kernel.Default'> <<anonymous>> <BEA1-0009897C74118C32D0F4>
<000000> <exception parsing document <?xml version="1.0"?>
<!DOCTYPE substance_id PUBLIC "-//CAS//DTD substance_id//EN"
"substance_id.dt ... (4869)
java.io.FileNotFoundException: D:\wls_domains\felix\substance_id.dtd (The
system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:6
9)
at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection
.java:156)
at java.net.URL.openStream(URL.java:960)
at
weblogic.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.ja
va:836)
at
weblogic.apache.xerces.impl.XMLEntityManager.startDTDEntity(XMLEntityManager
.java:796)
at
weblogic.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerIm
pl.java:275)
at
weblogic.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XM
LDocumentScannerImpl.java:841)
at
weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLD
ocumentFragmentScannerImpl.java:329)
at
weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:
525)
at
weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:
581)
at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at
weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.jav
a:1175)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:138)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
at org.cas.felix.util.XML.validate(XML.java:88)
at org.cas.felix.util.XML.validate(XML.java:69)
at org.cas.felix.si.master.MasterDocument.<init>(MasterDocument.java:94)
at org.cas.felix.si.master.MasterDocument.<init>(MasterDocument.java:139)
at
org.cas.felix.si.j2ee.processing.FelixSIProcessorBean.processRecord(Unknown
Source)
at org.cas.felix.si.j2ee.processing.FelixSIProcessorBean.onMessage(Unknown
Source)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:374)
at
weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:30
8)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:273)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2550)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2470)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)

Help!.... XA error: using Weblogic 6.1 and Oracle 8.1.6

 Hi,
 I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
 to use Container Managed Transaction through a Session Bean.
 Connection Pool Settings: -------------------------
 Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
 TXDataSource Settings : -----------------------
 Name - myXADS
 JNDIName - myXADS
 PoolName - myXAPool
 Everything works fine but once in a while I get the following exception:
 java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
 in the transaction branch start() failed on resource 'myXAPool' Unexpected error
 during start for XAResource 'myXAPool': null
 The connection pool size is 30 and the number connections high reached was 5,
 which means there are enough connections in the pool available at all time.
 It would be really great if you can help me out.
 Thanks in Advance, Sudhir.


Hi Slava,
Sorry about that Oracle instance I am using is 8.1.7.
For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
And my Weblogic version 6.1 Sp3.
Thanks,
Sudhir.
"Slava Imeshev" <[email protected]> wrote:
Hi Sudhir,
Are you using an instance of 8.1.6 or 8.1.7? In the message header you
say
8.1.6.
Regards,
Slava Imeshev
"Sudhir Babu" <[email protected]> wrote in message
news:[email protected]..
Hi,
I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
I wanted
to use Container Managed Transaction through a Session Bean.
Connection Pool Settings: -------------------------
Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource Settings : -----------------------
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
Everything works fine but once in a while I get the following exception:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
occured
in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
during start for XAResource 'myXAPool': null
The connection pool size is 30 and the number connections high reachedwas
5,
which means there are enough connections in the pool available at alltime.
It would be really great if you can help me out.
Thanks in Advance, Sudhir.

XA error: using Weblogic 6.1 and Oracle 8.1.6

Hi,
I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
to use Container Managed Transaction through a Session Bean.
Connection Pool Settings: -------------------------
Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource Settings : -----------------------
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
Everything works fine but once in a while I get the following exception:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
in the transaction branch start() failed on resource 'myXAPool' Unexpected error
during start for XAResource 'myXAPool': null
The connection pool size is 30 and the number connections high reached was 5,
which means there are enough connections in the pool available at all time.
It would be really great if you can help me out.
Thanks in Advance, Sudhir.

Hi Slava,
Sorry about that Oracle instance I am using is 8.1.7.
For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
And my Weblogic version 6.1 Sp3.
Thanks,
Sudhir.
"Slava Imeshev" <[email protected]> wrote:
Hi Sudhir,
Are you using an instance of 8.1.6 or 8.1.7? In the message header you
say
8.1.6.
Regards,
Slava Imeshev
"Sudhir Babu" <[email protected]> wrote in message
news:[email protected]..
Hi,
I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
I wanted
to use Container Managed Transaction through a Session Bean.
Connection Pool Settings: -------------------------
Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource Settings : -----------------------
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
Everything works fine but once in a while I get the following exception:
java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
occured
in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
during start for XAResource 'myXAPool': null
The connection pool size is 30 and the number connections high reachedwas
5,
which means there are enough connections in the pool available at alltime.
It would be really great if you can help me out.
Thanks in Advance, Sudhir.

Which database driver is required for weblogic 10.3 and Oracle DB 11g both on MS2008 separate server

Hi,
i am trying to configure JDBC with weblogic. Can any one tell me which deriver needs to be selected for weblogic 10.3 and Oracle DB 11g both on MS2008 separate server.
if i use BEA oracle Driver (Type 4) version 9.0.1, 9.2.0,10,11, i find error (see snap:2)
Connection test failed.
[BEA][Oracle JDBC Driver]Error establishing socket. Unknown host: hdyhtc137540d weblogic.jdbc.base.BaseExceptions.createException(Unknown Source) weblogic.jdbc.base.BaseExceptions.getException(Unknown Source) weblogic.jdbc.oracle.OracleImplConnection.makeConnectionHelper(Unknown Source) weblogic.jdbc.oracle.OracleImplConnection.makeConnection(Unknown Source) weblogic.jdbc.oracle.OracleImplConnection.connectAndAuthenticate(Unknown Source) weblogic.jdbc.oracle.OracleImplConnection.open(Unknown Source) weblogic.jdbc.base.BaseConnection.connect(Unknown Source) weblogic.jdbc.base.BaseConnection.setupImplConnection(Unknown Source) weblogic.jdbc.base.BaseConnection.open(Unknown Source) weblogic.jdbc.base.BaseDriver.connect(Unknown Source) com.bea.console.utils.jdbc.JDBCUtils.testConnection(JDBCUtils.java:505) c om.bea.console.actions.jdbc.datasources.createjdbcdatasource.CreateJDBCDataSource.testConn ectionConfiguration(CreateJDBCDataSource.java:369) sun.reflect.GeneratedMethodAccessor 826.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl. java:25) java.lang.reflect.Method.invoke(Method.java:597) org.apache.beehive.netui .pageflow.FlowController.invokeActionMethod(FlowController.java:870) org.apache.beehiv e.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809) org.ap ache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478) or g.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java :306) org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336 ) ...
and
when i use oracle's driver (thin) version 9.0.1, 9.2.0,10,11, i find error
Connection test failed.
Io exception: The Network Adapter could not establish the connection oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:10 1) oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112) oracle .jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173) oracle.jdbc.drive r.DatabaseError.throwSqlException(DatabaseError.java:229) oracle.jdbc.driver.DatabaseE rror.throwSqlException(DatabaseError.java:458) oracle.jdbc.driver.T4CConnection.logon( T4CConnection.java:411) oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnectio n.java:490) oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:202) oracle .jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33) oracle.jdbc. driver.OracleDriver.connect(OracleDriver.java:474) com.bea.console.utils.jdbc.JDBCUtil s.testConnection(JDBCUtils.java:505) com.bea.console.actions.jdbc.datasources.createjd bcdatasource.CreateJDBCDataSource.testConnectionConfiguration(CreateJDBCDataSource.java:36 9) sun.reflect.GeneratedMethodAccessor826.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl. java:25) java.lang.reflect.Method.invoke(Method.java:597) org.apache.beehive.netui .pageflow.FlowController.invokeActionMethod(FlowController.java:870) org.apache.beehiv e.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809) org.ap ache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478) or g.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java :306) org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336 ) ...

i am finding this error when i click on Test Configuration button to test the connection wth oracle DB

CF8 on Weblogic 10.0 and Apache

I am trying to configure CF8 as an EAR file on Weblogic 10.0
and configuring it with Apache webserver. The settings for Weblogic
are made as mentioned in the configuration document and CF8 is
working fine on Weblogic.
Now for Apache connectivity, a connector is configured for
Weblogic which handles *.cfm files requests as well.
- The CFM files are kept in webserver and when I try to open
a cfm file, the proxy is getting invoked but since Weblogic doesn't
find the file URI it returns 404.
- Please let me know how can the CFM files kept on Webserver
be rendered using CF8 deployed on Weblogic
Or there is a need for these files to be kept on the Weblogic
Appserver only

sam_cf09 wrote:
> Can the CFM files be a part of any WAR file deployed on
Weblgic and Cold
> fusion will take care of rendering them
Sure. If you want to put a file example.cfm in a WAR file,
put it in the
root of the WAR. Your folder structure will look something
like:
WAR/
WAR/example.cfm
WAR/WEB-INF
WAR/WEB-INF/web.xml
WAR/WEB-INF/*
WAR/WEB-INF/cfusion
WAR/WEB-INF/cfusion/lib/
etc.
Then if you have a context root "/test" in your
Application.xml you can
reach your template through the URL
http://server/test/example.cfm
The best way to get a WAR (or EAR) file for deployment is to
run the
installer. It has the option to generate a WAR or EAR for
you. Use that,
then later unjar it to see how it looks internally.
Jochem
Jochem van Dieten
Adobe Community Expert for ColdFusion

WebLogic 8.1SP4 and IIS

Hi,
I want to configure weblogic with IIS and have found enough articles on how to proxy IIS to point to a single instance or a clustered environment but not on how to proxy IIS to multiple WebLogic servers
I have the application running on
http://<weblogic-server>:7201/elms
http://<weblogic-server>:7301/elms
http://<weblogic-server>:7401/elms
and I want to be able to access these via the IIS through these URLs:
http://<IIS_Server>/elms
http://<IIS_Server>/elms_sit
http://<IIS_Server>/elms_uat
Is this configuration possible? Any help would be highly appreciated.
Thanks
Sandeep

Since you are attempting to proxy by path you need to configure the iisforward.dll as stated in step #3 here:
http://e-docs.bea.com/wls/docs81/plugins/isapi.html#100382

Weblogic Bridge "failed and will reconnect later"

The enterprise architecture is as follows:
1 Physical machine where I have 2 VMs on this machine, and each VM I have 1 domain, 1 Cluster and 1 managed server, and the second VM I have the replicated what I have in first VM.
In first domain I have the OSB, in the second domain I have SOA.
What I need ? Send information of queues (topics) of First Domain (OSB) to second domain(SOA).
At first the only thing I did was:
In the first domain I created OSB JMS Server, JMS Module, Connection Factory and Queue Topic.
In the second domain SOA I replied the same thing but with different names.
Then I created the bridge with configuration default between the first domain and the second domain, the bridge and when active it generates me a message Weblogic Bridge "failed and will reconnect later"
I did a test on my local machine windows where I created two domains, and the same procedures you did above, but the point was funcinou been activated now for the enterprise environment I'm not managing to make it work, you could tell me what is wrong . in both cases restarted the weblogic server as the machine itself the question that ran on my machine and machine company no.
If you can give me a light thank.

This is a bug (6973877, derby only) which has been fixed in 4.5 build14 and 4.4u2p1. Thanks for reporting. The problem is the missing "FOR BIT DATA" in LOG_RECORD column in derby table definition MQTMLRJMSBG41 in broker default.properties file
- LOG_RECORD VARCHAR(2048) NOT NULL,\
+ LOG_RECORD VARCHAR(2048) FOR BIT DATA NOT NULL,\

Help! Unable to Start - weblogic.policy - (Linux) and WLS 5.1

Does this hold true for NT as well? The comments in the weblogic.policy file read:
// If WebLogic is not installed in a root directory, you must only
// list the first component of the path in the "file:" URL. This is
// because of a bug in JavaSoft JDK 1.2.1. For example, if you
// install WebLogic in the "c:/test/weblogic" directory, the first
// two lines below must be:
// grant codeBase "file:/c:/test/-" {
// permission java.io.FilePermission "c:${/}test${/}weblogic${/}-", "read,write,delete,execute";
However, when I use the similar file structure:
grant codeBase "file:/c:/bea/-" {
permission java.io.FilePermission "c:${/}bea${/}wlserver6.0sp1${/}lib${/}-",
"read,write,delete,execute";
I receive the same error and WebLogic Server will not start up.
Thanks for your help.
Tawnya
Mark Griffith <[email protected]> wrote:
If you have a directory :
/usr/local/releases/451/weblogic
in that dir lives:
weblogic.policy
that policy file should say:
grant codeBase "file://weblogic/-" {
NOT
grant codeBase "file://usr/local/releases/451/weblogic/-" {
mbg
In article <[email protected]>, [email protected]
says...
ENV:
Redhat Linux 6.2 (Current Kernel)
Weblogic Server 5.1
Sun JDK for Linux version 1.2.2
It seems like I am having a weblogic.policy problem. I have read the
documenattion over and over and still cannot figure out this problem.
I have weblogic installed on /usr/local/weblogic directory
I Start with the command line:from the startWebLogic.sh Script
$JAVA $JAVA_OPTIONS -ms64m -mx64m -classpath $JAVACLASSPATH
-Dweblogic.class.path=$WEBLOGICCLASSPATH -Djava.security.manager
-Djava.security.policy=='pwd'/weblogic.policy
-Dweblogic.home=. weblogic.Server
I followed all the instrcutions on modifying the weblogic.policy
file.
example:
grant codeBase "file:/usr/local/weblogic/-" {
permission java.io.FilePermission "${/}usr${/}local${/}weblogic${/}-",
"read,write,delete,execute";
I still get the following :
Exception in thread "main" java.security.AccessControlException:access
denied (java.lang.RuntimePermission createSecurityManager )
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java
:191)
at
java.security.AccessController.checkPermission(AccessController.java:399)
at
java.lang.SecurityManager.checkPermission(SecurityManager.java:545)
at java.lang.SecurityManager.<init>(SecurityManager.java:303)
at
weblogic.boot.ServerSecurityManager.<init>(ServerSecurityManager.java:11)
at weblogic.Server.main(Server.java:59)
at weblogic.Server.main(Server.java:55)
Can anyboby Help me out here?
Tony McClay
Mr. BigMAN--
==================================================
NewsGroup Rant
==================================================
Rant 1.
The less info you provide about your problem means
the less we can help you. Try to look at the
problem from an external perspective and provide
all the data necessary to put your problem in
perspective.

Weblogic and xerces and xalan

Similar Messages

Maybe you are looking for