WLS 6.1SP3

I am trying to run SP3 since I saw that it fixed a problem with XA and EIS
          failures, but I'm running into something that I didn't see with SP2. I have
          3
          RAR files, one base RAR and two others using ra-link-ref to point to the
          base one. I am seeing 6 ManagedConnectionFactories being created.
          There are 2 calls for each RAR file, but this doesn't seem to happen all
          the time, sometimes its one others its 2 for a couple and 1 for another.
          If I go in and clear the config.xml, and re-run it works like it should. I
          am
          running in Development mode. It doesn't happen all the time and I don't
          know what causes this.
          Eric

          Eric,
          Thanks for reporting this. We will submit a bug against this for tracking.
          Deb
          >There are times when this happens, that the factories don't get deployed
          >correctly so I get an unable to resolve 'eis.xxxxx'. I can then delete
          >the
          >entries in the config.xml, restart and everything works. It is very
          >inconsistent.
          >
          >Eric
          >"Eric Hardesty" <[email protected]> wrote in message
          >news:[email protected]..
          >> I am trying to run SP3 since I saw that it fixed a problem with XA
          >and EIS
          >> failures, but I'm running into something that I didn't see with SP2.
          > I
          >have
          >> 3
          >> RAR files, one base RAR and two others using ra-link-ref to point to
          >the
          >> base one. I am seeing 6 ManagedConnectionFactories being created.
          >> There are 2 calls for each RAR file, but this doesn't seem to happen
          >all
          >> the time, sometimes its one others its 2 for a couple and 1 for another.
          >> If I go in and clear the config.xml, and re-run it works like it should.
          >I
          >> am
          >> running in Development mode. It doesn't happen all the time and I
          >don't
          >> know what causes this.
          >>
          >> Eric
          >>
          >>
          >
          >

Similar Messages

Does the JRE 1.5 is supported for the WLS 8.1SP3 client

Hi,
Does the JRE 1.5 is supported for the WLS 8.1SP3 client
Regards,
Ahamad

Hi,
Does the JRE 1.5 is supported for the WLS 8.1SP3 client
Regards,
Ahamad

Getting PetStore to run in WLS 6.1sp3 on Mac OS X 10.2.6?

Hi all!
I've read with great interest all the articles relating to WLS running on OS X.
It's great to read this as I am pretty much the only guy in the entire organisation
here trying to keep using his Mac.
I was able to get WLS admin server to run on my PowerBook running OS X 10.2.6.
However, after stopping the admin server and trying to start the PetStore demo
server, I've got a few exceptions that prevent the server from starting.
So, I was wondering how you people, running WLS 6.1 on OS X have configured your
start scripts. When trying to use the standard jdk that comes with WLS, I'm getting
an exception. When using the Apple 1.3.1 jdk, I'm getting another exception about
a missing 'libmuxer' library. Basically, what set of libraries are you using?
Thanks in advance!
-Laurent.

Thanks for the reply, Mark. I finally figured it out by replacing all references
to the WebLogic provided 1.3.1 jdk by the one provided by Apple and all is well
now!
Thanks!
-Laurent.
"Mark Griffith" <[email protected]> wrote:
All you should need (with 7.0 and 8.1) to start WLS is
"java weblogic.Server"
As long as your have your classpath set.
export CLASSPATH=$WLHOME:$WLHOME/server/lib/weblogic.jar
On my windoze box WLHOME=C:/bea/wls81/weblogic81
Libmuxer is our native socket muxing code, you don't need it to run you'll
just use java muxing.
Sam just posted the libs on another thread.
Any other exceptions?
cheers
mbg
"Laurent Daudelin" <[email protected]> wrote in message
news:3eccefbe$[email protected]..
Hi all!
I've read with great interest all the articles relating to WLS runningon
OS X.
It's great to read this as I am pretty much the only guy in the entireorganisation
here trying to keep using his Mac.
I was able to get WLS admin server to run on my PowerBook running OSX
10.2.6.
However, after stopping the admin server and trying to start the PetStoredemo
server, I've got a few exceptions that prevent the server from starting.
So, I was wondering how you people, running WLS 6.1 on OS X haveconfigured your
start scripts. When trying to use the standard jdk that comes withWLS,
I'm getting
an exception. When using the Apple 1.3.1 jdk, I'm getting anotherexception about
a missing 'libmuxer' library. Basically, what set of libraries areyou
using?
Thanks in advance!
-Laurent.

