Topic
5 replies Latest Post - ‏2008-10-06T15:15:37Z by SystemAdmin
blaine1
blaine1
4 Posts
ACCEPTED ANSWER

Pinned topic Plants by WebSphere Application is broken in V7

‏2008-07-14T18:41:18Z |
Hi,

I tried to start Plants by WebSphere application in V7 but it looks like it is broken in this version. Did anyone run into a similar problem? Please let me know.

7/9/08 14:03:53:164 CDT 00000012 ApplicationMg A WSVR0221I: Application started: SamplesGallery
7/9/08 14:03:53:179 CDT 00000012 CompositionUn A WSVR0191I: Composition unit WebSphere:cuname=SamplesGallery,cuedition=1.0 in BLA WebSphere:blaname=SamplesGallery,blaedition=1.0 started.
7/9/08 14:03:53:210 CDT 00000000 ContainerHelp E WSVR0501E: Error creating component com.ibm.ws.runtime.component.CompositionUnitMgrImpl@72047204
com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.metadata.MetaDataException: CNTR0146E: The META-INF/ibm-ejb-jar-bnd.xml bindings file contained in the PlantsByWebSphereEJB.jar module has a configuration error at line number: 4, column number: 41.
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:318)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:767)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1488)
Caused by: com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.metadata.MetaDataException: CNTR0146E: The META-INF/ibm-ejb-jar-bnd.xml bindings file contained in the PlantsByWebSphereEJB.jar module has a configuration error at line number: 4, column number: 41.
at com.ibm.ws.runtime.component.EJBContainerImpl.createMetaData(EJBContainerImpl.java:3920)
at com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaDataFromFactories(MetaDataMgrImpl.java:173)
at com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaData(MetaDataMgrImpl.java:307)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:602)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:915)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1019)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2394)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:336)
at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:126)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:286)
... 3 more
Caused by: com.ibm.ws.metadata.MetaDataException: CNTR0146E: The META-INF/ibm-ejb-jar-bnd.xml bindings file contained in the PlantsByWebSphereEJB.jar module has a configuration error at line number: 4, column number: 41.
at com.ibm.ws.metadata.bindings.EJBModuleHelper.processBindingsFile(EJBModuleHelper.java:423)
at com.ibm.ws.metadata.WCCMConfigReader.populateModuleData(WCCMConfigReader.java:289)
at com.ibm.ws.metadata.MetaDataOrchestrator.getModuleData(MetaDataOrchestrator.java:115)
at com.ibm.ws.runtime.component.EJBContainerImpl.createMetaData(EJBContainerImpl.java:3902)
... 12 more
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'current-backend'. One of '{"http://websphere.ibm.com/xml/ns/javaee":session, "http://websphere.ibm.com/xml/ns/javaee":message-driven, "http://websphere.ibm.com/xml/ns/javaee":interceptor, "http://websphere.ibm.com/xml/ns/javaee":message-destination}' is expected.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.startElement(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.ValidatingUnmarshaller.startElement(ValidatingUnmarshaller.java:73)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:101)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:202)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:175)
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:137)
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:184)
at com.ibm.ws.metadata.bindings.EJBModuleHelper.populateMaps(EJBModuleHelper.java:505)
at com.ibm.ws.metadata.bindings.EJBModuleHelper.processBindingsFile(EJBModuleHelper.java:379)
... 15 more

