Log4j problem -creating directory

My Log4j.properties is as follows:
log4j.rootLogger=info,stdout, R
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%c %d{ISO8601} -- %p -- %m%n
log4j.logger.org.apache.commons=INFO
log4j.logger.org.apache.struts=INFO
log4j.logger.org.hibernate=INFO
log4j.appender.R=org.apache.log4j.DailyRollingFileAppender
log4j.appender.R.File=../CustomeLog/myLog
log4j.appender.R.datePattern='_'MM-dd-yyyy'.txt'
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n
CustomLog folder does not exist in tomcat home directory.. i want it to be created automatically. i have written servlet for that. but problem is that servlet is read after log4.properties.. so tomcat gives me error fileNotFound as it cannot get CustomLog folder..
can anybody help me on this issue?? My aim is that whenever tomcat starts, customLogs folder shud be created if it doesnot exists.. log4j takes the care of the rest..

See if this forum thread helps:
http://forums.sun.com/thread.jspa?threadID=5193205

Similar Messages

Problem creating directory entry

InitialLdapContext is created using INITIAL_CONTEXT_FACTORY = com.sun.jndi.ldap.LdapCtxFactory. The following call attempts to create an entry in the directory:
context.createSubcontext("gid=BLANK,ou=ouname,dc=dcname", Attributes);
In this scenario:
-Will jndi send to the directory an attribute named gid with a value of
BLANK if said attributed is not explicitly provided in the Attributes
object?
- If so, can this behavior be overridden?

Hi,
JNDI will not send gid attribute with the said value in the DN. You have to specify the attribute value in the attribute list if you want to add it to the entry.

Problem creating directory configuration for BPM when using secure ldap

I have all the configuration sorted for the creation, but when the config wizard tries to connect to the server I get this:
fuego.directory.DirectoryRuntimeException: Exception [sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target].
I'm assuming it's because the config tool isn't using my keyStore, but I am unable to find out where I add this!
Thanks
mARK

Hi,
The problem got resolved when we tried same thing in BI publisher 10.1.3.4.2 (xmlpserver) in weblogic 10.3.5. It seems that BI publisher 10.1.3.4.1 does not have dynamic URI support.
Thanks,
Sanjaya
Edited by: Sanjaya on Sep 4, 2012 2:09 AM

Having problems installing firefox error msg says error creating directory c:\programme files (x86)\mozilla firefox\searchplugins

Hi, I have been having problems with Internet Explorer 8 using Windows 7 so wanted to install Firefox but unable to as get a message saying error creating directory c:\programme files (x86)\mozilla firefox\searchplugins

Thank you guig2! Followed your bleepingcomputer.com link above and found the problem was my permissions on C:\Users\Bill\AppData\Local/Temp. It was not "Full Control" for my User or Administrator. Updated the two lines to permit full control for folder, subfolder and files. Ran perfect.

Can not create directory error while creating database

i am creating database using dbca in oel but when i try to do so i get an error saying can not create directory pawii
and pawii is the sid
actually oracle is installed on u01 and i am creating database in u02
but this error is not allowing me to create database but when i try to create database in uo1 the database installed successfully but this is not happening when i try to create database in another mount point u02

987018 wrote:
so finally i had solved the problem myself as people like rukbat are very unhelpful in nature here
all we had to do is we had to change the group of the folder to oracle and oinstall where we are going to create our new database :)Actually he tries to be quite helpful. But sometimes the help you need isn't the help you want.
"When you need me but do not want me, then I must stay. When you want me but no longer need me, then I have to go." (Nanny McPhee)

Create directory utl_file errors

