BEA WebLogic 10.3 JMS Jar version

Hi,
Someone knows what specific version of JMS BEA Jar should be used when connecting to a 10.3 JMS BEA Server from a PI 7.0 system?
Thanks in advance.

I tried that but I could not find it, do you have the link?
Thanks.

Similar Messages

Jms from sun j2ee to bea weblogic

Hy,
          is there a easy way to connect a JmsFactory from an j2ee sun server to a
          bea weblogic server?
          JMS API Tutorial shows an example for connecting two j2ee Server:
          j2eeadmin --addJmsFactory MyFactory queue -props
          url=corbaname:iiop:remoteserver:1050:#remoteserver
          Weblogic 7 seems to support iiop (on Port 7001?) but
          something is missing ... no connection could be made to send Messages
          from j2ee (sun) to weblogic server?
          Any hint?
          Best Regards,
          Holger


Hi Holger,
          The WL JMS client does not support iiop in 7.0,
          although it does in 8.1 (beta soon). Instead use t3, a much
          faster protocol, or, if you need to tunnel, use http.
          Note that BEA has a comprehensive white-paper on integrating
          "foreign" JMS providers on dev2dev.bea.com:
          "Using Foreign JMS Providers With WebLogic Server"
          Tom
          Holger von Rhein wrote:
          > Hy,
          >
          > is there a easy way to connect a JmsFactory from an j2ee sun server to a
          > bea weblogic server?
          >
          > JMS API Tutorial shows an example for connecting two j2ee Server:
          >
          > j2eeadmin --addJmsFactory MyFactory queue -props
          > url=corbaname:iiop:remoteserver:1050:#remoteserver
          >
          > Weblogic 7 seems to support iiop (on Port 7001?) but
          > something is missing ... no connection could be made to send Messages
          > from j2ee (sun) to weblogic server?
          >
          > Any hint?
          >
          >
          > Best Regards,
          >
          > Holger
          >

BEA Weblogic Application Server

Hi All,
Is or was there an BEA Weblogic Application Server 8.0 version? I believe that
there was no such version, but can someone confirm this for me?
Thanks
Simon

Current versions are:
5.1, 6.0, 6.1 7.0 and 8.1
and coming soon 9.X
Jin
"simon" <[email protected]> wrote:
>
Hi All,
Is or was there an BEA Weblogic Application Server 8.0 version? I believe
that
there was no such version, but can someone confirm this for me?
Thanks
Simon

Welcome to the BEA WebLogic Server Version 6.0 Beta Program!

Welcome to the BEA WebLogic Server Version 6.0 Beta Program!
We are very excited about this beta program and appreciate your
participation. In the past, our public betas have been very well received
by our developer community. So, we have once again organized a public beta
program to enable everyone to preview our latest release.
We do ask that you follow a few guidelines:
-- There will be no voice, e-mail, or fax support for this beta through the
technical support organization. All questions, bug reports, or comments on
the beta program should be directed to to the WebLogic beta newsgroups at
news://newsgroups.bea.com. These newsgroups are:
weblogic.developer.interest.60beta.transaction
weblogic.support.install.60beta
weblogic.developer.interest.60beta.ejb
weblogic.developer.interest.60beta.clustering
weblogic.developer.interest.60beta.security
weblogic.developer.interest.60beta.jdbc
weblogic.developer.interest.60beta.jms
weblogic.developer.interest.60beta.performance
weblogic.developer.interest.60beta.misc
weblogic.developer.interest.60beta.servlet
weblogic.developer.interest.60beta.jsp
weblogic.developer.interest.60beta.tools
weblogic.developer.interest.60beta.rmi-iiop
weblogic.developer.interest.60beta.management
weblogic.developer.interest.60beta.management.console
weblogic.developer.interest.60beta.management.general_and_jmx
weblogic.developer.interest.60beta.internationalization
weblogic.developer.interest.60beta.xml
weblogic.developer.interest.60beta.jndi
weblogic.developer.interest.60beta.documentation
weblogic.developer.interest.60beta.javamail
-- Please remember that this release is currently beta code. This means that
it should not be put into production deployments until the final release
occurs.
-- It is very likely that this release will contain bugs and errors. This is
the nature of beta code. Please the patient with us as we do our best to fix
any problems that we find. We will do our absolute best to make sure that
your issues are addressed as soon as possible.
-- Please do not post any issues relevant to the beta on the standard
newsgroups also available at news://newsgroups.bea.com.
-- Please use the newsgroup for all communication and do not contact any BEA
employees directly. They have been instructed to direct you to comment only
via the newsgroup.
-- Please review previous posts in the newsgroups before posting. If you
locate a bug or need to ask a question, it is very likely that it will have
been asked before.
-- Please do not post on the newsgroup using hostile or profane language.
Inappropriate posts will be removed and offenders will be blocked from the
beta program.
Thank you again for your support and participation. We very much appreciate
all that you will be doing to make this release of the BEA WebLogic Server
as great as possible.
Michael Girdley
BEA Systems Inc

Welcome to the BEA WebLogic Server Version 6.0 Beta Program!
We are very excited about this beta program and appreciate your
participation. In the past, our public betas have been very well received
by our developer community. So, we have once again organized a public beta
program to enable everyone to preview our latest release.
We do ask that you follow a few guidelines:
-- There will be no voice, e-mail, or fax support for this beta through the
technical support organization. All questions, bug reports, or comments on
the beta program should be directed to to the WebLogic beta newsgroups at
news://newsgroups.bea.com. These newsgroups are:
weblogic.developer.interest.60beta.transaction
weblogic.support.install.60beta
weblogic.developer.interest.60beta.ejb
weblogic.developer.interest.60beta.clustering
weblogic.developer.interest.60beta.security
weblogic.developer.interest.60beta.jdbc
weblogic.developer.interest.60beta.jms
weblogic.developer.interest.60beta.performance
weblogic.developer.interest.60beta.misc
weblogic.developer.interest.60beta.servlet
weblogic.developer.interest.60beta.jsp
weblogic.developer.interest.60beta.tools
weblogic.developer.interest.60beta.rmi-iiop
weblogic.developer.interest.60beta.management
weblogic.developer.interest.60beta.management.console
weblogic.developer.interest.60beta.management.general_and_jmx
weblogic.developer.interest.60beta.internationalization
weblogic.developer.interest.60beta.xml
weblogic.developer.interest.60beta.jndi
weblogic.developer.interest.60beta.documentation
weblogic.developer.interest.60beta.javamail
-- Please remember that this release is currently beta code. This means that
it should not be put into production deployments until the final release
occurs.
-- It is very likely that this release will contain bugs and errors. This is
the nature of beta code. Please the patient with us as we do our best to fix
any problems that we find. We will do our absolute best to make sure that
your issues are addressed as soon as possible.
-- Please do not post any issues relevant to the beta on the standard
newsgroups also available at news://newsgroups.bea.com.
-- Please use the newsgroup for all communication and do not contact any BEA
employees directly. They have been instructed to direct you to comment only
via the newsgroup.
-- Please review previous posts in the newsgroups before posting. If you
locate a bug or need to ask a question, it is very likely that it will have
been asked before.
-- Please do not post on the newsgroup using hostile or profane language.
Inappropriate posts will be removed and offenders will be blocked from the
beta program.
Thank you again for your support and participation. We very much appreciate
all that you will be doing to make this release of the BEA WebLogic Server
as great as possible.
Michael Girdley
BEA Systems Inc

Where get weblogic.jar version 8.1 or 9.2?

I need to get weblogic.jar version 8.1 or 9.2 to use with Hermes because 10.3 apparently does not have class weblogic/security/subject/AbstractSubject... I failed finding it on the net...
Thank you
Leonard

I've got the exakt same problem using weblogic.Deployer .... -appversion, weblogic 10.0 in this case. Works fine with our new jaxws based webservices.
Would be nice if this problem was solved, especially since weblogic10 resolves softlinks so our old method of linking to new versions doesn't work anymore. And the fact that "Changing the source location is not allowed for a previously attempted deployment" doesn't help either.

Oracle ifs and BEA weblogic

Oracle ifs and BEA weblogic
We have one application server with weblogic and and ifs 1.0.9 , and one db server with Oracle 8.1.7.
with the following configuration:
Web server
appl server with weblogic 6.0 and ifs 1.1.9
Oracle 8i Enterprise with interMedia text
We need to use the iFS API call for our application.
As I know, weblogic 6.0 support JDK1.3 but ifs 1.1.9 supports up to JDK1.2.
Is this configuration possible?
Any conflict if two version JDK co-exist inside same machine?
Any suggestion?
If I separate the appl. server into two machines, that is,
one server installed with weblogic, the other one installed with ifs.
How could I make use the ifs API call from appl. server?
Is there any configuration guides for this setting?
Thanks a lot.
null

