NUMBER OF EJB's
How can I determine the max number of EJB's for a WLS, or for a cluster??
This max number is for EJB's or for instances of EJB's??
Thanks
J.Carlos
====================================================================
"Este mensaje y los documentos que, en su caso, lleve anexos, pueden
contener información confidencial. Por ello, se informa a quien lo
reciba por error que la información contenida en el mismo es reservada
y su uso no autorizado está prohibido legalmente, por lo que en tal
caso le rogamos que nos lo comunique por la misma vía o por teléfono
(981138847), se abstenga de realizar copias del mensaje o remitirlo o
entregarlo a otra persona y proceda a borrarlo de inmediato."
====================================================================
J. Carlos Ramis Oliver
[email protected]
Altia Consultores
====================================================================
Pat,
You are incorrect, otherwise our whole application would crash during
startup...
We have about 100 different EJBs, most of the entity EJBs having
max-beans-in-cache set to 10000 and more, and yet, we don't have any
problems with that.
The bug you are talking about (4390238 although it's disappeared from
Sun's bug DB) deals with different EJBs and mainly the number of loaded
classes, not EJB instances.
Dejan
Pat Bumpus wrote:
Hi,
I believe it is EJB instance. Therefore it would be the second choice below(the
calculation). BEA Support can give you specifics.
pat
"J.Carlos Ramis" <[email protected]> wrote:
Thanks a lot, but... 300-400 are diferent EJB (only its definition) or
the
number calculated by
number of EJB * max beans (instances of every EJB) * num. WLS in a cluster??
J.Carlos
"Pat Bumpus" <[email protected]> escribió en el mensaje
news:[email protected]...
Hi,
There isn't a maximum number of EJBs that you can deploy on WLS. It
is
constrainted
by the about of memory you have on your box. Having said that, there
is a
JDK
bug that has been reported to Sun (over and over again) which can cause
an
"out
of memory" exception when you have EJBs in the 300-400 range. As far
as I
know
that bug exists in JDK 1.3.
Also, you should review the deployment descriptors (ejb-jar.xml,
weblogic-ejb-jar.xml).
See http://e-docs.bea.com/wls/docs70/ejb/reference.html. There are
settings
which allow you to regulate the number of EJBs in cache etc.
To find more about the JDK bug mentioned above open a case with BEA
support and
ask them for information about the Sun bug with 300-400 EJBs and setting
MaxPermSize
as a workaround.
Hope this helps,
pat
"J.Carlos Ramis" <[email protected]> wrote:
How can I determine the max number of EJB's for a WLS, or for a cluster??
This max number is for EJB's or for instances of EJB's??
Thanks
J.Carlos
====================================================================
"Este mensaje y los documentos que, en su caso, lleve anexos, pueden
contener información confidencial. Por ello, se informa a quien lo
reciba por error que la información contenida en el mismo es reservada
y su uso no autorizado está prohibido legalmente, por lo que en tal
caso le rogamos que nos lo comunique por la misma vía o por teléfono
(981138847), se abstenga de realizar copias del mensaje o remitirlo
o
entregarlo a otra persona y proceda a borrarlo de inmediato."
====================================================================
J. Carlos Ramis Oliver
[email protected]
Altia Consultores
====================================================================
Similar Messages
-
How can I know the number of ejb instances
Hi all,
We need to know how can we get the number of ejb instances (entity and session) while the application is running.
We have a memory leak, so we need to know the amount opf memory used.
Please, it´s quite urgent, can anybody help us? It seems like an Oracle 9ias 903 bug.
ThanksI'm not sure if this will help you, but the "Spy" application that comes with OC4J stand-alone may help. I suggest you search this forum's archives for the words "Spy" and "AggreSpy".
Good Luck,
Avi. -
Maximum number of EJBs (any limitation?)
Hi,
Does anyone know what is the limitation as to the number of stateless session beans within a J2EE application server (Weblogic or Websphere)? Has anyone tried with hundreds of them in a single EAR? I would appreciate a response of someone who could shed some light about this or could point me to some technical documentation about it.
Thank you,Hello Alejca,
We have deployed multiple Stateless Session Beans [~20] with Maximum Bean Pool count as 100 and monitored the Performance.
It doesnot affect anything other than the Java Heap Size increases exponentially when the Beans are being used...
You need to take care of the Memory allocated for each Session Bean and consider Hardware Memory upgrade to handle such a load. The Application Server which we used was BEA Weblogic in JDK 1.3.1 Version. Though the JVM is enhanced for better performance and crash proof in JDK 1.4 and 1.5, the 1.3 JVM was able to handle the Bean creation and Garbage collection.
Some simple easy ways to monitor the bean and server performance are :
1. Create a Thread Program for each Bean. Spwan them in 100 of numbers to access the Beans.
2. Have some logic in the Beans so that some server processing is being done rather than simply calling and response coming back.
3. Open WebLogic / WebSphere Java Memory monitoring console to find any problems. You will be able to see that the garbage collection happens when the heap reaches its peak.
4. Moreover, you can also monitor the Bean Creation and Removal in the Bean Monitoring Console in WebLogic. I am not sure if this is available in WebSphere.
Other alternatives to monitor Server stability is to enable and monitor SNMP both in the Server OS level and BEA WebLogic Server level.
If you compare the request to response time, you can identify that the more load you throw in, the response time is more... But in reality if you believe that that is what you expect in you application, try increasing the Bean count or even the Java minimum and maximum memory paramater during startup...
Hope these tips help you. Do let us know what you have found...
Thanks and regards,
Pazhanikanthan. P -
Problem with Dynamically accessing EJB Class objects in WL 7.0 SP1
I am trying to build a component which has the ability to instantiate and execute
an known EJB method on the fly.
I have managed to build the component but when I try and execute it I get a ClassNotFoundException.
I know that the EJB I am trying to invoke is deployed and available on the server,
as I can see it in the console, I also seen to have been able to get the remote
interface of the object, my problem occurs when I try and access the class object
so I can perform a create on the object and then execute my method
The code I have written is below:
private Object getRemoteObject(Context pCtx, String pJNDIName, String pHomeBean)
throws Exception {
String homeCreate = "create";
Class []homeCreateParam = { };
Object []homeCreateParamValues = {};
try {
//This call seems to work and doesn't throw an exception
Object home = pCtx.lookup(pJNDIName);
//However this call throws a java.lang.ClassNotFoundException
Class homeBean = Class.forName(pHomeBean);
Method homeCreateMethod = homeBean.getMethod(homeCreate,homeCreateParam);
return homeCreateMethod.invoke(home, homeCreateParamValues);
} catch (NamingException ne) {
logStandardErrorMessage("The client was unable to lookup the EJBHome.
Please make sure ");
logStandardErrorMessage("that you have deployed the ejb with the JNDI
name "+pJNDIName+" on the WebLogic server ");
throw ne;
} catch (Exception e) {
logStandardErrorMessage(e.toString());
throw e;
Any advice would be really appreciated, I'm fast running out of ideas, I suspect
it has something to do with the class loader but I'm not sure how to resolve it
Regards
Jo CorlessHello Joanne,
Congratulations! I'm very happy that you've managed to fix your problem. It's
always essential to understand how to package applications when deploying on BEA
WebLogic. Usually, by throwing everything into an EAR file solves just about all
the class loader problems. :-) Let us know if you have any further problems that
we can assist you with.
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
"Joanne Corless" <[email protected]> wrote:
>
>
I've fixed it!!!!!!!!
Thanks to everyone who gave me help!!!!
The class loader was the culprit which is what I suspected all along.
As soon
as I put the 2 jar files I was using into an EAR file the problem went
away!!!!!
Thanks again
Jo Corless
"Ryan LeCompte" <[email protected]> wrote:
Hello Joanne,
As Mr. Woollen mentioned, I also believe it's a problem with the class
loader.
You need to be careful how you arrange your EJBs, because WebLogic has
a specific
method in which it loads classes in an EAR, JAR, and WAR file(s). Please
refer
to http://dev2dev.bea.com/articles/musser.jsp for more information about
BEA WebLogic
class loading mechanisms and caveats. Also, try printing out the various
methods
that are available on the object that was returned to you via reflection.
For
example, use the getMethods() method, which returns an array of Method
objects
that you can subsequently cycle through and print out the various method
names.
This way you can discover if the class found/returned to you is indeed
the one
you intend to locate.
Hope this helps,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
Rob Woollen <[email protected]> wrote:
I believe the issue is the home interface class for this EJB is not
available in the class loader which is doing the reflection.
If you do:
getClass().getClassLoader().loadClass(homeInterfaceClassName)
I suspect it will fail. Reflection still requires that the class be
loadable.
-- Rob
Joanne Corless wrote:
Hi Slava,
If I make my code look like you describe below I get a compliationerror telling
me that
home.getMethod() is not recognised (no such method)
If I change it slightly and use
Method homeCreateMethod =
home.getClass().getMethod(homeCreate,homeCreateParam);
The code will compile OK but when executed it still throws a NoSuchMethodException
Any ideas ?
Thanks for your help so far
Regards
Jo Corless
Your code should look like
Object home = pCtx.lookup(pJNDIName);
Method homeCreateMethod =
home.getMethod(homeCreate,homeCreateParam);
return homeCreateMethod.invoke(home, homeCreateParamValues);
Regards,
Slava Imeshev
"Joanne Corless" <[email protected]> wrote in message
news:[email protected]...
Hi Ryan,
I also wanted to mention that if you do a "header search" in this
particular
newsgroup
with the search query as "reflection", you will see many previousmessages
regarding
reflection and EJBs. I believe you could learn a lot from thedifficulties
that
others have faced and solved.I tried that and although there was a number of similar cases noneof them
actually
seem to fix my issue. Thanks for the suggestion though
Are the EJBs that you are trying to access accessible via your
system
classpath?
Try to avoid having them accessible via the main system classpath,and
only bundle
them in your appropriate EJB jar files (contained in an EAR file,for
example).Maybe I should have laid the problem out a little clearer.
I have a number of EJB's bundled up in a JAR file which is hot deployedto
the
server. Within this first JAR file is an EJB (SSB) component that
needs
to
be
able to invoke a known method on another EJB. This second EJB may
or
may
not be
within the first JAR file but it also will be hot deployed.
The component trying to invoke the method on the 2nd EJB has to
be
able to
create
an instance of the 2nd EJB without actually knowing anything bar
a
JNDI
Name which
is passed in at runtime.
I can get as far as doing the
Object home = pCtx.lookup(pJNDIName);
This returned a class with the name
"com.csc.edc.projects.allders.httppostoffice.postman.PostmanBean_mp8qy2_Home
Impl_WLStub"
My problem seems to occur when I try and invoke the create method
Method homeCreate = home.getClass().getMethod("create", new Class[0]);
My code throws a java.lang.NoSuchMethodException at this point so
I
am
unable
to progress to the next step of :
Object bean = homeCreate.invoke(home, null);
So I can return the instantiated bean back to the calling client.
Why am I getting the NoSuchMethodException, is is because I am gettinga
stub
back rather than the home interface and if so how do I get the truehome
interface
from the bean
Thanks in advance
Jo Corless -
How to use multiple ejb-jar.xml files
Hello -
If the project you work on has a lot of beans that you need to configure them in one ejb-jar.xml file. Then ejb-jar.xml file will be getting bigger and bigger. I am wondering if there is any way to divide the ejb-jar.xml file into multiple sub ejb-jar.xml files and then combin them together when deploy it. Same question question for the vendor ejb-jar.xml like weblogic-ejb-jar.xml.
Thanks!
BenHI Ben,
No, there is no notion of combining ejb-jar.xmls at deployment time in Java EE. There is no
set limit on the number of ejb components within an ejb-jar module either.
--ken -
I use the Ant task <xmlvalidate> in an EJB project to check the EJB XML deployment descriptors against their DTDs. Checking the (Sun-specified) "ejb-jar.xml" is fine. JDeveloper creates the OC4J specific deployment descriptor "orion-ejb-jar.xml" with a reference to the DTD located at "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd". Now this DTD seems to be broken.
Firstly, the DTD seems to have an invalid syntax. I'm not a DTD expert but Ant complains about lines 279-281 of that DTD :
279: isolation (commited | serializable | uncommited | repeatable_reads)
280: CDATA #IMPLIED
281: locking-mode (pessimistic | optimistic | read-only | old_pessimistic)
286: max-tx-retries CDATA #IMPLIED
287: update-changed-fields-only (true | false) "true"
There seems to be an attribut missing altogether at line 280 (see line 286) so I deleted that line. Then for lines 279 and 281, Ant complained about missing quotes - apparently, such an "enum" needs to have a "default value" (as in line 287), so I manually added such a value for each line.
The final error was in the "orion-ejb-jar.xml" (created by JDeveloper itself). Here is a piece of that:
<orion-ejb-jar>
<enterprise-beans>
<session-deployment max-instances="-1" name="DiscountCalculator"/>
I assume that the "max-instances" attribute sets the number of EJB instances in the OC4J pool to "unlimited". However, according to the DTD, session beans don't have such a "max-instances" attribute (lines 10-21):
<!-- Deployment info for a session bean. -->
ELEMENT session-deployment (env-entry-mapping*, ejb-ref-mapping*, resource-ref-mapping*)
ATTLIST session-deployment call-timeout CDATA #IMPLIED
copy-by-value CDATA #IMPLIED
location CDATA #IMPLIED
max-tx-retries CDATA #IMPLIED
name CDATA #IMPLIED
persistence-filename CDATA #IMPLIED
timeout CDATA #IMPLIED
wrapper CDATA #IMPLIED
replication CDATA #IMPLIED
>
So I copied and pasted the instances attribute from the entity bean section.
How come the DTD is broken? Even the 9.0.3 OC4J docs (http://download-east.oracle.com/docs/cd/A97688_08/generic.903/a97677/dtdxml.htm#620714) talk about all sorts of features (such as the "max-instances" attribute for session beans) and still points to the DTD "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd" that doesn't have these features at all.Karsten,
In case you are still on it, I stumbled upon this some time ago, too. My best guess is that they miss entire phrase, which I put in bold:
....mmited | repeatable_reads ) "commited"
disable-wrapper-cache CDATA #IMPLIED
locking-mode ( pesim...
(There is a line break between '"commited"' and 'disable-wrapper-cache'. 'commited', 'uncommited' must be MISSPELLED exactly as above.)
Btw, max-instances and min-instances are in the DTD that ships with 9.0.3 (jarred in oc4j.jar). This DTD, however, is still broken in the way that you found (it won't even XML-validate). How do they go around this? go figure! Oracle documentation? we all know ...
Best regards,
bjk -
Where do I deploy common EJB helper and utility classes
Hi,
I have a number of EJBs that each use a common set interfaces, exceptions and Value beans. If I deploy using the iasdeploy command line, then I must package up all these common classes within each of the EJB modules - leading to a lot of duplicate code.
Is there a smarter a way of packaged the common classes so that I can include them in the .EAR file but only in one module.
Note: I would prefer to only argument the IAS classpath with 3rd party classes that rarely change and not these common classes e.g. Jlog
cheers
DanielHi,
Try to put all the EJB's in a single package and import the package. I
can think of this solution right now, will keep posting for updates.
Regards
Raj
Daniel Westerdale wrote:
Hi,
I have a number of EJBs that each use a common set interfaces,
exceptions and Value beans. If I deploy using the iasdeploy command
line, then I must package up all these common classes within each of
the EJB modules - leading to a lot of duplicate code.
Is there a smarter a way of packaged the common classes so that I can
include them in the .EAR file but only in one module.
Note: I would prefer to only argument the IAS classpath with 3rd party
classes that rarely change and not these common classes e.g. Jlog
cheers
Daniel
Try our New Web Based Forum at http://softwareforum.sun.com
Includes Access to our Product Knowledge Base! -
I have created an EJB component which uses
some helper classes in JDeveloper 3.0 .
The component deploys sucessfully to OAS 4.0.8.1 . When I try to run the component through an applet ( including the _client.jar
in the archive tag) , the applet does not find the helper classes . How I do i include the helper classes in the _client.jar file ?Hi,
Try to put all the EJB's in a single package and import the package. I
can think of this solution right now, will keep posting for updates.
Regards
Raj
Daniel Westerdale wrote:
Hi,
I have a number of EJBs that each use a common set interfaces,
exceptions and Value beans. If I deploy using the iasdeploy command
line, then I must package up all these common classes within each of
the EJB modules - leading to a lot of duplicate code.
Is there a smarter a way of packaged the common classes so that I can
include them in the .EAR file but only in one module.
Note: I would prefer to only argument the IAS classpath with 3rd party
classes that rarely change and not these common classes e.g. Jlog
cheers
Daniel
Try our New Web Based Forum at http://softwareforum.sun.com
Includes Access to our Product Knowledge Base! -
Where do I put classes shared between EJBs and WAR
I have written some ValueObject classes stored in their own jar, they are used by a number of ejbs and and a Web application WAR. I have packaged the thing up as a single EAR but neither the EJBs or the jsps can see these classes.
How do I share these classes at each end. is their a general deployment descriptor solution or is it application server specific.
I am deploying to IBM Websphere 6verify .classpath file under your web folder for both options
Sorry, what do you mean is their a classpath value in the xml descriptors. I put my ValueObject into a jar within the WEB-INF\lib of the WAR but these arent seen by the EJBs which are within the EAR but not the WAR. Im not aware that there is a seperate WEB-INF directory for the EAR.
Structure as follows
app.ear
testejb.jar
META-INF
testweb.war
test.jsp
META-INF
WEB_INF
classes
testui.class
lib
valueobjects.jar -
We've got problems with respect to the number of EJB client threads (ExecuteThread) spawned by WebLogic in a client JVM. As the number of threads increase (~1700 in a JVM with 512Mb of memory and 2 hours of uptime), the JVM performance degrades substantially - although almost all these threads are waiting for requests, as one can see in the thread dump attached bellow.
This problem happens in an integration scenario involving both WebLogic (8.1 and 6.1 as service providers) and webMethods Integration Server (version 6.0.1); the webMethods EJB adapter (version 1.2) acts like EJB client from the WebLogic instances, and the "EJB client spawning threads" can be detected by thread dumps extracted from the Integration Server JVM. The URL property from the wm EJB adapter has been setup as t3://server:port. The Integration Server runs with Java HotSpot(TM) Server VM (build 1.4.2 1.4.2.02-040225-19:18-PA_RISC2.0 PA2.0 (aCC_AP), mixed mode) JRE in HP-UX (11.11) environment.
Although we couldn't reproduce this problem in a prod like environemnt, we'd identified that initially, WebLogic (weblogic.jar from WebLogic 6.1) spawns 5 ExecuteThreads plus 3 additional threads (TimeEventGenerator, SpinnerRandomSource and HighPriority TimeEventGenerator) in the first access of an EJB not matter the instance used, as well as two new threads (ExecuteThread) for each access to new WebLogic instances (different from previously accessed WebLogic instances). With weblogic.jar from the WebLogic 8.1 SP4 the behavior is slightly different: from the second instance access toward, only two new Threads (ExecuteThread in weblogic.JavaSocketReaders queue) are created.
We have also noticed that this problem should not be reflect of context classloaders because the counter of the ExecuteThread for the default pool only increases; in case of a pool cached in separate context classloaders, we should see "duplicate" threads with the same counter (starting with 0), which is not the case.
The questions are 1) why weblogic is spawning so much threads; 2) is there any setup/config to limit the number of WebLogic threads in the client context ?
Excerpt from the thread dump:
Full thread dump Java HotSpot(TM) Server VM (1.4.2 1.4.2.02-040225-19:18-PA_RISC2.0 PA2.0 (aCC_AP) mixed mode):
"ExecuteThread: '1749' for queue: 'default'" daemon prio=10 tid=05734140 nid=4813 lwp_id=583942 in Object.wait() [0x0dfbe000..0x0dfbe4f0]
at java.lang.Object.wait(Native Method)
- waiting on <4a5ef9f0> (a weblogic.common.internal.DynaQueue)
at weblogic.common.internal.DynaQueue.getW(DynaQueue.java:228)
- locked <4a5ef9f0> (a weblogic.common.internal.DynaQueue)
at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:252)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '1742' for queue: 'default'" daemon prio=10 tid=04c263f0 nid=4812 lwp_id=583845 runnable [0x06449000..0x064494f0]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:281)
- locked <4a5ee690> (a java.net.Socket)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '1735' for queue: 'default'" daemon prio=10 tid=05733fd8 nid=4811 lwp_id=583784 in Object.wait() [0x064ca000..0x064ca4f0]
at java.lang.Object.wait(Native Method)
- waiting on <4c40a6b8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:429)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
- locked <4c40a6b8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1734' for queue: 'default'" daemon prio=10 tid=01ecd940 nid=4810 lwp_id=583783 in Object.wait() [0x0654b000..0x0654b4f0]
at java.lang.Object.wait(Native Method)
- waiting on <4c40a728> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:429)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
- locked <4c40a728> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1733' for queue: 'default'" daemon prio=10 tid=05733e70 nid=4806 lwp_id=583777 in Object.wait() [0x066ce000..0x066ce4f0]
at java.lang.Object.wait(Native Method)
- waiting on <4c40a798> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:429)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
- locked <4c40a798> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1732' for queue: 'default'" daemon prio=10 tid=01ecd7d8 nid=4801 lwp_id=583771 in Object.wait() [0x065cc000..0x065cc4f0]
at java.lang.Object.wait(Native Method)
- waiting on <4c40a808> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:429)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
- locked <4c40a808> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1731' for queue: 'default'" daemon prio=10 tid=05733d08 nid=4798 lwp_id=583766 in Object.wait() [0x067d0000..0x067d04f0]
at java.lang.Object.wait(Native Method)
- waiting on <4c40a878> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:429)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
- locked <4c40a878> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
... (cut for brevity)
"ExecuteThread: '2' for queue: 'default'" daemon prio=10 tid=009251b8 nid=172 lwp_id=569500 in Object.wait() [0x3d61f000..0x3d61f4f0]
at java.lang.Object.wait(Native Method)
- waiting on <4a5b4498> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:429)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
- locked <4a5b4498> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1' for queue: 'default'" daemon prio=10 tid=00924ee8 nid=171 lwp_id=569499 in Object.wait() [0x3d6a0000..0x3d6a04f0]
at java.lang.Object.wait(Native Method)
- waiting on <4a5b40f0> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:429)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
- locked <4a5b40f0> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '0' for queue: 'default'" daemon prio=10 tid=00925050 nid=170 lwp_id=569498 in Object.wait() [0x3d7a2000..0x3d7a24f0]
at java.lang.Object.wait(Native Method)
- waiting on <4a5b3d48> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:429)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
- locked <4a5b3d48> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"Thread-2" daemon prio=10 tid=00bec5f0 nid=18 lwp_id=569246 in Object.wait() [0x41e2e000..0x41e2e4f0]
at java.lang.Object.wait(Native Method)
- waiting on <46c14ff0> (a com.wm.app.repov4.server.RepoServer$RepoLockTimeoutMgr)
at com.wm.app.repov4.server.RepoServer$RepoLockTimeoutMgr.run(RepoServer.java:1533)
- locked <46c14ff0> (a com.wm.app.repov4.server.RepoServer$RepoLockTimeoutMgr)
"Thread-1" daemon prio=10 tid=00bec488 nid=17 lwp_id=569244 in Object.wait() [0x41eaf000..0x41eaf4f0]
at java.lang.Object.wait(Native Method)
- waiting on <46c150a8> (a com.wm.driver.queue.data.DataQueue)
at java.lang.Object.wait(Object.java:429)
at com.wm.driver.queue.data.DataQueue.dequeue(DataQueue.java:310)
- locked <46c150a8> (a com.wm.driver.queue.data.DataQueue)
at com.wm.driver.queue.data.DataQueue.dequeueCommit(DataQueue.java:260)
- locked <46c150a8> (a com.wm.driver.queue.data.DataQueue)
at com.wm.driver.queue.data.DataQueue.dequeueCommit(DataQueue.java:254)
- locked <46c150a8> (a com.wm.driver.queue.data.DataQueue)
at com.wm.app.repov4.server.RepoServerBase$RepoEventManager.run(RepoServerBase.java:224)
"Log Thread" prio=10 tid=00bec320 nid=16 lwp_id=569243 in Object.wait() [0x41f30000..0x41f304f0]
at java.lang.Object.wait(Native Method)
- waiting on <46c15120> (a com.wm.util.sync.SimpleQueue)
at com.wm.util.sync.SimpleQueue.deq(SimpleQueue.java:171)
- locked <46c15120> (a com.wm.util.sync.SimpleQueue)
at com.wm.util.sync.SimpleQueue.deq(SimpleQueue.java:126)
- locked <46c15120> (a com.wm.util.sync.SimpleQueue)
at com.wm.app.b2b.server.ServerLogHandler$LogThread.run(ServerLogHandler.java:268)
"Cron Daemon" prio=10 tid=00bec1b8 nid=15 lwp_id=569241 in Object.wait() [0x41fb1000..0x41fb14f0]
at java.lang.Object.wait(Native Method)
- waiting on <46c15190> (a java.util.Vector)
at com.wm.util.Cron.run(Cron.java:424)
- locked <46c15190> (a java.util.Vector)
at java.lang.Thread.run(Thread.java:534)
"Cron Daemon Pool2" prio=10 tid=00bec050 nid=14 lwp_id=569240 in Object.wait() [0x42032000..0x420324f0]
at java.lang.Object.wait(Native Method)
- waiting on <46c15268> (a com.wm.util.pool.PooledThread)
at java.lang.Object.wait(Object.java:429)
at com.wm.util.pool.PooledThread.run(PooledThread.java:103)
- locked <46c15268> (a com.wm.util.pool.PooledThread)
at java.lang.Thread.run(Thread.java:534)
"Cron Daemon Pool1" prio=10 tid=00bebee8 nid=13 lwp_id=569239 in Object.wait() [0x420b3000..0x420b34f0]
at java.lang.Object.wait(Native Method)
- waiting on <46c152d0> (a com.wm.util.pool.PooledThread)
at java.lang.Object.wait(Object.java:429)
at com.wm.util.pool.PooledThread.run(PooledThread.java:103)
- locked <46c152d0> (a com.wm.util.pool.PooledThread)
at java.lang.Thread.run(Thread.java:534)
"webMethods Integration Server" prio=10 tid=000870e0 nid=12 lwp_id=569238 in Object.wait() [0x42134000..0x421344f0]
at java.lang.Object.wait(Native Method)
- waiting on <46c152f0> (a com.wm.app.b2b.server.Server)
at java.lang.Object.wait(Object.java:429)
at com.wm.app.b2b.server.Server.run(Server.java:353)
- locked <46c152f0> (a com.wm.app.b2b.server.Server)
"Signal Dispatcher" daemon prio=10 tid=00086f78 nid=7 lwp_id=569231 waiting on condition [0x00000000..0xffffffff]
"Finalizer" daemon prio=10 tid=00086e10 nid=5 lwp_id=569229 in Object.wait() [0x4293b000..0x4293b4f0]
at java.lang.Object.wait(Native Method)
- waiting on <46c15668> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
- locked <46c15668> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:188)
"Reference Handler" daemon prio=10 tid=00086ca8 nid=4 lwp_id=569228 in Object.wait() [0x429bc000..0x429bc4f0]
at java.lang.Object.wait(Native Method)
- waiting on <46c15340> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:429)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:120)
- locked <46c15340> (a java.lang.ref.Reference$Lock)
"main" prio=10 tid=00086b40 nid=1 lwp_id=569222 in Object.wait() [0x68ff3000..0x68ff24f0]
at java.lang.Object.wait(Native Method)
- waiting on <46c152f0> (a com.wm.app.b2b.server.Server)
at java.lang.Thread.join(Thread.java:1001)
- locked <46c152f0> (a com.wm.app.b2b.server.Server)
at java.lang.Thread.join(Thread.java:1054)
at com.wm.app.b2b.server.Server.start(Server.java:141)
at com.wm.app.b2b.server.Main.main(Main.java:40)
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 com.wm.proxy.Proxy.invokeStaticMethod(Proxy.java:166)
at com.wm.app.server.ServerProxy.ServerMain_main(ServerProxy.java:77)
at com.wm.app.server.ServerApp.start(ServerApp.java:105)
at com.wm.app.Application.launch(Application.java:490)
at com.wm.app.server.Main.main(Main.java:50)
"VM Thread" prio=7 tid=000167f8 nid=3 lwp_id=569227 runnable
"VM Periodic Task Thread" prio=8 tid=00016908 nid=11 lwp_id=569235 waiting on condition
"Suspend Checker Thread" prio=10 tid=00016880 nid=6 lwp_id=569230 runnableWe already opened a case. Actually, we did reproduce the problem: it happens because there is a hardware load balancing between the client and the WebLogic Server.
As far as I know, EJB load balancing can be done only with WebLogic clusters. Could you confirm that ? -
Problem in deploying EJBs (More than 390) in weblogic-BEA says JDK issue!!!
Our application had 390 EJBs before the current build. It was running fine on Weblogic 6.1-SP4 with JDK 1.3.1_08.
In the current build, 3 EJBs were introduced and the Weblogic server started giving deployment problems. We then came across the Weblogic Bug stating the magic Number of 390 and delegating it to a SUN Bug. But, contrary to the SUN bug which says of a OutofMemory issue, we were not getting any OutOfMemory error.
Then, just to test the 390 number, we cut downed on the number of EJBs reducing the number to 388, in a test environment. EJBs got deployed without problem. Then we added 3 EJBs (increasing the EJB count to 391), and Weblogic server started giving Deployment problem in a EJB which was one of the 388 that were running fine earlier.But, now also there was no OutOfMemory error. Then we removed one of the newly added EJBs to bring the EJB count to 390. The Weblogic deployed the EJBs without error(even the one which was giving problem when EJB count was 391).
So, 390 seems to be the number but, contrary to BEA problem ID: 035884 which delegates the problem to SUN Bug ID:4390238 (Incidentally SUN has closed this bug as Non-reproducable), we are not getting any OutOfMemory error.
My questions to the JAVA community are:
1)Is the problem really related to JDK or Weblogic?
2)If it's a problem with JDK, then what should be done to fix it?
==========================================
A deployment error generated is pasted below:
==========================================
java.lang.reflect.InvocationTargetException: weblogic.management.DistributedManagementException: Distributed Management [1 exceptions]
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:559)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
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 $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
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.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Distributed update exception
- remote object: stellar:Location=primary-server,Name=primary-server,Type=ServerConfig
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@1d5ebc
- actionName: addDeployment
- params: [Ljava.lang.Object;@5f97ae
- signature: [Ljava.lang.String;@5f28a6
Distributed update exception
- remote object: stellar:Location=primary-server,Name=primary-server,Type=ServerConfig
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@1d5ebc
Unable to deploy EJB: STTaskPrivilegeLinkEntity from Entities.jar:
java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:165)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:307)
at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:362)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
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:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
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 $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
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.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
[java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS]
at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:367)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
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:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
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 $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
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.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1087)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
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:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
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 $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
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.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Unable to deploy EJB: STTaskPrivilegeLinkEntity from Entities.jar:
java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:165)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:307)
at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:362)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
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:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
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 $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
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.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
[java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS]
at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:367)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
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:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
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 $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
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.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.DistributedOperationUpdateException:
Unable to deploy EJB: STTaskPrivilegeLinkEntity from Entities.jar:
java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:165)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:307)
at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:362)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
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:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
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 $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBSo, 390 seems to be the number but, contrary to BEA
problem ID: 035884 which delegates the problem to SUN
Bug ID:4390238 (Incidentally SUN has closed this bug
as Non-reproducable), we are not getting any
OutOfMemory error.Did you check the server logs? There might be an OutOfMemoryError logged.
My questions to the JAVA community are:
1)Is the problem really related to JDK or Weblogic?Apparently, the problem is with the Weblogic. Did you try deploying the same number on some higher version of Weblogic? (7.0 for instance)
2)If it's a problem with JDK, then what should be
done to fix it?Check the bug database for the same bug id. There is a workaround posted. The evaluation comments are also hinting at using the suggested VM options.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4390238 -
Performance Test resulting in more EJB bean instances
Hi Guys,
I am trying to profile my application using OptimizeIT.
If I conduct a load test using Load Runner , But for the test I am using only
virtual client continously repeating the same operation for a period of an hour
or so. I expect only entity bean instance to cater to the needs . What I observe
from OptimizeIT is the number of instances of entity bean continously increases
My question is when the same thread is doing the operation the Entity Bean instance
which catered to the need during the first round should be able to process client
request second time. Why should the bean instance continously increase?
Thanks in advance,
KumarKumar Raman wrote:
Hi Rob,
I am unable to send the .snp file as the file size is coming out to be 6 MB which
our mail server is not allowing to send thorough (we have a corporate limit of
3MB). If U have any other way across please let me know.Did you try compressing it? Or, just split it in multiple files and
send them separately. If none of that works, send me a private email,
and I can get you a FTP upload.
>
As regards to 2 questions
1) I know as to why two instances are getting created as I can see the code here.
But I really wanted to know as to when these instances be released from the memory
? They'll be kept in the cache at least until the transaction ends. Since
you're deleting them, they'll be removed from the cache and sent to the
pool when the tx completes.
Is this going to be there till the pool size defined is filled? I haven,t defined
any pool size in our configuration. I feel the default size is 1000.
Yes, they will be in the pool, and the default pool size is 1000.
2) As regards to 2nd question , the add/delete are running in different transaction.
I wanted to know as to whether the instances created during add , be used for
delete operation as well.
They can/should be the same instance. What is your concurrency-strategy
setting for this bean? I know in the past that exclusive concurrency
was not reusing bean instances as well as some of the other concurrency
strategies (eg database / optimistic).
3) Also for each of the bean instance will there be corresponding home instances
also floating in memory. I feel the home instances should be reusable.
There's just 1 home instance for the deployment, not 1 per bean.
In case of simple Entity bean creation in weblogic, how many objects will be
created vis. a vis , home object , remote object so on...
You'll need a bean interface (local and/or remote) and a bean
implementation class.
As the number of instances which OptimizeIT shows is beyond my understanding.
I wanted to ensure is there any configuration to help me optimize these creations.
Ok, let's try to get the snapshot to me so I can help you out.
-- Rob
>
Thanks,
Kumar
Rob Woollen <[email protected]> wrote:
Kumar Raman wrote:
Hi,
Actually we are running a scenario using Load Runner tool to add arow onto a
DB using an Container managed Entity Bean. This Bean is getting instantiated
using a Session Bean. In the workflow after creation we are deletingthe row in
the table by using the remove method of the same entity bean.
If we analyze using the profiler, the number of EJB instances increasesby 2 during
add and increases by another 2 after delete.Is your session bean only creating one bean?
There seems to be 2 questions:
1) Why are you getting 2 beans on add/delete? I'm not sure if you
expect this or not.
2) Why are the beans used for the creation not being used again when
you
issue the delete?
For #2, my first question is if the create and remove are both running
in the same transaction?
I am sending the OptimizeIT (ver5.5) snapshots to you by mail.
Haven't received them yet, but they would be very helpful.
-- Rob
Please let me know as to why the instances are increasing inspite explicitlycalling
the remove method in the code.
Thanks,
Kumar
Rob Woollen <[email protected]> wrote:
We'd need a little more information to diagnose this one.
First off, if you have an OptimizeIt snapshot file (the .snp extension
not the HTML output file), I'd be willing to take a look at it and
give
you some ideas. If you're interested, send me an email at rwoollenat
bea dot com.
If you're using a custom primary key class (ie not something like
java.lang.String), make sure it's hashCode and equals method are correct.
Otherwise, it'd be helpful if you gave us some more info about yourtest
and what you're doing with the entity bean(s).
-- Rob
Kumar Raman wrote:
Hi Guys,
I am trying to profile my application using OptimizeIT.
If I conduct a load test using Load Runner , But for the test I amusing only
virtual client continously repeating the same operation for a periodof an hour
or so. I expect only entity bean instance to cater to the needs .
What
I observe
from OptimizeIT is the number of instances of entity bean continouslyincreases
My question is when the same thread is doing the operation the EntityBean instance
which catered to the need during the first round should be able toprocess client
request second time. Why should the bean instance continously increase?
Thanks in advance,
Kumar -
EJB as Web Service doesnot Return value
Hi All,
I have cerated an EJB Wihich fetches the vendor data from MDM database,this EJB I have exposed as a web service.
This Ejb returns an array of object of java class which contains 7 attributes,
Like Vendor number,
City,
country,
Name,
company code,
purchase organization.
Now when i debug the EJB it is returning proper values with all attribute.
But in the web services response am able to get same number of records but attribute list is less...like I am getting the value of only City ,country and Vendor Number although EJB is returning all the values.
If any one can help me with the problem.
Thanks in advance.
ShrutiHai,
Is that returning java class is having setters and getters, and implementing serializable.
look like
public class beanToTest implements Serializable{
private String vendornumber=null;
private String city=null;
private String country=null;
private String name=null;
private String companyCode=null;
private String purchaseOrganization=null;
@return
public String getCity() {
return city;
@return
public String getCompanyCode() {
return companyCode;
@return
public String getCountry() {
return country;
@return
public String getName() {
return name;
@return
public String getPurchaseOrganization() {
return purchaseOrganization;
@return
public String getVendornumber() {
return vendornumber;
@param string
public void setCity(String string) {
city = string;
@param string
public void setCompanyCode(String string) {
companyCode = string;
@param string
public void setCountry(String string) {
country = string;
@param string
public void setName(String string) {
name = string;
@param string
public void setPurchaseOrganization(String string) {
purchaseOrganization = string;
@param string
public void setVendornumber(String string) {
vendornumber = string;
Regards,
naga -
I am trying to deploy an application with 22 EJBs. (yes, I know that's a lot...mostly for development) When I try this, I continually get the error "An error occurred while redeploying the application. Nested exception Root Cause: Syntax error in source. Syntax error in source".
When I install the application with only 21 EJBs, all seems ok. Even if I just add an "empty" EJB, I get this error. Is there a maximum allowable number of EJBs for an application? Is there a way to change this?
As always, thanks in advance!!Sorry, as always, I forget this:
Oracle9iAS release 2 running RedHat 8.0 -
JDeveloper 3.1 and JDK1.2.2: are they REALLY compliant?
Hi,
I've already been developing in JDev 3.0 using Java 1.1.8 for a few months and have a number of EJB's deployed in an Oracle8i 8.1.5 database. These are accessed by a servlet which is called from a C++ application in order to populate the db tables. I'm using Java Webserver 2.0 and everything works fine.
I've been upgrading to Java 2 with JDev 3.1, Oracle 8i R2, and JDK1.2.2. Everything again works fine when I am testing and debugging in the JDev 3.1 IDE but when I deploy to the Web server, my context lookup for the EJB published name freezes, returns an error status to the C++ app but does not display any error/exception msgs in the server console/log files.
On investigating I found that the java.exe bundled with JDev 3.1 as the JDK1.2.2 version is actually NOT the java.exe that has been dispatched with the release version of JDK1.2.2! There are however two files in the bin directory of the JDK1.2.2 called oldjava.exe and oldjavaw.exe which correspond to the ones bundled with JDev 3.1?
Could someone please explain what is going on? As it stands at the moment the version of java.exe with JDK1.2.2 does not work for my EJB's but if I replace it with the oldjava.exe, it works fine. Does this mean that JDev 3.1 is NOT actually JDK1.2.2 compliant or have I done something wrong?
This is potentially a major problem for our projects so if anyone at Oracle has any info it would be greatly appreciated.
Cheers
DaveDavid,
I changed Sun Java 1.2.2 VM to JDeveloper 3.0 1.1.8 VM and now I get this:
[Root exception is java.lang.ClassNotFoundException: EJBBibles.BibleSearchHomeHelper]javax.naming.Na
mingException: Unknown reasons
at oracle.aurora.jndi.sess_iiop.SessionCtx._activate(SessionCtx.java:82)
at oracle.aurora.jndi.sess_iiop.SessionCtx.activate(SessionCtx.java:276)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.lookup(ServiceCtx.java:320)
at oracle.aurora.jndi.sess_iiop.sess_iiopURLContext.lookup(sess_iiopURLContext.java:215)
at oracle.aurora.jndi.sess_iiop.sess_iiopURLContext.lookup(sess_iiopURLContext.java:201)
at javax.naming.InitialContext.lookup(InitialContext.java:288)
at EJBBiblesServlet.Servlet1.init(Servlet1.java:36)
at org.apache.tomcat.core.ServletWrapper.initServlet(ServletWrapper.java:315)
at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:445)
at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:597)
at org.apache.tomcat.servlets.InvokerServlet.service(InvokerServlet.java:257)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:503)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:559)
at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHand
ler.java:160)
at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:338)
at java.lang.Thread.run(Thread.java:466)
If I use JDev 1.2 VM, I get this:
javax.naming.NotContextException: fumaca:2481:eatg/test/BibleSearchRemote
java.lang.Object oracle.aurora.jndi.sess_iiop.sess_iiopURLContext.lookup(javax.naming.Name)
java.lang.Object oracle.aurora.jndi.sess_iiop.sess_iiopURLContext.lookup(java.lang.String)
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
void EJBBiblesServlet.Servlet1.init(javax.servlet.ServletConfig)
void org.apache.tomcat.core.ServletWrapper.initServlet()
void org.apache.tomcat.core.ServletWrapper.handleRequest(org.apache.tomcat.core.Request, org
.apache.tomcat.core.Response)
void org.apache.tomcat.core.ServletWrapper.handleRequest(org.apache.tomcat.core.HttpServletR
equestFacade, org.apache.tomcat.core.HttpServletResponseFacade)
void org.apache.tomcat.servlets.InvokerServlet.service(javax.servlet.http.HttpServletRequest
, javax.servlet.http.HttpServletResponse)
void javax.servlet.http.HttpServlet.service(javax.servlet.ServletRequest, javax.servlet.Serv
letResponse)
void org.apache.tomcat.core.ServletWrapper.handleRequest(org.apache.tomcat.core.Request, org
.apache.tomcat.core.Response)
void org.apache.tomcat.core.ContextManager.service(org.apache.tomcat.core.Request, org.apach
e.tomcat.core.Response)
void org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(org.apache.tomca
t.service.TcpConnection, java.lang.Object[])
void org.apache.tomcat.service.TcpConnectionThread.run()
void java.lang.Thread.run()
Which means that there is a difference relative to the VM version.
All the names are correct on 8i deployment. And all necessary files are on classpath, (including the EJB source and generated jars, that are also in the /lib on the context dochome).
Any thoughts?
Thanks,
Eduardo
null
Maybe you are looking for
-
Cancelling a report when no data found
Hi All! I have a report that prints directly to the printer. But if the report query fetches no data then a blank page is printed. How should I raise a customized message and stop the report execution if there is no data found? Thanks in advance
-
What's wrong with this html and css code? ref: Create your first website tut.
In reply to David Powers re: design view doesn't translate to browser. I hope this is the approved way to send copies of code and images. <!doctype html> <html> <head> <meta charset="utf-8"> <title>cable cars</title> <link href="main.css" rel="style
-
Total option in REUSE_ALV_LIST_DISPLAY
Hi, If we CHECK total option in REUSE_ALV_LIST_DISPLAY we get a total of numeric value with yellow color at the bottom. Requirement: Let say I have 3 line item records in the display, with 20 fields and one amount field. So I get the total of the amo
-
The Vertical example in the FlashHelp SDK provided with RHX5 (help example with safari guides for Africa), there are popup links that expand the text content of the current paragraph by adding an explanation in-line with the popup link. There is one
-
Viewing seamless textures in a grid
I am making seamless textures, and I was wondering is there a way to see the texture in a grid. Like side by side, vertically and horizontally. Still better if the grid can be zoomed in and out, so i can see the texture in different scales.