Informing an ejb container of dirty beans

I'm working on a system which automatically generates entity beans and one use of this technology is to make legacy databases available as entity beans.
I'd like to provide entity beans as an incremental integration approach for databases which are still being used by legacy systems. To do this I need to be able to tell the bean container when an object has been updated by an external system. I realize this may play hell with transactions and such, but in some cases this will be acceptable and allow a nice incremental movement to j2ee.
Are there ways to tell a container about a "dirty" bean?

Never mind - I don't really need the container's involvement (duh). The beans themselves can be made aware of external changes and reload when they need to.

Similar Messages

Dynamic Class Loading in an EJB Container

Hello,
We have a need to load classes from a nonstandard place with in an ejb container, ie a database or secure store. In order to do so we have created a custom class loader. Two issues have come up we have not been able to solve, and perhaps some one knows the answer to.
Issue 1.
Given the following code:
public static void main(String args[])
MyClassLoader loader = new MyClassLoader("lic.dat");
System.out.println("Loading class ..." + "TestObject");
Object o = Class.forName("TestObject",true,loader).newInstance();
System.out.println("Object:" + o.toString());
TestObject tstObj = (TestObject) o;
tstObj.doIt();
What happens when executed is as follows. Class.forName calls our loader and does load the class as we hoped, it returns it as well, and the o.toString() properly executes just fine. The cast of the object to the actual TestObject fails with a class not found exception. We know why this happens but don't know what to do about it. It happens because the class that contains main was loaded by the system class loader (the primordial class loader as its sometimes called), That class loader does not know about TestObject, so when we cast even though the class is "loaded" in memory the class we are in has no knowledge of it, and uses its class loader to attempt to find it, which fails.
> So the question is how do you let the main class know to use our class loader instead of
the system class loader dispite the fact is was loaded by the system class loader.
Issue 2:
To make matters worse we want to do this with in an EJB container. So it now begs the question how do you inform an EJB container to use a specific class loader for some classes?
Mike...

Holy crap! We are in a similar situation. In creating a plugin engine that dynamically loads classes we use a new class loader for each plugin. The purpose is so that we can easily unload and/or reload a class at runtime. This is a feature supposedly done by J2EE app servers for hot-deploy.
So our plugins are packaged as JAR files. If you put any class in the CLASSPATH, the JVM class loader (or the class loader of the class that is loading the plugin(s)), will load the class. The JavaDoc API states that the parent classloader is first used to see if it can find the class. Even if you create a new URLClassLoader with NULL for parent, it will always use the JVM class loader as its parent. So, ideally, in our couse, plugins will be at web sites, network drives, or outside of the classpath of the application and JVM.
This feature has two benefits. First, at runtime, new updates of plugins can be loaded without having to restart the app. We are even handling versions and dependencies. Second, during development, especially of large apps that have a long startup time, being able to reload only one plugin as opposed to the annoying startup time of Java apps is great! Speeds up development greatly.
So, our problem sounds just like yours. Apparently, the Client, which creates an instance of the plugin engine, tries to access a plugin (after the engine loades it via a new classloader instance for each plugin). Apparently, it says NoDefClassFound, because as you say, the client classloader has no idea about the plugin class loaded by another classloader.
My co-developer came up with one solution, which I really dont like, but seems to be the only way. The client MUST have the class (java .class file) in its classpath in order to work with the class loaded by another class loader. Much like how in an EJB container, the web server calling to EJB MUST contain the Home and Remote interface .class files in its classpath, the same thing needs to be done here. For us, this means if a plugin depends on 5 others, it must contain ALL of the .class files of those plugins it depends on, so that the classloader instance that loads the plugin, can also see those classes and work with them.
Have you got any other ideas? I really dislike that this has to be done in this manner. It seems to me that the JVM should be able to allow various class loaders to work with one another in such a way that if a client loaded by one classloader has an import statement in it to use a class, the JVM should be able to fetch the .class out of the other classloader and share it, or something!
This seems to me that there really is no way to actually properly unload and then reload a class so that the JVM will discard and free up the previous class completely, while using the new class.
I would be interested in discussing this topic further. Maybe some others will join in and help out on this topic. I am surprised there isn't a top-level forum topic about things like class loaders, JVM, etc. I wish there was a way to add one!

Proxying EJB Container Request

Hi,
As part of our application we have an Applet that requires communication
with EJB Container objects (Session beans, Message-driven beans ). Rather
than executing RMI calls directly to the WLS Cluster we would like to proxy
these requests through our web-server (IIS 5.0). I was wondering if
there's a way for us to do this (route the EJB Container requests through
the IIS webserver) without having to write Proxy Servlets?
Any help would be appreciated!
Regards,
OA

EnterTheDragon wrote:
it is said *'EJB container maintains an instance pool.'*
Is it a pool of Session beans ? is it a pool of Entity beans ?
Can anybody please elaborate at this part what pool they talk about ?The part of the pool that holds things, would be the part that holds instances.

How can i locate the properties files within a ejb container?

when i develop servlet+javabean structure application,in order to imploement decoupling,i
would like to write the config information in the properties files(key-value pair),in
servlet,i use "getResourceAsStream(String relativePath)" method to retrieve the
configuration information from the properties files(i even write the SQL clause
in the files),it alwsys works well.
now,i want to implement such function within the ejb container,that is to read
a properties file from session bean,but i don't know how can i locate the file
within the ejb container by using relative path,i wonder if there is the same
method within ejb container as "getResourceAsStream(.......)" method within servlet
container?
thanks for any helps!
the code snippet is appreciated!

