Skip to main content

EAR deployment problem for XA Datasource for DB2 using Type 4 driver

10 replies [Last post]
satyaranjan2006
Offline
Joined: 2009-03-05
Points: 0

I'm facing a problem while deploying the EAR in glassfish V2.It's not getting deployed as the process bar remains in the processing status for ever .In the server.log the following error appears.This is happening when I'm giving the JNDI of XA Datasource (for DB2 database ) in in sun-ejb-jar.xml file.

I am able to ping the connection pool for this datasource and it is successful.But not able to deploy the EAR.Incase of Non-XA datasource it is getting deployed.But for CMP EJB I need XA Datasource.

I'm using folowing jars for DB2
db2jcc.jar , db2jcc_javax.jar and db2jcc_license_cu.jar

The error I'm seeing in the log is :

Java.io.IOException: The filename, directory name, or volume label syntax is incorrect

at java.io.WinNTFileSystem.canonicalize0(Native Method)

at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:395)

at java.io.File.getCanonicalPath(File.java:531)

at com.sun.enterprise.loader.EJBClassLoader$1.run(EJBClassLoader.java:435)

at java.security.AccessController.doPrivileged(Native Method)

at com.sun.enterprise.loader.EJBClassLoader.findResource0(EJBClassLoader.java:405)

at com.sun.enterprise.loader.EJBClassLoader.findResources(EJBClassLoader.java:517)

at java.lang.ClassLoader.getResources(ClassLoader.java:1015)

at java.lang.ClassLoader.getResources(ClassLoader.java:1011)

at com.sun.naming.internal.VersionHelper12$5.run(VersionHelper12.java:145)

at java.security.AccessController.doPrivileged(Native Method)

at com.sun.naming.internal.VersionHelper12.getResources(VersionHelper12.java:142)

at com.sun.naming.internal.ResourceManager.getApplicationResources(ResourceManager.java:468)

at com.sun.naming.internal.ResourceManager.getInitialEnvironment(ResourceManager.java:159)

at javax.naming.InitialContext.init(InitialContext.java:219)

at javax.naming.InitialContext.(InitialContext.java:175)

at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.getConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:907)

at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.obtainManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.java:1027)

at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.getUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:1211)

at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.getConnection(ConnectorConnectionPoolAdminServiceImpl.java:1439)

at com.sun.enterprise.connectors.ConnectorRuntime.getConnection(ConnectorRuntime.java:1041)

at com.sun.jdo.spi.persistence.support.sqlstore.ejb.DeploymentHelper.getConnection(DeploymentHelper.java:173)

at com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.ensureDBSchemaExistence(MappingGenerator.java:763)

at com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.generateMapping(MappingGenerator.java:269)

at com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.loadOrCreateMappingClasses(JDOCodeGenerator.java:640)

at com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDOCodeGenerator.java:202)

at com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDOCodeGenerator.java:161)

at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:189)

at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:648)

at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:593)

at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:290)

at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:226)

at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:319)

at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:240)

at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148)

at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191)

at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)

at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)

at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279)

at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:788)

at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187)

at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223)
***********************************************

I need help urgently.I tried searching for solution couldn't get one.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Martin Gainty