I thought that I would be able to answer my problem with all the help I've seen online. I don't seem to be able to.
I have the following code (snippet) below from my procedure:
v_file varchar2(100);
v_direc constant varchar2(30) := 'c:\output\';
v_testfile UTL_FILE.FILE_TYPE;
BEGIN
v_testfile := utl_file.fopen('C:\output', 'JohnsUIICounts.txt', 'w');
open csr_uii;
loop
fetch csr_uii into csr_uii_a, csr_uii_b, csr_uii_c, csr_uii_d;
exit when csr_uii%NOTFOUND;
utl_file.put_line(v_testfile, csr_uii_a || ' ' || csr_uii_b || ' '|| csr_uii_c || ' '|| csr_uii_d);
end loop;
I logged on to SQL Developer and did:
CREATE DIRECTORY V_DIREC AS 'C:\output\';
GRANT WRITE ON DIRECTORY V_DIREC TO PUBLIC;
I got the message back that the directory was created. When I go to the c:\ drive, I don't see the directory.
Any ideas? I've gone through all sorts of iterations like changing the drive from c to e, different folder names, upper and lower case, nothing works.
Victoria

Thanks. Now that I understand that, I created the directory on the server. I reran the code. I'm still getting:
ORA-29280: invalid directory path
ORA-06512: at "SYS.UTL_FILE", line 33
ORA-06512: at "SYS.UTL_FILE", line 436
I notice that on the Windows Server, when I create the directory (as an admin user), I check on the properties, and it keeps staying read only. I can modify it, but the change doesn't save. I heard something about group permissions. Is it possible that the problem is because of permissions on the server? I would think that might be the real problem at this point.
Thanks,
Victoria
Edited by: user3804901 on May 20, 2009 4:31 AM

Can't create directory while in fakeroot

