WSRP Exception with jboss-portal-2.7.0.CR1-bundled

[axelmotyka]

Hello,

iam evaluating JBoss with Portal for my company.

My configuration is:

1. 
   
2. jboss-portal-2.7.0.CR1-bundled
   
3. Java 1.6.07
   
4. MS Sql Server 2000
   
5. MS JDBC 1.2
   
6. Windows XP SP2
   
   
   Now the only thing i modified is database access:
   

   <datasources>
   <local-tx-datasource>
   <jndi-name>PortalDS</jndi-name>
   <connection-url>jdbc:sqlserver://SQLSERVER:1433;DatabaseName=Portal_DEV</connection-url>
   <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
   <user-name>user</user-name>
   <password>user</password>
   
   <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
   <metadata>
   <type-mapping>MS SQLSERVER2000</type-mapping>
   </metadata>
   </local-tx-datasource>
   </datasources>

   
   
   All other things are default. When i start jboss with default config, my first exception is:
   

   
   2008-10-29 10:56:28,390 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/D:/Dev/jboss-4.2.3.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.war/
   org.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.SocketException: Connection reset
   at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:154)
   at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:295)
   at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder.buildMetaData(JAXRPCServerMetaDataBuilder.java:97)
   at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:56)
   at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118)
   at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
   at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
   at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
   at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
   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.system.server.jmx.LazyMBeanServer.invoke(LazyMBeanServer.java:291)
   at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
   at $Proxy201.start(Unknown Source)
   at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
   at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
   at org.jboss.deployment.MainDeployer.addDeployer(MainDeployer.java:368)

   
   
   No i searched the forum, and as far as I understand i have to add:
   

   set JAVA_OPTS=%JAVA_OPTS% -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
   set JAVA_OPTS=%JAVA_OPTS% -Djboss.platform.mbeanserver
   set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote
   

   
   
   But that didnt help.
   
   I am a totaly new to JBoss and most of the J2EE stuff.
   
   What must be done to execute JBoss+Portal without exceptions?

[claprun]

First question is: do you need WSRP? If not, you can remove portal-wsrp.sar from jboss-portal.sar without issues.

Second, where did you see that you had to set these Java options and why?

Third, are you running behind a firewall or without an internet connection?

[axelmotyka]

1. No, i dont need that. I deleted it, and now portal starts up without exceptions. What should i do that i can use WSRP?

2. Starting from
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=126884
to
https://jira.jboss.org/jira/browse/JBWS-1943
to
http://jbossws.jboss.org/mediawiki/index.php?title=FAQ#How_to_use_JDK_JMX_JConsole_with_JBossWS.3F
i thought i need these settings.

3. Yes, and we have a curios proxy configuration. Do i need additional files? Or should i set some proxy values?

[prabhat.jha]

Chris, The JVM options that poster mentioned allow you to monitor jboss mbeans using external tools like jconsole.

[claprun]

Are you using the JDK JMX console? If not, you shouldn't have to worry about 2.
For 3 (and that should solve 1 ^_^), please take a look at: http://www.jboss.org/community/docs/DOC-12633

[claprun]

Note also that, since Portal 2.7.0.CR1 bundles JBoss AS 4.2.3.GA, you will need to update JBoss WS to version 3.0.4.GA.

[axelmotyka]

I update JBoss WS 3.0.4.GA, i set proxy configuration. When starting JBoss no exceptions occure, but when accessing portal in my browser:

15:16:30,968 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
java.lang.NoClassDefFoundError: org/apache/catalina/authenticator/SavedRequest
at org.apache.catalina.authenticator.FormAuthenticator.saveRequest(FormAuthenticator.java:464)
at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:236)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassNotFoundException: Unexpected error during load of: org.apache.catalina.authenticator.SavedRequest, msg=PermGen space
at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:560)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
... 13 more

I think the easiest thing is for now to delete the portal-wsrp.sar, then i run without errors. Dont know what went wrong, the ant-build of WS 3.0.4.GA was successfull, but i couldnt run the tests - everything failed. Maybe this is an network issue in my office, i don't know. I have not much knowledge about WSRP now, and i never used it. We have an old Tomcat/C++ application, this old application should now get a new web framework - and i want to try it with portal.
But you should update documentation for this and how to configure it.

Thank you for your quick help! This is a big point for JBoss and its tools.

[prabhat.jha]

The root cause here is:

Caused by: java.lang.ClassNotFoundException: Unexpected error during load of: org.apache.catalina.authenticator.SavedRequest, msg=PermGen space

Please add -XX:MaxPermSize=128m to $JBOSS_HOME/bin/run.conf

You have not given enough memory to load all the classes.

[claprun]

Hmm, PermGen space has already been increased in the bundled version, hasn't it?
But, yes, this is not a Portal-specific issue. Increasing the PermGen space should solve the issue.

[axelmotyka]

First of all, system is running now :) Thank you!

Now i will check out my first portlet and then lets see how we can integrate our old Supervisory Controls & MES application in this mighty JBoss stuff :)


MaxPermSize is configured, but in run.conf - and this file is never used in a windows system, so its missing in run.bat.

run.bat has to be updated with

set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m -XX:MaxPermSize=256m

and it would be a good configuration hint if you add

set JAVA_OPTS=%JAVA_OPTS% -Dhttp.proxyHost={proxy ip} -Dhttp.proxyPort={proxy port} -DproxySet=true

[claprun]

Good points! Thanks for the report! :)

[theute]

Good suggestions.
I thought run.conf would be 'used' even on Windows. It is not the case.

Could you open a Jira for those 2 things in the JBPORTAL project so we don't forget please ?