no worries..no fault to be assigned..
i just sent a bug report to Sun on a JB PermGen stop error
(JB says JDK1.6.0.10 is'nt handling permgen space Garbage Collection properly..)
havent heard back from Sun but my guess theres a PermGen GC parameter that will fix this

the GUI tools available on Glassfish admin are so easy to work with compared to JB or resin
asadmin also is easy to work with and can script easily thru bash or cmd.exe execution environments
either way coding,configuring and deploy J2EE apps thru GF is a pleasure compared to other J2EE apps

My 2 pennies(..after taxes of course..)
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.

> Date: Thu, 5 Mar 2009 18:45:27 -0500
> From: armart3@tycho.ncsc.mil
> To: users@glassfish.dev.java.net
> Subject: RE: Re: EAR deployment problem for XA Datasource for DB2 using Type 4 driver
>
> I haven't decided that it is not my fault just yet.
> I don't think so, but I do not really know.
> The command line is serving me well for now until I learn more.
> Thanx.
>
> -----Original Message-----
> From: Rochelle.Raccah@Sun.COM [mailto:Rochelle.Raccah@Sun.COM]
> Sent: Thursday, March 05, 2009 6:32 PM
> To: users@glassfish.dev.java.net
> Subject: Re: EAR deployment problem for XA Datasource for DB2 using Type
> 4 driver
>
> If your Netbeans deployment takes 2 hours, you should probably file a
> bug with details against NB/serverplugins.
>
> Rochelle
>
> Martin, Ray wrote:
> > I would suggest deploying from the command line.
> > For me Netbeans takes 2 hours to deploy my ear - command line 5
> > minutes
> >
> > Hopefully, someone will be able to shed light on the error.
> >
> > -----Original Message-----
> > From: glassfish@javadesktop.org [mailto:glassfish@javadesktop.org]
> > Sent: Thursday, March 05, 2009 3:43 AM
> > To: users@glassfish.dev.java.net
> > Subject: EAR deployment problem for XA Datasource for DB2 using Type 4
>
> > driver
> >
> > I'm facing a problem while deploying the EAR in glassfish V2.It's not
> > getting deployed as the process bar remains in the processing status
> > for ever .In the server.log the following error appears.This is
> > happening when I'm giving the JNDI of XA Datasource (for DB2 database
> > ) in in sun-ejb-jar.xml file.
> >
> > I am able to ping the connection pool for this datasource and it is
> > successful.But not able to deploy the EAR.Incase of Non-XA datasource
> > it is getting deployed.But for CMP EJB I need XA Datasource.
> >
> > I'm using folowing jars for DB2
> > db2jcc.jar , db2jcc_javax.jar and db2jcc_license_cu.jar
> >
> > The error I'm seeing in the log is :
> >
> >
> > Java.io.IOException: The filename, directory name, or volume label
> > syntax is incorrect
> >
> > at java.io.WinNTFileSystem.canonicalize0(Native Method)
> >
> > at
> > java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:395)
> >
> > at java.io.File.getCanonicalPath(File.java:531)
> >
> > at
> > com.sun.enterprise.loader.EJBClassLoader$1.run(EJBClassLoader.java:435
> > )
> >
> > at java.security.AccessController.doPrivileged(Native
> > Method)
> >
> > at
> > com.sun.enterprise.loader.EJBClassLoader.findResource0(EJBClassLoader.
> > ja
> > va:405)
> >
> > at
> > com.sun.enterprise.loader.EJBClassLoader.findResources(EJBClassLoader.
> > ja
> > va:517)
> >
> > at
> > java.lang.ClassLoader.getResources(ClassLoader.java:1015)
> >
> > at
> > java.lang.ClassLoader.getResources(ClassLoader.java:1011)
> >
> > at
> > com.sun.naming.internal.VersionHelper12$5.run(VersionHelper12.java:145
> > )
> >
> > at java.security.AccessController.doPrivileged(Native
> > Method)
> >
> > at
> > com.sun.naming.internal.VersionHelper12.getResources(VersionHelper12.j
> > av
> > a:142)
> >
> > at
> > com.sun.naming.internal.ResourceManager.getApplicationResources(Resour
> > ce
> > Manager.java:468)
> >
> > at
> > com.sun.naming.internal.ResourceManager.getInitialEnvironment(Resource
> > Ma
> > nager.java:159)
> >
> > at
> > javax.naming.InitialContext.init(InitialContext.java:219)
> >
> > at
> > javax.naming.InitialContext.(InitialContext.java:175)
> >
> > at
> > com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.
> > ge
> > tConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:
> > 90
> > 7)
> >
> > at
> > com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.
> > ob
> > tainManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.j
> > av
> > a:1027)
> >
> > at
> > com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.
> > ge
> > tUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:1211)
> >
> > at
> > com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.
> > ge
> > tConnection(ConnectorConnectionPoolAdminServiceImpl.java:1439)
> >
> > at
> > com.sun.enterprise.connectors.ConnectorRuntime.getConnection(Connector
> > Ru
> > ntime.java:1041)
> >
> > at
> > com.sun.jdo.spi.persistence.support.sqlstore.ejb.DeploymentHelper.getC
> > on
> > nection(DeploymentHelper.java:173)
> >
> > at
> > com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.ensureDB
> > Sc
> > hemaExistence(MappingGenerator.java:763)
> >
> > at
> > com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.generate
> > Ma
> > pping(MappingGenerator.java:269)
> >
> > at
> > com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.loadOrCr
> > ea
> > teMappingClasses(JDOCodeGenerator.java:640)
> >
> > at
> > com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDO
> > Co
> > deGenerator.java:202)
> >
> > at
> > com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDO
> > Co
> > deGenerator.java:161)
> >
> > at
> > com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:189)
> >
> > at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:648)
> >
> > at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:593)
> >
> > at
> > com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBComp
> > il
> > er.java:290)
> >
> > at
> > com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.
> > ja
> > va:226)
> >
> > at
> > com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.
> > ja
> > va:319)
> >
> > at
> > com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.j
> > av
> > a:240)
> >
> > at
> > com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppD
> > ep
> > loyer.java:148)
> >
> > at
> > com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.j
> > av
> > a:191)
> >
> > at
> > com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(Dep
> > lo
> > ymentPhase.java:108)
> >
> > at
> > com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhase
> > s(
> > PEDeploymentService.java:919)
> >
> > at
> > com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDep
> > lo
> > ymentService.java:279)
> >
> > at
> > com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDep
> > lo
> > ymentService.java:788)
> >
> > at
> > com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.
> > ja
> > va:187)
> >
> > at
> >
> com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:
> > 223)
> > ***********************************************
> >
> >
> > I need help urgently.I tried searching for solution couldn't get one.
> > [Message sent by forum member 'satyaranjan2006' (satyaranjan2006)]
> >
> > http://forums.java.net/jive/thread.jspa?messageID=335226
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > For additional commands, e-mail: users-help@glassfish.dev.java.net
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > For additional commands, e-mail: users-help@glassfish.dev.java.net
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

