13 Replies Latest reply on Jun 2, 2008 7:23 PM by Chris Laprun

    Deployment of JBoss Portal from sources

    hello All Newbie

      Hi,
      I was able to sucessfully build and deploy Jboss portal from the source.
      I am able to bring up the portal screen and login as admin or user.

      However, the problem is that though I can see all the tabs like Admin, Members etc, no information gets displayed. They are just blank pages.
      I did point the defaultDS to a different database than hypersonic.

      There are no errors that are getting displayed but I do see a series of following messages :
      15:36:37,593 WARN [LoadContexts] fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@
      de1c4<rs=org.hsqldb.jdbc.jdbcResultSet@10c51ef>
      15:36:37,593 WARN [LoadContexts] fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@
      49a7<rs=org.hsqldb.jdbc.jdbcResultSet@e5488e>

      Per some other thread in this forum, these can be completely ignored.

      any suggestions greatly appreciated on why data is not displayed within the portal ? I want some clues as to where should I concentrate in order to find the problem.

      my Env details:
      JBoss Portal version - 2.6.5
      Jboss App version - 4.2.2
      Windows OS

      Thanks.


        • 1. Re: Deployment of JBoss Portal from sources
          Prabhat Jha Master

          Can you paste your ds.xml file? The datasource name should be PortalDS.

          • 2. Re: Deployment of JBoss Portal from sources
            hello All Newbie

            Thanks for the quick response.
            Here is my portal-ds.xml file under deploy dir.


            <local-tx-datasource>

            <jndi-name>PortalDS</jndi-name>

            <connection-url>jdbc:sqlserver://servername:1433;databaseName=JBossPortal</connection-url>

            <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>

            <user-name>id</user-name>

            pass

            </local-tx-datasource>




            Do you think it is a problem with the data source configuration ?

            • 3. Re: Deployment of JBoss Portal from sources
              Prabhat Jha Master

              Do you see tables related to portal created in your database? This is what sample SQLServer descriptor look like. You should be able to see this file in build/output/jboss-portal-version/setup


              <local-tx-datasource>
              <jndi-name>PortalDS</jndi-name>
              <connection-url>jdbc:jtds:sqlserver://localhost:1433;tds=8.0;lastupdatecount
              =true</connection-url>
              <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
              <user-name>portal</user-name>
              portalpassword
              </local-tx-datasource>

              • 4. Re: Deployment of JBoss Portal from sources
                hello All Newbie

                We already have the JBoss portal schema created on sql server.

                I am trying to point my portal deployment to this existing database/tables.

                Please let me know if this approach is not correct.

                Also, are we required to use the jdts driver for SQL server?
                Does the username/password have to portal/portalpassword ?

                Please advise.

                Thanks.





                • 5. Re: Deployment of JBoss Portal from sources
                  Prabhat Jha Master

                  No, you can use any jdbc driver that works for you. If you are not getting any error related to DB then that means it is able to connect so I do not think this is connection error.

                  What I typically do is, I just create the database and let portal create tables etc when it starts for the first time. See if this way, you are able to connect or not. I can not think of anything else.

                  • 6. Re: Deployment of JBoss Portal from sources
                    hello All Newbie

                    Ok. I used other database server and the portal created its tables when it started for the first time. But my original problem is still there - when I go to http://localhost:8080/portal, and login as admin/admin, the tabs are there but there is no content displayed within the tabs. Eg - if I go to Admin tab, there is nothing displayed.

                    Am I missing some steps ? The log does not show any errors.
                    Suggestions appreciated.

                    Thanks.


                    • 7. Re: Deployment of JBoss Portal from sources
                      Chris Laprun Master

                      As per the reference manual, Portal is build from several different modules, most of which are not deployed by default. You can deploy everything that comes with the source distribution using:

                      ant deploy-all
                      in the build directory. Most modules can also be deployed separately.
                      For example, to deploy the wsrp module (assuming Portal's core is already deployed):
                      cd wsrp; ant deploy;


                      • 8. Re: Deployment of JBoss Portal from sources
                        Chris Laprun Master

                        Also, the module that needs to be deployed to see the administration interface is core-admin.

                        • 9. Re: Deployment of JBoss Portal from sources
                          hello All Newbie

                          Thanks for the response. Sorry, I missed the deploy-all part.
                          I did it. Worked fine except for the following exception :

                          10:43:47,125 ERROR [Scheduler$Listener] Invoke of the Schedulable MBean failed
                          javax.management.MBeanException
                          at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180)
                          at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
                          at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                          at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
                          at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                          at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
                          at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                          at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
                          at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                          at org.jboss.varia.scheduler.Scheduler$MBeanListener.handleNotification(Scheduler.java:1346)
                          at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
                          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                          at java.lang.reflect.Method.invoke(Method.java:597)
                          at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:153)
                          at $Proxy11.handleNotification(Unknown Source)
                          at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:257)
                          at javax.management.NotificationBroadcasterSupport$SendNotifJob.run(NotificationBroadcasterSupport.java:322)
                          at javax.management.NotificationBroadcasterSupport$1.execute(NotificationBroadcasterSupport.java:307)
                          at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:229)
                          at javax.management.timer.Timer.sendNotification(Timer.java:1234)
                          at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1203)
                          at javax.management.timer.TimerAlarmClock.run(Timer.java:1286)
                          at java.util.TimerThread.mainLoop(Timer.java:512)
                          at java.util.TimerThread.run(Timer.java:462)
                          Caused by: org.jboss.portal.portlet.InvokerUnavailableException: Problem getting service description for producer self,
                          please see the logs for more information.
                          at org.jboss.portal.wsrp.consumer.WSRPConsumerImpl.getPortlets(WSRPConsumerImpl.java:156)
                          at org.jboss.portal.portlet.federation.impl.FederatedPortletInvokerService.getPortlets(FederatedPortletInvokerSe
                          rvice.java:90)
                          at org.jboss.portal.core.management.PortletDiscoveryService.processPortletDiscovery(PortletDiscoveryService.java
                          :88)
                          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)
                          at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                          ... 22 more
                          Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
                          at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:424)
                          at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:67)
                          at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:161)
                          at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
                          at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:156)
                          at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:289)
                          at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:517)
                          at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:277)
                          at org.jboss.ws.core.jaxrpc.client.PortProxy.invoke(PortProxy.java:151)
                          at $Proxy373.getServiceDescription(Unknown Source)
                          at org.jboss.portal.wsrp.consumer.ProducerInfo.getUnmanagedServiceDescription(ProducerInfo.java:660)
                          at org.jboss.portal.wsrp.consumer.ProducerInfo.internalRefresh(ProducerInfo.java:322)
                          at org.jboss.portal.wsrp.consumer.ProducerInfo.detailedRefresh(ProducerInfo.java:273)
                          at org.jboss.portal.wsrp.consumer.ProducerInfo.refresh(ProducerInfo.java:268)
                          at org.jboss.portal.wsrp.consumer.ProducerInfo.getPortletMap(ProducerInfo.java:608)
                          at org.jboss.portal.wsrp.consumer.WSRPConsumerImpl.getPortlets(WSRPConsumerImpl.java:151)

                          • 10. Re: Deployment of JBoss Portal from sources
                            Prabhat Jha Master

                            I am assuming that when you start server, you are binding to some different ip configuration than localhost. In that case this error is expected. I don't have the link handy but if you search there should be a wiki explaining why this happens. This error is harmless and should not affect you if you don't use WSRP. In case you don't need WSRP, you can remove portal-wsrp.sar and restart.

                            • 11. Re: Deployment of JBoss Portal from sources
                              Peter Johnson Master

                               

                              Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
                              at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:424)


                              This usually shows up when running with JDK 6. If that is the case, either use JDK 5, or see http://wiki.jboss.org/wiki/JBossWithJDK6?action=e&windowstate=normal&mode=view

                              • 12. Re: Deployment of JBoss Portal from sources
                                hello All Newbie

                                Thanks all for response.
                                I restarted the server and have not seen the error since.

                                • 13. Re: Deployment of JBoss Portal from sources
                                  Chris Laprun Master

                                  Yes, this error is encountered when running an older version (such as the one that's bundled with JBoss AS 4.2.x) of JBoss WS with Java 6.