Assertions in java
i m confused by the call by value property of java.those it sends an object it treats it as call by value.so what actually happens in terms of memory wise when an object is passed to a function.this quite a puzzed question to me and i ll be thank ful to u if u could help me
regards
bhushan
What has this with assertions to do? Assertions are a way to check the consistency of programs during development.
Anyway all parameters in method calls are passed by value in Java. This means that the content of a variable is passed.
Now in Java all objects are treated by their references. You can think of a reference as a pointer to an object. The object value itself is at a storage called the heap. So all object variables contains a reference to some object. That's why they're also called reference variables.
So the content of a reference variable is a reference and it's passed by value to a method. The object value always stays on the heap while references to it are passed around.
Similar Messages
-
Error Invoking Java class from Stored proc
We are getting this error while calling a stored procedure that invokes a
static function of a java class from inside Oracle 8.1.7.
ORA-29516: Aurora assertion failure: Java thread deadlock detected
ORA-06512: at "APPS.SERVICECONSUMERINVOKE", line 0
ORA-06512: at line 40
In a Toad SQL Window, when I execute the stored procedure that invokes the
java function, it executes successfully on the first attempt. When I try to
execute it again on the same SQL Window, it gives the above error. The java
class is part of a package and indirectly makes a JMS request-reply call
via other helper classes.
The same package works fine from other web containers and
unlike the Oracle JVM Aurora, the JVMs don't detect a deadlock.
Why does the Aurora throw an error?Did you try issusing a commit and then trying again in Toad SQL Window?
The advice is to contact support:
ORA-29516: Aurora assertion failure: string
Cause: An internal error occurred in the Aurora module.
Action: Contact Oracle Worldwide Support. -
Hi,
I am trying to deploy an EJB module have 4-5 EJB's on weblogic 8.1 through JBuilder.
I am getting following error during deployment.
Exception:weblogic.management.ApplicationException: prepare failed for Sample.jar
Module: Sample.jar Error: Exception preparing module: EJBModule(Sample.jar,status=NEW)
Unable to deploy EJB: SampleBean from Sample.jar:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot export non
clusterable object with jndiName ]
at weblogic.utils.Debug.assertion(Debug.java:57)
at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:272)
at weblogic.ejb20.internal.BaseEJBHome.setup(BaseEJBHome.java:95)
at weblogic.ejb20.internal.StatelessEJBHome.setup(StatelessEJBHome.java:67)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.prepare(ClientDrivenBeanInfoImpl.java:979)
at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:983)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2962)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Any clue?, what its talking about?
Thanks
NareshHi,
I am trying to deploy an EJB module have 4-5 EJB's on weblogic 8.1 through JBuilder.
I am getting following error during deployment.
Exception:weblogic.management.ApplicationException: prepare failed for Sample.jar
Module: Sample.jar Error: Exception preparing module: EJBModule(Sample.jar,status=NEW)
Unable to deploy EJB: SampleBean from Sample.jar:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot export non
clusterable object with jndiName ]
at weblogic.utils.Debug.assertion(Debug.java:57)
at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:272)
at weblogic.ejb20.internal.BaseEJBHome.setup(BaseEJBHome.java:95)
at weblogic.ejb20.internal.StatelessEJBHome.setup(StatelessEJBHome.java:67)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.prepare(ClientDrivenBeanInfoImpl.java:979)
at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:983)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2962)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Any clue?, what its talking about?
Thanks
Naresh -
I get Assertion Failed open report with CR viewer 2.0.23
Post Author: gionnyDeep
CA Forum: General
any help?
Assertion Failed: java.lang.Throwable at com.crystaldecisions.reports.common.j.b.a(Unknown Source) at com.crystaldecisions.reports.common.j.b.a(Unknown Source) at com.crystaldecisions.reports.queryengine.b0.char(Unknown Source) at com.crystaldecisions.reports.queryengine.b0.else(Unknown Source) at com.crystaldecisions.reports.queryengine.b0.else(Unknown Source) at com.crystaldecisions.reports.queryengine.b0.d(Unknown Source) at com.crystaldecisions.reports.queryengine.b0.dt(Unknown Source) at com.crystaldecisions.reports.queryengine.b0.dD(Unknown Source) at com.crystaldecisions.reports.queryengine.b9.int(Unknown Source) at com.crystaldecisions.reports.queryengine.b9.for(Unknown Source) at com.crystaldecisions.reports.queryengine.b9.int(Unknown Source) at com.crystaldecisions.reports.queryengine.b9.for(Unknown Source) at com.crystaldecisions.reports.queryengine.b9.int(Unknown Source) at com.crystaldecisions.reports.queryengine.b9.case(Unknown Source) at com.crystaldecisions.reports.queryengine.b9.if(Unknown Source) at com.crystaldecisions.reports.queryengine.b9.c(Unknown Source) at com.crystaldecisions.reports.queryengine.b0.d(Unknown Source) at com.crystaldecisions.reports.queryengine.b0.dt(Unknown Source) at com.crystaldecisions.reports.reportdefinition.datainterface.l.a(Unknown Source) at com.crystaldecisions.reports.dataengine.j.j(Unknown Source) at com.crystaldecisions.reports.dataengine.j.i(Unknown Source) at com.crystaldecisions.reports.dataengine.j.a7(Unknown Source) at com.crystaldecisions.reports.dataengine.j.a9(Unknown Source) at com.crystaldecisions.reports.dataengine.j.char(Unknown Source) at com.crystaldecisions.reports.dataengine.n.a(Unknown Source) at com.crystaldecisions.reports.dataengine.a5.a(Unknown Source) at com.crystaldecisions.reports.dataengine.a5.Z(Unknown Source) at com.crystaldecisions.reports.dataengine.a5.<init>(Unknown Source) at com.crystaldecisions.reports.dataengine.a5.<init>(Unknown Source) at com.crystaldecisions.reports.dataengine.a5.<init>(Unknown Source) at com.crystaldecisions.reports.dataengine.a5.a(Unknown Source) at com.crystaldecisions.reports.formatter.formatter.objectformatter.bn.<init>(Unknown Source) at com.crystaldecisions.reports.formatter.formatter.objectformatter.bn.if(Unknown Source) at com.crystaldecisions.reports.formatter.formatter.d.k.<init>(Unknown Source) at com.crystaldecisions.reports.formatter.formatter.d.o.<init>(Unknown Source) at com.crystaldecisions.reports.formatter.formatter.d.o.a(Unknown Source) at com.crystaldecisions.reports.reportengineinterface.g.if(Unknown Source) at com.crystaldecisions.reports.reportengineinterface.g.do(Unknown Source) at com.crystaldecisions.reports.reportengineinterface.JPEReportSource.getPage(Unknown Source) at com.businessobjects.crystalreports.viewer.core.rs.b.if(Unknown Source) at com.businessobjects.crystalreports.viewer.core.aw.a(Unknown Source) at com.businessobjects.crystalreports.viewer.core.aw.run(Unknown Source) at java.lang.Thread.run(Thread.java:619)Sorry, but you have to define "viewer just crashed". To different people this means different things; error, viewer never shows up, application terminates, etc., etc., etc....
If the issue is only 10% of computers then it is not
Re. "...could be caused by:"
- previous installation of CR8.5 (or earlier) runtime (how to cleanup it correctly?)
possibly - see below
- OS configuration (what we need to ajust?)
probably not - as long as it's the same OS and SPs
- something missing in our code (but why it works in 90% cases?)
-no
- something wrong with CRXI runtime (but we a using latest available MSMs, and again, this works in 90% ...)
possibly see below.
I would approach the issue by running [Modules|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] and comparing the dlls loading on a computer that works and one that "crashes"...
Your second utility is [Process Monitor|http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx] but ProcMon creates large and difficult to read files.
Oh, and get the powers that be to start to consider moving away from this legacy "stuff". Like I said, PE APIs have been gone since version 9 of CR and RDC has been retired in CR XI R2 (11.5). Neither product is supported anymore.
- Ludek -
Visual Age for Java 3.0 and EJBs
Michael,
We are also seeing problems with EJB development using the VAJ integration kit
for Weblogic 4.5.1 and Visual Age Java 3.0.2. The rest of the integration,
JSPs, Servlets, etc. appear to work just fine using the 4.5.1 integration kit
and Visual Age Java 3.0.2. However, with EJBs we are finding the deployment
tools to break into the VAJ debugger.
Comments (all welcome)
john
Michael Girdley wrote:
We plan to release an integration kit for VisualAge soon. Please check our
web site regularly for information on the availability of this kit.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
Vladimir Goncharov <[email protected]> wrote in message
news:[email protected]...
I'm getting Exception, when trying to create Initial context from withinthe
VisualAge for Java 3.0, the same compiled class by Visual Age for Java 3.0
works fine when run from the command line using JDK.2.2
My understanding is that client program may run on JDK 1.1.7 and above and
IBM using IBM JDK 1.1.8 which compatible with the SUN one
Please help.
Here is the classpath that VisualAge is using
C:\weblogic\classes;
C:\weblogic\lib\weblogicaux.jar;
C:\IBMVJava\ide\Program\lib\;
C:\IBMVJava\ide\Program\lib\classes.zip;
Here is the Exception thrown by Weblogic
weblogic.utils.AssertionError: ***** ASSERTION FAILED
****[ java.lang.InternalError: (Ex02) An error has occurred. ]
java.lang.Throwable(java.lang.String)
java.lang.Error(java.lang.String)
weblogic.utils.NestedError(java.lang.String)
weblogic.utils.AssertionError(java.lang.String)
java.lang.Object
weblogic.kernel.Kernel.getInstanceDynamically(java.lang.String,
java.lang.Class [], java.lang.Object [])
weblogic.logging.LogManager weblogic.kernel.Kernel.getLogManager()
weblogic.logging.LogOutputStream(java.lang.String)
weblogic.common.internal.LogOutputStream(java.lang.String)
weblogic.t3.services.ConfigClient()
java.lang.Objectjava.lang.reflect.Constructor.newInstance(java.lang.Object
java.lang.Object
weblogic.kernel.Kernel.getInstanceDynamically(java.lang.String,
java.lang.Class [], java.lang.Object [])
weblogic.t3.services.ConfigDef weblogic.kernel.Kernel.getConfig()
void weblogic.kernel.Kernel.ensureInitialized()
weblogic.rjvm.RJVM weblogic.rjvm.ServerURL.findOrCreateRJVM()
javax.naming.Context
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(weblogic.jnd
i.Environment, java.lang.String)
javax.naming.Context
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(java.util.Ha
shtable)
javax.naming.Context
weblogic.jndi.WLInitialContextFactory.getInitialContext(java.util.Hashtable)
javax.naming.Context
javax.naming.spi.NamingManager.getInitialContext(java.util.Hashtable)
javax.naming.Context javax.naming.InitialContext.getDefaultInitCtx()
void javax.naming.InitialContext.init(java.util.Hashtable)
javax.naming.InitialContext(java.util.Hashtable)
javax.naming.Context com.vlad.ejb.client.ClientTest.getInitialContext()
void com.vlad.ejb.client.ClientTest.main(java.lang.String [])
weblogic.utils.AssertionError: ***** ASSERTION FAILED
****[ weblogic.utils.AssertionError: ***** ASSERTION FAILED
****[ java.lang.InternalError: (Ex02) An error has occurred. ] ]
java.lang.Throwable(java.lang.String)
java.lang.Error(java.lang.String)
weblogic.utils.NestedError(java.lang.String)
weblogic.utils.AssertionError(java.lang.String)
java.lang.Object
weblogic.kernel.Kernel.getInstanceDynamically(java.lang.String,
java.lang.Class [], java.lang.Object [])
weblogic.t3.services.ConfigDef weblogic.kernel.Kernel.getConfig()
void weblogic.kernel.Kernel.ensureInitialized()
weblogic.rjvm.RJVM weblogic.rjvm.ServerURL.findOrCreateRJVM()
javax.naming.Context
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(weblogic.jnd
i.Environment, java.lang.String)
javax.naming.Context
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(java.util.Ha
shtable)
javax.naming.Context
weblogic.jndi.WLInitialContextFactory.getInitialContext(java.util.Hashtable)
javax.naming.Context
javax.naming.spi.NamingManager.getInitialContext(java.util.Hashtable)
javax.naming.Context javax.naming.InitialContext.getDefaultInitCtx()
void javax.naming.InitialContext.init(java.util.Hashtable)
javax.naming.InitialContext(java.util.Hashtable)
javax.naming.Context com.vlad.ejb.client.ClientTest.getInitialContext()
void com.vlad.ejb.client.ClientTest.main(java.lang.String [])
John N. Alegre
Javelin Solutions
[email protected] -
Client Asserts under VisualAge 2.0 & WLS 4.5.1
I followed the instructions of previous newsgroup posts on homw to get
weblogic.Server running under VA2.0. That works fine, my problem is my
client. Every time I try to run a simple client, I get the following
error:
Beginning statelessSession.Client...
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
java.lang.InternalError: (Ex02) An error has occurred. ]
java.lang.Throwable(java.lang.String)
java.lang.Error(java.lang.String)
weblogic.utils.NestedError(java.lang.String)
weblogic.utils.AssertionError(java.lang.String)
java.lang.Object
weblogic.rjvm.Kernel.getInstanceDynamically(java.lang.String,
java.lang.Class [], java.lang.Object [])
weblogic.t3.srvr.LogManager weblogic.rjvm.Kernel.getLogManager()
void weblogic.rjvm.Kernel.ensureInitialized()
weblogic.rjvm.RJVM
weblogic.common.internal.DNSBasedRJVMFinder.findOrCreate(java.lang.String,
int)
weblogic.rjvm.RJVM
weblogic.common.internal.ServerURL.findOrCreateRJVM()
javax.naming.Context
weblogic.jndi.WLInitialContextFactory.getInitialContext(weblogic.jndi.Environment,
java.lang.String)
javax.naming.Context
weblogic.jndi.WLInitialContextFactory.getInitialContext(java.util.Hashtable)
javax.naming.Context
javax.naming.spi.NamingManager.getInitialContext(java.util.Hashtable)
javax.naming.Context javax.naming.InitialContext.getDefaultInitCtx()
javax.naming.InitialContext(java.util.Hashtable)
javax.naming.Context
examples.ejb.basic.statelessSession.Client.getInitialContext()
void examples.ejb.basic.statelessSession.Client.main(java.lang.String
ANY THOUGHTS?I suspect that your client's classpath is inadequate. Make sure that you have
the weblogic classes in the CLASSPATH.
-- Rob
Joseph Krozak wrote:
I followed the instructions of previous newsgroup posts on homw to get
weblogic.Server running under VA2.0. That works fine, my problem is my
client. Every time I try to run a simple client, I get the following
error:
Beginning statelessSession.Client...
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
java.lang.InternalError: (Ex02) An error has occurred. ]
java.lang.Throwable(java.lang.String)
java.lang.Error(java.lang.String)
weblogic.utils.NestedError(java.lang.String)
weblogic.utils.AssertionError(java.lang.String)
java.lang.Object
weblogic.rjvm.Kernel.getInstanceDynamically(java.lang.String,
java.lang.Class [], java.lang.Object [])
weblogic.t3.srvr.LogManager weblogic.rjvm.Kernel.getLogManager()
void weblogic.rjvm.Kernel.ensureInitialized()
weblogic.rjvm.RJVM
weblogic.common.internal.DNSBasedRJVMFinder.findOrCreate(java.lang.String,
int)
weblogic.rjvm.RJVM
weblogic.common.internal.ServerURL.findOrCreateRJVM()
javax.naming.Context
weblogic.jndi.WLInitialContextFactory.getInitialContext(weblogic.jndi.Environment,
java.lang.String)
javax.naming.Context
weblogic.jndi.WLInitialContextFactory.getInitialContext(java.util.Hashtable)
javax.naming.Context
javax.naming.spi.NamingManager.getInitialContext(java.util.Hashtable)
javax.naming.Context javax.naming.InitialContext.getDefaultInitCtx()
javax.naming.InitialContext(java.util.Hashtable)
javax.naming.Context
examples.ejb.basic.statelessSession.Client.getInitialContext()
void examples.ejb.basic.statelessSession.Client.main(java.lang.String
ANY THOUGHTS? -
So anything LEGACY means it is probably not supported and chocked full of security issues.
what JAVA flavor do I need to install?
WHat do I do ?
I have a lot of work to do...
thanks in advanceHi,
Try this:
Download Java for Mac OS X 2014-001 from http://support.apple.com/kb/dl1572.
Install the Java update using the downloaded .dmg file.
When installation is complete, a Software Update dialog box appears. The dialog box asserts that Java SE 6 Runtime is required to run Adobe Illustrator CS6.
In the Software Update dialog box, click Install.
Launch Illustrator.
In Adobe Illustrator CS6 some plug-ins has dependency on Java, therefore Java is required for them to function properly.
With Best Regards,
Raghuveer -
ASSERTION FAILED of replica-related stub in a non-clustered SLSB
Wl 6.1 sp2
Solaris 2.8
We have 50 SLSBs running on non-clustered WL servers. Yet we are seeing
the following ASSERTION FAILED error, which from the stacktrace seems to
hint the ejb stub is doing something cluster-related... I have attached
ejb-jar.xml of the offending bean; someone please verify we are not
building cluster-capable stubs, and if we are building the right stub,
please explain why the exception is happening. Thanks!
******** STACKTRACE
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Assertion
violated ]
at weblogic.utils.Debug.assert(Debug.java:74)
at weblogic.rmi.cluster.BasicReplicaList.reset(BasicReplicaList.java:175)
at
weblogic.rmi.cluster.PrimarySecondaryReplicaHandler.setPiggybackResponse(Pri
marySecondaryReplicaHandler.java:94)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.setPiggybackResponse(ReplicaAware
RemoteRef.java:294)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:265)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy14.getStatus(Unknown Source)
at
com.go2.dtc.service.AccountStatus.accountIsOnline(AccountStatus.java:57)
******* EJB-JAR.XML
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
<remote>com.go2.ejb.services.accountservice.AccountService</remote>
<ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>getStatus</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>changeSearchListingStatus</method-name>
<method-params>
<method-param>int</method-param>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>RequiresNew</trans-attribute>
</container-transaction>
</assembly-descriptor>
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
<remote>com.go2.ejb.services.accountservice.AccountService</remote>
<ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>getStatus</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>changeSearchListingStatus</method-name>
<method-params>
<method-param>int</method-param>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>RequiresNew</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>Hi Rajesh,
This error was reported on our QA system error log, and only occurred a
couple of times in a very specific time frame. I will ask QA again if it
has happened since the first report.
However, even if this bug is minor and not production-worthy, what I am more
concerned about is the fact that the stacktrace seem to indicate the bug is
cluster-related, when we set our SLSBs to be non-clustered. Can someone
please confirm, given the ejb-jar.xml and weblogic-ejb-jar.xml I've posted
below, that I have properly configured and deployed our beans to be
non-clustered? I don't want to introduce cluster overhead (and cluster
bugs) when we don't need to!
Gene
"Rajesh Mirchandani" <[email protected]> wrote in message
news:[email protected]...
The reason I asked you if it is readily reproducable is because I had seenthis
issue (support case) in WLS 6.1(no sp). The problem there was that itcould not
be reproduced again and so I did not analyze it further.
Is this happening under load ?
Gene Chuang wrote:
Hi Rob,
AccountStatus is calling AccountService, which is a SLSB. I have
attached
its ejb-jar.xml in my original post, and here's the corresponding
weblogic-ejb-jar.xml:
!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic6.0.0
EJB//EN' 'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
<!-- Generated XML! -->
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<stateless-session-descriptor>
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>False</stateless-bean-is-clusterable>
>>
>>
<stateless-bean-methods-are-idempotent>False</stateless-bean-methods-are-ide
mpotent>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
<jndi-name>accountservice.AccountServiceHome</jndi-name>
</weblogic-enterprise-bean>
<transaction-isolation>
<isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>*</method-name>
</method>
</transaction-isolation>
</weblogic-ejb-jar>
"Rob Woollen" <[email protected]> wrote in message
news:[email protected]...
It looks like AccountStatus is calling a stateful session bean that
uses
in-memory replication. (The PrimarySecondary stub is only used forin-memory
replicated sfsb.)
Do you have any sfsb?
-- Rob
Gene Chuang wrote:
Wl 6.1 sp2
Solaris 2.8
We have 50 SLSBs running on non-clustered WL servers. Yet we are
seeing
the following ASSERTION FAILED error, which from the stacktrace
seems to
hint the ejb stub is doing something cluster-related... I haveattached
ejb-jar.xml of the offending bean; someone please verify we are not
building cluster-capable stubs, and if we are building the rightstub,
please explain why the exception is happening. Thanks!
******** STACKTRACE
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[Assertion
violated ]
at weblogic.utils.Debug.assert(Debug.java:74)
atweblogic.rmi.cluster.BasicReplicaList.reset(BasicReplicaList.java:175)
at
weblogic.rmi.cluster.PrimarySecondaryReplicaHandler.setPiggybackResponse(Pri
marySecondaryReplicaHandler.java:94)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.setPiggybackResponse(ReplicaAware
RemoteRef.java:294)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:265)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy14.getStatus(Unknown Source)
at
com.go2.dtc.service.AccountStatus.accountIsOnline(AccountStatus.java:57)
>>>>
******* EJB-JAR.XML
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
><remote>com.go2.ejb.services.accountservice.AccountService</remote>
<ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
>>>>>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>getStatus</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>changeSearchListingStatus</method-name>
<method-params>
<method-param>int</method-param>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>RequiresNew</trans-attribute>
</container-transaction>
</assembly-descriptor>
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
><remote>com.go2.ejb.services.accountservice.AccountService</remote>
<ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
>>>>>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>getStatus</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>accountservice.AccountServiceHome</ejb-name>
<method-intf>Remote</method-intf>
<method-name>changeSearchListingStatus</method-name>
<method-params>
<method-param>int</method-param>
<method-param>java.lang.String</method-param>
</method-params>
</method>
<trans-attribute>RequiresNew</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support -
will any body plz tell me the practical use of assertion, coz already made 5 or 6 projects on core, 1 chat messanger on swing + now i m going to prepare editor. But i don't c any practical usage of assertion. will i have to wait untill i got big projects after i m in a job.
rits wrote:
will any body plz tell me the practical use of assertion, coz already made 5 or 6 projects on core, 1 chat messanger on swing + now i m going to prepare editor. But i don't c any practical usage of assertion. will i have to wait untill i got big projects after i m in a job.Please make the extra effort to write out words such as "please", "because", "and", "am", and "see". The extra keystrokes won't cost much in the way of time, and the enhanced clarity will be appreciated by those communicating on a forum with international readership. Also, it will give the appearance that you take your question seriously, which will in turn make your question look more interesting to answer.
For practical uses of assertions, please read the following: [Programming With Assertions|http://java.sun.com/j2se/1.4.2/docs/guide/lang/assert.html]
~ -
ASSERTION FAILED - servicepack 10
Hi,
I've just upgraded to servicepack 10 and I get the following problem.
The problem does not occur all the time.
Any help greatly appreciated...
..Per
============================================================================
====
Enviroment:AIX version 4.3 weblogic 5.10 sp10 clustered environment
============================================================================
====
=========================================================
** Time to process jsp servlet = 31 msecs
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
Mon Aug 20 12:54:47 GMT+00:00 2001:<E> <HTTP> Connection failure
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
Mon Aug 20 12:54:47 GMT+00:00 2001:<E> <HTTP> Connection failure
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
Mon Aug 20 12:54:54 GMT+00:00 2001:<E> <HTTP> Connection failure
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
Mon Aug 20 12:54:55 GMT+00:00 2001:<E> <HTTP> Connection failure
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Attempt to
invoke 0
e request ]
at weblogic.utils.Debug.assert(Debug.java(Compiled Code))
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
8)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)Same problem for us. SP10 worked fine in development and test but has this problem
on the production servers. Part of the message is about a "0 byte request" so
perhaps this has to do with an ISP issue as this does not occur on other test
clients.
Ideas?
Tim
anna-maija.vesterinen <[email protected]> wrote:
Hi,
I have a similar problem in out production environment. Have you/any
one had any luck in finding out any solution?
rgds,
Ansku -
does any one know why we get this call stack? what does this mean? We didn't change our deployment descriptor but it just comes up suddenly.
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ invalid assignment from 'Object' to 'Object' ]
at weblogic.utils.Debug.assertion(Debug.java:57)
at weblogic.utils.classfile.expr.LocalVariableExpression.codeAssign(LocalVariableExpression.java:38)
at weblogic.utils.classfile.expr.AssignStatement.code(AssignStatement.java:28)
at weblogic.utils.classfile.expr.CompoundStatement.code(CompoundStatement.java:26)
at weblogic.utils.classfile.CodeAttribute.setCode(CodeAttribute.java:44)
at weblogic.rmi.internal.StubGenerator.addMethodCode(StubGenerator.java:457)
at weblogic.rmi.internal.StubGenerator.<init>(StubGenerator.java:125)
at weblogic.rmi.internal.StubGenerator.<init>(StubGenerator.java:86)
at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:769)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:810)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:797)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:79)
at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:232)
at weblogic.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:45)
at weblogic.rmi.cluster.ReplicaAwareRemoteObject.initialize(ReplicaAwareRemoteObject.java:77)
at weblogic.rmi.cluster.ReplicaAwareRemoteObject.<init>(ReplicaAwareRemoteObject.java:50)
at weblogic.rmi.cluster.ClusterableRemoteObject.<init>(ClusterableRemoteObject.java:79)
at weblogic.rmi.cluster.ClusterableRemoteBinderFactory.getStateToBind(ClusterableRemoteBinderFactory.j
ava:45)
at weblogic.jndi.internal.WLNamingManager.getReplacement(WLNamingManager.java:180)
at weblogic.jndi.internal.WLNamingManager.getStateToBind(WLNamingManager.java:154)
at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.java:168)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:382)
at weblogic.jndi.internal.WLEventContextImpl.rebind(WLEventContextImpl.java:118)
at weblogic.ejb20.internal.StatelessEJBHome.activate(StatelessEJBHome.java:115)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1096)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1362)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:270)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:83)
at weblogic.j2ee.Application.deploy(Application.java:429)
at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:241)
at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:2946)
at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:2864)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1638)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1085)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:337)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.RemoteMBeanServerImpl.private_setAttribute(RemoteMBeanServerImpl.java:
430)
at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:386)
at weblogic.management.internal.RemoteMBeanServerImpl_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)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:
1034)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:340)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.RemoteMBeanServerImpl.private_setAttribute(RemoteMBeanServerImpl.java:
430)
at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:386)
at weblogic.management.internal.RemoteMBeanServerImpl_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)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)You should contact [email protected]. That appears to be a WLS bug.
-- Rob
Guowei Shieh wrote:
does any one know why we get this call stack? what does this mean? We didn't change our deployment descriptor but it just comes up suddenly.
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ invalid assignment from 'Object' to 'Object' ]
at weblogic.utils.Debug.assertion(Debug.java:57)
at weblogic.utils.classfile.expr.LocalVariableExpression.codeAssign(LocalVariableExpression.java:38)
at weblogic.utils.classfile.expr.AssignStatement.code(AssignStatement.java:28)
at weblogic.utils.classfile.expr.CompoundStatement.code(CompoundStatement.java:26)
at weblogic.utils.classfile.CodeAttribute.setCode(CodeAttribute.java:44)
at weblogic.rmi.internal.StubGenerator.addMethodCode(StubGenerator.java:457)
at weblogic.rmi.internal.StubGenerator.<init>(StubGenerator.java:125)
at weblogic.rmi.internal.StubGenerator.<init>(StubGenerator.java:86)
at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:769)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:810)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:797)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:79)
at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:232)
at weblogic.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:45)
at weblogic.rmi.cluster.ReplicaAwareRemoteObject.initialize(ReplicaAwareRemoteObject.java:77)
at weblogic.rmi.cluster.ReplicaAwareRemoteObject.<init>(ReplicaAwareRemoteObject.java:50)
at weblogic.rmi.cluster.ClusterableRemoteObject.<init>(ClusterableRemoteObject.java:79)
at weblogic.rmi.cluster.ClusterableRemoteBinderFactory.getStateToBind(ClusterableRemoteBinderFactory.j
ava:45)
at weblogic.jndi.internal.WLNamingManager.getReplacement(WLNamingManager.java:180)
at weblogic.jndi.internal.WLNamingManager.getStateToBind(WLNamingManager.java:154)
at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.java:168)
at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:382)
at weblogic.jndi.internal.WLEventContextImpl.rebind(WLEventContextImpl.java:118)
at weblogic.ejb20.internal.StatelessEJBHome.activate(StatelessEJBHome.java:115)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1096)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1362)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:270)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:83)
at weblogic.j2ee.Application.deploy(Application.java:429)
at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:241)
at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:2946)
at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:2864)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1638)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1085)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:337)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.RemoteMBeanServerImpl.private_setAttribute(RemoteMBeanServerImpl.java:
430)
at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:386)
at weblogic.management.internal.RemoteMBeanServerImpl_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)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:
1034)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:340)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.RemoteMBeanServerImpl.private_setAttribute(RemoteMBeanServerImpl.java:
430)
at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:386)
at weblogic.management.internal.RemoteMBeanServerImpl_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)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) -
Hi,
Since Assertions are new addition to ver 1.4, can "assert" be treated as a new keyword? I could not find this anywhere else even in the Java Docs. Can someone please clarify?
Thanks,
Venkat DhurjatiThanks for your answer. My question is can we include the word "assert" in Java list of keywords. ie., just like "abstract" is a keyword, is "assert" also a keyword?
- Venkat -
Questioning assert()
Hi,
I have just started to use assert() having learned about how to compile assertions and enable them at runtime. I think it's a neat idea, like a mini-unit-test built into the language (obviously not as sophisticated as a real test case). But I am questioning how often I really want to use them -- it just seems like the code would be more robust if, instead of throwing AssertionError with assert(), I'd be better off checking the conditions and throwing a real exception that can be caught and handled. This is also more reliable than using assertions since in production, it is unlikely that assertions will be enabled.
They seem like a neat convenience but I have found myself continuing to do things like
private void doSomething(MyObject mo) {
if (mo == null)
throw new NullPointerException();
// doSomething code goes here
}(Obviously this can be extended to checking the range of passed numbers, or other conditionals.)
Am I using good practices? What do most people think of assertions?You should probably read the documentation as it
contains some advice on when to use (or rather when
not to use) assertions:
http://java.sun.com/j2se/1.4.1/docs/guide/lang/assert.h
ml
I would say that in your example it would be a good
idea to use assertions because the method is private
and therefore not part of the public API of your
program.Actually, that is why I specifically used private in my example, because I didn't want someone to end the thread by saying "No, you never use assert on public methods". I do know when not to use assertions (though admittedly I haven't read that page, b/c it fails to load, though I will read it later, thanks) -- generally assertions should never be used to check conditions that are critical to the program's integrity and which depend on outside (runtime) factors, because they are likely to be disabled when the program is used in production.
My point is to question this -- if assertions are usually disabled at runtime, why not just skip assertions altogether and check the condition/throw an exception? I can think of only one reason why assertions would be better, and that is when you don't want to bog down the performance of the program with tons of error-checking and exception throwing.
I'm just wondering if there are other reasons. -
Assertion error when closing QueueReceiver
Hi,
I initially posted this in the JMS newsgroup, but got the following response
from Zach:
This appears to a be a problem with class loaders and/or RMI,
that is to say it is not a JMS Problem. Specifically, the assertion
is ensuring that the thread has a class loader - and your thread does
not. The same check was in place for 6.0 so I am not sure why it
fails now on 6.1
Please post this in the rmi-iiop newsgroup.So here goes. One additional comment: when switching from WL 6.0 to 6.1, we
were able to improve the packaging of the application. With 6.0, we were
forced to make some of the classes available in the server's system
classpath. With 6.1, the application is now in an EAR file and uses a
Classpath: entry in the manifest file for referencing a utility package
(dc.jar). On the client side, the classpath contains weblogic.jar + the same
dc.jar file + another jar file containing various serializable classes
(value objects), JavaBeans etc that are necessary because we are passing
serialized objects as JMS messages.
Here is the original problem description:
We have a problem on WL6.1 with an application that used to work fine on WL
6.0 SP2. We have a JMS queue in the server, and a client process connects to
this queue. The application works fine, i.e. the client can both send and
receive messages on the queue without any problem. However, when the client
disconnects through the following bit of code:
public void stop() throws TransportException {
synchronized (jmsSync) {
try {
receiver.close();
session.close();
connection.close();
} catch (Exception e) {
throw new TransportException(e);
WL throws an AssertionError - see full trace below.
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Assertion
violated ]
at weblogic.utils.Debug.assert(Debug.java:74)
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:107)
at
weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.
java:211)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectIn
putStream.java:83)
at
weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectIn
putStream.java:115)
at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:56)
at
weblogic.rmi.internal.BasicRemoteRef.unmarshalReturn(BasicRemoteRef.java:230
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:134)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy2.dispatchSyncNoTranFuture(Unknown Source)
at
weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(Dispatcher
WrapperState.java:341)
at weblogic.jms.client.JMSSession.consumerClose(JMSSession.java:1331)
at weblogic.jms.client.JMSConsumer.close(JMSConsumer.java:329)
at ubiquity.dc.JMSComputer.stop(JMSComputer.java:112)
at ubiquity.rapids.matlab.Engine.stop(Engine.java:57)
at ubiquity.rapids.matlab.Engine.stopApplication(Engine.java:371)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Assertion
violated ]]
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
at $Proxy2.dispatchSyncNoTranFuture(Unknown Source)
at
weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(Dispatcher
WrapperState.java:341)
at weblogic.jms.client.JMSSession.consumerClose(JMSSession.java:1331)
at weblogic.jms.client.JMSConsumer.close(JMSConsumer.java:329)
at ubiquity.dc.JMSComputer.stop(JMSComputer.java:112)
at ubiquity.rapids.matlab.Engine.stop(Engine.java:57)
at ubiquity.rapids.matlab.Engine.stopApplication(Engine.java:371)
Thanks,
Alain.
Alain Rogister
http://www.ubiquity.beZach,
I checked this and the classloader is null, so this must be the cause of the
problem. Note that our JMS client app is installed as a W2K service. The
software we use registers the service with a set of parameters like this:
RapidsEngines.exe -install %1
%JAVA_HOME%\jre\bin\hotspot\jvm.dll -Djava.class.path=%ENGINE_CLASSPATH% -st
art ubiquity.rapids.matlab.Engine -stop
ubiquity.rapids.matlab.Engine -method stopApplication -out
%LOG_PATH%\stdout.log -err %LOG_PATH%\stderr.log
This means that, on the Engine class, the static main() method will be
called by the start event on the service (this is the default if no other
method is specified), and the stopApplication() static method will be called
by the stop event on the service. For some reason that I don't understand
yet, the ContextClassLoader is null at this point. Anyway, I guess if the
client connection to WL is just terminated without closing JMS resources
properly, WL will do the cleanup at some point.
Should I file a bug report anyway regarding the AssertionError that gets
thrown ?
Cheers,
Alain.
Alain Rogister
http://www.ubiquity.be
"Zach" <[email protected]> wrote in message
news:[email protected]..
Also, is this the bottom of the stack? Do you have a class loader
at the following place in the stack trace?
at ubiquity.dc.JMSComputer.stop(JMSComputer.java:112)
at ubiquity.rapids.matlab.Engine.stop(Engine.java:57)
at ubiquity.rapids.matlab.Engine.stopApplication(Engine.java:371)
if (Thread.getContextClassLoader() == null) {
System.out.println("DANGER WILL ROBINSON");
_sjz. -
Hi,
When I want to deploy my application on Bea Weblogic Server 8.1 SP4, I get the following error:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Assertion violated ]
at weblogic.utils.Debug.assertion(Debug.java:47)
at weblogic.j2ee.dd.J2EEDeploymentDescriptor.addJavaModule(J2EEDeploymentDescriptor.java:264)
at weblogic.j2ee.dd.xml.J2EEDeploymentDescriptorLoader_J2EE12.__post_3849685(J2EEDeploymentDescriptorLoader_J2EE12.java:412)
at weblogic.j2ee.dd.xml.J2EEDeploymentDescriptorLoader_J2EE12.postProc(J2EEDeploymentDescriptorLoader_J2EE12.java:248)
at weblogic.xml.process.ProcessorDriver.postProc(ProcessorDriver.java:211)
at weblogic.xml.process.ProcessorDriver.endElement(ProcessorDriver.java:94)
at weblogic.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:577)
at weblogic.apache.xerces.impl.xs.XMLSchemaValidator.endElement(XMLSchemaValidator.java:710)
at weblogic.apache.xerces.impl.XMLNamespaceBinder.endElement(XMLNamespaceBinder.java:647)
at weblogic.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:1937)
at weblogic.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:851)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1008)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1469)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
at weblogic.xml.jaxp.WebLogicParser.parse(WebLogicParser.java:67)
at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:137)
at weblogic.j2ee.dd.xml.J2EEDeploymentDescriptorLoader_J2EE12.process(J2EEDeploymentDescriptorLoader_J2EE12.java:147)
at weblogic.j2ee.dd.xml.DDUtils.processXML(DDUtils.java:369)
at weblogic.j2ee.dd.xml.DDUtils.processXML(DDUtils.java:322)
at weblogic.j2ee.dd.xml.DDUtils.loadStdDescriptor(DDUtils.java:217)
at weblogic.j2ee.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:181)
at weblogic.j2ee.J2EEApplicationContainerFactory.createMBeansForEar(J2EEApplicationContainerFactory.java:539)
at weblogic.j2ee.J2EEApplicationContainerFactory.initializeDeployment(J2EEApplicationContainerFactory.java:493)
at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:854)
at weblogic.management.deploy.DeployerRuntime.access$000(DeployerRuntime.java:69)
at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:1532)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:1523)
at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.runtime.DeployerRuntimeMBean_Stub.activate(DeployerRuntimeMBean_Stub.java:1139)
at weblogic.management.console.actions.mbean.ApplicationDeployAction.prePerform(ApplicationDeployAction.java:179)
at weblogic.management.console.actions.mbean.DoMBeanWizardAction.perform(DoMBeanWizardAction.java:215)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:173)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
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:1006)
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:6718)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
>
Any idea why this error is given and how to solve it? I don't think there is an error in my application, because it runs fine on Orion server.
The error is in a jar with:
-14 entity beans
-2 session beans with a relation to the entity beans
-session beans also with a relation to the other, but removing this relation does not help.I've hit assertion errors before. There is only one way I know of to isolate them.
Create a copy of your work so you don' disturb what you have now (the stuff that works on Orion).
Comment everything out of your ejb-jar and weblogic DD files so you have a trivial (e.g. one session bean) application. Add more things to the deployment one step at a time, redeploying at each step.
Then, when you get to the components or relationships
that cause the assertion failure, delete things one by one until you have the smallest number of components that cause the problem.
Then contact weblogic. If you aren't the first person who hit the problem, and ask nicely, they may cut a little patch for you containing code with the fix.
Not hard for them if they already did it for somebody else. Takes a lot longer if they actually have to
figure out what to fix first (and you best have a paid up support contract if it is a new problem).
Maybe you are looking for
-
Time machine backup from USB drive connected and backing up to Time Capsule
Hi all forum virgin here, so be gentle. I'll get straight to it. Much net trawling hasn't resulted in a definitive answer on this which surely I'm not alone in I have: MBP networked to TC (where TM resides) and USB drive connected. A- I simply want t
-
Need help in OID user Trusted recon
Hi all, I am using oim9.1.0.1,oid 9.0.4.7. When i run the OID user trusted recon it is bringing users based on pagesize.The problem is if i set the page size as 100 then it brought 98 users where as i have 30000 users in my OID.When i set the page si
-
Using Garageband as a sound source?
We have been trying to find a solution to the speed-change dilemma with GB - I have a 13 mins Cubase project that has 52 speed changes in it. It has been suggested by a Cubase person that we link the composer's Cubase PowerBook to our GB Desktop and
-
I'm trying to port an AS 2.0 file to AS 3.0 but I'm having trouble making the menu (little boxes) rotate, and I'm not sure what to do with a swapdepths(); in AS3.0. Here's my code: //------3D menu system in AS3.0-------------------------------------/
-
Selecting nodes using an XPath expression
Assuming that I have a DOM Document object containing a valid XML file, what is the quickest way to select a subset of nodes from the document using an XPath expression. I would like the results in either a NodeList object or another Document object.