_________________________________________________________________
Express your personality in color! Preview and select themes for Hotmail®.
http://www.windowslive-hotmail.com/LearnMore/personalize.aspx?ocid=TXT_M...
[att1.html]

satyaranjan2006
Offline
Joined: 2009-03-05
Points: 0

Can anyone tell me the solution to this problem?I'm not able to get rid of that.

Rochelle Raccah

If your Netbeans deployment takes 2 hours, you should probably file a
bug with details against NB/serverplugins.

Rochelle

Martin, Ray wrote:
> I would suggest deploying from the command line.
> For me Netbeans takes 2 hours to deploy my ear - command line 5 minutes
>
> Hopefully, someone will be able to shed light on the error.
>
> -----Original Message-----
> From: glassfish@javadesktop.org [mailto:glassfish@javadesktop.org]
> Sent: Thursday, March 05, 2009 3:43 AM
> To: users@glassfish.dev.java.net
> Subject: EAR deployment problem for XA Datasource for DB2 using Type 4
> driver
>
> I'm facing a problem while deploying the EAR in glassfish V2.It's not
> getting deployed as the process bar remains in the processing status for
> ever .In the server.log the following error appears.This is happening
> when I'm giving the JNDI of XA Datasource (for DB2 database ) in
> in sun-ejb-jar.xml file.
>
> I am able to ping the connection pool for this datasource and it is
> successful.But not able to deploy the EAR.Incase of Non-XA datasource it
> is getting deployed.But for CMP EJB I need XA Datasource.
>
> I'm using folowing jars for DB2
> db2jcc.jar , db2jcc_javax.jar and db2jcc_license_cu.jar
>
> The error I'm seeing in the log is :
>
>
> Java.io.IOException: The filename, directory name, or volume label
> syntax is incorrect
>
> at java.io.WinNTFileSystem.canonicalize0(Native Method)
>
> at
> java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:395)
>
> at java.io.File.getCanonicalPath(File.java:531)
>
> at
> com.sun.enterprise.loader.EJBClassLoader$1.run(EJBClassLoader.java:435)
>
> at java.security.AccessController.doPrivileged(Native
> Method)
>
> at
> com.sun.enterprise.loader.EJBClassLoader.findResource0(EJBClassLoader.ja
> va:405)
>
> at
> com.sun.enterprise.loader.EJBClassLoader.findResources(EJBClassLoader.ja
> va:517)
>
> at java.lang.ClassLoader.getResources(ClassLoader.java:1015)
>
> at java.lang.ClassLoader.getResources(ClassLoader.java:1011)
>
> at
> com.sun.naming.internal.VersionHelper12$5.run(VersionHelper12.java:145)
>
> at java.security.AccessController.doPrivileged(Native
> Method)
>
> at
> com.sun.naming.internal.VersionHelper12.getResources(VersionHelper12.jav
> a:142)
>
> at
> com.sun.naming.internal.ResourceManager.getApplicationResources(Resource
> Manager.java:468)
>
> at
> com.sun.naming.internal.ResourceManager.getInitialEnvironment(ResourceMa
> nager.java:159)
>
> at javax.naming.InitialContext.init(InitialContext.java:219)
>
> at
> javax.naming.InitialContext.(InitialContext.java:175)
>
> at
> com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.ge
> tConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:90
> 7)
>
> at
> com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.ob
> tainManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.jav
> a:1027)
>
> at
> com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.ge
> tUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:1211)
>
> at
> com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.ge
> tConnection(ConnectorConnectionPoolAdminServiceImpl.java:1439)
>
> at
> com.sun.enterprise.connectors.ConnectorRuntime.getConnection(ConnectorRu
> ntime.java:1041)
>
> at
> com.sun.jdo.spi.persistence.support.sqlstore.ejb.DeploymentHelper.getCon
> nection(DeploymentHelper.java:173)
>
> at
> com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.ensureDBSc
> hemaExistence(MappingGenerator.java:763)
>
> at
> com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.generateMa
> pping(MappingGenerator.java:269)
>
> at
> com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.loadOrCrea
> teMappingClasses(JDOCodeGenerator.java:640)
>
> at
> com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDOCo
> deGenerator.java:202)
>
> at
> com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDOCo
> deGenerator.java:161)
>
> at
> com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:189)
>
> at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:648)
>
> at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:593)
>
> at
> com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompil
> er.java:290)
>
> at
> com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.ja
> va:226)
>
> at
> com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.ja
> va:319)
>
> at
> com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.jav
> a:240)
>
> at
> com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDep
> loyer.java:148)
>
> at
> com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.jav
> a:191)
>
> at
> com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(Deplo
> ymentPhase.java:108)
>
> at
> com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(
> PEDeploymentService.java:919)
>
> at
> com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeplo
> ymentService.java:279)
>
> at
> com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeplo
> ymentService.java:788)
>
> at
> com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.ja
> va:187)
>
> at
> com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:
> 223)
> ***********************************************
>
>
> I need help urgently.I tried searching for solution couldn't get one.
> [Message sent by forum member 'satyaranjan2006' (satyaranjan2006)]
>
> http://forums.java.net/jive/thread.jspa?messageID=335226
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Martin, Ray