Hi all,
I'm trying to create a PKGBUILD for mplabx. When the installer tries to create the directory /opt/microchip, it gets the error permission denied.
My pkgbuild:
# This is an example PKGBUILD file. Use this as a start to creating your own,
# and remove these comments. For more information, see 'man PKGBUILD'.
# NOTE: Please fill out the license field for your package! If it is unknown,
# then please put 'unknown'.
# Maintainer: Cedric de Wijs <[email protected]>
pkgname=microchip_mplab-x
pkgver=7.02
pkgrel=1
epoch=
pkgdesc=""
arch=('x86_64')
url="http://www.microchip.com/en_US/family/mplabx/index.html"
license=('unknown')
groups=()
depends=()
makedepends=()
checkdepends=()
optdepends=()
provides=()
conflicts=()
replaces=()
backup=()
options=()
install=
changelog=
source=(http://ww1.microchip.com/downloads/mplab/X_Beta/mplabx-ide-beta7.02-linux-64-bit-installer.bin)
noextract=()
md5sums=('fbe573dabb54120947bbefaa2d8003d4')
build() {
whoami
check() {
whoami
package() {
whoami
chmod +x mplabx-ide-beta7.02-linux-64-bit-installer.bin
mkdir -p /opt
mkdir /opt/microchip
mkdir /opt/microchip/mplabx
./mplabx-ide-beta7.02-linux-64-bit-installer.bin
The console output:
$ makepkg
==> Making package: microchip_mplab-x 7.02-1 (Mon Sep 26 07:42:15 CEST 2011)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
-> Found mplabx-ide-beta7.02-linux-64-bit-installer.bin
==> Validating source files with md5sums...
mplabx-ide-beta7.02-linux-64-bit-installer.bin ... Passed
==> Extracting Sources...
==> Removing existing pkg/ directory...
==> Starting build()...
cedric
==> Starting check()...
cedric
==> Entering fakeroot environment...
==> Starting package()...
root
mkdir: cannot create directory `/opt/microchip': Permission denied
==> ERROR: A failure occurred in package().
Aborting...
When I create the directory /opt/microchip (in the real root), the above error changes:
$ su
Password:
[root@cedric mplab-test]# mkdir /opt/microchip
[root@cedric mplab-test]# exit
exit
[cedric@cedric mplab-test]$ makepkg
==> Making package: microchip_mplab-x 7.02-1 (Mon Sep 26 07:45:15 CEST 2011)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
-> Found mplabx-ide-beta7.02-linux-64-bit-installer.bin
==> Validating source files with md5sums...
mplabx-ide-beta7.02-linux-64-bit-installer.bin ... Passed
==> Extracting Sources...
==> Removing existing pkg/ directory...
==> Starting build()...
cedric
==> Starting check()...
cedric
==> Entering fakeroot environment...
==> Starting package()...
root
mkdir: cannot create directory `/opt/microchip': File exists
==> ERROR: A failure occurred in package().
Aborting...
What can I do to get around this?
Best regards,
Cedric

Thanks. I have now adjusted the PKGBUILD as such
# This is an example PKGBUILD file. Use this as a start to creating your own,
# and remove these comments. For more information, see 'man PKGBUILD'.
# NOTE: Please fill out the license field for your package! If it is unknown,
# then please put 'unknown'.
# Maintainer: Cedric de Wijs <[email protected]>
pkgname=microchip_mplab-x
pkgver=7.02
pkgrel=1
epoch=
pkgdesc=""
arch=('x86_64')
url="http://www.microchip.com/en_US/family/mplabx/index.html"
license=('unknown')
groups=()
depends=()
makedepends=()
checkdepends=()
optdepends=()
provides=()
conflicts=()
replaces=()
backup=()
options=()
install=
changelog=
source=(http://ww1.microchip.com/downloads/mplab/X_Beta/mplabx-ide-beta7.02-linux-64-bit-installer.bin)
noextract=()
md5sums=('fbe573dabb54120947bbefaa2d8003d4')
build() {
whoami
check() {
whoami
package() {
whoami
chmod +x mplabx-ide-beta7.02-linux-64-bit-installer.bin
install -d "$pkgdir"/opt/microchip/mplabx
./mplabx-ide-beta7.02-linux-64-bit-installer.bin
The directories are no made without problems, but the mplab installer still complains it can't create the directories.
$ makepkg
==> Making package: microchip_mplab-x 7.02-1 (Mon Sep 26 08:04:04 CEST 2011)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
-> Found mplabx-ide-beta7.02-linux-64-bit-installer.bin
==> Validating source files with md5sums...
mplabx-ide-beta7.02-linux-64-bit-installer.bin ... Passed
==> Extracting Sources...
==> Removing existing pkg/ directory...
==> Starting build()...
cedric
==> Starting check()...
cedric
==> Entering fakeroot environment...
==> Starting package()...
root
ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded: ignored.
==> ERROR: A failure occurred in package().
Aborting...
It looks like makepkg only runs install in the fakeroot. Is there any way a binary installer can be run inside the fakeroot?
Am I going in the right direction, or is there no way to run a binary installer like this?
Are there other binary installers that are run like this?
Best regards,
Cedric
Last edited by cdwijs (2011-09-26 06:32:06)

Creating Directory Errors

I get two error messages when I try to install 7.1
After itunes installs the update and it is going through it's last step (looks almost complete), I get the following error:
"An error occurred while attempting to create the directory:
C:\WINDOWS\Installer\{50D8FFDD-90CD-4859-841F-AA1961C7767A}"
After I click on cancel, another box appears with this message:
"The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2330."
I've updated my windows software and removed itunes from my computer prior to this install, but still no luck. Suggestions?

Hi,
In general I don't have problems creating folders in my directory. However, I can't locate a C:C:\WINDOWS\Installer\ folder. When I try to creat a folder called "installer" in the windows directory, i get an error saying the file already exists.
I do see a folder in c:\windows\ called "Downloaded Installations". It has the installer packages for ipod and itunes from successful updates over the years.
I tried to create a folder called {50D8FFDD-90CD-4859-841F-AA1961C7767A} in the "Downloaded Installations" folder. I was able to create the folder, but the iTunes update still didn't work. I ended up getting the same error message, but this time it had a different number than the one above (the 50D8FFDD-etc....number).
What should I do next? I really appreciate the help.
Are you getting errors about creating folders there?
Try creating the folder where you get the errors.
"An error occurred while attempting to create the
directory:
C:\WINDOWS\Installer\{50D8FFDD-90CD-4859-841F-AA1961C7
767A}
If you can't create the above folder by hand then its
possibly a permission problem. I don't think the run
as adminstrator works well. So make sure you are in
the adminstrators group or logged in as the admin.

Problem creating deployment weblogic 5.1

I have weblogic 5.1 running on Win2K. I can start it up without
problems when the deployment part is commented out.
The jdbc connection seems to be working with a Oracle 8.1.7
running on the same Win2K box.
When I try to deploy some EJBs I get this error on startup:
<error>
Thu Nov 07 12:59:31 CST 2002:<E> <EJB> Could not deploy:
'C:\apps\web\weblogic\mycluster\lib\ErfpLibrary.jar': file is not a
valid jar file, or does not contain a valid bean
</error>
here's the full error output:
Any ideas on what's missing here?
<full_output>
Thu Nov 07 12:59:31 CST 2002:<E> <EJB> Could not deploy:
'C:\apps\web\weblogic\m
ycluster\lib\ErfpLibrary.jar': file is not a valid jar file, or does
not
contain a valid bean
weblogic.ejb.common.DeploymentException: DeploymentException opening
JAR file C:
\apps\web\weblogic\mycluster\lib\ErfpLibrary.jar; nested exception is:
weblogic.ejb.deployment.JarLoadException - with nested
exception:
[weblogic.ejb.common.DeploymentException: Problem creating deployment
C:\apps\we
b\weblogic\mycluster\lib\ErfpLibrary.jar from
C:\apps\web\weblogic\mycluster\lib
\ErfpLibrary.jar; nested exception is:
java.lang.NoClassDefFoundError:
com/ebreviate/erfp/utils/ClusterInterfac
e]
weblogic.ejb.common.DeploymentException: Problem creating deployment
C:\apps\web
\weblogic\mycluster\lib\ErfpLibrary.jar from
C:\apps\web\weblogic\mycluster\lib\
ErfpLibrary.jar; nested exception is:
java.lang.NoClassDefFoundError:
com/ebreviate/erfp/utils/ClusterInterfac
e
java.lang.NoClassDefFoundError:
com/ebreviate/erfp/utils/ClusterInterface
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:488)
at java.lang.ClassLoader.defineClass(ClassLoader.java:423)
at weblogic.boot.ServerSecureClassLoader.secureDefineClass(ServerSecureC
lassLoader.java:143)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic
ClassLoader.java:495)
at weblogic.utils.classloaders.GenericClassLoader.reallyLoadClass(Generi
cClassLoader.java:339)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass
Loader.java:183)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass
Loader.java:157)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:310)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:488)
at java.lang.ClassLoader.defineClass(ClassLoader.java:423)
at weblogic.boot.ServerSecureClassLoader.secureDefineClass(ServerSecureC
lassLoader.java:143)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic
ClassLoader.java:495)
at weblogic.utils.classloaders.GenericClassLoader.reallyLoadClass(Generi
cClassLoader.java:339)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass
Loader.java:183)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass
Loader.java:157)
at weblogic.ejb.deployment.dd.DeploymentUnit.loadClass(DeploymentUnit.ja
va:101)
at weblogic.ejb.deployment.dd.DeploymentUnit.initializeMethodInfos(Deplo
ymentUnit.java:424)
at weblogic.ejb.internal.EJBJarLoader.initializeMethodInfos(EJBJarLoader
.java:129)
at weblogic.ejb.internal.EJBJarDeployment.setupJar(EJBJarDeployment.java
:392)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:21
1)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:18
2)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:16
4)
at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java
:172)
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:1
22)
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:1
12)
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:311)
at weblogic.ejb.internal.EJBManagerImpl.deployBeans(EJBManagerImpl.java:
653)
at weblogic.ejb.internal.EJBManagerImpl.<init>(EJBManagerImpl.java:247)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1386)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:879)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:140)
at weblogic.Server.main(Server.java:97)
at weblogic.Server.main(Server.java:58)
--------------- nested within: ------------------
weblogic.ejb.deployment.JarLoadException - with nested exception:
[weblogic.ejb.common.DeploymentException: Problem creating deployment
C:\apps\we
b\weblogic\mycluster\lib\ErfpLibrary.jar from
C:\apps\web\weblogic\mycluster\lib
\ErfpLibrary.jar; nested exception is:
java.lang.NoClassDefFoundError:
com/ebreviate/erfp/utils/ClusterInterfac
e]
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:319)
at weblogic.ejb.internal.EJBManagerImpl.deployBeans(EJBManagerImpl.java:
653)
at weblogic.ejb.internal.EJBManagerImpl.<init>(EJBManagerImpl.java:247)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1386)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:879)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:140)
at weblogic.Server.main(Server.java:97)
at weblogic.Server.main(Server.java:58)
Thu Nov 07 12:59:32 CST 2002:<I> <EJB> 0 EJB jar files loaded,
containing 0 EJBs
</full_output>

