Hi, I am still facing lots of issues in deploying JUDDIV3 with JBoss 7. Are there any plans of updating the user guide of JUDDIV3 for its deployment in JBoss 7.
-Thanks On Fri, Jun 15, 2012 at 7:06 PM, Kurt T Stam <[email protected]> wrote: > > In my prev email I sent the details when I was using derby database. > but the persisentence.xml you attached references the mysql dialect, just > wanted to point that out. > > > > I will be good if I could use Juddi on Jboss with either derby or Mysql. > You can use whatever database you want; jUDDI uses JPA. > > > http://people.apache.org/~kstam/releases/juddi-3.0.0.beta/juddi-jboss-4.2.3.GA.tgz > > uses Derby, just use is to compare the persistence.xml. Don't use the > files with the latest jUDDI since we may have added persistent classes since > > Really though all the info you need should be in docs: > > http://juddi.apache.org/docs/3.x/userguide/html/chap-database_setup.html > > The stack trace is too short to be of any value, but please check your > database settings. > > --Kurt > > > On 6/15/12 9:25 AM, tech evaluator wrote: > > Kurt, > > I have tried to deploy juddi.war in jboss by using two approaches. > In one approach I am using derby database and in another I am trying to > migrate to MySql. > In my prev email I sent the details when I was using derby database. > I hope I am not confusing you. > I will be good if I could use Juddi on Jboss with either derby or Mysql. > > > Many thanks for trying to help me... > > Approach1: (MySql database) > When I am using MySql as database. then I am getting the attached > exception logs. > > Exception: > Caused by: java.sql.SQLException: Field 'id' doesn't have a default value > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4098) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4030) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2490) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2677) > at > com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2134) > at > com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2434 > > > > On Fri, Jun 15, 2012 at 6:34 PM, Kurt T Stam <[email protected]> wrote: > >> Cool, >> >> I would use mysql (a 'real' database), which is the dialect you already >> specify in the persistence.xml: >> >> <property name="hibernate.dialect" >> value="org.hibernate.dialect.MySQLDialect"/> >> >> Make sure to create the juddiv3 database in MySQL, hibernate will create >> the tables >> >> <property name="hibernate.hbm2ddl.auto" value="update"/> >> >> You can check some of the settings here: >> >> http://juddi.apache.org/docs/3.x/userguide/html/chap-database_setup.html#sect-switch_to_mysql >> >> --Kurt >> >> >> On 6/15/12 8:51 AM, tech evaluator wrote: >> >> Please ignore my prev email. >> Thanks I am now able to download file. The juddi war kinda got deployed >> on JBoss but I am facing issue in creation of database. >> >> a) I made the necessary changes in my persistence.xml (File attached) >> b) I added the new datasource and driver in standalone.xml (File >> attached) >> c) I also changed my web.xml as provided in jboss-5.1.0.GA ( File >> attached) >> >> Should I use derby database. Please refer my standalone.xml >> I am also sending exception logs >> If you can provide any help. >> >> >> On Thu, Jun 14, 2012 at 8:40 PM, Kurt T Stam <[email protected]> wrote: >> >>> Hmm seems to work ok for me, but I put a copy up here for you >>> >>> http://dl.dropbox.com/u/2743585/jboss-5.1.0.GA.tgz >>> >>> Hopefully that works better for you, >>> >>> --Kurt >>> >>> >>> On 6/14/12 3:04 AM, tech evaluator wrote: >>> >>> Hi, >>> >>> I am not able to download the file. >>> I think the link is broken. Every time I am able to download only 17 MB >>> file. >>> Could you please check. >>> Thanks in advance. >>> >>> On Wed, Jun 13, 2012 at 9:41 PM, Kurt T Stam <[email protected]>wrote: >>> >>>> >>>> http://people.apache.org/~kstam/releases/juddi-3.0.0/jboss-5.1.0.GA.tgz >>>> >>>> Check out the juddiv3.war in the deploy directory. This is for >>>> jboss-5.1, but it may put you on the right track with the persistence.xml >>>> configuration. >>>> >>>> Cheers, >>>> >>>> --Kurt >>>> >>>> >>>> On 6/11/12 9:21 AM, tech evaluator wrote: >>>> >>>> Hi, >>>> >>>> UseCase: JUDDI deployment in JBOSS 7.1 >>>> >>>> I am able to resove the earlier exceptions related to ClassLoading, >>>> >>>> Now I am getting the following exception while deploying JUDDI.war >>>> version 3.1.3 on JBoss 7.1 >>>> My JBoss-deployment-structure.xml and persistence.xml is attached >>>> I think I need to make some changes in persistence.xml. >>>> The documentation provided in jUDDI userguide ( Chapter 12 Deploying >>>> to JBoss 6.0.0.GA ) is not applicable at all for new version of JBoss. >>>> I need help on section 12.4. Configure Datasource for JBoss 7.1 >>>> >>>> >>>> Exception Logs: >>>> >>>> >>>> >>>> 17:34:15,064 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA >>>> 17:34:15,204 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA >>>> 17:34:15,235 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final >>>> "Brontes" starting >>>> 17:34:16,001 INFO [org.xnio] XNIO Version 3.0.3.GA >>>> 17:34:16,001 INFO [org.jboss.as.server] JBAS015888: Creating http >>>> management service using socket-binding (management-http) >>>> 17:34:16,017 INFO [org.xnio.nio] XNIO NIO Implementation Version >>>> 3.0.3.GA >>>> 17:34:16,032 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA >>>> 17:34:16,048 INFO [org.jboss.as.logging] JBAS011502: Removing >>>> bootstrap log handlers >>>> 17:34:16,064 INFO [org.jboss.as.osgi] JBAS011940: Activating OSGi >>>> Subsystem >>>> 17:34:16,064 INFO [org.jboss.as.connector.subsystems.datasources] >>>> JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version >>>> 1.3) >>>> 17:34:16,360 INFO [org.jboss.as.naming] (MSC service thread 1-1) >>>> JBAS011802: Starting Naming Service >>>> 17:34:16,392 INFO [org.jboss.as.security] (MSC service thread 1-2) >>>> JBAS013100: Current PicketBox version=4.0.7.Final >>>> 17:34:16,470 INFO [org.jboss.as.mail.extension] (MSC service thread >>>> 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default] >>>> 17:34:16,579 INFO [org.apache.coyote.http11.Http11Protocol] (MSC >>>> service thread 1-4) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080 >>>> 17:34:16,751 INFO >>>> [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread >>>> 1-1) JBoss Web Services - Stack CXF Server 4.0. >>>> 2.GA >>>> 17:34:16,860 INFO [org.jboss.as.server.deployment.scanner] (MSC >>>> service thread 1-4) JBAS015012: Started FileSystemDeploymentService for dir >>>> ectory C:\Softwares\JBoss\jboss-as-7.1.1.Final\standalone\deployments >>>> 17:34:16,860 INFO [org.jboss.as.remoting] (MSC service thread 1-4) >>>> JBAS017100: Listening on /127.0.0.1:4447 >>>> 17:34:16,860 INFO [org.jboss.as.remoting] (MSC service thread 1-3) >>>> JBAS017100: Listening on /127.0.0.1:9999 >>>> 17:34:16,876 INFO [org.jboss.as.server.deployment.scanner] >>>> (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment >>>> judd >>>> i.war >>>> 17:34:17,126 INFO [org.jboss.as.connector.subsystems.datasources] (MSC >>>> service thread 1-2) JBAS010400: Bound data source [java:jboss/dataso >>>> urces/ExampleDS] >>>> 17:34:17,142 INFO [org.jboss.as.server.deployment] (MSC service thread >>>> 1-1) JBAS015876: Starting deployment of "juddi.war" >>>> 17:34:18,235 INFO [org.jboss.as.jpa] (MSC service thread 1-2) >>>> JBAS011401: Read persistence.xml for juddiDatabase >>>> 17:34:18,329 ERROR [org.jboss.msc.service.fail] (MSC service thread >>>> 1-3) MSC00001: Failed to start service jboss.deployment.unit."juddi.war" >>>> .INSTALL: org.jboss.msc.service.StartException in service >>>> jboss.deployment.unit."juddi.war".INSTALL: Failed to process phase INSTALL >>>> of depl >>>> oyment "juddi.war" >>>> at >>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) >>>> [jboss-as-server-7.1.1.Final >>>> .jar:7.1.1.Final] >>>> at >>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) >>>> [jboss-msc-1.0.2.GA.jar:1.0.2 >>>> .GA] >>>> at >>>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) >>>> [jboss-msc-1.0.2.GA.jar:1.0.2.GA] >>>> at >>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >>>> [rt.jar:1.6.0_22] >>>> at >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>>> [rt.jar:1.6.0_22] >>>> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] >>>> Caused by: javax.persistence.PersistenceException: JBAS011466: >>>> PersistenceProvider >>>> 'org.apache.openjpa.persistence.PersistenceProviderImpl' >>>> not found >>>> at >>>> org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.lookupProvider(PersistenceUnitDeploymentProcessor.java:555) >>>> at >>>> org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deployPersistenceUnit(PersistenceUnitDeploymentProcessor.java:295) >>>> at >>>> org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.addPuService(PersistenceUnitDeploymentProcessor.java:258) >>>> at >>>> org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.handleWarDeployment(PersistenceUnitDeploymentProcessor.java:194) >>>> at >>>> org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deploy(PersistenceUnitDeploymentProcessor.java:118) >>>> at >>>> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) >>>> [jboss-as-server-7.1.1.Final >>>> .jar:7.1.1.Final] >>>> ... 5 more >>>> >>>> 17:34:18,392 INFO [org.jboss.as.server] (DeploymentScanner-threads - >>>> 2) JBAS015870: Deploy of deployment "juddi.war" was rolled back with f >>>> ailure message {"JBAS014671: Failed services" => >>>> {"jboss.deployment.unit.\"juddi.war\".INSTALL" => >>>> "org.jboss.msc.service.StartException in >>>> service jboss.deployment.unit.\"juddi.war\".INSTALL: Failed to process >>>> phase INSTALL of deployment \"juddi.war\""}} >>>> 17:34:19,095 INFO [org.jboss.as.server.deployment] (MSC service thread >>>> 1-4) JBAS015877: Stopped deployment juddi.war in 703ms >>>> 17:34:19,110 INFO [org.jboss.as.controller] (DeploymentScanner-threads >>>> - 2) JBAS014774: Service status report >>>> JBAS014777: Services which failed to start: service >>>> jboss.deployment.unit."juddi.war".INSTALL: >>>> org.jboss.msc.service.StartException i >>>> n service jboss.deployment.unit."juddi.war".INSTALL: Failed to process >>>> phase INSTALL of deployment "juddi.war" >>>> >>>> 17:34:19,110 ERROR [org.jboss.as.server.deployment.scanner] >>>> (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed >>>> and was >>>> rolled back. Steps that failed:" => {"Operation step-2" => >>>> {"JBAS014671: Failed services" => >>>> {"jboss.deployment.unit.\"juddi.war\".INSTALL" >>>> => "org.jboss.msc.service.StartException in service >>>> jboss.deployment.unit.\"juddi.war\".INSTALL: Failed to process phase >>>> INSTALL of deploym >>>> ent \"juddi.war\""}}}} >>>> >>>> >>>> >>>> >>> >>> >> >> > >