I haven't decided that it is not my fault just yet.
I don't think so, but I do not really know.
The command line is serving me well for now until I learn more.
Thanx.

-----Original Message-----
From: Rochelle.Raccah@Sun.COM [mailto:Rochelle.Raccah@Sun.COM]
Sent: Thursday, March 05, 2009 6:32 PM
To: users@glassfish.dev.java.net
Subject: Re: EAR deployment problem for XA Datasource for DB2 using Type
4 driver

If your Netbeans deployment takes 2 hours, you should probably file a
bug with details against NB/serverplugins.

Rochelle

Martin, Ray wrote:
> I would suggest deploying from the command line.
> For me Netbeans takes 2 hours to deploy my ear - command line 5
> minutes
>
> Hopefully, someone will be able to shed light on the error.
>
> -----Original Message-----
> From: glassfish@javadesktop.org [mailto:glassfish@javadesktop.org]
> Sent: Thursday, March 05, 2009 3:43 AM
> To: users@glassfish.dev.java.net
> Subject: EAR deployment problem for XA Datasource for DB2 using Type 4

> driver
>
> I'm facing a problem while deploying the EAR in glassfish V2.It's not
> getting deployed as the process bar remains in the processing status
> for ever .In the server.log the following error appears.This is
> happening when I'm giving the JNDI of XA Datasource (for DB2 database
> ) in in sun-ejb-jar.xml file.
>
> I am able to ping the connection pool for this datasource and it is
> successful.But not able to deploy the EAR.Incase of Non-XA datasource
> it is getting deployed.But for CMP EJB I need XA Datasource.
>
> I'm using folowing jars for DB2
> db2jcc.jar , db2jcc_javax.jar and db2jcc_license_cu.jar
>
> The error I'm seeing in the log is :
>
>
> Java.io.IOException: The filename, directory name, or volume label
> syntax is incorrect
>
> at java.io.WinNTFileSystem.canonicalize0(Native Method)
>
> at
> java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:395)
>
> at java.io.File.getCanonicalPath(File.java:531)
>
> at
> com.sun.enterprise.loader.EJBClassLoader$1.run(EJBClassLoader.java:435
> )
>
> at java.security.AccessController.doPrivileged(Native
> Method)
>
> at
> com.sun.enterprise.loader.EJBClassLoader.findResource0(EJBClassLoader.
> ja
> va:405)
>
> at
> com.sun.enterprise.loader.EJBClassLoader.findResources(EJBClassLoader.
> ja
> va:517)
>
> at
> java.lang.ClassLoader.getResources(ClassLoader.java:1015)
>
> at
> java.lang.ClassLoader.getResources(ClassLoader.java:1011)
>
> at
> com.sun.naming.internal.VersionHelper12$5.run(VersionHelper12.java:145
> )
>
> at java.security.AccessController.doPrivileged(Native
> Method)
>
> at
> com.sun.naming.internal.VersionHelper12.getResources(VersionHelper12.j
> av
> a:142)
>
> at
> com.sun.naming.internal.ResourceManager.getApplicationResources(Resour
> ce
> Manager.java:468)
>
> at
> com.sun.naming.internal.ResourceManager.getInitialEnvironment(Resource
> Ma
> nager.java:159)
>
> at
> javax.naming.InitialContext.init(InitialContext.java:219)
>
> at
> javax.naming.InitialContext.(InitialContext.java:175)
>
> at
> com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.
> ge
> tConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:
> 90
> 7)
>
> at
> com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.
> ob
> tainManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.j
> av
> a:1027)
>
> at
> com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.
> ge
> tUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:1211)
>
> at
> com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.
> ge
> tConnection(ConnectorConnectionPoolAdminServiceImpl.java:1439)
>
> at
> com.sun.enterprise.connectors.ConnectorRuntime.getConnection(Connector
> Ru
> ntime.java:1041)
>
> at
> com.sun.jdo.spi.persistence.support.sqlstore.ejb.DeploymentHelper.getC
> on
> nection(DeploymentHelper.java:173)
>
> at
> com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.ensureDB
> Sc
> hemaExistence(MappingGenerator.java:763)
>
> at
> com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.generate
> Ma
> pping(MappingGenerator.java:269)
>
> at
> com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.loadOrCr
> ea
> teMappingClasses(JDOCodeGenerator.java:640)
>
> at
> com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDO
> Co
> deGenerator.java:202)
>
> at
> com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDO
> Co
> deGenerator.java:161)
>
> at
> com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:189)
>
> at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:648)
>
> at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:593)
>
> at
> com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBComp
> il
> er.java:290)
>
> at
> com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.
> ja
> va:226)
>
> at
> com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.
> ja
> va:319)
>
> at
> com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.j
> av
> a:240)
>
> at
> com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppD
> ep
> loyer.java:148)
>
> at
> com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.j
> av
> a:191)
>
> at
> com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(Dep
> lo
> ymentPhase.java:108)
>
> at
> com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhase
> s(
> PEDeploymentService.java:919)
>
> at
> com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDep
> lo
> ymentService.java:279)
>
> at
> com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDep
> lo
> ymentService.java:788)
>
> at
> com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.
> ja
> va:187)
>
> at
>
com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:
> 223)
> ***********************************************
>
>
> I need help urgently.I tried searching for solution couldn't get one.
> [Message sent by forum member 'satyaranjan2006' (satyaranjan2006)]
>
> http://forums.java.net/jive/thread.jspa?messageID=335226
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Vince Kraemer