<BLOCKQUOTE>quote:<HR>Originally posted by Luis:
The iFS API is 100% pure Java. You can use it from any other Java application, be it JSP, EJB, or a standalone application.
So it really comes down to the CLASSPATH. The iFS API is split among a set of .jar files, and some of the configuration information is stored in .properties files that are outside of these .jar files. All of this stuff needs to be in the CLASSPATH of whatever JVM is calling the iFS API.
The iFS API uses the Oracle JDBC driver to communicate with the Oracle database. This is another requirement. You can't use another JDBC driver; you have to use ours.
So again, it's all about configuration.<HR></BLOCKQUOTE>
Would you mind to share more detail on configurating weblogic to integrate the iFS API?
null

Problem in calling a web service hosted on tomcat from BEA WebLogic portal

Hi,
I have a wsdl file for my web service which is hosted on apache tomcat 5.5(running on port : 8080). The contents of the wsdl file are-
*<?xml version="1.0" encoding="UTF-8"?>*
*<wsdl:definitions targetNamespace="http://soa.tutorials.serg.edu" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://soa.tutorials.serg.edu" xmlns:intf="http://soa.tutorials.serg.edu" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">*
*
*<wsdl:types>*
*<schema elementFormDefault="qualified" targetNamespace="http://soa.tutorials.serg.edu" xmlns="http://www.w3.org/2001/XMLSchema">*
*<element name="getNums">*
*<complexType>*
*<sequence>*
*<element name="n" type="xsd:int"/>*
*<element name="m" type="xsd:int"/>*
*</sequence>*
*</complexType>*
*</element>*
*<element name="getNumsResponse">*
*<complexType>*
*<sequence>*
*<element maxOccurs="unbounded" name="getNumsReturn" type="xsd:int"/>*
*</sequence>*
*</complexType>*
*</element>*
*<element name="getNums2">*
*<complexType>*
*<sequence>*
*<element name="n" type="xsd:int"/>*
*<element name="m" type="xsd:int"/>*
*</sequence>*
*</complexType>*
*</element>*
*<element name="getNums2Response">*
*<complexType>*
*<sequence>*
*<element maxOccurs="unbounded" name="getNums2Return" type="xsd:int"/>*
*</sequence>*
*</complexType>*
*</element>*
*</schema>*
*</wsdl:types>*
*<wsdl:message name="getNums2Request">*
*<wsdl:part element="impl:getNums2" name="parameters"/>*
*</wsdl:message>*
*<wsdl:message name="getNumsRequest">*
*<wsdl:part element="impl:getNums" name="parameters"/>*
*</wsdl:message>*
*<wsdl:message name="getNums2Response">*
*<wsdl:part element="impl:getNums2Response" name="parameters"/>*
*</wsdl:message>*
*<wsdl:message name="getNumsResponse">*
*<wsdl:part element="impl:getNumsResponse" name="parameters"/>*
*</wsdl:message>*
*<wsdl:portType name="Echo">*
*<wsdl:operation name="getNums">*
*<wsdl:input message="impl:getNumsRequest" name="getNumsRequest"/>*
*<wsdl:output message="impl:getNumsResponse" name="getNumsResponse"/>*
*</wsdl:operation>*
*<wsdl:operation name="getNums2">*
*<wsdl:input message="impl:getNums2Request" name="getNums2Request"/>*
*<wsdl:output message="impl:getNums2Response" name="getNums2Response"/>*
*</wsdl:operation>*
*</wsdl:portType>*
*<wsdl:binding name="EchoSoapBinding" type="impl:Echo">*
*<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>*
*<wsdl:operation name="getNums">*
*<wsdlsoap:operation soapAction=""/>*
*<wsdl:input name="getNumsRequest">*
*<wsdlsoap:body use="literal"/>*
*</wsdl:input>*
*<wsdl:output name="getNumsResponse">*
*<wsdlsoap:body use="literal"/>*
*</wsdl:output>*
*</wsdl:operation>*
*<wsdl:operation name="getNums2">*
*<wsdlsoap:operation soapAction=""/>*
*<wsdl:input name="getNums2Request">*
*<wsdlsoap:body use="literal"/>*
*</wsdl:input>*
*<wsdl:output name="getNums2Response">*
*<wsdlsoap:body use="literal"/>*
*</wsdl:output>*
*</wsdl:operation>*
*</wsdl:binding>*
*<wsdl:service name="EchoService">*
*<wsdl:port binding="impl:EchoSoapBinding" name="Echo">*
*<wsdlsoap:address location="http://localhost:8080/SOATest/services/Echo"/>*
*</wsdl:port>*
*</wsdl:service>*
*</wsdl:definitions>*
I created a client from the above wsdl file using ClientGen wizard in WebLogic. This client contains the follwoing classes-
Echo.java
EchoService.java
EchoService_Impl.java
Echo_Stub.java
I created a JSP portlet and the jsp content of it is-
String url = "http://localhost:8080/SOATest/services/Echo";
Echo echo = new EchoService_Impl(url).getEcho();
getNumsResponse = echo.getNums(getNums);
I tried to call that web service from BEA weblogic portal through a JSP potlet. I got an error saying -
*<An exception [javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element] was thrown while rendering the content at [TestEcho.jsp].*
*javax.servlet.ServletException: javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
* at weblogic.servlet.jsp.PageContextImpl.handlePageException(PageContextImpl.java:420)*
* at jsp_servlet.__testecho._jspService(__testecho.java:112)*
* at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)*
* at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)*
* at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)*
* Truncated. see log file for complete stacktrace*
*javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
* at weblogic.wsee.jaxrpc.ServiceImpl.throwServiceException(ServiceImpl.java:174)*
* at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:485)*
* at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:119)*
* at edu.serg.tutorials.soa.EchoService_Impl.<init>(Unknown Source)*
* at edu.serg.tutorials.soa.EchoService_Impl.<init>(Unknown Source)*
* Truncated. see log file for complete stacktrace*
*weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
* at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:313)*
* at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)*
* at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:391)*
* at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:79)*
* at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:66)*
* Truncated. see log file for complete stacktrace*
*java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
* at weblogic.xml.domimpl.Loader.load(Loader.java:38)*
* at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:122)*
* at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)*
* at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)*
* at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)*
* Truncated. see log file for complete stacktrace*
*javax.xml.stream.XMLStreamException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
* at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:206)*
* at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:237)*
* at weblogic.xml.domimpl.Loader.load(Loader.java:112)*
* at weblogic.xml.domimpl.Loader.load(Loader.java:73)*
* at weblogic.xml.domimpl.Loader.load(Loader.java:35)*
* Truncated. see log file for complete stacktrace*
*Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
* at weblogic.xml.babel.baseparser.BaseParser.parseProlog(BaseParser.java:417)*
* at weblogic.xml.babel.baseparser.BaseParser.parseSome(BaseParser.java:328)*
* at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:195)*
* at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:237)*
* at weblogic.xml.domimpl.Loader.load(Loader.java:112)*
* Truncated. see log file for complete stacktrace*
My web service is using soap binding. I have tested it with eclipse and other tools also. It is working well and good. But when I tried to call a web service which is created and hosted on WebLogic server(running on port : 7001), I got the correct output.
Can anyone help me out in calling a web service hosted on different server from WebLogic server.
Thanks in advance,
Tiijnar
Edited by: user8715057 on Aug 13, 2009 1:11 AM

Hi
1. The way you are invoking the WebService deployed on Tomcat server is looks suspicious. It may be valid by adding extra ?wsdl etc into the url, but still I have not seen this way to invoke the webservice.
2. So you used Weblogic ant task to generate client JARs by giving this WSDL. So looks like it generated the 4 classes (.java) and in addition any other classes for Request/Response xml objects.
3. Look at the source code of EchoService.java. It should have one default empty constructor. Internally it uses the default wsdl defined in this class. You will see another constructor that takes WSDL URL as one of the parameters (QName) etc. Echo.java is the class corresponding to the Port. In the same EchoService you should see an instance method like getEcho() something like that. This Echo.java class will have methods for all the Operations defined on this Port. So the standard code snippet we use most of the times will be like this:
EchoService myEchoService = new EchoService(); // Default it uses WSDL deployed on Tomcat at localhost:8080
Echo myEchoPort = myEchoService.getEchoPort(); // Something along these lines.
myEchoPort.xxxYYY(); // NOW this is the operation name that takes the input parameters and returns outputs defined as per the WSDL defintions. If the Input and Outputs are complex xml types, it will have corresponing .JAVA files with setters and getters.
Now if this WebService is deployed on same Tomcat but on different machine or different port, you just give the full WSDL URL with that host and port in the constructor for new EchoService(...). You may need to instantiate QName object. But look at the methods generated in EchoService.java class.
The way you are using with Impl and Stubs class may also work. I am not much famiiar with this APIs apporach. Still look at the methods generated in these classes.
Also if you latest Sun JDK 1.6, it also has one command like wsimport. Infact if you install WLS 10.3 with Sun JDK, it should have C:\beawlp103\jdk160_05\bin\wsimport command. This will also generate client jar given a WSDL URL.
Thanks
Ravi Jegga

XSQL and BEA Weblogic 6.1

