Frequent "Internet Configuration leased" log messages

I'm getting these log messages about every 4 minutes since upgrading to the new Extreme from the previous generation Extreme:
Jul 18 19:26:39 5 Internet Configuration leased -- host <76.235.159.58/255.255.255.0> gateway <76.235.159.59> dns <192.168.0.1 192.168.0.1> wins lease <600> domain
Jul 18 19:31:01 5 Internet Configuration leased -- host <76.235.159.58/255.255.255.0> gateway <76.235.159.59> dns <192.168.0.1 192.168.0.1> wins lease <600> domain
The new Extreme connects directly to an AT&T dsl modem - previously there was a G-band router in between, and I don't recall seeing such messages. I must have missed something in the Extreme's Internet configuration to cause this. Any ideas?
Thanks...

Similar Messages

"Internet Configuration Leased" -- every 30 minutes??

That's right. I took a look at my Time Capsule's logs (should be the same as those of the AEBS), and there's a line like this just about every 30 minutes:
May 29 20:15:53 Severity:5 Internet Configuration leased -- host <67.198.108.106/255.255.248.0> gateway <67.198.111.254> dns <66.90.132.162 66.90.130.10> wins lease <3600> domain <grandenetworks.net>
Seems excessive (and the host IP is the same every time). Is the lease figure "3600" in seconds? Even so, it shouldn't be happening every 30 minutes, should it?

After many hours on the phone with my ISP and two repair visits, no change in the DHCP lease. However, I was reading reviews of my ISP on dslreports.com and found a rep who was responding to complaints and giving his email address. I emailed him, and he put me in touch with someone who acknowledged the problem and reconfigured the DHCP server.

Frequent %CRYPTO-4-PKT_REPLAY_ERR: log messages

Hi All,
I get following log message on my spoke 881 router from time to time.
For instance today I got 80 messages like this.
Frequent %CRYPTO-4-PKT_REPLAY_ERR: log messages
This is dual hub DMVPN connectivity and both tunnels are stable during the day and EIGRP never dropped.
User behind this router also never complained. They run mainly voip traffic and I have QoS both on HUB and Spokes defined under tunnel as qos-preclassify and policy-map is applied on the physical interface.
I have also increased replay window size up to 1024, but it did not help.
Wondering what else can be done here.
IOS ver both on spokes and hub is 15.2.3(T3)

Don't know where they came from, but you could turn on debugging ipsec and isakmp to see if there is a relation with other events like rekeying.
Michael
Please rate all helpful posts

MARS Error Log Message Thread 53300144:AnaRawmsgFileReader::

Anyone have any idea about the below message from MARS? It is showing up frequently in the Backend Log Messages..
Error
./pnesloader
Thread 53300144:AnaRawmsgFileReader::Read: NOT found the two separators in the end.

It's only affected by devices that are sending "blank" syslog messages. It is worth investigating which devices sent "blank" syslog and modify the logging on the device itself, instead of changing the logging level on MARS itself.
If it's not possible to check which devices are sending blank syslogs, then you can change the logging level on MARS to "fatal":
Admin->System Maintenance->Set Runtime Logging level

What Does The Log Message "Rejecting update: Lease..." Mean?

I use RelicatedCache and TransactionMap on Coherence 3.4.2.
I saw "Rejecting update: Lease..." message.
What does the log message mean?
2011/10/18 06:41:57.506 [DEBUG] Logger@9263394 3.4.2/411p16 N/A NOAH Coherence 3.4.2/411p16 [D4] (thread=ReplicatedCache, member=2): Rejecting update: Lease: [-8863526970089418959, -2793231267399579492, R] (Cache=issue-code, Size=Unknown, Version=0/0, IssuerId=1, HolderId=0, Status=LEASE_AVAILABLE, Last locked at Thu Jan 01 09:00:00 JST 1970)
by member=2, Lease: [-8863526970089418959, -2793231267399579492, R] (Cache=issue-code, Size=143, Version=0/0, IssuerId=2, HolderId=0, Status=LEASE_AVAILABLE, Last locked at Tue Oct 18 06:41:51 JST 2011)
I found a Note 1065352.1, but the message is little differnt...
Note 1065352.1
"What Does The Log Message "Rejected update: Lease..." Mean?"I'd like to know following 2 points..
- What does "Rejecting update: Lease..." message mean?
Do thsese messages have same meaning?
- My application didn't catch any exceptions, and
"CacheFactory.commitTransactionCollection" returned true.
So this "Rejecting update: Lease..." is not a error message, right?
(Does the transaction commited successfully?)
Thanks in advance.
-Noriyuki

