WL61SP4 EJBC recompilation problem
I am attempting to upgrade from WL6.1SP1 to WL6.1SP4. I have installed my server
on Solaris using an installation from weblogic610sp4_sol.bin. I compiled my beans
on NT using an installation from weblogic610sp4_win.exe. Everything builds fine.
At deployment time, I get the message below for every bean. My goal is no recompilation
at all. I have tried to insure that I have no
remnants of SP1 on the build (NT) side of the equation.
I installed in a a new bea home, and I double-checked the registry.xml file.
The "build on NT, deploy on Solaris" thing is something we have done since 5.1
with
no problems like this, so I'm guessing it is not a NT vs. Solaris problem. I'm
using the same compiler (Jikes 1.17) on both boxes.
How does the WL version get encoded at build time and verified at deploy time?
Any ideas as to what may be different under SP4?
<Mar 6, 2003 7:19:36 PM EST> <Warning> <EJB> <The EJB deployment named: phenotype_bfxdev
was compiled by a different version of the WebLogic Server.>
<Mar 6, 2003 7:19:36 PM EST> <Info> <EJB> <The EJB deployment named: phenotype.jar
is being recompiled within the WebLogic Server. Please consult the server logs
if there are any errors. It is also possible to run weblogic.ejbc as a stand-alone
tool to generate the required classes.>
Hello,
I currently meet the same problem. In my case, I compile and deploy my ejb
on the same machine (w2k running wls6.1sp4). And since I upgrades to sp4,
here what happens :
- older ejb compiled with previous version of service pack are recompiled
when starting (only once). I think it's normal.
- if I change method signature or method implementation on an ejb compiled
with sp4, weblogic doesn't see changes if it's method implementation or
throws an exception if it was method signature change.
If I want the problem to disappear, I must delete .wlnotdelete and the
tmp... dir
I think I will open a case at BEA.
Reagrds,
Dom
Here is some infos :
Weblogic version:
Console Release Build
6.1.4.0
Server Release Build
6.1.4.0
Server Build
WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641
All Server Product Versions
WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641
WebLogic XML Module 6.1 SP4 11/08/2002 22:04:40 #221641
wlgenerated included in the ejb jar in .wlnotdelete :
#Thu Apr 17 09:49:17 CEST 2003
WLRELEASE_BUILD_VERSION=6.1.4.0
Exception thrown when method signature change:
####<16 avr. 03 18:03:15 CEST> <Error> <J2EE> <UCPNE> <myserver> <main>
<system> <> <160001> <Error deploying application EJB Commercial:
Unable to deploy EJB: DemandeTarificationAppelOffre from
sofaxiscommercial.jar:
java.lang.NullPointerException
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMDField(ClientDrivenBean
InfoImpl.java:666)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMethodDescriptors(Client
DrivenBeanInfoImpl.java:723)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfo
Impl.java:858)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:364)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:286)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy38.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:3015)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:376)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:164)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy51.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1309)
at weblogic.management.Admin.finish(Admin.java:649)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:542)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:213)
at weblogic.Server.main(Server.java:35)
"John" <[email protected]> a écrit dans le message de news:
[email protected]...
>
On both the NT and Solaris side, "java weblogic.version" produces:
WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641
WebLogic XML Module 6.1 SP4 11/08/2002 22:04:40 #221641
The wlgenerated files in the beans I am trying to deploy read:
#Fri Mar 07 14:02:15 EST 2003
WLRELEASE_BUILD_VERSION=6.1.4.0
Again, the deployment on Solaris recompiles all of my EJBs. Even deployingon
the NT box where they were built leads to 5 out of 30 EJBs beingrecompiled.
I made sure to remove the .../wlserver6.1/tmp_* directories on Solarisbefore
deploying.
Any other ideas as to what I may be doing wrong, or is this a known SP4problem?
>
>
Rob Woollen <[email protected]> wrote:
Check the output of 'java weblogic.version' on both machines and ensure
it is the same.
ejbc (in 6.x or later) includes a file in the output ejb-jar which
includes the compilation version-stamp. The server compares this with
its own version and recompiles if there is any difference.
-- Rob
John wrote:
I am attempting to upgrade from WL6.1SP1 to WL6.1SP4. I have installedmy server
on Solaris using an installation from weblogic610sp4_sol.bin. I
compiled
my beans
on NT using an installation from weblogic610sp4_win.exe. Everythingbuilds fine.
At deployment time, I get the message below for every bean. My goalis no recompilation
at all. I have tried to insure that I have no
remnants of SP1 on the build (NT) side of the equation.
I installed in a a new bea home, and I double-checked the registry.xmlfile.
The "build on NT, deploy on Solaris" thing is something we have donesince 5.1
with
no problems like this, so I'm guessing it is not a NT vs. Solaris
problem.
I'm
using the same compiler (Jikes 1.17) on both boxes.
How does the WL version get encoded at build time and verified at
deploy
time?
Any ideas as to what may be different under SP4?
<Mar 6, 2003 7:19:36 PM EST> <Warning> <EJB> <The EJB deployment named:phenotype_bfxdev
was compiled by a different version of the WebLogic Server.>
<Mar 6, 2003 7:19:36 PM EST> <Info> <EJB> <The EJB deployment named:phenotype.jar
is being recompiled within the WebLogic Server. Please consult theserver logs
if there are any errors. It is also possible to run weblogic.ejbc asa stand-alone
tool to generate the required classes.>
Similar Messages
-
Apache 2.2.3 recompilation problem with updated openssl
I am trying to recompile an apache 2.2.3 with an updated openssl and stumble on httpd-2.2.3 make. I did compile this setup in the last year successfully, only difference is updated openssl.
First, I installed openssl-0.9.6m from source. Test install:
/usr/local/ssl/bin/openssl version
OpenSSL 0.9.6m 17 Mar 2004
Using following gcc version:
gcc -v
Reading specs from /usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6/specs
Configured with: ../configure with-as=/usr/ccs/bin/as with-ld=/usr/ccs/bin/ld enable-shared enable-languages=c,c++,f77
Thread model: posix
gcc version 3.4.6
PATH output:
echo $PATH
/usr/sbin:/usr/bin:/usr/local:/usr/local/bin:/usr/ccs/bin:/usr/openwin/bin:/usr /dt/bin:/usr/platform/SUNW,Sun-Fire-V240/sbin:/opt/sun/bin:/opt/SUNWvts/bin
This is my apache config options:
./configure enable-so enable-ssl enable-rewrite enable-proxy enable-proxy-balancer with-ssl=/usr/local/ssl
make output:
Making all in srclib
Making all in pcre
Making all in os
Making all in unix
Making all in server
Making all in mpm
Making all in prefork
Making all in modules
Making all in aaa
Making all in filters
Making all in loggers
Making all in metadata
Making all in proxy
Making all in ssl
In file included from /usr/local/ssl/include/openssl/ecdh.h:79,
from /usr/local/ssl/include/openssl/engine.h:85,
from ssl_toolkit_compat.h:45,
from ssl_private.h:59,
from mod_ssl.c:27:
/usr/local/ssl/include/openssl/ossl_typ.h:79: error: redefinition of typedef 'ASN1_INTEGER'
/usr/local/ssl/include/openssl/asn1.h:241: error: previous declaration of 'ASN1_INTEGER' was here
/usr/local/ssl/include/openssl/ossl_typ.h:80: error: redefinition of typedef 'ASN1_ENUMERATED'
/usr/local/ssl/include/openssl/asn1.h:242: error: previous declaration of 'ASN1_ENUMERATED' was here
/usr/local/ssl/include/openssl/ossl_typ.h:81: error: redefinition of typedef 'ASN1_BIT_STRING'
/usr/local/ssl/include/openssl/asn1.h:243: error: previous declaration of 'ASN1_BIT_STRING' was here
/usr/local/ssl/include/openssl/ossl_typ.h:82: error: redefinition of typedef 'ASN1_OCTET_STRING'
/usr/local/ssl/include/openssl/asn1.h:244: error: previous declaration of 'ASN1_OCTET_STRING' was here
/usr/local/ssl/include/openssl/ossl_typ.h:83: error: redefinition of typedef 'ASN1_PRINTABLESTRING'
/usr/local/ssl/include/openssl/asn1.h:245: error: previous declaration of 'ASN1_PRINTABLESTRING' was here
/usr/local/ssl/include/openssl/ossl_typ.h:84: error: redefinition of typedef 'ASN1_T61STRING'
/usr/local/ssl/include/openssl/asn1.h:246: error: previous declaration of 'ASN1_T61STRING' was here
/usr/local/ssl/include/openssl/ossl_typ.h:85: error: redefinition of typedef 'ASN1_IA5STRING'
/usr/local/ssl/include/openssl/asn1.h:247: error: previous declaration of 'ASN1_IA5STRING' was here
/usr/local/ssl/include/openssl/ossl_typ.h:86: error: redefinition of typedef 'ASN1_GENERALSTRING'
/usr/local/ssl/include/openssl/asn1.h:248: error: previous declaration of 'ASN1_GENERALSTRING' was here
/usr/local/ssl/include/openssl/ossl_typ.h:87: error: redefinition of typedef 'ASN1_UNIVERSALSTRING'
/usr/local/ssl/include/openssl/asn1.h:249: error: previous declaration of 'ASN1_UNIVERSALSTRING' was here
/usr/local/ssl/include/openssl/ossl_typ.h:88: error: redefinition of typedef 'ASN1_BMPSTRING'
/usr/local/ssl/include/openssl/asn1.h:250: error: previous declaration of 'ASN1_BMPSTRING' was here
/usr/local/ssl/include/openssl/ossl_typ.h:89: error: redefinition of typedef 'ASN1_UTCTIME'
/usr/local/ssl/include/openssl/asn1.h:251: error: previous declaration of 'ASN1_UTCTIME' was here
/usr/local/ssl/include/openssl/ossl_typ.h:90: error: redefinition of typedef 'ASN1_TIME'
/usr/local/ssl/include/openssl/asn1.h:252: error: previous declaration of 'ASN1_TIME' was here
/usr/local/ssl/include/openssl/ossl_typ.h:91: error: redefinition of typedef 'ASN1_GENERALIZEDTIME'
/usr/local/ssl/include/openssl/asn1.h:253: error: previous declaration of 'ASN1_GENERALIZEDTIME' was here
/usr/local/ssl/include/openssl/ossl_typ.h:92: error: redefinition of typedef 'ASN1_VISIBLESTRING'
/usr/local/ssl/include/openssl/asn1.h:254: error: previous declaration of 'ASN1_VISIBLESTRING' was here
/usr/local/ssl/include/openssl/ossl_typ.h:93: error: redefinition of typedef 'ASN1_UTF8STRING'
/usr/local/ssl/include/openssl/asn1.h:255: error: previous declaration of 'ASN1_UTF8STRING' was here
/usr/local/ssl/include/openssl/ossl_typ.h:94: error: redefinition of typedef 'ASN1_BOOLEAN'
/usr/local/ssl/include/openssl/asn1.h:256: error: previous declaration of 'ASN1_BOOLEAN' was here
/usr/local/ssl/include/openssl/ossl_typ.h:95: error: redefinition of typedef 'ASN1_NULL'
/usr/local/ssl/include/openssl/asn1.h:259: error: previous declaration of 'ASN1_NULL' was here
/usr/local/ssl/include/openssl/ossl_typ.h:107: error: redefinition of typedef 'BIGNUM'
/usr/local/ssl/include/openssl/bn.h:241: error: previous declaration of 'BIGNUM' was here
/usr/local/ssl/include/openssl/ossl_typ.h:108: error: redefinition of typedef 'BN_CTX'
/usr/local/ssl/include/openssl/bn.h:254: error: previous declaration of 'BN_CTX' was here
/usr/local/ssl/include/openssl/ossl_typ.h:109: error: redefinition of typedef 'BN_BLINDING'
/usr/local/ssl/include/openssl/bn.h:264: error: previous declaration of 'BN_BLINDING' was here
/usr/local/ssl/include/openssl/ossl_typ.h:110: error: redefinition of typedef 'BN_MONT_CTX'
/usr/local/ssl/include/openssl/bn.h:276: error: previous declaration of 'BN_MONT_CTX' was here
/usr/local/ssl/include/openssl/ossl_typ.h:111: error: redefinition of typedef 'BN_RECP_CTX'
/usr/local/ssl/include/openssl/bn.h:288: error: previous declaration of 'BN_RECP_CTX' was here
/usr/local/ssl/include/openssl/ossl_typ.h:114: error: redefinition of typedef 'BUF_MEM'
/usr/local/ssl/include/openssl/buffer.h:71: error: previous declaration of 'BUF_MEM' was here
/usr/local/ssl/include/openssl/ossl_typ.h:116: error: redefinition of typedef 'EVP_CIPHER'
/usr/local/ssl/include/openssl/evp.h:330: error: previous declaration of 'EVP_CIPHER' was here
/usr/local/ssl/include/openssl/ossl_typ.h:117: error: redefinition of typedef 'EVP_CIPHER_CTX'
/usr/local/ssl/include/openssl/evp.h:331: error: previous declaration of 'EVP_CIPHER_CTX' was here
/usr/local/ssl/include/openssl/ossl_typ.h:118: error: redefinition of typedef 'EVP_MD'
/usr/local/ssl/include/openssl/evp.h:276: error: previous declaration of 'EVP_MD' was here
/usr/local/ssl/include/openssl/ossl_typ.h:119: error: redefinition of typedef 'EVP_MD_CTX'
/usr/local/ssl/include/openssl/evp.h:328: error: previous declaration of 'EVP_MD_CTX' was here
/usr/local/ssl/include/openssl/ossl_typ.h:120: error: redefinition of typedef 'EVP_PKEY'
/usr/local/ssl/include/openssl/evp.h:186: error: previous declaration of 'EVP_PKEY' was here
/usr/local/ssl/include/openssl/ossl_typ.h:122: error: redefinition of typedef 'DH'
/usr/local/ssl/include/openssl/dh.h:78: error: previous declaration of 'DH' was here
/usr/local/ssl/include/openssl/ossl_typ.h:123: error: redefinition of typedef 'DH_METHOD'
/usr/local/ssl/include/openssl/dh.h:93: error: previous declaration of 'DH_METHOD' was here
/usr/local/ssl/include/openssl/ossl_typ.h:125: error: redefinition of typedef 'DSA'
/usr/local/ssl/include/openssl/dsa.h:87: error: previous declaration of 'DSA' was here
/usr/local/ssl/include/openssl/ossl_typ.h:126: error: redefinition of typedef 'DSA_METHOD'
/usr/local/ssl/include/openssl/dsa.h:112: error: previous declaration of 'DSA_METHOD' was here
/usr/local/ssl/include/openssl/ossl_typ.h:128: error: redefinition of typedef 'RSA'
/usr/local/ssl/include/openssl/rsa.h:76: error: previous declaration of 'RSA' was here
/usr/local/ssl/include/openssl/ossl_typ.h:129: error: redefinition of typedef 'RSA_METHOD'
/usr/local/ssl/include/openssl/rsa.h:114: error: previous declaration of 'RSA_METHOD' was here
/usr/local/ssl/include/openssl/ossl_typ.h:131: error: redefinition of typedef 'RAND_METHOD'
/usr/local/ssl/include/openssl/rand.h:76: error: previous declaration of 'RAND_METHOD' was here
/usr/local/ssl/include/openssl/ossl_typ.h:136: error: redefinition of typedef 'X509'
/usr/local/ssl/include/openssl/x509.h:280: error: previous declaration of 'X509' was here
/usr/local/ssl/include/openssl/ossl_typ.h:137: error: redefinition of typedef 'X509_ALGOR'
/usr/local/ssl/include/openssl/x509.h:130: error: previous declaration of 'X509_ALGOR' was here
/usr/local/ssl/include/openssl/ossl_typ.h:138: error: redefinition of typedef 'X509_CRL'
/usr/local/ssl/include/openssl/x509.h:407: error: previous declaration of 'X509_CRL' was here
/usr/local/ssl/include/openssl/ossl_typ.h:139: error: redefinition of typedef 'X509_NAME'
/usr/local/ssl/include/openssl/x509.h:176: error: previous declaration of 'X509_NAME' was here
/usr/local/ssl/include/openssl/ossl_typ.h:140: error: redefinition of typedef 'X509_STORE'
/usr/local/ssl/include/openssl/x509_vfy.h:176: error: previous declaration of 'X509_STORE' was here
/usr/local/ssl/include/openssl/ossl_typ.h:141: error: redefinition of typedef 'X509_STORE_CTX'
/usr/local/ssl/include/openssl/x509_vfy.h:157: error: previous declaration of 'X509_STORE_CTX' was here
/usr/local/ssl/include/openssl/ossl_typ.h:143: error: redefinition of typedef 'X509V3_CTX'
/usr/local/ssl/include/openssl/x509v3.h:132: error: previous declaration of 'X509V3_CTX' was here
/usr/local/ssl/include/openssl/ossl_typ.h:144: error: redefinition of typedef 'CONF'
/usr/local/ssl/include/openssl/conf.h:81: error: previous declaration of 'CONF' was here
/usr/local/ssl/include/openssl/ossl_typ.h:165: error: redefinition of typedef 'CRYPTO_EX_DATA'
/usr/local/ssl/include/openssl/crypto.h:194: error: previous declaration of 'CRYPTO_EX_DATA' was here
/usr/local/ssl/include/openssl/ossl_typ.h:168: error: redefinition of typedef 'CRYPTO_EX_new'
/usr/local/ssl/include/openssl/crypto.h:198: error: previous declaration of 'CRYPTO_EX_new' was here
/usr/local/ssl/include/openssl/ossl_typ.h:170: error: redefinition of typedef 'CRYPTO_EX_free'
/usr/local/ssl/include/openssl/crypto.h:201: error: previous declaration of 'CRYPTO_EX_free' was here
/usr/local/ssl/include/openssl/ossl_typ.h:172: error: redefinition of typedef 'CRYPTO_EX_dup'
/usr/local/ssl/include/openssl/crypto.h:204: error: previous declaration of 'CRYPTO_EX_dup' was here
In file included from /usr/local/ssl/include/openssl/engine.h:91,
from ssl_toolkit_compat.h:45,
from ssl_private.h:59,
from mod_ssl.c:27:
/usr/local/ssl/include/openssl/store.h:230: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:232: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:234: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:237: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:239: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:241: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:246: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:248: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:251: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:252: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:255: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:257: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:259: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:264: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:266: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:268: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:271: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:273: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:275: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:280: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:282: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:284: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:286: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:289: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:291: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:296: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:298: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:301: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:303: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:305: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:307: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:310: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:312: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:323: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:324: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:325: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:328: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:329: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:330: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:331: error: syntax error before "OPENSSL_ITEM"
/usr/local/ssl/include/openssl/store.h:377: error: syntax error before '*' token
In file included from ssl_toolkit_compat.h:45,
from ssl_private.h:59,
from mod_ssl.c:27:
/usr/local/ssl/include/openssl/engine.h:624: warning: no semicolon at end of struct or union
/usr/local/ssl/include/openssl/engine.h:624: error: syntax error before '*' token
/usr/local/ssl/include/openssl/engine.h:627: error: syntax error before '}' token
/usr/local/ssl/include/openssl/engine.h:627: warning: data definition has no type or storage class
/usr/local/ssl/include/openssl/engine.h:660: error: syntax error before '*' token
*** Error code 1
The following command caused the error:
/usr/local/apache2/build/libtool silent mode=compile gcc -g -O2 -DSOLARIS2=10 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOU
RCE -I/tmp/httpd-2.2.3/srclib/pcre -I. -I/tmp/httpd-2.2.3/os/unix -I/tmp/httpd-2.2.3/server/mpm/prefork -I/tmp/httpd-2.2.3/modules/http -I/t
mp/httpd-2.2.3/modules/filters -I/tmp/httpd-2.2.3/modules/proxy -I/tmp/httpd-2.2.3/include -I/tmp/httpd-2.2.3/modules/generators -I/tmp/httpd-2
.2.3/modules/mappers -I/tmp/httpd-2.2.3/modules/database -I/usr/local/apache2/include -I/tmp/httpd-2.2.3/modules/proxy/../generators -I/usr/loc
al/ssl/include -I/usr/sfw/include -I/tmp/httpd-2.2.3/modules/ssl -I/tmp/httpd-2.2.3/modules/dav/main -prefer-non-pic -static -c mod_ssl.c && to
uch mod_ssl.lo
make: Fatal error: Command failed for target `mod_ssl.lo'
Current working directory /tmp/httpd-2.2.3/modules/ssl
*** Error code 1
The following command caused the error:
otarget=`echo all-recursive|sed s/-recursive//`; \
list=' '; \
for i in $list; do \
if test -d "$i"; then \
target="$otarget"; \
echo "Making $target in $i"; \
if test "$i" = "."; then \
made_local=yes; \
target="local-$target"; \
fi; \
(cd $i && make $target) || exit 1; \
fi; \
done; \
if test "$otarget" = "all" && test -z 'libmod_ssl.la'; then \
made_local=yes; \
fi; \
if test "$made_local" != "yes"; then \
make "local-$otarget" || exit 1; \
fi
make: Fatal error: Command failed for target `all-recursive'
Current working directory /tmp/httpd-2.2.3/modules/ssl
*** Error code 1
The following command caused the error:
otarget=`echo all-recursive|sed s/-recursive//`; \
list=' aaa filters loggers metadata proxy ssl http generators mappers'; \
for i in $list; do \
if test -d "$i"; then \
target="$otarget"; \
echo "Making $target in $i"; \
if test "$i" = "."; then \
made_local=yes; \
target="local-$target"; \
fi; \
(cd $i && make $target) || exit 1; \
fi; \
done; \
if test "$otarget" = "all" && test -z ''; then \
made_local=yes; \
fi; \
if test "$made_local" != "yes"; then \
make "local-$otarget" || exit 1; \
fi
make: Fatal error: Command failed for target `all-recursive'
Current working directory /tmp/httpd-2.2.3/modules
*** Error code 1
The following command caused the error:
otarget=`echo all-recursive|sed s/-recursive//`; \
list=' srclib os server modules support'; \
for i in $list; do \
if test -d "$i"; then \
target="$otarget"; \
echo "Making $target in $i"; \
if test "$i" = "."; then \
made_local=yes; \
target="local-$target"; \
fi; \
(cd $i && make $target) || exit 1; \
fi; \
done; \
if test "$otarget" = "all" && test -z 'httpd '; then \
made_local=yes; \
fi; \
if test "$made_local" != "yes"; then \
make "local-$otarget" || exit 1; \
fi
make: Fatal error: Command failed for target `all-recursive'
Any help appreciatedI'm experiencing the same problem with the current DirecTV remote not being able to learn more than the first button prompted to enter (arrow-down). The error message "appletv has already learned this button" appears when attempting to enter the second button prompted (arrow-up). Furthermore, I have attempted configuration on two separate DirecTV HR21 remotes in both AV1 and AV2 modes.
Come on Apple -- don't tease us! Testing wasn't done to make sure AppleTV can learn to respond to a current DirecTV remote? Yikes. I wonder what 3rd-party remotes were tested and confirmed to work. -
JSP recompilation problem - losing text fragments
Hi,
I'm working on Oracle JDeveloper 10G and Oracle App Server 10G (9.0.4). Have the same problem on both. The following JSP fragment:
<tr<%= (idx.intValue()%2==0)?" class=bg3":"" %> height="30">
is in a loop where idx is incremented by 1. The page compiles and runs fine initially. If it is changed, then OC4J recompiles it resulting that the even rows print properly
<tr class=bg3 height="30">
but the odd rows instead of printing
<tr height="30">
it only prints
height="30">
i.e. doesn't print the "<tr" and the empty string. If the project is re-build in JDeveloper, that fixes the situation. My problem is that now the same happened on the Oracle App Server deployment, and I cannot force it to compile the JSP properly.
Any suggestions?
Thanks.Well I found out how to get EL to be ignored:
<%@ page contentType="text/html; charset=UTF-8" isELIgnored="true" %>
but output is now
+hello ${name}+
when before it was
hello
*So the tag is receiving the template text, but it's not evaluating the ${name} parameter.*
Reading the J2EE Tutorial, I don't think I'm doing anything wrong - but I obviously am! anyone shed any light, even a suggestion?
I'm using Tomcat 5.5 and servlet 2.4
"When used to specify a fragment attribute, the body of the jsp:attribute element can contain only static text and standard and custom tags; it cannot contain scripting elements"
"JSP fragments can be parametrized via expression language (EL) variables in the JSP code that composes the fragment. _The EL variables are set by the tag handler, thus allowing the handler to customize the fragment each time it is invoked_" -
Following environment is set with my setenv.cmd script.
set WL_HOME=c:\bea\wlserver6.0
set JAVA_HOME=c:\bea\jdk130
set classpath=c:\bea\jdk130\lib\tools.jar;c:\bea\wlserver6.0\lib\weblogic_sp.jar;c:\bea\wlserver6.0\lib\weblogic.jar;
set path=c:\bea\wlserver6.0\bin;c:\bea\jdk130\bin;
Following message appears when i'm running java weblogic.ejbc command
weblogic.xml.process.ProcessorFactoryException: Could not locate processor for public id="-//sun microsystems,inc.//dtd enterprise javabeans 1.1//en"
at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:181)
at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:164)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:65)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:47)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:38)
at weblogic.ejbc20.runBody(ejbc20.java:665)
at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.ejbc.main(ejbc.java:20)
plz. helpPlease check whether the DTD location in your ejb-jar.xml is
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
and in weblogic-ejb-jar.xml is
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB//EN' 'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
hope this helps.
regards,
Abhishek. -
Problem with registering Parser - Recompiled source code, don't see any changes
I had created a parser. I had register this parser with Ifs Manager. I had execute this following statement to see if been registered carefully:
On user ifssys/ifssys
sql)select name,stringvalue,bundle from odmv_property where name= 'p01';
I see my parser....
select name from odmv_propertybundle where id=1139;
ParserLookupByFileExtension
All it's ok. I upload a file with a 'p01' extension with option 'parser' on my Internet Explorer. All work fine.. My parser work. But I need to do some changes in my code. I update my code, recompile my code. My class file have been updated. After my parser (.class) file have been updated I upload a new file with parse option. I don't see any change I do in my code. Why??? How I can update my parser to view change. I have only recompile my code an place my new class files on the same directory. I have try again (change on code, recompile, test) and I don't see any changes.
But I have test by change my classname. My classname before is Test1 and I have rename my classe by Test2. I have compiled this code and a file Test2.class have been generate. I have update my register parser with Ifs Manager to use the new classname Test2. I have chack with sql statement to see if my parser have been updated. I have been updated correctly. I have upload a new file with parse option and I see my change on my code..
Do you have some explanations about that??
How I can update my source code of a parser already registered to the parser take the change I do.
Francois
nullOk, but they have another manner to resolve this problem. If I upload a file with parser option on Windows Nt explorer (Using SmbServer or WcpServer). How I can update the class file into the JVM? I need the restart this those server or just one? If just one which server I need to restart?
Thanks Francois
null -
I've been racing against time for some weeks now only to be flummoxed
by a nasty surprise. The problem is this -
I'm trying to deploy an ear file on WLS 6.0 sp2. The ear has a few
post-javac jars and a few post-ejbc jars. If I deploy these separately
they deploy fine. However, deployed together they cause Weblogic to
throw a series of errors complaining about lack of HomeImpl classes
for the post-javac beans. I thought it was supposed to generate these
on the fly - and it does seem to generate them when those same beans
are deployed independently.
Somehow the presence of the post-ejbc jars seems to inhibit WLS's
stub-generation activity. What I'm desperate to find out is how is
this generation controlled? Is there a switch/option that I can set on
a per-jar basis to say - generate stubs or dont, as the case may be?
The weird thing is that I have one such ear which DOES work despite a
combination of javac and ejbc jars. I have no idea why. I can see
nothing obviously different about it.
Advice is urgently sought.
I'm away from my work-machine now, so am unable to provide exception
traces and the like but will do so if required.Deepak Vohra <[email protected]> wrote in message news:<[email protected]>...
In the administration console select the node corresponding to the ejb.
Select the EJBC Options tab & set the ejbc options.
SL Sreenivas wrote:
Somehow the presence of the post-ejbc jars seems to inhibit WLS's
stub-generation activity. What I'm desperate to find out is how is
this generation controlled? Is there a switch/option that I can set on
a per-jar basis to say - generate stubs or dont, as the case may be?
<snipped>
Thanks, Deepak for the quick response. When you refer to the EJBC
Options tab I presume you mean the Compilers tab. At least this is
what the 6.0sp2 admin console gives me. Once you select this tab, you
see exactly 4 options, none of which seem quite suitable.
The first is the java compiler to be used - which in my case is javac.
So not much choice there. The next is Tmp Path. I dont think thats
what I am after either. Then we have the RMIC options. Now this sounds
promising but looking at the possibilities offered at BEA's site, none
seemed helpful. I did try -nowrite etc but they did not improve
matters.
The last option is KeepGenerated which again does not seem germane.
Deepak, would you mind telling me if there was something specific that
you had in mind that will let me turn off/on hot code generation (the
preferred term apparently, for weblogic's deploy-time generation of
stub/skeleton/proxy generation)?
Thanks,
Sreeni -
Java applet recompiling / updating applet problem?
I'm trying to teach myself how to program simple java applets. Anyway I have a weird problem....If I first create my applet with a background color of black and compile it, when I open my applet in internet explorer my bacground color is black. GREAT!
My problem is, is that if i change my background color to red and recompile my java code. Then close/reopen my applet with internet explorer the background is still black. My applet doesnt seem to be updating properly after the recompile.
I have This problem as well if I try to add shapes after the original compile, when I recompile and reopen my applet, my applet is still showing only whats there after the original compile. Any idea what going on?Sir,
Debugging applets in a browser is a real pain because it isn't reloading you class. You would need to shutdown your browser and restart it to see the changes.
Thankfully there is an easier way.. look at appletviewer.
Sincerely,
Slappy -
I am using JDeveloper 10.1.2.0.0 Build 1811.
I am using two projects, one of which has a dependency on the other.
It seems that when I change and save a .java file, and recompile and run, JDeveloper often does not compile my changed source. I say this because the new source is visible in the debugger, but JDeveloper skips over it when I step through the code, and because I have usually been able to solve the problem by deleting the files in the classes directory that JDeveloper makes when compiling and then compiling again.
Has anyone else encountered this ? Do I have a bad copy of JDeveloper ?
Thanks in advance for any advice -At least we don't have to leave JDeveloper for deleting the "classes"-directory/-ies. And one more: You have to be patient with JDeveloper. Don't expect the same productivity compared to Eclipse. I will never understand why vendors invent every time the whell from scratch. Oracle would have been better advised to create a plugin for Eclipse. Less effort and more time to concentrate on the core.
-
Hi all,
Can't find any problems related to compilng kernel 2.6.8 in the forum so I guess its just me doing something weird.
Well, I upgraded to stock 2.6.8 last night and all went fine. Then I decided to recompile with ABS today and all went fine. Then I was messing around with iptables and realised I needed some other modules so I went for another recompile - for some reason this time it keeps borking out on me. All I've changed is the config and the md5s in the PKGBUILD - this is the output I get:
[root@sigma7 kernel26]# makepkg -f
==> Making package: kernel26 (Wed Sep 8 22:17:05 BST 2004)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
==> Using local copy of linux-2.6.8.1.tar.bz2
==> Found config in build dir
==> Found cdburning.patch in build dir
==> Found logo_linux_clut224.ppm in build dir
==> Found bio_uncopy_user-mem-leak.patch in build dir
==> Found bio_uncopy_user-mem-leak-fix.patch in build dir
==> Using local copy of acpi-20040715-2.6.8.diff.bz2
==> Validating source files with MD5sums
linux-2.6.8.1.tar.bz2 ... Passed
config ... Passed
cdburning.patch ... Passed
logo_linux_clut224.ppm ... Passed
bio_uncopy_user-mem-leak.patch ... Passed
bio_uncopy_user-mem-leak-fix.patch ... Passed
acpi-20040715-2.6.8.diff.bz2 ... Passed
==> Extracting Sources...
==> tar --use-compress-program=bzip2 -xf linux-2.6.8.1.tar.bz2
==> bunzip2 acpi-20040715-2.6.8.diff.bz2
==> Removing existing pkg/ directory...
==> Starting build()...
patching file fs/bio.c
patching file fs/bio.c
patching file drivers/block/scsi_ioctl.c
patching file arch/i386/kernel/acpi/boot.c
patching file arch/i386/kernel/acpi/sleep.c
patching file arch/i386/kernel/cpu/cpufreq/acpi.c
patching file arch/i386/kernel/dmi_scan.c
patching file arch/i386/kernel/i8259.c
patching file arch/i386/kernel/io_apic.c
patching file arch/i386/kernel/setup.c
patching file arch/i386/kernel/smpboot.c
patching file arch/i386/mm/discontig.c
patching file arch/ia64/kernel/acpi.c
patching file arch/x86_64/kernel/i8259.c
patching file arch/x86_64/kernel/setup.c
patching file arch/x86_64/kernel/smpboot.c
patching file drivers/acpi/Makefile
patching file drivers/acpi/acpi_ksyms.c
patching file drivers/acpi/asus_acpi.c
patching file drivers/acpi/blacklist.c
patching file drivers/acpi/bus.c
patching file drivers/acpi/button.c
patching file drivers/acpi/dispatcher/dsmethod.c
patching file drivers/acpi/dispatcher/dsmthdat.c
patching file drivers/acpi/dispatcher/dsopcode.c
patching file drivers/acpi/dispatcher/dswload.c
patching file drivers/acpi/dispatcher/dswstate.c
patching file drivers/acpi/ec.c
patching file drivers/acpi/events/evevent.c
patching file drivers/acpi/events/evgpe.c
patching file drivers/acpi/events/evgpeblk.c
patching file drivers/acpi/events/evmisc.c
patching file drivers/acpi/events/evregion.c
patching file drivers/acpi/events/evxface.c
patching file drivers/acpi/events/evxfevnt.c
patching file drivers/acpi/events/evxfregn.c
patching file drivers/acpi/executer/exconfig.c
patching file drivers/acpi/executer/exfldio.c
patching file drivers/acpi/executer/exmisc.c
patching file drivers/acpi/executer/exmutex.c
patching file drivers/acpi/executer/exoparg2.c
patching file drivers/acpi/executer/exresolv.c
patching file drivers/acpi/executer/exstore.c
patching file drivers/acpi/hardware/hwgpe.c
patching file drivers/acpi/hardware/hwregs.c
patching file drivers/acpi/hardware/hwsleep.c
The next patch would create the file drivers/acpi/motherboard.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/acpi/motherboard.c.rej
patching file drivers/acpi/namespace/nsaccess.c
patching file drivers/acpi/namespace/nsalloc.c
patching file drivers/acpi/namespace/nseval.c
patching file drivers/acpi/namespace/nsinit.c
patching file drivers/acpi/namespace/nsparse.c
patching file drivers/acpi/namespace/nsxfeval.c
patching file drivers/acpi/namespace/nsxfname.c
patching file drivers/acpi/osl.c
patching file drivers/acpi/parser/psopcode.c
patching file drivers/acpi/parser/psxface.c
patching file drivers/acpi/pci_link.c
patching file drivers/acpi/power.c
patching file drivers/acpi/processor.c
patching file drivers/acpi/resources/rsutils.c
patching file drivers/acpi/resources/rsxface.c
patching file drivers/acpi/scan.c
patching file drivers/acpi/sleep/Makefile
patching file drivers/acpi/sleep/main.c
patching file drivers/acpi/sleep/proc.c
patching file drivers/acpi/sleep/sleep.h
The next patch would create the file drivers/acpi/sleep/wakeup.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/acpi/sleep/wakeup.c.rej
patching file drivers/acpi/tables/tbxfroot.c
patching file drivers/acpi/thermal.c
patching file drivers/acpi/utilities/utalloc.c
patching file drivers/acpi/utilities/uteval.c
patching file drivers/acpi/utilities/utglobal.c
patching file drivers/acpi/utilities/utxface.c
patching file include/acpi/acconfig.h
patching file include/acpi/acdebug.h
patching file include/acpi/acdisasm.h
patching file include/acpi/acdispat.h
patching file include/acpi/acevents.h
patching file include/acpi/acexcep.h
patching file include/acpi/acglobal.h
patching file include/acpi/achware.h
patching file include/acpi/acinterp.h
patching file include/acpi/aclocal.h
patching file include/acpi/acmacros.h
patching file include/acpi/acnamesp.h
patching file include/acpi/acobject.h
patching file include/acpi/acparser.h
patching file include/acpi/acpi_bus.h
patching file include/acpi/acpi_drivers.h
patching file include/acpi/acpiosxf.h
patching file include/acpi/acpixf.h
patching file include/acpi/acstruct.h
patching file include/acpi/actbl.h
patching file include/acpi/actypes.h
patching file include/acpi/platform/acenv.h
patching file include/acpi/platform/aclinux.h
patching file include/asm-i386/acpi.h
patching file include/asm-i386/smp.h
patching file include/asm-ia64/acpi.h
patching file include/asm-x86_64/acpi.h
patching file init/main.c
==> ERROR: Build Failed. Aborting...
Does anyone have any suggestions here?If I'd changed something major then it would give me a clue about what to fix.
Thanks in advance.Me again
IT seems like its the acpi file that the PKGBUILD needs that's causing the problem-I removed it from the PKGBUILD and it compiled fine (I have yet to load it and test it tho)...I can't find any news item or forum thread relating to what this file is and whether it's important or not, can anyone let me know?
On a side note, when I just ran makepkg the acpi.diff file wouldn't download - I had to go get it myself - is there an error in the url in the PKGBUILD?
nobody else seems to be having any trouble here, which is making me a bit paranoid! -
XMonad recompile failing - path problem?
I have XMonad setup on my machine, and whenever I try to recompile from within the environment (mod-Q), I get the error:
collect2: fatal error: cannot find 'ld'
compilation terminated.
However, if I open a terminal and do xmonad --recompile, it works fine.
Also, a few applications such as firefox and intellij don't run from dmenu/yeganesh, I have to launch them from the terminal.
This makes me think that xmonad doens't have the same $PATH as my terminal environment. How would I check this?thanks for your help skottish!
running ghc-pkg list displayed that i had two haskell-time's installed. querying the aur using paktahn said that i had haskell-time installed with ghc, which was correct but yaourt said i didn't have it installed. so i installed the package with yaourt, removing both dependancies defined in the pkgbuild, because those always sent yaourt into a terrible loop. the build succeeded and i promptly removed the package. I then reinstalled ghc, xmonad-darcs, and xmonad-contrib-darcs using paktahn. Everything is working splendid now. baller. -
Problems recompiling ffmpeg with additional codec support.
I took the PKGBUILD from the AUR, and added --enable-x264 to the configure line, then tried to makepkg.
gcc -O3 -g -Wall -Wno-switch -march=i686 -O2 -pipe -I. -I'/var/abs/ffmpeg-cvs/src/ffmpeg-build' -I'/var/abs/ffmpeg-cvs/src/ffmpeg-build'/libavutil -I'/var/abs/ffmpeg-cvs/src/ffmpeg-build'/libavcodec -I'/var/abs/ffmpeg-cvs/src/ffmpeg-build'/libavformat -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE -c -o ffmpeg.o ffmpeg.c
ffmpeg.c: In function 'output_packet':
ffmpeg.c:1229: warning: pointer targets in passing argument 2 of 'av_fast_realloc' differ in signedness
gcc -O3 -g -Wall -Wno-switch -march=i686 -O2 -pipe -I. -I'/var/abs/ffmpeg-cvs/src/ffmpeg-build' -I'/var/abs/ffmpeg-cvs/src/ffmpeg-build'/libavutil -I'/var/abs/ffmpeg-cvs/src/ffmpeg-build'/libavcodec -I'/var/abs/ffmpeg-cvs/src/ffmpeg-build'/libavformat -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE -c -o cmdutils.o cmdutils.c
gcc -Wl,--warn-common -rdynamic -g -o ffmpeg_g ffmpeg.o cmdutils.o -L./libavformat -lavformat -L./libavcodec -lavcodec -L./libavutil -lavutil -lm -lx264 -lz -ldl -lpthread -lvorbisenc -lvorbis -logg -lfaac -lxvidcore
./libavcodec/libavcodec.so: undefined reference to `XSync'
./libavcodec/libavcodec.so: undefined reference to `XDrawPoint'
./libavcodec/libavcodec.so: undefined reference to `XMapWindow'
./libavcodec/libavcodec.so: undefined reference to `XCreateImage'
./libavcodec/libavcodec.so: undefined reference to `XSetForeground'
./libavcodec/libavcodec.so: undefined reference to `XAllocNamedColor'
./libavcodec/libavcodec.so: undefined reference to `XResizeWindow'
./libavcodec/libavcodec.so: undefined reference to `XAllocSizeHints'
./libavcodec/libavcodec.so: undefined reference to `XFree'
./libavcodec/libavcodec.so: undefined reference to `XCreateColormap'
./libavcodec/libavcodec.so: undefined reference to `XDrawLine'
./libavcodec/libavcodec.so: undefined reference to `XCreateWindow'
./libavcodec/libavcodec.so: undefined reference to `XNextEvent'
./libavcodec/libavcodec.so: undefined reference to `XDrawRectangle'
./libavcodec/libavcodec.so: undefined reference to `XSelectInput'
./libavcodec/libavcodec.so: undefined reference to `XSetStandardProperties'
./libavcodec/libavcodec.so: undefined reference to `XPutImage'
./libavcodec/libavcodec.so: undefined reference to `XOpenDisplay'
collect2: ld returned 1 exit status
make: *** [ffmpeg_g] Error 1
I get the same error whether I use the build for the current CVS version in stable, or the latest CVS. I just tried taking out the --enable-x264 and I still get the same error. It looks like it won't compile with GCC4. gcc-compat has disappeared from the AUR, so what am I supposed to do to get gcc3.4 back again? This is why so many other distros haven't switched to gcc4.google:ffmpeg gcc4 - there's a patch out there......
Hey, that's the first time I've used the google: tags... -
Why do i need to recompile...please help ?
Hi Folks,
Iam in a big debate here concernning a moderately complex application. The application contains 20-30 EJbs and some war files. jar files and they are all packaged into a EAR file.
Please Note: We have to upgrade our weblogic servers from WLS8.1 -sp2 > WLS81-SP3. We have like 10 others application been upgraded, all we did is , just point the application to the new JDK and weblogic version....and they worked superbly !!!
But this application, didn't get deployed when we upgraded. Then i told them (actually one of my friend working in that application team and i told him to recompile the code and give back to me---just for our testing purpose), to recompile the code with newer jdk version. He finally did, and the application get deployed.
Now, the big problem is that the application team(managers and all of them) does not want to do it. .....they are saying that we have to do LOT of work and we will not do RECOMPILE (officially) ...UNLESS and UNTILL if you give them concrete details of "WHY".
Now since iam in server support team, i have very little idea for how to tell that they need this recompilation because of following reasons:
1 ?
2 ?
3 ?
could anybody please tell me some reasons , why an application needs to recompiled for this type of an upgrade ?
your guesses would be ok for me.....
Thanks a ton,
sangitaBTW, this is the exception that i get: ...hey, iam on HP box, and not on SUN box. The other application were upgraded on SUN box only,,,,would that make any difference ???
This is the exception:
####<Oct 22, 2004 8:31:16 PM CEST> <Warning> <Deployer> <ux23> <cdmv_ibm> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149004> <Failures were detected while initiating Deploy task for application cdmvbase_test8126.>
####<Oct 22, 2004 8:31:16 PM CEST> <Error> <Deployer> <ux23> <cdmv_ibm> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 1 for the application cdmvbase_test8126.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for baseEJB.jar
Module: baseEJB.jar Error: Exception preparing module: EJBModule(baseEJB.jar,status=NEW)
Unable to deploy EJB: baseEJB.jar from baseEJB.jar:
Compiler failed executable.exec
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:762)
at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:700)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1317)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3101)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1560)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
java.io.IOException: Compiler failed executable.exec
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:469)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:762)
at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:700)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1317)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3101)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1560)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2398)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for baseEJB.jar
Module: baseEJB.jar Error: Exception preparing module: EJBModule(baseEJB.jar,status=NEW)
Unable to deploy EJB: baseEJB.jar from baseEJB.jar:
Compiler failed executable.exec
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:762)
at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:700)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1317)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3101)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1560)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
java.io.IOException: Compiler failed executable.exec
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:469)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:762)
at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:700)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1317)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3101)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1560)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
-
WLS 6.1 SP4 Recompilation Error
Hi,
We run version WLS 6.1 SP4 (I never noticed this when we were using
WLS 6.1) on each of development, system test, and production machines.
When I compile and deploy my web app to our devlopment machine
everything is fine. It is always compiled on our devlopment machine.
However when I deploy the same web app to our system test machine it
gives the following error:
####<Nov 7, 2003 9:49:05 AM EST> <Warning> <EJB> <blah.com.au>
<myserver> <main> <system> <> <010004
<The EJB deployment named: blah_blah was compiled by a different version ofthe WebLogic Server.>
This has always happened on our development machine but not on our
production machine, so it has never really been a problem because it
just recompiles it and everything is fine.
But now I have added some EJBs to the web app and now when I
recompiles it at startup it never compiles the new EJBs, and thus
never deployes them.
I have check the following on each machine to compare WLS versions.
wlgenerated file in the app jar file
java weblogic.ejbc -version
java weblogic.version
and java -version
They all report to be the exactly the same version.
Are there any suggestions to stop the WLS recompiling my app or to
make it compile my new EJBs when the server starts up.
Any suggestions would be very much appricited.
Cheers
KeithKeith,
This message gives you exact reason. Double-check classpaths
used the start weblogic and to run ejbc. There may be something
left from previous installations.
Regards,
Slava Imeshev
"Keith" <[email protected]> wrote in message news:3fb0337c$[email protected]..
>
Hi,
We run version WLS 6.1 SP4 (I never noticed this when we were using
WLS 6.1) on each of development, system test, and production machines.
When I compile and deploy my web app to our devlopment machine
everything is fine. It is always compiled on our devlopment machine.
However when I deploy the same web app to our system test machine it
gives the following error:
####<Nov 7, 2003 9:49:05 AM EST> <Warning> <EJB> <blah.com.au>
<myserver> <main> <system> <> <010004
<The EJB deployment named: blah_blah was compiled by a different version ofthe WebLogic Server.>
This has always happened on our development machine but not on our
production machine, so it has never really been a problem because it
just recompiles it and everything is fine.
But now I have added some EJBs to the web app and now when I
recompiles it at startup it never compiles the new EJBs, and thus
never deployes them.
I have check the following on each machine to compare WLS versions.
wlgenerated file in the app jar file
java weblogic.ejbc -version
java weblogic.version
and java -version
They all report to be the exactly the same version.
Are there any suggestions to stop the WLS recompiling my app or to
make it compile my new EJBs when the server starts up.
Any suggestions would be very much appricited.
Cheers
Keith -
Terracotta: application deploy problem (WLP 9.2)
hi,
when i try to deploy a Portal application on a bea weblogic server (9.2.1), that is enabled for terracotta (added the java startup arguments to the bea server and the client is visible in the Terracotta Administrator Console), the deployment fails and a lot of compile errors are shown concerning bea classes (from netuix.jar and content.jar, see bottom for snippet). for some reason bea wants to compile these classes on deployment.
has anybody seen this same problem and does anybody have a solution or workaround for this problem? must the classes be compiled on the fly during development?
regards,
erik
log snippet:
####<Oct 4, 2007 6:48:49 PM CEST> <Error> <Deployer> <opteron-w2k3> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1191516529616> <BEA-149205> <Failed to initialize the application 'ps' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)
Unable to deploy EJB: netuix.jar from netuix.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\wsrp\services\persistence\internal\ProducerPersistenceManager_7vyoe8_Impl.java:11: com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Intf
public final class ProducerPersistenceManager_7vyoe8_Impl
^
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\BookDefinitionManager_1xzrxc_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Intf
public final class BookDefinitionManager_1xzrxc_Impl
^
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortletCategoryManager_uhkdka_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Intf
public final class PortletCategoryManager_uhkdka_Impl
[MORE CLASSES HERE]
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortalDefinitionManager_d875a8_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Intf
public final class PortalDefinitionManager_d875a8_Impl
^
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PageDefinitionManager_c4el9c_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Intf
public final class PageDefinitionManager_c4el9c_Impl
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
25 errors
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)the deployment problem is solved by putting the bea packages in the exclude section of the Terracotta configuration file.
-
Problem compiling NAS 2.1 AppLogics on iAS 6.0 SP4 on Solaris
I'm currently trying to upgrade our live server from
iAS 6.0 SP2 to iAS 6.0 SP4 (on Solaris 8) and ran into
a problem in recompiling some NAS 2.1 AppLogics on my
SP4 server. I made no modifications to the code or
build.xml which runs fine on SP2. Here's what happens
when I run build :
wwwtest% build
Searching for build.xml ...
Buildfile: /export/home/iplanet/ias6/ias/APPS/TBG/build.xml
compile:
[javac] Compiling 207 source files to /export/home/iplanet/ias6/ias/APPS
[javac] /export/home/iplanet/ias6/ias/APPS/TBG/BaseResource.java:0: The method void setSessionTimeout(int) declared in class com.netscape.server.nas.BaseResource cannot override the method of the same signature declared in interface com.kivasoft.ISession2. They must have the same return type.
[javac] package TBG;
[javac] ^
[javac] 1 error
BUILD FAILED
/export/home/iplanet/ias6/ias/APPS/TBG/build.xml:48: Compile failed, messages should have been provided.
Total time: 26 seconds
Here's my kludged-together build.xml (only the
compile target does anything for this app...)
<?xml version="1.0"?>
<!-- ============================================================== -->
<!-- Ant XML file for TBG application as deployed to -->
<!-- iPlanet Application Server. -->
<!-- -->
<!-- Copyright (c) 2000 Sun Microsystems, Inc. All rights reserved. -->
<!-- ============================================================== -->
<project name="TBG" default="compile" basedir="..">
<!-- App name-dependent settings. -->
<property name="appname" value="TBG"/>
<property name="ear" value="${appname}App.ear"/>
<property name="war" value="${appname}.war"/>
<property name="ejbjar" value="${appname}Ejb.jar"/>
<!-- Package directory structures of interest. -->
<property name="app.pkgprefix" value="TBG"/>
<property name="ias.bin" value="${ias.home}/bin"/>
<!-- change this property to use a compiler other than javac. -->
<property name="build.compiler" value="classic"/>
<!-- Source file location. -->
<property name="src" value="TBG"/>
<property name="src.docroot" value="${src}/docroot"/>
<!-- Destination directory for the build -->
<property name="build" value="TBG"/>
<property name="build.docdir" value="${build}/docs/api"/>
<property name="build.classesdir" value="."/>
<property name="build.classpath" value="${build.classesdir}:${ias.cpath}:${ias.home}/classes/java/nab25.jar"/>
<!-- Destination directory for the assembly targets -->
<property name="assemble" value="../assemble"/>
<property name="assemble.ejbjar" value="${assemble}/jar"/>
<property name="assemble.war" value="${assemble}/war"/>
<property name="assemble.ear" value="${assemble}/ear"/>
<!-- ======================================================= -->
<!-- Compile all classes. -->
<!-- ======================================================= -->
<target name="compile">
<javac srcdir="${src}"
destdir="${build.classesdir}"
classpath="${build.classpath}"/>
</target>
<!-- ======================================================= -->
<!-- Build iAS-specific EJB stubs and skeletons. -->
<!-- -->
<!-- See build/ejbc-<bean name>.txt files for ejbc results. -->
<!-- ======================================================= -->
<target name="stubs">
<property name="ias.ejbc.cpath" value=".${cpath.seperator}${build.classpath}"/>
<echo message="Started building iAS stubs and skeletons for EJBs" />
<echo message="GreeterEJB" />
<exec dir="${build.classesdir}" executable="${ias.bin}/ejbc">
<arg line="-classpath ${ias.ejbc.cpath} -sl samples.helloworld.ejb.GreeterHome samples.helloworld.ejb.Greeter samples.helloworld.ejb.GreeterEJB"/>
</exec>
<echo message="Finished building iAS stubs and skeletons for EJBs" />
</target>
<!-- ======================================================= -->
<!-- Clean up various files and directories. -->
<!-- ======================================================= -->
<target name="clean_ear">
<delete dir="${assemble.ear}"/>
</target>
<target name="clean_war">
<delete dir="${assemble.war}"/>
</target>
<target name="clean_ejbjar">
<delete dir="${assemble.ejbjar}"/>
</target>
<target name="clean_assemble">
<delete dir="${assemble}"/>
</target>
<target name="clean" depends="clean_assemble">
<delete dir="${build}"/>
</target>
<target name="fixforunix">
<fixcrlf srcdir="${src}"
cr="remove" eof="remove"
includes="**/*.jsp,**/*.html,**/*.tld,**/*.xml,**/*.java,**/*.sh,**/*.sql"
/>
</target>
<!-- ======================================================= -->
<!-- Assemble EJB JAR module. -->
<!-- ======================================================= -->
<target name="ejbjar" depends="clean_ejbjar">
<mkdir dir="${assemble.ejbjar}"/>
<copy todir="${assemble.ejbjar}/${app.pkgprefix}">
<fileset dir="${build.classesdir}/${app.pkgprefix}/" includes="**/*.class" excludes="**/servlet/"/>
</copy>
<mkdir dir="${assemble.ejbjar}/META-INF"/>
<copy file="ejb-jar.xml" tofile="${assemble.ejbjar}/META-INF/ejb-jar.xml"/>
<copy file="ias-ejb-jar.xml" tofile="${assemble.ejbjar}/META-INF/ias-ejb-jar.xml"/>
<jar jarfile="${assemble.ejbjar}/${ejbjar}"
basedir="${assemble.ejbjar}"/>
</target>
<!-- ======================================================= -->
<!-- Assemble WAR module. -->
<!-- ======================================================= -->
<target name="war" depends="clean_war">
<mkdir dir="${assemble.war}"/>
<copy todir="${assemble.war}">
<fileset dir="${src.docroot}" excludes="cvs,annontation"/>
</copy>
<copy todir="${assemble.war}/WEB-INF/classes/${app.pkgprefix}">
<fileset dir="${build.classesdir}/${app.pkgprefix}/" includes="**/servlet/*.class"/>
</copy>
<copy file="web.xml" tofile="${assemble.war}/WEB-INF/web.xml"/>
<copy file="ias-web.xml" tofile="${assemble.war}/WEB-INF/ias-web.xml"/>
<jar jarfile="${assemble.war}/${war}"
basedir="${assemble.war}"/>
</target>
<!-- ======================================================= -->
<!-- Assemble EAR module. -->
<!-- ======================================================= -->
<target name="ear" depends="ejbjar, war, clean_ear">
<mkdir dir="${assemble.ear}"/>
<copy file="${assemble.ejbjar}/${ejbjar}" tofile="${assemble.ear}/${ejbjar}"/>
<copy file="${assemble.war}/${war}" tofile="${assemble.ear}/${war}"/>
<copy file="application.xml" tofile="${assemble.ear}/META-INF/application.xml"/>
<jar jarfile="${assemble.ear}/${ear}"
basedir="${assemble.ear}"/>
<delete file="${assemble.ear}/${ejbjar}" />
<delete file="${assemble.ear}/${war}" />
</target>
<!-- ======================================================= -->
<!-- Create Javadocs. -->
<!-- ======================================================= -->
<target name="javadocs">
<delete dir="${build.docdir}"/>
<mkdir dir="${build.docdir}"/>
<javadoc packagenames="samples.helloworld.*"
sourcepath="${src}"
destdir="${build.docdir}"
author="true"
version="true"
use="true"
windowtitle="iPlanet App Server HelloWorld Sample Application API"
doctitle="iPlanet App Server HelloWorld Sample"
bottom="Copyright © 2000 Sun Microsystems Inc. All Rights Reserved."/>
</target>
<!-- ======================================================= -->
<!-- Install targets. -->
<!-- ======================================================= -->
<target name="install_javadocs">
<delete dir="../docs/api"/>
<mkdir dir="../docs/api"/>
<copy todir="../docs/api">
<fileset dir="${build.docdir}/"/>
</copy>
</target>
<target name="install_ear">
<copy file="${assemble.ear}/${ear}" tofile="../${ear}"/>
<echo message="Copied ${ear} to sample root directory." />
<echo message="Executing iasdeploy to register ${ear}."/>
<exec executable="${ias.bin}/iasdeploy">
<arg line="deployapp -verbose ../${ear}"/>
</exec>
</target>
<target name="deploy" depends="install_ear">
</target>
<target name="core" depends="compile, stubs, ejbjar, war, ear" />
<target name="all" depends="core, javadocs" />
<target name="install" depends="install_javadocs, install_ear" />
</project>Hi,
Greetings to you. I'm interested to know the following.
1. Are you able to run cxs engine ?. This means, just start the cxs engine
without any errors before invoking any components with app server.
2. Does cxs engine crash after you start and kas keeps restarting the cxs
engine.
Thanks & Regards
Raj
Maybe you are looking for
-
Problem with Mini DVI to DVI adapter
Hello friends Im trying to make my Mini DVI to DVI Adapter working with a projector but it appears that it's not working. It's seems a drivers issue because I've tried with one to Mini DVI to VGA adapter with the same computer and projector and it wo
-
IPod Touch Not Recognized in Windows 8.1 Preview
Hello. I installed Windows 8.1 Preview clean last week, and am now having problems getting my iPod Touch recognized within iTunes. Normally, there is a button marked On This iPod, which I click, and then load music in that screen. That button is no
-
Another case of css not behaving properly
this is the page as it is http://www.fourpawscatrescue.co.uk/tests.html it shows the html and css design of my lightbox, the green is where the content will go and it is working properly in that link I have put the code below will someone please expl
-
I have a 30 gb ipod formatted for windows I would like to reformat for a macbook
I have a 30 GB ipod formatted for windows How can it be reformatted to work with my macbook?
-
How to redeem a store credit in itunes
I would like to use my $100 store credit in itunes. Does anyone know how? Thanks!