IC91933: EXCEPTIONS IN STREAMS STUDIO WHEN COMPOSITE OPERATOR NAME MATCHES STREAM OR OPERATOR NAME

 

APAR status

  • Closed as fixed if next.

Error description

  • This problem can occur if you have an application that contains
    a composite operator in the default namespace and the composite
    operator name matches a stream name or another operator name.
     For example:
    composite test1 {
    graph
    stream<rstring message> test1 = Beacon(){
    param
    iterations : 20u ;
    output
    test1 : message = "Hello, world!" ; }
    ()as Sink = FileSink(test1){
    param
    file : "result.txt" ;
    format : line ; }
    }
    When you try to view the instance or application graph in
    Streams Studio, an exception occurs. For example:
    org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsExce
    ption: index=0, size=0
    at
    org.eclipse.emf.common.util.BasicEList.get(BasicEList.java:352)
    ...
    Similar exceptions occur if you try to launch the main
    composite in Streams Studio.
    

Local fix

  • Specify a namespace keyword in your SPL application. Putting
    operators into meaningful namespaces helps maintain modularity
    and prevents name clashing with
    operators, functions, and types in other namespaces. NOTE: The
    source files inside of a namespace must conform to a standard
    directory naming and structure. The namespace that is derived
    from the directory structure
    must match the namespace that you define in the .spl file.
    
    USERS AFFECTED: Streams Studio users.
    
    PROBLEM DESCRIPTION:  See Error Description.
    
    PROBLEM CONCLUSION: This problem is fixed in InfoSphere Streams
    3.1.
    

Problem summary

  • See Error Description
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IC91933

  • Reported component name

    INFOSPHERE STRE

  • Reported component ID

    5724Y95IS

  • Reported release

    300

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-26

  • Closed date

    2013-10-11

  • Last modified date

    2013-10-15

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • IDE
    

Fix information

Applicable component levels

  • R310 PSY

       UP

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

InfoSphere Streams

Software version:

3.0

Reference #:

IC91933

Modified date:

2013-10-15

Translate my page

Machine Translation

Content navigation