Hi
These are decoded results of the error message which u have recd in ur box..
%C4K_PKTPROCESSING-4-ERRORPACKET: [char]
The software is unable to process a packet; the packets have been forwarded to the CPU instead and the packet will be dropped.
Recommended Action: This is an informational message only. No action is required.
%C4K_HWACLMAN-4-WARNINGSTRING: [char]
A nonspecific warning message was displayed.
Recommended Action: See the message string [char] for more information.
Related documents- No specific documents apply to this error message
%C4K_HWACLMAN-4-WARNINGSTRING: [char]
A nonspecific warning message was displayed.
Recommended Action: See the message string [char] for more information.
Related documents- No specific documents apply to this error message.
regds

You can't use The following message is stopping me access my disk utility. 'this version of the application "Disk Utility" with this version of OS X.' not only that my Mac pro keeps dropping my internet connection and logs on to BT Open.

After installing Yosmite, The following message is stopping me accessing my disk utility. 'You can't use this version of the application “Disk Utility” with this version of OS X.' you have “Disk Utility” 12.1.1.
not only that my Mac pro keeps dropping my internet connection and logs on to BT Open.
Help

For whatever reason you don't have the Yosemite version of Disk Utility which is 13. I suggest you reinstall Yosemite.
Reinstalling OS X Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall OS X: Select Reinstall OS X and click on the Continue button.
Download and install the 10.10.1 update.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
Check that you have the current version of Disk Utility.

Decoding a fire wall log message

I need help decoding the following firewall log message:
Stealth Mode connection attempt to TCP 192.168.1.97:50459 from 70.42.185.114:80
Neither of these IP numbers belong to me (but mine is similar to the first).
Why is my firewall showing a connection attempt to a different computer?

Do not panic. That may be a more-or-less innocuous probe by, for example, a "web crawler" that's cataloging everything it can find on the internet. Think Google.
In your Applications/Utilities folder is the +Network Utility+ app. Among many other things, you can look up IP addresses and, often, find out where it's located and/or registered to.

Log Messages from Transaction Event Logger

I have 4 instances of MII v12.1 and within a transaction I want to add a message to the log when the transaction runs so I can view it through the message logger. All 4 MII instances were installed by the same consultant a few years ago so there "should" be no differences in the log configs. On 3 of the instances this is working fine - I have created a very simple transaction with one Event Logger action configured with a message "Test Message" and when I execute the transaction I see the correct entry in the log viewer. On the fourth however, although the transaction executes without error I am not seeing anything in the viewer for this event. I am using the standard "last 24 hours" log viewer with no filters and no specific log locations selected, and no customisations. I am seeing other system generated messages. I found some documentation about logging and the viewer and I found the Netweaver log config but as far as I can see it looks consistent between the instance which is working and the one which is not working. Is there some other config which needs to be done to enable Event Logging from transactions? My user has the same access across all instances. Any guidance would be appreciated. I attach a screen shot of what I am expecting to see (taken from one of the instances which is working).

Hi Partha
Many thanks for your reply. I have tried this and unfortunately it makes no difference. I also checked on the other instances and found they have their tracing levels all set to error, not Info. I have also noticed that on the instance which is working, in the System Configuration section at the bottom of the Log Config page - for Applications and all sub categories I see the entry .\log\applications_00.log in the Pattern column. On the instance which is not working I see that entry for the Applications root but not for any of the sub categories (even after selecting Copy to subtree). I cannot see where I can set this value (there is no modify function available, even under Administrator login).
Also, when I look at the log messages which have generated when setting the Event Type to Error on the instance which is not working, it shows one entry and the Category and Location columns show <com.sap.xmii.bls.executables.action.logging.LoggingActions>. When I generate an event with type Error on the instance which is working I get 2 log messages, one with the Category and Location <com.sap.xmii.bls.executables.action.logging.LoggingActions> and the other with Category /Applications/XMII/Xacute/Event and Location <com.sap.xmii.bls.executables.action.logging.LoggingActions>.
I guess that the .\log\applications_00.log should be showing for all subtree items under Applications and because it is not then the messages are not going into any application log. Not sure how to fix this however.
I have also reset to the default configuration and it does not change the above.
Best Rgds
Richard