Hi Martin,

If an IDE takes two hours to do something... it is unlikely that it is
your fault.

Please take a few minutes to describe your situation in a bug report.

That will get the ball rolling.
http://www.netbeans.org/community/issues.html

Note: even if the situation is 'your fault', we may be able to recommend
a change in how you are using the IDE to improve the situation...
sometime significantly.

thanks,
vbk

Martin, Ray wrote:
> I haven't decided that it is not my fault just yet.
> I don't think so, but I do not really know.
> The command line is serving me well for now until I learn more.
> Thanx.
>
> -----Original Message-----
> From: Rochelle.Raccah@Sun.COM [mailto:Rochelle.Raccah@Sun.COM]
> Sent: Thursday, March 05, 2009 6:32 PM
> To: users@glassfish.dev.java.net
> Subject: Re: EAR deployment problem for XA Datasource for DB2 using Type
> 4 driver
>
> If your Netbeans deployment takes 2 hours, you should probably file a
> bug with details against NB/serverplugins.
>
> Rochelle
>
> Martin, Ray wrote:
>
>> I would suggest deploying from the command line.
>> For me Netbeans takes 2 hours to deploy my ear - command line 5
>> minutes
>>
>> Hopefully, someone will be able to shed light on the error.
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

mvatkina
Offline
Joined: 2005-04-04
Points: 0