Thanks,
Zafar
Updated on 2008-10-06T15:15:37Z at 2008-10-06T15:15:37Z by SystemAdmin
  • bvperepa
    bvperepa
    4 Posts
    ACCEPTED ANSWER

    Re: Plants by WebSphere Application is broken in V7

    ‏2008-07-15T02:12:44Z  in response to blaine1
    Yes, I experienced the same problem last week on my Windows Install:

    I am getting the following error:

    7/8/08 20:53:07:312 PDT 00000000 ContainerHelp E WSVR0501E: Error creating component com.ibm.ws.runtime.component.CompositionUnitMgrImpl@42e642e6
    com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.metadata.MetaDataException: CNTR0146E: The META-INF/ibm-ejb-jar-bnd.xml bindings file contained in the PlantsByWebSphereEJB.jar module has a configuration error at line number: 4, column number: 41.
    at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:318)
    at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:767)
    at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1488)
    Caused by: com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.metadata.MetaDataException: CNTR0146E: The META-INF/ibm-ejb-jar-bnd.xml bindings file contained in the PlantsByWebSphereEJB.jar module has a configuration error at line number: 4, column number: 41.
    at com.ibm.ws.runtime.component.EJBContainerImpl.createMetaData(EJBContainerImpl.java:3920)
    at com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaDataFromFactories(MetaDataMgrImpl.java:173)
    at com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaData(MetaDataMgrImpl.java:307)
    at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:602)
    at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:915)
    at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1019)
    at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2394)
    at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:336)
    at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:126)
    at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:286)
    ... 3 more
    Caused by: com.ibm.ws.metadata.MetaDataException: CNTR0146E: The META-INF/ibm-ejb-jar-bnd.xml bindings file contained in the PlantsByWebSphereEJB.jar module has a configuration error at line number: 4, column number: 41.
    at com.ibm.ws.metadata.bindings.EJBModuleHelper.processBindingsFile(EJBModuleHelper.java:423)
    at com.ibm.ws.metadata.WCCMConfigReader.populateModuleData(WCCMConfigReader.java:289)
    at com.ibm.ws.metadata.MetaDataOrchestrator.getModuleData(MetaDataOrchestrator.java:115)
    at com.ibm.ws.runtime.component.EJBContainerImpl.createMetaData(EJBContainerImpl.java:3902)
    ... 12 more
    Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'current-backend'. One of '{"http://websphere.ibm.com/xml/ns/javaee":session, "http://websphere.ibm.com/xml/ns/javaee":message-driven, "http://websphere.ibm.com/xml/ns/javaee":interceptor, "http://websphere.ibm.com/xml/ns/javaee":message-destination}' is expected.
    at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
    at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
    at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
    at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
    at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
    at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
    at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
    at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
    at org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.startElement(Unknown Source)
    at com.sun.xml.internal.bind.v2.runtime.unmarshaller.ValidatingUnmarshaller.startElement(ValidatingUnmarshaller.java:73)
    at com.sun.xml.internal.bind.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:101)
    at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
    at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
    at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
    at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
    at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:202)
    at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:175)
    at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:137)
    at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:184)
    at com.ibm.ws.metadata.bindings.EJBModuleHelper.populateMaps(EJBModuleHelper.java:505)
    at com.ibm.ws.metadata.bindings.EJBModuleHelper.processBindingsFile(EJBModuleHelper.java:379)
    ... 15 more

    7/8/08 20:53:07:375 PDT 00000000 TCPChannel I TCPC0001I: TCP Channel TCP_1 is listening on host * (IPv4) port 9060.

    We have experienced the same again today in our Linux install as well:

    root@rhel1 bin# ./ivt.sh server1 AppSrv01
    WSVR0615W: The user.install.root system property is not set. Some product classes might not be found.
    Server name is:server1
    Profile name is:AppSrv01
    Profile home is:/opt/I/WAS70/profiles/AppSrv01
    Profile type is:default
    Cell name is:localhostNode01Cell
    Node name is:localhostNode01
    Current encoding is:UTF-8
    Server port number is:9080
    IVTL0010I: Connecting to the localhost WebSphere Application Server on port: 9080
    Start running the following command:/opt/I/WAS70/profiles/AppSrv01/bin/startServer.sh server1 -profileName AppSrv01
    ADMU0116I: Tool information is being logged in file
    /opt/I/WAS70/profiles/AppSrv01/logs/server1/startServer.log
    ADMU0128I: Starting tool with the AppSrv01 profile
    ADMU3100I: Reading configuration for server: server1
    ADMU3200I: Server launched. Waiting for initialization status.
    ADMU3000I: Server server1 open for e-business; process id is 20240
    Testing server using the following URL:http://localhost:9080/ivt/ivtserver?parm2=ivtservlet
    IVTL0050I: Servlet engine verification status: Passed
    Testing server using the following URL:http://localhost:9080/ivt/ivtserver?parm2=ivtAddition.jsp
    IVTL0055I: JavaServer Pages files verification status: Passed
    Testing server using the following URL:http://localhost:9080/ivt/ivtserver?parm2=ivtejb
    IVTL0060I: Enterprise bean verification status: Passed
    IVTL0035I: The Installation Verification Tool is scanning the /opt/I/WAS70/profiles/AppSrv01/logs/server1/SystemOut.log file for errors and warnings.
    7/14/08 14:59:18:564 EDT 00000000 WSKeyStore W CWPKI0041W: One or more key stores are using the default password.
    7/14/08 14:59:23:444 EDT 00000000 ThreadPoolMgr W WSVR0626W: The ThreadPool setting on the ObjectRequestBroker service is deprecated.

    </d iv>
    7/14/08 14:59:50:121 EDT 0000000d EJBModuleHelp E CNTR0146E: The META-INF/ibm-ejb-jar-bnd.xml bindings file contained in the PlantsByWebSphereEJB.jar module has a configuration error at line number: 4, column number: 41.
    7/14/08 14:59:50:457 EDT 0000000d EJBContainerI E WSVR0039E: Unable to start EJB jar, PlantsByWebSphereEJB.jar: CNTR0146E: The META-INF/ibm-ejb-jar-bnd.xml bindings file contained in the PlantsByWebSphereEJB.jar module has a configuration error at line number: 4, column number: 41.
    7/14/08 14:59:50:467 EDT 0000000d DeployedAppli W WSVR0206E: Module, PlantsByWebSphereEJB.jar, of application, PlantsByWebSphere.ear/deployments/PlantsByWebSphere, failed to start
    7/14/08 14:59:50:494 EDT 0000000d ApplicationMg W WSVR0101W: An error occurred starting, PlantsByWebSphere
    7/14/08 14:59:51:424 EDT 0000000d CompositionUn E WSVR0194E: Composition unit WebSphere:cuname=PlantsByWebSphere,cuedition=1.0 in BLA WebSphere:blaname=PlantsByWebSphere,blaedition=1.0 failed to start.
    7/14/08 14:59:52:652 EDT 00000000 ContainerHelp E WSVR0501E: Error creating component com.ibm.ws.runtime.component.CompositionUnitMgrImpl@3f203f2
    IVTL0040I: 8 errors/warnings are detected in the /opt/I/WAS70/profiles/AppSrv01/logs/server1/SystemOut.log file
    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<&lt ;<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

    IVTL0080I: The installation verification is complete.
    root@rhel1 bin#

    Please help us as we are validating the install and runtime using reference implementation. Thanks.
  • walward
    walward
    5 Posts
    ACCEPTED ANSWER

    Re: Plants by WebSphere Application is broken in V7

    ‏2008-07-18T14:12:27Z  in response to blaine1
    Yes, this is a problem with PlantsByWebSphere in the beta. Try these steps to correct it:

    1) make a copy of <was_install>/samples/lib/PlantsByWebSphere/PlantsByWebSphere.ear
    2) extract PlantsByWebSphereEJB.jar from the ear (winzip works well)
    3) extract ibm-ejb-jar-bnd.xml from the jar (winzip)
    4) update the xml so it looks like this:
    <?xml version="1.0" encoding="UTF-8"?>
    <ejb-jar-bnd xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://websphere.ibm.com/xml/ns/javaee"
    xsi:schemaLocation="http://websphere.ibm.com/xml/ns/javaee http://websphere.ibm.com/xml/ns/javaee/ibm-ejb-jar-bnd_1_0.xsd" version="1.0">
    <session name="Mailer">
    <resource-ref name="mail/PlantsByWebSphere" binding-name="mail/PlantsByWebSphere"/>
    </session>
    </ejb-jar-bnd>

    5) update the jar with the modified xml. Be sure to keep the path to the file the same within the jar (path = meta-inf/). Use Winzip or the java jar command.
    6) update the ear with the updated jar. Use Winzip or the java jar command
    7) reinstall PBW from the console or command line.
  • bvperepa
    bvperepa
    4 Posts
    ACCEPTED ANSWER

    Re: Plants by WebSphere Application is broken in V7

    ‏2008-07-20T17:44:17Z  in response to blaine1
    Hello William,

    Thank you for your instructions and I was able to deploy the Plants by WebSphere Application sample on two Windows servers successfully. We would try on Linux platform as well.

    Best wishes.
    • tennenjl
      tennenjl
      4 Posts
      ACCEPTED ANSWER

      Re: Plants by WebSphere Application is broken in V7

      ‏2008-07-25T15:45:47Z  in response to bvperepa
      On the Linux platform, the solution works, but with one important caveat. If you run ivt.sh to verify the installation, I had to stop the server and then rename the SystemOut.log to SystemOut.log.old, otherwise the ivt program still fails. It fails because the ivt program reads the OLD error messages in the SystemOut.log and thinks that they are still relevant.

      Jeff
      • SystemAdmin
        SystemAdmin
        103 Posts
        ACCEPTED ANSWER

        Re: Plants by WebSphere Application is broken in V7

        ‏2008-10-06T15:15:37Z  in response to tennenjl
        This is the behavior of IVT. A part of Installation Verification is starting the server process and reporting any detectable errors in the SystemOut.log file. IVT will report any errors found in SystemOut.log