I get the same thing pretty much every time I redeploy with Orion
Application Server.
Any idea what causes this? Is there any way to stop it?
Thanks
-Clay
> I am running OJB 1.0 with JBoss 3.2.5.
>
> On *occasional* redeployments of my EAR file (with nested Jars and Wars)
> I will get a nasty Cl
Hi,
I am using the ODMG API of OJB rc7 -
I have an m:n non-decomposed mapping defined between
two classes - say A and B. So an object A has a
collection of B's and vice-versa.
I have performed the following steps:
* I create two objects A, A1 and A2, that are stored
to the database - the database
That's a good idea about trying a modified version of commons-lang. However, I am not
sure what they will be able to do about it since they are using ObjectInputStream to
do the serialization, and that is Sun's code. Either way, I will see if there is a
workaround.
On the other hand -- why is O
Any ideas on this? I tried implementing all my transactin in ODMG and
had the same problem...
Thanks
-Clay
Clay Mitchell wrote:
Ok, maybe I don't understand exactly how this all works, but here is
what's going on.
I've posted the 3 relevant class-descriptors below. There are two source
tables
Clute, Andrew wrote:
I am wondering if it has something to do with the fact that
SerilizationUtils uses ObjectInputStream to serialize/desearlize the
objects, and ObjectInputStream on the deserialization does a
Class.forName() to create the new object -- which in the J2EE
classloader world can caus
I am wondering if it has something to do with the fact that
SerilizationUtils uses ObjectInputStream to serialize/desearlize the
objects, and ObjectInputStream on the deserialization does a
Class.forName() to create the new object -- which in the J2EE
classloader world can cause problems. I think t
> So, now I need to figure out why this is happening. Something thing
> looks weird for the after-serilization version after redploying, since
> the url for that class is null. Not sure where it is loading it from, or
> why it has a stored copy of it.
>
I must admit that I don't have a clue...
Did
Well, I have narrowed the issue down further, but still do not have a
solution yet. In ConnectionRepository.getAllDescriptor(), the
JdbcConnectionDescriptor's that are in the current repository are cloned
(seralized) into another list and returned. I made the guess (and I was
right) that when this
Just for giggles, I changed my EAR to use the Application.xml file to
denote the dependant jar files, and took it out of the Manifest file for
my Ejb jar, and it still is causing the issue!
Ughh. Might be time to post this to the Jboss forums -- but they are not
nearly as helpful! :)
-Andrew
I don't fill out the application.xml entries, since I Thought it was an
either-or situation (either Class-Path in the manifest file, or entries
in Application.xml)
-Original Message-
From: Armin Waibel [mailto:[EMAIL PROTECTED]
Sent: Friday, August 13, 2004 3:18 PM
To: OJB Users List
S
Clute, Andrew wrote:
Upgrading to the newest versions of the lib files for OJB did not fix
the problem.
I wish there was someway I could figure out what was keeping the
reference to the previous classes around that would conflict with the
new classloader. Ugh!
last-ditch attempt ;-)
Did you check t
Clute, Andrew wrote:
Ahh, I don't think that is the case, since my Class-Path setting is
dynamically generated when I produce the EAR by taking all of the jars
in my lib directory and adding it to that setting.
Now, I did not update my commons-* jar file for 1.0 -- and you are
saying that there was
Upgrading to the newest versions of the lib files for OJB did not fix
the problem.
I wish there was someway I could figure out what was keeping the
reference to the previous classes around that would conflict with the
new classloader. Ugh!
-Andrew
-Original Message-
From: Clute, Andre
Ahh, I don't think that is the case, since my Class-Path setting is
dynamically generated when I produce the EAR by taking all of the jars
in my lib directory and adding it to that setting.
Now, I did not update my commons-* jar file for 1.0 -- and you are
saying that there was some upgrades? I wo
Clute, Andrew wrote:
Armin,
Could you clarify for me what you mean by "I think that some jar files
changed between rc6 and 1.0".
sorry, my bad English ;-)
I mean the names of some jars are changed, e.g.
commons-collections-2.1.1.jar
instead of commons-collections.jar.
Maybe you have a jar in class
Armin,
Could you clarify for me what you mean by "I think that some jar files
changed between rc6 and 1.0". Are you saying that dependencies were
removed that rc6 had that 1.0 doesn't need? My Class-Path entry from my
EJB jar file contains the following entries:
Manifest-Version: 1.0
Ant-Version:
Clute, Andrew wrote:
I am almost certain that is a ClassLoader issue.
Yes, my deployment looks almost the exact same as Stephen's (in fact, I
chimed in when he first posted that stating that is already how I was
doing it, and it worked fine).
Now, something I forgot to mention: We have only start
I am almost certain that is a ClassLoader issue.
Yes, my deployment looks almost the exact same as Stephen's (in fact, I
chimed in when he first posted that stating that is already how I was
doing it, and it worked fine).
Now, something I forgot to mention: We have only started seeing this
since
Hi Andrew,
think this is a ClassLoader problem. Maybe ojb.jar itself or one of the
jars OJB depends on is not correctly reloaded.
Did you follow the instructions made by Stephen Ting
http://db.apache.org/ojb/docu/guides/deployment.html#Packing+an+.ear+file
regards,
Armin
Clute, Andrew wrote:
I am
I am running OJB 1.0 with JBoss 3.2.5.
On *occasional* redeployments of my EAR file (with nested Jars and Wars)
I will get a nasty ClassCastException that is only fixable by restarting
Jboss. This happens in the MetadataManager.buildDefaultKey() method.
The top part of the stack trace is posted b
Joose Vettenranta wrote:
I solved it so, that I made 3 classes
abstarct A
B extends A
C extends A
and in code I call B or C not A. But still, B and C can't use same
table name. Oh well, can't have everything. Problem is that now I
have to change every class to use C instead of using A or B. Wha
Hi,
it seems that when I try to get Child it also get's SuperChild.. even
though I haven't said that it should get superchild. All I want is
to get just Child not superCHild.. Perhaps it's not possible to get
like this?
You'll need to add a field called 'ojbConcreteClass' so that OJB knows
Joose Vettenranta wrote:
Hi,
it seems that when I try to get Child it also get's SuperChild.. even
though I haven't said that it should get superchild. All I want is to
get just Child not superCHild.. Perhaps it's not possible to get like
this?
You'll need to add a field called 'ojbConcreteCl
Hi,
it seems that when I try to get Child it also get's SuperChild.. even
though I haven't said that it should get superchild. All I want is to
get just Child not superCHild.. Perhaps it's not possible to get like
this?
How about if I do Child interface
and SuperChild implements Child
and Ch
Hi,
I actually solved that JDO, problem but now my problems continue...
I made that superchild and child has same table name.. superchild uses
different connection than connection using child object.
But when I try to fetch Child, it actually tries to get SuperChild and
not Child -> SQL-error.
Cyril Ledru wrote:
Thanks again for your answer.
I tried to delay the threads but the result are almost the same.
Do you use different delay times for each thread? If all threads wait
e.g 100ms it doesn't change anything, because they will access at same
time again.
When i told you about the "2
Joose Vettenranta wrote:
I did this and it did not work.
I get this:
java.lang.NullPointerException
...
java.lang.VerifyError: Class net.vettenranta.super.Child overrides
final method jdoReplaceFlags.()V
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Cla
You have to specify the extent-class as the first sub-tag of
class-descriptor (see
http://db.apache.org/ojb/docu/guides/repository.html#class-descriptor
for details).
Also, you have to duplicate all fields/references/collections from
Child in SuperChild, currently they are not automatically
Thanks again for your answer.
I tried to delay the threads but the result are almost the same.
When i told you about the "200ms" it the average time took to retreive
all employees in the db when the datas are in the cache.
Here, it seems like the datas aren't in a cache...
Do you know which class
Cyril Ledru wrote:
Thanks for you answer.
> I think your test case has a few drawbacks and do not reflect a
> production scenario.
Our clients are asking our datas every 3 sec through a web service. So
this case'll occure a lot i think.
ok, but your test doesn't reflect this. Your test starts
Thanks for you answer.
> I think your test case has a few drawbacks and do not reflect a
> production scenario.
Our clients are asking our datas every 3 sec through a web service. So
this case'll occure a lot i think.
I tried to launch a first dummy call before the others. It reduce a
little the
Thank you very much Armin.
the third solution is the right one, the two others dont change any thing.
- Original Message -
From: "Armin Waibel" <[EMAIL PROTECTED]>
To: "OJB Users List" <[EMAIL PROTECTED]>
Sent: Friday, August 13, 2004 10:58 AM
Subject: Re: org.apache.ojb.broker.Persiste
Hi Cyril,
I think your test case has a few drawbacks and do not reflect a
production scenario.
First time PBF was used OJB parse and create all metadata objects (OJB
startup phase), this is time consuming and only occur one time in OJB
runtime. So before you start the LoadThread classes you sho
Hi,
I there a problem with my mail ? Did i forget something ? I am not clear ?
Please, tell me, i really need this info.
Cyril Ledru wrote:
Hi all,
This is my problem : I have an application which launch several threads.
In each thread, there is a call to getCollectionByQuery.
Here is the code of
Hi,
never used mysql (so take this with a pinch of salt ;-)), but it seems
that by default reconnected connections set to 'read-only' mode. Did you
try to set failOverReadOnly=false
http://dev.mysql.com/doc/connector/j/en/index.html#id2423002
In jdbc-connection-descriptor you should set useAutoC
Thomas Dudziak wrote:
The fix should be a simple change of the compile-classpath at the
beginning of the build.xml of the ojb-blank project to:
[..]
That works for me, thanks.
--
Christian
-
To unsubscribe, e-mail: [EMAIL PROTECTE
I reproduced the exeption by stopping and restarting the sql server.
the probleme is that OJB dont auto-Reconnect in spite of putting in my
repository.xml in the connection declaration
dbalias="//localhost/MyDB?autoReconnect=true"
How can i tell to OJb to auto reconnect?
- Original Messag
Hi all,
I have a SQL probleme, it seems like the connection died after some time, it happen
only for the OJB connection, because I have another connection that use classic java
connection managed with a connection pool, this kind of connection dont throw any
exception at the same time the ojb c
38 matches
Mail list logo