Did you solve the IOException problem?

thanks,
-marina

Martin, Ray

I would suggest deploying from the command line.
For me Netbeans takes 2 hours to deploy my ear - command line 5 minutes

Hopefully, someone will be able to shed light on the error.

-----Original Message-----
From: glassfish@javadesktop.org [mailto:glassfish@javadesktop.org]
Sent: Thursday, March 05, 2009 3:43 AM
To: users@glassfish.dev.java.net
Subject: EAR deployment problem for XA Datasource for DB2 using Type 4
driver

I'm facing a problem while deploying the EAR in glassfish V2.It's not
getting deployed as the process bar remains in the processing status for
ever .In the server.log the following error appears.This is happening
when I'm giving the JNDI of XA Datasource (for DB2 database ) in
in sun-ejb-jar.xml file.

I am able to ping the connection pool for this datasource and it is
successful.But not able to deploy the EAR.Incase of Non-XA datasource it
is getting deployed.But for CMP EJB I need XA Datasource.

I'm using folowing jars for DB2
db2jcc.jar , db2jcc_javax.jar and db2jcc_license_cu.jar

The error I'm seeing in the log is :

Java.io.IOException: The filename, directory name, or volume label
syntax is incorrect

at java.io.WinNTFileSystem.canonicalize0(Native Method)

at
java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:395)

at java.io.File.getCanonicalPath(File.java:531)

at
com.sun.enterprise.loader.EJBClassLoader$1.run(EJBClassLoader.java:435)

at java.security.AccessController.doPrivileged(Native
Method)

at
com.sun.enterprise.loader.EJBClassLoader.findResource0(EJBClassLoader.ja
va:405)

at
com.sun.enterprise.loader.EJBClassLoader.findResources(EJBClassLoader.ja
va:517)

at java.lang.ClassLoader.getResources(ClassLoader.java:1015)

at java.lang.ClassLoader.getResources(ClassLoader.java:1011)

at
com.sun.naming.internal.VersionHelper12$5.run(VersionHelper12.java:145)

at java.security.AccessController.doPrivileged(Native
Method)

at
com.sun.naming.internal.VersionHelper12.getResources(VersionHelper12.jav
a:142)

at
com.sun.naming.internal.ResourceManager.getApplicationResources(Resource
Manager.java:468)

at
com.sun.naming.internal.ResourceManager.getInitialEnvironment(ResourceMa
nager.java:159)

at javax.naming.InitialContext.init(InitialContext.java:219)

at
javax.naming.InitialContext.(InitialContext.java:175)

at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.ge
tConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:90
7)

at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.ob
tainManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.jav
a:1027)

at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.ge
tUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:1211)

at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.ge
tConnection(ConnectorConnectionPoolAdminServiceImpl.java:1439)

at
com.sun.enterprise.connectors.ConnectorRuntime.getConnection(ConnectorRu
ntime.java:1041)

at
com.sun.jdo.spi.persistence.support.sqlstore.ejb.DeploymentHelper.getCon
nection(DeploymentHelper.java:173)

at
com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.ensureDBSc
hemaExistence(MappingGenerator.java:763)

at
com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.generateMa
pping(MappingGenerator.java:269)

at
com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.loadOrCrea
teMappingClasses(JDOCodeGenerator.java:640)

at
com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDOCo
deGenerator.java:202)

at
com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDOCo
deGenerator.java:161)

at
com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:189)

at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:648)

at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:593)

at
com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompil
er.java:290)

at
com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.ja
va:226)

at
com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.ja
va:319)

at
com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.jav
a:240)

at
com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDep
loyer.java:148)

at
com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.jav
a:191)

