Implementing a JNDI-SPI
I'm trying to write a JNDI-SPI for a SQL database but first have tried to get the SUN example implementation to work. It was fine in JDK 1.2.2 but I am getting the following error in JDK 1.3........
Exception in thread "main" java.lang.StackOverflowError
at com.sun.naming.internal.VersionHelper12$2.run(VersionHelper12.java:92)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.naming.internal.VersionHelper12.getJndiProperties(VersionHelper12.java:88)
at com.sun.naming.internal.ResourceManager.getInitialEnvironment(ResourceManager.java:131)
at javax.naming.InitialContext.init(InitialContext.java:218)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:83)
...........the error occurs if I call "super(env);" in the context constructr, I don't really know what I can do to stop this, any help would be most appreciated.
Thanks
Jon
Hi Addyj,
Did u get to solve this problem. Im getting a similar issue with JBoss 3.x.
If u have a solution, could u possibly mail me at [email protected]
Thanks
Ameesh
Similar Messages
-
Alright. I'm new using JNDI, but i get all the Context, Binding, lookup operations and rellated issues.
But, I need to connect to a server who has Tomcat using JNDI. (A high-school homework)
In a manner of fact, I need to create 2 subcontext an in the last one I need to bind a name with a reference to cmd.exe (it seems that I need to execute it), all of it using Tomcat's JNDI connection capabilities.
but when I'm trying to Construct the Initial Context reference, I'm not doing it in the right way... this is my Hashtable:
Hashtable env = new Hastable();
env.put(Context.INITIAL_CONTEXT_FACTORY, //I don't know what the hell goes hereApparentntly from web examples I have seen, It's the Implementation of the JNDI SPI from the Service Provider I want to connect... I really don't know which one to put when using Tomcat, or find other one.
I read in the HOW-TO section in the apache site, but find nothing...
or didn't get the idea, I saw they only get the container like this:
Context ct = new InitialContext();
with no arguments... but I also tryed to do it that way, but the same NamingException is thrown, with the message that I need to psecify the context factory. Well. I hope it's clear my trouble, and any of you would help me.
Not reporting anything else. Thanks.Hello,
have you check the following link
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-resources-howto.html
excerpts
Tomcat 5 provides a JNDI InitialContext implementation instance to web applications running under it, in a manner that is compatible with those provided by a Java2 Enterprise Edition application server. Entries in this InitialContext are configured in the $CATALINA_HOME/conf/server.xml file, and may be referenced by the following elements in the web application deployment descriptor (/WEB-INF/web.xml) of your web application:
used the resource file <resource-env-ref> , do not harcdode your jndi.properties
basic data source factory
<org.apache.commons.dbcp.BasicDataSourceFactory>
and bean factory
org.apache.naming.factory.BeanFactory
thaks -
Datasource without J2EE/JNDI - just J2SE
I'm writing a small program that work quite well with ResultSet but I would like to add pooling conections and a serialized RowSet, so I would like to replace DriverManager with DataSource.
But every thing in the doc's drive me to JDNI and J2EE and I don't want to.
I'm working with J2SE and my appa should be capable to run in very small machines (Pentium 200 MHz, 32MB, 6 GB).
I don't want to start an JDNI SPI (just like RMI, LDAP or anything else)
So, can be made javax.sql.Datasource to work without using JNDI?Absolutely.
Like yourself I write non-web/j2ee apps and would like to use the DataSource/ConnectionPoolDataSource interfaces.
All that a JNDI implementation does is to call a object factory (passing DataSource configuration details like driver,url,logid,password...) which instantiates a DataSource instance, configures it and passes it back to you. Now you can do all that in your code.
I use Sybases DataSource and am in the process of developing my own Connection pool using Jakarta Pool and the Sybase Pooling classes.
Heres what I have to do to create a DataSource instance:
DataSource ds = new SybDataSource();
ds.setServerName(machine);
ds.setDatabaseName(database);
ds.setUser(logid);
ds.setPassword(password);
ds.setPortNumber(Integer.parseInt(port));
return ds;
Connection c = ds.getConnection();I typically develop Tomcat apps and so to keep my coding techniques similar, I decided to retain JNDI for non-web apps. This involves writing a JNDI SPI, which is no big deal. The benefit is that I have the same configuration techniques (XML files) the same ServiceLocator pattern to get DataSources by name, and the same code in web or non-web apps.
Dave -
What's the difference between Netscape SDK for Java & JNDI?
I know I can use either JNDI or Netscape SDK to access iDS. So whats their differences basically?
Why would I need JNDI/Netscape SDK if I can just use either of them to access iDS?
Thanks!Netscape SDK for JAVA developed only for iplanet Directory Server but JNDI for any directory server.
JNDI has classes provided by Sun that will help your application interact with an LDAP server.JNDI applications work similarly to JDBC applications - write applications once and be free to use "drivers" from different vendors. Sun provides the "driver" that will help interact with the LDAP server. Sun also provides "drivers" for other naming services (like CORBA, Netscape).
The Java Naming and Directory Interface (JNDI) allows Java applications to use a single set of methods to access multiple naming and directory services such as LDAP and NIS.
JNDI is a Java API that provides a common way for programmers to access a variety of naming and directory services. The API consists of several packages:
javax.naming for naming operations (access entries)
javax.naming.directory for directory operations (access attributes)
javax.naming.event for requesting event notification
javax.naming.ldap for LDAP-specific features.
JNDI operates through a layer of software called a Service Provider. The Service Provider implements the JNDI operations in terms of a particular underlying protocol.
JNDI's Service Provider Interface (SPI) allows you to select Service Providers at runtime. In many cases you can use the same JNDI methods regardless of whether the Service Provider is talking to an LDAP server or using another protocol such as NIS. In order to access all of the functionality of the LDAP protocol, however, you will have to use methods outside of this abstraction. -
Proposal for global JNDI support in future Virgo releases
Hello,
when I first started using Virgo more than 2 years ago, I had trouble finding a convenient approach for establishing database connections using EclipseLink.
To cut a long story short, I eventually ended up implementing a fragment for the catalina bundle in order to register a custom InitialContextFactoryBuilder in the JNDI SPI that would be just a proxy over Tomcat JNDI support, so that I could use plain old InitialContext().lookup() in Virgo to lookup resources declared in tomcat-server.xml
I understand that this is not 100% OSGi aware, but the other two OSGi App Servers I know of, Apache Karaf and WebSphere Liberty, both provide an optional feature that enables the same behaviour, and IMHO this largely reduces the learning curve for new users.
So, I would like to ask the project team to evaluate the possibility to include a similar feature OOTB in Virgo 3.7.x.
If you are interested, I can share the code and I am also willing to help out in the implementation.
GianMaria.Hi,
This is bit difficult to answer.. however here is the EOS/EOL details for 1230 series..
http://www.cisco.com/en/US/prod/collateral/wireless/ps5678/ps6108/eol_c51-506614.html
Since we support this product till 2014, My strong feeling is that this will be stretched till what ever the software that comes till end 2012 or max early 2013.. i really dont know what will be the train that time though!!
lemme know if this answered your question..
Regards
Surendra
====
Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull -
LDAP or JNDI Synchronization Across JVMs?
I need to perform an atomic operation (get & set) in
LDAP that is synchronized between multiple
applications (i.e. across JVMs).
Is that possible using iDS 4.x or 5.x?
Does iDS implementation of JNDI/LDAP API provide a
global lock mechanism (I know that this feature is not
supported in the API)?
Here is my actual problem. I need to generate a unique
id of type "long". This id should be unique across
several Java applications. I would like to store this
id in LDAP.
Any help is appreciated.
Thanks, ShahriarThere is no such locking mechanism. Is there a reason the unique id has to be type long? If not, then how about using a UUID? If it needs to be long, perhaps apportioning the number space between applications would work for you.
-
Content MS - Architecture/Implementation
Hi
Can someone point me to a document which explanin the underlying architecture
of the CMS. Whethr it uses Ejbs/classes/is the Data cached for the Content Operation
(add/delete). I want to write my own interface for BEA Content Management (do
not want to use BulkLoader OR myContent/Portal App tool). I am planning to develop
my own server side classes using the Content API/classes but before that wanted
to undestand the underlying arch of the CMS.
Any help would be highly appreciated
Petepete, below is an example of how to create a content node, with a binary property.
it also includes creating the content type (objectclass), which i don't believe
you will need to do. hopefully this will help.
repositoryMgr.connect();
NodeOps nops = repositoryMgr.getNodeOps();
ObjectClassOps ocops = repositoryMgr.getObjectClassOps();
ID repId = new ID();
repId.setRepositoryName(repositoryName);
PropertyDefinition[] pds = new PropertyDefinition[1];
pds[0] = new PropertyDefinition(repId, "binaryType", null, Property.BINARY,
false, false, false, false, false, null);
ObjectClass oc = new ObjectClass(repId, "schema", null, pds);
oc = ocops.createObjectClass(oc);
Node newNode = nops.createHierarchyNode(repId, "A");
Property[] props = new Property[1];
BinaryValue bv = new BinaryValue(mimeType, fileName, size, inputStream);
props[0] = new Property("binaryType", new Value(bv));
Node updatedNode = nops.addNodeContent(newNode.getId(), oc.getId(),
props);
"pete" <[email protected]> wrote:
>
James
Thanx for your reply.
I have been trying to take a look at the myContent portlet code but to
be very
honest with you it is too cluttered for me and I could not follow the
jpf code
however hard I try.
It would be extremely helpful to me if you can provide some sample code
which
just connects to a repository and then does some Add/Update function
on the CMs
tables.
Thanks, Pete
"James Owen" <[email protected]> wrote:
Pete, ok, so you want to configure your own repository (using the Portal
CM Repository),
then from a jsp, call your own classes that call the cm api, which will
store/retrieve
the content in the Portal CM Repository.
In that case, you don't need to do anything with the SPI, you'll just
be using
the CM API.
Just to clarify, when you "create" your own repository (using the Portal
CM Repository),
it doesn't really create a Repository, it just configures it, more like
a jdbc
connection. So if you delete the BEA Repository and then create your
own, using
the same Repository class (shift plus / will fill it in for you) your
newly configured
repository will point to the same tables that the BEA Repository did,
so it is
more like a rename.
For api examples, I would suggest you take a look at the sample cm portlet
code
- not for best practices ;) - but it does give good examples of howto
use the
api to create content, search, etc. if it is doesn't address your specific
questions
then let me know.
James
"pete" <[email protected]> wrote:
James, Thanks for the answers, Your Question
sorry, i'm not following what you would like to do. if you are developing
your
own ui, then all you'll just need to use the API, if you would liketo
expose
your own repository to the Virtual Repository then you will need toimplement
the SPI. what exactly is your goal?My goal is to have a UI(JSP) which in turn will call some functionsin
a Server
Side class for CRUD operation on a new Repository(with my <Application
name> Repository
instead of BEA Repository) in BEA PORTAL DB. Currently I do not have
my Virtual
repository, I just will use the BEA's virual repository and either
rename
it to
<app>Repository OR will create a new repository in the BEA Portal DB.
Do you think
If I just write some functions in a server side class for Content Oprations
using
the API that should suffice OR I will have to implement SPI
Also it would be extremely helpful if you could provide me with some
sample code
for connecting to a repository in BEA PORTAL DB and some function like
adding/updating
content in the that repository. You have been very helpful so far,thanks
a bunch
"James Owen" <[email protected]> wrote:
"pete" <[email protected]> wrote:
James
Thanks for the diagram.
1. From this it becomes clear that the Content SPI is a combinationof
Entity
and Session beans and the property set is a Facade pattern, am I
correct
in my
understanding?
this is true of the BEA Content Repository, which implements the Content
SPI.
2. If the Content Database it implemented as a Entity Bean (probably
CMP) then
is it safe to assume that it is cached?Yes, it is CMP and yes, the beans are cached with the default setting
(1000).
You can up the settings by cracking open the descriptor in content_repo.jar.
3. what is the diff between BEA content SPI and Content SPI I am
planning
to develop
the server side classes for Adding/Updating/Deleting Content in BEACMS
(developing
my own methods using content API), do you think it is safe to do
it
this
way.sorry, i'm not following what you would like to do. if you are developing
your
own ui, then all you'll just need to use the API, if you would liketo
expose
your own repository to the Virtual Repository then you will need toimplement
the SPI. what exactly is your goal?
Pete
"James Owen" <[email protected]> wrote:
Pete,
here is a diagram showing the architecture. are you planning on
implementing
the
SPI? if so, i submitted a doc on dev2dev that describes the SPI.it
hasn't
been
posted yet, so i can send it to you separately.
James
"pete" <[email protected]> wrote:
Hi
Can someone point me to a document which explanin the underlying
architecture
of the CMS. Whethr it uses Ejbs/classes/is the Data cached for
the
Content
Operation
(add/delete). I want to write my own interface for BEA Content
Management
(do
not want to use BulkLoader OR myContent/Portal App tool). I amplanning
to develop
my own server side classes using the Content API/classes but beforethat
wanted
to undestand the underlying arch of the CMS.
Any help would be highly appreciated
Pete -
JNDI lookup for UserTransaction
Hi all,
in Weblogic, in a typical scenario, do a client provide exactly
one JNDI lookup for the UserTransaction object (interface) or do
the client have to provide a JNDI lookup for each transaction?
In some EJB implementations, a JNDI lookup for UserTransaction
returns always the same reference. For example, in JOnAS, you can
have one static reference which is set when the client starts.
Then, more threads can simultaneously use the same static
UserTransaction reference without any conflict, since the
implementation of UserTransaction recognizes, which thread invoked
a particular method.
In other words, can I make an assumption that two different JNDI
lookups for UserTransaction returns different references or not?
Thanks a lot,
Marek Prochazka
Distributed Systems Research Group
Department of Software Engineering
Charles University, Faculty of Mathematics and Physics
Malostranske namesti 25, 118 00 Prague 1, Czech Republic
phone: +420-2-2191 4236
http://nenya.ms.mff.cuni.cz/thegroup/
Actually, UserTransaction is a singleton and it's not a transaction. It's just
very mis-named.
It should be called UserTransactionManager or UserInterfaceToJTA.
The actual transaction is javax.transaction.Transaction.
-- Rob
Cameron Purdy wrote:
> Within a transaction, it is different instances? For example, if you call
> it two times one right after another?
>
> A transaction is a unit of work. I understand why the transaction object
> changes from transaction to transaction, since a single transaction object
> (UserTransaction) represents exactly one transaction. Why would it be a
> singleton? It is not a transaction manager.
>
> Peace,
>
> --
> Cameron Purdy
> Tangosol, Inc.
> http://www.tangosol.com
> +1.617.623.5782
> WebLogic Consulting Available
>
> "Sarita" <[email protected]> wrote in message
> news:[email protected]...
> >
> > Hi Priscilla--
> >
> > This is not the behavior that I'm seeing, and I'm perplexed.
> > Every time I request a UserTransaction from JNDI, I receive a
> > a different instance. Should the value immediately returned by JNDI be
> the singleton
> > instance? If not, then how do I retrieve the singleton instance?
> >
> > I would like a session bean to start a transaction, and then call a method
> on another
> > session bean (which should operate under the same transaction). How does
> the second
> > session bean grab the correct transaction object? Is that possible?
> >
> > Thanks In Advance,
> > Sarita
> >
> > "Priscilla Fung" <[email protected]> wrote:
> > >
> > >Hi Marek,
> > >
> > >In Weblogic 6.0, JNDI lookup of UserTransaction returns a reference to
> the
> > >singleton
> > >Transaction Manager instance, which is thread-safe and can be used from
> > >multiple
> > >threads for transaction demarcations etc.
> > >
> > >-- Priscilla Fung, BEA Systems, Inc.
> > >
> > >"Marek Prochazka" <[email protected]> wrote:
> > >>
> > >>Hi all,
> > >>
> > >>in Weblogic, in a typical scenario, do a client provide exactly
> > >>one JNDI lookup for the UserTransaction object (interface) or do
> > >>the client have to provide a JNDI lookup for each transaction?
> > >>
> > >>In some EJB implementations, a JNDI lookup for UserTransaction
> > >>returns always the same reference. For example, in JOnAS, you can
> > >>have one static reference which is set when the client starts.
> > >>Then, more threads can simultaneously use the same static
> > >>UserTransaction reference without any conflict, since the
> > >>implementation of UserTransaction recognizes, which thread invoked
> > >>a particular method.
> > >>
> > >>In other words, can I make an assumption that two different JNDI
> > >>lookups for UserTransaction returns different references or not?
> > >>
> > >>Thanks a lot,
> > >>Marek Prochazka
> > >>--------------------------------------------------------------
> > >> Distributed Systems Research Group
> > >> Department of Software Engineering
> > >> Charles University, Faculty of Mathematics and Physics
> > >> Malostranske namesti 25, 118 00 Prague 1, Czech Republic
> > >> phone: +420-2-2191 4236
> > >> http://nenya.ms.mff.cuni.cz/thegroup/
> > >>--------------------------------------------------------------
> > >>
> > >
> >
-
Hi, I've a cms portlet that does CRUD of content in it's own repository (maybe
Oracle DB)
I would like to integrate the the content as well as repository to the BEA portal
for personalization purposes.
Is there anyone who has done it before.
Can anyone provide me some details on how I can do this?Edmund, unfortunately i don't know of an example spi implementation to point you
to that is public. The article does discuss the interfaces you need to implement,
there are about 5 of them that reside in com.bea.content.spi. content_repo.jar
is the bea ootb implementation of the spi, but the spi interfaces reside in content.jar.
let me know if you run into specific issues/questions with your implementation.
James
"Fred Simone" <[email protected]> wrote:
>
Hi James,
I read through the article you emailed me, the article is still very
brief.
It does not mentioned what are implementation needed to be involved
what are the interface exactly required for implementation.
Is there a more detailed guide on how i can do this.
Btw, I noticed that there a content_repo.jar, is that what I need to
implement?
I would appreciate if there are any sample or detail guide that I can
continue
my
implementation for the BEA Portal 3rd Party CM Personal.
regards,
Edmund Leong
93897453
"James Owen" <[email protected]> wrote:
We recently submitted an article to dev2dev on the content spi, butit
hasn't been
posted yet. If you send me an email ([email protected]) requesting the article,
i'll
pass it along.
regards,
james
"Fred Simone" <[email protected]> wrote:
Hi, I've a cms portlet that does CRUD of content in it's own repository
(maybe
Oracle DB)
I would like to integrate the the content as well as repository to
the
BEA portal
for personalization purposes.
Is there anyone who has done it before.
Can anyone provide me some details on how I can do this? -
JBoss Can't find Oracle Driver
Hello, everyone,
I'm hoping someone can help me.
I've created a small web service. I have one method which returns something very straight forward, and it works fine.
I have then progressed this to try to return some data from an Oracle table.
However, when I try to do this, I get an error back saying that the Oracle Driver can not be found.
I am using JBoss, and am running this in Eclipse's Web Service Explorer.
The things I have tried to solve the issue are:
- Ensuring the Oracle driver is located in Windows>Preferences>General>Data Management>Connectivity>Driver Definitions
- Placing the Oracle driver jar in as many lib folders in my JBoss directory on my C drive as possible (I may have missed some out).
I am not sure what else to try. Please can someone help me or point me in the right direction?
Any help would be hugely appreciated.
Thank you very much in advance.
Robin
My stacktrace is as follows:
[code]
java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver from BaseClassLoader@1652e61{VFSClassLoaderPolicy@1c7eb33{name=vfsfile:/C:/Jboss/jboss-5.0.0.GA/server/default/conf/jboss-service.xml domain=ClassLoaderDomain@9fe84e{name=DefaultDomain parentPolicy=BEFORE parent=org.jboss.system.NoAnnotationURLClassLoader@a97b0b} roots=[MemoryContextHandler@2254409[path= context=vfsmemory://4shc4f-nlo6vf-hjk3qb83-1-hjk3qewj-6 real=vfsmemory://4shc4f-nlo6vf-hjk3qb83-1-hjk3qewj-6], DelegatingHandler@6903079[path=antlr.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/antlr.jar], DelegatingHandler@22387624[path=autonumber-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/autonumber-plugin.jar], DelegatingHandler@22963857[path=bcel.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/bcel.jar], DelegatingHandler@10479206[path=bsf.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/bsf.jar], DelegatingHandler@30371681[path=bsh.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/bsh.jar], DelegatingHandler@26839239[path=commons-collections.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/commons-collections.jar], DelegatingHandler@14875150[path=commons-httpclient.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/commons-httpclient.jar], DelegatingHandler@26137220[path=commons-logging.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/commons-logging.jar], DelegatingHandler@27193209[path=dtdparser121.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/dtdparser121.jar], DelegatingHandler@24916054[path=edb-jdbc14.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/edb-jdbc14.jar], DelegatingHandler@4824957[path=ejb3-persistence.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ejb3-persistence.jar], DelegatingHandler@25551189[path=el-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/el-api.jar], DelegatingHandler@9229531[path=hibernate-annotations.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hibernate-annotations.jar], DelegatingHandler@32148925[path=hibernate-commons-annotations.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hibernate-commons-annotations.jar], DelegatingHandler@33522601[path=hibernate-core.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hibernate-core.jar], DelegatingHandler@1899900[path=hibernate-entitymanager.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hibernate-entitymanager.jar], DelegatingHandler@21354482[path=hibernate-jmx.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hibernate-jmx.jar], DelegatingHandler@6588912[path=hibernate-validator.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hibernate-validator.jar], DelegatingHandler@10229202[path=hsqldb-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hsqldb-plugin.jar], DelegatingHandler@22852149[path=hsqldb.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hsqldb.jar], DelegatingHandler@12046052[path=ibatis-2.3.4.726.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ibatis-2.3.4.726.jar], DelegatingHandler@24115680[path=jaxen.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jaxen.jar], DelegatingHandler@8259012[path=jboss-bindingservice.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-bindingservice.jar], DelegatingHandler@28085047[path=jboss-common-jdbc-wrapper.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-common-jdbc-wrapper.jar], DelegatingHandler@15191255[path=jboss-current-invocation-aspects.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-current-invocation-aspects.jar], DelegatingHandler@3753755[path=jboss-ejb3-cache.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-cache.jar], DelegatingHandler@7028679[path=jboss-ejb3-common.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-common.jar], DelegatingHandler@19417347[path=jboss-ejb3-core.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-core.jar], DelegatingHandler@30502607[path=jboss-ejb3-deployers.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-deployers.jar], DelegatingHandler@12704779[path=jboss-ejb3-ext-api-impl.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-ext-api-impl.jar], DelegatingHandler@22379127[path=jboss-ejb3-ext-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-ext-api.jar], DelegatingHandler@14371981[path=jboss-ejb3-interceptors.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-interceptors.jar], DelegatingHandler@25089808[path=jboss-ejb3-metadata.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-metadata.jar], DelegatingHandler@5868125[path=jboss-ejb3-proxy-clustered.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-proxy-clustered.jar], DelegatingHandler@9114403[path=jboss-ejb3-proxy.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-proxy.jar], DelegatingHandler@9795777[path=jboss-ejb3-security.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-security.jar], DelegatingHandler@19590177[path=jboss-ejb3-transactions.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-transactions.jar], DelegatingHandler@16028187[path=jboss-ha-client.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ha-client.jar], DelegatingHandler@10766816[path=jboss-ha-server-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ha-server-api.jar], DelegatingHandler@32391332[path=jboss-ha-server-cache-jbc.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ha-server-cache-jbc.jar], DelegatingHandler@14017136[path=jboss-ha-server-cache-spi.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ha-server-cache-spi.jar], DelegatingHandler@345667[path=jboss-hibernate.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-hibernate.jar], DelegatingHandler@4725080[path=jboss-iiop.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-iiop.jar], DelegatingHandler@24635060[path=jboss-integration.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-integration.jar], DelegatingHandler@13327669[path=jboss-jaspi-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-jaspi-api.jar], DelegatingHandler@22302276[path=jboss-javaee.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-javaee.jar], DelegatingHandler@31347466[path=jboss-jca.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-jca.jar], DelegatingHandler@18733404[path=jboss-jmx-remoting.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-jmx-remoting.jar], DelegatingHandler@11086506[path=jboss-jpa-deployers.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-jpa-deployers.jar], DelegatingHandler@3152885[path=jboss-jsr77.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-jsr77.jar], DelegatingHandler@8104009[path=jboss-jsr88.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-jsr88.jar], DelegatingHandler@6656120[path=jboss-management.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-management.jar], DelegatingHandler@32490450[path=jboss-messaging-int.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-messaging-int.jar], DelegatingHandler@2167036[path=jboss-messaging.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-messaging.jar], DelegatingHandler@14820075[path=jboss-metadata.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-metadata.jar], DelegatingHandler@6467398[path=jboss-monitoring.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-monitoring.jar], DelegatingHandler@14768745[path=jboss-profileservice.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-profileservice.jar], DelegatingHandler@16166715[path=jboss-remoting-aspects.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-remoting-aspects.jar], DelegatingHandler@23747954[path=jboss-remoting.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-remoting.jar], DelegatingHandler@1902564[path=jboss-security-aspects.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-security-aspects.jar], DelegatingHandler@32586504[path=jboss-security-spi.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-security-spi.jar], DelegatingHandler@5935979[path=jboss-serialization.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-serialization.jar], DelegatingHandler@8687994[path=jboss-srp.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-srp.jar], DelegatingHandler@23794987[path=jboss-sunxacml.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-sunxacml.jar], DelegatingHandler@20627169[path=jboss-transaction-aspects.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-transaction-aspects.jar], DelegatingHandler@30003582[path=jboss-xacml.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-xacml.jar], DelegatingHandler@14199075[path=jboss.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss.jar], DelegatingHandler@4740342[path=jbossas-remoting.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossas-remoting.jar], DelegatingHandler@12716179[path=jbossha.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossha.jar], DelegatingHandler@12653911[path=jbossjta-integration.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossjta-integration.jar], DelegatingHandler@6300663[path=jbossjta.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossjta.jar], DelegatingHandler@31019059[path=jbosssx-server.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbosssx-server.jar], DelegatingHandler@2115134[path=jbosssx.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbosssx.jar], DelegatingHandler@14919969[path=jbossts-common.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossts-common.jar], DelegatingHandler@7651652[path=jbossws-common.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-common.jar], DelegatingHandler@20739678[path=jbossws-framework.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-framework.jar], DelegatingHandler@8331318[path=jbossws-native-jaxrpc.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-native-jaxrpc.jar], DelegatingHandler@1823783[path=jbossws-native-jaxws-ext.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-native-jaxws-ext.jar], DelegatingHandler@17125267[path=jbossws-native-jaxws.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-native-jaxws.jar], DelegatingHandler@28000914[path=jbossws-native-saaj.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-native-saaj.jar], DelegatingHandler@10464309[path=jbossws-spi.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-spi.jar], DelegatingHandler@14869110[path=jmx-adaptor-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jmx-adaptor-plugin.jar], DelegatingHandler@25281771[path=jnpserver.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jnpserver.jar], DelegatingHandler@10968735[path=joesnmp.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/joesnmp.jar], DelegatingHandler@3486913[path=jsp-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jsp-api.jar], DelegatingHandler@18513535[path=log4j-snmp-appender.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/log4j-snmp-appender.jar], DelegatingHandler@6749397[path=log4j.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/log4j.jar], DelegatingHandler@23142099[path=mail-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/mail-plugin.jar], DelegatingHandler@19847791[path=mail.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/mail.jar], DelegatingHandler@17226797[path=properties-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/properties-plugin.jar], DelegatingHandler@23150623[path=quartz.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/quartz.jar], DelegatingHandler@28882952[path=scheduler-plugin-example.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/scheduler-plugin-example.jar], DelegatingHandler@3816987[path=scheduler-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/scheduler-plugin.jar], DelegatingHandler@29594642[path=servlet-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/servlet-api.jar], DelegatingHandler@19811980[path=slf4j-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/slf4j-api.jar], DelegatingHandler@19335035[path=slf4j-jboss-logging.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/slf4j-jboss-logging.jar]] delegates=null exported=[, org.hibernate.loader.collection, org.jboss.deployers.spi.management.deploy, org.jboss.remoting.transporter, org.jboss.ejb3.proxy.clustered.objectfactory.session.stateful, com.arjuna.ats.txoj.semaphore, org.jboss.varia.property, com.arjuna.common.util.propertyservice, com.arjuna.common.util.logging, org.jboss.jms.server.messagecounter, org.jboss.ejb3.proxy.invocation, org.jboss.remoting.invocation, org.jboss.remoting.samples.transporter.proxy, javax.persistence, org.hibernate.engine.loading, org.jboss.security.xacml.sunxacml.combine, org.jboss.jms.client.remoting, com.arjuna.ats.internal.txoj.recovery, org.jboss.remoting.samples.transporter.serialization.server, javax.xml.registry.infomodel, org.jboss.resource.adapter.jdbc.remote, org.jboss.resource.spi.timer, org.jboss.ha.cachemanager, org.jboss.web.tomcat.service.session.distributedcache.spi, org.jboss.ejb3.timerservice, org.jboss.wsf.test, org.jboss.ejb3.cluster.metadata, org.jboss.metadata.annotation.creator.client, org.jboss.resource.statistic.formatter, com.arjuna.ats.internal.jta.transaction.arjunacore, org.jboss.ejb3.proxy.handler.stateless, com.edb.util, org.jboss.security.mapping.providers.principal, org.jboss.hibernate.deployers.metadata, org.jboss.wsf.common.management, org.jboss.resource.metadata, javax.enterprise.deploy.spi, com.ibatis.common.logging.log4j, org.apache.log4j.lf5, org.jboss.remoting.detection.jndi, org.jboss.security.integration, com.arjuna.common.internal.util.logging.simpleLog, org.jboss.jms.server.remoting, org.jboss.ejb3.metadata, org.hibernate.cache.access, META-INF.maven.org.jboss.cluster.jboss-ha-server-api, org.jboss.remoting.samples.transporter.basic, org.apache.bsf.util, org.jboss.ejb3.proxy.handler.session.service, org.hibernate.intercept.cglib, org.jboss.remoting.transport.sslrmi, org.hibernate.proxy, org.apache.bcel.verifier.exc, org.jboss.remoting.stream, org.apache.log4j.varia, org.hibernate.cache, org.jboss.jmx.adaptor.rmi, org.jboss.security.auth.container.config, org.jboss.ejb3.timerservice.jboss, org.hibernate.usertype, javax.security.auth.message.module, org.jboss.management.j2ee.statistics, org.jboss.remoting, org.jboss.serial.util, org.jboss.security.acl.config, com.ibatis.sqlmap.engine.mapping.sql.dynamic.elements, org.jboss.resource.adapter.jdbc.vendor, META-INF.maven.org.jboss.ws.native.jbossws-native-saaj, org.jboss.resource.adapter.jdbc, org.hibernate.ejb.event, org.jboss.metadata.validation.chain.ejb.jboss, com.arjuna.ats.jta.utils, javax.servlet, org.jboss.monitor.alerts, org.hibernate.annotations, org.jboss.jms.wireformat, com.arjuna.ats.internal.arjuna.objectstore.jdbc, antlr.debug.misc, org.jboss.security.xacml.jaxb, org.jboss.ejb3.deployers, com.edb.ds, org.hibernate.hql.ast.exec, com.ibatis.common.jdbc, org.jboss.metadata.process.processor, org.jboss.wsf.spi.util, org.hibernate.context, org.jboss.remoting.samples.detection.multicast, org.jboss.jmx.connector.invoker, javax.enterprise.deploy.model, org.jboss.web.tomcat.service.session.distributedcache.impl.jbc, xmdesc, org.jboss.ejb3.interceptors.container, org.jboss.ejb3.proxy.objectfactory.session, org.jboss.remoting.transport.web, org.hibernate.id.enhanced, javax.enterprise.deploy.shared, org.jboss.metadata.common.jboss, org.jboss.ejb3.enc, org.jboss.ejb3.proxy.factory, org.jboss.remoting.samples.callback.statistics, com.arjuna.ats.jta.xa, org.jboss.proxy.ejb.handle, org.jboss.ejb3.proxy.clustered.factory.session.stateful, org.jboss.metadata.serviceref, javax.mail.event, org.apache.bsf.engines.xslt, org.jaxen.pattern, org.jboss.ha.client.loadbalance, org.apache.log4j.lf5.viewer, org.jboss.ejb.plugins.cmp.jdbc, org.jboss.metadata.annotation.finder, org.jboss.jms.server.security, org.jboss.aspects.currentinvocation, org.jboss.wsf.framework.serviceref, org.jboss.web.tomcat.service.session.distributedcache.impl, org.jboss.ejb3.dependency, com.arjuna.ats.jbossatx.jta, org.jboss.iiop.jacorb, org.apache.bcel.generic, org.slf4j.helpers, org.quartz.plugins.xml, com.arjuna.ats.txoj.lockstore, com.edb.core.v2, org.jboss.ejb3.proxy.objectstore, com.sun.mail.handlers, com.ibatis.sqlmap.engine.transaction.user, org.jboss.remoting.serialization.impl.java, org.jboss.metadata.jpa.spec, com.edb.core.v3, org.hibernate.intercept.javassist, org.jboss.injection.lang.reflect, org.jboss.ejb3.protocol.jarjar, org.jboss.remoting.transport.servlet, com.arjuna.ats.internal.jta.xa, com.edb.fastpath, org.jboss.ha.client.loadbalance.aop, org.hibernate.stat, javax.xml.ws, org.jboss.invocation.iiop, com.arjuna.ats.tsmx.mbeans, com.ibatis.sqlmap.engine.impl, org.jboss.varia.autonumber, org.jboss.deployers.spi.management, org.quartz.simpl, com.edb.largeobject, org.jboss.security.plugins.acl, org.jboss.deployment.services, org.jboss.profileservice.management, org.quartz.jobs, javax.xml.rpc.handler.soap, org.hibernate.impl, com.arjuna.ats.internal.arjuna.gandiva.nameservice, org.hibernate.event.def, org.jboss.remoting.samples.multiplex, org.hibernate.persister, org.hibernate.ejb.transaction, org.hibernate.validator.resources, org.jboss.ejb3.proxy.clustered.handler.session.stateful, org.jboss.remoting.marshal.serializable, org.jboss.remoting.samples.transporter.complex.server, org.jboss.security.mapping.providers, org.jboss.wsf.framework.management.recording, org.jboss.messaging.core.impl.jchannelfactory, org.jnp.interfaces, org.jboss.verifier, javax.xml.rpc, org.apache.commons.httpclient.methods, org.opennms.protocols.snmp.asn1, org.jboss.ejb3.interceptors.currentinvocation, org.hibernate.tool.instrument.cglib, org.jboss.client, org.hibernate.annotations.common.reflection.java, bsh.util.lib, com.edb.translation, org.jboss.remoting.samples.transporter.multiple.client, org.jboss.ha.hasessionstate.server, org.jboss.security.xacml.interfaces, com.ibatis.sqlmap.engine.transaction.jdbc, org.jboss.iiop.test, org.quartz.core, org.jboss.ejb.plugins.cmp.jdbc2.schema, org.jboss.ejb3.interceptors.proxy, META-INF.maven.org.jboss.jpa.jboss-jpa-deployers, com.arjuna.ats.txoj.logging, com.arjuna.ats.internal.arjuna.template, org.jboss.metadata.ejb.spec, org.hibernate.type, com.arjuna.ats.arjuna.gandiva.inventory, javax.xml.ws.http, com.arjuna.ats.jbossatx.logging, org.jboss.verifier.strategy, org.apache.commons.httpclient.protocol, com.ibatis.sqlmap.engine.mapping.sql.raw, org.jboss.remoting.samples.transporter.custom.server, org.apache.bsf.util.event.adapters, org.apache.log4j.lf5.viewer.images, org.apache.commons.collections.set, org.hibernate.loader, org.jboss.jms.delegate, org.jboss.services.binding, org.hibernate.engine, org.quartz.spi, META-INF.maven.org.jboss.ws.jbossws-common, org.jboss.security.propertyeditor, org.jboss.ha.framework.server.util, META-INF.maven.org.jboss.security.jboss-sunxacml, org.jboss.mail, org.jboss.remoting.detection.util, org.jboss.ejb, org.jboss.wsf.spi.metadata.j2ee.serviceref, com.arjuna.ats.jdbc, org.jboss.ha.jndi.spi, org.hsqldb.jdbc, org.jboss.serial.objectmetamodel, com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.jca, META-INF.maven.org.hibernate.hibernate-core, javax.mail.util, org.apache.log4j.nt, org.jboss.security.srp, com.arjuna.ats.internal.txoj.semaphore, com.arjuna.common.internal.util.propertyservice.plugins.io, com.arjuna.ats.internal.jbossatx.jta.jca, org.jboss.security.xacml.locators, org.hibernate.tuple, org.jboss.remoting.transport.rmi, org.hibernate.annotations.common.reflection, org.jboss.web, bsh.reflect, org.hibernate.classic, org.hibernate.ejb.connection, org.jboss.security.xacml.util, org.jboss.security.ssl, org.jboss.ejb3.mdb, javax.transaction.xa, org.hsqldb, org.apache.bsf.engines.netrexx, com.arjuna.ats.jta.common, org.hibernate.jdbc.util, javax.security.auth.message.config, com.ibatis.sqlmap.engine.cache.oscache, com.wutka.dtd, org.jboss.jms.server.connectormanager, org.jboss.wsf.spi.transport, org.jboss.metadata.process.processor.ejb.jboss, org.omg.stub.javax.ejb, org.jboss.jpa.tx, org.hibernate.loader.entity, org.jboss.remoting.samples.oneway, org.jboss.messaging.core.impl.clusterconnection, org.jboss.wsf.spi.deployment, org.jboss.ejb3.interceptors.direct, antlr.collections.impl, org.apache.log4j.or, org.hibernate, javax.xml.rpc.soap, com.ibatis.sqlmap.engine.mapping.result, com.ibatis.common.logging.nologging, com.arjuna.ats.internal.tsmx.agent.exceptions, org.jboss.ha.jndi, org.hsqldb.sample, org.hibernate.bytecode.util, org.hsqldb.lib, com.arjuna.ats.txoj.exceptions, org.jboss.ejb3.metamodel, org.apache.log4j.or.jms, javax.management.remote.rmi, META-INF.maven.org.jboss.ws.native.jbossws-native-jaxws-ext, javax.interceptor, org.jboss.wsf.spi.tools.ant, security, org.jboss.resource.timer, com.arjuna.ats.tsmx.agent.exceptions, org.jboss.ejb3.proxy.objectfactory.session.stateless, com.arjuna.ats.jta.transaction, org.jboss.ejb3.metadata.plugins.loader, org.jboss.deployment.vfs, com.arjuna.ats.internal.jta.recovery.arjunacore, org.jaxen, com.ibatis.sqlmap.engine.execution, com.ibatis.sqlmap.engine.cache.memory, com.arjuna.ats.jta.resources, org.jboss.wsf.common.logging, com.arjuna.ats.arjuna.utils, org.jboss.ejb3.aop, META-INF.maven.org.jboss.ejb3.jboss-ejb3-security, org.jboss.jms.client.delegate, bsh.commands, com.arjuna.ats.tsmx.agent, org.jboss.security.xacml.sunxacml.support, org.jboss.serial.finalcontainers, com.arjuna.ats.internal.txoj.lockstore, org.jboss.resource.security, org.jboss.messaging.core.impl.tx, org.jboss.resource.connectionmanager, javax.xml.ws.addressing.soap, org.quartz.impl.calendar, com.arjuna.ats.internal.jdbc.drivers, org.jboss.deployment.dependency, org.jboss.security.identity.fed, org.jboss.ejb3.kernel, com.edb.ds.common, META-INF.maven.org.jboss.ejb3.jboss-ejb3-proxy-clustered, org.jboss.wsf.framework, com.arjuna.ats.arjuna.coordinator, org.jboss.services.binding.impl, org.jboss.invocation, javax.servlet.http, com.arjuna.common.internal.util.licence.utils, org.jboss.metadata.validation, javax.jws, org.hibernate.bytecode, org.jboss.jms.exception, org.jboss.security.mapping, org.apache.log4j.spi, org.jboss.ejb3.interceptors.lang, com.arjuna.ats.arjuna.gandiva.nameservice, org.jboss.security.xacml.sunxacml.ctx, org.jboss.ejb3.naming, org.jboss.messaging.core.impl, org.jboss.jpa.resolvers, org.jboss.remoting.samples.transporter.clustered.server, org.hsqldb.util.sqltool, org.jboss.hibernate.deployers, org.jboss.ejb.plugins.local, org.jboss.monitor, org.jboss.remoting.samples.transporter.proxy.client, org.hibernate.cache.entry, org.quartz, org.hibernate.hql, org.jboss.security.auth.spi, com.arjuna.common.util, org.hibernate.transform, org.hibernate.tuple.component, org.jboss.ejb3.cache.persistence, org.jboss.invocation.pooled.server, org.jboss.security.identitytrust.modules, org.jboss.metadata.common.spi, com.arjuna.ats.internal.jta.utils, org.jboss.security.authorization.modules, org.jboss.verifier.event, org.jboss.iiop.rmi.marshal, org.jboss.ejb3.proxy.clustered.registry, org.apache.log4j.jdbc, com.arjuna.ats.internal.jta.resources.errorhandlers, org.jboss.ejb3.proxy.clustered.familyname, org.apache.bcel.util, org.jboss.annotation.javaee, org.jboss.ejb3.metadata.annotation, org.hibernate.sql, org.jboss.messaging.util, org.jboss.ejb.plugins.cmp.jdbc.metadata, com.arjuna.common.util.propertyservice.propertycontainer, org.jboss.invocation.http.server, org.hsqldb.persist, org.jboss.remoting.transport.sslsocket, com.arjuna.ats.arjuna.state, org.jboss.ejb3.interceptors.aop, org.hibernate.lob, org.jboss.ejb3.security.helpers, org.jboss.wsf.spi.management, org.jboss.remoting.detection.multicast, org.jboss.security.authorization.modules.web, antlr.build, org.hibernate.persister.entity, com.edb.stream, org.jboss.classloading.spi, org.jboss.metadata.rar.jboss, org.jboss.jpa.injection, org.apache.bsf.engines.jacl, org.jboss.mx.remoting.event, org.jboss.ejb3.proxy.jndiregistrar, META-INF.maven.org.jboss.ejb3.jboss-ejb3-ext-api, org.jboss.jca.spi, org.jboss.remoting.samples.bisocket, org.apache.log4j.lf5.viewer.configure, org.jboss.ejb3.common.registrar.spi, org.jboss.ejb3.security.embedded.plugins, org.jboss.crypto.digest, org.jboss.naming.java, org.jboss.security.xacml.sunxacml, org.jboss.remoting.samples.transporter.complex, META-INF.maven.org.jboss.ejb3.jboss-ejb3-ext-api-impl, com.arjuna.ats.arjuna.thread, org.apache.commons.collections.map, javax.xml.rpc.holders, org.jboss.jms.server.plugin.contract, org.jboss.ejb3.interceptors.registry, org.jboss.tm.usertx.client, com.arjuna.ats.txoj, org.hibernate.cfg.search, org.jboss.remoting.transport.bisocket, org.jboss.resource.binding.remote, org.jboss.wsf.framework.transport, org.jboss.ejb3.injection, com.arjuna.ats.txoj.common, org.jboss.wsf.spi.serviceref, com.ibatis.sqlmap.client.extensions, com.ibatis.sqlmap.engine.cache.fifo, javax.security.jacc, META-INF.maven.org.jboss.ws.native.jbossws-native-jaxrpc, org.jboss.wsf.common.utils, org.jboss.jms.server.bridge, com.arjuna.ats.internal.arjuna, javax.enterprise.deploy.spi.exceptions, org.quartz.xml, org.jboss.management.j2ee, org.jboss.deployment.spi.configurations, bsh.servlet, org.jboss.aspects.tx, org.apache.commons.collections.iterators, org.jboss.serial.io, com.ibatis.sqlmap.engine.accessplan, com.edb.core.charset, org.hibernate.cfg.annotations.reflection, org.hibernate.id, org.jboss.ejb3.proxy.handler.session, org.jboss.ejb3.common.thread, com.arjuna.common, org.jboss.jpa.util, org.jboss.deployment, javax.ejb.spi, bsh.collection, org.jboss.metamodel.descriptor, org.jboss.profileservice.management.upload, org.jboss.invocation.local, META-INF.maven.org.slf4j.slf4j-api, org.jaxen.function, META-INF.maven.org.jboss.cluster.jboss-ha-client, org.jboss.security.microcontainer.beans.metadata, com.arjuna.ats.arjuna.objectstore.jdbc, org.jboss.remoting.samples.multiplex.invoker, org.jaxen.javabean, org.jboss.ejb3.tx.container, org.jboss.lang.ref, org.hsqldb.resources, org.jboss.security.xacml.sunxacml.finder.impl, org.jboss.ejb3.common.spi, com.edb, org.jboss.metadata.process.chain.ejb.jboss, org.jboss.security.xacml.sunxacml.support.finder, org.jboss.jms.server.container, org.jboss.profileservice.management.templates, org.apache.bsf.util.cf, org.quartz.utils, org.jboss.ha.framework.test, org.hibernate.validator.event, javax.security.auth.message.callback, org.jboss.ejb3.common.lang, org.hsqldb.lib.java, org.jboss.ejb3.proxy.intf, org.jboss.iiop.naming, org.jboss.security.xacml.bridge, org.jboss.remoting.samples.chat, org.jnp.server, org.hsqldb.scriptio, org.apache.commons.httpclient.methods.multipart, org.jboss.ejb3.proxy.factory.stateful, org.jboss.metadata.client.spec, org.w3c.dom, com.arjuna.ats.tsmx.common, org.jaxen.function.ext, javax.management.remote, com.arjuna.ats.internal.jbossatx.jta, org.jboss.ejb3.security.annotation, org.jnp.interfaces.java, org.jboss.ejb3.entity.hibernate, bsh, org.apache.log4j.lf5.util, org.quartz.plugins.management, org.jaxen.saxpath.helpers, org.jboss.metadata.annotation.creator.ws, org.jboss.remoting.samples.transporter.proxy.server, javax.jms, org.jboss.ejb3.util, antlr.actions.python, org.hibernate.loader.custom, stylesheets, org.jnp.client, javax.jws.soap, org.jboss.profileservice.management.upload.remoting, org.jboss.ejb3.common.string, org.hibernate.engine.query.sql, org.jboss.ejb3.metadata.spi.signature, org.jboss.metadata.validation.validator.ejb.jboss, org.jboss.ejb3.javaee, javax.resource.spi, org.hibernate.persister.collection, org.hibernate.hql.ast.tree, org.jboss.remoting.samples.simple, org.jboss.remoting.serialization, org.jboss.profileservice.management.matchers, org.jaxen.expr.iter, org.jboss.remoting.transport.servlet.web, org.jboss.ha.singleton.examples, org.jboss.ejb3.proxy.clustered.objectstore, org.jboss.ejb3.proxy.objectfactory.session.stateful, org.jboss.jms.client.plugin, org.jboss.remoting.samples.chat.utility, org.jboss.remoting.transport.sslservlet, org.jboss.security.plugins.audit, org.jboss.ejb3.proxy, org.hibernate.hql.antlr, org.jboss.security.identitytrust, org.jboss.ejb3.interceptors.annotation, org.jboss.deployment.spi.status, org.hibernate.proxy.pojo.javassist, org.jboss.remoting.loading, javax.resource.spi.work, com.arjuna.common.util.exceptions, org.jboss.security.jndi, org.apache.commons.collections.bidimap, org.jboss.ejb.plugins.lock, com.ibatis.sqlmap.engine.datasource, META-INF.maven.org.jboss.aspects.jboss-remoting-aspects, org.jboss.aspects.remoting.interceptors.invoker, org.apache.bcel.verifier.structurals, org.jboss.remoting.samples.transporter.multiple, org.quartz.helpers, org.jboss.varia.scheduler.example, com.arjuna.ats.jdbc.common, org.jboss.mx.remoting.provider.iiop, org.jboss.crypto, org.apache.bsf, com.ibatis.sqlmap.client.event, org.jboss.security.identity, org.quartz.utils.weblogic, javax.servlet.jsp.tagext, com.arjuna.ats.jbossatx, org.hibernate.jmx, org.jboss.resource.work, javax.enterprise.deploy.spi.status, org.jboss.security.identitytrust.config, org.jboss.metadata.validation.validator, org.hibernate.hql.ast, antlr, com.arjuna.ats.internal.txoj, org.jboss.resource.statistic, org.jboss.naming, org.jboss.jms.server.connectionfactory, org.jboss.remoting.detection, org.hibernate.proxy.map, org.apache.commons.collections.buffer, org.jboss.metadata.validation.chain, org.jboss.wsf.spi.binding, org.jboss.wsf.spi.invocation, com.ibatis.sqlmap.engine.mapping.sql.stat, org.jboss.remoting.security, org.hibernate.annotations.common.util, org.jboss.ejb3.timerservice.quartz, javax.xml.registry, org.jboss.jpa.remote, org.jboss.metadata.javaee.jboss, org.jaxen.jdom, org.jboss.messaging.core.contract, org.jboss.ejb3.common.registrar.plugin.mc, org.jboss.messaging.util.prioritylinkedlist, org.jboss.ejb3.proxy.factory.session.service, org.apache.bsf.engines.javascript, antlr.preprocessor, org.jboss.wsf.framework.http, org.jboss.security.jce, org.jboss.ejb.plugins.jms, org.quartz.ee.jmx.jboss.doc-files, javax.xml.rpc.server, org.jboss.ejb3.proxy.clustered.factory.session.stateless, com.sun.mail.smtp, org.jboss.metadata.web.jboss, com.edb.core.types, org.jboss.remoting.transport.multiplex, org.quartz.jobs.ee.mail, org.apache.log4j.or.sax, org.jboss.wsf.common, org.jaxen.util, org.jboss.remoting.samples.http, org.jboss.aspects.security, org.jboss.security.acl, com.arjuna.common.util.concurrency, org.hibernate.engine.transaction, com.ibatis.common.beans, org.hibernate.bytecode.cglib, org.jboss.util.stream, org.jboss.jms.server.destination, javax.enterprise.deploy.shared.factories, org.jboss.ejb3.common.proxy.spi, org.jboss.ejb3.annotation, org.jboss.corba, org.hibernate.loader.criteria, org.jboss.metadata.merge, org.jboss.ejb3.proxy.clustered.objectfactory.session.stateless, org.jboss.ejb3.proxy.clustered.jndiregistrar, com.arjuna.ats.internal.tsmx.mbeans, org.hibernate.annotations.common, org.jboss.remoting.ident, org.jboss.invocation.unified.interfaces, org.jboss.security.plugins.authorization, org.jboss.ejb.deployers, org.hsqldb.util, org.jboss.hibernate, META-INF.maven.org.jboss.security.jboss-xacml, com.ibatis.sqlmap.engine.type, org.jboss.ejb3.metadata.jpa.spec, org.jboss.ejb3.proxy.objectfactory, org.jboss.ha.framework.server.spi, org.jboss.ejb3.interceptor, org.jboss.jms.server.endpoint.advised, javax.servlet.jsp, org.jboss.mx.remoting, org.jboss.security.factories, org.jboss.resource.connectionmanager.xa, org.jboss.verifier.factory, org.jboss.ha.hasessionstate.interfaces, org.jboss.aspects.remoting.interceptors.marshall, org.hibernate.engine.query, META-INF.maven.org.jboss.ejb3.jboss-ejb3-cache, org.apache.commons.logging, org.jboss.deployment.security, org.jboss.jpa.javaee, org.jboss.iiop.rmi.marshal.strategy, org.jboss.cache.invalidation.triggers, com.arjuna.ats.internal.arjuna.objectstore, org.jboss.tm, org.jboss.security.auth, javax.resource.cci, org.jboss.management.j2ee.deployers, org.jboss.jms.server, org.jboss.security.srp.jaas, com.edb.jdbc2, com.arjuna.common.internal.util.propertyservice, com.edb.jdbc3, javax.xml.ws.spi, org.jboss.naming.interceptors, org.jboss.metadata.annotation.creator.ejb.jboss, org.jboss.security.xacml.sunxacml.cond, org.jboss.security, org.jboss.security.auth.message.config, org.apache.commons.collections.functors, org.jboss.ejb3.proxy.clustered.invocation, META-INF.maven.org.jboss.cluster.jboss-ha-server-cache-jbc, org.jboss.slf4j, org.hibernate.mapping, org.jboss.jms.server.endpoint, org.jboss.metadata.process, META-INF.services, org.quartz.impl, org.jboss.ejb3.proxy.factory.session.stateful, org.hibernate.validator.interpolator, META-INF.maven.org.jboss.ws.jbossws-framework, org.jboss.ejb3.security, org.jboss.security.auth.login, org.apache.bsf.util.type, org.apache.commons.collections.collection, org.jboss.jms.client.state, com.arjuna.ats.internal.jta.resources.arjunacore, org.jboss.remoting.samples.transporter.multiple.server, org.jboss.ejb3.common.proxy.plugins.async, org.jboss.remoting.samples.config.factories, org.hibernate.ejb.instrument, org.apache.log4j.xml, org.jboss.remoting.samples.transporter.serialization, org.hibernate.action, org.jboss.resource, org.jboss.wsf.spi.tools, org.jboss.deployment.spi.beans, org.jboss.remoting.samples.transporter.clustered.client, org.jboss.ejb3, org.jboss.metadata.annotation.creator, org.jboss.ha.framework.server.deployers, org.jboss.ejb3.proxy.factory.stateless, org.quartz.jobs.ee.jmx, org.jboss.wsf.framework.invocation, org.apache.bsf.engines.jython, org.jboss.invocation.jrmp.server, org.jboss.wsf.spi.annotation, org.jboss.ejb3.connectionmanager, org.hibernate.dialect, org.jboss.ejb3.jms, org.jboss.invocation.unified.marshall, com.ibatis.sqlmap.engine.cache.lru, org.jboss.messaging.core.jmx, javax.mail, org.jboss.wsf.spi.deployment.integration, com.edb.core, org.hibernate.bytecode.javassist, com.edb.copy, org.apache.log4j.helpers, com.arjuna.ats.jta.recovery, META-INF.maven.org.jboss.metadata.jboss-metadata, org.jboss.security.xacml.core.ext, org.jboss.proxy.generic, org.jboss.metadata.lang, com.arjuna.ats.arjuna, org.slf4j.impl, com.arjuna.ats.internal.tsmx.agent.implementations.ri, org.hsqldb.index, org.jboss.persistence, org.hibernate.connection, org.jboss.aspects.remoting, org.jboss.remoting.serialization.impl.jboss, org.jboss.web.tomcat.service.sso.spi, org.jboss.jms.server.connectionmanager, com.ibatis.sqlmap.engine.mapping.statement, com.ibatis.common.xml, org.jboss.ejb3.proxy.handler.session.stateful, org.hibernate.proxy.pojo, org.jaxen.expr, com.ibatis.sqlmap.engine.mapping.parameter, org.jboss.remoting.samples.detection.jndi.ssl, org.jboss.messaging.core.impl.message, org.jboss.security.authorization.resources, org.jboss.ejb.plugins.cmp.jdbc2, org.jboss.metadata.ejb.jboss, antlr.collections, org.jboss.security.cache, org.jboss.web.tomcat.service.sso.jbc, javax.enterprise.deploy.model.exceptions, org.hsqldb.rowio, META-INF, org.jboss.mx.remoting.tracker, org.jboss.mx.remoting.provider.rmi, com.arjuna.ats.txoj.tools, org.jboss.security.xacml.core, org.jboss.wsf.spi.metadata.webservices, org.jboss.security.authorization.util, org.quartz.ee.jmx.jboss, org.jboss.ejb3.proxy.objectfactory.session.service, org.hibernate.validator, com.arjuna.ats.internal.arjuna.coordinator, org.apache.commons.collections.keyvalue, com.ibatis.common.resources, org.jboss.security.xacml.sunxacml.attr.proxy, javax.mail.internet, com.arjuna.ats.arjuna.objectstore, org.jboss.ha.framework.interfaces, org.apache.log4j.lf5.config, org.jboss.metadata.annotation.creator.jboss, org.jboss.invocation.pooled.interfaces, javax.xml.ws.handler, org.jboss.ejb3.cache, org.jboss.metadata.ejb.jboss.proxy, com.ibatis.common.logging.jdk14, com.arjuna.ats.internal.jta.resources, org.jboss.remoting.samples.transporter.basic.client, org.quartz.ee.jta, com.ibatis.common.jdbc.exception, org.hibernate.transaction, org.jboss.security.config, com.arjuna.ats.internal.jta.utils.arjunacore, org.jboss.ejb3.proxy.factory.session, org.jboss.ejb3.proxy.clustered.handler.session.stateless, javax.security.auth.message, org.jboss.ejb3.cache.tree, com.edb.xa, org.jboss.remoting.samples.callback.acknowledgement, com.ibatis.common.jdbc.logging, org.jboss.remoting.samples.serialization, org.jboss.hibernate.jmx, com.sun.mail.iap, META-INF.maven.org.jboss.aspects.jboss-current-invocation-aspects, com.ibatis.sqlmap.engine.scope, org.jboss.ejb3.proxy.factory.session.stateless, org.jboss.jms, org.jboss.ejb3.statistics, org.apache.commons.httpclient.params, org.jboss.ejb.plugins.cmp.jdbc.keygen, com.edb.geometric, org.apache.commons.logging.impl, org.hibernate.intercept, com.arjuna.ats.internal.jdbc.recovery, org.quartz.plugins.history, org.jboss.jmx.connector.invoker.serializablepolicy, javax.ejb, org.jboss.ha.singleton, com.sun.mail.imap, org.apache.commons.collections, org.jboss.ejb.plugins.keygenerator, org.hibernate.jdbc, org.jboss.security.audit, org.jboss.wsf.spi.http, com.ibatis.sqlmap.engine.mapping.result.loader, org.jboss.managed.plugins.advice, org.hsqldb.store, org.slf4j.spi, org.jboss.wsf.spi, org.jboss.remoting.samples.transporter.complex.client, org.jboss.jms.recovery, org.jboss.iiop, com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate, org.jboss.ha.jmx.examples, org.jboss.monitor.client, org.jboss.security.xacml.sunxacml.cond.cluster, org.hibernate.secure, org.jboss.metadata, org.jboss.ejb3.tx, org.jboss.security.callbacks, com.arjuna.ats.internal.arjuna.thread, org.quartz.impl.jdbcjobstore.oracle, javax.xml.ws.soap, org.jboss.ejb3.interceptors, org.jboss.wsf.spi.metadata.j2ee, javax.xml.ws.wsaddressing, org.hibernate.cfg, org.jboss.management.j2ee.cluster, org.jboss.security.client, org.jboss.security.plugins.identitytrust, org.jboss.ejb3.interceptors.metadata, org.jboss.ejb3.proxy.handler, org.hibernate.tool.instrument.javassist, org.jboss.ejb3.remoting, org.jboss.metadata.ejb.jboss.jndipolicy.spi, com.arjuna.ats.internal.jta, org.jboss.security.plugins.javaee, com.ibatis.common.logging.jakarta, org.jaxen.saxpath.base, org.jboss.remoting.network.filter, META-INF.maven.org.jboss.ejb3.jboss-ejb3-interceptors, org.apache.commons.httpclient.cookie, org.jboss.remoting.marshal, org.jboss.ejb3.resolvers, org.hibernate.cache.impl, org.jboss.proxy.compiler, org.jboss.jpa.deployment, org.jboss.serial.exception, org.jboss.invocation.unified.server, org.hibernate.id.insert, org.jboss.ejb.plugins.cmp.ejbql, org.jboss.cache.invalidation.bridges, org.jboss.remoting.transport.local, com.arjuna.common.internal.util.logging.jakarta, org.jaxen.dom, com.arjuna.ats.arjuna.gandiva, com.arjuna.ats.arjuna.tools, org.jboss.remoting.marshal.http, bsh.util, org.apache.log4j.lf5.viewer.categoryexplorer, org.jboss.ejb.plugins, org.jboss.ejb.txtimer, org.jboss.serial.references, javax.xml.rpc.handler, org.jboss.ejb3.pool, org.hibernate.hql.ast.util, org.jboss.mx.remoting.connector, org.jboss.security.auth.callback, org.jboss.metadata.annotation.creator.ejb, org.apache.commons.collections.comparators, org.jboss.ejb3.stateless, com.arjuna.ats.internal.jdbc.drivers.modifiers, org.jboss.remoting.samples.detection.jndi, com.arjuna.ats.arjuna.logging, org.jboss.ejb3.interceptors.aop.annotation, org.jboss.ejb3.annotation.impl, org.jboss.ejb3.mdb.inflow, javax.servlet.resources, org.jboss.security.authorization.modules.ejb, org.jboss.proxy, org.jboss.remoting.samples.chat.server, org.jboss.jms.jndi, org.jboss.aspects.txlock, org.jboss.remoting.transport.https, org.quartz.impl.jdbcjobstore.oracle.weblogic, org.jboss.security.xacml.sunxacml.attr, org.jboss.iiop.csiv2, org.jboss.remoting.transport.coyote.ssl, javax.el, org.jaxen.xom, META-INF.maven.org.jboss.ejb3.jboss-ejb3-metadata, com.arjuna.ats.internal.jbossatx.agent, javax.management.j2ee.statistics, META-INF.maven.org.jboss.javaee.jboss-jaspi-api, com.arjuna.ats.internal.arjuna.gandiva.inventory, org.jboss.ejb3.service, org.jboss.remoting.samples.chat.client, org.jboss.metadata.validation.validator.ejb, org.hibernate.ejb.util, org.hibernate.ejb, org.jboss.security.plugins.auth, org.hibernate.dialect.function, org.jboss.invocation.http.interfaces, com.arjuna.ats.arjuna.recovery, org.quartz.impl.jdbcjobstore, schema, org.jboss.messaging.core.impl.postoffice, org.jboss.security.authorization, org.jboss.ejb3.cache.simple, META-INF.maven.org.jboss.ejb3.jboss-ejb3-core, org.jboss.ejb3.interceptors.annotation.impl, org.jboss.monitor.services, org.jboss.profileservice.spi, org.jboss.remoting.socketfactory, org.jboss.profileservice.spi.types, org.apache.commons.collections.list, org.jboss.tm.iiop, com.arjuna.ats.arjuna.common, org.jboss.jms.server.recovery, org.hibernate.annotations.common.reflection.java.generics, antlr.actions.java, com.ibatis.sqlmap.engine.exchange, org.jboss.resource.deployment, org.jboss.annotation.ear, com.ibatis.sqlmap.engine.mapping.sql.simple, META-INF.maven.org.jboss.naming.jnpserver, org.jboss.ha.jndi.impl.jbc, org.hibernate.dialect.lock, org.jboss.remoting.transport.coyote, org.apache.commons.httpclient.auth, org.hibernate.proxy.dom4j, org.hibernate.pretty, javax.annotation, org.jboss.remoting.transport.multiplex.utility, javax.xml.ws.handler.soap, org.hibernate.util, javax.resource, org.jaxen.dom4j, org.jboss.jms.tx, org.jboss.remoting.util.socket, org.jboss.jmx.connector.invoker.client, META-INF.maven.org.jboss.slf4j.slf4j-jboss-logging, org.jboss.wsf.spi.management.recording, META-INF.maven.org.jboss.ws.native.jbossws-native-jaxws, com.arjuna.ats.internal.arjuna.state, org.jboss.jpa.deployers, org.hibernate.proxy.pojo.cglib, com.sun.mail.pop3, org.jboss.proxy.ejb, org.jboss.messaging.core.impl.memory, org.jboss.remoting.samples.transporter.custom.client, org.jboss.security.javaee, org.apache.log4j.ext, org.apache.bcel.verifier.statics, org.jboss.jms.client.container, org.jboss.metadata.rar.spec, org.slf4j, org.apache.bsf.util.event, com.arjuna.common.internal.util.logging, META-INF.maven.org.jboss.ejb3.jboss-ejb3-transactions, org.jboss.remoting.samples.transporter.serialization.client, org.jboss.serial.objectmetamodel.safecloning, org.hibernate.ejb.packaging, org.jboss.ejb3.proxy.clustered.objectfactory.session, javax.persistence.spi, bsh.classpath, com.arjuna.ats.tsmx, org.jboss.ejb.plugins.cmp.bridge, org.jboss.resource.metadata.repository, com.arjuna.ats.tsmx.logging, org.jboss.cache.invalidation, org.jboss.profileservice.aop, org.hibernate.cache.impl.bridge, org.jboss.remoting.network, org.jboss.ejb3.cache.impl, org.jboss.ejb3.naming.client.java, org.jboss.ha.jmx, org.apache.commons.httpclient.util, org.jboss.monitor.alarm, dtd, com.ibatis.sqlmap.client, com.ibatis.sqlmap.engine.mapping.sql, META-INF.maven.org.jboss.aspects.jboss-transaction-aspects, org.jboss.metadata.annotation.creator.web, org.jboss.jms.destination, org.jboss.remoting.samples.chat.exceptions, org.jboss.web.deployers, org.jboss.ejb.plugins.security, org.jboss.tm.usertx.interfaces, com.edb.ssl, org.jboss.wsf.common.handler, org.jboss.ejb3.proxy.container, com.ibatis.common.logging, javax.servlet.jsp.el, META-INF.maven.org.jboss.ws.jbossws-spi, org.jboss.remoting.marshal.encryption, org.jboss.ejb3.entity, org.jboss.security.microcontainer.beans, org.jboss.jms.server.jbosssx, org.jboss.jms.client, org.apache.log4j.jmx, org.jboss.ejb.plugins.inflow, org.jboss.ejb3.security.client, org.jboss.ha.framework.server, org.apache.log4j.config, org.jboss.profileservice.spi.repository, org.jboss.serial, org.hibernate.tuple.entity, javax.xml.ws.addressing, org.jboss.tm.usertx.server, org.jboss.resource.adapter.jdbc.jdk5, org.jboss.remoting.marshal.compress, org.jboss.security.annotation, META-INF.maven.org.jboss.ejb3.jboss-ejb3-deployers, com.arjuna.ats.internal.jta.transaction.arjunacore.jca, org.jboss.metadata.ear.jboss, org.jboss.injection, com.ibatis.sqlmap.engine.transaction.jta, com.arjuna.ats.jta.exceptions, org.jboss.jms.message, org.jboss.serial.persister, org.hibernate.hql.classic, org.jboss.remoting.util, org.quartz.jobs.ee.ejb, org.jboss.remoting.callback, org.jboss.remoting.samples.transporter.simple, org.jboss.resource.statistic.pool, com.arjuna.ats.jta.logging, com.ibatis.sqlmap.engine.transaction.external, com.ibatis.sqlmap.engine.cache, org.hibernate.criterion, javax.transaction, javax.xml.soap, org.jboss.security.xacml.core.model.context, org.jboss.remoting.marshal.rmi, org.jboss.invocation.jrmp.interfaces, org.jboss.security.jacc, org.apache.log4j, org.jboss.ejb3.proxy.clustered.objectfactory, org.hibernate.tool.instrument, org.jboss.remoting.samples.transporter.basic.server, org.jboss.ejb3.annotation.defaults, org.jboss.iiop.rmi, org.jboss.mq.server.jmx, org.jboss.metadata.ear.spec, org.jboss.security.plugins, org.jboss.ejb3.proxy.impl, org.apache.commons.collections.bag, org.apache.log4j.chainsaw, org.opennms.protocols.snmp, org.jboss.deployment.spi.factories, org.jboss.security.mapping.config, org.jboss.aspects.remoting.interceptors.transport, com.ibatis.sqlmap.engine.builder.xml, org.jboss.serial.classmetamodel, com.arjuna.ats.internal.arjuna.recovery, org.jboss.security.identity.plugins, org.apache.bsf.util.event.generator, org.apache.bcel, org.jboss.remoting.transport.http, org.jboss.tm.usertx, org.jboss.remoting.marshall.encryption, org.jboss.security.auth.message, org.hibernate.loader.hql, org.jboss.security.identity.extensions, META-INF.maven.org.jboss.ejb3.jboss-ejb3-common, javax.mail.search, org.jboss.security.auth.container.modules, org.hibernate.metadata, org.jboss.metadata.web.spec, org.jboss.deployment.spi, org.jboss.security.authorization.config, org.jboss.iiop.tm, org.jboss.ejb3.interceptors.util, org.jboss.wsf.framework.deployment, org.jboss.ejb3.asynchronous, org.hibernate.property, org.jboss.remoting.samples.stream, javax.management.j2ee, org.jboss.util, org.jboss.mx.remoting.rmi, org.jboss.deployment.remoting, org.jnp.interfaces.jnp, org.hibernate.collection, org.jboss.management.j2ee.factory, com.ibatis.common.util, org.hibernate.exception, org.jboss.wsf.spi.tools.cmd, org.jboss.naming.client.java, com.sun.mail.util, org.hibernate.param, META-INF.maven.org.jboss.ejb3.jboss-ejb3-proxy, org.jboss.metadata.rar.jboss.mcf, org.jboss.wsf.spi.invocation.integration, com.arjuna.ats.arjuna.xa, org.jboss.jms.server.plugin, org.jboss.ejb.plugins.cmp.jdbc2.keygen, org.jboss.wsf.common.servlet, javax.servlet.jsp.resources, org.jboss.security.plugins.mapping, org.jboss.hibernate.session, org.jboss.remoting.transport.sslbisocket, com.sun.mail.imap.protocol, org.jboss.ejb3.timerservice.quartz.jmx, com.edb.jdbc2.optional, META-INF.maven.org.jboss.aspects.jboss-security-aspects, org.jboss.remoting.transport, org.jboss.jpa.spi, com.arjuna.ats.internal.arjuna.utils, org.apache.bcel.classfile, org.jboss.ejb3.stateful, antlr.ASdebug, org.jboss.metadata.client.jboss, org.hibernate.tool.hbm2ddl, org.jboss.jms.referenceable, com.arjuna.ats.arjuna.exceptions, org.hibernate.loader.custom.sql, org.jboss.remoting.samples.callback, com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors, org.jboss.ws.tools.ant, org.hsqldb.types, org.jboss.iiop.codebase, META-INF.maven.org.hibernate.hibernate-jmx, org.jboss.security.xacml.factories, org.apache.bcel.verifier, com.ibatis.sqlmap.engine.transaction, org.apache.commons.httpclient, com.arjuna.ats.jdbc.logging, org.jboss.ejb.plugins.cmp.jdbc2.bridge, org.jaxen.saxpath, antlr.debug, com.arjuna.common.util.propertyservice.plugins, org.jboss.metadata.process.chain, antlr.actions.csharp, org.jboss.remoting.security.domain, org.jboss.security.xacml.sunxacml.finder, org.jboss.ejb3.proxy.remoting, org.jboss.ejb.plugins.cmp.jdbc.bridge, org.jboss.iiop.rmi.ir, org.jboss.jms.server.selector, org.jboss.ejb3.proxy.handler.stateful, org.hibernate.annotations.common.annotationfactory, org.jboss.ejb3.security.bridge, org.jboss.security.audit.config, org.jboss.remoting.transport.http.ssl, org.jboss.deployment.plugin, org.jboss.security.xacml.core.model.policy, org.apache.log4j.net, org.jboss.ejb3.tx.metadata, org.jboss.security.auth.certs, antlr.actions.cpp, org.jboss.metadata.ejb.jboss.jndipolicy.plugins, org.jboss.resource.metadata.mcf, licenses, com.ibatis.sqlmap.engine.config, org.hibernate.event, org.jboss.metadata.common.ejb, org.jaxen.function.xslt, javax.resource.spi.endpoint, javax.resource.spi.security, org.hibernate.cfg.annotations, META-INF.maven.org.jboss.cluster.jboss-ha-server-cache-spi, org.jboss.wsf.framework.management, org.jboss.ejb3.cache.grouped, org.jboss.metadata.javaee.support, org.jboss.ejb3.session, org.jboss.ejb3.proxy.handler.session.stateless, org.jboss.remoting.transport.socket, org.quartz.ee.servlet, com.arjuna.ats.jta, org.jboss.profileservice.remoting, javax.xml.rpc.encoding, javax.enterprise.deploy.spi.factories, org.jboss.security.audit.providers, javax.annotation.security, org.jboss.remoting.transport.sslmultiplex, org.jboss.varia.scheduler, com.ibatis.sqlmap.engine.mapping.sql.dynamic, org.jboss.logging, org.jboss.metadata.javaee.spec, org.jboss.jdbc, com.arjuna.ats.internal.jdbc, com.ibatis.common.io] <IMPORT-ALL>NON_EMPTY}}
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:385)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.hibernate.util.ReflectHelper.classForName(ReflectHelper.java:123)
at org.hibernate.connection.DriverManagerConnectionProvider.configure(DriverManagerConnectionProvider.java:84)
at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:137)
at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:79)
at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:448)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:89)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2101)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1325)
at ws.RobinWebService.getRobinTest(RobinWebService.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Unknown Source)
16:56:55,319 ERROR [STDERR] Failed to create sessionFactory object.org.hibernate.HibernateException: JDBC Driver class not found: oracle.jdbc.OracleDriver
16:58:29,557 INFO [STDOUT] hello
16:58:29,557 INFO [Configuration] configuring from resource: support/oracle.hibernate.cfg.xml
16:58:29,557 INFO [Configuration] Configuration resource: support/oracle.hibernate.cfg.xml
16:58:30,116 INFO [Configuration] Reading mappings from resource : support/Centres.hbm.xml
16:58:30,116 INFO [HbmBinder] Mapping class: ws.Centres -> CENTRE_DETAIL
16:58:30,116 INFO [Configuration] Reading mappings from resource : support/RobinTest.hbm.xml
16:58:30,116 INFO [HbmBinder] Mapping class: ws.RobinTest -> ROBIN_TEST
16:58:30,116 INFO [Configuration] Configured SessionFactory: null
16:58:30,116 INFO [DriverManagerConnectionProvider] Using Hibernate built-in connection pool (not for production use!)
16:58:30,116 INFO [DriverManagerConnectionProvider] Hibernate connection pool size: 1
16:58:30,116 INFO [DriverManagerConnectionProvider] autocommit mode: false
16:58:30,131 ERROR [DriverManagerConnectionProvider] JDBC Driver class not found: oracle.jdbc.OracleDriver
java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver from BaseClassLoader@1652e61{VFSClassLoaderPolicy@1c7eb33{name=vfsfile:/C:/Jboss/jboss-5.0.0.GA/server/default/conf/jboss-service.xml domain=ClassLoaderDomain@9fe84e{name=DefaultDomain parentPolicy=BEFORE parent=org.jboss.system.NoAnnotationURLClassLoader@a97b0b} roots=[MemoryContextHandler@2254409[path= context=vfsmemory://4shc4f-nlo6vf-hjk3qb83-1-hjk3qewj-6 real=vfsmemory://4shc4f-nlo6vf-hjk3qb83-1-hjk3qewj-6], DelegatingHandler@6903079[path=antlr.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/antlr.jar], DelegatingHandler@22387624[path=autonumber-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/autonumber-plugin.jar], DelegatingHandler@22963857[path=bcel.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/bcel.jar], DelegatingHandler@10479206[path=bsf.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/bsf.jar], DelegatingHandler@30371681[path=bsh.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/bsh.jar], DelegatingHandler@26839239[path=commonsYou have to put the path of the driver jar file on server.xml file. If you open up the server.xml file inside the config directory of the appserver instance you will find all the paths are added to <java-config java-home = tag. So place the path in this place. Then there should not be any problem getting the driver.
Thanks -
I have read the posts about caching initial context lookups and have
implemented the solution and seen some benefits.
I am dealing with a third party application that I cannot change.
When I put my InitialContextFactory in the architecture I also logged
how many getInitialContext() calls were being made - I was absolutely
shocked - often 4+ per user transaction. I suspect that the code gets
one, does a call and dereferences all over the place.
90% of InitialContexts had the same environment passed to the getIC()
call so it struck me that what I should do is create a pool of IC, and
in my factory just serve one from the pool.
So, the question is, what is the best way of detecting when the IC has
been dereferenced so I know I can serve it again from my pool?
I presume this is a generic pool problem when you can't guarantee that
your client's will be good citizens and call a close() method or
similar.
I've posted here as it is performance related; also, is there any
reason why what I am doing is not a good idea?
Can the client do something with the IC which means it is not suitable
for use by another client? If so, can I detect this so I may discard?
As always, many thanks in advance.
Presuming I can get it to work I will post the code so that we can all
share ;-)
Cheers
EdWhy don't you instrument your factory then to give out your own
implementation of InitialContext that will in fact only wrap a "loaner"
InitialContext every time a method is invoked on it and before returning
the value to the caller will put the real InitialContext back to the
pool to be reused by another one.
Then your clients can do whatever they want with those ICs and still
would not cause so big performance hits.
It's just an idea that just came to mind and I haven't tested it so it
might have flaws but it looks viable.
--dejan
Ed Barrett wrote:
The application is a third-party product that cannot be changed.
By introducing the factory you gave below (thanks!) we put the application
back under the load test and saw minimal improvements (like 1% response
time).
I then instrumented the factory with a system.out on finalize and noticed
that a factory instance is created for each call to getInitialContext() - is
this the way that WLS/J2EE works? I would have hoped that factories were
shared or something. What we did see is that for one user request a number
(sometimes 5!) ICs were being created ;-( Obviously the lookup cache is a
class instance and shared across the lot.
So then I started to think about pre-creating ICs and haveing a pool for the
default ones (environment specifies URL and no security details or the
like). Trouble is how to implement such when you cannot change the client
code to call a factory return method (such as returnToPool()).
Any ideas would be appreciated
"Dimitri I. Rakitine" <[email protected]> wrote in message
news:[email protected]...
I've ran into this problem while porting 5.1 application (JNDI lookups
were
super-cheap) to 6.1 (where they are not so cheap due to
serialization/deserialization)
and did this test to see if this indeed was the problem. As you saw I
didn't bother to
cache InitialContext's - I just cached JNDI lookups and that resulted in
very significant
performance improvements.
Which application are you testing it with?
Graham <[email protected]> wrote:
Dimitri,
We did this but did not see that much improvement over the default way -
we
are using 6.1 sp2.
We put some messages in our factory and found that the client code often
created over 4 ICs for one user click - aaggghhhh!! As I say we cannot
change their code but if we could take the time to create an IC away
from
the online response we feel we would save some time.
We also observed a new instance of the IC factory being created every
time a
new IC was created - is this what you would expect?
I think this is what NamingManager.getInitialContext() is supposed to do.
Cheers
Ed
"Dimitri I. Rakitine" <[email protected]> wrote in message
news:[email protected]...
Caching InitialContext's will probably not quite solve the problem,
because lookup()'s are expensive (in 6.x), so, caching lookup results
will result in performance improvements.
If you cannot change the 3'rd party code and all it does is:
... DataSource ds = (DataSource)new InitialContext().lookup(".....");
or similar, you can add caching by implementing your own InitialContext
factory,
for example: (extremely simplistic)
Startup class :
System.setProperty("java.naming.factory.initial",
"myjndi.InitialContextFactory");
where
myjndi.InitialContextFactory is :
public class InitialContextFactory implements
javax.naming.spi.InitialContextFactory {
public Context getInitialContext(Hashtable env) throws
NamingException
Context ctx = new
weblogic.jndi.WLInitialContextFactory().getInitialContext(env);
return
(Context)Proxy.newProxyInstance(ctx.getClass().getClassLoader(),
new Class[]
{ Context.class },
new
ContextHandler(ctx));
and myjndi.ContextHandler is:
public class ContextHandler implements InvocationHandler {
Context ctx;
static Hashtable cache = new Hashtable();
public ContextHandler(Context ctx) {
this.ctx = ctx;
public Object invoke(Object proxy, Method method, Object[] args)
throws Throwable {
try {
Object retVal;
if("lookup".equals(method.getName()) && args[0] instanceof
String) {
retVal = cache.get(args[0]);
if(retVal == null) {
retVal = method.invoke(ctx, args);
cache.put(args[0], retVal);
} else {
retVal = method.invoke(ctx, args);
return retVal;
} catch(InvocationTargetException oops) {
throw oops.getTargetException();
Ed <[email protected]> wrote:
Adarsh,
We agree it is a brilliant idea - now just to work out how to do it.
As you cannot always guarantee to be able to change the client code
you cannot use normal pooling techniques:
getObjectFromPool()
// do work
returnObjectToPool()
So, the client code needs an InitialContext. We can put in our own
Factory and intercept the getInitialContext() calls. This method
must
return class javax.naming.Context - therefore the only way I can see
to spot when the class is dereferenced is to extend the class and add
a finalize() method that notifies the factory.
The trouble I believe is that the class cannot be "rescued" in the
finalize() method (i.e. "I'm dying - take me back" ;-). If it simply
told the factory to add another one to its pool this would mean that
the new IC create "hit" would be in garbage collection (i.e. the
users
will pay somewhere along the line) - is this correct?
Anyone any ideas on a solution? I have discovered out code create
HUNDREDS of contexts in an hour and discards them very quickly. Be
nice to be able to cache them!
Cheers
Ed
"Adarsh Dattani" <[email protected]> wrote in message
news:<[email protected]>...
Ed,
This a brilliant idea. We are planning something similar too. We
first
want to create a pool of LDAP connections as apps make extensive
calls
to
LDAP. Did you check-out the object pooling api at Jakarta Commons.
It
deserves a close look.
http://jakarta.apache.org/commons/pool/index.html
Thanks,
Adarsh
"Ed" <[email protected]> wrote in message
news:[email protected]...
I have read the posts about caching initial context lookups and
have
implemented the solution and seen some benefits.
I am dealing with a third party application that I cannot change.
When I put my InitialContextFactory in the architecture I also
logged
how many getInitialContext() calls were being made - I was
absolutely
shocked - often 4+ per user transaction. I suspect that the code
gets
one, does a call and dereferences all over the place.
90% of InitialContexts had the same environment passed to the
getIC()
call so it struck me that what I should do is create a pool of IC,
and
in my factory just serve one from the pool.
So, the question is, what is the best way of detecting when the IC
has
been dereferenced so I know I can serve it again from my pool?
I presume this is a generic pool problem when you can't guarantee
that
your client's will be good citizens and call a close() method or
similar.
I've posted here as it is performance related; also, is there any
reason why what I am doing is not a good idea?
Can the client do something with the IC which means it is not
suitable
for use by another client? If so, can I detect this so I may
discard?
As always, many thanks in advance.
Presuming I can get it to work I will post the code so that we can
all
share ;-)
Cheers
Ed
Dimitri
Dimitri -
Hi,
I tried to compile the SimpleTopicPublisher and SimpleTopicSubscriber from the following link. I used the javax.jms.jar and the jms.jar from sun.
http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/client.html#1027256
The code got compiled.
I had a queue in MQSeries, its sample queue called postcard.
When I tried running SimplePublisherTopic, the following exception was thrown:
<code>
D:\>java SimpleTopicPublisher postcard 1
Topic name is postcard
JNDI API lookup failed: javax.naming.NoInitialContextException: Need to specify
class name in environment or system property, or as an applet parameter, or in a
n application resource file: java.naming.factory.initial
javax.naming.NoInitialContextException: Need to specify class name in environmen
t or system property, or as an applet parameter, or in an application resource f
ile: java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
43)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.jav
a:283)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at SimpleTopicPublisher.main(SimpleTopicPublisher.java:60)
</code>
The program is J2EE server independent. The MQSeries for Win 2000 is used for JMS services.
Please help me in understanding the following :
1) How to get the JNDI server running and registering our topic there?
2) There was no reference of 'Topic' in MQSeries. There are only 'Queue'. If this is the case, how to create topics in MQSeries.
3) Who are providers? There are JNDI provider and IBMMQSeries provider. What is to be used? Can they both be used?
4) MQSeries has a Java API. Is it a replacement/substitute for Sun JMS API? Which should we use to write a generic JMS code?
Thanks in advance,
RajeshI could solve some of the exceptions based on Steve's suggestions. I am giving below on how I solved.
"JNDI API lookup failed: javax.naming.NoInitialContextException: "
The SimpleTopicPublisher has set env property for InitialContext and expects our System's properties to specify the provider URL. I have added the property this way in code:
try {
// Identify service provider to use
Hashtable env = new Hashtable(11);
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sun.jndi.fscontext.RefFSContextFactory");
env.put(Context.PROVIDER_URL,
"file:/C:/Program Files/IBM/MQSeries/Java/lib");
jndiContext = new InitialContext(env);
} catch (NamingException e) {
System.out.println("Could not create JNDI API " +
"context: " + e.toString());
e.printStackTrace();
System.exit(1);
}1) How to get the JNDI server running and registering our topic there?
Unlike RMI Naming server/registry, JNDI is a standard API for naming services. Hence it is not designed as a server listening on a port. I understand the File System based name space. The bindings of key-value is maintained in .bindings file in the place you specify as a PROVIDER_URL. Both publisher and subscriber has to refer this name space. This is how you start registering and retrieving MQ objects.
3) Who are providers? There are JNDI provider and IBMMQSeries provider. What is to be used? Can they both be used?
Providers are vendors who have implemented javax.naming.Spi package. The default provider you get from Sun is one reference implementation. It is "com.sun.jndi.fscontext.RefFSContextFactory". There is no IBM MQSeries provider. The same "com.sun.jndi.fscontext.RefFSContextFactory" is only supplied with MQSeries also.
I don't know the answers for questions 2 and 4. I shall post it as soon as I understand.
Those of you who read this, if you find deviation from righteouness, please correct.
Thanks/Regards,
Rajesh -
Name and Directory Service (Soap, Rest)
Hello everyone,
i would like to implement a directory service for Web-services (like UDDI) that supports SOAP and Rest. My question is can i use JNDI to do that. When yes, muss I write a Plug in for JNDI SPI to support this Protocols(SOAP, Rest). When no, what would you recommend me.
Thank you very much
Rodolfooops,thought i was replying to the PgP question:)
I think you should be able to achieve this via adapter module but i m not really sure how exactly it will be done .
Thanks
Aamir
Edited by: Aamir Suhail on Jul 28, 2009 1:42 PM -
Changing env-entry after deployment
Hi,
I was wondering how I can change the value of an env-entry after deployment? Do I have to change the value in the ejb-jar.xml, redeploy the application, or is there a utility I can use?
thanks
SteveOkay gentlemen, I dug around and couldn't find anything on this concept of defining an env-entry after deployment using Sun Java System Application Server 8.1 - so I just came up with my own hack. Thought I'd share it in case others have the same question and can't find the answer.
Just to restate the problem: In SJAS you can't seem to define an environment entry that you can just look up via JNDI (you can do this in Tomcat pretty easy though using the context.xml file and an env-entry like syntax) - the benefit of this being of course that you can easily define deployment-time variables which a system administrator can set based on his setup. There seems to be no way to do this is SJAS 8.1
As a workaround, you can create your own custom JNDI resource which will expose the properties that you set in the Admin Console as a simple java.util.Map that you can use from your app.
Here's the blow by blow:
2. Create a JNDIProperties object that implements java.util.Map but does NOT implement java.io.Serializable:
package helpers.jndi;
import java.util.Collection;
import java.util.Map;
import java.util.Set;
public final class JNDIProperties implements Map {
private Map map;
public JNDIProperties(Map aMap) { map = aMap; }
public boolean containsKey(Object key) { return map.containsKey(key); }
public void clear() { map.clear(); }
public Object get(Object key) { return map.get(key); }
public boolean containsValue(Object value) { return map.containsValue(value); }
public Set entrySet() { return map.entrySet(); }
public boolean isEmpty() { return map.isEmpty(); }
public Set keySet() { return map.keySet(); }
public Object put(Object key, Object value) { return map.put(key, value); }
public void putAll(Map t) { map.putAll(t); }
public Object remove(Object key) { return map.remove(key); }
public int size() { return map.size(); }
public Collection values() { return map.values(); }
}2. Create an object that implements javax.naming.spi.ObjectFactory and returns an instance of JNDIProperties containing the properties defined in the container:
package helpers.jndi;
import java.util.Enumeration;
import java.util.Hashtable;
import java.util.Map;
import javax.naming.Context;
import javax.naming.Name;
import javax.naming.RefAddr;
import javax.naming.Reference;
import javax.naming.spi.ObjectFactory;
public class PropertyFactory implements ObjectFactory {
public Object getObjectInstance(Object obj, Name name, Context nameCtx, Hashtable environment) throws Exception {
Map myMap = new Hashtable();
Reference myReference = (Reference)obj;
Enumeration myEnumeration = myReference.getAll();
while (myEnumeration.hasMoreElements()) {
RefAddr myRefAddr = (RefAddr)myEnumeration.nextElement();
myMap.put(myRefAddr.getType(), myRefAddr.getContent());
JNDIProperties myJNDIProperties = new JNDIProperties(myMap);
return myJNDIProperties;
}3. Build this and copy the jar to $SJAS_HOME/domains/domain1/lib/ext/ (or other appropriate folder for your setup), then restart the app server to get to load the jar.
4. Go to the admin console and go to Resources -> JNDI -> Custom Resources -> New. Give it a sensible JNDI name (I'll use "testproperties" in this example), enter java.util.Map as the resource type and the name of your factory class for the "factory class" field, e.g. "helpers.jndi.PropertyFactory". Below that under "Additional Properties", add in each of the properties that you want to expose, for example enter a property named "testproperty1" with the value of "my test".
5. You can now get a java.util.Map that contains the properties that you set for your custom JNDI resource by doing something like the following (example in JSP):
<%
Context myContext = new InitialContext();
Context myEnvContext = (Context)myContext.lookup("java:comp/env");
Map myMap = (Map)myEnvContext.lookup("testproperties");
%>
<%=myMap.get("testproperty1")%>Output is:
my testNOTE: If this sounds convoluted - I agree, it is. If anyone's got a better idea, please post it; as I could not find another solution to this seemingly simple problem. -
A question about a method with generic bounded type parameter
Hello everybody,
Sorry, if I ask a question which seems basic, but
I'm new to generic types. My problem is about a method
with a bounded type parameter. Consider the following
situation:
abstract class A{ }
class B extends A{ }
abstract class C
public abstract <T extends A> T someMethod();
public class Test extends C
public <T extends A> T someMethod()
return new B();
}What I want to do inside the method someMethod in the class Test, is to
return an instance of the class B.
Normally, I'm supposed to be able to do that, because an instance of
B is also an instance of A (because B extends A).
However I cannot compile this program, and here is the error message:
Test.java:16: incompatible types
found : B
required: T
return new B();
^
1 errorany idea?
many thanks,Hello again,
First of all, thank you very much for all the answers. After I posted the comment, I worked on the program
and I understood that in fact, as spoon_ says the only returned value can be null.
I'm agree that I asked you a very strange (and a bit stupid) question. Actually, during recent months,
I have been working with cryptography API Core in Java. I understood that there are classes and
interfaces for defining keys and key factories specification, such as KeySpec (interface) and
KeyFactorySpi (abstract class). I wanted to have some experience with these classes in order to
understand them better. So I created a class implementing the interface KeySpec, following by a
corresponding Key subclass (with some XOR algorithm that I defined myself) and everything was
compiled (JDK 1.6) and worked perfectly. Except that, when I wanted to implement a factory spi
for my classes, I saw for the first time this strange method header:
protected abstract <T extends KeySpec> T engineGetKeySpec
(Key key, Class<T> keySpec) throws InvalidKeySpecExceptionThat's why yesterday, I gave you a similar example with the classes A, B, ...
in order to not to open a complicated security discussion but just to explain the ambiguous
part for me, that is, the use of T generic parameter.
The abstract class KeyFactorySpi was defined by Sun Microsystem, in order to give to security
providers, the possibility to implement cryptography services and algorithms according to a given
RFC (or whatever technical document). The methods in this class are invoked inside the
KeyFactory class (If you have installed the JDK sources provided by Sun, You can
verify this, by looking the source code of the KeyFactory class.) So here the T parameter is a
key specification, that is, a class that implements the interface KeySpec and this class is often
defined by the provider and not Sun.
stefan.schulz wrote:
>
If you define the method to return some bound T that extends A, you cannot
return a B, because T would be declared externally at invocation time.
The definition of T as is does not make sense at all.>
He is absolutely right about that, but the problem is, as I said, here we are
talking about the implementation and not the invocation. The implementation is done
by the provider whereas the invocation is done by Sun in the class KeyFactory.
So there are completely separated.
Therefore I wonder, how a provider can finally impelment this method??
Besides, dannyyates wrote
>
Find whoever wrote the signature and shoot them. Then rewrite their code.
Actually, before you shoot them, ask them what they were trying to achieve that
is different from my first suggestion!
>
As I said, I didn't choose this method header and I'm completely agree
with your suggestion, the following method header will do the job very well
protected abstract KeySpec engineGetKeySpec (Key key, KeySpec key_spec)
throws InvalidKeySpecException and personally I don't see any interest in using a generic bounded parameter T
in this method header definition.
Once agin, thanks a lot for the answers.
Maybe you are looking for
-
Ipod connection issues with itunes
i know, i am the one-thousandth person to write in about a connection issue, but i just bought a 8gb nano. my pc is recognizing the ipod, but itunes does not automatically start. instead, if i manually try to start up itunes, it either doesn't start
-
downloaded the update, tried installing it on my phone, something messed up and I lost everything on it and now it's going through the "restore" phase
-
How do i get firefox to not be in full screen mode without a mouse or keyboard?
for some reason Firefox switched to full screen mode and i can't get out of it. I'm using Firefox on a tablet PC running windows 8.1 so using F11 or a mouse is not an option. at least i assume it's full screen mode. i can't see my bookmarks bar, my a
-
Final Cut Pro finished project looks good in FC but when I export The slugs appear as a Red screen any ideas?
-
Merge two differents tables in one new structure
Hello guys, How can I merge two differents tables in one new structure (workarea) dynamically? For example, merge MARA and MARC in a new structure that contains all fields from MARA and all fields from MARC. In this case, it isn't necessary that iden