Bug 778597 (SOA-1070) - jUDDI does not work with MS-SQL
Summary: jUDDI does not work with MS-SQL
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1070
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.3 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP02
Assignee: Jervis Liu
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On: SOA-544
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-11 11:09 UTC by Jervis Liu
Modified: 2013-11-07 22:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-09-09 17:19:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1070 0 None None None Never

Description Jervis Liu 2008-12-11 11:09:45 UTC
Date of First Response: 2008-12-16 05:01:00
project_key: SOA

jUDDI does not work with MS-SQL, I got following exceptions:

2008-12-11 16:11:23,031 WARN  [org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle] Unexpected exception caught while initialisation
java.lang.NullPointerException
	at org.apache.ws.scout.registry.infomodel.ClassificationImpl.setClassificationScheme(ClassificationImpl.java:103)
	at org.apache.ws.scout.registry.LifeCycleManagerImpl.createClassification(LifeCycleManagerImpl.java:198)
	at org.apache.ws.scout.registry.LifeCycleManagerImpl.createClassification(LifeCycleManagerImpl.java:210)
	at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findService(JAXRRegistryImpl.java:425)
	at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.registerEPR(JAXRRegistryImpl.java:140)
	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:585)
	at org.jboss.internal.soa.esb.services.registry.RegistryService$1.invoke(RegistryService.java:61)
	at $Proxy36.registerEPR(Unknown Source)
	at org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor.registerEPR(InVMRegistryInterceptor.java:51)
	at org.jboss.soa.esb.services.registry.RegistryFactory$HeadRegistryInterceptor.registerEPR(RegistryFactory.java:242)
	at org.jboss.soa.esb.listeners.RegistryUtil.register(RegistryUtil.java:143)
	at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:209)
	at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:134)
	at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:105)
	at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:62)
	at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:105)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
	at $Proxy0.start(Unknown Source)
	at org.jboss.system.ServiceController.start(ServiceController.java:417)
	at org.jboss.system.ServiceController.start(ServiceController.java:435)
	at org.jboss.system.ServiceController.start(ServiceController.java:435)
	at org.jboss.system.ServiceController.start(ServiceController.java:435)
	at org.jboss.system.ServiceController.start(ServiceController.java:435)
	at org.jboss.system.ServiceController.start(ServiceController.java:435)
	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy4.start(Unknown Source)
	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)

BTW, I already done following changes :
in deploy\juddi-service.sar\META-INF\ddl: 
1. change ACCESS_POINT_URL VARCHAR(50) to ACCESS_POINT_URL VARCHAR(2000)
2. change CREATED TIMESTAMP NOT NULL, LAST_USED TIMESTAMP NOT NULL to CREATED DATETIME NOT NULL, LAST_USED DATETIME NOT NULL

in deploy\juddi-service.sar\META-INF\jboss-service.xml, set CreateOnStart and DropOnStart to true.

Comment 2 Mark Little 2008-12-13 22:24:49 UTC
Link: Added: This issue depends SOA-544


Comment 3 Mark Little 2008-12-13 22:25:14 UTC
Link: Added: This issue depends JBESB-1721


Comment 4 tcunning 2008-12-16 10:00:59 UTC
Link: Added: This issue duplicates SOA-818


Comment 5 tcunning 2008-12-16 10:01:00 UTC
Needs the org.jboss.soa.esb:category TModel

Comment 6 Jervis Liu 2008-12-17 15:40:48 UTC
I reopen SOA-1070 as I do not think this issue is same as SOA-818. This issue is MS-SQL specific, juddi 2.0 rc5 does not ship with scripts to create and populate juddi tables for MS-SQL, we have to provide these scripts by ourself. 

Comment 7 Jervis Liu 2008-12-22 09:43:05 UTC
Link: Added: This issue depends JBESB-2241


Comment 8 tcunning 2009-01-12 04:52:45 UTC
Should be resolved in JBESB-2241, will be seen in next ESB merge -> SOA-P.

Comment 9 Kevin Conner 2009-01-23 16:25:23 UTC
Link: Removed: This issue depends JBESB-1721 


Comment 10 Kevin Conner 2009-01-23 16:28:53 UTC
Link: Added: This issue depends JBESB-2308


Comment 11 Dana Mison 2009-08-19 09:17:59 UTC
added to 4.3.CP02 release notes as resolved:

JBESB-2241 - jUDDI database scripts for Microsoft SQL Server are now included.


Note You need to log in before you can comment on or make changes to this bug.