Known Issues
This section lists known issues for this release along with work-arounds when available. Issues are listed for the following components:
BPEL Service Engine
Note –
For BPEL SE stop/restart issues, see JBI Management.
The following are known issues for the BPEL Service Engine:
-
If a BPEL project is deleted using the Delete Source option and a new project is then created that reuses the same name, the newly created project's Properties window cannot be opened.
To work around this issue, stop and then restart the NetBeans IDE.
-
The BPEL Service Engine only creates connection pools and data sources for the Derby database. This functionality is available to assist developers and is not available for other databases or in a cluster. The BPEL Service Engine does create the persistence tables automatically for all supported databases, but only in standalone mode; this feature is not available in cluster mode. If you create connection pools, data sources, and tables before you install the BPEL Service Engine, it is possible to install the component with persistence enabled. Otherwise, installing to the cluster will fail.
To work around the issue of tables not being automatically created, you can create the tables in standalone mode and then add the BPEL SE to the cluster. For more information, see Setting Up the BPEL Database in Configuring GlassFish ESB for Clustering.
-
When an optional node is missing in the input message, an invalidVariable exception is thrown. This should not occur since the node is not required. This is due to an issue with BPEL case and message variables of the schema type.
Data Mashup Service Engine
The following are known issues for the Data Mashup Service Engine:
-
When querying an Axion database using the current_timestamp function in the WHERE clause, a parsing exception occurs.
To work around this issue, use the now function instead.
For example:
WHERE DEPARTMENT.DEPTID=EMPLOYEES.DEPTID and EMPLOYEES.DEPTDATE <= NOW()
-
In the Collaboration Properties window for a Data Mashup project, the Response Type field is no longer a drop-down field. It accepts the following values:
-
WebRowset
-
RelationalMap
-
JSON
-
Database Binding Component
The following are known issues for the Database Binding Component:
-
The ojdbc5.jar driver for Oracle does not support prepared statements. The following error message is given:
java.sql.SQLException: Unsupported feature
No resultset is populated, and java.lang.string is selected for every parameter, regardless of the datatype.
To work around this issue, use DataDirect drivers instead of ojdbc5.jar.
-
No error message displayed if too many parameters are supplied in an insert prepared statement. For example, insert into table values(?,?,?,?,?) into a 3-column table causes a runtime exception, and no parameters are added.
-
When a prepared statement is used to update or delete parameters, the result displays the default java.lang.String datatype irrespective of the actual datatype. This is because the DataDirect connect of JDBC driver for Oracle does not support returning parameter metadata information for an update statement with mixed literal and parameterized arguments.
To work around this issue, manually change the datatype of the parameter in the generated XSD.
-
Built-in functions require an alias to avoid misinterpreting names of elements with special characters. For example, the prepared statement select avg(float) from table where number in(...); yields the following error:
ERROR: s4s-att-invalid-value: Invalid attribute value for 'name' in element 'element'. Recorded reason: cvc-datatype-valid.1.2.1: 'AVG(NUMBER)' is not a valid value for 'NCName'.
To work around this issue, use an alias for the function. For example: select avg(float) avg from table where number in(...);
-
DataDirect driver does not return correct metadata, resulting in an incorrect resultset for output parameters of stored procedures. This is a driver error, and work ticket W809210001 has been filed with DataDirect about the metadata call getProcedureColumns() returning incorrect parameters.
-
A datetime value cannot be inserted for SQL Server 2005 using the sqljdbc.jar driver. This was caused by a syntax error involving spaces and parentheses.
See the resolution at http://forums.microsoft.com/technet/ShowPost.aspx?siteid=17&postid=4061403.
-
Stored procedures do not support the BLOB (binary large object) datatype. Although the procedure runs without generating an error, a select statement fails to yield any BLOB data.
-
When using a Derby database for polling in a clustered environment with the Number of Records option set to a low value, the following exception is thrown and the connection pool becomes unusable:
java.sql.SQLException: Connection closed.
To work around this issue, configure the number of records per poll to a high number; for example, 100 per 1000 records. A second workaround is to create all cluster-related tables in the same database
-
When the Database BC is implemented in a clustered environment across multiple servers, failover does not always work because the message status in the polling table prevents the in-process messages from being picked up by another instance (or by the same instance when it resumes).
To work around this issue, manually delete records in the polling table that are have a status of “In progress” or “SENT”. This allows running instances to pick up the messages and reprocess them.
-
When you create a Database BC WSDL document using the wizard, an XSD file named table_name.xsd is also created. If there is already an existing XSD file by that name, it is overwritten.
To work around this issue, make sure the table name is different from any existing XSD file names.
File Binding Component
The following are known issues for the File Binding Component:
-
The File BC supports encodings in UTF-8 format only; if the encoding is in non-UTF-8 format, the File BC fails to read the input data. However, data of any encoding style (either UTF or non-UTF-8) and binary data can both be forwarded as attachments.
You can work around the UTF-8 limitation by doing the following:
-
To read non-UTF-8 data, employ a custom encoder upstream of the File BC and convert it to UTF-8 format, which in turn can be provided as input to File BC.
-
To write non-UTF-8 data, route the output from the File BC to a custom encoder and convert it from UTF-8 to the preferred encoding format. For more information, refer to Designing Custom Encoders.
-
-
On the Windows operating system, when the File BC transforms XML text to bytes, an additional carriage return is added for each newline character. For example, \r\n is converted to \r\r\n.
FTP Binding Component
The following are known issues for the FTP Binding Component:
-
When the messageCorrelate attribute is set to true in the ftp:transfer element of the FTP WSDL, the FTP BC expects the input file to match a fixed pattern (req.UUID) so the UUID can be used as the ID to correlate a request with a response.
-
A project with invalid FTP BC property values can be built using command-line builds (ant tasks) but fails validation in NetBeans and is not built. This happens because certain validations that are performed automatically by NetBeans when building a project are not performed by command-line builds (ant tasks). For example, a project with a non-positive or non-integer FTP BC poll value (pollIntervalMillis) fails validation in NetBeans but can be built using ant commands.
-
On all operating systems, the delimiter for path components specified for preReceiveLocation (in sendTo, receiveFrom, and so forth) is the forward slash (/). Using the backslash instead results in errors such as the following:
FTPBC-E004026.
Exception when preparing ftp connection parameters in inbound processor. java.lang.Exception:
FTPBC-E004019.
No directory name found in PreReceiveLocation [...] when PreReceiveCommand is RENAME or COPY.
-
When the append attribute is set to true in the file:transfer element of the WSDL file, the FTP BC overwrites the existing output file instead of appending the information to the end of the file.
IEP Service Engine
The following are known issues for the IEP Service Engine:
-
When using Oracle as the IEP database platform, you must use Oracle JDBC driver version 10.2.0.4.0 or above. The default driver included with Oracle 9.2 (ojdbc14.jar) is version 9.0.2.0.0, and will not work with IEP. To determine the driver version you are using, view the manifest.mf file in the driver JAR file.
-
When a cluster instance is stopped using the asadmin stop-instance command, IEP processes that are currently running do not fail over to a live instance. This is due to the order in which methods are called during the stop process.
To work around this issue, stop and restart the Service Assembly.
-
The relation aggregator does not work as expected for various operations, and the output is an incorrect number of events. For example, invalid aggregations are not removed for Oracle. In certain cases with Derby, aggregations are updated even if the aggregation has not changed, leading to extra events.
-
When running the IEP SE on Solaris SPARC using an Oracle database, connection errors might occur.
To work around this issue, restart the GlassFish server.
-
When IEP SE is running on Solaris SPARC and using a Derby database, not all events are processed. This is due to an issue with a JDK method used by the IEP SE to get the current timestamp.
To verify whether you are having this issue, send events to an IEP application and verify the timestamp.
-
When the IEP SE is configured for Oracle and a RelationStream operator is used to retrieve events from an input relation, duplicate events may be produced.
To work around this issue, use an InsertStream operator instead of RelationStream. Another option is to use a Distinct operator after the RelationStream operator to filter duplicates. Note that neither of these options may be able to completely replace RelationStream
-
The IEP Service Engine creates connection pools and JDBC resources during installation. This automatic creation takes place only when the IEP Service Engine is installed in a GlassFish Domain Administration Server (DAS) instance. If the IEP Service Engine is installed in a GlassFish standalone instance, then the IEP Service Engine does not create the connection pools and JDBC resources.
To work around this issue, manually create the connection pools and JDBC resources and then install the IEP Service Engine.
-
An IEP Module project can have multiple event processors, and one database connection is created and kept open for each event processor. Therefore, each event processor has a dedicated database connection. When the event processors stop running (for example, when the Composite Application is stopped), this connection is released. Because the IEP SE uses database connections for other tasks, the maximum pool size of the connection pools should be larger than the number of event processors that are running in the IEP SE by a count of 10.
-
By default, the IEP SE generates a WSDL document for each IEP process document, and regenerates the WSDL document every time the IEP process is edited. By default, bindings and services are generated in this WSDL, and these elements usually need to be edited to work properly when deployed. However, if these WSDL documents are edited, the edits are replaced by the default values every time the WSDL document is regenerated.
Bindings and services created in the CASA Editor are not affected when the IEP WSDL documents are regenerated. However, you should not clone the IEP WSDL file to customize its generated bindings and services in the CASA Editor because updates to the generated WSDL files are not updated after cloning. Over time, the cloned and edited WSDL deployed for the bindings becomes inconsistent with the WSDL document deployed for the IEP Service Engine. Consider using the following procedure for setting up your Composite Application and IEP project for iterative development:
-
Define the IEP Module project.
-
Turn off the generation of concrete configuration elements (bindings and services) in the IEP generated WSDL files by setting the always.generate.abstract.wsdl flag in the project.properties file to true.
-
Build the IEP Module project.
-
Add the IEP Module project to a new Composite Application project and build the project.
-
Define the binding components and connections using the CASA Editor. To use the composite application test feature, define SOAP input and file output bindings as appropriate for your test environment.
-
Build and deploy the composite application.
-
Run tests.
-
Change the IEP Module project, adjust binding component and service configurations if necessary in the CASA Editor, and rebuild and redeploy the composite application. Run tests and repeat.
-
Java Application Project for JAXB
The following is a known issue for Java Application projects with JAXB:
-
In Java Application projects for JAXB, JAXB class files are deleted at runtime and the application fails to run.
To work around this issue, deselect Compile on Save in the Project Properties window. Compile on Save is located in the Build > Compiling properties node.
LDAP Binding Component
The following are known issues for the LDAP Binding Component:
-
When the authentication type is not agreed upon between the LDAP server and client, an AuthenticationNotSupportedExceptionoccurs. For example, the error occurs when a client specifies strong SSL authentication with a DSEE 6 server that handles none or simple authentication, but not strong authentication.
-
No design-time validation is performed when an invalid root DN is supplied (such as dc=suninstead of dc=sun,dc=com), and the user is (incorrectly) allowed to create LDAP WSDL files with the incorrect values. Such a project correctly fails at runtime with a No such object error message.
XSLT Service Engine
The following are known issues for the XSLT Service Engine:
-
A SEVERE error appears in the server log when running an XSLT project with an HTTP/SOAP binding. The error is:
Unable to create envelope from given source because the root element is not named Envelope
This is an erroneous log message and does not interfere with the running of the XSLT project.
To prevent the message from being logged, set the SAAJ Logger for the XSLT SE to OFF.
-
If you change text in the XML editor, clicking Validate does not save the changes before compiling and validating the code. You need to click Save All before validating the XML.
-
Issue 1760 and NetBeans Issue 162869
The XSLT SE does not support catalog.xml, which is required for the correct Referenced Resources support. For example, when referencing a WSDL document from another project using Project Reference, the XSLT project fails to deploy.
Cluster Configuration
The following is a known issue for configuring GlassFish ESB cluster instances:
-
When you configure cluster instances using the GlassFish Admin Console, the configuration does not propagate to any new cluster instances. This is because instances are configured individually. In some cases, this can cause deployment to fail.
To work around this, configure each cluster instance individually or use the following asadmin command to configure all instances in the cluster:
asadmin update-jbi-application-variable --component=sun-jms-binding name=value
Usage: asadmin update-jbi-application-variable [--terse=false] [--echo=false] [--interactive=true] [--host localhost] [--port 4848|4849] [--secure | -s] [--user admin_user] [--passwordfile file_name] [--target target(Default server)] --component Component Name (name=value)[,name=value]*|property file
Composite Application
The following are know issues for Composite Application (CA) projects:
-
A test case cannot be created using the SOAP12 binding, even though GlassFish otherwise supports SOAP 1.2.
To work around this issue, use a SOAP binding instead of SOAP12.
-
NetBeans Issue 152455 (now 138971)
When the design canvas of the CASA Editor is at certain sizes, the display of its scrollbars oscillates and CPU usage goes to 100%.
To work around this issue, increase the size of the window or of the CASA Editor design canvas so scrollbars do not display.
-
When a new project type is freshly installed, the Composite Application project is initially unable to determine the service engine type and is thus unable to deploy the service unit. The following error message appears:
Cannot add JBI module project_type. Its target component type engine_name is unknown.
To work around this issue, stop and then restart the NetBeans IDE.
-
You cannot rebuild a Composite Application project after a Service Unit (SU) has been deleted from it.
To work around this issue, manually edit the build-impl.xml file and delete all sections that operate on the deleted SU.
Installation and Upgrading
The following are known issues for installation and upgrading:
-
When you run the GlassFish ESB uninstaller, the several folders under the GlassFishESB_Home\netbeans directory are not removed.
To work around this issue, manually remove the folders after the GlassFish ESB uninstallation is complete.
-
When you perform a side-by-side upgrade of GlassFish ESB, the upgrade tool (asupgrade) does not migrate application variables and application configuration.
To work around this issue, perform the upgrade and then recreate the application variables and application configurations in the new domain for GlassFish ESB 2.1.
-
When using GlassFish ESB with JDK 1.6.0_13 or 1.6.0_14, several of the wizards used to develop application will not work correctly and may have problems importing XSDs from files. In addition, the GlassFish ESB Installer fails to install on Windows when using JDK 1.6.0_13 or 1.6.0_14.
To work around this issue, install a different version of JDK 1.6.
JBI Management
The following are known issues in managing JBI components:
-
Issue 884, Issue 885, and OJC Issue 559
When a component is shut down while there are configuration errors, it cannot be restarted and its configuration settings cannot be edited within the NetBeans IDE or the web console.
When this occurs, the state of the component changes to “Stopped”, and you can reconfigure the properties correctly. After you correct the property values, shutdown and then restart the component in order for the changes to take effect.
For the BPEL Service Engine, when there is an error in the JDBC resource name, the engine will create the resource with the given name and assume that the default connection pools are used. If the Derby database is not started, the default connection pools are not created.
-
Selecting the Compile on Save option in a Java Application Project Properties window causes a JAXB class file to be deleted at runtime. The project fails at runtime with the following exception:
Exception in thread "main" java.lang.NoClassDefFoundError
To work around this issue, deselect the Compile on Save option. This option is located on the Java Application Properties window under Build > Compiling.
Localization
The following is a known localization issue:
-
When you perform the following steps in a non-English locale, you cannot expand the GlassFish server tree to select the value.
-
Launch the New File Wizard to create a new JCA message-driven bean.
-
Complete steps 1 through 3 on the wizard.
-
For the Connection URL in step 4, click the ellipses button and start the GlassFish server to obtain the JNDI value.
To work around this issue, use the GlassFish Admin Console to retrieve the JNDI value to enter for the Connection URL. The value is located under Resources > Connectors > Admin Object Resources.
-
Databases
-
MySQL does not support microseconds in date and timestamp fields, so if an incoming message contains any time or timestamp fields that drill down to the microsecond, the fractal part of the seconds is ignored in the database. For example, if the value of a timestamp is '2010–12–10 14:12:09.019473', the last six digits (019473) are ignored.
- © 2010, Oracle Corporation and/or its affiliates