9 Replies Latest reply on Jan 2, 2013 10:55 AM by Jesper Pedersen

    trouble with RAR with ResourceAdapter

    Frank Langelage Master

      I have a rar file in charge for some month on JBoss AS7 Alpha1-SNAPSHOT, using ironjacamer 1.0.13.Final now.

      After some trouble with the migration from 4.2x it worked fine for a long time. Code was not changed.

      Now I encounter problems again.

       

      Validation is still successful:

      ksh validator.sh $JBOSS_HOME/standalone/deployments/filesystem.rar

      Validation sucessful

       

      standalone.xml contains:

          <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0">
              <resource-adapters>
                  <resource-adapter>
                      <archive>filesystem.rar</archive>
                      <config-property name="Path">/mbi</config-property>
                      <connection-definitions>
                          <connection-definition jndi-name="java:/Filesystem" class-name="biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory"/>
                      </connection-definitions>
                  </resource-adapter>
              </resource-adapters>
          </subsystem>

       

      Sources are:

      FilesystemConnectionFactoryImpl.java

      FilesystemConnectionImpl.java

      FilesystemConnectionManager.java

      FilesystemManagedConnection.java

      FilesystemManagedConnectionFactory.java

      FilesystemManagedConnectionMetaData.java

      FilesystemResourceAdapter.java

      ci/FilesystemConnectionFactory.java

      ci/FilesystemConnection.java

       

      From server.log:

      22:25:20,347 INFO  [org.jboss.as.server.deployment.scanner#startScanner] JBAS015012: Started FileSystemDeploymentService for directory /mbi/tools/jboss/7.2/standalone/deployments

      22:25:20,356 INFO  [org.jboss.as.server.deployment#start] JBAS015876: Starting deployment of "filesystem.rar"

      22:25:48,109 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#<init>]

      22:25:48,111 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#<init>]

      22:25:48,112 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#setLogWriter] java.io.PrintWriter@1ee88dd

      22:25:48,112 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#setLogWriter]

      22:25:48,113 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#createConnectionFactory]

      22:25:48,114 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#createConnectionFactory] biz.mbisoftware.fn.jca.filesystem.FilesystemConnectionFactoryImpl@15b9f9a

      22:25:48,115 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/Filesystem

      22:25:48,119 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer#createObjectsAndInjectValue] IJ020002: Deployed: file:/mbi/tools/jboss/7.2/standalone/tmp/vfs/tempf60d0c19e890fd72/filesystem.rar-dafe9e7274262254/contents/

      22:25:53,058 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/Filesystem]

      ...

      22:30:03,300 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#hashCode]

      22:30:03,304 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#hashCode] 17

      22:30:03,306 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemConnectionImpl#<init>] biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory@11

      22:30:03,307 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemConnectionImpl#<init>]

      22:30:03,309 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemConnectionImpl#getRepositoryPath]

      22:30:03,311 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#getResourceAdapter]

      22:30:03,312 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#getResourceAdapter] null

      22:30:03,314 ERROR [biz.mbisoftware.fn.jca.filesystem.FilesystemConnectionImpl#getRepositoryPath] this.mcf.getResourceAdapter() == null

      22:30:03,315 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#getResourceAdapter]

      22:30:03,317 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#getResourceAdapter] null

       

      No instance of FilesystemResourceAdapter taking the "Path" property is created and set for the ManagedConnectionFactory object during deployment.


        • 1. Re: trouble with RAR with ResourceAdapter
          Frank Langelage Master

          Switched back to ironjacamar 1.0.12.Final in pom.xml and made a new build of JBoss AS7.

          Tata: problem disappeared.

           

          sb2000.[maj2e_langfr]/mbi/mbi2e_all. egrep -i "(DEBUG|filesys)" `jbosslogfile` | pg

          09:03:45,471 INFO  [org.jboss.as.server.deployment#start] JBAS015876: Starting deployment of "filesystem.rar"

          09:03:45,599 INFO  [org.jboss.as.server.deployment.scanner#startScanner] JBAS015012: Started FileSystemDeploymentService for directory /mbi/tools/jboss/7.2/standalone/deployments

          09:03:51,846 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemResourceAdapter#setPath] /mbi

          09:03:51,848 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemResourceAdapter#setPath]

          09:03:52,052 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemResourceAdapter#setPath] /mbi

          09:03:52,071 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemResourceAdapter#setPath]

          09:03:52,074 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#<init>]

          09:03:52,075 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#<init>]

          09:03:52,076 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#setLogWriter] java.io.PrintWriter@de1cb6

          09:03:52,077 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#setLogWriter]

          09:03:52,078 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemResourceAdapter#hashCode]

          09:03:52,079 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemResourceAdapter#hashCode]

          09:03:52,079 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#setResourceAdapter] biz.mbisoftware.fn.jca.filesystem.FilesystemResourceAdapter@a11663

          09:03:52,080 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#setResourceAdapter]

          09:03:52,119 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#createConnectionFactory]

          09:03:52,120 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#createConnectionFactory] biz.mbisoftware.fn.jca.filesystem.FilesystemConnectionFactoryImpl@161c602

          09:03:52,121 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/Filesystem

          09:03:52,129 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemResourceAdapter#start]

          09:03:52,130 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemResourceAdapter#start]

          09:03:52,303 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer#createObjectsAndInjectValue] IJ020002: Deployed: file:/mbi/tools/jboss/7.2/standalone/tmp/vfs/temp533fa173e0480750/filesystem.rar-e40ac13931b7ec47/contents/

          09:03:52,367 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/Filesystem]

          09:05:13,004 INFO  [org.jboss.as.server#handleResult] JBAS018559: Deployed "filesystem.rar"

           

          Seems something has been broken from 1.0.12 to 1.0.13.

          • 2. Re: trouble with RAR with ResourceAdapter
            Jesper Pedersen Master

            Are you running the latest snapshot of AS ?  Also .13 is more strict with rar deployments than .21 - but this looks like an issue in AS that is fixed...

            • 3. Re: trouble with RAR with ResourceAdapter
              Frank Langelage Master

              It's build from sources pulled from git as of yesterday evening.

              And with this current sources I replaced 1.0.13.Final by 1.0.12.Final in pom.xml and did a new build.

              So it seems to be not a problem in AS but in this specific ironjacamar version.

              • 4. Re: trouble with RAR with ResourceAdapter
                Jesper Pedersen Master

                Please, attach TRACE log for "org.jboss.jca" and "org.jboss.as.connector". And if possible the .rar itself - if not possible the report from the RAR info tool (IronJacamar 1.1.0.Beta3)

                • 5. Re: trouble with RAR with ResourceAdapter
                  Frank Langelage Master

                  OK, here you are.

                  The servere.log files using Ironjacamar 1.0.12 and 1.0.13 including TRACE logging.

                  Also attached the rar file as I deployed it and the sources for this, although they are not open source,

                  • 6. Re: trouble with RAR with ResourceAdapter
                    Jesper Pedersen Master

                    Just tried it on master, I see the ResourceAdapter being activated.

                     

                    Looking at your log it look like the @Connector bug we have fixed some time ago. You could try using IronJacamar 1.0.14-SNAPSHOT with master which will explode if the resourceadapter-class isn't defined. Or you could add a ra.xml file with just that element (as a work-around).

                     

                    filesystem.rar sounds like http://xadisk.java.net/ - but I didn't look at your source

                    • 7. Re: trouble with RAR with ResourceAdapter
                      Frank Langelage Master

                      Replacing IronJacamar 1.0.13.Final by 1.0.14-SNAPSHOT in the JBossAS7 build solves the problem.

                      And thanks for the hint to xadisk, was not aware of this. It seems worth looking a bit closer on it as a potential replacement for our adapater.

                      • 8. Re: trouble with RAR with ResourceAdapter
                        Frank Langelage Master

                        Mysteriously the problem reappeared suddenly.

                        Adding META-INF/ra.xml with this content

                        <?xml version="1.0" encoding="UTF-8"?>

                        <connector xmlns="http://java.sun.com/xml/ns/javaee"

                              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

                              xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/connector_1_6.xsd"

                              version="1.6">

                            <display-name>Filesystem</display-name>

                            <vendor-name>20-20 Technologies GmbH</vendor-name>

                            <eis-type>Filesystem</eis-type>

                            <resourceadapter-version>3.5</resourceadapter-version>

                            <resourceadapter>

                                <resourceadapter-class>biz.mbisoftware.fn.jca.filesystem.FilesystemResourceAdapter</resourceadapter-class>

                            </resourceadapter>

                        </connector>

                        the problem can be worked around.

                        • 9. Re: trouble with RAR with ResourceAdapter
                          Jesper Pedersen Master

                          If you have a test case for https://issues.jboss.org/browse/JBJCA-925 feel free to submit that