Hi Tom,
I have no idea about that error.. But on jboss I would use the native
jpa provider (Hibernate, not OpenJPA) and the native webserver stack.
You should take a look at the server/default/deploy/juddiv3.war in this
archive:
http://people.apache.org/~kstam/appserver/juddi-on-jboss-6.0.0.CR1.tgz
and see that the war is very light. Also when using hibernate you can
use an orm.xml file to overwrite the database settings such as field
lengths. This maybe something you'd want to do for you first issue.
Please let us know if using the light-weight war fixes your second
issue. See also
http://juddi.apache.org/docs/3.0/userguide/html/chap-deployjboss.html,
for how to switch to using CXF on JBoss.
In the near future we'd like to add other deployment packages for some
popular appservers: http://issues.apache.org/jira/browse/JUDDI-480
--Kurt
On 5/18/11 9:50 AM, Cleal, Thomas A wrote:
We are using 3.0.4.
We are using Oracle as the back end DB so it created it as a CLOB with
a size of 4000.
I was looking through the logs and also have this error:
2011-05-17 19:05:14,898 ERROR
[org.jboss.kernel.plugins.dependency.AbstractKernelController] (main)
Error installing to Start:
name=persistence.unit:unitName=#juddiDatabase state=Create
java.lang.AbstractMethodError:
org.jboss.jpa.deployment.PersistenceUnitInfoImpl.getValidationMode()Ljavax/persistence/ValidationMode;
at
org.apache.openjpa.persistence.PersistenceUnitInfoImpl.toOpenJPAProperties(PersistenceUnitInfoImpl.java:477)
at
org.apache.openjpa.persistence.PersistenceProductDerivation.load(PersistenceProductDerivation.java:318)
at
org.apache.openjpa.persistence.PersistenceProviderImpl.createContainerEntityManagerFactory(PersistenceProviderImpl.java:164)
at
org.apache.openjpa.persistence.PersistenceProviderImpl.createContainerEntityManagerFactory(PersistenceProviderImpl.java:66)
at
org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
Thanks for the help,
Tom
*From:*Kurt T Stam [mailto:[email protected]]
*Sent:* Tuesday, May 17, 2011 1:39 PM
*To:* [email protected]
*Subject:* Re: Where is this coming from
Hi Tom,
It looks like the maximum size of the subscriptionFilter field is set
to 4000 bytes and one of your Filters is longer. You should be able to
alter your database and make your
j3_subscription.subscription_filter | text |
field larger.
BTW in juddi-3.0.4 and newer this seems to be set to 65636, what
version of juddi are you using?
--Kurt
On 5/17/11 3:00 PM, Cleal, Thomas A wrote:
I am seeing the below error message in the log files. I'm not sure
what to do to get rid of it.
Is it really anything to worry about?
I am running juddi v3 in JBoss AS 5.1
[STDERR] (Timer-1) 33458 juddiDatabase WARN [Timer-1]
openjpa.MetaData -
"org.apache.juddi.model.Subscription.subscriptionFilter" is being
mapped with a handler
that may not be able to store values over 4000 bytes/chars long.
Thanks
Tom