Generally we get this error when we did not packaged properly, like if use
tool win zip for packaging the bean.
1. when you are building EJB jar, please make sure that you have created a
directory "META-INF" with upper case letters
2. Make sure that you have deployment descriptors in 'META-INF".
3. Use Command line console, java command to package the bean like
"jar -cv0f".
ignore this mail, if you already done this way.
Can you try packaging your
"Sharkie" <[email protected]> wrote in message
news:[email protected]...
I have weblogic 5.1 running on Win2K. I can start it up without
problems when the deployment part is commented out.
The jdbc connection seems to be working with a Oracle 8.1.7
running on the same Win2K box.
When I try to deploy some EJBs I get this error on startup:
<error>
Thu Nov 07 12:59:31 CST 2002:<E> <EJB> Could not deploy:
'C:\apps\web\weblogic\mycluster\lib\ErfpLibrary.jar': file is not a
valid jar file, or does not contain a valid bean
</error>
here's the full error output:
Any ideas on what's missing here?
<full_output>
Thu Nov 07 12:59:31 CST 2002:<E> <EJB> Could not deploy:
'C:\apps\web\weblogic\m
ycluster\lib\ErfpLibrary.jar': file is not a valid jar file, or does
not
contain a valid bean
weblogic.ejb.common.DeploymentException: DeploymentException opening
JAR file C:
\apps\web\weblogic\mycluster\lib\ErfpLibrary.jar; nested exception is:
weblogic.ejb.deployment.JarLoadException - with nested
exception:
[weblogic.ejb.common.DeploymentException: Problem creating deployment
C:\apps\we
b\weblogic\mycluster\lib\ErfpLibrary.jar from
C:\apps\web\weblogic\mycluster\lib
\ErfpLibrary.jar; nested exception is:
java.lang.NoClassDefFoundError:
com/ebreviate/erfp/utils/ClusterInterfac
e]
weblogic.ejb.common.DeploymentException: Problem creating deployment
C:\apps\web
\weblogic\mycluster\lib\ErfpLibrary.jar from
C:\apps\web\weblogic\mycluster\lib\
ErfpLibrary.jar; nested exception is:
java.lang.NoClassDefFoundError:
com/ebreviate/erfp/utils/ClusterInterfac
e
java.lang.NoClassDefFoundError:
com/ebreviate/erfp/utils/ClusterInterface
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:488)
at java.lang.ClassLoader.defineClass(ClassLoader.java:423)
atweblogic.boot.ServerSecureClassLoader.secureDefineClass(ServerSecureC
lassLoader.java:143)
atweblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic
ClassLoader.java:495)
atweblogic.utils.classloaders.GenericClassLoader.reallyLoadClass(Generi
cClassLoader.java:339)
atweblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass
Loader.java:183)
atweblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass
Loader.java:157)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:310)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:488)
at java.lang.ClassLoader.defineClass(ClassLoader.java:423)
atweblogic.boot.ServerSecureClassLoader.secureDefineClass(ServerSecureC
lassLoader.java:143)
atweblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic
ClassLoader.java:495)
atweblogic.utils.classloaders.GenericClassLoader.reallyLoadClass(Generi
cClassLoader.java:339)
atweblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass
Loader.java:183)
atweblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass
Loader.java:157)
atweblogic.ejb.deployment.dd.DeploymentUnit.loadClass(DeploymentUnit.ja
va:101)
atweblogic.ejb.deployment.dd.DeploymentUnit.initializeMethodInfos(Deplo
ymentUnit.java:424)
atweblogic.ejb.internal.EJBJarLoader.initializeMethodInfos(EJBJarLoader
.java:129)
atweblogic.ejb.internal.EJBJarDeployment.setupJar(EJBJarDeployment.java
:392)
atweblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:21
1)
atweblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:18
2)
atweblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:16
4)
atweblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java
:172)
atweblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:1
22)
atweblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:1
12)
atweblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:311)
atweblogic.ejb.internal.EJBManagerImpl.deployBeans(EJBManagerImpl.java:
653)
atweblogic.ejb.internal.EJBManagerImpl.<init>(EJBManagerImpl.java:247)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1386)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:879)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:140)
at weblogic.Server.main(Server.java:97)
at weblogic.Server.main(Server.java:58)
--------------- nested within: ------------------
weblogic.ejb.deployment.JarLoadException - with nested exception:
[weblogic.ejb.common.DeploymentException: Problem creating deployment
C:\apps\we
b\weblogic\mycluster\lib\ErfpLibrary.jar from
C:\apps\web\weblogic\mycluster\lib
\ErfpLibrary.jar; nested exception is:
java.lang.NoClassDefFoundError:
com/ebreviate/erfp/utils/ClusterInterfac
e]
atweblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:319)
atweblogic.ejb.internal.EJBManagerImpl.deployBeans(EJBManagerImpl.java:
653)
atweblogic.ejb.internal.EJBManagerImpl.<init>(EJBManagerImpl.java:247)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1386)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:879)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:140)
at weblogic.Server.main(Server.java:97)
at weblogic.Server.main(Server.java:58)
Thu Nov 07 12:59:32 CST 2002:<I> <EJB> 0 EJB jar files loaded,
containing 0 EJBs
</full_output>