In general, you should look at using environment entries (variables) in the
deployment descriptors (both the war and EJB jar rather than properties
files for configuring J2EE applications. The reasons for this are many:
1. This is the official way to do it according to the spec. Properties
files are the J2SE way of doing things
2. As you note, that it's not obvious how you would (legally) read a
properties file inside an EJB.
3. It's consistent between the web and EJB part of your code
4. the weblogic console and tools have good capabilities to edit these
fields.
Kent
"zhebincong" <[email protected]> wrote in message
news:[email protected]..
>
when i develop servlet+javabean structure application,in order toimploement decoupling,i
would like to write the config information in the propertiesfiles(key-value pair),in
servlet,i use "getResourceAsStream(String relativePath)" method toretrieve the
configuration information from the properties files(i even write the SQLclause
in the files),it alwsys works well.
now,i want to implement such function within the ejb container,that is toread
a properties file from session bean,but i don't know how can i locate thefile
within the ejb container by using relative path,i wonder if there is thesame
method within ejb container as "getResourceAsStream(.......)" methodwithin servlet
container?
thanks for any helps!
the code snippet is appreciated!

Logging ejb container operations

Hello guys,
I'm new to WebLogic, so excuse me for such, probably, a faq-question.
Is there a way to enable logging of EJB container operations? I.e. to make the
container to log what beans, what cmp and cmr fields it loads.
TIA,
alex

"alex" <[email protected]> wrote
I'm new to WebLogic, so excuse me for such, probably, a faq-question.No problem...
Is there a way to enable logging of EJB container operations? I.e. to make the
container to log what beans, what cmp and cmr fields it loads.Well, first start here:
http://edocs.bea.com/wls/docs70/logging/
NOTE: This documentation applies to version 7.0 of WebLogic Server.
Next, I'd make sure my WebLogic Server was sending (to STDOUT)
low-level DEBUG messages -- that appears to be the sort of information
you are looking to obtain from your EJB operations. One of the things
I did on a project a while back was create an object that contained a
boolean value (within my app.). Then, to enable/disable this
debugging, we'd appropriately toggle this value. Do you understand
what I mean?
Hope this helps...
Brian J. Mitchell
BEA Systems Administrator
TRX
Atlanta, GA
email: [email protected]
office: 404-327-7238
mobile: 678-283-6530

Error at SJSAS-8_1(XP Pro SP2) startup:Can't create EJB Container

Hi Guys,
I installed Sun Java System App Server v.8 update 1 on my XP Pro(SP2) machine.
Here are the particulars:
Install Dir : C:\Sun\AppServer
Java Version : 1.4.2_04
J2EE_HOME: Set to Install Dir
JAVA_HOME:C:\j2sdk1.4.2_04
PATH : Includes [Install Dir] \ bin
Here is the problem(On the very first run,I verified):
-----------------------------------------------SNIP--------------------------------------------------------------------------------
[#|2004-11-15T03:26:52.812+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-11-15T03:26:53.343+0530|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5090: Exception in creating EJB container [java.lang.RuntimeException: java.lang.ClassNotFoundException: com.sun.enterprise.management.agent._MEJB_Stub]|#]
[#|2004-11-15T03:26:53.359+0530|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|appId=MEjbApp moduleName=mejb_jar ejbName=MEJBBean|#]
[#|2004-11-15T03:26:53.359+0530|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5004: UnExpected error occured while creating ejb container
java.lang.RuntimeException: java.lang.ClassNotFoundException: com.sun.enterprise.management.agent._MEJB_Stub
     at com.sun.enterprise.iiop.POARemoteReferenceFactory.<init>(POARemoteReferenceFactory.java:150)
     at com.sun.enterprise.iiop.POAProtocolMgr.getRemoteReferenceFactory(POAProtocolMgr.java:117)
     at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:290)
     at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:135)
     at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:191)
     at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:477)
     at com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:125)
     at com.sun.enterprise.server.TomcatApplicationLoader.load(TomcatApplicationLoader.java:96)
     at com.sun.enterprise.server.AbstractManager.loadSystem(AbstractManager.java:265)
     at com.sun.enterprise.server.SystemAppLifecycle.loadSystemApps(SystemAppLifecycle.java:133)
     at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:74)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     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 org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.ClassNotFoundException: com.sun.enterprise.management.agent._MEJB_Stub
     at com.sun.enterprise.loader.EJBClassLoader.findClass(EJBClassLoader.java:505)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
     at com.sun.enterprise.iiop.POARemoteReferenceFactory.<init>(POARemoteReferenceFactory.java:132)
     ... 18 more