Configuration of logging severity

Hello everyone,
I am trying to use the weblogic Admin console to modify the logging severity at runtime. I have an application deployed on the AdminServer.
In the web console, I go to the AdminServer Settings page and navigate to the Logging tab. I click the "Advanced" link to show the "Logger severity properties". In this box I have tried entering many different values. I save. There is no change to the logs. I restart the server, there is still no change to the logs.
Some values I've attempted to use:
com.mycompany.level=Trace
com.mycompany.level=Debug
com.mycompany=Trace
com.mycompany=Debug
.level=Trace
.level=Debug
I am using weblogic 10.3.2.0 with jdk logging.
Does anyone know if these configuration changes are supposed to affect the log files? Am I using this configuration parameter incorrectly?
Note that I have found a way to configure the logging severity using a logging.properties file, by calling:
LogManager.getLogManager().readConfiguration(EventDAOEJBImpl.class.getResourceAsStream("/logging.properties"));
However, this does not allow me to configure the application from the weblogic console. Is there a way to configure the logging severity using the weblogic console?

You may want to ask in the WebLogic Server - Diagnostics / WLDF / SNMP forum. They own logging.
I asked them to reply to this message.

Log4j not logging messages out to weblogic console for custom automatplugin

Hi,
We have a custom automation plugin for the OSM application build 381 in our environment(HP-UX Itanium platform). The plugins are bundled in a single ear application "A.ear" which is a mixed bag of pre-defined automation plugins of type XsltSender, XsltAutomator(both InternalReciever as well ExternalReceiver) as well other custom automators(java). For logging of messages in order to aid debugging of custom automators, we are using a logger "com.xyz.osm.plugin" which is also declared in log4j.xml file that is within omslogging.jar. You must already be aware that the build scripts of assembling, deploying ansd registering plugins also includes omslogging.jar are part of the application ear.
<category name="com.mtsa.osm.plugin">
<priority value="debug"/>
</category>
Below java code snippet is taken from our custom automation plugin classes indicating how the above logger is being used for printing messages.
//Declaration
private static Log log = LogFactory.getLog("com.mtsa.osm.plugin");
mthod1(){
log.info("xyz");
In addition to the above logger, the pre-defined automators XsltSender, XsltReceiver also enable logging from xsl files by making the "log" parameter available. Thus we have lines such as the one below in our xsl files that should print messages to the weblogic console.
<xsl:variable name="addLog1" select="java:info($log, 'transformSiebelActivationRequest: ***** Starting *****')"/>
The logger that allows printing of these lines is "com.mslv.oms.automation".
<category name="com.mslv.oms.automation">
<priority value="info"/>
</category>
These configurations should have ideally allowed one to see messages such as one below getting printed out to weblogic console:
<16-Mar-2012 8:59:36,931 CDT PM> <INFO> <plugin.XSLTReceiver> <ExecuteThread: '19' for queue: 'oms.automation'> <transformSiebelActivationRequest: ***** Starting *****>
Unfotunately after having done all the above configuration, we are still unable to see any such log messages in the console apart from those emitting from SOP and from <xsl:message> inserted in java & xsl files respectively.
I also checked if the log4j sub-system is able to correctly initialize after parsing the log4j.xml. It does and one can confirm it by setting system property log4j.debug=true in setDomainEnv.sh file.
$$$$$$$$ log4j initialization by application classloader for oms.ear application $$$$$$$$$$$$$$$$$$
log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1592141 finder: weblogic.utils.classloaders.CodeGenClassFinder@1112e85 annotation: oms@.
log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/oms/amuube/omslogging.jar!/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
$$$$$$$$ log4j initialization by application classloader for custom automation plugin xyz.ear application $$$$$$$$$$$$$$$$$$
log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1b7a8c5 finder: weblogic.utils.classloaders.CodeGenClassFinder@10bc849 annotation: xyz.ear@.
log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/xyz.ear/ah0eeq/omslogging.jar!/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: weblogic.xml.jaxp.RegistryDocumentBuilderFactory
log4j: debug attribute= "false".
Ironically, logging levels for loggers defined in log4j.xml of oms.ear could be dynamically changed from log4jAdmin.jsp page and the results are immediately visible. However for some reason, loggers defined in log4j.xml of custom plugin application were completely getting ignored. I don't see any warnings or erro messages in the logs indicating that log4j configuration failed for custom application failed. We want to refrain using SOP and <xsl:message> but I am afraid we have no option other than filling up our sources files with them.
Bottomline, how do we get application B(which in our case is the custom plugin) to log messaged the console just like that done by application A(oms.ear).
I am sure OSM developers would like to leverage log4j bundled with OSM SDK to log messages that would aid in trouble-shooting during development cycles. Both application ear files have commons-logging-1.1.jar,log4j-1.2.13.jar, omslogging.jar available in their classpaths. In other words, META-INF/MANIFEST.MF file of oms.war(web module within oms.ear) and xyz.jar(ejb module within xyz.ear) has references to these jars.
Appreciate if one can reply and let me know if they could get log messages to print from custom plugin.
Thanks
Edited by: user3693508 on Mar 18, 2012 11:38 AM

Hi,
We have a custom automation plugin for the OSM application build 381 in our environment(HP-UX Itanium platform). The plugins are bundled in a single ear application "A.ear" which is a mixed bag of pre-defined automation plugins of type XsltSender, XsltAutomator(both InternalReciever as well ExternalReceiver) as well other custom automators(java). For logging of messages in order to aid debugging of custom automators, we are using a logger "com.xyz.osm.plugin" which is also declared in log4j.xml file that is within omslogging.jar. You must already be aware that the build scripts of assembling, deploying ansd registering plugins also includes omslogging.jar are part of the application ear.
<category name="com.mtsa.osm.plugin">
<priority value="debug"/>
</category>
Below java code snippet is taken from our custom automation plugin classes indicating how the above logger is being used for printing messages.
//Declaration
private static Log log = LogFactory.getLog("com.mtsa.osm.plugin");
mthod1(){
log.info("xyz");
In addition to the above logger, the pre-defined automators XsltSender, XsltReceiver also enable logging from xsl files by making the "log" parameter available. Thus we have lines such as the one below in our xsl files that should print messages to the weblogic console.
<xsl:variable name="addLog1" select="java:info($log, 'transformSiebelActivationRequest: ***** Starting *****')"/>
The logger that allows printing of these lines is "com.mslv.oms.automation".
<category name="com.mslv.oms.automation">
<priority value="info"/>
</category>
These configurations should have ideally allowed one to see messages such as one below getting printed out to weblogic console:
<16-Mar-2012 8:59:36,931 CDT PM> <INFO> <plugin.XSLTReceiver> <ExecuteThread: '19' for queue: 'oms.automation'> <transformSiebelActivationRequest: ***** Starting *****>
Unfotunately after having done all the above configuration, we are still unable to see any such log messages in the console apart from those emitting from SOP and from <xsl:message> inserted in java & xsl files respectively.
I also checked if the log4j sub-system is able to correctly initialize after parsing the log4j.xml. It does and one can confirm it by setting system property log4j.debug=true in setDomainEnv.sh file.
$$$$$$$$ log4j initialization by application classloader for oms.ear application $$$$$$$$$$$$$$$$$$
log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1592141 finder: weblogic.utils.classloaders.CodeGenClassFinder@1112e85 annotation: oms@.
log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/oms/amuube/omslogging.jar!/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
$$$$$$$$ log4j initialization by application classloader for custom automation plugin xyz.ear application $$$$$$$$$$$$$$$$$$
log4j: Trying to find [log4j.xml] using context classloader weblogic.utils.classloaders.GenericClassLoader@1b7a8c5 finder: weblogic.utils.classloaders.CodeGenClassFinder@10bc849 annotation: xyz.ear@.
log4j: Using URL [zip:/home/osmwl/bea/user_projects/domains/dev04/servers/osmdev04/tmp/_WL_user/xyz.ear/ah0eeq/omslogging.jar!/log4j.xml] for automatic log4j configuration.
log4j: Preferred configurator class: org.apache.log4j.xml.DOMConfigurator
log4j: System property is :null
log4j: Standard DocumentBuilderFactory search succeded.
log4j: DocumentBuilderFactory is: weblogic.xml.jaxp.RegistryDocumentBuilderFactory
log4j: debug attribute= "false".
Ironically, logging levels for loggers defined in log4j.xml of oms.ear could be dynamically changed from log4jAdmin.jsp page and the results are immediately visible. However for some reason, loggers defined in log4j.xml of custom plugin application were completely getting ignored. I don't see any warnings or erro messages in the logs indicating that log4j configuration failed for custom application failed. We want to refrain using SOP and <xsl:message> but I am afraid we have no option other than filling up our sources files with them.
Bottomline, how do we get application B(which in our case is the custom plugin) to log messaged the console just like that done by application A(oms.ear).
I am sure OSM developers would like to leverage log4j bundled with OSM SDK to log messages that would aid in trouble-shooting during development cycles. Both application ear files have commons-logging-1.1.jar,log4j-1.2.13.jar, omslogging.jar available in their classpaths. In other words, META-INF/MANIFEST.MF file of oms.war(web module within oms.ear) and xyz.jar(ejb module within xyz.ear) has references to these jars.
Appreciate if one can reply and let me know if they could get log messages to print from custom plugin.
Thanks
Edited by: user3693508 on Mar 18, 2012 11:38 AM

Wert SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message ID and no WSRM assertion provided.

Hi All,
Im trying to call this Webservice in SOAP UI and Im getting this error.
The webservice , I Need to use is:
BusinessPartnerSUITEBulkReplicateRequest_In
http://es-workplace.sap.com/socoview(bD1lbiZjPTAwMSZkPW1pbg==)/render.asp?id=84B45EB7B18A11DE2B8D000F20FCB6A9&fragID=&pa…
Can you please help me to avoid it.
thank you for your help
Gireesh P.
Error Log:
Wert SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message ID and no WSRM assertion provided.

Hi Tim,
For this error following are the places that needs to be checked.
1. In C4C the protocol defined in the Communication System should be 5 - Web Services
2. In C4C Communication Arrangement should have the right protocol selected
3. In PI make sure the Communication Channel's are created using provided Communication Channel Templates as part of the standard PI content.
In other words just follow the integration guide available in SMP to avoid such errors.
Hope this helps.
Thanks,
Prakash

CREATE PDF fails with ALC-PDG-null-Generic Log Message java.lang.OutOfMemoryError

Adobe LiveCycle PDF Generator ES (Version: 8.2.1)
The CREATE PDF service fails. It does not convert word documents to PDF. It used to work earlier. We haven't changed any configuration. The Server.log has the below entries:
2014-01-07 10:18:49,536 INFO [com.adobe.pdfg.GeneratePDFImpl] ALC-PDG-001-000-
Job ID for the submitted createPDF job =BXU004275.docx911bb3-b13cac-ba31d8-1e253f-c932e7-fa2bf0
2014-01-07 10:18:52,176 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-024-BXU004275.docx: Time Job Submitted: 1/7/14 10:18 AM
2014-01-07 10:18:52,458 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-021-BXU004275.docx: PDF Settings Used: pdfg Standard 55865
2014-01-07 10:18:52,458 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-022-BXU004275.docx: Security Settings Used: No Security
2014-01-07 10:18:52,458 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-023-BXU004275.docx: FileType Settings Used: Standard
2014-01-07 10:18:52,458 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-017-BXU004275.docx: Job Submitted by User: administrator
2014-01-07 10:18:52,536 INFO [com.adobe.service.ProcessResource] BMC505: Service PDFMakerSvc: Starting native process with command line "C:\\Adobe\\LiveCycle8.2\\jboss\\server\\all\\svcnative\\PDFMakerSvc\\bin\\dll\\pdfgen.ex e" PDF-PD1936a0002 -beginExecutable "C:\\Java\\jdk1.5.0_14\\jre\\bin\\javaw.exe" -endExecutable -Xmx64m -cp "C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-appmon.jar;C:/Ado be/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-appmondata.jar;C:/Adobe/L iveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-bslj.jar;C:/Adobe/LiveCycle8. 2/jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-csa.jar;C:/Adobe/LiveCycle8.2/jboss/ser ver/all/svcnative/PDFMakerSvc/bin/adobe-generatepdf-client.jar;C:/Adobe/LiveCycle8.2/jboss /server/all/svcnative/PDFMakerSvc/bin/adobe-pdfg-common-jaxb.jar;C:/Adobe/LiveCycle8.2/jbo ss/server/all/svcnative/PDFMakerSvc/bin/adobe-pdfg-common.jar;C:/Adobe/LiveCycle8.2/jboss/ server/all/svcnative/PDFMakerSvc/bin/adobe-pdfg-commonbmc.jar;C:/Adobe/LiveCycle8.2/jboss/ server/all/svcnative/PDFMakerSvc/bin/adobe-pdfg-idl-bmc-websphere.jar;C:/Adobe/LiveCycle8. 2/jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-pdfg-idl-bmc.jar;C:/Adobe/LiveCycle8.2/ jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-utilities.jar;C:/Adobe/LiveCycle8.2/jboss /server/all/svcnative/PDFMakerSvc/bin/avalon-framework-4.1.5.jar;C:/Adobe/LiveCycle8.2/jbo ss/server/all/svcnative/PDFMakerSvc/bin/comfyj-2.4.jar;C:/Adobe/LiveCycle8.2/jboss/server/ all/svcnative/PDFMakerSvc/bin/jacorb.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/ PDFMakerSvc/bin/jaxb-api.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/ bin/jaxb-impl.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jaxb-li bs.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_acrobat1 .1.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_autocad1 .1.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_autocad2 007.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_excel1. 3.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_pdfmapi1. 0.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_ppt2.6.ja r;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_project4.4.ja r;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_publisher1.0. jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_visio4.a.ja r;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_word8.1.jar;C :/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniwrap-3.6.1.jar;C:/Adobe /LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/logkit-1.2.jar;C:/Adobe/LiveCycle 8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/namespace.jar;C:/Adobe/LiveCycle8.2/jboss/s erver/all/svcnative/PDFMakerSvc/bin/PDFMakerConverterServer.jar;C:/Adobe/LiveCycle8.2/jbos s/server/all/svcnative/PDFMakerSvc/bin/winpack-3.6.jar;C:/Adobe/LiveCycle8.2/jboss/server/ all/svcnative/ServicesNatives2/jars/adobe-bslj.jar" com.adobe.native2pdf.bmc.PDFMakerServer -IOR IOR:000000000000002249444C3A636F6D2F61646F62652F736572766963652F4D616E616765723A312E30000 0000000000200000000000000D8000102000000000D31302E32302E3133302E353200000DC8000000134A426F7 3732F42522D312F010000000000000000000000050000000000000008000000004A414300000000010000001C0 000000000010001000000010501000100010109000000010501000100000021000000500000000000000001000 0000000000024000000200000007E00000000000000010000000D31302E32302E3133302E353200000DC900000 0000000000000000000000000000000000000000000000000000000002000000004000000000000001F0000000 400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003 -AppServer jboss
2014-01-07 10:18:52,567 INFO [STDOUT] Command line '"C:\Java\jdk1.5.0_14\jre\bin\javaw.exe"'
2014-01-07 10:18:52,770 INFO [STDOUT] [configuration loaded from classpath resource jar:file:/C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-pdfg-com monbmc.jar!/jacorb.properties]
2014-01-07 10:18:53,942 INFO [com.adobe.native2pdf.bmc.WordToPDFConverter] ALC-PDG-001-001-Begin processing job : C:\Documents and Settings\infodba\Local Settings\Temp\pdfg-infodba\6f\40a5-a1cb14-9618a9-a39550-d1e383-217845\native-in.docx
2014-01-07 10:19:04,925 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-016-BXU004275.docx: Job Type: Convert to PDF
2014-01-07 10:19:04,940 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-027-BXU004275.docx: Job Completion Status: Succeeded
2014-01-07 10:19:04,940 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-025-BXU004275.docx: Time Job Completed: 1/7/14 10:19 AM
2014-01-07 10:19:04,940 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-026-BXU004275.docx: Time of Job Execution: 12,764 ms
2014-01-07 10:19:04,940 INFO [com.adobe.aes.web.create.CreatePDFAct] ALC-PDG-001-018-BXU004275.docx: User Connected from Host: 10.2.113.168/10.2.113.168
2014-01-07 10:19:04,940 INFO [com.adobe.aes.web.create.CreatePDFAct] ALC-PDG-001-029-BXU004275.docx: Job Source: Admin UI
2014-01-07 10:19:05,018 ERROR [com.adobe.aes.web.create.CreatePDFAct] ALC-PDG-null-Generic Log Message
java.lang.OutOfMemoryError
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:194)
at com.adobe.idp.Document.passivateInitData(Document.java:1219)
at com.adobe.idp.Document.passivate(Document.java:1055)
at com.adobe.idp.Document.passivate(Document.java:1012)
at com.adobe.idp.Document.getInputStream(Document.java:1524)
at com.adobe.idp.Document.copyToFile(Document.java:1623)
at com.adobe.aes.web.create.CreatePDFAct.execute(CreatePDFAct.java:192)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at com.adobe.aes.web.AesActionServlet.service(AesActionServlet.java:63)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.adobe.idp.um.auth.filter.AuthenticationFilter.doFilter(AuthenticationFilter.java:154)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.ja va:159)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11P rotocol.java:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)

