Ebase Installation: Red Hat Enterprise Linux & JBoss AS

Post any questions regarding Installing or Upgrading Ebase, including problems starting up the Ebase Xi Server or Designer

Moderators: Jon, Steve, Ian, Dave

AJDulk
Ebase User
Posts: 94
Joined: Fri Sep 14, 2007 12:18 pm
Location: The Netherlands
Contact:

Ebase Installation: Red Hat Enterprise Linux & JBoss AS

#1

Postby AJDulk » Thu Jan 30, 2014 12:07 pm

The Setup:

2 Virtual Servers with the following:
- Red Had Enterprise Linux (v5.9)
- JBoss AS 7.1 (JBoss Web/7.2.2.Final)
- Java 7 (1.7.0_17)

The backend database is Oracle 10g

Deployment:
- UFSSetup.properties and the 2 preference files have been placed in the modules folder under JBoss.
- A .war file has been created with the the latest Ebase 4.4.4 webapps directory excluding the files placed in the modules folder. Included in the .war file are some extra classes delivered to us by Ebase and a jar that is specifically written by us. Further we have some extra jars to support Apache FOP and ImgScalr, namely:
  • avalon-framework-4.2.0.jar
    batik-all-1.7.jar
    commons-io-1.3.1.jar
    commons-logging-1.1.1.jar
    fop.jar
    geronimo-jaxws_2.2_spec-1.0.jar
    imgscalr-lib-4.2.jar
    serializer-2.7.0.jar
    xalan-2.7.0.jar
    xercesImpl-2.7.1.jar
    xml-apis-1.3.04.jar
    xml-apis-ext-1.3.04.jar
    xmlgraphics-commons-1.4.jar
    xmlsec-1.3.0.jar
The .war file has been deployed to the cluster and a basic application run under Ebase. Basic database connectivity has thus been established.

When deploying we see: WARN [org.jboss.as.ee] (MSC service thread 1-3) JBAS011006: Not installing optional component org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation due to an exception (enable DEBUG log level to see the cause). This is expected, see https://issues.jboss.org/browse/WFLY-924

There are currently 2 known problems:
- Calling a web-service defined by us.
- a database error when calling a specific application.

Web-service call:
Send:

Code: Select all

Address: /ufs/cxf/get_user
Encoding: ISO-8859-1
Content-Type: text/xml
Headers: {content-type=[text/xml], host=[services.nl], Content-Length=[289], SOAPAction=[getDetails], user-agent=[Jakarta Commons-HttpClient/3.0], Content-Type=[text/xml]}
Messages: (message truncated to -1 bytes)

Payload&#58; <xml>
<soap>
<soap>
<bur>
  <bur>bsn=126946036</bur>
</bur>
</soap>
</soap>
Returns:

Code: Select all

Response-Code&#58; 500
Encoding&#58; ISO-8859-1
Content-Type&#58; text/xml
Headers&#58; &#123;&#125;
Messages&#58; &#40;message truncated to -1 bytes&#41;

Payload&#58; <xml>
<soap>
  <soap>
    <soap>
      <faultcode>soap&#58;Server</faultcode>
      <faultstring>Fault occurred while processing.</faultstring>
    </soap>
  </soap>
</soap>
It seems that JBoss AS 7.1 already uses CXF - see https://docs.jboss.org/author/display/A ... ntegration. This could be causing a conflict with the version packaged with Ebase. What needs to be done to get web-services working under Ebase again?

Database error
DEBUG Start execution of command - fetch: 13:41:30.049
DEBUG Debug for database resource FORM_METADATA - fetch SQL statement:
DEBUG select * from FORMS where NAME='TEST'
INFO Datasource TEST lookup in application context successful
ERROR Error getting connection from datasource TEST, javax.resource.ResourceException: IJ000457: Unchecked throwable in managedConnectionReconnected() cl=org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@5e8aaae2[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@5eea3629 connection handles=0 lastUse=1391085690151 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@4d8468a5 pool internal context=SemaphoreArrayListManagedConnectionPool@34707898[pool=jdbc/TEST] xaResource=LocalXAResourceImpl@61d90beb[connectionListener=5e8aaae2 connectionManager=2521d006 warned=false currentXid=null productName=Oracle productVersion=Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options jndiName=java:/jdbc/TEST] txSync=null]
Any ideas what could be going wrong here?
0 x

AJDulk
Ebase User
Posts: 94
Joined: Fri Sep 14, 2007 12:18 pm
Location: The Netherlands
Contact:

RE: Ebase Installation: Red Hat Enterprise Linux & JBoss

#2

Postby AJDulk » Fri Jan 31, 2014 12:08 pm

Looks like the Database connection problem is triggered by the following code:

Code: Select all

	try &#123;
		dbConnection = system.getDatabaseConnection&#40;"DATA"&#41;;
		...
With at least one of my connections it is only a problem the first time around, the second time works as expected.

I get the impression that it brings the UFSREPOSITORY connection totally down if done against it. That is, not even Ebase is able to connect after that until a restart of the server.

Update: It looks like there is a database resource that is corrupt that is causing the problem in the UFSREPOSITORY. I had the idea that the whole was down because I tried to export the database resources and received the error message yesterday.
0 x

Hovik
Moderator
Moderator
Posts: 184
Joined: Tue Sep 11, 2007 8:58 am

#3

Postby Hovik » Fri Jan 31, 2014 3:39 pm

For the CXF conflict issue, You need to turn off the webservices subsystem by adding a jboss-deployment-structure.xml as follows:

Code: Select all

<jboss-deployment-structure xmlns="urn&#58;jboss&#58;deployment-structure&#58;1.2">
    <deployment>
        <exclude-subsystems>
            <subsystem name="webservices" />
        </exclude-subsystems>
    </deployment>
</jboss-deployment-structure>
0 x

AJDulk
Ebase User
Posts: 94
Joined: Fri Sep 14, 2007 12:18 pm
Location: The Netherlands
Contact:

RE: Ebase Installation: Red Hat Enterprise Linux & JBoss

#4

Postby AJDulk » Thu Apr 17, 2014 1:48 pm

We have updated to the newest version of JBoss and are still having the Soap Webservice problem. The suggestion does not work.
0 x

Steve
Moderator
Moderator
Posts: 414
Joined: Fri Sep 07, 2007 3:44 pm
Location: Sandy, UK
Contact:

#5

Postby Steve » Tue Apr 22, 2014 10:16 am

Hi Antony,

After speaking to you on Thursday I believe we established that the Integration Services are working with the exclusion of the CXF module. This would make sense otherwise the CXF libraries will clash.

You tested a basic integration service and this worked as expected.

I do believe that the problem is elsewhere in the configuration. You have a clustered environment that might be causing problems. Further investigation might be required.

Steve
0 x


Who is online

Users browsing this forum: No registered users and 12 guests