11:48:49,482 ERROR JDBCExceptionReporter Table not found in statement…
Nothing's wrong, the table don't exist in the first startup, an error is thrown but the table is created just after. Those messages will disappear on the next startup.
Another issue, when I start JBoss Portal Server using run.bat, and WSRP is now complaining with the following stack trace:
14:05:46,564 ERROR [Scheduler$Listener] Invoke of the Schedulable MBean failed
javax.management.MBeanException
......................................
... 22 more
Caused by: java.lang.UnsupportedOperationException: setProperty must be overridd
en by all subclasses of SOAPMessage
......................................
... 29 more
To resolve the issue, we need to reconfigure WSRP to listen on the correct interface. Updating WSRP ports and URL bindings when Portal is not running on the default port or not bound to localhost.
You can pass the full host name using the -b option of the run command when you launch AS. If it is still not working, you can then force the port number by modifying jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse/WEB-INF/wsdl/wsrp_services.wsdl (if you're not using the source distribution and compiling Portal from scratch, you might need to expand jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse just like you would expand a JAR file) to change all the soap-address elements to include http://hostname
I unzip the jboss-portal-2.6.2.GA\server\default\deploy\jboss-portal.sar\portal-wsrp.sar\portal-wsrp.jse file, then I find the portal-wsrp\WEB-INF\wsdl\wsrp_services.wsdl, and then enable the 'wsdl:service name="WSRPService"'

No comments:
Post a Comment