Thanks guys for the response..
I checked the IR and the SAP Basis has been added. Here are the details I got.
Name: SAP_BASIS
Version: 700
SWCV: SAP BASIS 7.00
Available Support Packages: 12
Any more suggesions/feedback will be greatly appreciated.
Thanks

User Defined activity does not log messages

I have created a User Defined activity which calls a unix shell script.
This script writes messages to standrard output ("echo") that I want
the process flow to catch in its log, so I can see the messages in
Control Center Manager.
This was actually the behaviour of my User Defined activity until recently.
I must have changed, unintentionally, some parameter/configuration that
I cannot remember. Maybe some "suppress script-messages" parameter? :-)
Anyone in this forum who knows which paramater I might have changed
and/or how I can get back the old behaviour of my activity?
// Pontus

I had the same experience recently: I was trying to log a message to a Unix file, but the process flow would always fail, even though the script executed well from the Unix prompt.
The problem in my case was that redirection is not supported from within an OWB version 9.0.4 process flow. Once I eliminated the "echo My message > logfile" everything was fine. You can even keep "echo My message" with no redirection and it's still ok.
The above holds regardless of where you put your script -- external Unix file, or as part of an "external process" icon in the flow.
If things are the same in your case, you'll need to figure out an alternative way of logging messages when executing the script. I decided to use external files as flags, by renaming them from the script.
Santiago