|#]
[#|2004-11-15T03:26:53.359+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5021: Application NOT loaded: [MEjbApp]|#]
------------------------------------------------------SNIP--------------------------------------------------------------------
The server starts up properly otherwise , i.e. , I came to see the problem only with
a "--verbose" flag to "asadmin".There is no problem with the server startup, and I even
tested the "Hello" app in quickstart folder successfully.I have not yet deployed any ejb sample.
I have tried all that I could think of(ENV_VARIABLES,PATH,CLASSPATH etc.)
I would appreciate it if someone can help me out on this.

I tried uninstalling the app server and J2SE-1.4.2,and reinstalled the server with 1.4.2_04,again.
Strangely enough it worked!
Here is the log:
---------------------------------------server.log----------------------------------------------------------
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2004-11-16T13:42:54.703+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2004-11-16T13:42:56.437+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-11-16T13:42:56.812+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-11-16T13:42:59.687+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-11-16T13:42:59.703+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-11-16T13:42:59.734+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-11-16T13:43:06.468+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-11-16T13:43:08.609+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-11-16T13:43:09.031+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-11-16T13:43:10.203+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-11-16T13:43:10.265+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2004-11-16T13:43:10.265+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-11-16T13:43:10.265+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2004-11-16T13:43:12.078+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2004-11-16T13:43:12.093+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2004-11-16T13:43:12.125+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Compiling RMI-IIOP code ...|#]
[#|2004-11-16T13:43:23.093+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2004-11-16T13:43:23.125+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.out|_ThreadID=10;| role is admin-role class class java.lang.String|#]
[#|2004-11-16T13:43:23.250+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.out|_ThreadID=10;|
role is admin-role class class java.lang.String|#]
[#|2004-11-16T13:43:23.593+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 12859 msec, Total EJB Compiler Module Time: 11015 msec, Portion spent EJB Compiling: 85%
Breakdown of EJBC Module Time: Total Time for EJBC: 11015 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 10968 msec (99%), JAX-RPC Generation: 16 msec (0%),
|#]
[#|2004-11-16T13:43:23.625+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
[#|2004-11-16T13:43:23.734+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2004-11-16T13:43:24.750+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-11-16T13:43:24.765+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-11-16T13:43:24.781+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2004-11-16T13:43:24.781+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-11-16T13:43:25.484+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-11-16T13:43:30.281+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2004-11-16T13:43:30.281+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2004-11-16T13:43:30.453+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5594 msec, Total EJB Compiler Module Time: 4797 msec, Portion spent EJB Compiling: 85%
Breakdown of EJBC Module Time: Total Time for EJBC: 4797 msec, CMP Generation: 1563 msec (32%), Java Compilation: 3125 msec (65%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2004-11-16T13:43:30.453+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
[#|2004-11-16T13:43:30.515+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2004-11-16T13:43:31.203+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-11-16T13:43:31.203+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-11-16T13:43:31.203+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-11-16T13:43:31.218+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-11-16T13:43:31.234+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-11-16T13:43:31.515+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-11-16T13:43:31.781+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-11-16T13:43:31.781+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-11-16T13:43:31.812+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-11-16T13:43:31.843+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-11-16T13:43:31.843+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-11-16T13:43:32.000+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-11-16T13:43:37.796+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-11-16T13:43:40.828+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-11-16T13:43:40.890+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-11-16T13:43:41.140+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-11-16T13:43:41.156+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-11-16T13:43:41.234+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-11-16T13:43:41.250+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-11-16T13:43:41.562+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer\imq\bin].|#]
[#|2004-11-16T13:43:41.578+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1100592821578|#]
[#|2004-11-16T13:43:41.578+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-11-16T13:43:41.578+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-11-16T13:47:06.859+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|sending notification to server...server|#]
[#|2004-11-16T13:47:06.921+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=11;|WEB0303: Stopping Tomcat.|#]
[#|2004-11-16T13:47:06.921+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=11;|Stoping http11 protocol on 8080 server:type=ThreadPool,name=http8080|#]
[#|2004-11-16T13:47:06.984+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=11;|Stoping http11 protocol on 1043 server:type=ThreadPool,name=http1043|#]
[#|2004-11-16T13:47:07.015+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=11;|Stoping http11 protocol on 4848 server:type=ThreadPool,name=http4848|#]
[#|2004-11-16T13:47:07.203+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=11;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2004-11-16T13:47:07.234+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=11;|EJB5122:EJB Timer Service shutdown at [2004/11/16 13:47:07]|#]
[#|2004-11-16T13:47:07.234+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=11;|CORE5052: Application shutdown complete.|#]
[#|2004-11-16T13:47:07.250+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Disabling AutoDeployment service.|#]
[#|2004-11-16T13:47:07.250+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=11;|JMS5025: JMS service shutting down.|#]
[#|2004-11-16T13:47:07.656+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=11;|JMS5026: JMS service shutdown complete.|#]
[#|2004-11-16T13:47:08.328+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown complete.|#]
[#|2004-11-16T13:53:39.500+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2004-11-16T13:53:41.984+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-11-16T13:53:42.359+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-11-16T13:53:48.312+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-11-16T13:53:48.328+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-11-16T13:53:48.453+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-11-16T13:53:54.203+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-11-16T13:53:56.968+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-11-16T13:53:57.406+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-11-16T13:53:59.000+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-11-16T13:54:00.734+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-11-16T13:54:02.031+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-11-16T13:54:02.031+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-11-16T13:54:02.265+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-11-16T13:54:02.718+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-11-16T13:54:03.015+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-11-16T13:54:03.031+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-11-16T13:54:03.031+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-11-16T13:54:03.046+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-11-16T13:54:03.062+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-11-16T13:54:03.250+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-11-16T13:54:09.234+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-11-16T13:54:12.140+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-11-16T13:54:12.203+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-11-16T13:54:12.375+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-11-16T13:54:12.390+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-11-16T13:54:12.453+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-11-16T13:54:12.468+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-11-16T13:54:13.265+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer\imq\bin].|#]
[#|2004-11-16T13:54:13.281+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1100593453281|#]
[#|2004-11-16T13:54:13.281+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-11-16T13:54:13.281+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-11-16T13:54:44.234+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|sending notification to server...server|#]
[#|2004-11-16T13:54:44.296+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=11;|WEB0303: Stopping Tomcat.|#]
[#|2004-11-16T13:54:44.296+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=11;|Stoping http11 protocol on 8080 server:type=ThreadPool,name=http8080|#]
[#|2004-11-16T13:54:44.328+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=11;|Stoping http11 protocol on 1043 server:type=ThreadPool,name=http1043|#]
[#|2004-11-16T13:54:44.359+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=11;|Stoping http11 protocol on 4848 server:type=ThreadPool,name=http4848|#]
[#|2004-11-16T13:54:44.546+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=11;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2004-11-16T13:54:44.546+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=11;|EJB5122:EJB Timer Service shutdown at [2004/11/16 13:54:44]|#]
[#|2004-11-16T13:54:44.546+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=11;|CORE5052: Application shutdown complete.|#]
[#|2004-11-16T13:54:44.562+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Disabling AutoDeployment service.|#]
[#|2004-11-16T13:54:44.562+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=11;|JMS5025: JMS service shutting down.|#]
[#|2004-11-16T13:54:45.812+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=11;|JMS5026: JMS service shutdown complete.|#]
[#|2004-11-16T13:54:46.453+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown complete.|#]
---------------------------------------------server.log------------------------------------------------------------------
Interesting thing is,when I had tried reinstalling it with 1.4.2_04 earlier,the log was not clean.
The problem is still not clear.Anyway , it is working fine for now.
Thanks.

Unable to call Container Managed Entity Bean

Hi
I am developing a JMS application using NetBeans 5.5.1 and Sun Java Application Server 9.0 and J2EE 1.4.When I run the application client it throws me following EXCEPTION:
{color:#ff0000}Sep 9, 2010 1:43:43 PM com.sun.enterprise.appclient.MainWithModuleSupport <init>
WARNING: ACC003: Application threw an exception.
javax.naming.NameNotFoundException: No object bound to name java:comp/env/jms/MDBDestinationFactory
at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:751)
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:156)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:307)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at jmsdemo.Main.main(Main.java:30)
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:597)
at com.sun.enterprise.util.Utility.invokeApplicationMain(Utility.java:232)
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:329)
at com.sun.enterprise.appclient.Main.main(Main.java:180)
Exception in thread "main" java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:340)
at com.sun.enterprise.appclient.Main.main(Main.java:180)
Caused by: java.lang.reflect.InvocationTargetException
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:597)
at com.sun.enterprise.util.Utility.invokeApplicationMain(Utility.java:232)
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:329)
... 1 more
Caused by: javax.naming.NameNotFoundException: No object bound to name java:comp/env/jms/MDBDestinationFactory
at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:751)
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:156)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:307)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at jmsdemo.Main.main(Main.java:30)
... 7 more
{color}{color:#000000}Source Code for Message Driven Bean:
package jmsdemo;
import javax.ejb.*;*
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
*public class MDBBean implements MessageDrivenBean, MessageListener {*
private MessageDrivenContext context;
*public void setMessageDrivenContext(MessageDrivenContext aContext) {context = aContext;}*
public void ejbCreate() {}
public void ejbRemove() {}
*public void onMessage(Message aMessage) {*
if(aMessage instanceof TextMessage)
TextMessage t = (TextMessage)aMessage;
try
System.out.println("Received message : " + t.getText());
*}catch(Exception e) {e.printStackTrace();}*
Source code for JMS Client:
package jmsdemo;*
import javax.jms.;
import javax.naming.*;*
*public class Main {*
*public Main() {*
public static void main(String[] args) throws Exception
*// TODO code application logic here*
InitialContext ic = new InitialContext();
ConnectionFactory cf = (ConnectionFactory)ic.lookup("java:comp/env/jms/MDBDestinationFactory");
Destination dest = (Queue) ic.lookup("java:comp/env/jms/MDBBean");
Connection con = cf.createConnection();
Session session = con.createSession(false,Session.AUTO_ACKNOWLEDGE);
MessageProducer mp = session.createProducer(dest);
TextMessage tm = session.createTextMessage();
tm.setText("Hello world .,.");
System.out.println("Sending message ...");
mp.send(tm);
con.close();
Generating code for ejb-jar.xml
<?xmlversion="1.0"encoding="UTF-8"?>*
*<ejb-jarversion="2.1"xmlns="[http://java.sun.com/xml/ns/j2ee%22xmlns:xsi=%22http://www.w3.org/2001/XMLSchema-instance%22xsi:schemaLocation=%22http://java.sun.com/xml/ns/j2eehttp://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd]">*
*<display-name>JMSDemo-ejb</display-name>*
*<enterprise-beans>*
*<message-driven>*
*<display-name>MDBMDB</display-name>*
*<ejb-name>MDBBean</ejb-name>*
*<ejb-class>jmsdemo.MDBBean</ejb-class>*
*<transaction-type>Container</transaction-type>*
*<message-destination-type>javax.jms.Queue</message-destination-type>*
*<message-destination-link>MDBDestination</message-destination-link>*
*<activation-config>*
*<activation-config-property>*
*<activation-config-property-name>acknowledgeMode</activation-config-property-name>*
*<activation-config-property-value>Auto-acknowledge</activation-config-property-value>*
*</activation-config-property>*
*<activation-config-property>*
*<activation-config-property-name>destinationType</activation-config-property-name>*
*<activation-config-property-value>javax.jms.Queue</activation-config-property-value>*
*</activation-config-property>*
*</activation-config>*
*</message-driven>*
*</enterprise-beans>*
*<assembly-descriptor>*
*<container-transaction>*
*<method>*
*<ejb-name>MDBBean</ejb-name>*
*<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<message-destination>
<display-name>DestinationforMDB</display-name>
<message-destination-name>MDBDestination</message-destination-name>
</message-destination>
</assembly-descriptor>
</ejb-jar>
Please let me when I am going wrong.
Thanks in advance
Senthil{color}

Hi
I am using sun java application server 9.0 and netbeans 5.5.1. For your information the Netbeans 5.5.1 has created already Queue in the sun java application server 9.0 when I created Message driven bean and I am able to see the queue connection in the Sun application server admin console. Even then I getting the same exception displayed below:
{color:#ff0000}Sep 11, 2010 11:45:17 AM com.sun.enterprise.appclient.MainWithModuleSupport <init>
WARNING: ACC003: Application threw an exception.
javax.naming.NameNotFoundException: No object bound to name java:comp/env/jms/MDBDestinationFactory
at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:751)
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:156)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:307)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at jmsdemo.Main.main(Main.java:30)
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:597)
at com.sun.enterprise.util.Utility.invokeApplicationMain(Utility.java:232)
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:329)
at com.sun.enterprise.appclient.Main.main(Main.java:180)
Exception in thread "main" java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:340)
at com.sun.enterprise.appclient.Main.main(Main.java:180)
Caused by: java.lang.reflect.InvocationTargetException
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:597)
at com.sun.enterprise.util.Utility.invokeApplicationMain(Utility.java:232)
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:329)
... 1 more
Caused by: javax.naming.NameNotFoundException: No object bound to name java:comp/env/jms/MDBDestinationFactory
at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:751)
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:156)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:307)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at jmsdemo.Main.main(Main.java:30)
... 7 more
Java Result: 1
{color}
The following connection properties {color:#0000ff}*jmsCF-jms_MDBBean.sun-resource_*{color} file:
<?xml version="1.0" encoding="UTF-8"?>
<resources>
<connector-resource enabled="true" jndi-name="jms/MDBDestinationFactory" object-type="user" pool-name="jms/MDBDestinationFactory">
<description/>
</connector-resource>
<connector-connection-pool connection-definition-name="javax.jms.QueueConnectionFactory" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" max-pool-size="32" max-wait-time-in-millis="60000" name="jms/MDBDestinationFactory" pool-resize-quantity="2" resource-adapter-name="jmsra" steady-pool-size="8"/>
</resources>
The following connection properties {color:#0000ff}_jms-jms_MDBBean.sun-resource_{color} file:
<?xml version="1.0" encoding="UTF-8"?>
<resources>
<admin-object-resource enabled="true" jndi-name="jms/MDBBean" object-type="user" res-adapter="jmsra" res-type="javax.jms.Queue">
<description/>
<property name="Name" value="MDBBean"/>
</admin-object-resource>
</resources>
Please help.
Thanks in advance
Senthil

Exception [EJB - 10008]: Cannot find bean of type [SalesBean] using finder

I'm trying to call an entity bean froma session bean i get the error :-
7/02/27 14:35:25 javax.ejb.ObjectNotFoundException: Exception [EJB - 10008]: Cannot find bean of type [SalesBean] using finde
[findByCustID].
7/02/27 14:35:25       at oracle.toplink.internal.ejb.cmp.EJBExceptionFactory.objectNotFound(EJBExceptionFactory.java:325)
7/02/27 14:35:25       at oracle.toplink.internal.ejb.cmp.finders.Finder.checkNullResult(Finder.java:224)
My session bean looks like this :-
public class HelloBean implements SessionBean
public String helloWorld (String pzCustomerID) throws SQLException,RemoteException
     String lzRevenue=null;
     int liCustomerID=Integer.parseInt(pzCustomerID);
     try
          Context initial = new InitialContext();
          Object objref =   initial.lookup("SalesBean");
          SalesHome salesHome =(SalesHome) PortableRemoteObject.narrow(objref,SalesHome.class);
          Sales sales=salesHome.findByCustID(liCustomerID);
          lzRevenue=(String) sales.findByCustID(liCustomerID);
My entity bean looks like this:-
public class SalesBean implements EntityBean
public String factPK;
public int timeID;
public int custID;
public int locID;
public int itemID;
public int entityID;
public String currency;
public float qty;
public float unitPrice;
public float amount;
public EntityContext context;
private Connection con;
    private void makeConnection() {
        try {
            InitialContext ic = new InitialContext();
            javax.sql.DataSource ds = (javax.sql.DataSource) ic.lookup("jdbc/DSource");
            con = ds.getConnection();
        } catch (Exception ex) {
            throw new EJBException("Unable to connect to database. " +
                ex.getMessage());
public SalesBean()
public String ejbFindByCustID(int custID) throws SQLException,RemoteException,FinderException
     makeConnection();
     PreparedStatement pstmt = con.prepareStatement("select sum(amount) from sales where cust_id= ? ");
     pstmt.setInt(1, custID);
     ResultSet rset = pstmt.executeQuery();
     if (!rset.next())
          throw new RemoteException("no records present" );
     return rset.getString(1);
}My entity bean's home interface looks like this:-
public interface SalesHome extends EJBHome
public Sales create() throws RemoteException, CreateException;
public Sales findByCustID(int custID) throws SQLException,RemoteException,FinderException;
My entity bean's remote interface looks like this:-
public interface Sales extends EJBObject
     public String findByCustID(int custID) throws SQLException,RemoteException,FinderException;
my ejb-jar.xml looks like this:-
<enterprise-beans>
<session>
<description>Hello Bean</description>
<ejb-name>HelloBean</ejb-name>
<home>myEjb.HelloHome</home>
<remote>myEjb.HelloRemote</remote>
<ejb-class>myEjb.HelloBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
     <entity>
          <ejb-name>SalesBean</ejb-name>
          <home>myEjb.SalesHome</home>
          <remote>myEjb.Sales</remote>
          <ejb-class>myEjb.SalesBean</ejb-class>
          <persistence-type>Container</persistence-type>
          <prim-key-class>java.lang.String</prim-key-class>
          <reentrant>False</reentrant>
          <cmp-field>
          <field-name>factPK</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>timeID</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>custID</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>locID</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>itemID</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>entityID</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>currency</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>qty</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>unitPrice</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>amount</field-name>
     </cmp-field>
          <primkey-field>factPK</primkey-field>
          <resource-ref>
          <res-ref-name>jdbc/DSource</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
     </resource-ref>
     </entity>
</enterprise-beans>
please help me out of this trouble.

I'm trying to call an entity bean froma session bean i get the error :-
7/02/27 14:35:25 javax.ejb.ObjectNotFoundException: Exception [EJB - 10008]: Cannot find bean of type [SalesBean] using finde
[findByCustID].
7/02/27 14:35:25       at oracle.toplink.internal.ejb.cmp.EJBExceptionFactory.objectNotFound(EJBExceptionFactory.java:325)
7/02/27 14:35:25       at oracle.toplink.internal.ejb.cmp.finders.Finder.checkNullResult(Finder.java:224)
My session bean looks like this :-
public class HelloBean implements SessionBean
public String helloWorld (String pzCustomerID) throws SQLException,RemoteException
     String lzRevenue=null;
     int liCustomerID=Integer.parseInt(pzCustomerID);
     try
          Context initial = new InitialContext();
          Object objref =   initial.lookup("SalesBean");
          SalesHome salesHome =(SalesHome) PortableRemoteObject.narrow(objref,SalesHome.class);
          Sales sales=salesHome.findByCustID(liCustomerID);
          lzRevenue=(String) sales.findByCustID(liCustomerID);
My entity bean looks like this:-
public class SalesBean implements EntityBean
public String factPK;
public int timeID;
public int custID;
public int locID;
public int itemID;
public int entityID;
public String currency;
public float qty;
public float unitPrice;
public float amount;
public EntityContext context;
private Connection con;
    private void makeConnection() {
        try {
            InitialContext ic = new InitialContext();
            javax.sql.DataSource ds = (javax.sql.DataSource) ic.lookup("jdbc/DSource");
            con = ds.getConnection();
        } catch (Exception ex) {
            throw new EJBException("Unable to connect to database. " +
                ex.getMessage());
public SalesBean()
public String ejbFindByCustID(int custID) throws SQLException,RemoteException,FinderException
     makeConnection();
     PreparedStatement pstmt = con.prepareStatement("select sum(amount) from sales where cust_id= ? ");
     pstmt.setInt(1, custID);
     ResultSet rset = pstmt.executeQuery();
     if (!rset.next())
          throw new RemoteException("no records present" );
     return rset.getString(1);
}My entity bean's home interface looks like this:-
public interface SalesHome extends EJBHome
public Sales create() throws RemoteException, CreateException;
public Sales findByCustID(int custID) throws SQLException,RemoteException,FinderException;
My entity bean's remote interface looks like this:-
public interface Sales extends EJBObject
     public String findByCustID(int custID) throws SQLException,RemoteException,FinderException;
my ejb-jar.xml looks like this:-
<enterprise-beans>
<session>
<description>Hello Bean</description>
<ejb-name>HelloBean</ejb-name>
<home>myEjb.HelloHome</home>
<remote>myEjb.HelloRemote</remote>
<ejb-class>myEjb.HelloBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
     <entity>
          <ejb-name>SalesBean</ejb-name>
          <home>myEjb.SalesHome</home>
          <remote>myEjb.Sales</remote>
          <ejb-class>myEjb.SalesBean</ejb-class>
          <persistence-type>Container</persistence-type>
          <prim-key-class>java.lang.String</prim-key-class>
          <reentrant>False</reentrant>
          <cmp-field>
          <field-name>factPK</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>timeID</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>custID</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>locID</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>itemID</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>entityID</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>currency</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>qty</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>unitPrice</field-name>
     </cmp-field>
     <cmp-field>
          <field-name>amount</field-name>
     </cmp-field>
          <primkey-field>factPK</primkey-field>
          <resource-ref>
          <res-ref-name>jdbc/DSource</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
     </resource-ref>
     </entity>
</enterprise-beans>
please help me out of this trouble.

EJB 3.0 entity beans and WebDynpro models

Hi all,
first off all my setup:
WebDynpro Development Component: dcA
EJB Module Development Component: dcB
i wan't to create Entity Beans in dcB an use it for my model in dcA.
My questions:
1. Why does the "New Wizard" only offer EJB 3.0 Session and Message Beans an no Entity Beans? What is the correct way for creating Entity Beans in DevStudio?
2. Is ist right that i have to define a public Part containing the Entity Bean to make it visible to dcA?
Regards,
Christian

Hi,
I'm experiencing same problems, is this a bug or an feature?

How to lookup a EJB 3.0 session bean which is deployed in WebLogic 10.3

Now Jdeveloper 11.1.1, is giving WebLogic server 10.3.
With internal WebLogic server, when I created a Sample client, it generated code as:
private static Context getInitialContext() throws NamingException {
    Hashtable env = new Hashtable();
    // WebLogic Server 10.x connection details
    env.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory" );
    env.put(Context.PROVIDER_URL, "t3://127.0.0.1:7101");
    return new InitialContext( env );
public static void main(String [] args) {
    try {
        final Context context = getInitialContext();
        DefaultSession defaultSession = (DefaultSession)context.lookup("property-DefaultSession#com.vs.property.model.session.DefaultSession");
    } catch (Exception ex) {
}How to update the above code to lookup the EJB 3.0 session beans with an external WebLogic server 10.3?
Is there any documentation available on how to install weblogic, troubleshoot, debug, WebLogic server 10.3?
regds
-raju

Raju,
Hi, to start, here is a tutorial on a quickstart web application using an EJB 3.0 stateless session bean that fronts a container managed EclipseLink JPA entity manager on WebLogic 10.3, you will find references there to other general WebLogic documentation.
[http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial]
using @EJB injection on the client instead of a JNDI lookup as below
[http://edocs.bea.com/wls/docs103/ejb30/annotations.html#wp1417411]
1) in your second env.put I noticed that your t3 port is 7101, I usually use the default 7001 - but It looks like this port is valid for the JDeveloper embedded version of WebLogic server runs - just verify that it matches the port of your server.
2) your name#qualified-name lookup looks ok. Verify that the jndi-name element is set in your weblogic-ejb-jar.xml for non injection clients like the following
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>ApplicationService</ejb-name>
<jndi-name>ApplicationService</jndi-name>
3) as a test outside of your application - launch the WebLogic admin console and goto the testing tab of your bean in [Home > Summary of Deployments > "application" > "session bean name"
thank you
/michael : http://www.eclipselink.org

Deploying EJB 3.0 entity beans without a Datasource

[Cross-posted from the TopLink list]
My question: Is there any way to configure the container or persistence provider to defer trying to connect to the Datasource until I make some call that involves persistence? Or any other way to deploy an app containing entity beans without having a database configured?
Background: I am working on a component that can be configured to run in either persistent or in-memory mode. For the persistent mode we would like to use EJB 3.0 entity beans; for the in-memory mode we would like the component to be deployable without having to have a database available.
However in my prototype of the application, when I try to deploy to OC4J 10.1.3, as soon as the entity beans are detected the TopLink persistence provider tries to establish a connection to the db via either the configured or default DataSource. So if the db is unavailable, deployment fails. Since this is occuring at deployment, it happens regardless of whether I am actually using any persistence features or not.

Hi,
I'm experiencing same problems, is this a bug or an feature?

Multiple inheritance in remote interfaces for EJB 3.0 session beans on Webl

Hi All,
We started migration from EJB 2.1(WLS 8.1) to EJB 3.0(WLS 10.3.2) and identified few serious problems. One of them is related with multiple business interfaces inheritance. I wrote simple example that presents point of the problem.
we have session bean AImpl:
+@Stateless(name="A")+
+@Remote({A.class})+
+@TransactionAttribute(TransactionAttributeType.REQUIRED)+
+public class AImpl implements A {+
+@Override+
+public void writeA() {+
System.out.println("A");
+}+
+@Override+
+public void writeB() {+
System.out.println("B");
+}+
+@Override+
+public void writeC() {+
System.out.println("C");
+}+
+}+
with remote interface A:
+@Remote+
+@JNDIName(A.JNDI_NAME)+
+public interface A extends B, C {+
public static String JNDI_NAME = "A_JNDI_NAME";
void writeA();
+}+
As you can see A extends B, and C. Definition of both interfaces is very simple:
+public interface B {+
void writeB();
+}+
+public interface C {+
void writeC();
+}+
Everything looks nice until we want to invoke some method on AImpl bean. For above implementation code:
A a = ctx.lookup(A. JNDI_NAME);
a.writeA();
a.writeB();
a.writeC();
writes down ”A \n B” and throws exception:
caused by: java.lang.NoSuchMethodException: pl.gov.arimr.zszik.bazowe.slowniki.ejb.A_vt0zts_AImpl_1032_WLStub.*writeC()*
at java.lang.Class.getMethod(Class.java:1605)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.getTargetMethod(RemoteBusinessIntfProxy.java:165)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:57)
so.. in stub generated by WLS there is no method from interface C ! What more interesting after small change in interface A rely on change in interface implementation order from B, C to C, B (+public interface A extends C, B {+) server writes down only A and I have stack like below:
Caused by: java.lang.NoSuchMethodException: pl.gov.arimr.zszik.bazowe.slowniki.ejb.A_vt0zts_AImpl_1032_WLStub.*writeB()*
at java.lang.Class.getMethod(Class.java:1605)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.getTargetMethod(RemoteBusinessIntfProxy.java:165)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:57)
After this experience I came up with suspicion that Weblogic 10.3 does not support inheritance from multiple interfaces in one “generation”. Instead of that it takes only the first interface from the list.
Does anybody have some experience with such a situation? maybe someone have an idea how to work around this problem?

This is Not Supported in WebLogic that the Remote Interface extends other Interfaces. Because Annotation Processor just looks up inside the implemented interface methods. The actual interface which is Implemented by the Bean Class. So the Methods declared inside the Interface B and Interface C will be ignored and will not be available as part of the generated Stubs. Thats why u are getting NoSuchMethodError.
You can even contact Oracle Support on this...there are 3-4 Cases on it. And the Solution is Work As Designed.
Workaround is : edit your interface A as following
Declare all the Business Methods only in the Remote Interface and not inside it's Super Interfaces.
Example:
@Stateless(name="A")
@Remote({A.class})
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public class AImpl implements A {
@Override
public void writeA() {
System.out.println("A");
@Override
public void writeB() {
System.out.println("B");
@Override
public void writeC() {
System.out.println("C");
@Remote
@JNDIName(A.JNDI_NAME)
public interface A extends B, C {
public static String JNDI_NAME = "A_JNDI_NAME";
void writeA();
void writeB();
void writeC();
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

How am I able to use an injected EJB in a Managed Bean Constructor?

JSF 1.2
EJB 3.0
Glassfish v1
Summary:
Managed bean injected EJB is null when referencing EJB var in constructor.
Details:
In my managed bean, I have a constructor that tries to reference an injected EJB, such as:
public class CustomerBean implements Serializable {
@EJB private CustomerSessionRemote customerSessionRemote;
public CustomerBean() {
List<CustomerRow> results = customerSessionRemote.getCustomerList();
}The call within the constructor to customerSessionRemote is null - I've double checked this in Netbeans 5.5.
How am I able to use an injected EJB in a Managed Bean Constructor?
Thanks,
--Todd

OK, I was reading the article Web Tier to Go With Java EE 5: A Look at Resource Injection and I understand your statement too.
Is there any way possible to Inject the EJB prior to the bean instance creation at all?
Maybe, I need to approach it with the old fashion Java EE 1.4 route and using JNDI in the PostConstruct annotated method to reference the EJB in the managed bean.
This had to been thought out before, I don't understand why a manged bean's life cycle places any injections at the end of the bean creation.
Also, now that I understand that the @PostConstruct annotated method will be called by the container after the bean has been constructed and before any business methods of the bean are executed.
I am trying to reference my EJB as part of the creation of the managed bean.
What happens: the JSF page loads the managed bean and I need to populate a listbox component with data from an EJB.
When I try to make the call to the EJB in the listbox setter method, the EJB reference is null.
Now, I'm not for sure if the @PostConstruct annotation is going to work... hmmmm.
** Figured it out. ** I just needed to move the EJB logic that was still in the setter of the component I wanted to populate into the annotated PostConstruct method.

Interop Survey: Which EJB Container is _known_ to work with which RDBMS?

Which EJB Container
have you personally used to successfully deploy entity beans
in combination with which RDBMS Server Product[s]
in a production environment supporting more than just a few users?
EJB Container
.VendorName =
.ProductName =
.ProductVersion =
.ProductLanguage =
.EJB-Spec-Version =
RDBMS Server 1
.VendorName =
.ProductName =
.ProductVersion =
.ProductLanguage =
Did you do multi database update ACID transactions that were managed by the EJB Container (ie CMP not BMP)?
YES
NO
If so, did you do them across more than one RDBMS Server Product, such as mixing DB2 with SQL Server?
YES
NO
RDBMS Server Product 2
.VendorName =
.ProductName =
.ProductVersion =
.ProductLanguage =
I intend to publish the results to this forum by 15 Aug 2005.
Please post any responses until 31 July 2005 so I can consider them in the survey.

Tomcat does not support EJB deployment as it is a mere servlet engine. But it can be integrated with with JBoss, an app server which is freely available.
-amit

Container Managed Entity Beans and Client Identifier in Oracle

Is it possible to use Container Managed Entity Beans (EJB with CMP)
in a way that the Oracle database sessions still know the
individual Client Identifiers of the actual users
(not just the Identifier of the proxy user defined in the
Connection Pool)?
If Yes: How?
If No: The consequence would be that the
technologies EJB with CMP cannot be user together with
Oracle Virtual Private Databases (VPN) because VPN requires
some kind of Client Identifier.
I am grateful for any hint.
Regards,
Martin Siepmann
+49 (0)163 / 7765328

Not quite an auto-incrementing PK, but it is managed by the container. the following is from the turorial
Generating Primary Key Values
For some entity beans, the value of a primary key has a meaning for the business entity. For example, in an entity bean that represents a phone call to a support center, the primary key might include a time stamp that indicates when the call was received. But for other beans, the key's value is arbitrary--provided that it's unique. With container-managed persistence, these key values can be generated automatically by the EJB container. To take advantage of this feature, an entity bean must meet these requirements:
* In the deployment descriptor, the primary key class is defined as a java.lang.Object. The primary key field is not specified.
* In the home interface, the argument of the findByPrimaryKey method must be a java.lang.Object.
* In the entity bean class, the return type of the ejbCreate method must be a java.lang.Object.
In these entity beans, the primary key values are in an internal field that only the EJB container can access. You cannot associate the primary key with a persistent field or any other instance variable. However, you can fetch the bean's primary key by invoking the getPrimaryKey method, and you can locate the bean by invoking its findByPrimaryKey method.
Maybe that is good enough
christina

Informing an ejb container of dirty beans

Similar Messages

Maybe you are looking for