at
com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(Deplo
ymentPhase.java:108)

at
com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(
PEDeploymentService.java:919)

at
com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeplo
ymentService.java:279)

at
com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeplo
ymentService.java:788)

at
com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.ja
va:187)

at
com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:
223)
***********************************************

I need help urgently.I tried searching for solution couldn't get one.
[Message sent by forum member 'satyaranjan2006' (satyaranjan2006)]

http://forums.java.net/jive/thread.jspa?messageID=335226

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

satyaranjan2006
Offline
Joined: 2009-03-05
Points: 0

I did't use Net Beans.I generated the EAR through build script using ANT and then tried to deploy though admin console.

Martin Gainty

/****start of IBM Doc for configuring DB2 XA Data Source*****/

http://www.ibm.com/developerworks/websphere/library/techarticles/0407_wo...

Configure a DB2 XA data source

This example also includes a DB2 XA data source. The configuration
settings for a DB2 data source are very similar to those for an Oracle
data source.

First, define a JAAS identity capable of logging into your database. In this example, we've set up one named DB2.

DB2 JAAS authentication entry settings

Property nameProperty ValueDefault?AliasDB2
User IDdb2
Passworda_password

Second, we need to create a JDBC provider for DB2 XA data sources.

DB2 JDBC provider settings

Property NameProperty ValueDefault?JDBC Provider typeDB2 Universal JDBC Driver Provider (XA)
Name
DB2 Universal JDBC Driver Provider (XA)
Implementation class namecom.ibm.db2.jcc.DB2XADataSourcedefaultClass path
${DB2UNIVERSAL_JDBC_DRIVER_PATH}}/db2jcc.jar

${UNIVERSAL_JDBC_DRIVER_PATH}}/db2jcc_license_cu.jar

${DB2UNIVERSAL_JDBC_DRIVER_PATH}}/db2jcc_license_cisuz.jar

default

Third, we need to create a DB2 XA data source with the JNDI name jdbc/DB2XADS. We'll use the JAAS identity from
step 1. Whereas an Oracle data source needs a URL string for accessing the database, a DB2 data source
just needs the name of the database, in this case, "sample."

DB2 JDBC data source settings

Property NameProperty ValueDefault?JDBC Provider typeDB2 Universal JDBC Driver Provider (XA), version 5.0
NameExample DB2 XA Data Source
JNDI namejdbc/DB2XADS
Helper classcom.ibm.websphere.rsadapter.DB2UniversalDataStoreHelperdefaultAuthentication aliasDB2
databaseNamesample

Fourth, we need to specify the path where the DB2 drivers are installed, which is the directory that contains the db2jcc.jar
file. Also, verify the default value of the other variable in the data source's class path.

DB2 defined variables (for nodes) settings

Property NameProperty ValueDefault?DB2UNIVERSAL_JDBC_DRIVER_PATHC:\db2\SQLLIB\java
UNIVERSAL_JDBC_DRIVER_PATH${WAS_INSTALL_ROOT}/universalDriver/libdefault

You have now configured a DB2 XA data source registered as jdbc/DB2XADS. Save the server configuration.
/********end doc********/
http://www.ibm.com/developerworks/websphere/library/techarticles/0407_wo...

HTH
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.

> Date: Thu, 5 Mar 2009 04:28:18 -0800
> From: glassfish@javadesktop.org
> To: users@glassfish.dev.java.net
> Subject: Re: RE: EAR deployment problem for XA Datasource for DB2 using Type 4 driver
>
> I did't use Net Beans.I generated the EAR through build script using ANT and then tried to deploy though admin console.
> [Message sent by forum member 'satyaranjan2006' (satyaranjan2006)]
>
> http://forums.java.net/jive/thread.jspa?messageID=335260
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

_________________________________________________________________
Windows Liveâ„¢: Life without walls.
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_allup_1a_explore_032009
[att1.html]

satyaranjan2006
Offline
Joined: 2009-03-05
Points: 0

I configured the connection pool for DB2 using the following drivers.

com.ibm.db2.jcc.DB2XADataSource (For XA) and the JNDI name is jdbc/xaDS
com.ibm.db2.jcc.DB2DataSource(For Non-XA).and JNDI name is jdbc/nonXADS

But when I'm using jdbc/nonXADS as then the EAR is getting deployed.But when using jdbc/xaDS then it's not getting deployed.