WLS 6.1sp3 classloader loads all archives within WEB-INF/lib/*

          Within the lib directory of my webapp, I have several different versions of myarchive.jar.
          In WLS 6.0 I would keep older version within the lib directory but renaming them
          so that the current release would get loaded.
          $WL_HOME/config/mydomain/applications/myapp/WEB-INF/lib
          myarvhive.jar
          myarvhive.jar_bf_2.3release
          myarvhive.jar_bf_2.4release
          myarvhive.jar_bf_2.5release
          In WLS 6.0 this method of storing the previous archive version was safe. However,
          now after implementing WLS 6.1, I only can have the current archive release within
          the lib directory. If the previous versions are store within the lib, old methods
          are used.
          I do not understand the WLS classloader behavior and why is it different from
          WLS 6.0?
          wls- WebLogic Server 6.1 SP3
          platform- OSF1 localhost V5.1 1885 alpha
          jvm- Classic VM (build 1.3.0-1, native threads, jit)


          Within the lib directory of my webapp, I have several different versions of myarchive.jar.
          In WLS 6.0 I would keep older version within the lib directory but renaming them
          so that the current release would get loaded.
          $WL_HOME/config/mydomain/applications/myapp/WEB-INF/lib
          myarvhive.jar
          myarvhive.jar_bf_2.3release
          myarvhive.jar_bf_2.4release
          myarvhive.jar_bf_2.5release
          In WLS 6.0 this method of storing the previous archive version was safe. However,
          now after implementing WLS 6.1, I only can have the current archive release within
          the lib directory. If the previous versions are store within the lib, old methods
          are used.
          I do not understand the WLS classloader behavior and why is it different from
          WLS 6.0?
          wls- WebLogic Server 6.1 SP3
          platform- OSF1 localhost V5.1 1885 alpha
          jvm- Classic VM (build 1.3.0-1, native threads, jit)

Change request #063743 & WLS 6.1sp3

          Change request #063743 in the WLS sp4 resolved JMS issue list says:
          "Fixed a problem with Message Driven Beans not acknowledging object messages"
          Are there any more details on this? Would this affect any MDB onMessage() operation,
          or just those that throw exceptions? Would this affect MapMessages as well as
          ObjectMessages? Also, is this related to the negative numbers I see in the "Bytes
          Pending" column after my message is processed? What sort of problems do the unacknowledged
          messages usually cause for people?
          Any thoughts would be much appreciated!
          -JT


Actually I think the text on this one is wrong, or at least
          misleading. I just read the internal notes on the problem
          and it seems that the actual problem was that
          topic MDBs were not acknowledging messages if max-beans-in-free-pool
          was explicitly set to 1 in the weblogic descriptor, regardless
          of message type. Which leads me to guess you could work-around
          the problem temporarily by making the topic MDB transactional or
          increasing max-beans-in-free-pool higher than 1. Not 100%
          sure. Contact customer support to nail it down. (The newsgroups
          are not run by customer support - instead they are run by various
          volunteers.)
          Note that SP4 introduces another problem that breaks
          acknowledgement rather than fixes it. You will do best to
          go directly to SP5 (do not pass go, do not collect $200). Or
          contact customer support for the patch on SP4. I do not
          have the change request number for that one.
          Tom
          Jason Taylor wrote:
          > Change request #063743 in the WLS sp4 resolved JMS issue list says:
          > "Fixed a problem with Message Driven Beans not acknowledging object messages"
          >
          > Are there any more details on this? Would this affect any MDB onMessage() operation,
          > or just those that throw exceptions? Would this affect MapMessages as well as
          > ObjectMessages? Also, is this related to the negative numbers I see in the "Bytes
          > Pending" column after my message is processed? What sort of problems do the unacknowledged
          > messages usually cause for people?
          Messages never get deleted. The JMS server eventually runs out
          of memory or or starts to throw quota exceptions.
          When the JMS server is rebooted, messages re-appear.
          >
          > Any thoughts would be much appreciated!
          >
          > -JT

ArrayStoreException in WLS 8.1SP3: Object and inner type of array differs

Has anyone seen this? We seem to get them from time to time, am running WLS 8.1 SP3 on JRockit 1.4.2.03. Stack trace follows.
          cheers
          dim
          <BEA-000802> <ExecuteRequest failed
          java.lang.ArrayStoreException: Object and inner type of array differs.
          java.lang.ArrayStoreException: Object and inner type of array differs
          at weblogic.rjvm.BasicOutboundRequest.sendReceive()Lweblogic.rmi.spi.InboundResponse;(BasicOutboundRequest.java:108)
          at weblogic.rmi.internal.BasicRemoteRef.invoke(Ljava.rmi.Remote;Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;[Ljava.lang.Object;Ljava.lang.reflect.Method;)Ljava.lang.Object;(BasicRemoteRef.java:137)
          at weblogic.cluster.replication.ReplicationManager_813_WLStub.update(Lweblogic.cluster.replication.ROID;ILjava.io.Serializable;)V(Unknown Source)
          at weblogic.cluster.replication.ReplicationManager.updateSecondary(Lweblogic.cluster.replication.ROID;Ljava.io.Serializable;Ljava.lang.String;)Ljava.lang.Object;(ReplicationManager.java:811)
          at weblogic.servlet.internal.session.ReplicatedSessionData.syncSession()V(ReplicatedSessionData.java:490)
          at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Ljavax.servlet.http.HttpSession;)V(ReplicatedSessionContext.java:184)
          at weblogic.servlet.internal.ServletRequestImpl.syncSession()V(ServletRequestImpl.java:2471)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic.servlet.internal.ServletRequestImpl;Lweblogic.servlet.internal.ServletResponseImpl;)V(WebAppServletContext.java:3679)
          at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel.ExecuteThread;)V(ServletRequestImpl.java:2630)
          at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
          at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
          at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
          Caused by: java.lang.ArrayStoreException: Object and inner type of array differs
          at java.io.ObjectInputStream.readObject(Unknown Source)
          at java.util.HashMap.readObject(Unknown Source)
          at java.io.ObjectInputStream.readSerialData(Unknown Source)
          at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
          at java.io.ObjectInputStream.readObject0(Unknown Source)
          at java.io.ObjectInputStream.readSerialData(Unknown Source)
          at java.io.ObjectInputStream.readObject(Unknown Source)
          at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:120)
          at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:117)
          at weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
          at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
          ... 3 more

You have to be careful how you define your complex elements, define complex elements outside of the root element or in a seperate file and reference them.
          While the following is syntactically correct, in weblogic you will result in the error you had previously
          <element>
          <complex type>
          </complex type>
          </element>
          Instead do
          <element type="ir:ComEx">
          <complex type name="ComEx"></complex type>
          outside of the root element
          Had this exact same problem today, this is how I fixed it

JMS Persistence with WLS 8.1SP3 in a cluster

I have been following the BEA recommendations. I have configured my JMS to write to an Oracle DB for JMS persistence. This is in a clustered environment. I have had one server go down and then come back. During the outage or right before the outage there were request in the JMS queue. I would assume when the server that failed came back up it would then receive and process the JMS request that were waiting in the DB. That doesn't seem to be happening. My setup is one JMS topic for out bound. The JMS queue is set up for internal traffic. It uses Message Beans. We are also using XADrivers.
The setup is WLS8.1SP3 on Solaris hitting an Oracle 9 db. Please forward me any questions or suggestions. Thank you in advance.

WebLogic JMS won't automatically recover messages that enter an "in-doubt" state due to persistence errors that occur while they are being sent or received. To recover such messages, JMS needs to be restarted. You can contact customer support for an 8.1 sample program that automatically restarts JMS (without restarting all of WebLogic) when this problem occurs.
Tom

WLS 8.1sp3 blocked threads halt MDB processing

Under Weblogic Server 8.1 SP3 JMS consumers stop processing the JMS queues. This only started happening following our upgrade from SP2. We had numerous test baselines as well as months of production data to validate this.
          Specifically it appears that internal weblogic threads are blocked, preventing the MDBs (JMS consumers) from being dispatched. This doesn't immediately impact the user experience, but eventually unprocessed JMS messages accumulate and consume heap. You can figure out the rest.
          We had 5 MDBs working on this particular JMS queue, so under moderate traffic all 5 would need to be blocked before the problem was realized.
          As a work around, you'll need to request a patch from BEA. CR188391 appears to resolve this issue. You must request this however. BEA will not contact you - regardless of functional or economic impact.
          Thanks
          -Sean

Sean,
          I've forwarded your comments internally. Usually, one can look in the release notes of future service-packs to see what's been fixed. I would think upgrading from SP3 to sp4, or even sp5 (the latest) would also have fixed the problem.
          Tom, BEA

Performance Monitoring and WLS 8.1 SP3

I've already send this question to
"weblogic.developer.interest.management" with no answer. Maybe it was the
wrong group so I try again here.
Should I open a case to BEA support ?
I'm trying to use the performance monitoring tool on a WLS 8.1 SP3 server.
I've noticed that it is now included in the full distribution of the
platform
(apparently not in the service pack 3 where a separate download is
necessary).
I have installed a the full platform on Win XP SP1 and started the sample
server. After booting, I connect to the console and I try to access the
'Performance
Monitor' settings by clicking on the corresponding item.
I only get garbage and the server logs the following:
<21-Sep-2004 10:20:36 o'clock CEST> <Error> <HTTP> <BEA-101017>
<[ServletContext
(id=259488,name=PerformanceMonitor,context-path=/PerformanceMonitor)] Root
cause
of ServletException.
java.lang.NullPointerException
at
weblogic.management.console.tags.TextTag.getText(TextTag.java:46)
at
weblogic.management.console.tags.LinkTag.doStartTag(LinkTag.java:126)
at
weblogic.management.console.tags.StandardBannerTag.printEnd(StandardB
annerTag.java:186)
at
weblogic.management.console.tags.StandardBannerTag.doEndTag(StandardB
annerTag.java:114)
at jsp_servlet.__prfinstall._jspService(__prfinstall.java:253)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:996)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:419)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:463)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:315)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6452)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3661)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2630)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
--------------- nested within: ------------------
weblogic.management.console.utils.NestedJspException - with nested
exception:
[java.lang.NullPointerException]
at
weblogic.management.console.tags.LinkTag.doStartTag(LinkTag.java:141)
at
weblogic.management.console.tags.StandardBannerTag.printEnd(StandardB
annerTag.java:186)
at
weblogic.management.console.tags.StandardBannerTag.doEndTag(StandardB
annerTag.java:114)
at jsp_servlet.__prfinstall._jspService(__prfinstall.java:253)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:996)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:419)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:463)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:315)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6452)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3661)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2630)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
>
I have a similar problem on Sun Solaris 8 running WLS 8.1SP3 where the
Performance Monitor has been installed separately.
(PMConsoleExt.tar.gz)
any suggestion ?

Looks like a bug to me. I think you should contact support.

XAER_RMERR with oracle thin 9.0.1.4 and wls 6.1 sp3

I am trying to use Oracle Thin 9.0.1.4 Driver in a distributed Transaction and
while trying to call connection.createStatement() I am getting the
following error.
RootCause=[java.sql.SQLException: XA error: XAER_RMERR : A resource
manager error has occured in the transaction branch start() failed on
resource 'CoreJDBCPool' null]
We are using WLS 6.1SP3
Any help on the issue will be really appreciated
here's the simple test that causes this error
<%@ page isErrorPage="false" errorPage="/common/error.jsp" %>
<%@ page import="javax.sql.DataSource" %>
<%@ page import="java.sql.Connection" %>
<%@ page import="java.sql.Statement" %>
<%@ page import="javax.naming.InitialContext" %>
<%@ page import="javax.transaction.UserTransaction" %>
<html>
<body>
Testing update
<p> </p>
<%
Statement stmt = null;;
Connection conn = null;
UserTransaction ut = null;
try {
InitialContext ctx = new InitialContext();
// TODO: add the JNDI name for the datasource here
// get the datasource from the app
DataSource ds = (DataSource)ctx.lookup("jdbc/TrueResolutionDB");
ut =(UserTransaction) ctx.lookup("java:comp/UserTransaction");
ut.begin();
if (ds != null){
// Get a connection to the database
conn = ds.getConnection();
// Get a statement from the connection
stmt = conn.createStatement();
// Execute the Update
int rows = stmt.executeUpdate( "update csr_submission set
userid='wilaw' where submissionseq=436");
// Print how many rows were modified
out.println( rows + " Rows modified" ) ;
ut.commit();
} else {
out.println("datasource is null");
catch( Exception e ){
if (ut != null)
ut.rollback();
out.println(e.toString()) ;
e.printStackTrace();
// Close the statement and the connection
if (stmt != null)
stmt.close() ;
if (conn != null)
conn.close() ;
%>

Hi Bala,
Here is what I remembered - I saw this error when a part of the network
connecting weblogic to oracle was misconfigured, so throughput dropped
from 100Mbit/s to somewhat 64Kbit-sec.
When weblogic message level was set to warning, it was showing lots
of pool's connection refreshes. In my case this error was appearing
after some time. The source of the error is that when a weblogic XA
resource is inactive for 2 minutes, the server delists it and everything
goes south. The workaround for this is to have refresh period a bit less
than 2 minutes, or, better, have an operating network infrastructure :)
As for the settings you provided - they are not optimal. The better
configuration would look like this:
<JDBCConnectionPool
CapacityIncrement="0" 
ConnLeakProfilingEnabled="false" 
DriverName="oracle.jdbc.driver.OracleDriver"
InitialCapacity="40" 
LoginDelaySeconds="1"
MaxCapacity="40"
Name="nonXACoreJDBCPool"
Properties="oracle.jdbc.V8Compatible=true;user=bala;password=bala;dll=ocijdb
c9;protocol=thin"
RefreshMinutes="99999" 
Targets="TrueResolutionServer"
TestTableName="CSR_Submission"
URL="jdbc:oracle:thin:@yoshi:1521:hestia"

TestConnectionsOnReserve="true" 
TestTableName="DUAL" 
ShrinkingEnabled="false" 
/>
These settings will give you maximum performance from the pool.
Hope this helps.
Regards,
Slava
"Bala" <[email protected]> wrote in message
news:[email protected]...
>
Hi Slava,
I was hoping for a response from someone like you - I saw you had similarerrors
but did not see the solution :-). In any case, here's my connection pooland datasource
information.
<JDBCTxDataSource EnableTwoPhaseCommit="true"JNDIName="jdbc/TrueResolutionDB"
Name="CoreDataSource" PoolName="CorePool" StreamChunkSize="8192"Targets="TrueResolutionServer"
/>
<JDBCConnectionPool CapacityIncrement="5" ConnLeakProfilingEnabled="true"DriverName="oracle.jdbc.driver.OracleDriver"
InitialCapacity="10" LoginDelaySeconds="1" MaxCapacity="40"Name="nonXACoreJDBCPool"
>
Properties="oracle.jdbc.V8Compatible=true;user=bala;password=bala;dll=ocijdb
c9;protocol=thin"
RefreshMinutes="10" Targets="TrueResolutionServer"TestTableName="CSR_Submission"
URL="jdbc:oracle:thin:@yoshi:1521:hestia" />
as you can see from the entry below the number of execute threads isreasonable
>
<ExecuteQueue Name="default" ThreadCount="15" ThreadPriority="10" />
"Slava Imeshev" <[email protected]> wrote:
Hi Bala.
I remember I had the same problem. Trying to recollect how I fixed it...
Meanwhile, can you post your connection pool and datasource
definitions from your config.xml?
Regards,
Slava Imeshev
"Bala" <[email protected]> wrote in message
news:[email protected]...
I do have the oracle thin driver in the classpath. the failure thatI see
is sporadic
- this makes it worse than a predictable failure. The ThreadCountparameter in
config.xml is set to 15 and the min and max capacity of the
ConnectionPool
is
set to 25 and 40 respectively (high enough, I would think).
Is Oracle Thin 9.0.1.4 Driver in the Classpath variable?
Get Oracle Thin 9.0.1.4 Driver from
http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html
"Bala" <[email protected]> wrote:
I am trying to use Oracle Thin 9.0.1.4 Driver in a distributed
Transaction
and
while trying to call connection.createStatement() I am getting the
following error.
RootCause=[java.sql.SQLException: XA error: XAER_RMERR : A resource
manager error has occured in the transaction branch start() failedon> >> >>resource 'CoreJDBCPool' null
We are using WLS 6.1SP3
Any help on the issue will be really appreciated
here's the simple test that causes this error
<%@ page isErrorPage="false" errorPage="/common/error.jsp" %>
<%@ page import="javax.sql.DataSource" %>
<%@ page import="java.sql.Connection" %>
<%@ page import="java.sql.Statement" %>
<%@ page import="javax.naming.InitialContext" %>
<%@ page import="javax.transaction.UserTransaction" %>
<html>
<body>
Testing update
<p> </p>
<%
Statement stmt = null;;
Connection conn = null;
UserTransaction ut = null;
try {
InitialContext ctx = new InitialContext();
// TODO: add the JNDI name for the datasource here
// get the datasource from the app
DataSource ds = (DataSource)ctx.lookup("jdbc/TrueResolutionDB");
ut =(UserTransaction) ctx.lookup("java:comp/UserTransaction");
ut.begin();
if (ds != null){
// Get a connection to the database
conn = ds.getConnection();
// Get a statement from the connection
stmt = conn.createStatement();
// Execute the Update
int rows = stmt.executeUpdate( "update csr_submission set
userid='wilaw' where submissionseq=436");
// Print how many rows were modified
out.println( rows + " Rows modified" ) ;
ut.commit();
} else {
out.println("datasource is null");
catch( Exception e ){
if (ut != null)
ut.rollback();
out.println(e.toString()) ;
e.printStackTrace();
// Close the statement and the connection
if (stmt != null)
stmt.close() ;
if (conn != null)
conn.close() ;
%>

Weblogic.wtc.applicationQueue problem on WLS 813

Hi all I am trying to get WLS 813 to use weblogic.wtc.applicationQueue as opposed to the default execution queue when it is called by Tuxedo. When I test this on 815 it works perfectly however when I try it on 813 it seems to ignor the dispatch policy input in the deployment descriptor and simply uses the default execution queue.
One solution is to upgrade to 815 however my client does not want to do this as they feel the risk is too great at the moment.
Have any of you out there experienced a similar situation and is there a fix without resorting to an upgrade?
tia
ed

I think that property was introduced post WLS 8.1SP3, but I'm not certain of that. If so, you could request a backport of the change from BEA Support. They should be able to accomodate you.
Regards,
Todd Little
BEA Tuxedo Chief Architect

Building /deploying sample plugin in WLI 2.1 and WLS 6.1

I'm running WLI 2.1 (service pack 1) and WLS 6.1. I'm trying to build and deploy
the sample plugin (sampleplugin-ejb.jar) but have had numerous problems.
Specifically, though there are no errors and the WLS admin console tells me the
plugin is deployed I cannot actually see any of the plugin actions etc. on the
WLI Studio and am told that the plugin is not loaded when I open the template
definitions.
I've even resorted to deploying the version of the plugin bundled in WLI_HOME\lib\sampleplugin-ejb.jar
i.e. one I didn't build myself but again, although there are no errors, the plugin
does not seem to be correctly loaded.
In order to get this far I've had to include the plugin jar file in the server
CLASSPATH. Otherwise I get an 'java.lang.NoClassDefFoundError: com/bea/wlpi/common/plugin/PluginObject'
error. I know I shouldn't have to include the EJB in the CLASSPATH but it seems
to resolve this error. Perhaps this is contributing to the other problem ????
Any help gratefully appreciated. Has anyone successfully built and deployed the
sample plugin to WLI 2.1/ WLS 6.1 ?

I found WLI sp2.
Thanks.
Sangeetha
"Sangeetha.R" <[email protected]> wrote in message
news:[email protected]..
Thanks Chris.
But, I couldn't find this in the support downloads too.
Could you let me know, from where can I download this?
Thanks,
Sangeetha
"Chris Stead" <[email protected]> wrote in message
news:[email protected]..
Sangeetha,
WLI 2.1 SP2 will go live tomorrow (7/31) and is compatible with WLS 6.1SP3.
Cheers,
Chris
Sangeetha.R wrote:
Is there a service pack for WLI 2.1 that is compatible with WLS 6.1
sp3
Thanks in advance.
Sangeetha

Send a request to a conversation that has already been finished

This error continually occurs. Any idea why?
          An attempt was made to send a request to conversation id []:169.254.17.244-b61346.100533c48f4.-7fea-gend.
          This is not a valid conversation id. The most common cause of this exception is an attempt to send a request to a conversation that has already been finished.
          Work around is to restart WLS and maybe this time it will not happen. WLS 8.1SP3.
          From: [email protected] ([email protected])
          Subject: Weblogic Tutorial Question - Need help
          This is the only article in this thread
          View: Original Format
          Newsgroups: weblogic.developer.interest.jms
          Date: 2004-09-17 09:12:33 PST
          Hi guys,
          I'm a Weblogic newbie. I have started working with Weblogic Workshop's
          Tutorial. I find them interesting and easy to follow. All was going
          well until I reached the Step 4 (Add a JMS Control). The url to this
          page is:
          http://edocs.bea.com/workshop/docs81/doc/en/workshop/reference/navResources.html
          After completing this tutorial to the end I get all the results
          mentioned, but I get additional error messages like these in my
          InvestigateTest.jws Web Service client:
          1095373714829
          investigate:creditScoreJMS:listener.onMessage
          External Service Callback investigate:creditScoreJMS:listener.onMessage
          Submitted at Friday, September 17, 2004 10:25:52 AM EDT
          Executable Request:Callback.onMessage
          ConversationNotFound Exception
          Submitted at Friday, September 17, 2004 10:25:52 AM EDT
          An attempt was made to send a request to conversation id 1095373714829.
          This is not a valid conversation id. The most common cause of this
          exception is an attempt to send a request to a conversation that has
          already been finished.
          Request Cancelled
          Submitted at Friday, September 17, 2004 10:25:52 AM EDT
          Processing Request
          Submitted at Friday, September 17, 2004 10:25:53 AM EDT
          Request Complete
          Submitted at Friday, September 17, 2004 10:25:53 AM EDT
          I cannot figure out why I'm getting these. I'm doing everything as
          described in the Tutorial. Can somebody tell me what I'm doing wrong.
          I would greatly appreciate.
          Thanks.
          Adnan

hi
          We just encountered this problem while load testing using JMeter. While it may not be the same scenario, we have found that we can consistently trigger this error if:
          a) multiple threads from the same client are invoking the service (i.e. a JMeter using JavaSamplerClient can do this)
          b) the web service is conversational according to the polling design pattern recommended in the WLW doco: i.e.
          startQuery()(one-way) conversation phase = start
          checkQueryStatus() conversation phase = continue
          fetchQueryResponse()conversation phase = finish
          c) buffering is enabled for the startQuery() operation.
          d) the number of threads > 3 (might occur very infrequently <= 3 - cant remember)
          This is reproducable in our WLS/WLW 8.1 SP2/SP3 environment.
          With buffering enabled - errors occur
          With buffering not enabled - no errors
          On reflection, buffering isn't really needed for our usage so we removed it, however the errors might indicate a bug or unsupported use case
          Regards
          Jim Nicolson

Error during deployment of Message Driven Bean

Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
          I am getting some error (or perhaps warning) during deployment of Message
          Driven Bean. Any one seen this before?
          This error only comes on a machine with Dual Network card.
          Thanks.
          ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
          ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
          <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
          enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
          Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
          is of a non-final version of the appropriate specification. It is subject to
          change in future releases once the specification becomes finalized. This may
          cause application code developed for BEA WebLogic Server 6.1 that uses the
          new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
          supported in future releases of BEA WebLogic Server.>
          ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
          unable to connect to the JMS destination: CQM_MessageQueue. The EJB
          container will automatically attempt to re-establish the connection with the
          JMS server. This warning may occur during WebLogic Cluster start-up if the
          JMS destination is located on another server. When the JMS server connection
          is re-established, the Message-Driven EJB will again receive JMS messages.
          The Error was:
          Unable to create a JNDI InitialContext to lookup the JMS destination. The
          error was:
          javax.naming.CommunicationException. Root exception is
          java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
          nested exception is:
          java.net.ConnectException: Connection refused: connect; No available router
          to destination
          at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
          at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
          at
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          textFactoryDelegate.java:307)
          at
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          textFactoryDelegate.java:211)
          at
          weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
          ory.java:149)
          at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
          at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          at javax.naming.InitialContext.init(InitialContext.java:217)
          at javax.naming.InitialContext.<init>(InitialContext.java:193)
          at
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
          rivenBeanInfoImpl.java:641)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
          nPoller.java:474)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
          .java:418)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
          nectionPoller.java:286)
          at
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
          foImpl.java:511)
          at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
          at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
          at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
          at weblogic.j2ee.Application.addComponent(Application.java:170)
          at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          arget.java:360)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
          Target.java:285)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
          eploymentTarget.java:239)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
          entTarget.java:199)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          .java:636)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          21)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy34.updateDeployments(Unknown Source)
          at
          weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
          ServerMBean_CachingStub.java:2977)
          at
          weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
          icationManager.java:372)
          at
          weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
          r.java:160)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          .java:636)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          21)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy49.start(Unknown Source)
          at
          weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
          ApplicationManagerMBean_CachingStub.java:480)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          at weblogic.management.Admin.finish(Admin.java:644)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          at weblogic.Server.main(Server.java:35)
          >
          ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010009> <EJB Deployed EJB with JNDI name
          ASYNCMessageDrivenBean.>


Hi Tom
          Yes we do have an URL provided in the descriptor. It's
          t3://jms.server.net:7001.
          and the jms.server.net is resolved via a hosts file in Win2K
          eg,
          192.168.100.200 jms.server.net
          You are right in saying that the loopback in a dual-net card is a problem.
          But our solution
          above solves the issue as long as your host file does not use 127.0.0.1 as
          the IP.
          We need the URL b/c depending on our client's deployment , the JMS Server
          may be remote or may be local.
          "Tom Barnes" <[email protected]> wrote in message
          news:[email protected]...
          > Hi x,
          >
          > Something to do with the loopback and dual-network cards is
          > messin' with WLS' mind. I do not know what the problem is,
          > but I can guess:
          >
          > You have specified an URL in the MDB descriptor when there
          > is no need for one. If t3://127.0.0.1:7001 is in the same
          > cluster the MDB is running in (I suspect this URL is
          > actually the same WL server), then don't specify the URL.
          > This URL is only useful for connecting an MDB to a JMS
          > server that is outside local server and outside the cluster.
          > The URL may be working on single-network card systems
          > as perhaps then WL has enough info to guess that you
          > actually mean the local WL server, and simply converts
          > the context to a local context.
          >
          > Note that the URL option in the MDB descriptor is actually
          > a WebLogic extension of J2EE.
          >
          > Tom
          >
          >
          >
          > x wrote:
          > > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
          > >
          > > I am getting some error (or perhaps warning) during deployment of
          Message
          > > Driven Bean. Any one seen this before?
          > > This error only comes on a machine with Dual Network card.
          > >
          > > Thanks.
          > >
          > >
          > >
          > > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          > > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
          > > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
          <main>
          > > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
          features
          > > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
          1.2,
          > > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
          6.1
          > > is of a non-final version of the appropriate specification. It is
          subject to
          > > change in future releases once the specification becomes finalized. This
          may
          > > cause application code developed for BEA WebLogic Server 6.1 that uses
          the
          > > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
          > > supported in future releases of BEA WebLogic Server.>
          > > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
          <main>
          > > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
          > > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
          > > container will automatically attempt to re-establish the connection with
          the
          > > JMS server. This warning may occur during WebLogic Cluster start-up if
          the
          > > JMS destination is located on another server. When the JMS server
          connection
          > > is re-established, the Message-Driven EJB will again receive JMS
          messages.
          > > The Error was:
          > > Unable to create a JNDI InitialContext to lookup the JMS destination.
          The
          > > error was:
          > > javax.naming.CommunicationException. Root exception is
          > > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
          > > nested exception is:
          > > java.net.ConnectException: Connection refused: connect; No available
          router
          > > to destination
          > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
          > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:307)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:211)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
          > > ory.java:149)
          > > at
          javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
          > > at
          javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          > > at javax.naming.InitialContext.init(InitialContext.java:217)
          > > at javax.naming.InitialContext.<init>(InitialContext.java:193)
          > > at
          > >
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
          > > rivenBeanInfoImpl.java:641)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
          > > nPoller.java:474)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
          > > .java:418)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
          > > nectionPoller.java:286)
          > > at
          > >
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
          > > foImpl.java:511)
          > > at
          weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
          > > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
          > > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
          > > at weblogic.j2ee.Application.addComponent(Application.java:170)
          > > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          > > arget.java:360)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
          > > Target.java:285)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
          > > eploymentTarget.java:239)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
          > > entTarget.java:199)
          > > at java.lang.reflect.Method.invoke(Native Method)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          > > .java:636)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          > > 21)
          > > at
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > nImpl.java:360)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > > at $Proxy34.updateDeployments(Unknown Source)
          > > at
          > >
          weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
          > > ServerMBean_CachingStub.java:2977)
          > > at
          > >
          weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
          > > icationManager.java:372)
          > > at
          > >
          weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
          > > r.java:160)
          > > at java.lang.reflect.Method.invoke(Native Method)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          > > .java:636)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          > > 21)
          > > at
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > nImpl.java:360)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > > at $Proxy49.start(Unknown Source)
          > > at
          > >
          weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
          > > ApplicationManagerMBean_CachingStub.java:480)
          > > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          > > at weblogic.management.Admin.finish(Admin.java:644)
          > > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          > > at weblogic.Server.main(Server.java:35)
          > >
          > > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          > > <system> <> <010009> <EJB Deployed EJB with JNDI name
          > > ASYNCMessageDrivenBean.>
          > >
          > >
          >

JVM Crash on Unix (Solaris)

Hi,
I have an application which works fine on Windows environment. If the ear prepared on Windows is deployed on Unix it works fine. But when the application is build in Unix, the application gets deployed but when accessing the application it crashes.
I have pasted the crash details below
0xf9540000      /anfield/opt/bea/wls/8.1sp3/jdk142_04/jre/lib/sparc/libioser12.so
0xdf650000      /anfield/mqseries1/opt/mqm/java/lib/libmqjbnd05.so
0xdf610000      /opt/mqm/lib/libmqm.so
0xdbf80000      /opt/mqm/lib/libmqz.so
0xdbe00000      /opt/mqm/lib/libmqmcs.so
0xdf560000      /opt/mqm/lib/libmqmzse.so
0xdf530000      /anfield/mqseries1/opt/mqm/java/lib/libmqjbdf02.so
0xdf510000      /anfield/mqseries1/opt/mqm/java/lib/libMQXAi02.so
Heap at VM Abort:
Heap
def new generation total 32768K, used 25924K [0xe4c00000, 0xe6cf0000, 0xe8ea0000)
eden space 31808K, 81% used [0xe4c00000, 0xe65510f0, 0xe6b10000)
from space 960K, 0% used [0xe6b10000, 0xe6b10000, 0xe6c00000)
to space 960K, 0% used [0xe6c00000, 0xe6c00000, 0xe6cf0000)
tenured generation total 67296K, used 40373K [0xe8ea0000, 0xed058000, 0xf1400000)
the space 67296K, 59% used [0xe8ea0000, 0xeb60d7c0, 0xeb60d800, 0xed058000)
compacting perm gen total 40960K, used 40910K [0xf1400000, 0xf3c00000, 0xf9400000)
the space 40960K, 99% used [0xf1400000, 0xf3bf3818, 0xf3bf3a00, 0xf3c00000)
Local Time = Tue Feb 21 06:58:18 2006
Elapsed Time = 207
# HotSpot Virtual Machine Error : 11
# Error ID : 4F530E43505002EF 01
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Server VM (1.4.2_04-b05 mixed mode)
# An error report file has been saved as hs_err_pid7291.log.
# Please refer to the file for further information.
I think I have localised the crash to a section of the code where there is character comparison done. If I comment out this section, it works fine. I ahve pasted below the section:
else if (getChar() == '\'' && getOffset() < getBuffer().length())
{ // Start of a Literal - so just copy until the end of the literal
do
sb.append(getChar());
setChar(getNextChar());
while (getChar() != '\'' && getOffset() < getBuffer().length());
sb.append(getChar()); // Append the final single quote
setChar(getNextChar());
After substituting " ' "for it integer value, I started getting a JVM crash with a different error id.; pasted it below
[Loaded javax.servlet.http.HttpServletResponseWrapper]
[Loaded weblogic.servlet.internal.RemoveWrapperOnForward]
[Loaded weblogic.servlet.jsp.NestedBodyResponse]
[Loaded weblogic.servlet.jsp.BodyOutputStream]
[Loaded java.io.CharArrayReader from /anfield/opt/bea/wls/8.1sp3/jdk142_04/jre/lib/rt.jar]
[Loaded weblogic.servlet.internal.CharChunkOutput]
[Loaded sun.io.ConversionBufferFullException from /anfield/opt/bea/wls/8.1sp3/jdk142_04/jre/lib/rt.jar]
[Loaded org.apache.struts.taglib.html.SubmitTag]
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Server VM (1.4.2_04-b05 mixed mode)
# Error ID: 4255494C442F4F502D41500E4350500107 01
# Problematic Thread: prio=5 tid=0x000ea6f0 nid=0xa runnable
Heap at VM Abort:
Heap
def new generation total 25088K, used 1933K [0xe4c00000, 0xe6530000, 0xe8ea0000)
eden space 24384K, 5% used [0xe4c00000, 0xe4d33408, 0xe63d0000)
from space 704K, 99% used [0xe6480000, 0xe652fff8, 0xe6530000)
to space 704K, 0% used [0xe63d0000, 0xe63d0000, 0xe6480000)
tenured generation total 51432K, used 43087K [0xe8ea0000, 0xec0da000, 0xf1400000)
the space 51432K, 83% used [0xe8ea0000, 0xeb8b3e90, 0xeb8b4000, 0xec0da000)
compacting perm gen total 40960K, used 40883K [0xf1400000, 0xf3c00000, 0xf9400000)
the space 40960K, 99% used [0xf1400000, 0xf3becc48, 0xf3bece00, 0xf3c00000)
Could you please help me to find out the cause? Also how do you make sense of the details(which I have pasted above) in the logs written at time of crash. Is there anyway to look at the core files other than dbx or gdb?
Thanks,
Ragesh

Hi,
I have an application which works fine on Windows environment. If the application prepared on Windows is deployed on Unix but when accessing it crashes.
here by i am pasting the error.
# An unexpected error has been detected by HotSpot Virtual Machine:
# SIGSEGV (0xb) at pc=0x2a6f5075, pid=5044, tid=8201
# Java VM: Java HotSpot(TM) Client VM (1.4.2_10-b03 mixed mode)
# Problematic frame:
# j e4p_DecisionMaker.makeDecision(Le4p_InitailArrayContainer;I)I+2668
--------------- T H R E A D ---------------
Current thread (0x082a3ed8): JavaThread "Thread-0" [_thread_in_Java, id=5330]
siginfo:si_signo=11, si_errno=-1071498229, si_code=12, si_addr=0x00000000
Registers:
EAX=0x04000000, EBX=0x30797160, ECX=0x00000000, EDX=0x0c800002
ESP=0xbe5ff960, EBP=0xbe5ff988, ESI=0x30ac7d44, EDI=0xbe5ff9b8
EIP=0x2a6f5075, CR2=0xc580a700, EFLAGS=0x00010206
Top of Stack: (sp=0xbe5ff960)
0xbe5ff960: 2a6e8d43 30ac8950 00000000 be5ff96c
0xbe5ff970: 30ac7d44 be5ff9b8 30ac80f0 00000000
0xbe5ff980: 30ac7290 be5ff9b0 be5ff9d8 2a6e8def
0xbe5ff990: 00000000 00000000 00000000 00000000
0xbe5ff9a0: 00000000 00000001 00000000 00000000
0xbe5ff9b0: 00000005 2cd46c58 2c798b58 be5ff9bc
0xbe5ff9c0: 30a772f7 be5ffa1c 30a81da8 00000000
0xbe5ff9d0: 30a771a0 be5ffa1c be5ffa3c 2a6e8e9b
Instructions: (pc=0x2a6f5075)
0x2a6f5065: 75 e8 8b c2 81 e0 00 00 00 04 0f 84 05 00 00 00
0x2a6f5075: 3b 01 ff 63 3c 8b 41 04 8b 9c 98 dc 00 00 00 8b
Stack: [0xbe40e000,0xbe600000), sp=0xbe5ff960, free space=1990k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
j e4p_DecisionMaker.makeDecision(Le4p_InitailArrayContainer;I)I+2668
j e4p_Schedular.scheduleCaller()V+271
j e4p_ModuleIterator.run()V+34
j java.util.TimerThread.mainLoop()V+221
j java.util.TimerThread.run()V+1
v ~StubRoutines::call_stub
V [libjvm.so+0x1a8aa4]
V [libjvm.so+0x25e605]
V [libjvm.so+0x1a8cf6]
V [libjvm.so+0x1a85c6]
V [libjvm.so+0x1a913f]
V [libjvm.so+0x203695]
V [libjvm.so+0x2aaa9a]
V [libjvm.so+0x2a5f57]
V [libjvm.so+0x260113]
C [libpthread.so.0+0x5b85] pthread_detach+0x515
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x082922e8 JavaThread "Thread-5" [_thread_blocked, id=5335]
0x0825a818 JavaThread "Thread-4" [_thread_blocked, id=5334]
0x0828e8a0 JavaThread "Thread-3" [_thread_in_native, id=5333]
0x082553d8 JavaThread "DestroyJavaVM" [_thread_blocked, id=5044]
0x082a3980 JavaThread "Thread-2" [_thread_blocked, id=5332]
0x082a3800 JavaThread "Thread-1" [_thread_blocked, id=5331]
=>0x082a3ed8 JavaThread "Thread-0" [_thread_in_Java, id=5330]
0x080995d0 JavaThread "CompilerThread0" daemon [_thread_blocked, id=5328]
0x080987f8 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=5327]
0x080954d8 JavaThread "Finalizer" daemon [_thread_blocked, id=5325]
0x080939f8 JavaThread "Reference Handler" daemon [_thread_blocked, id=5324]
Other Threads:
0x08090880 VMThread [id=5323]
0x080b45c8 WatcherThread [id=5329]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
def new generation total 576K, used 190K [0x2c790000, 0x2c830000, 0x2cc70000)
eden space 512K, 24% used [0x2c790000, 0x2c7afbd8, 0x2c810000)
from space 64K, 100% used [0x2c810000, 0x2c820000, 0x2c820000)
to space 64K, 0% used [0x2c820000, 0x2c820000, 0x2c830000)
tenured generation total 1408K, used 1105K [0x2cc70000, 0x2cdd0000, 0x30790000)
the space 1408K, 78% used [0x2cc70000, 0x2cd845a0, 0x2cd84600, 0x2cdd0000)
compacting perm gen total 4096K, used 3457K [0x30790000, 0x30b90000, 0x34790000)
the space 4096K, 84% used [0x30790000, 0x30af0400, 0x30af0400, 0x30b90000)
Dynamic libraries:

WLS 6.1SP3

Similar Messages

Maybe you are looking for