I spent a lot of time trying to figure out how to configure
the XSQL servlet to run on BEA Weblogic 6.1
It is really simple once you understand that you should work
off expanded directory instead of trying to get a .war or .ear
file uploaded.
I decided to give my explanation to help others...
This works with the current XDK (9.0.2.0.0D) on OTN and I got it
running on Windows 2000 and/or Solaris.
I based these instructions on Steve Muench for
"ANN Deploy Oracle XSQL Pages to OC4J" off the OTN web site.
1) get the latest xdk_java off the OTN web site.
2) create a directory (or subdirectory) named xsql (to hold the entire application
3) create /xsql/META-INF
/xsql/WEB-INF
/xsql/WEB-INF/lib
/xsql/WEB-INF/classes
structure to hold the XSQL servlet
4) create a /xsql/META-INF/application.xml with the following code:
<!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN'
'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
<application>
<display-name>Oracle XSQL Servlet</display-name>
<description>Oracle XSQL Servlet</description>
<module>
<web>
<web-uri>xsql.war</web-uri>
<context-root>xsql</context-root>
</web>
</module>
</application>
5) create the file /xsql/WEB-INF/web.xml with the following content
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">
<web-app>
<servlet>
<servlet-name>oracle-xsql-servlet</servlet-name>
<servlet-class>oracle.xml.xsql.XSQLServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>oracle-xsql-servlet</servlet-name>
<url-pattern>*.xsql</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>oracle-xsql-servlet</servlet-name>
<url-pattern>/xsql/*</url-pattern>
</servlet-mapping>
</web-app>
6)extract the xdk_java (that you copied from the OTN) on a temporary directory. (/otn)
7) copy the following files (they are in the /otn/lib subdirectory) into /xsql/WEB-INF/lib
oraclexsql.jar
xsqlserializers.jar
xmlparserv2.jar
xsu12.jar
8) copy /otn/xdk/admin/XSQLConfig.xml to xsql/WEB-INF/classes
9) copy the entire directory and subdir /otn/xdk/demo/java/xsql to /xsql/demo
10) no need to create a war or ear file as Weblogic will work better from the expanded directory
anyway and it is simpler to implement.
11) Now you need to copy that entire directory structure /xsql over to the Weblogic Application Server
config/domain-name/applications area so in my case it is
/bea/wlserver6.1/config/your_domain/applications/xsql
12) If Weblogic is running in development mode, it should deploy and load the servlet automatically.
If it is running in production mode, then we would need to restart it.
13) You should be able to test this with http://your_host:7001/xsql/demo/index.html
Any URL that specifies the /xsql will then be treated by the
XSQL Servlet.
It works for me...

Hi Denis,
I followed your procedure to deploy XSQL Servlet on WebLogic 6.1. First I deployed as expanded directory structure although I turned 'Auto Deployed Enabled' flag to on for my domain, WebLogic couldn't pick up the application. Then I tried to create ear application and deployed it (In your message you are saying that don't need to create ear or war, you mean this is not just a necessity or it never could be deployed as ear/war files). I saw on the as deployed on console but when I tried the http://myhost:7001/xsql/demo/index.html, I got the following error message.
Oracle XDK Java 9.2.0.2.0 Production
XSQL-013: XSQL Page URI is null or has an invalid format.
Oracle XDK Java 9.2.0.2.0 Production
XSQL-013: XSQL Page URI is null or has an invalid format.
Can you help me to trouble shoot this problem? Thank you very much
Deha Peker

Cannot run BEA WebLogic 8.1 SP 3 with JDK 1.6

Hi,
Im using BEA Weblogic 8.1 SP3 trying to run a sample where a Robot from Kapow Mashup Server is called from a WebService hosted in the server.
The thing is that I keep getting a EJB Exception: : java.lang.NoClassDefFoundError: java/lang/StringBuilder (I attach the full exception below). I realised that by default the server uses the JDK which comes with the software (version 1.4) and that the class java.lang.StringBuilder is only available from JDK 1.5 onwards.
I have JDK 1.6 in my system, so in WebLogic -> Tools -> Application Properties -> JDK Home, I set that folder but still same exception occurs.
Through the Configuration Wizard I create a new “Basic WebLogic Server Domain” and in the step to configure the Java SDK I set the JDK 1.6 folder. However, when I try to start that server I get this error.
JAVA Memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m
WLS Start Mode=Development
CLASSPATH=;C:\bea\WEBLOG~1\server\lib\weblogic_knex_patch.jar;C:\bea\WEBLOG~1\common\lib\log4j.jar;C:\bea\WEBLOG~1\server\lib\debugging.jar;C:\bea\WEBLOG~1\server\lib\knex.jar;C:\bea\WEBLOG~1\javelin\lib\javelin.jar;C:\bea\WEBLOG~1\server\lib\wlw-lang.jar;C:\ARCHIV~1\Java\JDK16~1.0_1\lib\tools.jar;C:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;C:\bea\WEBLOG~1\server\lib\weblogic.jar;C:\bea\WEBLOG~1\server\lib\ant\ant.jar;C:\ARCHIV~1\Java\JDK16~1.0_1\jre\lib\rt.jar;;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient+ssl.jar;C:\bea\WEBLOG~1\server\lib\xbean.jar;C:\bea\WEBLOG~1\server\lib\wlxbean.jar;C:\bea\WEBLOG~1\server\lib\xqrl.jar;C:\bea\WEBLOG~1\server\lib\netui\netui-compiler.jar;C:\bea\WEBLOG~1\server\lib\wli.jar;C:\bea\WEBLOG~1\server\lib\fop.jar;C:\bea\WEBLOG~1\integration\adapters\sample\lib\sample-eis.jar;
PATH=C:\bea\WEBLOG~1\server\bin;C:\ARCHIV~1\Java\JDK16~1.0_1\jre\bin;C:\ARCHIV~1\Java\JDK16~1.0_1\bin;C:\Archivos de programa\PC Connectivity Solution\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Intel\DMIX;C:\Archivos de programa\HPQ\IAM\bin;C:\Archivos de programa\Java\jdk1.6.0_10\bin;C:\eclipseJava\plugins\org.apache.ant_1.7.0.v200803061910\bin;C:\Archivos de programa\Archivos comunes\Adobe\AGL;c:\Archivos de programa\Microsoft SQL Server\90\Tools\binn\;c:\matlab6p5\bin\win32;C:\Nokia\Update_Manager\bin;C:\Archivos de programa\QuickTime\QTSystem\;C:\Sun\jwsdp-2.0\jwsdp-shared\bin;C:\Archivos de programa\Kapow Mashup Server 6.3\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Intel\DMIX;C:\Archivos de programa\HPQ\IAM\bin;C:\Archivos de programa\Java\jdk1.6.0_10\bin;C:\eclipseJava\plugins\org.apache.ant_1.7.0.v200803061910\bin;C:\bea\WEBLOG~1\server\bin\oci920_8
* To start WebLogic Server, use a username and *
=== Debugging ===
This window is necessary for debugging code using WebLogic Workshop
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
Listening for transport dt_socket at address: 8453
Starting WLS with line:
C:\ARCHIV~1\Java\JDK16~1.0_1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=C:\bea\WEBLOG~1 -Dwls.home=C:\bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.configuration=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=myserver -Djava.security.policy=C:\bea\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
Listening for transport dt_socket at address: 8453
<27-abr-2009 11H22' CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 11.0-b15 from Sun Microsystems Inc.>
<27-abr-2009 11H22' CEST> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
<27-abr-2009 11H22' CEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic Integration 8.1 SP3 Wed Jun 30 14:05:38 PDT 2004 405464>
Stopping the Weblogic Workshop debugger...
Debugger Stopped.
Stopping Pointbase server...
Pointbase server stopped.
If I modify the settings of this new domain an pick a BEA Supplied SDKs, everything works just fine.
Someone can give a hand on that? It seems like Bea WebLogic 8.1 and JDK 1.6 are not compatible. Completely stacked here.
Regards.
Full Exception
EJB Exception: : java.lang.NoClassDefFoundError: java/lang/StringBuilder
at robosuite.wizard.jws5a1dbbea00000001.ApiKapowIN.toString(ApiKapowIN.java:141)
at java.lang.String.valueOf(String.java:2131)
at java.lang.StringBuffer.append(StringBuffer.java:370)
at com.bea.wlw.runtime.core.context.WlwThreadContext.logInvoke(WlwThreadContext.java:363)
at com.bea.wlw.runtime.core.context.WlwThreadContext.startInvocation(WlwThreadContext.java:608)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:414)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:248)
at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:198)
at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:153)
at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62)
at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:160)
at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100)
at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161)
at com.bea.wlw.runtime.core.dispatcher.Dispatcher.dispatch(Dispatcher.java:49)
at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executePostRequest(HttpServerHelper.java:713)
at com.bea.wlw.runtime.core.dispatcher.HttpServer.doPost(HttpServer.java:49)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6456)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Even if it is a very naive question but I just cannot get it worked, what do you mean by using jdk 1.5 on client side?
I guess client side is completely out of WLS so the jdk to be used on the client side is not set in the environment.
However, the Exception Im getting is on the server side, when it tries to run the code automatically generated from Kapow Mashup Server 6.3. That code is embedded in a jar file, but it seems it makes a call to the java.lang.StringBuilder class which as said before, it is only available from jdk 1.5 onwards.
Should I contact Kapow Mashup Server support to see how the sample code is generated or I am missing something?
Regards.

How to install oracle xsql servlet on bea weblogic 5.1

 Hi there,
 I tried to install oracles xsql servlet (1.0.4.1) on bea weblogic 5.1 without
 any success.
 in weblogic.properties I started with:
 weblogic.httpd.webApp.xsql=c:\\weblogic\\myserver\\servletclasses\\xsql
 And in this dir I have WEB-INF with the following web.xml:
 <?xml version="1.0" encoding="ISO-8859-1"?>
 <!DOCTYPE web-app
 PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
 "http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">
 <web-app>
 <servlet>
 <servlet-name>oracle-xsql-servlet</servlet-name>
 <servlet-class>oracle.xml.xsql.XSQLServlet</servlet-class>
 </servlet>
 <servlet-mapping>
 <servlet-name>oracle-xsql-servlet</servlet-name>
 <url-pattern> *.xsql </url-pattern>
 </servlet-mapping>
 </web-app>
 So the xsql extension is mapped to the named servlet which is found in a jar file
 contained in subdirectory lib.
 The problem is that the general mapping of *.xsql extension to specified class
 does not work at all. And there are no errors...
 Application server just presents me with the content of the xsql file instead
 of executing servlet whith the xsql file as input.
 Any ideas??
 Thanx in advance.
 JK


What kind of problem do you have?
If it's not connected with JDBC, you'd better post your question
in webservices newsgroup.
Regards,
Slava Imeshev
"leopld goess" <[email protected]> wrote in message
news:[email protected]..
hy out there.
i've been working with apache soap on wl 5.1 for a while now, and
everything seems to be working allright- as long as i don't try to
install a servicepack, namely sp8 or sp10. if i do that, the entire
soap service fails to deploy.
any ideas...
thanx
leopold

Error in shutdown script for bea weblogic

We have this error in the shutdown script of our bea weblogic:
./stopWebLogic.sh[33]: -Xms256m: not found.
using the Oracle OCI database driver
Shutdown initiated
The shutdown sequence has been initiated.the script is as follows:
echo "using the Oracle OCI database driver"
export ORACLE_HOME=/opt/oracle/product/8.1.7
export NLS_LANG=AMERICAN_AMERICA.UTF8
export ORACLE_CLIENT_VERSION=817
export ORACLE_API_VERSION=8
PATH=$PATH:$ORACLE_HOME/bin
SHARED_LIBRARY_PATH=$WEBLOGIC_HOME/lib/hpux11:$WEBLOGIC_HOME/lib/hpux11/oci$ORACLE_CLIENT_VERSION\_$ORACLE_API_VERSION:$ORACLE
_HOME/lib
PATH=$JDK_HOME/bin:$PATH
export PATH
# Set application specific variables
DOMAIN_NAME=eGovStarters
SERVER_NAME=MyServer
WLS_PW=weblogic
# change to domain directory
cd $WEBLOGIC_HOME/config/$DOMAIN_NAME
# Allow other users in group to see created files - i.e. logfiles
umask 027
# Set system classpath initially to contain WebLogic product JARs
CLASSPATH=$WEBLOGIC_HOME:$WEBLOGIC_HOME/lib/weblogic.jar
#!/bin/sh
# Weblogic start script for egovernment
# Based on Colin Brick's initial version
# Modified 02/04/03 - Colin Brick
#       - included settings for Oblix from using SSO Assembly Test as example
# Set General environment variables (Should normally not be changed)
#Java settings
JDK_HOME=/opt/bea/jdk131/
export JDK_HOME
JAVACMD=java
JAVA_OPTIONS=""-server -Xms1024m -Xmx1024m -Xmn320m -XX:SurvivorRatio=8 -Xverbosegc:file=/opt/bea/wlserver6.1/config/eGovStart
ers/logs/gc.log -Dweblogic.system.gc.enabled=false ""
export JAVA_OPTIONS
WEBLOGIC_PORT=51080
#Bea settings
BEA_HOME=/opt/bea
export BEA_HOME
WEBLOGIC_HOME=/opt/bea/wlserver6.1
export WEBLOGIC_HOME
BEA_SECURITY_POLICY=/opt/bea/wlserver6.1/lib/weblogic.policy
export BEA_SECURITY_POLICY
#Oracle settings
echo "using the Oracle OCI database driver"
export ORACLE_HOME=/opt/oracle/product/8.1.7
export NLS_LANG=AMERICAN_AMERICA.UTF8
export ORACLE_CLIENT_VERSION=817
export ORACLE_API_VERSION=8
PATH=$PATH:$ORACLE_HOME/bin
SHARED_LIBRARY_PATH=$WEBLOGIC_HOME/lib/hpux11:$WEBLOGIC_HOME/lib/hpux11/oci$ORACLE_CLIENT_VERSION\_$ORACLE_API_VERSION:$ORACLE
_HOME/lib
PATH=$JDK_HOME/bin:$PATH
export PATH
# Set application specific variables
DOMAIN_NAME=eGovStarters
SERVER_NAME=MyServer
WLS_PW=weblogic
# change to domain directory
cd $WEBLOGIC_HOME/config/$DOMAIN_NAME
# Allow other users in group to see created files - i.e. logfiles
umask 027
# Set system classpath initially to contain WebLogic product JARs
CLASSPATH=$WEBLOGIC_HOME:$WEBLOGIC_HOME/lib/weblogic.jar
domain_NAME=eGovStarters
SERVER_NAME=MyServer
WLS_PW=weblogic
# change to domain directory
cd $WEBLOGIC_HOME/config/$DOMAIN_NAME
# Allow other users in group to see created files - i.e. logfiles
umask 027
# Set system classpath initially to contain WebLogic product JARs
CLASSPATH=$WEBLOGIC_HOME:$WEBLOGIC_HOME/lib/weblogic.jar
#Set the shared library path
if [ -n "$SHLIB_PATH" ]; then
        SHLIB_PATH=$SHLIB_PATH:$SHARED_LIBRARY_PATH
else
        SHLIB_PATH=$SHARED_LIBRARY_PATH
fi
export SHLIB_PATH
# Start weblogic
# change to weblogic home
cd $WEBLOGIC_HOME
PATH=$WL_HOME/bin:$JAVA_HOME/jre/bin:$JAVA_HOME/bin:$PATH
$JAVACMD -classpath $CLASSPATH -Dbea.home=$BEA_HOME -Dweblogic.Domain=$DOMAIN_NAME -Dweblogic.Name=MyServer weblogic.Admin -ur
l t3://localhost:$WEBLOGIC_PORT -username system -password $WLS_PW SHUTDOWNIt has obviously something to do with the line
JAVA_OPTIONS=""-server -Xms1024m -Xmx1024m -Xmn320m -XX:SurvivorRatio=8 -Xverbosegc:file=/opt/bea/wlserver6.1/config/eGovStart
ers/logs/gc.log -Dweblogic.system.gc.enabled=false ""I googled for this Xms1024m, Xmx1024m and it turns out to be for memory management for the java virtual machine.
I don't know why it sais it can't find "-Xms256m" since it's not in the script.
Anyone with some experience in this field who can help me out?

./stopWebLogic.sh[33]: -Xms256m: not found.
this can be produced by something like this:
javaoptions="-Xms256m" // or other option too
$javacmd $javaoptions
Now if javacmd has not been set, then $javacmd will be evaluated to the empty string, and the program to look for is the first part in $javaoptions, -Xms256m in our case.

Trouble defining BAM Enterprise Message Source for BEA WebLogic Server

Hi all,
I've just started to play a little with Oracle BAM Architect.
I've WLS 10.0 and Oracle BAM Architect 10g release 3.
On Oracle BAM Architect I've defined an Enterprise Message Source for BEA WebLogic Server as follows:
Name: ALSBSource
Owner: ...
Type: BEA WebLogic Server
Initial context factory: weblogic.jndi.WLInitialContextFactory
JNDI Service Provider URL: t3://mypc:7001
TopicConnectionFactory name: com.myConnectionFactory
Topic name: com.myBAMTopic
JMS message type: TextMessage
Durable subscriber name: BAMSubscriber
Client ID: BAMSubscriber
Name | Flow name | Type | Max size | Formatting
content | BAM | String | 1024 | (none)
On WLS 10.0 I've defined the required JMS stuff.
On Oracle Design Studio I've defined a plan that includes:
- an Oracle BAM Enterprise Message Receiver from which I've selected the above 'ALSBSource' Enterprise Message Source
- a simple Grid
I've connected the BAM Enterprise Message Receiver to the Grid and clicked on 'Update' button.
When I try to publish a message on 'com.myBAMTopic' I don't see anything on the grid defined in the Oracle Design Studio.
The first question is about the definition of an Enterprise Message Source for BEA WebLogic Server in the Oracle BAM Architect.
I did not change the Oracle BAM Architect classpath or Oracle Design Studio classpath adding the weblogic.jar, because no error has been raised during the configuration of the message source and the plan. Should I update Oracle classpath with the weblogic.jar ?
Did I forget any other step ?
I thank you in advance for any feedback.
Regards
ferp

ferp - I got this to work with
JNDI Service Provider URL: http://localhost
When I add the port
JNDI Service Provider URL: http://localhost:23891
I cannot get my EMS to start.
Hopefully this should fix your issue.
Sudeep.

BEA WebLogic JRockit(TM) 1.4.2_03 SDK Dump on linux

===== BEGIN DUMP =============================================================
JRockit context dump produced after 0 days, 00:36:09 on Mon May 31 11:31:15 2004
If you see this dump, please send it, along with as much
information as you can on your system setup and the program
you were running, to [email protected]. Please include the
file jrockit.29196.dump from the current directory in the bug
report. Thank you.
No core file will be created because core dumps have been
disabled. To enable core dumping, try "ulimit -c unlimited"
before starting JRockit again.
Error Message: Null pointer exception in native code
Signal info : si_signo=11, si_code=1
Version : ari-24879-20031212-1523-linux-ia32
Threads / GC : Native Threads, GC strategy: parallel
: mmHeap->data = 0x40400000, mmHeap->top = 0x60400000
: mmStartCompaction = 0x42c00000, mmEndCompaction = 0x45400000
Number CPUs : 4
Tot Phys Mem : 1051901952
OS version : Red Hat Linux Advanced Server release 2.1AS (Pensacola)
Linux version 2.4.9-e.3smp ([email protected]) (gcc version
2.96 20000731 (Red Hat Linux 7.2 2.96-108.1)) #1 SMP Fri May 3 16:48:54 EDT 2002
State : JVM is running
Command Line : -Djava.class.path=. -Xms512m -Xmx512m -Dembarcadero.license.valid=true
-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=org.apache.crimson.jaxp.SAXParserFactoryImpl
-Djava.class.path=:run.jar:EmbtOpensource.jar:../lib/crimson.jar:../lib/ext/jcert.jar:../lib/ext/ibmrandomizer.jar:../lib/ext/rhino.jar:../lib/ext/Sprint.jar:../lib/ext/xerces-full.jar:../lib/ext/jtidy-modified.jar:../lib/ext/xalan.jar:../lib/ext/mm.mysql-2.0.14-bin.jar:../lib/ext/jconn2.jar:../lib/ext/classes12.zip:../lib/ext/servlet.jar:../../swift/jars/jms.jar:../../swift/jars/swiftmq.jar:../../swift/jars/dom4j-full.jar:../../swift/jars/SwiftLicense.jar:../lib/ext/oswego-concurrent.jar:../lib/ext/activation.jar:../lib/ext/mail.jar:../lib/ext/jgl3.1.0.jar:../lib/ext/domsdk.jar:../lib/ext/w3cdom1.jar:../lib/ext/xmlsax.jar:../lib/ext/jcifs.jar:
-Xbootclasspath/p:../lib/embtClasses_JROCKIT.jar -Xverify:none -Xgc:parallel -Xnativethreads
-Xnoagent -Dsun.java.command=org.jboss.Main
Environment : JAVA_HOME=(null), java.home=/opt/Extreme/JVM/JROCKIT/jre, java.class.path=:run.jar:EmbtOpensource.jar:../lib/crimson.jar:../lib/ext/jcert.jar:../lib/ext/ibmrandomizer.jar:../lib/ext/rhino.jar:../lib/ext/Sprint.jar:../lib/ext/xerces-full.jar:../lib/ext/jtidy-modified.jar:../lib/ext/xalan.jar:../lib/ext/mm.mysql-2.0.14-bin.jar:../lib/ext/jconn2.jar:../lib/ext/classes12.zip:../lib/ext/servlet.jar:../../swift/jars/jms.jar:../../swift/jars/swiftmq.jar:../../swift/jars/dom4j-full.jar:../../swift/jars/SwiftLicense.jar:../lib/ext/oswego-concurrent.jar:../lib/ext/activation.jar:../lib/ext/mail.jar:../lib/ext/jgl3.1.0.jar:../lib/ext/domsdk.jar:../lib/ext/w3cdom1.jar:../lib/ext/xmlsax.jar:../lib/ext/jcifs.jar:,
java.library.path=/opt/Extreme/JVM/JROCKIT/jre/lib/i386/jrockit:/opt/Extreme/JVM/JROCKIT/jre/lib/i386:/opt/Extreme/JVM/JROCKIT/jre/../lib/i386::./../lib
C Heap : Good; no memory allocations have failed
Registers:
EAX = 0004001c EBX = 61af0a6c
ECX = 09abb501 EDX = 00040014
ESI = 61af0a6c EDI = 098172b0
ESP = 628e6ed4 EIP = 4026d313
EBP = 00000000 EFL = 00010246
CS = 0023 DS = 002b ES = 002b
SS = 002b FS = 017f GS = 017f
Stack:
628e6ed4 :61af0aa4 61af0a6c 00000001 0811a3b0 628e6fd8 628e6fcc
628e6eec :0000064a 4029d4dd 61af0a6c 628e6f20 00000000 4029b6db
628e6f04 :61af0a98 61af0c18 628e6fcc 61af0a6c 00000001 628e6f90
628e6f1c :628e6f20 00000000 61af0a6c 628e6fcc 61af0a98 4029cf93
628e6f34 :0811a3b0 61af0a6c 61af0a98 61af0c18 00000020 628e6fcc
628e6f4c :0000000b 00000000 00000000 628e6fcc 0000000b 628e70c4
628e6f64 :61571ed8 61af0a28 00040010 4029b32c 61af0a28 628e6fcc
628e6f7c :0000000b 6274b000 00000000 00000000 6276b000 00000000
628e6f94 :00000000 00000000 00000000 4029b541 628e6fcc 61571ed8
628e6fac :628e70c4 628e7030 4003b918 00000000 61ffeeb4 628e701c
628e6fc4 :00000000 6276a580 62090d58 0811a3b0 61571ed8 00000002
628e6fdc :628e70c4 00000000 00000000 628e7030 00000000 09abb64a
628e6ff4 :61584110 628e70b0 628e701c 40030b53 0000000b 628e7030
628e700c :628e70b0 40030b0a 01b80000 00040000 61571ed8 40091950
628e7024 :0000000b 628e7030 628e70b0 0000000b 00000000 00000001
628e703c :00040010 00000000 00000000 00000000 00000000 00000000
628e7054 :00000000 00000000 00000000 00000000 00000000 00000000
628e706c :00000000 00000000 00000000 00000000 00000000 00000000
628e7084 :00000000 00000000 00000000 00000000 00000000 00000000
628e709c :00000000 00000000 00000000 00000000 00000000 00000000
628e70b4 :00000000 628e53a0 00000000 00002000 0000017f 0000017f
628e70cc :0000002b 0000002b 61ffeeb4 00040000 61571ed8 0004000c
628e70e4 :01b80000 00000000 00000000 00000000 0000000e 00000004
628e70fc :09abb64a 00000023 00010246 0004000c 0000002b 628e7124
628e7114 :80000000 00040010 80000000 00000000 ffff037f ffff0020
628e712c :ffffffff 401e6430 00a70023 403545c8 0000002b 00000310
628e7144 :00000000 1008ffff 00001010 ffff0000 10101010 00000000
628e715c :0000ffff 45000000 3ffefb04 00000000 00000000 00000000
628e7174 :00000000 4008fa00 cccccccd bb3ac6cc a9804014 1f822d80
628e718c :4003beb0 00000020 0020037f 00a70000 401e6430 00000023
628e71a4 :403545c8 0000002b 00001f80 0000ffff 00000310 00000000
628e71bc :0000ffff 00000000 10101008 00000000 0000ffff 00000000
628e71d4 :10101010 00000000 0000ffff 00000000 00000000 fb044500
628e71ec :00003ffe 00000000 00000000 00000000 00000000 00000000
628e7204 :00000000 fa000000 00004008 00000000 cccccccd bb3ac6cc
628e721c :00004014 00000000 2d80a980 beb01f82 00004003 00000000
628e7234 :00000000 00000000 00000000 00000000 00000000 00000000
628e724c :00000000 00000000 00000000 00000000 00000000 00000000
628e7264 :00000000 00000000 00000000 00000000 00000000 00000000
628e727c :00000000 00000000 00000000 00000000 00000000 00000000
628e7294 :00000000 00000000 00000000 00000000 00000000 00000000
628e72ac :00000000 00000000 00000000 00000000 00000000 00000000
628e72c4 :00000000 00000000 00000000 00000000 00000000 00000000
628e72dc :00000000 00000000 00000000 00000000 00000000 00000000
628e72f4 :00000000 00000000 00000000 00000000 00000000 00000000
628e730c :00000000 00000000 00000000 00000000 00000000 00000000
628e7324 :00000000 00000000 00000000 00000000 00000000 00000000
628e733c :00000000 00000000 00000000 00000000 00000000 00000000
628e7354 :00000000 00000000 00000000 00000000 00000000 00000000
628e736c :00000000 00000000 00000000 00000000 00000000 00000000
628e7384 :00000000 00000000 00000000 00000000 00000000 00000000
628e739c :00000000 00002008 00000031 00000000 4026b824 00000000
628e73b4 :00000003 08fe1334 08fe1334 0a518380 62974e50 00000001
628e73cc :00000000 00000030 00000021 628e73f8 00000000 620c9b30
628e73e4 :00000000 0a0fc449 00000000 00000000 00000031 00000000
628e73fc :4026b824 00000000 00000003 09e29198 09e29198 0a0fc030
628e7414 :628e73d8 00000001 6254c6f8 00000030 00000019 00000000
628e742c :09b38a24 0000000f 7afa2e87 00000000 000000b1 6555fa28
628e7444 :66d645e0 02002000 00000000 00000000 40000000 00000000
628e745c :00000000 00000000 00000000 00000000 00000000 00000000
628e7474 :00000000 00000000 00000000 00000000 00000680 00000050
628e748c :00000050 00000013 00000000 00000000 00000000 00000000
628e74a4 :00000000 00000000 00000000 00000000 00000000 00000000
628e74bc :00000000 00000000 00000000 00000000 00000000 00000000
628e74d4 :00000000 000000a0 00000010 622450f0 622450f0 000000b0
628e74ec :00000020 61aaba28 629d6848 675ede88 00000021 00000021
628e7504 :00000001 00000020 00000039 62fbcf60 629e56d8 00020000
628e751c :00000000 00000000 00000000 0012f712 0000769a 60d4c920
628e7534 :00000000 00000000 00000000 00000038 00000050 2f6d6f63
628e754c :61626d65 64616372 2f6f7265 72747865 2f656d65 69726373
628e7564 :6e697470 6f6e2f67 2f736564 656c6552 45657361 6e69676e
628e757c :72615665 65646f4e 00003124 00000000 00000000 00000050
628e7594 :00000019 00000000 09b70094 00000006 abe4e85a 00000000
628e75ac :00000029 00000000 4026b824 00000000 00000003 09afc7a8
628e75c4 :09afc7a8 09abfce0 62257390 00000029 00000011 54746567
628e75dc :65677261 00007374 00000011 45505954 54414e5f 00455649
628e75f4 :000003c1 66d07cc8 65548cf0 00000000 00000000 00000000
628e760c :00000000 00000000 00000000 00000000 00000000 00000000
628e7624 :00000000 00000000 00000000 00000000 00000000 00000000
628e763c :00000000 00000000 00000080 00000000 00000000 00000000
628e7654 :00000000 00000000 00000000 00000000 00000000 00000000
628e766c :00000000 00000000 00000000 00000000 00000000 00000000
628e7684 :00000000 00000000 00000000 00000000 00000000 00000000
628e769c :00000000 00000000 00000000 00000000 00000000 00000000
628e76b4 :00000000 00000000 00000000 00000000 00000000 00000000
628e76cc :00000000 00000000 00000000 00000000 00000000 00000000
Code:
4026d213 :83ffffff 5e5b20c4 c314c483 14ec8390 5c8b5356 748b2424
4026d22b :438b2024 04f8830c c0310b75 b48d54eb 00000026 047b8300
4026d243 :832a7400 e853f4c4 00064dbd 5650026a 53f4c483 0649d0e8
4026d25b :10c48300 fe1be850 01b8ffff 83000000 1eeb20c4 fcc48390
4026d273 :c483026a 53026af8 066220e8 10c48300 46e85650 83ffffff
4026d28b :5e5b10c4 c314c483 10ec8390 8b535657 8b20245c 83388b03
4026d2a3 :75020c7b 24538b20 1974d285 408b028b 8b038910 89400440
4026d2bb :428b0843 24438904 000156e9 0c7b8300 8b2f7701 1b40f603
4026d2d3 :8b097401 c0830443 144389fc 488a038b 02c1f61b 538b1474
4026d2eb :01e18004 83fc428d c984f8c2 89c2450f 438b1843 74c08510
4026d303 :0843890c 001043c7 eb000000 04438b08 4389008b 83338b08
4026d31b :448bf8c4 8b502c24 50480843 f767d4e8 830389ff c08510c4
4026d333 :43c70c75 00000004 00dde900 053b0000 40354850 053b1d74
4026d34b :40354854 538b1574 40b70f04 3fff2518 448d0000 43890482
4026d363 :8b5eeb04 b60f044b 548b1a46 438b0c81 fce2830c 7501f883
4026d37b :2043c714 00000001 000003c7 018b0000 eb084389 fcfa8334
4026d393 :03c70f75 00000000 000443c7 eb000000 287b837a c70b7400
4026d3ab :00000003 04538900 8b5069eb 53501042 fcbfe852 c483ffff
4026d3c3 :0c7b8310 8b547502 74c08503 2c508b4e 4774d285 8b04408b
4026d3db :c129084b 1d740a39 00047a83 d0893574 26748d90 08c08300
4026d3f3 :3908c283 83067408 75000478 04428bf0 1774c085 8904408b
4026d40b :428b2443 8b008b04 03891040 4004408b 89084389 5f5e5bf8
Loaded modules:
(* denotes the module causing the exception)
0x08048000-0x0804cd66 /opt/Extreme/JVM/JROCKIT/bin/java
0x40027000-0x40033ec3 /lib/i686/libpthread.so.0
0x4003c000-0x4005db42 /lib/i686/libm.so.6
0x4005f000-0x4006100c /lib/libdl.so.2
0x40063000-0x40195305 /lib/i686/libc.so.6
0x4019f000-0x403534ef* /opt/Extreme/JVM/JROCKIT/jre/lib/i386/jrockit/libjvm.so
0x403ef000-0x403f82ad /lib/libnss_files.so.2
0x60c4c000-0x60c5bfa5 /opt/Extreme/JVM/JROCKIT/jre/lib/i386/libverify.so
0x60fa3000-0x60fc29cf /opt/Extreme/JVM/JROCKIT/jre/lib/i386/libjava.so
0x60fd4000-0x60fe633a /lib/libnsl.so.1
0x6104d000-0x610a2fcf /opt/Extreme/Hub/jboss/lib/libLinuxInstrumentor.so
0x610ba000-0x610f277b /usr/lib/libstdc++-libc6.2-2.so.3
0x403e4000-0x403ed5cb /lib/libnss_nisplus.so.2
0x619e7000-0x619e9d11 /lib/libnss_dns.so.2
0x619eb000-0x619f8ce5 /lib/libresolv.so.2
Java Thread ID = 0x00001780, Name = PulseRunner
Thread Stack Trace:
at frameIterGetCurrentAndStep2+127(:0)@0x4026d313
If you see this dump, please send it, along with as much
information as you can on your system setup and the program
you were running, to [email protected]. Please include the
file jrockit.29196.dump from the current directory in the bug
report. Thank you.
===== END DUMP ===============================================================
Running web server load test.

I would suggest you grab the latest version of JRockit (1.4.2_04) from
www.bea.com. Also, have a look at the supported platforms at:
http://e-docs.bea.com/wljrockit/docs142/certif.html
Thanks,
/Staffan
wendy yang wrote:
===== BEGIN DUMP =============================================================
JRockit context dump produced after 0 days, 00:36:09 on Mon May 31 11:31:15 2004
If you see this dump, please send it, along with as much
information as you can on your system setup and the program
you were running, to [email protected]. Please include the
file jrockit.29196.dump from the current directory in the bug
report. Thank you.
No core file will be created because core dumps have been
disabled. To enable core dumping, try "ulimit -c unlimited"
before starting JRockit again.
Error Message: Null pointer exception in native code
Signal info : si_signo=11, si_code=1
Version : ari-24879-20031212-1523-linux-ia32
Threads / GC : Native Threads, GC strategy: parallel
: mmHeap->data = 0x40400000, mmHeap->top = 0x60400000
: mmStartCompaction = 0x42c00000, mmEndCompaction = 0x45400000
Number CPUs : 4
Tot Phys Mem : 1051901952
OS version : Red Hat Linux Advanced Server release 2.1AS (Pensacola)
Linux version 2.4.9-e.3smp ([email protected]) (gcc version
2.96 20000731 (Red Hat Linux 7.2 2.96-108.1)) #1 SMP Fri May 3 16:48:54 EDT 2002
State : JVM is running
Command Line : -Djava.class.path=. -Xms512m -Xmx512m -Dembarcadero.license.valid=true
-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=org.apache.crimson.jaxp.SAXParserFactoryImpl
-Djava.class.path=:run.jar:EmbtOpensource.jar:../lib/crimson.jar:../lib/ext/jcert.jar:../lib/ext/ibmrandomizer.jar:../lib/ext/rhino.jar:../lib/ext/Sprint.jar:../lib/ext/xerces-full.jar:../lib/ext/jtidy-modified.jar:../lib/ext/xalan.jar:../lib/ext/mm.mysql-2.0.14-bin.jar:../lib/ext/jconn2.jar:../lib/ext/classes12.zip:../lib/ext/servlet.jar:../../swift/jars/jms.jar:../../swift/jars/swiftmq.jar:../../swift/jars/dom4j-full.jar:../../swift/jars/SwiftLicense.jar:../lib/ext/oswego-concurrent.jar:../lib/ext/activation.jar:../lib/ext/mail.jar:../lib/ext/jgl3.1.0.jar:../lib/ext/domsdk.jar:../lib/ext/w3cdom1.jar:../lib/ext/xmlsax.jar:../lib/ext/jcifs.jar:
-Xbootclasspath/p:../lib/embtClasses_JROCKIT.jar -Xverify:none -Xgc:parallel -Xnativethreads
-Xnoagent -Dsun.java.command=org.jboss.Main
Environment : JAVA_HOME=(null), java.home=/opt/Extreme/JVM/JROCKIT/jre, java.class.path=:run.jar:EmbtOpensource.jar:../lib/crimson.jar:../lib/ext/jcert.jar:../lib/ext/ibmrandomizer.jar:../lib/ext/rhino.jar:../lib/ext/Sprint.jar:../lib/ext/xerces-full.jar:../lib/ext/jtidy-modified.jar:../lib/ext/xalan.jar:../lib/ext/mm.mysql-2.0.14-bin.jar:../lib/ext/jconn2.jar:../lib/ext/classes12.zip:../lib/ext/servlet.jar:../../swift/jars/jms.jar:../../swift/jars/swiftmq.jar:../../swift/jars/dom4j-full.jar:../../swift/jars/SwiftLicense.jar:../lib/ext/oswego-concurrent.jar:../lib/ext/activation.jar:../lib/ext/mail.jar:../lib/ext/jgl3.1.0.jar:../lib/ext/domsdk.jar:../lib/ext/w3cdom1.jar:../lib/ext/xmlsax.jar:../lib/ext/jcifs.jar:,
java.library.path=/opt/Extreme/JVM/JROCKIT/jre/lib/i386/jrockit:/opt/Extreme/JVM/JROCKIT/jre/lib/i386:/opt/Extreme/JVM/JROCKIT/jre/../lib/i386::./../lib
C Heap : Good; no memory allocations have failed
Registers:
EAX = 0004001c EBX = 61af0a6c
ECX = 09abb501 EDX = 00040014
ESI = 61af0a6c EDI = 098172b0
ESP = 628e6ed4 EIP = 4026d313
EBP = 00000000 EFL = 00010246
CS = 0023 DS = 002b ES = 002b
SS = 002b FS = 017f GS = 017f
Stack:
628e6ed4 :61af0aa4 61af0a6c 00000001 0811a3b0 628e6fd8 628e6fcc
628e6eec :0000064a 4029d4dd 61af0a6c 628e6f20 00000000 4029b6db
628e6f04 :61af0a98 61af0c18 628e6fcc 61af0a6c 00000001 628e6f90
628e6f1c :628e6f20 00000000 61af0a6c 628e6fcc 61af0a98 4029cf93
628e6f34 :0811a3b0 61af0a6c 61af0a98 61af0c18 00000020 628e6fcc
628e6f4c :0000000b 00000000 00000000 628e6fcc 0000000b 628e70c4
628e6f64 :61571ed8 61af0a28 00040010 4029b32c 61af0a28 628e6fcc
628e6f7c :0000000b 6274b000 00000000 00000000 6276b000 00000000
628e6f94 :00000000 00000000 00000000 4029b541 628e6fcc 61571ed8
628e6fac :628e70c4 628e7030 4003b918 00000000 61ffeeb4 628e701c
628e6fc4 :00000000 6276a580 62090d58 0811a3b0 61571ed8 00000002
628e6fdc :628e70c4 00000000 00000000 628e7030 00000000 09abb64a
628e6ff4 :61584110 628e70b0 628e701c 40030b53 0000000b 628e7030
628e700c :628e70b0 40030b0a 01b80000 00040000 61571ed8 40091950
628e7024 :0000000b 628e7030 628e70b0 0000000b 00000000 00000001
628e703c :00040010 00000000 00000000 00000000 00000000 00000000
628e7054 :00000000 00000000 00000000 00000000 00000000 00000000
628e706c :00000000 00000000 00000000 00000000 00000000 00000000
628e7084 :00000000 00000000 00000000 00000000 00000000 00000000
628e709c :00000000 00000000 00000000 00000000 00000000 00000000
628e70b4 :00000000 628e53a0 00000000 00002000 0000017f 0000017f
628e70cc :0000002b 0000002b 61ffeeb4 00040000 61571ed8 0004000c
628e70e4 :01b80000 00000000 00000000 00000000 0000000e 00000004
628e70fc :09abb64a 00000023 00010246 0004000c 0000002b 628e7124
628e7114 :80000000 00040010 80000000 00000000 ffff037f ffff0020
628e712c :ffffffff 401e6430 00a70023 403545c8 0000002b 00000310
628e7144 :00000000 1008ffff 00001010 ffff0000 10101010 00000000
628e715c :0000ffff 45000000 3ffefb04 00000000 00000000 00000000
628e7174 :00000000 4008fa00 cccccccd bb3ac6cc a9804014 1f822d80
628e718c :4003beb0 00000020 0020037f 00a70000 401e6430 00000023
628e71a4 :403545c8 0000002b 00001f80 0000ffff 00000310 00000000
628e71bc :0000ffff 00000000 10101008 00000000 0000ffff 00000000
628e71d4 :10101010 00000000 0000ffff 00000000 00000000 fb044500
628e71ec :00003ffe 00000000 00000000 00000000 00000000 00000000
628e7204 :00000000 fa000000 00004008 00000000 cccccccd bb3ac6cc
628e721c :00004014 00000000 2d80a980 beb01f82 00004003 00000000
628e7234 :00000000 00000000 00000000 00000000 00000000 00000000
628e724c :00000000 00000000 00000000 00000000 00000000 00000000
628e7264 :00000000 00000000 00000000 00000000 00000000 00000000
628e727c :00000000 00000000 00000000 00000000 00000000 00000000
628e7294 :00000000 00000000 00000000 00000000 00000000 00000000
628e72ac :00000000 00000000 00000000 00000000 00000000 00000000
628e72c4 :00000000 00000000 00000000 00000000 00000000 00000000
628e72dc :00000000 00000000 00000000 00000000 00000000 00000000
628e72f4 :00000000 00000000 00000000 00000000 00000000 00000000
628e730c :00000000 00000000 00000000 00000000 00000000 00000000
628e7324 :00000000 00000000 00000000 00000000 00000000 00000000
628e733c :00000000 00000000 00000000 00000000 00000000 00000000
628e7354 :00000000 00000000 00000000 00000000 00000000 00000000
628e736c :00000000 00000000 00000000 00000000 00000000 00000000
628e7384 :00000000 00000000 00000000 00000000 00000000 00000000
628e739c :00000000 00002008 00000031 00000000 4026b824 00000000
628e73b4 :00000003 08fe1334 08fe1334 0a518380 62974e50 00000001
628e73cc :00000000 00000030 00000021 628e73f8 00000000 620c9b30
628e73e4 :00000000 0a0fc449 00000000 00000000 00000031 00000000
628e73fc :4026b824 00000000 00000003 09e29198 09e29198 0a0fc030
628e7414 :628e73d8 00000001 6254c6f8 00000030 00000019 00000000
628e742c :09b38a24 0000000f 7afa2e87 00000000 000000b1 6555fa28
628e7444 :66d645e0 02002000 00000000 00000000 40000000 00000000
628e745c :00000000 00000000 00000000 00000000 00000000 00000000
628e7474 :00000000 00000000 00000000 00000000 00000680 00000050
628e748c :00000050 00000013 00000000 00000000 00000000 00000000
628e74a4 :00000000 00000000 00000000 00000000 00000000 00000000
628e74bc :00000000 00000000 00000000 00000000 00000000 00000000
628e74d4 :00000000 000000a0 00000010 622450f0 622450f0 000000b0
628e74ec :00000020 61aaba28 629d6848 675ede88 00000021 00000021
628e7504 :00000001 00000020 00000039 62fbcf60 629e56d8 00020000
628e751c :00000000 00000000 00000000 0012f712 0000769a 60d4c920
628e7534 :00000000 00000000 00000000 00000038 00000050 2f6d6f63
628e754c :61626d65 64616372 2f6f7265 72747865 2f656d65 69726373
628e7564 :6e697470 6f6e2f67 2f736564 656c6552 45657361 6e69676e
628e757c :72615665 65646f4e 00003124 00000000 00000000 00000050
628e7594 :00000019 00000000 09b70094 00000006 abe4e85a 00000000
628e75ac :00000029 00000000 4026b824 00000000 00000003 09afc7a8
628e75c4 :09afc7a8 09abfce0 62257390 00000029 00000011 54746567
628e75dc :65677261 00007374 00000011 45505954 54414e5f 00455649
628e75f4 :000003c1 66d07cc8 65548cf0 00000000 00000000 00000000
628e760c :00000000 00000000 00000000 00000000 00000000 00000000
628e7624 :00000000 00000000 00000000 00000000 00000000 00000000
628e763c :00000000 00000000 00000080 00000000 00000000 00000000
628e7654 :00000000 00000000 00000000 00000000 00000000 00000000
628e766c :00000000 00000000 00000000 00000000 00000000 00000000
628e7684 :00000000 00000000 00000000 00000000 00000000 00000000
628e769c :00000000 00000000 00000000 00000000 00000000 00000000
628e76b4 :00000000 00000000 00000000 00000000 00000000 00000000
628e76cc :00000000 00000000 00000000 00000000 00000000 00000000
Code:
4026d213 :83ffffff 5e5b20c4 c314c483 14ec8390 5c8b5356 748b2424
4026d22b :438b2024 04f8830c c0310b75 b48d54eb 00000026 047b8300
4026d243 :832a7400 e853f4c4 00064dbd 5650026a 53f4c483 0649d0e8
4026d25b :10c48300 fe1be850 01b8ffff 83000000 1eeb20c4 fcc48390
4026d273 :c483026a 53026af8 066220e8 10c48300 46e85650 83ffffff
4026d28b :5e5b10c4 c314c483 10ec8390 8b535657 8b20245c 83388b03
4026d2a3 :75020c7b 24538b20 1974d285 408b028b 8b038910 89400440
4026d2bb :428b0843 24438904 000156e9 0c7b8300 8b2f7701 1b40f603
4026d2d3 :8b097401 c0830443 144389fc 488a038b 02c1f61b 538b1474
4026d2eb :01e18004 83fc428d c984f8c2 89c2450f 438b1843 74c08510
4026d303 :0843890c 001043c7 eb000000 04438b08 4389008b 83338b08
4026d31b :448bf8c4 8b502c24 50480843 f767d4e8 830389ff c08510c4
4026d333 :43c70c75 00000004 00dde900 053b0000 40354850 053b1d74
4026d34b :40354854 538b1574 40b70f04 3fff2518 448d0000 43890482
4026d363 :8b5eeb04 b60f044b 548b1a46 438b0c81 fce2830c 7501f883
4026d37b :2043c714 00000001 000003c7 018b0000 eb084389 fcfa8334
4026d393 :03c70f75 00000000 000443c7 eb000000 287b837a c70b7400
4026d3ab :00000003 04538900 8b5069eb 53501042 fcbfe852 c483ffff
4026d3c3 :0c7b8310 8b547502 74c08503 2c508b4e 4774d285 8b04408b
4026d3db :c129084b 1d740a39 00047a83 d0893574 26748d90 08c08300
4026d3f3 :3908c283 83067408 75000478 04428bf0 1774c085 8904408b
4026d40b :428b2443 8b008b04 03891040 4004408b 89084389 5f5e5bf8
Loaded modules:
(* denotes the module causing the exception)
0x08048000-0x0804cd66 /opt/Extreme/JVM/JROCKIT/bin/java
0x40027000-0x40033ec3 /lib/i686/libpthread.so.0
0x4003c000-0x4005db42 /lib/i686/libm.so.6
0x4005f000-0x4006100c /lib/libdl.so.2
0x40063000-0x40195305 /lib/i686/libc.so.6
0x4019f000-0x403534ef* /opt/Extreme/JVM/JROCKIT/jre/lib/i386/jrockit/libjvm.so
0x403ef000-0x403f82ad /lib/libnss_files.so.2
0x60c4c000-0x60c5bfa5 /opt/Extreme/JVM/JROCKIT/jre/lib/i386/libverify.so
0x60fa3000-0x60fc29cf /opt/Extreme/JVM/JROCKIT/jre/lib/i386/libjava.so
0x60fd4000-0x60fe633a /lib/libnsl.so.1
0x6104d000-0x610a2fcf /opt/Extreme/Hub/jboss/lib/libLinuxInstrumentor.so
0x610ba000-0x610f277b /usr/lib/libstdc++-libc6.2-2.so.3
0x403e4000-0x403ed5cb /lib/libnss_nisplus.so.2
0x619e7000-0x619e9d11 /lib/libnss_dns.so.2
0x619eb000-0x619f8ce5 /lib/libresolv.so.2
Java Thread ID = 0x00001780, Name = PulseRunner
Thread Stack Trace:
at frameIterGetCurrentAndStep2+127(:0)@0x4026d313
If you see this dump, please send it, along with as much
information as you can on your system setup and the program
you were running, to [email protected]. Please include the
file jrockit.29196.dump from the current directory in the bug
report. Thank you.
===== END DUMP ===============================================================
Running web server load test.

Crystal Reports in Java with BEA Weblogic (test drive)

Hello, 
 
The question is: What is wrong with Crystal Reports or BEA Weblogic, when they are working together? And how can it be repaired? 
 
I have a project working with reports. Tried to implement it for crystal reports and found an interesting problem. Crystal Reports didn't work with BEA Weblogic as well as with other servers. 1-2 years ago we just took Tomcat and worked with it. Right now we are interested in working with BEA. 
 
Everything works, but much slower than other servers. The best explanation is just a my tries in the end of the post. I hope some clever man helps me to option Weblogic or at least explains what is wrong. 
 
Test results are: 
 
- Apache Software Foundation - Tomcat 6.0: 
~3 sec for clientDoc.open(reportName, OpenReportOptions._openAsReadOnly); 
~1 sec for crystalReportPageViewer.processHttpRequest(request, response, application, null); 
 
- OC4J - Oracle Containers for J2EE 10g (10.1.3.3.0): 
~4 sec for clientDoc.open(reportName, OpenReportOptions._openAsReadOnly); 
~1 sec for crystalReportPageViewer.processHttpRequest(request, response, application, null); 
 
- Jetty 7.0.0.pre5: 
~2 sec for clientDoc.open(reportName, OpenReportOptions._openAsReadOnly); 
~0 sec for crystalReportPageViewer.processHttpRequest(request, response, application, null); 
 
- BEA Weblogic 9.2: 
~30 sec for clientDoc.open(reportName, OpenReportOptions._openAsReadOnly); 
~8 sec for crystalReportPageViewer.processHttpRequest(request, response, application, null); 
 
simple_cr_webapp.war (30 MB) can be downloaded [here|http://rapidshare.com/files/221096566/simple_cr_webapp.war.html] or [here|http://math.ut.ee/~a30858/simple_cr_webapp.war]: 
crystalreportviewers //all viewers for 2.0
WEB-INF
classes
CRConfig.xml //see WAR - without key, only sets timeout and report location
lib //all libraries for Eclipse plugin's web-app + j2ee.jar
web.xml //see WAR - generated by Eclipse plugin
sample.jsp //see WAR - generated by Eclipse plugin
sample.rpt //"Consolidated Balance Sheet.rpt" from Eclipse plugin's web-app samples
 
P.S. It is also suites if someone gives a simple project with CR, that works well. I really need to get solution for this problem, so any advises are expected. 

I also tried for different java vendors on BEA Weblogic 9.2.
Results for Jrockit are above: 30 sec and 8 sec
Results for Sun are worse than JRockit: 50 sec and 10 sec
JRockit:
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
BEA JRockit(R) (build R26.0.0-189_CR269406-59389-1.5.0_04-20060322-1120-win-ia32, )
JAVA Memory arguments: -Xms500m -Xmx1000m
Sun:
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode)
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=256m -XX:MaxPermSize=256m

Bea weblogic server 6.1 - Failure in process sockets - Java.lang.NoSuchmethod Error

Hi
I have installed the BEA weblogic server 6.1 service pack 4 as part of PIA (PeopleSoft
Internet Architecture) installation for PeopleSoft 8.8.
After starting the weblogic server, When I type the
http://localhost:12080 (http port number 12080) ideally it should take me to
the BEA home page, but it is throwing an error in the log file.
" Failure in Process sockets - Get Data Java.lang.nosuchmethod error"
Your help is very much appreciated.
Any pointers are welcome.
Thanks
Aswartha

I had similar problems with my install of Weblogic 6.1 sp4. I am installing PS
HRMS 8.8 sp1
and PeopleTools 8.44 Patch 2 (Patch 2 is required for install) Peoplesoft sent
me Weblogic 8.1
with my new Tools 8.44. This version and installation is light years ahead of
Weblogic 6.1. If
you are able to load the new version of Weblogic and Tuxedo, it is worth it.
If not, you may want to check to see if your JAR file was installed correctly.
(The new version
of WL doesn't make you unzip your JAR files for the install.)
In the command line for unzipping the JAR file, make sure you type the phrase
EXACTLY as
shown IT IS CASE SENSITIVE. I messed with this for two hours until I saw that
I wasn't putting
a capital letter in one of the words where I should have been.
Hope this helps.
"Aswarth" <[email protected]> wrote:
>
Hi
I have installed the BEA weblogic server 6.1 service pack 4 as part of
PIA (PeopleSoft
Internet Architecture) installation for PeopleSoft 8.8.
After starting the weblogic server, When I type the
http://localhost:12080 (http port number 12080) ideally it should take
me to
the BEA home page, but it is throwing an error in the log file.
" Failure in Process sockets - Get Data Java.lang.nosuchmethod error"
Your help is very much appreciated.
Any pointers are welcome.
Thanks
Aswartha

BEA WebLogic 10.3 JMS Jar version

Similar Messages

Maybe you are looking for