Inbound Web Service calls get error "Reliable Messaging(RM) configured, but no Message ID..."

We are setting up the Communication System and Communication Arrangement "Business Partner Replication from SAP ERP".
For protocol, we are using Type 5 - WebServices. See screenshot below.
Our error is that when we send webservice calls to our C4C, we get messages:
1. Web service response is "Web service processing error; more details in the web service error log on provider side"
2. Backend error messages is "SRT: Plain SOAP: Reliable messaging (RM) configured, but no Messaging ID and no WSRM assertion provided"
We have sent messages from PI and also independently thru soapUI.
So it seems the C4C in the backend is stuck on the RM messaging protocol setting.
Appreciate any and all assistance.

Hi Tim,
For this error following are the places that needs to be checked.
1. In C4C the protocol defined in the Communication System should be 5 - Web Services
2. In C4C Communication Arrangement should have the right protocol selected
3. In PI make sure the Communication Channel's are created using provided Communication Channel Templates as part of the standard PI content.
In other words just follow the integration guide available in SMP to avoid such errors.
Hope this helps.
Thanks,
Prakash

What's best practice for logging messages in pageflow?

What's best practice for logging messages in pageflow?
Workshop complains when I try to use a Log4J logger by saying it's not serializable. Is there a context similar to JWSContext that you can get a logger from?
There seems to be a big hole in the documentation on debug logging in workflows and JSP pages.
thanks,
Rodger...

Make the configuration change in setDomainEnv.cmd. Find where the following variable is set:
LOG4J_CONFIG_FILE
and change it to your desired path.
In your Global.app class, instantiate a static Logger like this:
transient static Logger logger = Logger.getLogger(Global.class);
You should be logging now as long as you have the categories and appenders configured properly in your log4j.xml file.

Frequent "Internet Configuration leased" log messages

Similar Messages

Maybe you are looking for