Problems Creating PDFs

A lot of problems creating PDFs come from using the wrong printer to create the PDF or underlying printfile.
You should use Adobe's Distiller printer instance to create a PDF. This comprises the latest Adobe Postscript printer for your operating system plus the Distiller PPD.
Don't use an HP printer to create your PDF. PostScript, or otherwise.
Don't use a Xerox printer to create your PDF. PostScript or otherwise.
See #1.
Note: If you are outputting to a service bureau, you might want to use something other than the Distiller printer instance. However, if you encounter problems with your particular PDFs, try using the official method with the Distiller printer to see whether any problems are limited just to your setup. If problems persist, you might have to create your PostScript output using one printer driver and the PDF using Adobe's Distiller printer instance.
Common problems include:
Black and white, or greyscale, PDFs created from color FrameMaker books and documents.
Distiller terminating the PDF creation process early, thus no PDF is created.
Troubleshooting:
For lack-of-color problems, first check you don't have Spot as Black set in the Frame Print dialog.
Update the printer you are using to the latest Adobe PostScript printer driver version.
Uninstall the printer you are using to create PDFs and to reinstall the latest version from scratch.

FAQ: Creating PDF Files from FrameMaker Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!
Dov Isaacs - 07:02pm Dec 6, 2001 Pacific
An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
GOOD NEWS
I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
DON'T USE "SAVE AS PDF"
But what's wrong with "save as PDF" as currently implemented?
The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
(1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
(2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
(3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
(4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
(5) Some or all text in the resultant PDF file cannot be searched or indexed.
(6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
(7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
(8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
(9) Some or all page content is missing (other than margin areas).
(10) Relatively inefficient PDF is generated.
If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
Whether the printer supports color (Acrobat Distiller does)
What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
Resident fonts (Acrobat Distiller doesn't really have resident fonts)
Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
DON'T USE PDFWRITER
The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
Case 3: Acrobat 3
Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
- Dov

Problem creating service jboss.security:name=XMLLoginConfig

Hello,
I am trying to to run my application using Java 5 and JBoss 4.2.1, but i am stuck in the middle. The error which i received is as follows:-
2008-10-15 12:56:06,031 WARN | (org.jboss.system.ServiceController:337) - Problem creating service jboss.security:name=XMLLoginConfig
java.lang.AbstractMethodError: org.jboss.security.auth.login.XMLLoginConfig.jbossInternalLifecycl
(Ljava/lang/String;)V
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:330)
at org.jboss.system.ServiceController.create(ServiceController.java:273)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.create(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
2008-10-15 12:56:06,078 INFO | (org.jboss.logging.Log4jService$URLWatchTimerTask:440) - Configur
ng from URL: resource:log4j.xml
log4j: Reading configuration from URL resource:log4j.xml
log4j: Could not find root logger information. Is this OK?I am not able to find the cause of this error. May be deployment is not happening. But the code was properly working on Java 4 and JBoss 3.0.0. Now when i migrated it to newer version , here i get this error.
Please help me
Thanks in advance
Monadear

Hi,
Looking at your document URL for the WSDL, the PeopleSoft IB should contain "Service" in it's name, it looks like you are using your IB Gateway URL instead.
This is what you posted:
- http://xxx.com:11001/PSIGW/PeopleSoftListeningConnector/CI_Z_POSITION_DATA.1.wsdl
Try the following and this should resolve your problem.
- http://xxx.com:11001/PSIGW/PeopleSoftServiceListeningConnector/CI_Z_POSITION_DATA.1.wsdl
Regards,
Dan

Has anyone received this error, "Failed to create directory for PX images"

I recently migrated to Windows7. 98% of the migration went well. All of my pictures and Elements Catalog came over fine. I had to "reconnect" all of the pictures in the catalog due to new directory name, but it worked fairly well. Of the 11,000 entries synch'd with photoshop.com, 10,500 re-synch'd fine. However almost 500 are stuck with an error of "Failed to create directory for PX images". Can anyone help with how to resolve this issue? Note, I did try to remove the picture from the album and then re-add, but that didn't work.
Thank you in advance for any help you can provide.
Thanks,
Jeff

function(){return A.apply(null,[this].concat($A(arguments)))}
JeffAGoldberg wrote:
Erased everything on photoshop.com (which I couldn't accomplish due to bugs on photoshop.com) and created a new catalog.
Jeff
What problems are you facing in deleting files from PS.com. Are you able to maintain a proper synced catalog now ? If possible please elaborate so that we can help.

Fetch error message: Can't create directory

Hi again--Help!!
I have my whole site fixed of "errant" characters and ??? and it is ready to upload to a GoDaddy host.. And after turning off "Translate ISO characters" in the Fetch preferences, I now get this message:
"Server response: Can't create directory: File exists."
Woe is me, what can be done? Can be so kind as to help me again?? Thanks so much...

Just a note to say that I figured out the problem myself. It was a "space" in front of the named web pages in the iWeb list. You have to make sure there are no spaces like that or it will not publish properly! Everything is up and running now...Whew.

Re:create directory

hi all,
i have created one transaction steps are getfile_list follwed by repeater follwed by zipper and finally create directory .Here the problem is whatever file in .zip extension i want to move that file into directory ,here the plm is directory are created successfully but zip files are not moving to that particular directory.

Hi Devakrishnan,
Try this way: Create a directory first & then get the file list & zip it using a repeater. Set the path for the zip file to the folder created in step one.
This will work.
Thanks,
Sushma.
Pls. award points if satisfied.

Error Cannot create directory /tmp/ .xorg.conf72

During an install of Solaris 10 (as a virtual machine) I was attempting to run /usr/X11/bin/xorgconfig
I received the following error:
Cannot create directory /tmp/ .xorg.conf72
Any Ideas as to how I could fix the problem?

Hi,
So, try to create this folder by your hands before create the track and assign all permissions to sap admin user.
It will solve this issue.
regards,
Luciano

Log4j problem -creating directory

Similar Messages

Maybe you are looking for